Tim Kolb
Forum Replies Created
-
Unless you’ve checked the box to “Use Previews” as an encoding source, the location of the scratch disk shouldn’t really affect this process outside of using conformed audio perhaps, but that would be in the location targeted for cache…
Are your encoded output files also targeted back at the NAS?
One thing to keep in mind…editing doesn’t have the hard, constant, simultaneous read/write duplexing going on that encoding does…it’s more read-heavy. If all the files need to be read from the NAS, and also the finished file is being written to that same device, the network connection may easily be max out in both directions…the reads from the disk actually slowing down the writes to the same disk and vice versa.
On a bigger disk unit, I don’t know if it would be a problem, but you might be uber-loading your NAS depending on what sort of data you’re using.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
It sounds like the loss of internet is simply a symptom of your whole network going offline sporadically.
Does it happen more often when rendering using assets that are in use on one or more of the other workstations?
What sort of throughput are you designed for…vs what kind of throughput are you expecting?
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
There are a few key behaviors that changed in CC…
Not a lot of them, more sort of “modality” changes…for instance, “Ctrl+D” still places the default transition, but where CS6 places it any clip edge on a selected track nearest to the playhead, CC actually prioritizes selected clip in/out points or entire clips (will apply to both in and out) over a clip on a selected track closest to the playhead…which only works now when nothing else is selected.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Hmmm…that’s interesting.
Andrew…are the audio settings consistent between your source video, your sequence, and any external device (video I/O card, etc) you have?
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Unfortunately you have a professional application running on your multi-purpose machine…and most of us want encoding to be as fast as possible so we can get the file to our client (who always needs everything yesterday) and get on to other things.
Adobe’s approach is to grab all the CPU it can get it’s hands on and use it to encode faster. It’s one of the more efficient applications that exists in this sense.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
…don’t take any of my input as trying to justify the playback lag in relation to timeline zoom thing as -not- peculiar…
I’m just looking for anything that could help or improve performance.
…it’s still weird.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
FCP7 was a 32 bit program that probably didn’t bite down as hard on your CPU as 64 bit PPro/ME does when encoding.
What you’re seeing isn’t the speed of the connection…you’re seeing the CPU trying to simply process and load the pages. Everything on your computer uses the CPU…everything. If some program is dominating the CPU resources, every other process on the machine will slow, web browsers, anti-virus, media players, the operating system itself…it all uses the CPU.
The data can come in as fast as you like…if you can’t process it, it will seem less reponsive. I’m guessing that if you look at all the other things I mentioned, you’ll find that they slow down too.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Oh…that explains a lot actually. I wasn’t picturing a lot of audio tracks…are there adjustments/filters on all of it?
If you select “render audio when rendering video” in the preferences, at least rendering a preview would render a single track of preview audio as well.
MPEG audio is typically “conformed” creating uncompressed audio tracks from the clips to enable more responsive editing than you would have if only using the muxed audio inside the MPEG file.
The issue -may- be that your conformed audio is on a drive that isn’t fast enough, or is full…or is the system drive…the conformed audio files are going to wherever your preferences-media-media cache files are targeted.
It also never hurts to use the “clean” media cache database button from time to time if things seem inexplicably clunky.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
In theory, you could interpret one of your video clips to 30 fps and check to see if that takes care of the problem…also in theory you could interpret all your video to 30fps and cut the show, and just make the adjustment on the back end if you have a broadcast job…
Some audio recorders will write video timecode to an audio file, but interpreting the audio clip by video framerate probably isn’t possible…
The error is so small, that you should probably make the adjustment in Audition or a digital audio application. The speed of a 30 fps equivalent clip reduced to 29.97 fps ends up being 99.9% speed…a pretty subtle adjustment.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
The cards didn’t make the “white list” at whatever point Adobe published it, but they may be too new…the 650M and 750M are on the list.
CC version of Premiere Pro works with any GPU on the machine that meets minimum spec (1 GB RAM is a little meager, but it meets the minimum requirement).
I suspect if there is some issue with the card’s functionality or a bug that seems to be specific to a card not on the “white list” Adobe just wouldn’t guarantee compatibility…but there are a LOT of users using cards not on the white list (CUDA or OpenCL). It’s far from unheard of…
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor