Gates Bradley
Forum Replies Created
-
It’s still not working for me. I know my keyboard shortcuts are mapped properly. I can even select Sequence>Apply Default Transition and nothing happens. However, when I drag the transition from the effects window, it works fine (my default transition is cross dissolve).
Not sure what else I could be missing, but at least the option is no longer greyed out in the menu bar.
-
[Kevin Monahan] “5. Make sure the V2 track is selected and the playhead is parked on the beginning or end of the clip, and then type CMD+D.”
First off, I apologize for posting reply after reply. Poor form, I know. But, in regards to this issue, I still do not seem to be able to make it work. I’ve posted an image of my timeline. As you’ll see, I have both video tracks selected (though I’ve tried this with only track 1 selected as well). My CTI is on my edit, the clip is selected, but still I can not apply the transition.
-
Again, thank you for your response, but I fear I erred when describing question #4. I wrote that I wanted to see marker information in the “project” panel. I meant to say “program” panel. I’m getting my ‘P” panels mixed up.
Basically though, the issue is I created a marker, and I labelled it. I wanted to know how to be able to view that label. When I skip to the marker, I don’t see anything. It defeats the point of labelling a marker if you can’t see what you’ve labelled it. But I imagine it’s just a setting somewhere that I am unaware of.
Again, thank you for your detailed responses. I really appreciate you taking the time.
-
You, sir, are a god among men. I can’t thank you enough.
-
Tom, I’m in the same boat, experiencing the same problem. Thank you Ben for the very helpful info about activated tracks. However, it still is not solving the problem for me. Did it for you Tom?
I still cannot use the keyboard shortcut of “Apply Default Transition” on a clip if it is not adjacent to other clips. Am I missing something stil?
I really like some aspects of premiere, but the actual editing in the timeline (which really, is the heart of what we do) still feels a step behind FCP – somewhere between Final Cut and Avid. I feel like there is no sure-fire option at the moment with all of the big 4 options (i’m considering FCP 7 separate from FCPX) asking us as editors to give up something crucial in one area, even as we gain something in another. argh.
-
Hey Jon, thanks a lot for responding. This is kind of what I feared, but maybe you could help clarify things further? It seems to me regardless of what I do, I’m just going to have to wait for something to get proper fast, real-time playback on things. I was initially under the impression that this sort of hardware accelerated playback was inherent to Premiere CS5 (Adobe fail to mention that half the video card market is excluded in their press releases).
The thing is, the sort of scaling down of the res and/or frame rate to achieve realtime playback is already something that is done in FCP 7. Do you think that, given these features existing in both programs, Premiere, via its 64-bit nature would still see a significant performance boost? That promised boost is the single biggest reason I was willing to completely overhaul my editing workflow, but now I’m starting to feel like I’m doomed to 2008-level performance regardless of which NLE I choose.
When do you guys think things will just be what they say they are? Shoot, OSX has been touting it’s 64-bitness since Panther back in 2003.
-
I likewise am having the same problem. As well, I am a first time Premiere user (what’s more I’m working on a PC for the first time in 8 years). I am running CS5, with 24Gb of RAM and 2×12 3.3Ghz processors, so am not lacking for power.
The sequence looks fine in After Effects, but super jittery like I applied the wiggler or something when I look at it in After Effects.
I am using AVIs in the Intel IYUV codec (which I know nothing about, but don’t believe uses i-frames). All I am doing in the AE comp is starting way zoomed in on an image (300% or so), and then pulling back. Nothing crazy at all. A portion of this zoom is time-remapped to create a speed-ramp effect, but this jitter effects even the parts playing back at their normal frame rate.
Also this problem persists even if I render the sequence in Premiere.
I was excited about the easy workflow between AE and Premiere but so far it’s been almost all headaches. Any help would be much appreciated.
Gates
-
I didn’t even realize Pro Tools assigned frame rates. Very good to know.
-
John. A big word up to you. It worked! It’s just one of those things where machines get confused with all of the bouncing around of metadata (or looking for it when there is none). One of the many pitfalls of the modern prosumer workflow. You completely saved my neck. Kudos to you sir.
I should add for others encountering this problem that for some reason, on the really long clip (18min) I had to change the sample rate in Wave Agent from 48k to 48.0048khz. I do not know why, but I did, so if the above solution doesn’t work for you, if the sound is still a little ahead of the video, try this. (Or if it is a little behind try changing it to 47.9-something khz – you will see the option in wave agent).
-
Dang, I am having the same issue, but this solution did not work for me. I am cutting a feature length music doc and the film has to be ready in 2 days for a premier, and I can’t figure this out. I didn’t notice it until the last performance, which is roughly 20 minutes.
I am using a sequence based off of the Panasonic HVX 720p native settings: DVCPRO HD, 23.98 frame rate, 48khz audio. All of my audio is mixed by a sound engineer in ProTools and brought back in. It never changes sample rates, however- they stay the same.
Anyone have any other ideas? Or perhaps I am performing incorrectly this solution. I deleted the protools mix file from my timeline and project, did an easy setup as suggested, and then reimported. It not only did not work in my edit timeline, but I made a new timeline and it did not work there either. I’m at a total loss…
[Final Cut Pro 7.02; OSX 10.6.4; Macbook Pro 15″; 4gb RAM]