View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009273ardourbugspublic2023-03-08 00:502023-12-19 19:52
ReporterMark Knecht Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
PlatformMicrosoftOSWindowsOS Version10
Product Version7.3 
Summary0009273: Ardour/Mixbus32C VST scan hangs on HALion 7, DAW Crashes - but HALion works after editing blacklist file
DescriptionI am resubmitting this report in a shortened version. I just spent 30 minutes typing in a detailed report only to have the submission fail due to some sort of time out in Mantis.

Using the 30-day Halion 7 demo the stand alone version works fine. However Ardour 7.2 from the subscription service and both Mixbus32C-7.2 and Mixbus32C-8.2 hang and crash during the plugin scan in the Plugin Manager window.

It appears that all the files necessary to use HALion 7 are created but the vst3_x64_blacklist.text file has it listed so it's not selectable as a plugin. However removing it from the blacklist file let's the DAW use it and it works fine. No crashes at all. All features work fine.
Steps To Reproduce1) Install HALion 7 demo file

2) Scan for new plugins in any of the 3 versions of the DAW listed above.
Additional InformationI will attempt to attach some files after this report is submitted.
Tagscrash, VST3

Relationships

has duplicate 0009582 new Halion Sonic scan failed 

Activities

Mark Knecht

2023-03-08 00:52

reporter   ~0027436

In all 3 DAW versions an XML file is created for HALion 7. The file is attached.
ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i (587 bytes)    
<?xml version="1.0" encoding="UTF-8"?>
<VST3Cache version="2" bundle="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3" module="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3">
  <VST3Info uid="3B63D74130B34AE397AF92A9659137D5" name="HALion 7" vendor="Steinberg Media Technologies" category="Instrument|Sampler" version="7.0.0" sdk-version="VST 3.7.5" url="http://www.steinberg.net" email="mailto:info@steinberg.de" n_inputs="0" n_outputs="70" n_aux_inputs="2" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="0"/>
</VST3Cache>
ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i (587 bytes)   

Mark Knecht

2023-03-08 00:53

reporter   ~0027437

The blacklist file that was created is attached. Removing the HALion entry allows all 3 versions of the DAW to use HALion 7
vst3_x64_blacklist.txt (93 bytes)    
C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3
vst3_x64_blacklist.txt (93 bytes)   

x42

2023-03-08 01:01

administrator   ~0027438

This is odd. Ardour launches an external tool to scan the plugin to prevent crashes. The plugin scanner may crash, but it should not be able to take the Ardour down.

Mark Knecht

2023-03-08 13:35

reporter   ~0027439

OK, so if Ardour launches the scanner and I'm watching the progress bar I see it going back and forth, it comes to a point where the progress bar just stops moving. At that point Ardour is waiting but the answer doesn't come from the scanning app. The problem is the buttons to cancel the scan don't work and everything is hung. Ardour isn't 'taken down', it's just hung waiting. I click the upper right window 'X'' to close Ardour and everything in the application goes kind of blurry white and the program stops.

Keep in mind that it appears the external tool appears to have worked because the XML file and the blacklist entry are created. It seems more like it failed at the very end of whatever process it's using to return a response to Ardour.

Is the external plugin scan tool something I can run at the command line and provide feedback?

x42

2023-03-09 00:32

administrator   ~0027440

> Is the external plugin scan tool something I can run at the command line and provide feedback?

Yes, with the official binary. on Linux
LD_LIBRARY_PATH=/opt/Ardour-7.2.0/lib/ /opt/Ardour-7.2.0/lib/ardour-vst3-scanner -vf ~/.vst3/Surge\ XT.vst3


On Windows open a cmd.exe terminal, cd C:\Program Files\Ardour7\bin\
and run ardour-vst3-scanner.exe C:\..path-to-the...\plugin.vst3

Mark Knecht

2023-03-09 03:59

reporter   ~0027441

Thanks for clear directions. The scanner returns nothing for HALion 7. It does return results for other plugins.

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Harrison\AVA\AVA-BF_64bit.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Harrison\AVA\AVA-BF_64bit.vst3
[Info]: Found Plugin: AVA Bass Flow
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\f3d9791b16e4996acc257552df742a1576913bcc.v3i

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

C:\Program Files\Ardour7\bin>


I don't know if it's valid to do this with a VST3 that's actually licensed under Windows but I copied the HALion 7.vst3 file to another directory where MiniMonsta2 exists. MiniMonsta2 works, the HALion7 copy does not work:

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Minimonsta2.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Minimonsta2.vst3
[Info]: Found Plugin: Minimonsta2
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\a0c47334ba3b8e0d9e562d42b330986dab8bebfe.v3i

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\HALion7Copy.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\HALion7Copy.vst3
Cannot load VST3 module: 'c:\Program Files\Common Files\VST3\HALion7Copy.vst3'

C:\Program Files\Ardour7\bin>

Mark Knecht

2023-03-09 04:01

reporter   ~0027442

C:\Program Files\Ardour7\bin>dir "C:\Program Files\Common Files\VST3
 Volume in drive C has no label.
 Volume Serial Number is E8DF-F3F4

 Directory of C:\Program Files\Common Files\VST3

03/08/2023 08:56 PM <DIR> .
03/08/2023 08:56 PM <DIR> ..
01/31/2023 10:12 AM 106,967,064 HALion7Copy.vst3
06/15/2022 01:08 PM <DIR> Harrison
02/21/2023 01:39 PM 11,860,480 Minimonsta2.vst3
03/06/2023 11:41 AM <DIR> Scaler2
02/26/2023 01:12 PM <DIR> sforzando
03/06/2023 01:18 PM <DIR> Steinberg
               2 File(s) 118,827,544 bytes
               6 Dir(s) 816,342,151,168 bytes free

C:\Program Files\Ardour7\bin>

Mark Knecht

2023-03-11 16:43

reporter   ~0027443

A little more info showing ardour-vst3-scanner working with Scaler2 but failing to do anything with Halion 7.

C:\Program Files\Ardour7\bin>ardour-vst3-scanner -v "c:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3
[Info]: FactoryInfo: 'Plugin Boutique' 'http://www.pluginboutique.com/' ''
[Info]: Class count: 2
[Info]: Class: 0 'Scaler 2' 'Audio Module Class'
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 1
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 1
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Found Plugin: Scaler 2
[Info]: Touch cachefile: set mtime = 1678552461 (2023-03-11 09:34:21), plugin mtime = 1675183798 (2023-01-31 09:49:58)
        <VST3Cache version="2" bundle="c:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3" module="c:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3">
          <VST3Info uid="ABCDEF019182FAEB654D616953636C32" name="Scaler 2" vendor="Plugin Boutique" category="Instrument" version="2.7.3" sdk-version="VST 3.7.2" url="http://www.pluginboutique.com/" email="" n_inputs="2" n_outputs="2" n_aux_inputs="0" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="1">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\7aecbfdc3bac602537b65d5e1b390c993ba29584.v3i

C:\Program Files\Ardour7\bin>ardour-vst3-scanner -v "c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

C:\Program Files\Ardour7\bin>

Mark Knecht

2023-03-11 16:46

reporter   ~0027444

Possibly ardour-vst3-scanner doesn't like (DOT)vst3 in the path name?

Here I show the sforzando vst3 being scanned correctly when the directory is just sforzando, but failing to do anything when the directory is renamed sforzando.vst3 like the HALion install did with its vst3


