Sean Oneil
Forum Replies Created
-
Thx!
-
I’ve seen this a lot when the system can’t keep up. It seems to happen in lieu of getting a dropped frames warning.
-
Robert Etoll’s stuff is the golden standard for trailer sfx. He isn’t cheap though.
-
[CharlieX] “….err, I’d need windows for that 🙂 “
If there was a Mac product, I point you to that. But there isn’t.
I have Paralles. It’s pretty darn useful when stuff like this comes up.
-
[CharlieX] “Anyhow, I’m demuxing their m2v and ac3 files for something (no time to compress the HD master with DVDSP right now), and would REALLY like a way to remove the 3:2 without having to convert that m2v file into a quicktime and then recompress a m2v files. Don’t want a generation loss. “
MPEG Video Wizard for Windows.
https://www.womble.comDownload the demo and see if it works. I used this thing in the past to edit MPEG files. It does everything intelligently without re-encoding.
I never tried pulldown removal, but it says it “Video frame rate conversion and scene change
-
I’m running FCP 6, Kona 3. Different systems. But I’m absolutely seeing it the way I described. Of course, maybe I just need to trash preferences and it will stop. Who knows.
-
I had to deal with this recently. Thanks for mapping out the steps. I didn’t remember what it was I did to solve it.
BTW, I don’t use DV50. So this probably applies to any YUV codec.
-
[Tom Brooks] “I’m puzzled at the moment. I don’t have any digibeta in house. I’ll try it with some beta-sp though”
Do you have Quicktime 7.2?
I’ve been having a lot of problems lately with the Mac not recognizing the right field dominance. Today was a special kind of nightmare. Exporting to Compressor (either directly or otherwise), the deinterlace filter does not work whatsoever. Doesn’t matter if I manually choose even or odd. I’ve tried SD source and 1080i source.
Anyway, that could be related to the behavior I’m seeing in regards to this discussion.
-
No. The sequence is identical to DV NTSC – just changed it to “None”. It’s outputting 525i 8-bit, viewing on a Panasonic BT-H1350.
It could just be a difference between the LHE and the Kona 3. Or maybe because I captured it from a digibeta and not DV (but then why does changing the clip to None work fine?).
-
HOLD UP!!! I think you are mistaken Tom.
I just played around with it. Do NOT put a DV clip set to “lower field” on a sequence that is set to “none”. Viewing it on my external monitor (via Kona 3) the image is horrible. It appears to be line-doubling one field only while throwing away the other field – which of course equals garbage.
Change the clip to “none” as well as the sequence and it looks great. So I think this is mandatory – not just a good idea.
BTW, this footage was captured as interlaced from a digibeta. So even in this case it’s a clean process to switch between interlaced and progressive-scan.
You are right in some sense. FCP does not require rendering when placing lower-field in a “none” sequence. FCP knows there’s really no difference. But appearantly the Kona does not know this. And who knows what other plugins don’t know this either.