Tim Kocher
Forum Replies Created
-
I know it is 8.5 years later, but THANK YOU! I wish I had bothered to look for a solution YEARS ago, as this always bugged me. I’m working on a project right now where I have to do this like 10 times every hour, so this is a life-saver. Better late then never I guess. THANKS AGAIN!!!
-
Hi Ole:
I am in a similar situation and mindset (where I don’t care about people with 15-20-year old DVD players) and would really like to keep everything at 24p throughout the mastering process, and have it played back at 24p. Considering most displays are 24p capable these days (I think), it doesn’t seem an unreasonable request, eh?
Anyway, I just wanted to make sure I was understanding your’s and Bill’s final conclusion. Am I right in understanding that I can simply go ahead an encode an elementary stream (.m2v / ac3) to a 720×480 24P format? I can than author the DVD with this format and the DVD players (or most of them) will play back with the 24p by decoding it correctly themselves? Is this accurate? Or do I still need something that inserts the proper flags?
Thanks,
Tim -
Eureka!! And thank you, Todd! The problem was interlaced-related, but not in the way you think … exactly. What happened is, when I tried the time-remapping method (which is much more elegant/straight-forward, so thank you Dave!) it was bouncing not just at the reverse, but the entire playback.
Sooo, besides “what in the world”, I started thinking this has to be an interlacing issue of some sort, as Todd said. Sure enough, the footage was being interpreted as INTERLACED, when in actuality it is just recorded in an interlaced stream, but is actually progressive. Shot with an XA10, Canon calls it (as do others I think) PF30.
I have run into this before and could have sworn I fixed AE’s interpretation, so I don’t know if I forgot, or did it and hit cancel or what, but that is definitely the issue. I never understood why they had to record (and still do with the XA20/25 in AVCHD mode anyway) to an interlaced stream.
Anyway, thanks to both of you once again!
-
Thanks for the responses, guys. Todd, no this is 1080p footage … good thinking though. Dave, true … haven’t done that before (time-reverse has always worked), but I’ll give it a shot.
Maybe it is just an optical illusion (it does deal with an item rotating), but I kind of doubt it. Maybe I’ll try it with some other unrelated footage and see what happens.
-Tim
-
Anyone??
There is an option (“Include Source XMP data”) in the output module main screen, but I DO have that UNchecked, yet it still writes the XMP file(s). There is no option within the MPEG2 settings itself (i.e. Format Options).
-
Thanks, Paul. Didn’t see your message until after I posted my solution. Thanks for trying to help out!
-
Nevermind, figured it out … The 3D app does not export alpha information for those frames where NO background is showing. (i.e. an object(s) fill the frame. In this case, it was the first 60 frames or so of the animation. Thus AE saw it as having no alpha/transparency.
Dumb on the 3D app’s part. Will test this with another 3D app to see if that is common or not.
-
Hi Peter, and thanks. Yes, I talked to someone in tech support right before the weekend, and can confirm this is indeed what is happening.
Can I suggest that a future release addresses this issue, and make it user selectable whether the GPU or CPU is utilized for a plug-in. I am using a CUDA-capable graphics card — and I don’t believe your plugs are even utilizing CUDA — but my CPU power far outclasses any GPU acceleration available. GPU acceleration should be relegated to editing only IMHO.
Thanks again,
Tim -
Did you ever find out if it is possible. I’m thinking it isn’t, but AE is ALWAYS surprising me. Usually with functionality-type things, but little unknowns like this at times too.
-
Just to be clear, you’re saying it’s a known bug that cropped up since CS4? (or at least know to you.)
Unfortunately this is happening to me more than a few times. It’s not quite all the time, but often enough that I kind “internally cringe” whenever I reach for the Numpad-0 Key. (Well, in my case it’s usually the SHIFT-0 as I have my ALT RAM preview setup to preview between the working area, which is what I normally do … probably should change that to plain old “0” since I do it most often, eh?)
I should add that sometimes it only gets a second, or maybe a half-second in, before it stops and begins repeating that little blip it’s rendered. Really weird as FREE RAM is at like 12 GIGs at the time and things are rendered (green) just beyond the little space in the timeline display. It’s like it chokes on a small point and just gives up. But there is nothing “special” in those frames.
Guess it COULD be a physical issue with my keyboard. I’ll test that theory out with notepad or something. Thanks for the input.
-Tim