C:\Program Files\Ardour7\bin>ardour-vst3-scanner -v "c:\Program Files\Common Files\VST3\sforzando\Contents\x86_64-win\sforzando.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\sforzando\Contents\x86_64-win\sforzando.vst3
[Info]: FactoryInfo: 'Plogue Art et Technologie, Inc' 'https://www.plogue.com' 'mailto:info@plogue.com'
[Info]: Class count: 2
[Info]: Class: 0 'sforzando' 'Audio Module Class'
valid signature detected for C:\Program Files\Plogue\Aria\aria_x64.dll
Engine path:C:\Program Files\Plogue\Aria\aria_x64.dll
queried details:ARIA Engine v1.973 (Win x64)
**ARIA_ENGINE_INFO**
1973
1973
ARIA Engine v1.973 (Win x64)
productName:sforzando
vendorName :Plogue Art et Technologie, Inc
productId:1014
slots:1
supportURL:https://www.plogue.com
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 0
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 0
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 1
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Found Plugin: sforzando
[Info]: Touch cachefile: set mtime = 1678552911 (2023-03-11 09:41:51), plugin mtime = 1667581110 (2022-11-04 09:58:30)
        <VST3Cache version="2" bundle="c:\Program Files\Common Files\VST3\sforzando\Contents\x86_64-win\sforzando.vst3" module="c:\Program Files\Common Files\VST3\sforzando\Contents\x86_64-win\sforzando.vst3">
          <VST3Info uid="5C5CA79682FC437AB6539BA204BAB349" name="sforzando" vendor="Plogue Art et Technologie, Inc" category="Instrument" version="2.1.0.5" sdk-version="VST 3.7.6" url="https://www.plogue.com" email="mailto:info@plogue.com" n_inputs="0" n_outputs="2" n_aux_inputs="0" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="0">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\79d9aed65a1068beacdbfdb4b47a474ae39825ee.v3i

C:\Program Files\Ardour7\bin>ardour-vst3-scanner -v "c:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3

C:\Program Files\Ardour7\bin>

Mark Knecht

2023-03-11 16:56

reporter   ~0027445

And finally, here is the scanner working with HALion 7 when the ".vst3" is removed from the directory name:

C:\Program Files\Ardour7\bin>ardour-vst3-scanner -v "c:\Program Files\Common Files\VST3\Steinberg\HALion 7\Contents\x86_64-win\HALion 7.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Steinberg\HALion 7\Contents\x86_64-win\HALion 7.vst3
[Info]: FactoryInfo: 'Steinberg Media Technologies' 'http://www.steinberg.net' 'mailto:info@steinberg.de'
[Info]: Class count: 4
[Info]: Class: 0 'HALion 7' 'Audio Module Class'
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 1
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 33
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: - bus: 1 count: 2
[Info]: VST3: - bus: 2 count: 2
[Info]: VST3: - bus: 3 count: 2
[Info]: VST3: - bus: 4 count: 2
[Info]: VST3: - bus: 5 count: 2
[Info]: VST3: - bus: 6 count: 2
[Info]: VST3: - bus: 7 count: 2
[Info]: VST3: - bus: 8 count: 2
[Info]: VST3: - bus: 9 count: 2
[Info]: VST3: - bus: 10 count: 2
[Info]: VST3: - bus: 11 count: 2
[Info]: VST3: - bus: 12 count: 2
[Info]: VST3: - bus: 13 count: 2
[Info]: VST3: - bus: 14 count: 2
[Info]: VST3: - bus: 15 count: 2
[Info]: VST3: - bus: 16 count: 2
[Info]: VST3: - bus: 17 count: 2
[Info]: VST3: - bus: 18 count: 2
[Info]: VST3: - bus: 19 count: 2
[Info]: VST3: - bus: 20 count: 2
[Info]: VST3: - bus: 21 count: 2
[Info]: VST3: - bus: 22 count: 2
[Info]: VST3: - bus: 23 count: 2
[Info]: VST3: - bus: 24 count: 2
[Info]: VST3: - bus: 25 count: 2
[Info]: VST3: - bus: 26 count: 2
[Info]: VST3: - bus: 27 count: 2
[Info]: VST3: - bus: 28 count: 2
[Info]: VST3: - bus: 29 count: 2
[Info]: VST3: - bus: 30 count: 2
[Info]: VST3: - bus: 31 count: 2
[Info]: VST3: - bus: 32 count: 6
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 33
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 4
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Skipping non-effect class: Preset Compatibility Class
[Info]: Skipping non-effect class: Preset Version Class
[Info]: Found Plugin: HALion 7
[Info]: Touch cachefile: set mtime = 1678553721 (2023-03-11 09:55:21), plugin mtime = 1675185166 (2023-01-31 10:12:46)
        <VST3Cache version="2" bundle="c:\Program Files\Common Files\VST3\Steinberg\HALion 7\Contents\x86_64-win\HALion 7.vst3" module="c:\Program Files\Common Files\VST3\Steinberg\HALion 7\Contents\x86_64-win\HALion 7.vst3">
          <VST3Info uid="3B63D74130B34AE397AF92A9659137D5" name="HALion 7" vendor="Steinberg Media Technologies" category="Instrument|Sampler" version="7.0.0" sdk-version="VST 3.7.5" url="http://www.steinberg.net" email="mailto:info@steinberg.de" n_inputs="0" n_outputs="70" n_aux_inputs="2" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="0">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\0fc720aed6787b66171763b0e87f86b731d0de3f.v3i

C:\Program Files\Ardour7\bin>

Mark Knecht

2023-03-11 17:02

reporter   ~0027446

Please note that I was pointed in this direction by Nathan @ Mixbus Support when he gave me this pointer:

https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Locations+Format/Plugin+Format.html

which says the directories are supposed to have the NAME.vst3/Contents format.

This note appears under the Windows section:

Note
In previous SDKs, the VST 3 plug-in was defined as a single dll file with the .vst3 extension. This is deprecated since VST 3.6.10

x42

2023-03-11 22:33

administrator   ~0027447

Ardour does support both. a single [dll] .vst3 file as well as the bunle-structure MyPlugin.vst3/Contents/x86_64-win/MyPlugin.vst3

Your change make Ardour fall back to assume the old version: traverse into sub-directories without .vst3 suffix, until a .vst3 file or folder is found. After your change a .vst3 file is found and loaded as dll.
It's a neat workaround you found.

However there is indeed an oddity. The specs [1] read "MyPlugin.vst3/Contents/x86_64-win/MyPlugin.vst3" is a **folder** containing the plugin dll.
In many cases it's not a folder by a dll.

Anyway to fix this, before you renamed the bundle dir:
Is C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3 a file or a directory, and if it is a directory, what file is contained therein?



[1] https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Locations+Format/Plugin+Format.html#for-the-windows-platform

Mark Knecht

2023-03-11 22:46

reporter   ~0027448

All of these are directories: Steinberg\HALion 7.vst3\Contents\x86_64-win

The final HALion 7.vst3 is the actual dll.

And I'm sure you understand but but for clarity the change I made by hand was renaming the HALion 7.vst3 directory just under Steinberg.

If this is real I'm sure you can probably take an existing VST3.dll file and create directories that do what I think the spec says and create the problem. If not maybe I'm on the wrong track.

Mark Knecht

2023-03-11 22:54

reporter   ~0027449

I agree, it is different than before. In this path

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

the last HALion 7.vst3 is the executable. It does not have a ".dll" at the end.

I'm currently in Ubuntu. I'll double check in Windows but I'm pretty sure that's the way it works.

Mark Knecht

2023-03-11 23:00

