A scene boundary can't be placed at 00:39:59:27, so Scenarist picks the closest previous I-frame at 00:39:59:15. Thus, I frames only occur every 15 frames, on 15 frame boundaries. Most probably, the GOP structure of your MPEG-2 file is a standard 3/5 pattern of 1 I-frame, 4 P-frames, and 10 B-frames: BBIBBPBBPBBPBBP. The reason that a scene marker seems to "jump" to a different timecode is because scene/chapter markers (which by definition make a cell boundary), must occur on an MPEG-2 I-frame. You're running into two separate problems here:ġ. Checked in VobEdit that the VOB produced out of my video had the drop flag set to non-drop, but the VOBs of the DVD I ripped for testing had the drop flag enabled.Īppreciate any suggestions how to make Scenarist handle drop frame time codes correctly. However, Scenarist still behaved the same way when I added a scene. Ripped a video stream from some DVD movie to ensure that it’s not my. I couldn’t find a program to check this flag, and pulldown didn’t change anything. m2v file has internal drop type flag, which pulldown supposed to be able to set. Pulldown source.m2v target.m2v -nopulldown -drop_frame trueĪs I understand. I already tried a few things without any success: I don’t have any issues with audio either. sst script, and the closed captions stay in sync just fine. Although things work fine if I use non-drop frame format for everything, I want to get to the source of the problem, especially since it says everywhere that you should use drop frame for NTSC.ĭoes anyone have an idea, what causes this Scenarist behavior? Is it the video, Scenarist settings, or something else?īy the way, I also imported Line 21 closed captioning data with the same time codes as subtitles in the. sst script, but I see a more global issue here. Of course I could adjust the timing in the. I read a number of threads about subtitles going out of sync and how it can be fixed by setting drop type to Drop Frame however, I already import all my assets with drop frame. ![]() If a certain subtitle screen is set to appear at the scene start time in my example (00:39:59:27) according to its Start Time to Video property, it will in fact appear at the "drop frame adjusted" point (00:39:57:15). ![]() sst script or type them in manually, they go out of sync. The same remains true anywhere on the track.Īlthough I already made many DVDs with captured video in Scenarist, I just noticed this problem because I decided to add subtitles. I calculated that this difference has something to do with the drop frame setting: Scenarist takes timestamp of the scene and for some reason converts it into non-drop frame time code before moving the slider. The problem is that when I double-click on this scene, the slider jumps to a different position: 00:39:57:15 (frame 71925). m2v video stream, set Scenarist default setting to Drop Frame, imported the. Remember that no question is stupid and we work together to create a friendly community.Here’s a problem I came across a in Scenarist 2.7 when trying to author a DVD out of NTSC TV program I captured into MPEG-2 using ATI Radeon VIVO card. All things video are welcome!įeel free to post anything you like from questions to pictures. From a dad with a camcorder to a professional engineer at the superbowl, or a small meeting room operator to a widescreen specialist, projectionist, LED wall engineer or a electrical video engineer. This subreddit is open to anyone to discuss, share and show their work, as well as ask questions towards anything concerning video production. Welcome to r/videoengineering! Inspired by our brother subreddit: audioengineering
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |