Misc Bugs Digi will not fix

[PTcomposer]

1.) Session length. "Edit Window Default Length" has no effect on existing session, leaving you with 12 hours of time no matter how long your material is. And no, it's not because there is midi or automation data somewhere at 12 hours. I suspect this may be the reason why notation view takes minutes to open when dealing with a huge number of midi tracks, but can't be sure.

2.) Anyone ever tried looping midi regions? Sometimes, on a perfectly quantized MIDI region, Pro Tools will not include a midi note at a cut. The only way to have the midi note at the cut duplicate is to slightly nudge it off the grid first. Effed up.

3.) Ever try editing midi in region view? After recording midi data, upon using the selector tool to select and cut part of a midi region, that region will "snap back" to it's original size seconds after making the cut. The only way to permanently trim a midi region in region view is to consolidate that region immediately after trimming.

4.) Track Colors. WHY CAN'T WE GET TRACK COLORS TO IMPORT WHEN IMPORTING SESSION DATA. ARGH.

- a frustrated film composer

[yanncrusoe]

This explains some hassles im having..frustrating.

[DigiTechSupt]

1) We've got this logged for a fix.
2) Are you possibly using Real-time properties? Can you send me a session that exhibits this problem? I want to be sure of what's happening before commenting further. Send to vi [at] digidesign [dot] com and include the thread number (246638) in the subject of the message.
3) I'll have this looked into
4) This is on the list of features, though I can't say when it will be implemented, exactly.