reporter   ~0027450

Here's an actual directory listing:

Microsoft Windows [Version 10.0.19045.2604]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Titan-R7>cd "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win"

C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win>dir
 Volume in drive C has no label.
 Volume Serial Number is E8DF-F3F4

 Directory of C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win

03/08/2023 09:02 PM <DIR> .
03/08/2023 09:02 PM <DIR> ..
01/31/2023 10:12 AM 106,967,064 HALion 7.vst3
01/31/2023 10:12 AM 856,576 Rex Shared Library.dll
01/31/2023 10:12 AM 136,088 WebView2Loader.dll
               3 File(s) 107,959,728 bytes
               2 Dir(s) 816,802,988,032 bytes free

C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win>

x42

2023-03-11 23:04

administrator   ~0027451

Odd. this should work as-is, then. Ardour should load

HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3 as DLL according to

https://github.com/Ardour/ardour/blob/master/libs/ardour/vst3_scan.cc#L315-L316

x42

2023-03-11 23:18

administrator   ~0027452

> And I'm sure you understand but but for clarity the change I made by hand was renaming the HALion 7.vst3 directory just under Steinberg.

Yes. As described above, that works around the issue.

Thanks for the info, I'll investigate why this fails, currently I cannot recreate this however. It seems in your above sfz example you have also removed the .vst suffix from sfzorando.vst3 bundle

Testing the same here. note that the verbose output below has

 bundle="C:\Program Files\Common Files\VST3\sforzando.vst3"
 module="C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3"

C:\Users\rgareus>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -fv "C:\Program Files\Common Files\VST3\sforzando.vst3"

[Info]: Scanning: C:\Program Files\Common Files\VST3\sforzando.vst3
[Info]: Found cache file: 'C:\Users\rgareus\AppData\Local\Ardour7\cache\vst\5e934701448d7ce1dd0ef71f2815b950bccb2a85.v3i'
[Info]: Cache file timestamp is valid.
[Info]: Cache file is valid and up-to-date.
[Info]: FactoryInfo: 'Plogue Art et Technologie, Inc' 'https://www.plogue.com' ' mailto:info@plogue.com'
[Info]: Class count: 2
[Info]: Class: 0 'sforzando' 'Audio Module Class' valid signature detected for C:\Program Files\Plogue\Aria\aria_x64.dll
Engine path:C:\Program Files\Plogue\Aria\aria_x64.dll
queried details:ARIA Engine v1.967 (Win x64)
**ARIA_ENGINE_INFO**
1967
1967
ARIA Engine v1.967 (Win x64)
productName:sforzando
vendorName :Plogue Art et Technologie, Inc
productId:1014
slots:1
supportURL:http://www.plogue.com
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 0
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 0
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 1
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Found Plugin: sforzando
[Info]: Touch cachefile: set mtime = 1678576322 (2023-03-12 00:12:02), plugin mtime = 1589295654 (2020-05-12 17:00:54)
        <VST3Cache version="2" bundle="C:\Program Files\Common Files\VST3\sforzando.vst3" module="C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3">
          <VST3Info uid="5C5CA79682FC437AB6539BA204BAB349" name="sforzando" vendor="Plogue Art et Technologie, Inc" category="Instrument" version="2.0.6.6" sdk-version="VST 3.6.12" url="https://www.plogue.com" email="mailto:info@plogue.com" n_inputs="0" n_outputs="2" n_aux_inputs="0" n_aux_outputs="0" n_midi_inputs="1"  n_midi_outputs="0">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\rgareus\AppData\Local\Ardour7\cache\vst\5e934701448d7ce1dd0ef71f2815b950bccb2a85.v3i

Mark Knecht

2023-03-11 23:29

reporter   ~0027453

Unless I've messed up something I think the only thing I changed what the directory name. On my machine I have this installed:

C:\Program Files\Common Files\VST3>dir
 Volume in drive C has no label.
 Volume Serial Number is E8DF-F3F4

 Directory of C:\Program Files\Common Files\VST3

03/11/2023 10:09 AM <DIR> .
03/11/2023 10:09 AM <DIR> ..
03/11/2023 10:09 AM <DIR> Cherry Audio
06/15/2022 01:08 PM <DIR> Harrison
02/21/2023 01:39 PM 11,860,480 Minimonsta2.vst3
03/06/2023 11:41 AM <DIR> Scaler2
02/26/2023 01:12 PM <DIR> sforzando
03/11/2023 10:00 AM <DIR> Steinberg
               1 File(s) 11,860,480 bytes
               7 Dir(s) 816,514,883,584 bytes free

C:\Program Files\Common Files\VST3>

In the case of sforzando the directory isn't called sforzando.vst3, so the current code finds the vst3 file in its Contents directory:

C:\Program Files\Common Files\VST3>dir sforzando
 Volume in drive C has no label.
 Volume Serial Number is E8DF-F3F4

 Directory of C:\Program Files\Common Files\VST3\sforzando

02/26/2023 01:12 PM <DIR> .
02/26/2023 01:12 PM <DIR> ..
02/26/2023 01:12 PM <DIR> Contents
               0 File(s) 0 bytes
               3 Dir(s) 816,514,113,536 bytes free

C:\Program Files\Common Files\VST3>

My ___GUESS___ is that the current code traverses the directory structure just looking for SOMETHING.vst3 and tries to load it. In the case of Halion the first thing it finds is the new directory and stops there. I suspect it doesn't keep going down to actually find the executable.

Logically I think what should happen is that when the code finds _anything_ named SOMETHING.vst3 it should test it to see if it's a directory or a file. If it's a file, then load it and see if it works. If it's a directory then traverse the hierarchy below it to find a vst3 with the same name.

I completely defer to your vastly larger experience on how to deal with this.

x42

2023-03-11 23:50

administrator   ~0027454

No need to guess, you can read the source (and your guess is wrong).

When a directory named .vst3 is found, Ardour checks if it is a bundle and if so, tries to loads it as bundle. Also in this case Ardour does not traverse further into this folder.
Otherwise Ardour recursively scans subfolders until either a file or a folder with the suffix .vst3 is found.
If a file named .vst3 is found it is loaded as dll. directly (old style)

I currently have no explanation why this failed for ...\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

When I Installed sforzando to test it was deployed to C:\Program Files\Common Files\VST3\sforzando.vst3\ as bundle, and it matches the VST3 spec.
It's odd that this differs on your machine and the .vst3 suffix is missing.

Mark Knecht

2023-03-11 23:52

reporter   ~0027455

I hope this helps. Here's a tree view of everything currently in my VST3 directory. As you can see Minimonsta2 installs the file at the top, some (Scaler2) install multiple in a single directory, some like Harrison created a subgroup AVA directory, some like sforzando followed the new spec but didn't have a dot in the name so the current code worked, and some like Halion followed the new spec but had a dot in the path name and failed.

