Tracktion Software

mwstl · Post by **mwstl** » Mon Nov 11, 2019 6:25 pm

I recently purchased a bundle that has both biotek2 and waveform pro... I would like to be able to use the biotek2 plugin with other daws here on linux, with ardour and mixbus. The thing is the biotek2 plugin crashes with any other daw that is not Waveform.. As soon as I add the Biotek2 plugin to a track in Ardour, there is a 'segmentation fault' as it is telling me from terminal, ...

The ready-to-run bundles of ardour and mixbus run well (can be used on any Linux), so there can't be an issue with the distribution -- the segmentation fault could also be occurring with the other distributions..

I have other commercial plugins for ardour/mixbus and those plugins do not crash the daw,.. so it definitely has to be the biotek2 plugin that is causing it..

Ardour/Mixbus is a daw that places plugins directly into its real-time threads,

https://ardour.org/plugins-in-process.html
"Why doesn't Ardour offer "plugin crash protection" ?
It is a commonly asked question: why doesn't Ardour offer plugin crash protection in the way that (e.g.) Bitwig and Reaper do?

The answer can be given in two ways, one simple and one very technical.

The Simple Answer
It doesn't scale up to work with large sessions with low latency settings.
....
"

Maybe it is "partially" crashing but anything partial would instead be causing the entire daw to collapse...

please fix this, I'd like to use the biotek2 plugin with other daws on my system..

thanks

Kott · Post by **Kott** » Mon Nov 11, 2019 11:34 pm

The ready-to-run bundles of ardour and mixbus run well (can be used on any Linux), so there can't be an issue with the distribution -- the segmentation fault could also be occurring with the other distributions.

BioTek2 loads in Ardour without crashes in my setup, openSUSE TW Ardour 5.12
what do You use?

mwstl · Post by **mwstl** » Tue Nov 12, 2019 12:05 am

I'm using Debian 10 64-bit with the latest updates...

Kott · Post by **Kott** » Tue Nov 12, 2019 1:01 am

Could You test it on separate hardware or in virtual machine? I haven't Debian installed, only Ubuntu in VM for testing because it is supported distro form many DAWs/pluigns

madrang · Post by **madrang** » Fri Nov 15, 2019 12:29 am

For me, even in Waveform10, BioTek 1 and 2 are failing to load....
And many other Tracktion plugins are loading fine.
All of the DAW Essentials Collection plugins are working.

Waveform 64-bit version: 10.3.6 (Built: 28 October 2019)

Code: Select all

14 Nov 2019 19:19:55  ----- Launched Plugin Scan Process
14 Nov 2019 19:19:56  *** ERROR: Plugin crashed:  /home/madrang/.vst/Tracktion/BioTek 2.so
14 Nov 2019 19:19:56  ----- Launched Plugin Scan Process
14 Nov 2019 19:19:57  *** ERROR: Plugin crashed:  /home/madrang/.vst/Tracktion/BioTek 2.so
14 Nov 2019 19:19:57  ----- Launched Plugin Scan Process
14 Nov 2019 19:19:58  *** ERROR: Plugin crashed:  /home/madrang/.vst/Tracktion/Collective.so
14 Nov 2019 19:19:58  ----- Launched Plugin Scan Process
14 Nov 2019 19:19:59  *** ERROR: Plugin crashed:  /home/madrang/.vst/Tracktion/Collective.so
14 Nov 2019 19:19:59  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:00  *** ERROR: Plugin crashed:  /home/madrang/.vst/Tracktion/BioTek.so
14 Nov 2019 19:20:00  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:01  *** ERROR: Plugin crashed:  /home/madrang/.vst/Tracktion/BioTek.so
14 Nov 2019 19:20:01  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:02  *** ERROR: Plugin crashed:  /home/madrang/.vst/RetroMod/RetroMod LoFreq Classic.so
14 Nov 2019 19:20:02  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:03  *** ERROR: Plugin crashed:  /home/madrang/.vst/RetroMod/RetroMod LoFreq Classic.so
14 Nov 2019 19:20:03  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:05  *** ERROR: Plugin crashed:  /home/madrang/.vst/RetroMod/RetroMod LoFreq Modern.so
14 Nov 2019 19:20:05  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:06  *** ERROR: Plugin crashed:  /home/madrang/.vst/RetroMod/RetroMod LoFreq Modern.so
14 Nov 2019 19:20:06  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:07  *** ERROR: Plugin crashed:  /home/madrang/.vst/RetroMod/RetroMod 106.so
14 Nov 2019 19:20:07  ----- Launched Plugin Scan Process
14 Nov 2019 19:20:08  *** ERROR: Plugin crashed:  /home/madrang/.vst/RetroMod/RetroMod 106.so
14 Nov 2019 19:20:08  ----- Launched Plugin Scan Process

Code: Select all

System Info:
   Ubuntu 18.04.3 LTS (64 bit)
   Kernel Version:  4.15.0-69-generic

Sound Cards:
 0 [PCH            ]: HDA-Intel - Realtek ALC1150
 1 [NVidia         ]: HDA-Intel - HDA NVidia HDMI
 2 [Adapter       ]: USB-Audio - Hercules Rocksmith USB Guitar Adapter
 3 [CODEC        ]: USB-Audio - USB Audio Burr-Brown from TI USB Audio CODEC
 4 [A96             ]: USB-Audio - PreSonus AudioBox USB 96
 5 [X18XR18      ]: USB-Audio - BEHRINGER X18/XR18
 6 [Device        ]: USB-Audio - C-Media Electronics Inc. USB Audio Device
 7 [P7xx           ]: USB-Audio - Plantronics Savi 7xx
 8 [C930e         ]: USB-Audio - Logitech Webcam C930e

