Waveform Problem Plugins

[JamminFool]

If not already reported, Jamstix 4 does not draw correctly in Waveform 9. Using enabling DPI does not fix the problem.

[chico.co.uk]

If not already reported, Jamstix 4 does not draw correctly in Waveform 9. Using enabling DPI does not fix the problem.

Works fine for me. It's worth contacting Ralph at Rayzoon about this, because i had graphics issues with Jamstix in Waveform in the past, and he pointed me to a setting in Jamstix which corrected the problem. But your issue may be different to mine (and tbh, i can't remember which setting it was ... )

[JamminFool]

If not already reported, Jamstix 4 does not draw correctly in Waveform 9. Using enabling DPI does not fix the problem.

Works fine for me. It's worth contacting Ralph at Rayzoon about this, because i had graphics issues with Jamstix in Waveform in the past, and he pointed me to a setting in Jamstix which corrected the problem. But your issue may be different to mine (and tbh, i can't remember which setting it was ... )

Thank you! I will contact Ralph.

[spoontechnique]

I've had problems (crashes that make a project un-openable) in W10 with ReaControlMidi. W10 can't seem to disable it like W9 can (it causes crashes in that too, but I can at least open it).

For reference, I'm using ReaControlMidi to automate pitch wheel and automation data, since it is either frustrating or sometimes doesn't work in Waveform otherwise.

[JamminFool]

If not already reported, Jamstix 4 does not draw correctly in Waveform 9. Using enabling DPI does not fix the problem.

Works fine for me. It's worth contacting Ralph at Rayzoon about this, because i had graphics issues with Jamstix in Waveform in the past, and he pointed me to a setting in Jamstix which corrected the problem. But your issue may be different to mine (and tbh, i can't remember which setting it was ... )

Thank you! I will contact Ralph.

Rayzoon Jamstix 4 is still a problem.

So I contacted Ralph at Rayzoon. He asked me to try the beta version of JS and enable DPI in Waveform. It fixed the problem (but only with the beta, not the release version). However, Waveform does not save the DPI setting with the plugin or the project so it must be reset every time.

So he asked me to request that Waveform save the setting somehow.

He also asked me to try a troubleshooting mode in Jamstix called APS mode, stating:

"This will work-around the DPI issue with Waveform as Jamstix will run in its
own process outside of Waveform. I'd still encourage you to file a ticket
with Tracktion to have the High DPI setting in Waveform recalled once set."

So yes, the APS Mode seems to fix the problem, but is only a troubleshooting work-around (and seems to make Waveform take a very long time to shut down). In addition, the setting will affect how Jamstix runs in ALL DAWS, not just Waveform, so not exactly great.

[operandx]

If not already reported, Jamstix 4 does not draw correctly in Waveform 9. Using enabling DPI does not fix the problem.

Works fine for me. It's worth contacting Ralph at Rayzoon about this, because i had graphics issues with Jamstix in Waveform in the past, and he pointed me to a setting in Jamstix which corrected the problem. But your issue may be different to mine (and tbh, i can't remember which setting it was ... )

Thank you! I will contact Ralph.

Rayzoon Jamstix 4 is still a problem.

So I contacted Ralph at Rayzoon. He asked me to try the beta version of JS and enable DPI in Waveform. It fixed the problem (but only with the beta, not the release version). However, Waveform does not save the DPI setting with the plugin or the project so it must be reset every time.

So he asked me to request that Waveform save the setting somehow.

He also asked me to try a troubleshooting mode in Jamstix called APS mode, stating:

"This will work-around the DPI issue with Waveform as Jamstix will run in its
own process outside of Waveform. I'd still encourage you to file a ticket
with Tracktion to have the High DPI setting in Waveform recalled once set."

So yes, the APS Mode seems to fix the problem, but is only a troubleshooting work-around (and seems to make Waveform take a very long time to shut down). In addition, the setting will affect how Jamstix runs in ALL DAWS, not just Waveform, so not exactly great.

W10 now saves DPI setting for Jamstix4 and any other plug that requires it..

[JamminFool]

If not already reported, Jamstix 4 does not draw correctly in Waveform 9. Using enabling DPI does not fix the problem.

Works fine for me. It's worth contacting Ralph at Rayzoon about this, because i had graphics issues with Jamstix in Waveform in the past, and he pointed me to a setting in Jamstix which corrected the problem. But your issue may be different to mine (and tbh, i can't remember which setting it was ... )

Thank you! I will contact Ralph.

Rayzoon Jamstix 4 is still a problem.

So I contacted Ralph at Rayzoon. He asked me to try the beta version of JS and enable DPI in Waveform. It fixed the problem (but only with the beta, not the release version). However, Waveform does not save the DPI setting with the plugin or the project so it must be reset every time.

So he asked me to request that Waveform save the setting somehow.

He also asked me to try a troubleshooting mode in Jamstix called APS mode, stating:

"This will work-around the DPI issue with Waveform as Jamstix will run in its
own process outside of Waveform. I'd still encourage you to file a ticket
with Tracktion to have the High DPI setting in Waveform recalled once set."