Mantis isn't allowing me to post the tree output for some reason so I'm attaching a text version hoping that's allowed.
All_VSTS.txt (3,094 bytes)    
C:\Program Files\Common Files\VST3>tree /f
Folder PATH listing
Volume serial number is E8DF-F3F4
C:.
│   Minimonsta2.vst3
│
├───Cherry Audio
│       Sines.vst3
│       Surrealistic MG-1 Plus.vst3
│
├───Harrison
│   └───AVA
│           AVA-BF_64bit.vst3
│           AVA-DF_64bit.vst3
│           AVA-DS_64bit.vst3
│           AVA-LegacyQ_64bit.vst3
│           AVA-MC_64bit.vst3
│           AVA-ME_64bit.vst3
│           AVA-SC_64bit.vst3
│           AVA-VF_64bit.vst3
│
├───Scaler2
│       Scaler2.vst3
│       ScalerAudio2.vst3
│
├───sforzando
│   └───Contents
│       ├───Resources
│       │   └───Snapshots
│       │           5C5CA79682FC437AB6539BA204BAB349_snapshot.png
│       │           5C5CA79682FC437AB6539BA204BAB349_snapshot_2.0x.png
│       │
│       └───x86_64-win
│               sforzando.vst3
│
└───Steinberg
    └───HALion 7.vst3
        │   desktop.ini
        │   PlugIn.ico
        │
        └───Contents
            ├───Resources
            │   │   HALion 7.srf
            │   │
            │   ├───Help
            │   │   │   credits and copyrights.xml
            │   │   │   help-urls.xml
            │   │   │   urls.xml
            │   │   │
            │   │   └───help-redirect
            │   │       │   help-redirect-DE.html
            │   │       │   help-redirect-EN.html
            │   │       │   help-redirect-ES.html
            │   │       │   help-redirect-FR.html
            │   │       │   help-redirect-IT.html
            │   │       │   help-redirect-JP.html
            │   │       │   help-redirect-PT.html
            │   │       │   help-redirect-RU.html
            │   │       │   help-redirect-ZH.html
            │   │       │   offline.html
            │   │       │
            │   │       ├───css
            │   │       │       app.css
            │   │       │
            │   │       └───img
            │   │               favicon.ico
            │   │               sdh-logo.svg
            │   │
            │   ├───Snapshots
            │   │       3B63D74130B34AE397AF92A9659137D5_snapshot.png
            │   │       3B63D74130B34AE397AF92A9659137D5_snapshot_2.00x.png
            │   │
            │   └───VST Sound
            │           FCL_SMT_222_Basic_Controls.vstsound
            │           FCL_SMT_223_Additional_Controls.vstsound
            │           FCP_SMT_823_HALion_SP.vstsound
            │           SMT_030_Vector_Controls.vstsound
            │
            └───x86_64-win
                    HALion 7.vst3
                    Rex Shared Library.dll
                    WebView2Loader.dll


C:\Program Files\Common Files\VST3>
All_VSTS.txt (3,094 bytes)   

Mark Knecht

2023-03-12 00:23

reporter   ~0027456

OK, I must have changed it while debugging and forgotten to change it back. I uninstalled and reinstalled and it is sforzando.vst3 as you say. Now neither sforzando or Halion 7 scan correctly, or at least on my system the scanner doesn't output anything to this terminal:

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

C:\Program Files\Ardour7\bin>

whereas these both do. Sines is a new install and scan so the extra stuff makes sense. Minimonsta2 has been scanned before:

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Minimonsta2.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Minimonsta2.vst3
[Info]: Cache file is valid and up-to-date.
[Info]: Skipping scan.

C:\Program Files\Ardour7\bin>

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe "c:\Program Files\Common Files\VST3\Cherry Audio\Sines.vst3"

C:\Program Files\Ardour7\bin>[Info]: Scanning: c:\Program Files\Common Files\VST3\Cherry Audio\Sines.vst3
[Info]: Found Plugin: Sines
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\dccb46cc6f75fcaf87dac46c25e92d6103461d84.v3i

C:\Program Files\Ardour7\bin>

I'm not a programmer so reading the code is not a reasonable use of my time.

x42

2023-03-12 00:50

administrator   ~0027457

You need to specify options the scanner -v (for verbose) and -f (to force a rescan)

try

C:\Program Files\Ardour7\bin>ardour-vst3-scanner.exe -v -f "c:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3"

Mark Knecht

2023-03-12 08:35

reporter   ~0027458

On my system, with the period removed from the folder name it scans. With the period in if doesn't do anything,


C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -f -v "C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3


C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -f -v "C:\Program Files\Common Files\VST3\sforzandovst3\Contents\x86_64-win\sforzando.vst3

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\sforzandovst3\Contents\x86_64-win\sforzando.vst3
[Info]: FactoryInfo: 'Plogue Art et Technologie, Inc' 'https://www.plogue.com' 'mailto:info@plogue.com'
[Info]: Class count: 2
[Info]: Class: 0 'sforzando' 'Audio Module Class'
valid signature detected for C:\Program Files\Plogue\Aria\aria_x64.dll
Engine path:C:\Program Files\Plogue\Aria\aria_x64.dll
queried details:ARIA Engine v1.973 (Win x64)
**ARIA_ENGINE_INFO**
1973
1973
ARIA Engine v1.973 (Win x64)
productName:sforzando
vendorName :Plogue Art et Technologie, Inc
productId:1014
slots:1
supportURL:https://www.plogue.com
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 0
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 0
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 1
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Found Plugin: sforzando
[Info]: Touch cachefile: set mtime = 1678609439 (2023-03-12 01:23:59), plugin mtime = 1667581110 (2022-11-04 09:58:30)
        <VST3Cache version="2" bundle="C:\Program Files\Common Files\VST3\sforzandovst3\Contents\x86_64-win\sforzando.vst3" module="C:\Program Files\Common Files\VST3\sforzandovst3\Contents\x86_64-win\sforzando.vst3">
          <VST3Info uid="5C5CA79682FC437AB6539BA204BAB349" name="sforzando" vendor="Plogue Art et Technologie, Inc" category="Instrument" version="2.1.0.5" sdk-version="VST 3.7.6" url="https://www.plogue.com" email="mailto:info@plogue.com" n_inputs="0" n_outputs="2" n_aux_inputs="0" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="0">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\8b734b44b11890474f2a15748a25fffc680c973b.v3i

C:\Users\Titan-R7>




For HALion it doesn't scan with the period in. With the period removed it says it's not a valid bundle



C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -f -v "C:\Program Files\Common Files\VST3\Steinburg\HALion 7vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinburg\HALion 7vst3\Contents\x86_64-win\HALion 7.vst3
VST3 not a valid bundle: 'C:\Program Files\Common Files\VST3\Steinburg\HALion 7vst3\Contents\x86_64-win\HALion 7.vst3'

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -f -v "C:\Program Files\Common Files\VST3\Steinburg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinburg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

C:\Users\Titan-R7>


So, what does it mean "VST3 is not a valid bundle"

x42

2023-03-12 13:06

administrator   ~0027460

Last edited: 2023-03-12 13:06

 Looks like you made some typos.

Steinburg -> Steinberg

Hint: You can Drag/Drop the bundle folder from an explorer to the cmd.exe terminal.

sforzando.vst3 does not scan because it does not exist since you have removed the .vst3 suffix from the bundle dir.

Mark Knecht

2023-03-12 14:11

reporter   ~0027461

I'm getting so tired of Mantis not accepting new info and the back button not working. Someone needs to fix this thing. I will work to reenter all the work I just did.

Thanks for teaching me the drag and drop trick with cmd.exe. Saves a lot of time and fewer errors.

Mark Knecht

2023-03-12 14:13

reporter   ~0027462

