kflorian Calculating status...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Thanks Ken, that's what I needed.
OK, here's the story: these files will never play on a Windows machine. The AVIs won't al all, and the MOVs won't either--at least, not without some help.
The MOVs are using the Apple Intermediate Codec (that's what the "hdv2" business is all about), and Apple never released a decoding component for QuickTime on Windows. Similarly, when you converted these to AVIs, all that happened was that the encoded video got moved from one box (a QuickTime MOV) to another box (a Microsoft AVI). This doesn't enable decoding--even though the codec is reported as MJPEG, which is basically a false positive--so that's why the AVIs won't work either.
The AVIs are pretty much a lost cause, I'm sorry to say, but you might have some luck with the QuickTimes. Try the demo (yes, another thing to install
) of the Calibrated{Q} XD Decode components. These should crack open the MOVs so you can use them on Windows. There is a watermark, but at least you can see if it will work.Barring that, you will have to go back to the Mac and actually transcode these files using a different codec, rather than simply rewrapping them. If you need to do this, I'll be happy to provide some thoughts on that subject. Let's see how you make out with the XD Decode plugins (and if you want to purchase them), and we'll take it from there.
EDIT: After looking a little more closely at the MediaInfo report, the AVIs don't have the AIC codec, but might actually be MJPEG. For giggles, try changing the extension to MOV and see what happens...
| -
-
Hey Ken,
Sorry, I missed the part about the AVIs previously working. I tried to follow the thread, but got in late and couldn't follow all the permutations
Theoretically, nothing major should have changed as far as format support between 5.0.0/5.0.1 and 5.0.2/5.0.3, but that is a question and consideration for the engineering team. You don't happen to have an itty-bitty sample of one of these files you could upload somewhere for testing, do you?Regarding Calibrated: check out this page at Calibrated for information and a solution involving a customized XML file. It's designed to specifically deal with the slow-down when decoding XD/HDV formats with this plug-in. I actually communicated with Greg at Calibrated (a very helpful guy--contact him via the website if you have questions and he will respond quickly) about this issue, and here is what he had to say:
Per the XML file - yep it can be used with Calibrated{Q} XD Decode for Windows too.Basically the XML file is modified from the one that comes with PPro - and it just tells Adobe CS5 applications (AE and PPro) that our Decode codecs support native YUV decoding - thus PPro will ask our Decode codecs for YUV frames which in turn makes the performance/playback much much faster.Without the XML file, PPro asks our codecs for 8-bit RGB frames - which then takes a big hit on playback - as our codecs must first decompress the data to YUV and then convert the YUV to RGB and then hand to PPro. The XML file let's PPro know that it can just ask for the YUV frames directly.That should get you up and running in short order, at a decent speed. This is the only solution for these files on the PC that I am aware of; yes, there is cost associated, but it may be worth it to you. The other "free" solution as I alluded to before, would be to convert these to a wholly different codec on a Mac. This assumes you have ready access to a Mac to do this; if you want, I'll suggest some codecs that will preserve the original quality and be cross-platform.
As far as MainConcept is concerned: for the MOVs, it's not necessary (if you go with Calibrated). Why it's not functional with the AVIs is a mystery... still scratching my head over that issue...
| -
-
Rerendering the MOVs is a much bigger proposition because I'm not cool enough to have a mac friend with the right camera and cpu....
That's funny...I think my last question is what is the optimal cs5 editing preset for the MOV files I have?
If this is the only footage you'll be editing, the simple solution is to just drag one of the clips to the New Item button at the bottom of the Project Panel; it's the one that looks like a dog-eared sheet of paper. This will cause Premiere to create a new sequence that matches your footage parameters as closely as possible.
Generally speaking, however, there is not really an "optimal" preset for any given footage type. Premiere Pro is pretty flexible, in that you can use footage of any sort in any sort of sequence you want or need. Certainly, in most applications, you want things like frame size, pixel aspect ratio, and frame rate to match your footage, but this not always necessary or even desired. I frequently work in sequences that are almost completely different from my source footage--it really is dictated by your personal working preferences and your desired output. For example, I work frequently with 1080i/p assets, but need to output to an SD output; in cases like this, I don't even bother with an HD sequence preset.
How's that for non-commital
Anyway, glad you're on the way to resolution. Wish it hadn't cost you a C-note, plus!
| -
- 10 points awarded for Correct Answers
- 5 points awarded for
-
10,000+ points
-
1,001-10,000 points
-
501-1,000 points
-
5-500 points
-