CPU:  Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz
RAM:  64335 Mb
Video Card: NVIDIA Corporation GeForce GTX TITAN X
Primary VRAM: 12288 MB

Edit: By using drag and drop i got one of the failing plugins to load but...

Code: Select all

14 Nov 2019 20:51:26  Attempting to load VST: /home/madrang/.vst/RetroMod/RetroMod 106.so
14 Nov 2019 20:51:26  Creating VST instance: RetroMod 106
14 Nov 2019 20:51:26  Crash Location: tracktion_ExternalPlugin.cpp:operator():720
14 Nov 2019 20:51:26  Maintenance took: 1 ms
14 Nov 2019 20:51:26  Crashed
14 Nov 2019 20:51:26  

14 Nov 2019 20:51:26  Thread 0:
14 Nov 2019 20:51:26    ** Plugin crashed: RetroMod 106 (VST)
14 Nov 2019 20:51:26    0: tracktion_ExternalPlugin.cpp:operator():720
14 Nov 2019 20:51:26    1: tracktion_AsyncFunctionUtils.h:handleAsyncUpdate:182
14 Nov 2019 20:51:26    ** Plugin crashed: RetroMod 106 (VST)
14 Nov 2019 20:51:26    2: tracktion_ExternalPlugin.cpp:doFullInitialisation:715
14 Nov 2019 20:51:26    ** Plugin crashed: 
14 Nov 2019 20:51:26    3: tracktion_ExternalPlugin.cpp:initialiseFully:481
14 Nov 2019 20:51:26    4: tracktion_ExternalPlugin.cpp:ExternalPlugin:436

mwstl · Post by **mwstl** » Fri Nov 15, 2019 1:59 am

Here too I have the DAW Essentials and they don't seem to be causing any issues. I got the bundle deal which came with Waveform. Any "micro problems" of a plugin with Ardour/Mixbus will cause a crash because it puts everything to the same context-switch for the application -- the explanation for this is less latency and therefore more DSP processing available for the other plugins on the same track. The ardour team created a document for plugin developers to explain why they will not implement plugin-protection.
https://ardour.org/plugins-in-process.html

On some daws maybe there is a bit of plugin protection, but any micro problem from plugins would cause the whole daw to crash. I filed a bugreport on this plugin to mixbus, but they're calling it a plugin issue, so I am back here again on the kvraudio forums. Since they are confident that the problem is not the daw, I suppose then it is likely the plugin..

Other tracktion effects plugins work without issue, it is just Biotek2.... this is another reason why I think it can't be the daw...

The crash is happening with the latest version of Debian 10 64-bit with the latest updates(backports attached).. I suppose the same issue would be happening on other distributions (and for Ardour/Mixbus), because I am actually using non-distro specific run bundles.
..and these run-bundles are meant to be equally stable on any distro that uses them.

Using only the official ready-to-run bundles::
Ardour-5.12.0-x86_64.run
Mixbus32C-5.2.191-x86_64-gcc5.run
-- install paths would be in /opt/Ardour* and /opt/Mixbus* places, .. completely out of the way of getting interfered by any other packaged software, etc.

I know there are ardour packages that are not maintained by the ardour-team, but here I am using the "official" ready-to-run bundle from ardour.org. So now I got that out of the way, I can say that I'm not very optimistic in trying other distributions to test Biotek2 in other distributions right now, and hope staff can see our reports on what works/what doesn't...

Here I'm not seeing those errors of Biotek2 in Waveform10 as @madrang is mentioning. The release of waveform "pro" that I have here is version 10.3.1 to be more specific, maybe he is using a different release of Waveform.

I'm starting /usr/bin/Waveform10 from terminal and see jack connect messages but no errors with Biotek2 when I add it to a track...

I did this even though I have no issues of Waveform+Biotek2, as I was just seeing if there were any micro-problems that may surface in Waveform's output. So far as I can tell there aren't any..

gavindi · Post by **gavindi** » Sun Nov 17, 2019 1:06 am

Nothing new to add here but I wanted to be counted in the Biotek2 crashes just to help show it effects +1 people.
I've very recently done a fresh install of Ubuntu 19.10 since I built a new PC and this is happening without all the baggage of an old install with software cruft everywhere.

Kott · Post by **Kott** » Mon Nov 18, 2019 2:02 am

That's sad. Waveform is "Tested on Ubuntu 18.04" while BioTek 2 is "Tested on Ubuntu 16.04".

mwstl · Post by **mwstl** » Mon Nov 18, 2019 7:12 am

not to be rude or anything, but Waveform 10.3.6 is a "beta", you guys should be reporting issues of it over here --> viewtopic.php?t=533843

Here I'm not using the Waveform beta, but a purchased production release of 10.3.1..

gavindi · Post by **gavindi** » Mon Nov 18, 2019 7:46 am

Actually, to be pedantic, it should all be in the bug tracker but we all know how forums get misused.

mwstl · Post by **mwstl** » Mon Nov 18, 2019 8:53 am

title now includes "[Ardour/Mixbus]" to place emphasis of the Biotek2 plugin crashing the Ardour/Mixbus daw..

I should of included it as part of the title when initially creating the topic.

Tracktion Software

KVR Audio

biotek2 plugin segmentation faults [Ardour/Mixbus]