With '.vst3' in the path name neither sforzando or HALion 7 scan in cmd.exe:

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3
[Info]: FactoryInfo: 'Plugin Boutique' 'http://www.pluginboutique.com/' ''
[Info]: Class count: 2
[Info]: Class: 0 'Scaler 2' 'Audio Module Class'
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 1
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 1
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 1
[Info]: VST3: - bus: 0 count: 16
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Found Plugin: Scaler 2
[Info]: Touch cachefile: set mtime = 1678630310 (2023-03-12 07:11:50), plugin mtime = 1675183798 (2023-01-31 09:49:58)
        <VST3Cache version="2" bundle="C:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3" module="C:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3">
          <VST3Info uid="ABCDEF019182FAEB654D616953636C32" name="Scaler 2" vendor="Plugin Boutique" category="Instrument" version="2.7.3" sdk-version="VST 3.7.2" url="http://www.pluginboutique.com/" email="" n_inputs="2" n_outputs="2" n_aux_inputs="0" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="1">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\4592086e7db3afb2705f8303f5c9645e125cc8ab.v3i

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3

C:\Users\Titan-R7>

Mark Knecht

2023-03-12 14:19

reporter   ~0027463

Running Rescan All in Ardour eventually hangs on HALion 7. Skip This Plugin doesn't work. Ardour has a red X in the upper right. Clicking it says "Ardour.exe is not responding". I click it and Windows says it's sending info to M$.

After Ardour crashes I have a vst3_x86_blacklist.txt file and the vst directory is populated including an entry for Halion
vst3_x64_blacklist-2.txt (93 bytes)    
C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3
vst3_x64_blacklist-2.txt (93 bytes)   
ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52-2.v3i (587 bytes)    
<?xml version="1.0" encoding="UTF-8"?>
<VST3Cache version="2" bundle="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3" module="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3">
  <VST3Info uid="3B63D74130B34AE397AF92A9659137D5" name="HALion 7" vendor="Steinberg Media Technologies" category="Instrument|Sampler" version="7.0.0" sdk-version="VST 3.7.5" url="http://www.steinberg.net" email="mailto:info@steinberg.de" n_inputs="0" n_outputs="70" n_aux_inputs="2" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="0"/>
</VST3Cache>
ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52-2.v3i (587 bytes)   

Mark Knecht

2023-03-12 14:22

reporter   ~0027464

I note that the SDK referenced in the HALion file attached above (3.7.5) is newer than any of the versions referenced in other files in the cache/vst directory.

Steinberg's release info talks about new changes:

https://forums.steinberg.net/t/vst-3-7-5-sdk-released/786928

The GITHUB page shows that there's a later 3.7.7 version also.

https://forums.steinberg.net/t/vst-3-7-7-sdk-released/822572

Mark Knecht

2023-03-12 14:37

reporter   ~0027465

And after the Ardour crash if I remove the HALion line from the blacklist file Halion becomes usable inside of Ardour. Screenshot attached - I had to crop to meet the 2MB limit in Mantis.

Mark Knecht

2023-03-12 14:49

reporter   ~0027466

Screenshot of HALion 7 in Ardour:

https://drive.google.com/file/d/1dyzeuBIPsKLVqfxhTmro6CcNYkpLhsLP/view?usp=share_link

x42

2023-03-12 15:29

administrator   ~0027467

What you describe is exactly what I would excpect. except that Ardour should not hang.

1. Create a blacklist entry
2. Scan the plugin
3. Remove the blacklist entry

Since you kill Ardour at Step 2, the plugin remains backlisted.

Also "bundle="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3" module="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"
now looks correct. The bundle is correctly detected.

Now the big question is: Does the VST3 scanner also hang when you launch it manually, or does it only happen if you use the GUI. Please run

"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3"

Mark Knecht

2023-03-12 16:27

reporter   ~0027468

Ah, so creating the blacklist entry ahead of time, then removing it if it worked is something I did not consider. thanks for the explanation.

The specific command you requested appears to me to work correctly:

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3
[Info]: Found cache file: 'C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i'
[Info]: Cache file timestamp is valid.
[Info]: Cache file is valid and up-to-date.
[Info]: FactoryInfo: 'Steinberg Media Technologies' 'http://www.steinberg.net' 'mailto:info@steinberg.de'
[Info]: Class count: 4
[Info]: Class: 0 'HALion 7' 'Audio Module Class'
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 1
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 33
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: - bus: 1 count: 2
[Info]: VST3: - bus: 2 count: 2
[Info]: VST3: - bus: 3 count: 2
[Info]: VST3: - bus: 4 count: 2
[Info]: VST3: - bus: 5 count: 2
[Info]: VST3: - bus: 6 count: 2
[Info]: VST3: - bus: 7 count: 2
[Info]: VST3: - bus: 8 count: 2
[Info]: VST3: - bus: 9 count: 2
[Info]: VST3: - bus: 10 count: 2
[Info]: VST3: - bus: 11 count: 2
[Info]: VST3: - bus: 12 count: 2
[Info]: VST3: - bus: 13 count: 2
[Info]: VST3: - bus: 14 count: 2
[Info]: VST3: - bus: 15 count: 2
[Info]: VST3: - bus: 16 count: 2
[Info]: VST3: - bus: 17 count: 2
[Info]: VST3: - bus: 18 count: 2
[Info]: VST3: - bus: 19 count: 2
[Info]: VST3: - bus: 20 count: 2
[Info]: VST3: - bus: 21 count: 2
[Info]: VST3: - bus: 22 count: 2
[Info]: VST3: - bus: 23 count: 2
[Info]: VST3: - bus: 24 count: 2
[Info]: VST3: - bus: 25 count: 2
[Info]: VST3: - bus: 26 count: 2
[Info]: VST3: - bus: 27 count: 2
[Info]: VST3: - bus: 28 count: 2
[Info]: VST3: - bus: 29 count: 2
[Info]: VST3: - bus: 30 count: 2
[Info]: VST3: - bus: 31 count: 2
[Info]: VST3: - bus: 32 count: 6
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 33
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 4
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Skipping non-effect class: Preset Compatibility Class
[Info]: Skipping non-effect class: Preset Version Class
[Info]: Found Plugin: HALion 7

x42

2023-03-12 16:31

administrator   ~0027469

" appears to me to work correctly:"

Unless the output was truncated at the end. the scanner does not seem to complete. The XML cache should be printed at the end.

Mark Knecht

2023-03-12 16:35

reporter   ~0027470

Actually, you are correct. The CLI did NOT return to the windows command line prompt. It's just sitting there after the Found Plugin: Halion 7 line.

It does not respond to Ctrl-C. I don't use Windows enough to know if that's expected but it's hung in the terminal.

Good catch!

x42

2023-03-14 03:00

administrator   ~0027473

> It does not respond to Ctrl-C.

OK. That can also explains why Ardour hangs.
The scan does not complete. Ardour tries to stop the plugin-scanner after a timeout by calling TerminateProcess() and then wait the child process to quit..

Now the big question is how killing the process ends up writing the cache file and why the scanner does not complete in the first place.

Mark Knecht

2023-03-14 14:17

reporter   ~0027474

OK, let me make sure I've given you all the info on what I'm seeing.

1) I erase the blacklist file and all files in the cache directory.

2) If I run the vst3 scanner on the actual vst3 file it does nothing other than return at the command line. Nothing is written into the cache directory. No blacklist file is created:

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3

C:\Users\Titan-R7>

