[John Riker]

OK think I may have figured it out and caused another question. The key to me if right is the display format. Since premiere can not for whatever reason display it in 23.976fps I went into Subtitle Edit and had it Synchronize the frame rate of the subtitles from 23.976 to 24. Seems pretty much accurate now. New questions if that makes sense and I’m right in what I’m doing:

Subtitle Edit lists a starting segment for a subtitle as: 01:53:30.078

How do I deal with this in Premiere to be fairly exact when premiere has a two digit millisecond?

With the length of a subtitle, I do CTRL-R in Windows to pull up the duration. If the duration is 2.333 how do I put in for Duration (##:##:##:##)

Are there formulates to translate these? Or ways to have premiere show three digit milliseconds?

Thanks.

JR

[John Riker]

Thanks for the reply. Here’s the final results. Since I’ve opted to manually enter my subtitles guess I could adjust each one I do however let me know your thoughts:

Location of First and last subtitle in the SUB file:

Start Time: 00:20:52,669
End Time: 00:20:54,212
Duration: 1,543

Start Time: 01:53:36,895
End Time: 01:53:39,230
Duration: 2,335

Playing the resulting video testing from Handbrake the subtitles are right on with the people talking and the time they are supposed to start (looking at start and end time in WMP and VLC) is exactly the same as what’s listed above.

If I open the Handbrake version of the file in Premiere with the subs burned in the above subtitles show up for the first one, about a second off and in the final one six seconds off. Below settings are showing where the Handbrake burned subtitles show in Premiere:

Start Time: 00:20:51:12
End Time: 00:20:53:00

Start Time: 01:53:30:04
End Time: 01:53:32:11

Considering the video and SUB are original would not think there needs to be any adjustments made in theory. The fact that Handbrake has the ability to burn in the included sub file right on target makes me question why things are a bit off in Premiere.

For reference my sequence settings are 23.976 (what the footage is) Timebase and Display Format 24fps Timecode (can’t set to 23.976).

As mentioned I’m going to assume premiere should be superior to Handbrake and that premieres timecodes are not off or something is not right.

So I guess to summarize what I’m saying, what shows at 00:20:52:00 on the screen matches what Handbrake sees at that exact moment, but in Premiere it’s in a slightly different place visually on the video footage at 00:20:52:00.

Thoughts?

Thanks.

JR

[John Riker]

Thanks for the link and extra info. Good info that lead to other info. I read somewhere that for like after effect or something you can change the app so it works the “old” way instead of 1050 by default. Interesting enough in Premiere when I pick 1024 on output I get black bars on all sides. Then trim them off after so footage ends up around 1000 by something. When I select a width of 1050 on export shows no bars in preview but end up with 12 pixel on the right and left side but top is fine. Not sure if there is something in premiere to tell it in this case to use 1024 instead of 1050 by default so it doesn’t stick in the black bars when converting. Assuming getting premier back to the cs3 way it used to work would change anything.

Thanks.

JR

[John Riker]

I couldn’t open a MPEG 2 file on the PC until I got main concept totalcode. Mpeg2 is not supported on my version which is pro 7.2.1 for windows.

JR

[John Riker]

Thanks for the detailed information. I think one more question. In my case, should the size be 1024×576 or 1050×576? From reading there is an 720×576 anamorphic ITU which seems to be linked to my pixel aspect ratio of 1.458 (article says 1050×576 is the right size), and a 720×576 anamorphic ‘NLE’ which seems to relate to a pixel aspect ratio of 1.42 (article says 1024×576 is the right size).

Here is where I’m reading. Hopefully not bad to post links:

https://www.sciencemedianetwork.org/wiki/Tutorials/Video/Pixel_Aspect_Ratio

Thoughts?

Steve

[John Riker]

Genius. Thanks Jeff.

I left the source materials and sequence as they are (1.4587 pixel aspect ratio) and on export set to 1.0 and width to 1024. Output is then as expected.

Two other questions.

1. Should I be doing anything additional with NeatVideo? When I add that plugin and click on it to manage any noise, it shows in the scrunched view that I was dealing with before your response. Not sure if that’s something to be concerned with or how I’m supposed to be managing that.

2. Are there any articles that describe how to calculate things as you did or tutorials to understand when/why you set things certain ways. Find I don’t retain things unless I fully understand the why’s.

Thanks.

JR

[John Riker]

Premiere Pro CC so specifically 7.2.1 and Mainconcept because it can’t handle MPEG2 content. Note even when I convert this content to MP4 with Handbrake still an issue in Premiere but either way TotalCode codec lets me work without converting multiple times.

Thanks.

JR

[John Riker]

Thanks for the reply. Interpret Footage, if that’s what you were referring to, shows D1/DV PAL Widescreen 16:9 (1.4587) for the Pixel Aspect Ratio. Final output is square and visually stretched vertically. This happens with our without NeatVideo. Tried several other “Interpret” settings but all seem the same. Maddening.

One other item to note you mentioned Sequence. I checked that and it has Pixel Aspect Ratio the same as about with Widescreen 16:9 but the Editing Mode, which I’ve never messed with before, says “Rovi TotalCode DVCPRO SD”. Also preview file format says “DVCPRO 25 24p Wide”.

JR

[John Riker]

Thanks for the reply. Microsoft Expressions encoder says “Cannot find video codec Uyvy”. Is there a particular DLL or something that contains the codec for Sony YUV codec?

One item to note since Vegas 12 is 64-bit, Expression Encoder is 32-bit. I have 32-bit versions of prior versions of Vegas, but not sure if there is something I can do in order to get support for this.

As a side note, is there any reason to use Sony YUV as an intermediate codec over just doing an uncompressed AVI? I know Expression can open the uncompressed AVI file, just not sure if I run into any colorspace issues with uncompressed files as opposed to one labeled as YUV.

I have read in some of the posts here the sony yuv codec is self contained to the app so not positive if having Vegas installed is enough.

Thanks.

JR

[John Riker]

Highly possible. Came from a creative firm that had the original video, the DTS track, a stereo track with the president speaking, and a bunch of ASS translation overlay files in the MKV. Unfortunately the vendor is now not our friends so to speak as our marketing group tends to have a fallout with every darn vendor they work with so can’t comfortably go back to them for help.

Funny thing if I convert the video in Handbrake it still can’t open in Vegas. However, if I run the video thru eac3to with the -slowdown I think it was command, it complains about the video but when I take the resulting MKV and the extracted DTS track and multiplex those back together, then have handbrake convert it, Vegas can open it. Problem to date is though I’m loosing audio sync in the final result so hoping for some advice on how best to deal with this situation.

Thanks.

JR