Subtitles only importing correctly at pal framerate (25)

AngryTurkeyStudios wrote on 9/18/2016, 2:51 PM

I'm having a very odd issue with DVD architect. Every time I try to import a subtitle file, it imports at the wrong timecode, unless I've set the disk to be a PAL disk. I've reinstalled DVD arcitect, and just done everything I could imagine to fix the issue. I am wondering if anyone knows how to solve this issue.

The subtitles show up here on the timeline, 01:17:56:09, with the settings shown in the second image

 

The file in question is here https://www.dropbox.com/s/el74imyv693kjut/test4.sub?dl=0

I have subtitles I need to convert from SRT. I have been able to do so, but they refuse to import correctly, and I cannot understand why.

This is the refernce to the manual

http://dspcdn.sonycreativesoftware.com/manuals/dvdarchitectpro6.0_manual_enu.pdf#page=98

Comments

Former user wrote on 9/18/2016, 5:42 PM

This is a drop-frame vs non-drop issue probably. You need to make the timeline that the subtitles are created in a drop-frame Timecode mode. That should fix it.

 

 

AngryTurkeyStudios wrote on 9/18/2016, 11:55 PM

I seemed to be able to fix it by using this program https://sourceforge.net/projects/subadjuster/

I calculated that every second of video was off by .03 frames. (makes sense with 29.97) From there I was able to move the first and last timecode by .03 * # of sec in timecode, forcing the subtitles to sync with the video when imported through DVD arcitect.

However, this is not a real solution to the problem. I don't understand why DVD arcitect will not import the files properly.

Former user wrote on 9/19/2016, 9:06 AM

I had never imported an SRT for anything over 10 or 15 minutes so I tested a 2 hour TV capture. I get the same error I believe you are getting. The timeline I have set for non-drop but Vegas treats the SRT file as if it is drop frame and aligns incorrectly. It becomes very evident around the hour mark that this is what is happening. In both vegas and DVDA. Not sure why this is happening but it should be written up as a bug.