3) However if I run the vst3 scanner on the HALion 7.vst3 directory just under Steinberg, the scanner does run and appears to finish correctly. The info about the vst3 file 2 directories down is shown on the screen and the cache file is created:

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3
[Info]: FactoryInfo: 'Steinberg Media Technologies' 'http://www.steinberg.net' 'mailto:info@steinberg.de'
[Info]: Class count: 4
[Info]: Class: 0 'HALion 7' 'Audio Module Class'
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 1
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 33
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: - bus: 1 count: 2
[Info]: VST3: - bus: 2 count: 2
[Info]: VST3: - bus: 3 count: 2
[Info]: VST3: - bus: 4 count: 2
[Info]: VST3: - bus: 5 count: 2
[Info]: VST3: - bus: 6 count: 2
[Info]: VST3: - bus: 7 count: 2
[Info]: VST3: - bus: 8 count: 2
[Info]: VST3: - bus: 9 count: 2
[Info]: VST3: - bus: 10 count: 2
[Info]: VST3: - bus: 11 count: 2
[Info]: VST3: - bus: 12 count: 2
[Info]: VST3: - bus: 13 count: 2
[Info]: VST3: - bus: 14 count: 2
[Info]: VST3: - bus: 15 count: 2
[Info]: VST3: - bus: 16 count: 2
[Info]: VST3: - bus: 17 count: 2
[Info]: VST3: - bus: 18 count: 2
[Info]: VST3: - bus: 19 count: 2
[Info]: VST3: - bus: 20 count: 2
[Info]: VST3: - bus: 21 count: 2
[Info]: VST3: - bus: 22 count: 2
[Info]: VST3: - bus: 23 count: 2
[Info]: VST3: - bus: 24 count: 2
[Info]: VST3: - bus: 25 count: 2
[Info]: VST3: - bus: 26 count: 2
[Info]: VST3: - bus: 27 count: 2
[Info]: VST3: - bus: 28 count: 2
[Info]: VST3: - bus: 29 count: 2
[Info]: VST3: - bus: 30 count: 2
[Info]: VST3: - bus: 31 count: 2
[Info]: VST3: - bus: 32 count: 6
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 33
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 4
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Skipping non-effect class: Preset Compatibility Class
[Info]: Skipping non-effect class: Preset Version Class
[Info]: Found Plugin: HALion 7
[Info]: Touch cachefile: set mtime = 1678802571 (2023-03-14 07:02:51), plugin mtime = 1675185166 (2023-01-31 10:12:46)
        <VST3Cache version="2" bundle="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3" module="C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3">
          <VST3Info uid="3B63D74130B34AE397AF92A9659137D5" name="HALion 7" vendor="Steinberg Media Technologies" category="Instrument|Sampler" version="7.0.0" sdk-version="VST 3.7.5" url="http://www.steinberg.net" email="mailto:info@steinberg.de" n_inputs="0" n_outputs="70" n_aux_inputs="2" n_aux_outputs="0" n_midi_inputs="1" n_midi_outputs="0">
          </VST3Info>
        </VST3Cache>
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i

C:\Users\Titan-R7>


4) If I then run the vst3 scanner a SECOND time on the HALion 7.vst DIRECTORY, that's when the scanner fails at the command line and doesn't return to the DOS prompt:

C:\Users\Titan-R7>"C:\Program Files\Ardour7\bin\ardour-vst3-scanner.exe" -v -f "C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3"

C:\Users\Titan-R7>[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3
[Info]: Found cache file: 'C:\Users\Titan-R7\AppData\Local\Ardour7\cache\vst\ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i'
[Info]: Cache file timestamp is valid.
[Info]: Cache file is valid and up-to-date.
[Info]: FactoryInfo: 'Steinberg Media Technologies' 'http://www.steinberg.net' 'mailto:info@steinberg.de'
[Info]: Class count: 4
[Info]: Class: 0 'HALion 7' 'Audio Module Class'
[Info]: VST3: media: kAudio dir: kInput type: kMain n_busses: 1
[Info]: VST3: media: kAudio dir: kInput type: kAux n_busses: 1
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: media: kAudio dir: kOutput type: kMain n_busses: 33
[Info]: VST3: - bus: 0 count: 2
[Info]: VST3: - bus: 1 count: 2
[Info]: VST3: - bus: 2 count: 2
[Info]: VST3: - bus: 3 count: 2
[Info]: VST3: - bus: 4 count: 2
[Info]: VST3: - bus: 5 count: 2
[Info]: VST3: - bus: 6 count: 2
[Info]: VST3: - bus: 7 count: 2
[Info]: VST3: - bus: 8 count: 2
[Info]: VST3: - bus: 9 count: 2
[Info]: VST3: - bus: 10 count: 2
[Info]: VST3: - bus: 11 count: 2
[Info]: VST3: - bus: 12 count: 2
[Info]: VST3: - bus: 13 count: 2
[Info]: VST3: - bus: 14 count: 2
[Info]: VST3: - bus: 15 count: 2
[Info]: VST3: - bus: 16 count: 2
[Info]: VST3: - bus: 17 count: 2
[Info]: VST3: - bus: 18 count: 2
[Info]: VST3: - bus: 19 count: 2
[Info]: VST3: - bus: 20 count: 2
[Info]: VST3: - bus: 21 count: 2
[Info]: VST3: - bus: 22 count: 2
[Info]: VST3: - bus: 23 count: 2
[Info]: VST3: - bus: 24 count: 2
[Info]: VST3: - bus: 25 count: 2
[Info]: VST3: - bus: 26 count: 2
[Info]: VST3: - bus: 27 count: 2
[Info]: VST3: - bus: 28 count: 2
[Info]: VST3: - bus: 29 count: 2
[Info]: VST3: - bus: 30 count: 2
[Info]: VST3: - bus: 31 count: 2
[Info]: VST3: - bus: 32 count: 6
[Info]: VST3: media: kAudio dir: kOutput type: kAux n_busses: 33
[Info]: VST3: media: kEvent dir: kInput type: kMain n_busses: 4
[Info]: VST3: - bus: 0 count: 16
[Info]: VST3: media: kEvent dir: kOutput type: kMain n_busses: 0
[Info]: Skipping non-effect class: Component Controller Class
[Info]: Skipping non-effect class: Preset Compatibility Class
[Info]: Skipping non-effect class: Preset Version Class
[Info]: Found Plugin: HALion 7



So in my mind the question is why does the scanner care that the cache file already exists? If using the -f option shouldn't it erase the existing cache file and write a new on in it's place? Granted, possibly it doesn't know the cache file exists? The cache file name is NOT the same as the long VST3Info uid inside the file.

Mark Knecht

2023-03-14 14:57

reporter   ~0027475

I need to double check this but I believe this also suggests how I got Halion to work originally. There's no cache file and I do a scan, either scan all or certainly scan new, then the scanner writes the cache file and the vst3 becomes available for use. If I rescan all vst3 then the scanner finds the cache file, fails and the blacklist item is left in the blacklist file. I then hand edit the blacklist file and the old cache file becomes usable again.

If any of that requires checking to help you figure this out let me know. Very happy to have your attention.

Mark Knecht

2023-03-22 18:32

reporter   ~0027498

So I've continued to look at this problem:

1) Uninstalled Mixbus32C-7, Mixbuis32C-8 and Ardour
2) Attempted to clean up old directories that hold the VST cache type stuff along with anything else that looked like it was left over. The only thing left on purpose was session files.
3) Purchased the full version of what Steinberg calls 'Absolute 6' which includes HALion 7 and a bunch of other stuff. All of this works fine in stand alone mode on the Windows desktop.

