Waveform Problem Plugins

Discussion about: tracktion.com
User avatar
ero
KVRist
42 posts since 12 Jan, 2005

Post Thu Aug 29, 2019 12:37 am

[img]D:\Bilder\Captain[/img]


Captain plugins UI problem. I cant access the plugins at all. This is affecting all the Captain plugins. See image.

Win 10 64bit Waveform 10
You do not have the required permissions to view the files attached to this post.

akeia
KVRist
149 posts since 14 Nov, 2016 from Berliner Umland

Re: Waveform Problem Plugins

Post Mon Sep 02, 2019 11:05 am

Waveform 10.2.1 on OSX 10.14.6 crashes on me with all Softube plugins when the GUI is opened.

Example scan for VST3 of OTO Bisquit:

pluginval v0.2.3 - JUCE v5.4.3
Started validating: /Library/Audio/Plug-Ins/VST3/OTO Biscuit 8-bit Effects.vst3
Random seed: 0x55771f2
Validation started: 2 Sep 2019 9:00:40pm

Strictness level: 5
-----------------------------------------------------------------
Starting test: pluginval / Scan for known types: /Library/Audio/Plug-Ins/VST3/OTO Biscuit 8-bit Effects.vst3...
Num types found: 1

Testing plugin: VST3-OTO Biscuit 8-bit Effects-6fd1df8c-3c6b9635
Softube: OTO Biscuit 8-bit Effects v2.4.83
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Open plugin (cold)...

Time taken to open plugin (cold): 1 sec
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Open plugin (warm)...

Time taken to open plugin (warm): 441 ms
Running tests 1 times
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Plugin info...

Plugin name: OTO Biscuit 8-bit Effects
Alternative names: OTO Biscuit 8-bit Effects
SupportsDoublePrecision: no
Reported latency: 0
Reported taillength: 0

Time taken to run test: 0
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Editor...

*** FAILED: VALIDATION CRASHED

0 pluginval 0x00000001054fce91 _ZN4juce11SystemStats17getStackBacktraceEv + 65
1 pluginval 0x00000001054431c4 _ZN12_GLOBAL__N_119getCrashLogContentsEv + 52
2 pluginval 0x00000001054fcf84 _ZN4juceL11handleCrashEi + 20
3 libsystem_platform.dylib 0x00007fff61088b5d _sigtramp + 29
4 ??? 0x0000000000000001 0x0 + 1
5 Biscuit_VST_AU_Protect 0x000000010b156148 bundleExit + 892376
6 libdispatch.dylib 0x00007fff60e5063d _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff60e5b68d _dispatch_main_queue_callback_4CF + 1135
8 CoreFoundation 0x00007fff34eae556 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
9 CoreFoundation 0x00007fff34eadc83 __CFRunLoopRun + 2300
10 CoreFoundation 0x00007fff34ead135 CFRunLoopRunSpecific + 459
11 HIToolbox 0x00007fff340fe1ab RunCurrentEventLoopInMode + 292
12 HIToolbox 0x00007fff340fdee5 ReceiveNextEventCommon + 603
13 HIToolbox 0x00007fff340fdc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
14 AppKit 0x00007fff3249679d _DPSNextEvent + 1135
15 AppKit 0x00007fff3249548b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
16 pluginval 0x0000000105517a9c _ZN4juce14MessageManager20runDispatchLoopUntilEi + 268
17 pluginval 0x00000001054558be _ZL34createAndShowEditorOnMessageThreadRN4juce19AudioPluginInstanceE + 462
18 pluginval 0x000000010545d3b1 _ZN10EditorTest7runTestER11PluginTestsRN4juce19AudioPluginInstanceE + 113
19 pluginval 0x0000000105453b32 _ZN4juce14MessageManager16AsyncCallInvokerIZN11PluginTests8testTypeERKNS_17PluginDescriptionEE3$_1E15messageCallbackEv + 34
20 pluginval 0x0000000105512015 _ZN4juce12MessageQueue18deliverNextMessageEv + 245
21 pluginval 0x0000000105511ece _ZN4juce12MessageQueue21runLoopSourceCallbackEPv + 14
22 CoreFoundation 0x00007fff34eca3bb __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
23 CoreFoundation 0x00007fff34eca361 __CFRunLoopDoSource0 + 108
24 CoreFoundation 0x00007fff34eae26b __CFRunLoopDoSources0 + 195
25 CoreFoundation 0x00007fff34ead833 __CFRunLoopRun + 1196
26 CoreFoundation 0x00007fff34ead135 CFRunLoopRunSpecific + 459
27 HIToolbox 0x00007fff340fe1ab RunCurrentEventLoopInMode + 292
28 HIToolbox 0x00007fff340fdee5 ReceiveNextEventCommon + 603
29 HIToolbox 0x00007fff340fdc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
30 AppKit 0x00007fff3249679d _DPSNextEvent + 1135
31 AppKit 0x00007fff3249548b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
32 AppKit 0x00007fff3248f5a8 -[NSApplication run] + 699
33 pluginval 0x0000000105449c6c main + 348
34 libdyld.dylib 0x00007fff60e9d3d5 start + 1
35 ??? 0x0000000000000004 0x0 + 4

