Comments

vkmast wrote on 2/22/2022, 2:17 AM

I find vegas190.chm here C:\Program Files (x86)\Sony\Shared Plug-Ins\Help Files (or C:\Program Files (x86)\Vegas\Shared Plug-Ins\Help Files). For some it may be in C:\Program Files (x86)\Vegas\Shared Plug-Ins\Help Files

@Grazie

Grazie wrote on 2/22/2022, 3:38 AM

@vkmast - Thanks for that.

EricLNZ wrote on 2/22/2022, 4:29 AM

Interesting - Vegas 19 and it's still using a "Sony" folder.

Grazie wrote on 2/22/2022, 4:40 AM

Area 51 👽

Dexcon wrote on 2/22/2022, 4:42 AM

Interesting - Vegas 19 and it's still using a "Sony" folder

Yes, very much so. But the clean uninstall process for fully uninstalling Vegas Pro 14-19 and therefore presumably Vegas Movie Studio - https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-do-a-clean-uninstall-of-vegas-pro--111205/ - includes the following which has a number of Sony entries in the registry:

5. In the Windows registry, using Regedit, manually delete these folders:

  • HKEY_CURRENT_USER\SOFTWARE\Sony Creative Software\VEGAS Pro\1X.0
  • HKEY_LOCAL_MACHINE\SOFTWARE\Sony Creative Software\Vegas Pro\1X.0
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sony Creative Software\VEGAS Pro - MAGIX (This may only exist for version VP14)

6. You could also consider deleting some of the other folders in the following locations, but only if you are 100% sure they are only related to VEGAS Pro and not other VEGAS or Sony Creative software:

  • KEY_CURRENT_USER\SOFTWARE\Sony Creative Software\
  • HKEY_LOCAL_MACHINE\SOFTWARE\Sony Creative Software\
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sony Creative Software\

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

vkmast wrote on 2/22/2022, 4:45 AM

@EricLNZ as you know the Sony vs. Vegas folder case was discussed earlier here. Maybe this is still the reason. Has not been an issue for me, personally.

EricLNZ wrote on 2/22/2022, 5:39 AM

I only commented as we jump on users who through habit still think their software is Sony Vegas...

vkmast wrote on 2/22/2022, 6:01 AM

And not only "through habit" it seems.

Dexcon wrote on 2/22/2022, 6:02 AM

I only commented as we jump on users who through habit still think their software is Sony Vegas...

@EricLNZ ... IMO, your comment was a valid comment. Years ago when I first read the clean uninstall procedure, I thought that this can't be right - surely Sony registry entries refers back to pre-MAGIX days. But on checking the registry, it was true for VP in MAGIX days.

I think that the difference is that VP users - particularly new VP users on the forum - referring to Sony Vegas Pro some 8 years after Sony's last version release - 13 - is often a cause for concern. I'm not sure that a VP "pirate" is basing their naming convention of Sony Vegas Pro on file names deep in the bowels of Windows Program Files or the registry.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

EricLNZ wrote on 2/22/2022, 4:33 PM

I just thought it quite hilarious that deep inside VP it was still using "Sony". Apart from "through habit" users and pirates isn't there a legal issue here with the continuing use of "Sony"?

Maybe it's been overlooked.

Former user wrote on 2/22/2022, 5:07 PM

@EricLNZ Maybe it's some kind of ghost or left over because mine's C:\Program Files (x86)\VEGAS\Shared Plug-Ins\Help Files, I've never had a Sony version on this pc,

Just did a search on my pc & 45 items are related to Sony & Vegas, so4compound, upscale, ,, there's a few like that that still have Sony in the details,

walter-i. wrote on 2/23/2022, 2:30 AM

Maybe it's some kind of ghost or left over .......

This "some kinde of ghost" will not disappear until all the code is rewritten.

We users already had to do our homework by adjusting our scripts according to the following instruction:
The scripting namespace for VEGAS Pro 14 changes from “Sony” to “ScriptPortal”. In your scripts, any occurrence of items like “Sony.Vegas” or “Sony.MediaSoftware” must be changed to “ScriptPortal.Vegas” and “ScriptPortal.MediaSoftware”. We chose this namespace (“ScriptPortal”) in order to remove any company branding and thus avoid this problem in the future.

With all the Vegas Pro code, it certainly won't be that easy - but at some point, this work has to happen too.

Maybe this thread is a good impetus to put more energy into it again👍

Howard-Vigorita wrote on 2/23/2022, 11:37 AM

@Grazie @vkmast On my machines implemented since Vegas16 was current, I have help files in 2 places:

C:\Program Files (x86)\VEGAS\Shared Plug-Ins\Help Files

C:\Program Files (x86)\Sony\Shared Plug-Ins\Help Files

All my Vegas160.chm through Vegas190.chm files are in the VEGAS folder. All of the other help files in that folder are for newer fx and also have chm file types. My Sony folder has help files for older fx and most of them are in the much older hlp format.

Btw, the older hlp format is no longer supported by Win10 unless you get the the old winhlp32.exe from win7 or win8 and install it correctly. This link outlines how to get it from Microsoft and do it. This github link already has the pieces extracted and includes the script I use. The process works for both Win10 and Win11. Keep in mind its not needed for recent Vegas chm help but if you use older versions of Vegas, fx, or maybe Sound Forge 7 and/or its vintage noise reduction and restoration pack, you'll definitely want it.