Tom Donnelly
Forum Replies Created
-
Well, I already use it to back up main system drive – I was not aware that it can be set up to back up specific drives, and more than one instance, ie boot drive to a TM drive, and then RAID to an entirely diff drive.
Can it?
-
Looks like that software is no longer supported as of 10.7 Lion.
Anyone else?
Tom
-
Thanks, guys, all very helpful info. The spots were encoded and delivered successfully. Just wanted to point out that the last 3-4 few replies in particular were instrumental in proper encoding for this particular workflow for those stumbling upon this post 3 years from now…a lot of the search results that I came up with before posting were not clear in their success, wanted to make sure that others with this issue know that this worked.
And now, the best part – the final invoice!
-
Thanks, trying pulldown now.
To confirm – I am frame rate to 29.97 in the PRHQ dialog box, set duration to 100% in Compressor, setting rate conversion to fast, deinterlace to fast/upper field first (staying 1920×1080), and also setting “interlaced” to “top field field” in the ProRes HQ-specific dialog box. This will provide correctly interlaced 29.97 footage, yes?
What should I see different than the repeated fourth frame – a blended 5th one (field of each image?) or a split frame if I view fields in a 59.94 comp in After Effects for instance? I would like to be able to proof that it is done correctly…
Thanks!
-
Thanks, that’s what I was resorting to, but if it’s the correct workflow than that makes me feel better.
Follow-up question:
Several of the stations that I am submitting to said that they would accept a progressive frame file for delivery, but if I introduce interlacing myself at this point, is there less chance that something they do, beynd my control, would make the image quality not look ideal for air? Or progressive/interlaced delivery is irrelevant?
-
Grrrrrrrrr….
Looks like this is Safari 4 bug. Firefox still working correctly.
TD
-
Do not have FCStudio 2 on that machine, using FCP 5. Thus, Compressor v.2.3. SO – cannot first transcode to ProRes, or I would be using that (this is actually for a co-worker at a different location than me – trying to find a decent editing codec for him since he does not have access to ProRes.)
(Unless I’m mistaken – I know there’s a ProRes decoder available – is than an ENCODER as well for those without FCP Studio 2?)
Exporting directly from QT to the AIC DOES work, which is why it not working in Compressor is such a mystery. All other formats coming out of Compressor work fine.
He just tried MPEGStreamclip per your suggestion, and it appears to work, so MUST be a Compressor issue. He has already uninstalled and re-installed the entire FC Suite.
Argh.
-
Footage comes from a PC, Windows XP, Service Pack 3
Encoded with FRAPS codec, decoded on Mac using Perian
Attempted compression to Apple Intermediate Codec on Mac OS 10.4.11
Compressor v. 2.3
Quicktime v. 7.6.2 -
One final thought – its almost as if the AJa IO LA is not capable of even passing through something as large a res as an HD signal (through any of the outputs…), and breaks it up before it hits the monitor – is this possible? As SD files, and outputting an SD sequence, seem to play crisp and fine to the CRT.
TD
-
Additionally, I opened an old SD sequence, filed dominance set to “none,” and full of frame-based animation. This stuff plays perfectly on the monitor.
I pasted in all of the HD stuff, various codecs and resolutions (FCP auto-scaled that stuff to be the correct size to fit in the SD frame…) and that stuff played great there. I changed seq settings to make the seq an HD res, and then 1.) All of the HD stuff is suddenly small and I would have to go through sequence manually, increasing the size and changing the “distort” pan in the Motion tab for every clips and 2.) – when I do this to one clip just to see if it plays w/out the jaggies, no dice, jaggies still present…
Double-argh.
TD