So yes, the APS Mode seems to fix the problem, but is only a troubleshooting work-around (and seems to make Waveform take a very long time to shut down). In addition, the setting will affect how Jamstix runs in ALL DAWS, not just Waveform, so not exactly great.

W10 now saves DPI setting for Jamstix4 and any other plug that requires it..

yes, so I was told by product support. that is very nice for new customers.

but W10 is a paid upgrade and I would expect to receive at least one bug fix update to W9. But so far I have only had the same current version since I bought it (ie, NO BUG FIXES at all). Not sure I want to buy a new version every time i need a bug fixed.

[fde101]

Schoeps Double MS from Plugin Alliance - VST3 version crashes as below, AU version seems ok so far

pluginval v0.2.1 - JUCE v5.4.1
Started validating: /Library/Audio/Plug-Ins/VST3/Schoeps Double MS.vst3
Random seed: 0x27e4c9f
Validation started: 11 Feb 2019 9:49:00am

Strictness level: 5
-----------------------------------------------------------------
Starting test: pluginval / Scan for known types: /Library/Audio/Plug-Ins/VST3/Schoeps Double MS.vst3...
Num types found: 1

Testing plugin: VST3-Schoeps Double MS-958c6f53-55c804b8
Plugin Alliance: Schoeps Double MS v1.0.0
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Open plugin (cold)...

*** FAILED: VALIDATION CRASHED

0 pluginval 0x000000010b59cfc1 _ZN4juce11SystemStats17getStackBacktraceEv + 65
1 pluginval 0x000000010b4e3754 _ZN12_GLOBAL__N_119getCrashLogContentsEv + 52
2 pluginval 0x000000010b59d0f4 _ZN4juceL11handleCrashEi + 20
3 libsystem_platform.dylib 0x00007fffbf408b3a _sigtramp + 26
4 ??? 0x3fdb5af92cb2b1f4 0x0 + 4601371470532358644
5 Schoeps Double MS 0x000000010f893541 _ZN4juce12MessageQueue21runLoopSourceCallbackEPv + 129
6 CoreFoundation 0x00007fffa95e5311 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
7 CoreFoundation 0x00007fffa95c6507 __CFRunLoopDoSources0 + 423
8 CoreFoundation 0x00007fffa95c5a76 __CFRunLoopRun + 934
9 CoreFoundation 0x00007fffa95c5474 CFRunLoopRunSpecific + 420
10 HIToolbox 0x00007fffa8b23ebc RunCurrentEventLoopInMode + 240
11 HIToolbox 0x00007fffa8b23cf1 ReceiveNextEventCommon + 432
12 HIToolbox 0x00007fffa8b23b26 _BlockUntilNextEventMatchingListInModeWithFilter + 71
13 AppKit 0x00007fffa70b8a54 _DPSNextEvent + 1120
14 AppKit 0x00007fffa78347ee -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
15 AppKit 0x00007fffa70ad3db -[NSApplication run] + 926
16 pluginval 0x000000010b4ea25c main + 348
17 libdyld.dylib 0x000000010c187235 start + 1

Binary Images:
0x10b4da000 pluginval
0x7fffbf406000 libsystem_platform.dylib
0x10f776000 Schoeps Double MS
0x7fffa9540000 CoreFoundation
0x7fffa8af3000 HIToolbox
0x7fffa7072000 AppKit
0x10c182000 libdyld.dylib

[chico.co.uk]

"So yes, the APS Mode seems to fix the problem, but is only a troubleshooting work-around" - Did Ralph actually say that, or did you decide that's what he meant? I made this change months ago in Jamstix 4, and have just got on with using it. I'm not really seeing what the problem is with running the plugin in this mode...

[JamminFool]

"So yes, the APS Mode seems to fix the problem, but is only a troubleshooting work-around" - Did Ralph actually say that, or did you decide that's what he meant? I made this change months ago in Jamstix 4, and have just got on with using it. I'm not really seeing what the problem is with running the plugin in this mode...

The actual quote from Ralph was just above that in my post; the part you quoted there was my paraphrasing it.

I felt like Waveform took MUCH longer to shut down when Jamstix was open in this mode. But I may be wrong and attributed it to the wrong cause. I'm not sure.

Take note that this is not a setting in the Options menu of the plugin (and thus meant as a user preference). It is a special mode set in the Manager Tool under the category "Troubleshooting" with an added warning that these settings should only be set when directed by support to do so. So I am assuming it is not the optimal way to run the plugin. And if there is a penalty for running in this mode, it will be paid in all other DAWs also. I would rather avoid that.

I hope that helps.

[DCPImages]

SWAM Audiomodeling Instruments all repeatedly crash when trying to adjust CC association/values.

Waveform 10 Windows 10

David

[fde101]

With 2.3.1.2, MacOS - AU version:

pluginval v0.2.1 - JUCE v5.4.1
Started validating: AudioUnit:Effects/aufx,VMXR,SlDg
Random seed: 0x1eaa971
Validation started: 21 Feb 2019 6:51:14am

Strictness level: 5
-----------------------------------------------------------------
Starting test: pluginval / Scan for known types: AudioUnit:Effects/aufx,VMXR,SlDg...

