Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Timeline weirdness:Showing long time

  • Timeline weirdness:Showing long time

    Posted by Nick White on December 29, 2012 at 10:18 pm

    I have converted a series of .vob files to mp4 using Handbrake. Mediainfo shows that they have the expected lengths in time. They are for the movie Gran Torino, which is about 2 hours or a bit less. I wanted to join the mp4 files for playing.

    However when I placed them on the timeline in Vegas, they showed as being just in excess of 7 hours. So I discarded the project and tried again. This time they show as being in excess of 9 hours. 09:42:28:20 in fact.

    This is not because I have placed them too far along the timeline.They start at 0:00:00:00 and the entire timeline shows a proportionate incorrect time reading.So it’s not just of the clips, AFAICS.

    Going to frames and seconds gives the same way out readings: 1,750,000 frames, for instance. Interestingly that no of frames says to me that the film is over _19_ hours long at 25fps: in fact twice the length the timeline shows in hours minutes seconds.

    I tried with another clip and it was OK. So I tried again with the offending group and it looks OK! The only difference I saw was that as I dropped the clips onto the timeline in the first two sessions, which showed incorrect times, I could zoom the TL out more than a tiny bit past the end of the last clip, but Vegas was automatically zooming it out to just that place, so I could drop the next clip. In the _last_ session, where time is correct, I could zoom out at will, but I had to do the zooming to let me drop the next clip.

    I would appreciate any input on this.

    EDIT: Interestingly Vegas was also saying that the render was going to take forever as well. On the last try the render time is showing as much shorter

    Nick

    Nick White replied 13 years, 4 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy