[Tim Kolb]

For PPro CS3, you’d also have to specify what sort of timeline you’re running.

You could go to XDCamHD EX using MPEG Stream…or you could use an intermediate codec like CineForm.

You need to decide what format you want to edit in (is the rest of the project shot as something else?…or is it all DSLR?) …and convert to that.

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

Hmmm…

Even on a four-core machine I had a chance to quickly test, both BCC Light Wrap and Digieffects Lightwrap from Delerium2 seem to render pretty quickly…in fact I would have to say that this would be the first time I’ve ever checked them and I was a little surprised at how fast they were…and they seemed to light up all four cores for the 2 seconds they took to render an 8 second segment…again on a dual-dual core system.

I have a CPU gauge on the desktop and the task manager performance tab all seem to indicate the same thing…all four cores seem to spike.

…and of course I’m not using anything but that effect in an attempt to isolate it.

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

After install and successful activation, there are additional codecs that need to be installed, the MPEG codecs are part of that.

Did you de-activate the software before you uninstalled it? There are a finite number of activations available for each license…

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

You aren’t running the trial version for some reason?

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

You would have to do any audio work on individual camera shots in the multicamera sequence itself…where you have access to all the audio in the source tracks.

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

Hi John,

Well…Light wrapping isn’t a simple effect to calculate certainly…but how do you determine it’s only working on one core?

When I put it on a clip and render a preview, I seem to use all the cores…so I have no idea if other functions are triggering those other cores, but in this case, lightwrap was the only thing active at all as I tried to isolate it.

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

You can make a custom sequence setting with framesize and frame rate of the file…look in help for “custom sequence setting”.

Or…you can drag the video clip over the “new sequence” widget on the bottom of the project panel and it should use the clip settings as the guide…

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

[Jeff Greenberg] “Decode is free in QuickTime pro. Can’t encode ProRes on Windows at all. (Turns out both of us mentioned Calibrated’s XDCam)”

Ooops…I should have looked up-thread a bit more…it’s the best option I can think of as well.

I know I use to have to install the ProRes decoder separately on Windows at some point back there…I know I haven’t in the last few years, so I wasn’t sure if the ProRes decode capability was in the free version of QuickTime or not.

I know there is no ProRes encode on Windows…(unless you have an HDSDI card and a KiPro).

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

Yes, Dragan…your system is excruciatingly limited on power. I now see that you mentioned your system specs in an earlier post and I apparently skipped over them.

A 5400rpm harddrive is a severe limitation…I’m not in the least surprised that you’d have playback problems on a large HD file. Your processor is also very limited. When you’re decoding, that will affect it. It’s likely that PPro is dropping the clip to 1/2 res decode when you re-import it and that’s why PPro can play it while an outside player (like Windows Media Player or whatever) is trying to play it back at full resolution.

Now…why these files are a problem for the TV station is a mystery to me…

I assume you’ve tried to delete the source clips at the “glitch” points from the edit timeline and tried a full export to see if it implicates a bad source file?

TimK,
Director, Consultant
Kolb Productions,

[Tim Kolb]

[Jeff Greenberg] “THe problem is, that he has the XDCAM codec in HIS QuickTime because it came with FCP; I don’t think that Premiere Pro includes the XDCAM codec for QuickTime.”

Premiere can’t include it…because QuickTime doesn’t have it on Windows…like the QT wrapped HDV and DVCProHD codecs…and of course, ProRes encoding is only available to FCP owners.

Premiere Pro handles the material in it’s native form, but once it’s wrapped as QT, the essence of the file has to be read through QT…and that’s all Apple’s call as to whether or not the decoder is in QT. It certainly adds unique value to FCP, but can make the traveling potential for these files rather limited.

You might try https://www.calibratedsoftware.com/QXD.asp on the web…the “XD Decode” product would probably get you rolling with the material if it’s just rewrapped XDcamEX files.

The good news is that if it’s been transcoded to ProRes, you should be able to use QuickTime to read it and you’re set…the data rate has probably gone up by a factor of 5 at the least if this is the case, but the ProRes codec runs rather smoothly on most systems.

I always run QT Pro (it’s likely the most no-brainer 30 bucks you can spend in this business), so I’m not sure if ProRes decode capability is in the free download version of QT for Windows, or if you need to spend the couple of bucks on QT Pro…

TimK,
Director, Consultant
Kolb Productions,