Wil Renczes
Forum Replies Created
-
Actually, you don’t even need to switch to the Pen tool anymore – if you have the selection tool, hold down Ctrl + click to create keyframes…
-
I’m not familiar with the Convergent box, but I’ve messed with other analog to firewire converters, and most generally drop the ball when it comes to timecode data (I think I messed with the Sony DA2 at the time, and it only converted the video & audio). The app relies on the timestamp data embedded in the DV stream, so it’s probably not there. You’ll probably need to talk to the guys who make the converter box… (does it have as RS-232/422 input that you feed your deck into?)
-
For 1.5, same as XP, ie 2 Gigs. Premiere Pro 2.0 is aware of the /3Gig boot.ini switch in XP, so it will make use of 3 Gigs if available & enabled.
-
Actually, the sluggishness you refer to between switching apps is probably because Premiere Pro (esp. 2.0) tries to play nice with memory with other apps. Premiere maintains a memory cache of video frames (for example, when you’re scrubbing over un-rendered material – it takes a bit to composite the image, but the app hangs onto the frame in case you might scrub back over it again), and this cache is flushed when Premiere loses application focus. It also tells any plugins responsible for importing media to ‘let go’ of their files so that they’ll be accessible (ie writeable) to other applications. So the lag you’re experiencing is likely when Premiere comes back to focus, it needs to re-open various media files & possibly re-render certain frames (thumbnails, or if your CTI is parked over an area that needs rendering, etc).
If you have your thumbnails turned on for all frames, try either setting it to tail/end or disabling them entirely – see if that makes an impact at all on the lag time you’re describing…
-
If the clips are showing up as video only, odds are that the toggle for Audio in the capture window was off when the batch list was created. (I’ve heard that this can happen to people accidentally via keyboard shortcuts.)
Try selecting one of the clips in the project window & make it offline, then double-click on the clip to bring up the offline clip dialog. It should show you whether or not the clip was captured as video-only. (The drag is there’s no way currently to reset this back to a/v, so you would need to rebuild a batch list for the video-only clips.)
-
FYI, within Premiere, you can change the reel name – under the File menu, choose the ‘Timecode…’ entry after selecting a clip in the project window.
(Unfortunately, there’s no way to select multiple clips and change them all with this dialog in one shot. Sounds like a good feature request…)
-
[Carl] “.- Imagine being able to apply an effect over a large number of clips (ie color correction) in just one step. Imagine to crop several clips at the same time. That’s what you can do with the Avid’s implementation of invisible layer (and you CAN’T with Adobe’s one). You can even put several effects on their “invisible layer” (It’s called FILLER)”
I think you’re just using the wrong tool for the job.
There’s a different way to do this in Premiere: what you do is create a separate sequence (call it Master, if you like) – drop your existing sequence into it as a clip, then apply your color correction (or any combination of filters) to the embedded sequence. Very powerful workflow. What I like about this over the invisible layer method you describe is that I can copy / paste the filters to any combination of sequences – if I would want to port your master color correction, with the invisible layer method, I would need to copy & physically move that invisible clip around between timelines, and the track layering may not match up, etc. Feels more kludgy…
-
Two things off the top of my head:
– check/update your graphic card’s display drivers to the latest available. (Also, you can try messing with Premiere’s playback settings – there are 3 modes: hardware accelerated, normal (regular D3D), and GDI. Try each out, see if it has an impact on the problem)
– same idea, but for your audio drivers. Are you using the default audio settings, or did you try using a custom ASIO driver for some specific sound card?