Binary Images:
0x10543a000 pluginval
0x7fff61084000 libsystem_platform.dylib
0x10b02c000 Biscuit_VST_AU_Protect
0x7fff60e4d000 libdispatch.dylib
0x7fff34e73000 CoreFoundation
0x7fff340f3000 HIToolbox
0x7fff3247c000 AppKit
0x7fff60e87000 libdyld.dylib

swartzta
KVRer
2 posts since 6 Jun, 2019

Re: Waveform Problem Plugins

Post Sat Sep 07, 2019 9:10 am

ero wrote:
Thu Aug 29, 2019 12:37 am
[img]D:\Bilder\Captain[/img]


Captain plugins UI problem. I cant access the plugins at all. This is affecting all the Captain plugins. See image.

Win 10 64bit Waveform 10
I get the same thing. It also did it to Kontakt, but once I changed DPI awareness seems to work. Doesn't work for Captain Plugins though. Windows 10, 64 bit.

Kott
KVRist
84 posts since 12 Mar, 2013 from Russia, Vladivostok

Re: Waveform Problem Plugins

Post Sun Sep 08, 2019 10:33 pm

Return to long-suffering Wavefowm+Drumgizmo pair.
I just checked it under Windows and behavior is the same. Drumgizmo hangs Waveform successfully.
It's easy to prove: download from https://www.drumgizmo.org/wiki/doku.php ... st_version unpack/to vst-dir and add to project.

pauljennings
KVRer
7 posts since 3 Apr, 2016

Re: Waveform Problem Plugins

Post Tue Sep 10, 2019 11:13 pm

currently on 10.3.1 and have a problem with the mute button
i muted a vocal track but when i un mute it all i get is really loud white noise and have to close down waveform and restart it to fix the issue, it has happened a couple of times and did actually happen before in the beta once.Also on mutes some times i record an audio track then when i mute it the
adjacent midi keyboard track does not sound, i can see the audio in the input level meter but no sound as if that is also muted , any ideas guys

jabe
KVRAF
1919 posts since 9 Oct, 2008 from UK

Re: Waveform Problem Plugins

Post Fri Sep 13, 2019 7:48 am

