Hello,
Unfortunately Waverazor for Linux does not work at all. There's no response from the plugin in both Bitwig and Mixbus32C. I use Biotek on a current basis, as well as the DAW essentials, all of them working fine. But Waverazor does not. System is Linux Mint 18 (ubuntu based). I have installed the Waverazor .deb file using 'dpkg -i' and the files are in /usr/local/lib/vst/ as the installation puts them. The path is recognized by both Bitwig and Mixbus32C. See attached. There's was no Waverazor other window shown behind Bitwig.
Looking forward to try Waverazor for Linux !
I have emailed Taiho and Tracktion about this. This msg here is to give a heads up for anyone interested in getting the Linux version at the moment. Please do get it, as I'm sure the problem will be fixed.
Waverazor for Linux
-
- KVRAF
- 3729 posts since 3 Nov, 2015
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 189 posts since 27 Mar, 2014 from Brisbane, Australia
Running Ubuntu 17.10 here and I've tried Waveform 8 & 9 and Renoise. The plugin loads but not a single peep comes out of it.
Making Bitpop music....
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
-
- KVRist
- 82 posts since 25 Nov, 2015 from Berlin, Germany
@mevla - thanks for the report on this, and really sorry to hear about that, I will look into it! I see the email to Tracktion and Taiho and I am guessing they'll send it over to our MOK queue soon. So, it is just hanging during scan? If you remove the WaverazorFX (the one in your screen shot) does the Waverazor virtual instrument just do the same thing then?
@gavindi - Have you registered the plugin? It doesn't make sound until you have registered (you don't need to purchase, just register for the free demo period)
On my side, I have tested in Waveform, Tracktion7, Bitwig Studio, and Ardour, on Ubuntu 16.04... and we had a couple other testers during beta, both were on Ubuntu I believe, so I figured we had it all working well. Will follow up with you @melva via the support ticket.
- Rob
@gavindi - Have you registered the plugin? It doesn't make sound until you have registered (you don't need to purchase, just register for the free demo period)
On my side, I have tested in Waveform, Tracktion7, Bitwig Studio, and Ardour, on Ubuntu 16.04... and we had a couple other testers during beta, both were on Ubuntu I believe, so I figured we had it all working well. Will follow up with you @melva via the support ticket.
- Rob
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Hello Rob,
OK. I removed WaverazorFX and Waverazor loaded. So I registered. Then I've chosen a sound patch, pressed a key on the MIDI keyboard ... and it made a noise ! A nice one at that, 'biodiversity'.
Observations:
1) There's no 'MOK' (or Tracktion) category for the plugin. It falls under generic VST. Not that much of a big deal, although it would be nice if it had a category. See attached.
2) The first time it loaded in Bitwig it took a looong time. At least 60 seconds, surely more as I went doing something else.
3) The first time it loaded, and after registering, it did not made a sound with the default patch. A patch had to be manually selected. After selecting a patch and having it make a sound, going back to the default patch made a sound.
4) Terminating Bitwig and restarting: this time Waverazor loaded immediately and a sound was produced with the default patch.
Cheers.
OK. I removed WaverazorFX and Waverazor loaded. So I registered. Then I've chosen a sound patch, pressed a key on the MIDI keyboard ... and it made a noise ! A nice one at that, 'biodiversity'.
Observations:
1) There's no 'MOK' (or Tracktion) category for the plugin. It falls under generic VST. Not that much of a big deal, although it would be nice if it had a category. See attached.
2) The first time it loaded in Bitwig it took a looong time. At least 60 seconds, surely more as I went doing something else.
3) The first time it loaded, and after registering, it did not made a sound with the default patch. A patch had to be manually selected. After selecting a patch and having it make a sound, going back to the default patch made a sound.
4) Terminating Bitwig and restarting: this time Waverazor loaded immediately and a sound was produced with the default patch.
Cheers.
You do not have the required permissions to view the files attached to this post.
Last edited by mevla on Sat Jan 13, 2018 5:30 pm, edited 2 times in total.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
I've noticed the same the first time it loaded in Bitwig. Had to manually select a patch for it to make a sound. Terminating Bitwig, restarting and reloading, it made a sound the first time around. It is also registered, but that should not matter I believe.gavindi wrote:Running Ubuntu 17.10 here and I've tried Waveform 8 & 9 and Renoise. The plugin loads but not a single peep comes out of it.
Cheers.
-
- KVRist
- 82 posts since 25 Nov, 2015 from Berlin, Germany
That is really helpful info and gives me something to work with to attempt a fix... Thanks!mevla wrote:I've noticed the same the first time it loaded in Bitwig. Had to manually select a patch for it to make a sound. Terminating Bitwig, restarting and reloading, it made a sound the first time around. It is also registered, but that should not matter I believe.gavindi wrote:Running Ubuntu 17.10 here and I've tried Waveform 8 & 9 and Renoise. The plugin loads but not a single peep comes out of it.
Cheers.
-
- KVRist
- 82 posts since 25 Nov, 2015 from Berlin, Germany
Many thanks for figuring that out! I wonder why WaverazorFX was hanging, but glad to hear that you can use the regular Waverazor synth plugin.mevla wrote: OK. I removed WaverazorFX and Waverazor loaded. So I registered. Then I've chosen a sound patch, pressed a key on the MIDI keyboard ... and it made a noise ! A nice one at that, 'biodiversity'.
Agreed, it would be much easier if it were under a mok category. I will plan to do this for the next build.mevla wrote: 1) There's no 'MOK' (or Tracktion) category for the plugin. It falls under generic VST. Not that much of a big deal, although it would be nice if it had a category. See attached.
That is odd... and I don't know what is taking so long. The first time Waverazor loads, it does need to get the patch database created and populate it with entries from the bundled factory presets, that will make the first run slower than subsequent ones, but it shouldn't be anywhere near that slow! -- My guess is that something is taking way too long, again great info, that gives me good insight into where I should go looking.mevla wrote: 2) The first time it loaded in Bitwig it took a looong time. At least 60 seconds, surely more as I went doing something else.
A guess is that this is related to #2, and I need to re-check from a completely clean slate...mevla wrote: 3) The first time it loaded, and after registering, it did not made a sound with the default patch. A patch had to be manually selected. After selecting a patch and having it make a sound, going back to the default patch made a sound.
Given my guess on #2, this would make sense then.mevla wrote: 4) Terminating Bitwig and restarting: this time Waverazor loaded immediately and a sound was produced with the default patch.
Again, really happy to hear that you are able to run Waverazor and I am feeling optimistic now given the great insight/info you've provided. Much appreciated!
- Rob
-
- KVRist
- 189 posts since 27 Mar, 2014 from Brisbane, Australia
Slow to get back to you, sorry...r_mok wrote:
@gavindi - Have you registered the plugin? It doesn't make sound until you have registered (you don't need to purchase, just register for the free demo period)
- Rob
Well as already reported, manually selecting a patch worked for me too.
Making Bitpop music....
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
-
- KVRist
- 82 posts since 25 Nov, 2015 from Berlin, Germany
That is really good to know. Cheers!gavindi wrote: Slow to get back to you, sorry...
Well as already reported, manually selecting a patch worked for me too.
( now back to inspecting lines of code for me
-
- KVRian
- 766 posts since 25 Jul, 2010 from Northern Ireland
I too had the exact same problem as described in the 1st post above, However what worked for me was loading Waverazor in Renoise ( which had no errors ) and when i restarted Bitwig the plugin worked fine.
I should maybe try reinstalling or moving and rescanning Waverazor ( demo for now ) and see if there is any useful info from the terminal or log files if the plugin fails to load again.
I should maybe try reinstalling or moving and rescanning Waverazor ( demo for now ) and see if there is any useful info from the terminal or log files if the plugin fails to load again.