*** FAILED: VALIDATION CRASHED

0 pluginval 0x000000010a9aefc1 _ZN4juce11SystemStats17getStackBacktraceEv + 65
1 pluginval 0x000000010a8f5754 _ZN12_GLOBAL__N_119getCrashLogContentsEv + 52
2 pluginval 0x000000010a9af0f4 _ZN4juceL11handleCrashEi + 20
3 libsystem_platform.dylib 0x00007fff98eb9b3a _sigtramp + 26
4 CoreFoundation 0x00007fff9e54fde0 __kCFAllocatorSystemDefault + 0
5 Virtual Mix Rack 0x00000001116cb2e8 ACFShutdown + 381496
6 Virtual Mix Rack 0x00000001118f68c8 ACFShutdown + 2656280
7 Virtual Mix Rack 0x00000001119f66e1 ACFShutdown + 3704369
8 Virtual Mix Rack 0x0000000111ad4d43 ACFShutdown + 4615315
9 pluginval 0x000000010a968290 _ZN4juce23AudioUnitPluginInstance20refreshParameterListEv + 5264
10 pluginval 0x000000010a960765 _ZZN4juce21AudioUnitPluginFormat20createPluginInstanceERKNS_17PluginDescriptionEdiPvPFvS4_PNS_19AudioPluginInstanceERKNS_6StringEEEN29AUAsyncInitializationCallback10completionEP23ComponentInstanceRecordi + 2469
11 pluginval 0x000000010a95e375 _ZN4juce21AudioUnitPluginFormat20createPluginInstanceERKNS_17PluginDescriptionEdiPvPFvS4_PNS_19AudioPluginInstanceERKNS_6StringEE + 981
12 pluginval 0x000000010a945b71 _ZN4juce17AudioPluginFormat29createInstanceFromDescriptionERKNS_17PluginDescriptionEdiRNS_6StringE + 945
13 pluginval 0x000000010a95d424 _ZN4juce21AudioUnitPluginFormat19findAllTypesForFileERNS_10OwnedArrayINS_17PluginDescriptionENS_20DummyCriticalSectionEEERKNS_6StringE + 324
14 pluginval 0x000000010a96e74b _ZN4juce15KnownPluginList14scanAndAddFileERKNS_6StringEbRNS_10OwnedArrayINS_17PluginDescriptionENS_20DummyCriticalSectionEEERNS_17AudioPluginFormatE + 1035
15 pluginval 0x000000010a96dfcb _ZN4juce15KnownPluginList29scanAndAddDragAndDroppedFilesERNS_24AudioPluginFormatManagerERKNS_11StringArrayERNS_10OwnedArrayINS_17PluginDescriptionENS_20DummyCriticalSectionEEE + 123
16 pluginval 0x000000010a906901 _ZN4juce14MessageManager16AsyncCallInvokerIZN11PluginTests7runTestEvE3$_0E15messageCallbackEv + 97
17 pluginval 0x000000010a9c3de5 _ZN4juce12MessageQueue18deliverNextMessageEv + 245
18 pluginval 0x000000010a9c3c9e _ZN4juce12MessageQueue21runLoopSourceCallbackEPv + 14
19 CoreFoundation 0x00007fff83096311 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
20 CoreFoundation 0x00007fff8307758c __CFRunLoopDoSources0 + 556
21 CoreFoundation 0x00007fff83076a76 __CFRunLoopRun + 934
22 CoreFoundation 0x00007fff83076474 CFRunLoopRunSpecific + 420
23 HIToolbox 0x00007fff825d4ebc RunCurrentEventLoopInMode + 240
24 HIToolbox 0x00007fff825d4cf1 ReceiveNextEventCommon + 432
25 HIToolbox 0x00007fff825d4b26 _BlockUntilNextEventMatchingListInModeWithFilter + 71
26 AppKit 0x00007fff80b69a54 _DPSNextEvent + 1120
27 AppKit 0x00007fff812e57ee -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
28 AppKit 0x00007fff80b5e3db -[NSApplication run] + 926
29 pluginval 0x000000010a8fc25c main + 348
30 libdyld.dylib 0x000000010b58c235 start + 1

Binary Images:
0x10a8ec000 pluginval
0x7fff98eb7000 libsystem_platform.dylib
0x7fff82ff1000 CoreFoundation
0x111107000 Virtual Mix Rack
0x7fff825a4000 HIToolbox
0x7fff80b23000 AppKit
0x10b587000 libdyld.dylib




The VST and VST3 versions pass validation, but the VST3 version seems to cause some random crashes in Waveform. The VST version seems to be working so far.

[dupont]

micro tonic UI is laggy on OSX

[pauljennings]

just got update 10.0.26
the midi editor no longer changes to drums when set to channel 10
also had a crash for the 1st time in ages
any ideas?

[pauljennings]

also has any one had success with tracktion waveform an uad 2 quad ,all problems i have seen relate to interface issues
i have focusrite claret and would not use the interface side of uad
hoping someone has positive results using the pcie accelerator
cheers Paul.