4) Installed Mixbus32C-8 and run it for the first time. It indexes but does not scan the plugins. In the Mixbus8->plugin_metadata directory there is a scan_log file which I will attach. However at this point it's alredy complaining about an "Invalid Module Path "

  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Minimonsta2.vst3" scan-log="" scan-result="1"/>
  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Scaler2\Scaler2.vst3" scan-log="" scan-result="1"/>
  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Scaler2\ScalerAudio2.vst3" scan-log="" scan-result="1"/>
  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Steinberg\Backbone.vst3" scan-log="" scan-result="1"/>
  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Steinberg\Backbone.vst3\Contents\x86_64-win\Backbone.vst3" scan-log="Invalid Module Path " scan-result="4"/>
  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Steinberg\Groove Agent.vst3" scan-log="" scan-result="1"/>
  <PluginScanLogEntry type="VST3" path="C:\Program Files\Common Files\VST3\Steinberg\Groove Agent.vst3\Contents\x86_64-win\Groove Agent.vst3" scan-log="Invalid Module Path " scan-result="4"/>

In the screenshot attached below you can see the 'Error' listed for a couple of the new Steinberg VST3's
Mixbus32C-8 error.png (21,165 bytes)   
Mixbus32C-8 error.png (21,165 bytes)   

Mark Knecht

2023-03-22 18:35

reporter   ~0027499

Continued from above...

At this point I can select a single VST, such as sforzando.vst3 and tell Mixbus to Rescan Selected. It works and prints this info in the bottom window of the plugin manager:

VST3 module-path 'C:\Program Files\Common Files\VST3\sforzando.vst3\Contents\x86_64-win\sforzando.vst3'
[Info]: Scanning: C:\Program Files\Common Files\VST3\sforzando.vst3
valid signature detected for C:\Program Files\Plogue\Aria\aria_x64.dll
Engine path:C:\Program Files\Plogue\Aria\aria_x64.dll
queried details:ARIA Engine v1.973 (Win x64)
**ARIA_ENGINE_INFO**
1973
1973
ARIA Engine v1.973 (Win x64)
productName:sforzando
vendorName :Plogue Art et Technologie, Inc
productId:1014
slots:1
supportURL:https://www.plogue.com
[Info]: Found Plugin: sforzando
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Mixbus8\cache\vst\5e934701448d7ce1dd0ef71f2815b950bccb2a85.v3i

Mark Knecht

2023-03-22 18:41

reporter   ~0027500

Continued from above...

At this point I try scanning HALion Sonic and get the same failure I see for HALion 7. The scan starts but appears to hang. The cache file is written into Mixbus8 and HALion Sonic is written into the blacklist file. However I let it sit for literaly 2-3 inutes and it eventually returns. The blacklist entry is removed. The following info is in the bottom window:

VST3 module-path 'C:\Program Files\Common Files\VST3\Steinberg\HALion Sonic.vst3\Contents\x86_64-win\HALion Sonic.vst3'
[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion Sonic.vst3
[Info]: VST3: \ ignored bus: 1 type: kMain count: 2
[Info]: VST3: \ ignored bus: 2 type: kMain count: 2
[Info]: VST3: \ ignored bus: 3 type: kMain count: 2
[Info]: VST3: \ ignored bus: 4 type: kMain count: 2
[Info]: VST3: \ ignored bus: 5 type: kMain count: 2
[Info]: VST3: \ ignored bus: 6 type: kMain count: 2
[Info]: VST3: \ ignored bus: 7 type: kMain count: 2
[Info]: VST3: \ ignored bus: 8 type: kMain count: 2
[Info]: VST3: \ ignored bus: 9 type: kMain count: 2
[Info]: VST3: \ ignored bus: 10 type: kMain count: 2
[Info]: VST3: \ ignored bus: 11 type: kMain count: 2
[Info]: VST3: \ ignored bus: 12 type: kMain count: 2
[Info]: VST3: \ ignored bus: 13 type: kMain count: 2
[Info]: VST3: \ ignored bus: 14 type: kMain count: 2
[Info]: VST3: \ ignored bus: 15 type: kMain count: 2
[Info]: Found Plugin: HALion Sonic
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Mixbus8\cache\vst\623c584c77832ba982eb59fdb0f799cdf055bc9b.v3i

x42

2023-03-22 18:43

administrator   ~0027501

Note that uninstalling Mixbus does not remove the config or any of the prior plugin caches. In fact un/reinstalling Mixbus should be a no-op.

Remove %localappdata%\mixbus9\ to clear the preferences and plugin-cache.

Mark Knecht

2023-03-22 18:48

reporter   ~0027502

Continued from above...

Finally I brave the HALion 7 scan. It hangs for about 4 minutes but eventually completes with this info in the bottom window:

VST3 module-path 'C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3\Contents\x86_64-win\HALion 7.vst3'
[Info]: Scanning: C:\Program Files\Common Files\VST3\Steinberg\HALion 7.vst3
[Info]: VST3: \ ignored bus: 0 type: kAux count: 2
[Info]: VST3: \ ignored bus: 1 type: kMain count: 2
[Info]: VST3: \ ignored bus: 2 type: kMain count: 2
[Info]: VST3: \ ignored bus: 3 type: kMain count: 2
[Info]: VST3: \ ignored bus: 4 type: kMain count: 2
[Info]: VST3: \ ignored bus: 5 type: kMain count: 2
[Info]: VST3: \ ignored bus: 6 type: kMain count: 2
[Info]: VST3: \ ignored bus: 7 type: kMain count: 2
[Info]: VST3: \ ignored bus: 8 type: kMain count: 2
[Info]: VST3: \ ignored bus: 9 type: kMain count: 2
[Info]: VST3: \ ignored bus: 10 type: kMain count: 2
[Info]: VST3: \ ignored bus: 11 type: kMain count: 2
[Info]: VST3: \ ignored bus: 12 type: kMain count: 2
[Info]: VST3: \ ignored bus: 13 type: kMain count: 2
[Info]: VST3: \ ignored bus: 14 type: kMain count: 2
[Info]: VST3: \ ignored bus: 15 type: kMain count: 2
[Info]: VST3: \ ignored bus: 16 type: kMain count: 2
[Info]: VST3: \ ignored bus: 17 type: kMain count: 2
[Info]: VST3: \ ignored bus: 18 type: kMain count: 2
[Info]: VST3: \ ignored bus: 19 type: kMain count: 2
[Info]: VST3: \ ignored bus: 20 type: kMain count: 2
[Info]: VST3: \ ignored bus: 21 type: kMain count: 2
[Info]: VST3: \ ignored bus: 22 type: kMain count: 2
[Info]: VST3: \ ignored bus: 23 type: kMain count: 2
[Info]: VST3: \ ignored bus: 24 type: kMain count: 2
[Info]: VST3: \ ignored bus: 25 type: kMain count: 2
[Info]: VST3: \ ignored bus: 26 type: kMain count: 2
[Info]: VST3: \ ignored bus: 27 type: kMain count: 2
[Info]: VST3: \ ignored bus: 28 type: kMain count: 2
[Info]: VST3: \ ignored bus: 29 type: kMain count: 2
[Info]: VST3: \ ignored bus: 30 type: kMain count: 2
[Info]: VST3: \ ignored bus: 31 type: kMain count: 2
[Info]: VST3: \ ignored bus: 32 type: kMain count: 6
[Info]: Found Plugin: HALion 7
[Info]: Saved VST3 plugin cache to C:\Users\Titan-R7\AppData\Local\Mixbus8\cache\vst\ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i

Mark Knecht

2023-03-22 19:20

reporter   ~0027503

I found the Mixbus32C Preferences window in the Plugins section has buttons to clear cache and the Ignore List for both vst2 & vst3. It's probably there in Ardour also.

From my POV it appears that at least with the full version of HALion 7 that simply letting it sit for 4-5 minutes was enough to allow Mixbus to complete successfully. I assume Ardour also which I could check if it's important to you.

Even though it works there are, I think, 2 issue left outstanding:

1) All of the Steinberg VSTs that came in this package still have 'Invalid Module PAth' errors left in the Plugin Manager window.

