"Some problem with cursor & clips out of split position" - SOLVED

Ardante wrote on 7/4/2018, 3:21 PM

Few days ago I posted this problem https://www.vegascreativesoftware.info/us/forum/some-problem-with-cursor-clips-out-of-split-position-screenshot--111970/ on this forum. As title says, it has something to do with cursor & clips out of split position (link to screenshot - https://plus.google.com/u/0/photos/photo/115185730676100091884/6573931537499803906). Unfortunately, none of the given answers on that topic were right about the solution, still, thank you all who tried to help me (maybe it was my fail to explain well the situation, but at the moment, I just said what I thought it was necessary & has to do with the problem).

 

PROBLEM

So, as you can see through screenshot, I couldn't manage to put my cursor at split zone for some reason, even though I was able to do so when I split clips the first time, with NEVER TURNING OFF "Quantize to Frames". After creating new SV file, I pasted clips there from an old SV save file (old file that had no problems with that zone split cursor) & what I got ? The same problem with cursor out of split position. This gave me some clues to possible sources of this issue, as the old SV file had no problems with it, while new SV file had it. After a wasted hour of tries & searches in Sony Vegas Pro 13...

SOLUTION

This all problem with "cursor & clips out of split position" has all to do with PROJECT PROPRIETIES, namely, with FRAME RATE ! If you copy clips from one project (SV file), which is at "59,940 (Double NTSC)" Frame rate, & paste them to a new project but with a different frame rate, for example, "29,970 (NTSC)", you will get that problem with CURSOR PROBLEM (which is in that screenshot) !!! The only solution to it is to make both project files at the same frame rate !!!! In this case, it doesn't matter the resolution of projects, only the same frame rate. Take in notice that this ONLY MAY WORK if you first change frame rate at Project Proprieties & then paste clips - if you do the opposite (first pasted clips, then changed frame rate), it may not work.

 

I understand now that this might be a noobs issue & that all professionals knew this all the time, but I decided to post it since 1st- I couldn't find this solution on google, 2nd- I had no idea what key-words should I write in searches to find answers (wasted 30 minutes, with no results needed), 3rd- no right answer were given in my another post related to this issue (I assume it might me my fault of not giving more details - I just didn't know what was important to identify in that case).

Comments

Former user wrote on 7/4/2018, 3:27 PM

In the other post you never mentioned copying and pating. That is crucial information.

Ardante wrote on 7/4/2018, 3:32 PM

In the other post you never mentioned copying and pating. That is crucial information.

Yes, as I said here, I just didn't know what was important to say, beyond the consequences of the problem 😭

Kinvermark wrote on 7/4/2018, 6:40 PM

Main thing is that you posted about this esoteric problem & solution. Thanks!

I think this one could easily trip up both pros and "noobs", although experienced users would perhaps be more likely catch-on when the issue arises.

Musicvid wrote on 7/5/2018, 5:02 PM

A specific procedure, with it's own Project icon, is aptly named "Match Media Settings." Since this state is not only preferred but expected, it is easy to understand why it seemed to get passed over by our experienced contributers.

A screenshot of your project properties, as in Section C-3 of this thread, will help us in the future, especially if you are moving assets around between projects. To take Kinvermark's lead, thanks for following up on the issue.

Tim L wrote on 7/5/2018, 5:33 PM

@Ardante -- Thanks for the follow-up.  It may help others.

I will point out a related trap that I fell into last night.  I had a new project, which defaulted to 1920x1080?  Anyway, when I dragged my first video clip to the timeline, it asked me "Do you want to set the project properties to match this media?" (or something like that).  I thought it unusual to ask (since it was already 1920x1080), but said "yes".

After dragging a few more clips to the timeline, and noticing somewhat jittery playback behavior, I checked project properties and saw it was set to something crazy, like "30.187 fps".  The clip I started with was a cellphone video, and they tend to have somewhat irregular pacing of the frames.

So... In spite of the nice feature to help users set the project properties at the start of a project (and I'm not being sarcastic, that generally is a helpful feature) -- you should always be suspicious about that if your first clip is cellphone media, and instead decline the offer and set the project properties manually.

Oh, and how it relates to this specific thread: after manually setting project fps back to 29.97, I was immediately concerned about the events on my timeline not being properly frame aligned.  Since I only had 4 or 5 events at that point, I just manually dragged each event left and right a bit to requantize the start frame, then dragged the ends left and right a bit to do the same with the last frame.  I expect there is a script to do this (quantize frames), but this was easy enough with just a few events.