-
media markers in trimmer Vegas Pro 22
Vegas Pro 22 will not save my trimmer markers, and will not read existing ones.
This is in Windows 11. I think it works in Windows 10. I have tried on 3 computers in Windows 11. The Save trimmer markers is greyed out. Auto save markers is checked in preferences, and under View/Event Media Markers – both have check marks.
-
11 Replies
-
Hello!
This seems to be a compatibility issue if it works on windows 10. Did it ever work on windows 11?
-
Not that I’m aware of.
-
I still have one computer on Windows 10 and can confirm that Vegas Pro 22 trimmer markers are saved and read. In Windows 11, under the trimmer window, the Save Trimmer Markers is greyed out. This is true on 4 work stations.
-
First I would switch compatibility issues.
Right click on the vegas shortcut. Go to properties then compatibility.
Make sure to change that to Windows 10.
If that doesn’t work, you could try resetting the settings on Vegas. You will lose all other settings if hou do so.
To do that, hold Ctrl+Shift and double click the vegas shortcut.
You need to “delete all cached app data”.
After you launch vegas, you need to set your preferences again, and make sure marker autosave is on.
-
Hi Blaine
I just spent a 2 hours investigating your problem and can confirm you have definitely found a bug in VEGAS Pro 22. I own every version of VEGAS Pro, going back to version 9 and have been testing VP 17, 18, 19, 20, 21 & 22. It appears the bug started to creep into the program when VP20 was released.
On my analysis, I don’t think it has anything to do with Windows 10 vs Windows 11.
My guess is the problem has something to do with the VEGAS decoder/encoder engine, in regards to file types, BUT it also has a secondary bug related to the backup service for saving Markers and Regions created in the Trimmer Window.
When you add Markers/Regions in older versions of VP, it’s secondary action is to create a new .sfl file which is saved in the same location your video files is located. I believe (guessing) that a tiny range of older professional video types can actually save Markers & Regions inside the actual video file, like XDCAM. Most people are not using these older formats, so VEGAS Pro should be at least creating a .sfl file, which simply saves marker/region data.
If you own an older version of VP, you could create Markers with that, which will save an .sfl file. When you open the same videos with VP22, it should be able to read the .sfl file and show Markers.I am a member of the Beta testing team, so I will report this bug and see what they say. When I get some good information, I will report back here for you.
Regards, Derek -
In Vegas Pro 22, “Cannot save markers and regions. Either media is read-only, markers are not supported, or media is offline.” None of these are the case. I’m still using Vegas Pro 19 because of this problem (which works fine). I tried resetting/clearing all preferences and cache and it did not help. Just did another update too (Deep Learning), but no change. Compatibility mode did not help either. It does not read Markers that exist, made by Vegas 19.
Processor Intel(R) Core(TM) i9-14900K 3.20 GHz
Installed RAM 64.0 GB (63.8 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro
Version 23H2
Installed on 11/1/2024
OS build 22631.5189
Experience Windows Feature Experience Pack 1000.22700.1077.0
NVIDIA RTX A5000
-
Our primary format is MXF for broadcast. 1080 60i 50Mbps.
-
Build 250 and still not fixed. It will save trimmer markers with MOV files, but not MP4 or MXF. It will also not read or recognize markers saved with the media by previous versions of Vegas.
As I recall, it worked in Windows 10, but we now have new computers which are all Windows 11. I could be wrong about that but it would be difficult for me to determine that now.
-
I see I had proved it worked in Windows 10 before. Something is different about Windows 11.
-
Hi Blaine
This is a follow up message for you.
I can confirm from my own extensive testing and checking with other long time VEGAS Pro users, that the bug you are experiencing is being experienced by all VEGAS Pro 22 users, with the formats you have mentioned.
.mts and .m2ts formats are also affected.
The first appearance of the bug began in VEGAS Pro 21 and then became worse in VEGAS Pro 22. In VP21 it was only affecting .mp4 videos (as far as I know), but now more extensions are also affected. However, things like .mov ProRes are still working OK though.
I wish I had known about this a long time ago, because I might have been able to apply some extra pressure to get it fixed, way back last year when VP22 was first released, but I was in and and out of hospital and out of the loop for the last 9 months.I have reported this bug to the developers of VEGAS Pro for you. At this stage I don’t know when it will be fixed. VP22 – Build #250 which was the last update to be released so far, was only released recently. So I don’t expect anything to happen quickly, at the moment.
I’m really not sure if Windows 11 is the actual cause ?
I am guessing it has something to do with the decoder engine.
One example of something that did screw up VEGAS Pro after a Windows 11 update, was the removal of AC-3 decoding/encoding. Any videos that contain AC-3 audio streams won’t work now, unless you reinstall the AC-3 decoder/encoder manually into Windows 11.
I suspect a major re-write of some important section of the program, has caused this bug to appear with .sfl Markers not saving/reading. What I do know, is that the VEGAS Pro code base is being extensively updated, rewritten and modernized one section at a time. This task can’t be done quickly, so it’s a gradual process and small things do get missed, until users like yourself discover problems.I will be sure to report back here, if and when I receive any news about a fix. It will be fixed and has to be fixed !!
Derek
Reply to this Discussion! Login or Sign Up