2) If I hit the 'Ignore unresponsive plugins' buttons while waiting for HALion to scan it does cause Mixbus and Ardour to be marked as crashed and sends a report to M$.

It would be good to figure out the fixes for both of these. I'm here to help if you need me.

x42

2023-04-04 21:47

administrator   ~0027534

Nathan tested this today on a Windows 10 system and the plugin scanned without issue in Mixbus 32C, and directly showed up.

He said it took 3 install steps
* Steinberg Downloader
* Activation Manager
* Steinberg Library


After that I logged into the machine and installed an Ardour debug build to verify that the bundle is scanned and this works correctly as expected.

I cannot see a codepath in Ardour 7 or Mixbus 9 that would require the plugin folder to be renamed. It remains a mystery why [only] your system is affected by this.
HALion-vst3-scan.png (124,872 bytes)   
HALion-vst3-scan.png (124,872 bytes)   

Mark Knecht

2023-04-04 23:04

reporter   ~0027535

I guess I'm unlucky.

A couple of things for the record:

1) Nathan emailed me that he's on Win 11. Possibly that's a misprint. I'm on Win 10.

2) I reported earlier that if the cache files and blacklist are deleted then the scan doesn't fail.

3) I find that almost none of the Steinberg stuff works after the session has been saved and reloaded. It's fine when first instantiated.

4) If there's only 2 machines tested (that I know of) and one works/one fails, I don't think that's much of a data set but yes, it's so far only my machine that fails.

x42

2023-04-04 23:46

administrator   ~0027536

Re (3) do you mean https://tracker.ardour.org/view.php?id=9287 (different issue, unrelated to scanning)?

Mark Knecht

2023-04-07 20:31

reporter   ~0027563

OK, interesting news concerning the %PLUGIN%.vst3/Contents/x86_64-win/%PLUGIN%.vst3 "Invalid path" problem.

I will leave it to you to decide to call it resolved or leave it open.

I set up my only 2 Windows machines with lots of plugins, but to be transparent they aren't the same set beyond what the installs give me.

1) The laptop has Mixbus32C-7, Mixbus32C-9 and Ardour-7.3.0. On that machine all 3 versions of the programs cause the error for the sforzando VST3 which is, on this machine, the only plugin that uses this new Steinberg directory structure. This machine has some Native Instrument plugins. They don't use the structure and they are fine.

2) The big machine has Mixbus32C-8, Mixbus32C-9 and the nightly from last night Ardour-7.3.187. On this machine in BOTH versions of Mixbys32C all plugins with the new directory structure fail with the "Invalid path" message but 7.3.187, which solved the Halion VST scan problem, does not have the "Invalid path" problem. Nothing marked 'Error' anymore.

Is it solved by the same fix, or by something else? I don't know, but for now it appears to be fixed at least for Ardour nightly.

If you choose to close this bug report I think that's reasonable. If I see the problem again I'll open a new bug report with new data.

I don't know how these updates get to Harrison but I'll hope they get there sooner than later and test each update they make available.

Issue History

Date Modified Username Field Change
2023-03-08 00:50 Mark Knecht New Issue
2023-03-08 00:50 Mark Knecht Tag Attached: crash
2023-03-08 00:50 Mark Knecht Tag Attached: VST3
2023-03-08 00:52 Mark Knecht Note Added: 0027436
2023-03-08 00:52 Mark Knecht File Added: ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52.v3i
2023-03-08 00:53 Mark Knecht Note Added: 0027437
2023-03-08 00:53 Mark Knecht File Added: vst3_x64_blacklist.txt
2023-03-08 01:01 x42 Note Added: 0027438
2023-03-08 13:35 Mark Knecht Note Added: 0027439
2023-03-09 00:32 x42 Note Added: 0027440
2023-03-09 03:59 Mark Knecht Note Added: 0027441
2023-03-09 04:01 Mark Knecht Note Added: 0027442
2023-03-11 16:43 Mark Knecht Note Added: 0027443
2023-03-11 16:46 Mark Knecht Note Added: 0027444
2023-03-11 16:56 Mark Knecht Note Added: 0027445
2023-03-11 17:02 Mark Knecht Note Added: 0027446
2023-03-11 22:33 x42 Note Added: 0027447
2023-03-11 22:46 Mark Knecht Note Added: 0027448
2023-03-11 22:54 Mark Knecht Note Added: 0027449
2023-03-11 23:00 Mark Knecht Note Added: 0027450
2023-03-11 23:04 x42 Note Added: 0027451
2023-03-11 23:18 x42 Note Added: 0027452
2023-03-11 23:29 Mark Knecht Note Added: 0027453
2023-03-11 23:50 x42 Note Added: 0027454
2023-03-11 23:52 Mark Knecht Note Added: 0027455
2023-03-11 23:52 Mark Knecht File Added: All_VSTS.txt
2023-03-12 00:23 Mark Knecht Note Added: 0027456
2023-03-12 00:50 x42 Note Added: 0027457
2023-03-12 08:35 Mark Knecht Note Added: 0027458
2023-03-12 13:06 x42 Note Added: 0027460
2023-03-12 13:06 x42 Note Edited: 0027460
2023-03-12 14:11 Mark Knecht Note Added: 0027461
2023-03-12 14:13 Mark Knecht Note Added: 0027462
2023-03-12 14:19 Mark Knecht Note Added: 0027463
2023-03-12 14:19 Mark Knecht File Added: vst3_x64_blacklist-2.txt
2023-03-12 14:19 Mark Knecht File Added: ed88f2b4c7d4b3ff3583533ad8c95e8e16d6bb52-2.v3i
2023-03-12 14:22 Mark Knecht Note Added: 0027464
2023-03-12 14:37 Mark Knecht Note Added: 0027465
2023-03-12 14:49 Mark Knecht Note Added: 0027466
2023-03-12 15:29 x42 Note Added: 0027467
2023-03-12 16:27 Mark Knecht Note Added: 0027468
2023-03-12 16:31 x42 Note Added: 0027469
2023-03-12 16:35 Mark Knecht Note Added: 0027470
2023-03-14 03:00 x42 Note Added: 0027473
2023-03-14 14:17 Mark Knecht Note Added: 0027474
2023-03-14 14:57 Mark Knecht Note Added: 0027475
2023-03-22 18:32 Mark Knecht Note Added: 0027498
2023-03-22 18:32 Mark Knecht File Added: Mixbus32C-8 error.png
2023-03-22 18:35 Mark Knecht Note Added: 0027499
2023-03-22 18:41 Mark Knecht Note Added: 0027500
2023-03-22 18:43 x42 Note Added: 0027501
2023-03-22 18:48 Mark Knecht Note Added: 0027502
2023-03-22 19:20 Mark Knecht Note Added: 0027503
2023-04-04 21:47 x42 Note Added: 0027534
2023-04-04 21:47 x42 File Added: HALion-vst3-scan.png
2023-04-04 23:04 Mark Knecht Note Added: 0027535
2023-04-04 23:46 x42 Note Added: 0027536
2023-04-07 20:31 Mark Knecht Note Added: 0027563
2023-12-19 19:52 x42 Relationship added has duplicate 0009582