This content has been marked as final. Show 17 replies
Opening maximized instead of dual screen.
Pop up boxes astride the bezels between twin monitors.
Titler templates only on primary monitor.
Titler layout not preserved between titles.
Timeline doesn't (quite) display one picon per frame (PAL) at maximum zoom.
Audio segments that require rendering do not always generate a 'rendered' line in the timeline to show that they have been rendered.
Garbage matte problem. Oops! Sorry, I didn't notice it on the list.
Column picker in project panel always resets upon closing and re-opening PPro application.
Workspace layouts for timelines leave multiple "No Timeline" tabs open when switching between projects with varying number of timelines open.
Fast Color Corrector's white balance color picker (eye dropper) does not always pick up color from Program monitor when the eye dropper tool is selected and a reference white object clicked on. Behavior sporadic--sometimes it works, sometimes not.
(I need someone else to confirm this, but...)
When viewing File Properties for a P2 MXF clip that has had its metadata edited in an external program (like Panasonic P2 Viewer, or P2Forge), PPro crashes. This doesn't happen with clips that haven't had their metadata edited, or with clips that have metadata recorded in-camera.
In the effects panel where you can type a word in 'contains' one cannot select the whole word to type in another word (like in all the other versions), one has to delete the word first.
You have to preform 'reveal in project' twice before the actual clip is revealed.
A note on Ann's bug...this is not actually a bug, this was by design. The little "x" to delete the word (1 step process) was considered preferable to selecting a word and hitting delete (2 step process).
I know, sometimes I am still used to the old way I'm trained to do it - and the way After Effects makes me do it - that I wonder how much time I'm really saving ;)
But it was made to work that way, so technically, and request regarding this functionality should be considered a feature request and not a bug.
About revealing in project...what do you mean you have to do it twice? When I choose "reveal in project" from the timeline, it always goes right there for me, on the first try.
Clicking a sequence in the project panel (icon view) and nothing happens.
Yes, Alt+double click will open it but what if I only had one arm. :)
> About revealing in project...what do you mean you have to do it twice? When I choose "reveal in project" from the timeline, it always goes right there for me, on the first try.
The first time it just opens the bin in a seperate window, the second time it finally selects the clip.
This has turned out to be a surprisingly short list of actual bugs.
Should be easy for Adobe to sort them. Especially considering two of them worked fine in CS2.
Titler , Garbage mattes...
Export to Encore - doesn't remember previous target folder.
How do you know it's supposed to, David? Is that a real bug, or just the way it's designed?
I don't know. But no doubt the developers can work that out.
But since it always points to a particularly obscure folder and not to that set in Preferences for DVD encoding, I strongly suspect an oversight = design bug.
I have one!
If you make a title in Premiere CS3.2.0, then click the "New Title Based on Current Title" button and enter a name for the new title that includes a full stop (period, one of these ".") the program does not include any of the portion of the new title's name after the full stop. So for example if you name the new title "test.01test" the name that appears for this in the bin is "test" rather than "test.01test"
This is a real pain as I always number my titles 01, 02, etc and if a client wants a new title inserted between 01 and 02 I call it 01.5. Not anymore I can't! I'm pretty certain this is new in 3.2.0 but can't be 100% sure.
I have reported this as a bug using the bug report form.
>I strongly suspect an oversight = design bug.
Hmmm. A bug is more of an unforseen event as a result of bad programming. If the developers wanted to point to a certain folder, and it didn't, that would be a bug. If it just doesn't work the way you think it should, that's not a bug. A design flaw, maybe. But not a bug.
Yours sounds more like a Wish List item than a genuine bug, which is what Craig was looking for.
It sounds a lot more relevant than semantic arguments, though. BTW, see my edited version.