Forum Replies Created

Page 4 of 4
  • Jurgen Murataj

    January 27, 2025 at 5:35 pm in reply to: Vegas2handbrake issues with windows 11?

    I agree with what Baskeh said. Windows 11 has stricter rules when it comes to premissions. Running as admin should overwrite that.

    Additionally, if that suggestion is not enough to solve your problem you could try reinstalling Avisynth and Frameserver and then configure Vegas2Handbrake again. That ensures that you’re using the latest version which is compatible with Windows 11.

    If this still doesn’t work, you could try and find log files so you can see exactly where the problem is occurring. That could give you a clear idea of what to work with.

    Good luck!

  • Jurgen Murataj

    January 25, 2025 at 11:43 pm in reply to: Optimizing Settings for Best Performance (?)

    Hello, Kelly!

    Based on what I see, it seems like the main issue here might be the RAM usage.

    Windows 10 uses about two times more RAM than Windows 7. Considering the massive jump on your Vegas version, too, it looks like your hardware cannot keep up with the RAM usage.

    Are you able to open task manager and take a screenshot with Vegas running, so I can see the RAM usage? If this is indeed the issue, there are some settings you can adjust to improve the performance without affecting the quality as much.

  • Jurgen Murataj

    January 24, 2025 at 10:21 pm in reply to: Rendering WAV produces WDP?

    Happy to hear that!

  • Jurgen Murataj

    January 23, 2025 at 9:17 pm in reply to: Rendering WAV produces WDP?

    Hello! It seems like there is a registry issue indeed.
    This is what I recommend to return things to normal:

    – Undo DLL Registration Changes: If you manually registered certain DLL files in the registry, it’s possible that a misstep occurred during that process, causing system associations to get mixed up. You can try reversing this by unregistering those DLLs.

    Open the Command Prompt as Administrator (right-click and select Run as Administrator).

    Type the following commands to unregister the DLLs (substitute with the name of the DLL you registered): regsvr32 /u (dllname).dll

    – Re-register the Correct DLLs:
    If the “Class Not Registered” error persists even after unregistering, it may be worth trying to re-register the necessary DLLs to ensure everything is correct.
    The command you need for that is: regsvr32 (dllname).dll

    You can also try re-registering some other key Windows Media Player and audio-related DLLs:

    regsvr32 jscript.dll

    regsvr32 vbscript.dll

    regsvr32 mshtml.dll

    I hope this helps!

  • Jurgen Murataj

    January 23, 2025 at 1:27 pm in reply to: Get eGPU working with Vegas 22 pro

    Hello!
    It seems like Vegas Pro is not utilizing the GPU. There might be a few reasons for this, but here are three important things to consider.

    – First things first, make sure that your laptop is using the highest performance setting for Thunderbolt, and there are no issues with the Thunderbolt cable or port. Performance can be limited if the Thunderbolt connection is not optimal.

    – Check that hardware acceleration is working properly.

    To do that, go to Options > Preferences > Video tab.

    Under GPU acceleration, make sure you’ve selected the option that uses your 4060. If it’s set to “Auto,” select your GPU manually to ensure Vegas is utilizing it.

    – For Vegas to render the video whith hardware acceleration, you need to make sure you’re rendering using the NV encoder (NVEC) instead of Mainconcept AVC. You can change that when customizing render settings under “Encode mode”

     

Page 4 of 4

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