Not exactly a plug-in problem.
[W10-64, T5/6/7/W8/9/10, 32&64, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

dellboy
KVRian
1030 posts since 28 Mar, 2007

Re: Waveform Problem Plugins

Post Fri Sep 13, 2019 7:59 am

Air Strike drum plugin does not work in Waveform 10.

I tried it in five other DAWs and it works fine.

tovokas
KVRist
286 posts since 9 Sep, 2005 from Washington State. USA

Re: Waveform Problem Plugins

Post Fri Sep 13, 2019 11:40 pm

dellboy wrote:
Fri Sep 13, 2019 7:59 am
Air Strike drum plugin does not work in Waveform 10.
Hmmm, Strike version 2.0.7.19000 seems to be working fine on my MacOS Mojave machine with the latest version of Waveform 10. (And the Strike VST passed all tests in the PluginVal scan...)
iMac (Retina 5K, 27-inch, 2017), 4.2 GHz Intel Core i7
Radeon Pro 580 8 GB
Focusrite Scarlett 4i4 3rd Gen
Waveform 10/Studio One Pro 3.5

dellboy
KVRian
1030 posts since 28 Mar, 2007

Re: Waveform Problem Plugins

Post Sat Sep 14, 2019 12:45 am

tovokas wrote:
Fri Sep 13, 2019 11:40 pm
dellboy wrote:
Fri Sep 13, 2019 7:59 am
Air Strike drum plugin does not work in Waveform 10.
Hmmm, Strike version 2.0.7.19000 seems to be working fine on my MacOS Mojave machine with the latest version of Waveform 10. (And the Strike VST passed all tests in the PluginVal scan...)
I am on Windows 10.

I have no idea what "PluginVal" scan is.

jabe
KVRAF
1919 posts since 9 Oct, 2008 from UK

Re: Waveform Problem Plugins

Post Sat Sep 14, 2019 6:00 am

dellboy wrote:
Sat Sep 14, 2019 12:45 am
tovokas wrote:
Fri Sep 13, 2019 11:40 pm
dellboy wrote:
Fri Sep 13, 2019 7:59 am
Air Strike drum plugin does not work in Waveform 10.
Hmmm, Strike version 2.0.7.19000 seems to be working fine on my MacOS Mojave machine with the latest version of Waveform 10. (And the Strike VST passed all tests in the PluginVal scan...)
I am on Windows 10.

I have no idea what "PluginVal" scan is.
PluginVal is software the Tracktion devs wrote which attempts to validate plug-ins. It's available from the T website under the Develop tab.
[W10-64, T5/6/7/W8/9/10, 32&64, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

dellboy
KVRian
1030 posts since 28 Mar, 2007

Re: Waveform Problem Plugins

Post Sat Sep 14, 2019 7:58 am

jabe wrote:
Sat Sep 14, 2019 6:00 am

PluginVal is software the Tracktion devs wrote which attempts to validate plug-ins. It's available from the T website under the Develop tab.
Ok, thanks.

I found the app, ran it, and Air Strike fails. And yet it works fine in all other DAWs on windows.

bburtin
KVRist
180 posts since 12 Mar, 2002 from Mountain View, CA

Re: Waveform Problem Plugins

Post Sat Sep 14, 2019 8:08 am

I can't run Strike on Windows 10 in W10 either. I also can't run the Novation Ultranova editor on W9 or W10. Metric Halo Channel Strip bombed on W9, but seems to be working again in W10.

It's pretty discouraging. The Tracktion devs blame the plugins for not following the VST spec properly. But the plugin devs have no incentive to fix their code, because they're working on new products that make them money. So I'm still stuck on W8.

jabe
KVRAF
1919 posts since 9 Oct, 2008 from UK

Re: Waveform Problem Plugins

Post Sat Sep 14, 2019 2:01 pm

Waveform (and Tracktion) are based on Juce, which is a set of modules written by Julian Storer, who invented Tracktion in the first place. Juce is also the basis for the software used by the Roli keyboards. While changes can be made to the Waveform code by the Tracktion devs, the parts processed by Juce code need changing higher up the food chain. Whether that is the location of some plug-in compatibility problems (and one can hardly blame Tracktion for correctly following the VST protocols), I have no idea, but if it were the case, the Juce modules would need changing to allow the shoddy plug-ins to work. I can't really see Juce slackening its standards, so there may be something of an impasse.

Some of the Tracktion source code (the Tracktion Engine) was made available a few years ago, although not the user interface code. Perhaps someone more experienced in whichever coding language it is might be able to use the Tracktion Engine and find where its shortcoming might lie, if any.
[W10-64, T5/6/7/W8/9/10, 32&64, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

dellboy
KVRian
1030 posts since 28 Mar, 2007

Re: Waveform Problem Plugins

Post Sun Sep 15, 2019 1:19 am

jabe wrote:
Sat Sep 14, 2019 2:01 pm
(and one can hardly blame Tracktion for correctly following the VST protocols), I have no idea, but if it were the case, the Juce modules would need changing to allow the shoddy plug-ins to work. I can't really see Juce slackening its standards, so there may be something of an impasse.

I do blame Tracktion for not making my paid for plugin work in a DAW that I paid for.

I have zero interest in excuses about Tracktion being a superior DAW and blocking a "shoddy" plugin that runs ok in every other DAW you care to name.

As for Tracktion being written in Juce,my memory is that Julian only started to develop that after he sold Tracktion to Mackie. So the original Tracktion was not written in Juce because it did not exist back then.

*edit:

I have an old CD with Tracktion 1.6 on it and it installed on Windows 10 with no problems. I scanned my old 32bit directory with Air Strike 32 bit in it and it works fine in Tracktion 1.6. Theres progress for you.

jabe
KVRAF
1919 posts since 9 Oct, 2008 from UK

Re: Waveform Problem Plugins

Post Sun Sep 15, 2019 5:46 am

dellboy wrote:
Sun Sep 15, 2019 1:19 am
jabe wrote:
Sat Sep 14, 2019 2:01 pm
(and one can hardly blame Tracktion for correctly following the VST protocols), I have no idea, but if it were the case, the Juce modules would need changing to allow the shoddy plug-ins to work. I can't really see Juce slackening its standards, so there may be something of an impasse.

I do blame Tracktion for not making my paid for plugin work in a DAW that I paid for.

I have zero interest in excuses about Tracktion being a superior DAW and blocking a "shoddy" plugin that runs ok in every other DAW you care to name.

As for Tracktion being written in Juce,my memory is that Julian only started to develop that after he sold Tracktion to Mackie. So the original Tracktion was not written in Juce because it did not exist back then.

*edit:

I have an old CD with Tracktion 1.6 on it and it installed on Windows 10 with no problems. I scanned my old 32bit directory with Air Strike 32 bit in it and it works fine in Tracktion 1.6. Theres progress for you.
I don't dispute any of that. As you say, it wasn't originally written in Juce because it preceded it. I'm sure a lot of it is now.

It appears that it worked as recently as Waveform 9.3.2, so perhaps the devs can sort it soon.
[W10-64, T5/6/7/W8/9/10, 32&64, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Return to “Tracktion”