-
Audioon 4/6/2023
Very strange audio problem!
Further to @john_dennis superb analysis over the years, I can confirm this was introduced with Vegas 19 build 636 and above. Vegas 19 build 550 is not affected. All versions of Vegas 20 are broken.
-
Videoon 1/8/2022
Installation of Vegas 19 fails on Windows 11
Bitdefender Total Security was the culprit in this saga. I'm not sure if it was the anti-virus or the firewall as I disabled both but the installation proceeded at ten times the speed and didn't miss a beat.
-
Scriptingon 6/28/2021
Bug report - ReplaceWith file lock - Vegas 18 (Build 527)
myVegas.UnloadScriptDomainOnScriptExit = true; Thanks for the suggestion but it didn't resolve the issue.
-
Scriptingon 6/23/2021
Bug report - ReplaceWith file lock - Vegas 18 (Build 527)
It’s similar to the one I linked but not the same. The difference is important to clarify because they have been working on it.
-
Scriptingon 6/23/2021
Bug report - ReplaceWith file lock - Vegas 18 (Build 527)
Workaround: Copy the "compoundplug" folder from "C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\". Edit: This may result in Vegas 18 crashing and is not a suitable workaround.
-
Scriptingon 5/23/2021
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
Still broken in Vegas 18 Update 5 (build 527)
-
Scriptingon 3/24/2021
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
Still broken in Vegas 18 Update 4 (build 482)
-
Scriptingon 2/3/2021
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
Still broken in Vegas 18 Update 3 (build 434)
-
Scriptingon 11/6/2020
Bug report - RenderFinished event Vegas 18 (builds 284 and 334)
Fixed in Vegas 18 Update 2 (Build 373). Thank you.
-
Scriptingon 11/6/2020
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
Still broken in Vegas 18 Update 2 (build 373)
-
Scriptingon 10/10/2020
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
The problem arises when the decoder uses "compoundplug.dll" instead of "so4compoundplug.dll". On the virtual machine, the "compoundplug.dll" decoder is always used. I'm not sure why. On my main computer this was caused by enabling legacy AVC decoding on the File I/O tab. This option was on due to past issues with the so4 decoder and because the first time this locking issue arose, there were m2ts files involved, which always appear to use the "compoundplug.dll" decoder.
-
Scriptingon 10/10/2020
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
I can't reproduce the issue on my notebook. I wonder what the difference is. I tried a heap of different mp4 files, including one rendered by Vegas and it always locks, every single time on my main computer, and on a clean virtual machine with default settings. My main computer is stuck at Win 10 1909 due to a driver issue but my notebook and the virtual machine are both 2004. Vegas 9 through 17 don't have the issue on the same computer. It locks using avi, and mp4. It doesn't lock using wmv files. It doesn't lock using audio only files mp3, and flac after switching video to audio in the script. I also tried inserting both video and audio streams from the mp4 files but they still lock every single time.
-
Scriptingon 10/9/2020
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
@VEGASPascal, thanks so much for looking into this. It took me a while to work out what the difference was for you. When I followed your video, it worked fine. The difference is renaming the file while the project is still open. This clears the lock. I thought it was playing and stopping the media but this isn't enough to clear the lock. It's the actual step of renaming the file before closing the project.
-
Scriptingon 10/8/2020
Bug report - File locking Vegas 18 (Builds 284,334,373,434,482,527)
@VEGASPascal, I tested on a vanilla Windows 10 virtual machine with only Vegas 18 before posting. Are you closing just the project? Shutting Vegas down releases the lock. Are you on Windows 10 with all updates?
-
Scriptingon 10/7/2020
Bug report - RenderFinished event Vegas 18 (builds 284 and 334)
The workaround is to unhook the event from within the handler. I've simplified the steps to reproduce it. It also occurs using the asynchronous BeginRender method. Save the included script as "C:\Program Files\VEGAS\VEGAS Pro 18.0\Script Menu\RenderFinishedIssue.cs" Copy an mp4 file to "C:\Test\Test.mp4" Open Vegas 18 Run the script | Tools | Scripting | RenderFinishedIssue In Vegas 18, two messages are displayed, "completed" and then "rendering" In Vegas 9 through 17, only the first message, "completed" is shown. using ScriptPortal.Vegas; using System.Windows.Forms; public class EntryPoint { public void FromVegas(Vegas vegas) { const string testMedia = @"C:\Test\Test.mp4"; const string testRender = @"C:\Test\Rendered.mp4"; const string testRenderer = "MAGIX AVC/AAC MP4"; const string testTemplate = "Internet HD 1080p 25 fps"; var videoTrack = new VideoTrack(); vegas.Project.Tracks.Add(videoTrack); videoTrack.AddVideoEvent().AddTake(new Media(testMedia).GetVideoStreamByIndex(0)); var template = vegas.Renderers.FindByName(testRenderer).Templates.FindByName(testTemplate); var renderArgs = new RenderArgs(vegas.Project) {RenderTemplate = template, OutputFile = testRender}; vegas.RenderFinished += RenderFinishedHandler; vegas.Render(renderArgs); vegas.RenderFinished -= RenderFinishedHandler; } private void RenderFinishedHandler(object sender, RenderStatusEventArgs args) { MessageBox.Show(args.Status.ToString()); } }
-
Scriptingon 7/18/2019
Media length incorrect using So4 Compound Reader
After investigating this issue for several days, I can't find a workaround. Once the decoder is confused, it always returns the old file details. Even if the file is deleted or renamed, new Media(fileName) will incorrectly load the non existent file from it's cache and give the incorrect length. Closing the current project and starting a new one, which usually clears the media pool doesn't help. The media pool is empty but the decoder still loads the old file from somewhere. Disabling the So4 Compound Reader rectifies the issue. I'm going to have to rebuild a significant section of my plugin to ensure unique file names between videos to workaround this bug. I appreciate your time @j-v but we're not on the same page. This is a scripting issue. This may still be a GoPro 7 issue as the cached file I've been using to reproduce the issue is a GoPro 7 file.
-
Scriptingon 7/16/2019
Media length incorrect using So4 Compound Reader
I'm pretty sure some kind of caching is going on. The files are different but the file names are the same. When the incorrect length is reported, it's the length of the file that was previously in that location.
-
Scriptingon 7/16/2019
Media length incorrect using So4 Compound Reader
I've reproduced the error with a GoPro 3 file so I've edited the post to remove the GoPro 7 references. This is all the same file. Before inserting it, the length is 17 seconds but after inserting it, the length is 14 seconds. It should be 14 seconds as Media Info reports it to be. It's the initial length from the Vegas Media object in code that's causing me grief. As stated in the initial post, disabling the So4 Compound Reader completely fixes this.
-
Scriptingon 7/16/2019
Media length incorrect using So4 Compound Reader
The media loads fine.
-
Scriptingon 7/16/2019
Media length incorrect using So4 Compound Reader
This is in scripting. The media loads fine but "new Media(fullName).Length" is incorrect. I wrote the plugin.
-
Videoon 8/27/2018
Vegas Pro Edit 16 won't Open
After the Vegas installation, I installed each plugin individually and fired up Vegas between each installation. Everything is still working with all the plugins from the suite installed and activated. I'm guessing Joelson-Forte's solution also works. The plugins are downloaded to "D:\My Documents\MAGIX Downloads\Installationsmanager" during the suite installation. I didn't install "MAGIX Connect" or "Music Maker" during the initial suite installation nor during the re-installation. Crazy workaround for a suite of plugins but it's all good now.
-
Videoon 8/27/2018
Vegas Pro Edit 16 won't Open
I uninstalled Vegas 16, all the plugins that came with the suite and Microsoft C++ 2013. This was everything that was installed today. I rebooted for good measure. I reinstalled Vegas 16 on it's own and it's starting fine now.
-
Videoon 8/27/2018
Vegas Pro Edit 16 won't Open
I have the same issue. The problem details highlight the ignitecore bundle from the Vegas 16 Suite. C:\Program Files\Common Files\OFX\Plugins\IgniteCore.ofx.bundle I removed HitFilm Ignite Pro and it now finishes loading the plugins but still crashes before starting at "Initialising DotNet framework...". Problem Description Application Name: VEGAS Pro Application Version: Version 16.0 (Build 248) Problem: Unmanaged Exception (0xc0000005) Fault Module: C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll Fault Address: 0x00007FF98EC43D4C Fault Offset: 0x0000000000073D4C
-
Videoon 12/1/2017
AVC/XAVC-S issues in VP15/16? Try disabling so4compoundplug.dll!
Thanks Nick. I can confirm this release appears to have fixed all my issues, which were far wider reaching than the simple version I presented here. Cheers to the developers. I can finally release my application.
mickhardy
Offline, Last login 5/10/2023, Member since 9/30/2016