Paul Neumann
20
COW Coins
Forum Replies Created
-
Try setting up the timeline in a native adobe timeline. Turn off the Matrox. I used to see this problem with Axio all the time on mp4 exports of any considerable length. Short clips were ok, long stuff got iffy.
-
How’s the level on that clip? There’s a “mute clipped audio” setting that’s given me fits before.
-
Though if you change a sequence name in the project bin it does change it on the timeline even if that sequence is currently “open”.
-
Highlight the clip in the timeline, highlight the source clip in the bin, alt/option drag the source clip onto the clip in the timeline. That should replace the modified clip but also keep any other effects/adjustments you may have done to it.
-
Like so many Adobe products it pays to think like Photoshop to get the most out of what you’re working with. Stacking adjustment layers, multiple instances of effects at different degrees, multiple blend modes, etc. On the surface it looks like an editor but underneath there’s so much you can do. You always heard After Effects as “Photoshop on steroids” and if you take that same thinking into your PPro environment a whole bunch of things open up for you.
-
I hold down the command key a lot when I’m in a super detailed situation. Total fine tuning.
-
Send one of the clips’ audio track to Audition and then bring it right back as rendered and replaced. See if you get the same results. Just curious. I’ve seen PCM conversion issues in the past though none in quite a while.
-
I ran CS/Matrox set ups for years as having a native format to work with was always top priority as was SDI and/or component in and out. Once CS4 came out with 64-bit and I was able to load my HP workstation (8200?) up with 32gig of RAM I couldn’t understand how anybody could still WANT to edit in 32-bit regardless of platform or editing software. Then came CS5 and the CUDA cards. Got the upgrade, got the card and kicked Matrox to the curb. Never looked back. So I’ve been using CS since v1 through XP to Vista-64 to Win7-64 and have used it for everything imaginable. Couldn’t have been happier.
I run CS5.5/6 and on a MBP now with no TBolt peripherals but a 27″ Cinema and it works better than my old HP workstation. 8 gig of ram and nothing else added. FCPX on the same machine is a freaking nightmare. Slow, clunky, lost projects, projects changed (from 1080/29.97 to 720/25? Really? and no way to change it back!) and damaged after beachball induced restarts.
I like FCPX. I really do. There’s a lot there to like. I just don’t like the way it runs. I CANNOT watch footage render knowing I’d be zipping through it were I in PPro. Maybe that’s just me.
So everybody has their experience and that’s mine. If anything starts mucking up on your machine the first thing I’d start with is to go totally native and pull any I/O out of the mix and see what happens. Getting out from under Matrox’s thumb was liberating. It’s my opinion that that’s how all this editing software is developed despite any 3rd party’s best intentions.
-
Unfortunately you can only add notes to timeline markers.
-
Are you saving your caches next to your source files? If not, that could be your problem.