08-18-2022, 07:56 PM | #1 | |||||||
Human being with feelings
Join Date: Feb 2008
Location: Westgate-on-Sea, Thanet, Kent
Posts: 523
|
Behringer. Gah! Grr! (SynthTribe/Wine etc)
I've exchanged many an email with Behringer about the usual.
This is my most recent exchange, after asking why I can't connect to the SynthTribe cloud from Win10Pro in VirtualBox. Quote:
Quote:
Quote:
Quote:
__________________
Dave - formerly Socket Using Linux Reaper in Ubuntu Studio Website | YouTube | Facebook | Soundcloud |
|||||||
08-18-2022, 09:49 PM | #2 |
Human being with feelings
Join Date: Mar 2017
Posts: 861
|
The harsh reality is that companies who struggle just to support the status quo of two very different operating systems amidst strong competition, don't have the budget to support a third OS with few potential customers, and then a subset of the few attempting virtualization.
You might want to take a look at BlueCat's 'Connector' https://www.bluecataudio.com/Product...uct_Connector/ which is designed to bridge the chasms people often face. I use their Accoufiend and Axiom amp-sim-effects suite in linux, no weirdo registration schemes etc. Cheers
__________________
Songs I've made with linux and Reaper, a qwerty forehead danger zone: https://www.youtube.com/watch?v=NtlO...RvGI8-_TqqZ7ij https://franklincheney.bandcamp.com/ |
08-19-2022, 02:02 AM | #3 |
Human being with feelings
Join Date: Feb 2021
Posts: 2,288
|
I feel for you, I really do. However, it is just a fact that they have no obligation to cater for Linux or Windows in a virtual machine even if they had the budget to do so (coming from a slightly different angle than 4duhwinnn). It's like if I wrote to a Win/Mac only VST plugin company and complained that their EQ doesn't work in yabridge or, if a company's audio interface's DSP wasn't controllable in Linux. Yes, it's incredibly frustrating and maybe, just maybe, I might be able to plant a Linux seed in their minds, but I don't consider it "unacceptable". To use 4duhwinnn's term, it's just the reality of things.
__________________
ReaClassical -- Open Source Classical Music Editing Tools for REAPER | Donate via PayPal, Liberapay or Stripe airwindows JSFX ports | Debian & Arch Pro Audio Guides |
08-19-2022, 07:52 AM | #4 |
Human being with feelings
Join Date: Feb 2008
Location: Westgate-on-Sea, Thanet, Kent
Posts: 523
|
Sorry, it's not clear from my post that the Synth Tribe software works fine in the VirtualBox apart from connecting to the cloud for firmware updates.
That's the only bit that doesn't work. Personally, I think they should be available as SysEx anyway.
__________________
Dave - formerly Socket Using Linux Reaper in Ubuntu Studio Website | YouTube | Facebook | Soundcloud |
08-19-2022, 02:48 PM | #5 | |
Human being with feelings
Join Date: Nov 2011
Posts: 973
|
Quote:
Another possibility is that you could try to communicate with WINE. Unlike Virtualbox (which I haven't used in quite a while since I prefer KVM/QEMU), I know of several Linux using musicians that have successfully used midi through WINE. If any of this has already been said, then I apologies in advance. Edit: So the only part that doesn't work is the cloud? Is it trying to use the internet? Maybe you need to try a different hardware network device. Maybe you could run into something more compatible... If that doesn't work, consider looking into the following virtualization stack that I like: * NOTE: this method I'm mentioning is much faster than Virtualbox, and isn't too much more difficult to set up, but because it follows the Unix software principle of "do one thing and do it well", you have a separate "stack" of tools to accomplish the same thing that Virtualbox does. Also, your system needs to be a vPro compatible platform. This is because this virtualization method works directly with these components of your hardware. The stack of apps is: * Xwayland (or x if you aren't using wayland) * KVM * QEMU * LibVirt * Virt-manager * virt-viewer * Spice Edit #2: I just did a brief check of virtualbox and it looks like there are now USB solutions that weren't around the last time I used it. But then again, you mentioned that the problem you are having is with the cloud, so I suspect a network compatibility problem. Either way, aside from just Virtualbox, there are some other options to consider and try (as mentioned above). Last edited by audiojunkie; 08-19-2022 at 03:05 PM. |
|
08-22-2022, 09:05 AM | #6 |
Human being with feelings
Join Date: Jun 2009
Location: Wuppertal
Posts: 213
|
Yes, maybe a network problem? The default network for VirtualBox is a NAT network. I would try a bridged network. The bridged network will give your VM a IP from your internet router (DHCP) and this IP is visible/routable from your internet router.
https://docs.oracle.com/en/virtualiz...kingmodes.html Last edited by swindus; 08-22-2022 at 09:18 AM. |
09-19-2022, 08:24 AM | #7 |
Human being with feelings
Join Date: Sep 2022
Posts: 1
|
Today I would like to share how I solved this problem. In the last two years I had the same problems trying to update my Behringer Crave and also my Behringer Brains with a Windows 10 in a virtualbox on a Linux Host.
Last weekend I did my yearly "lets try it again" and after I found out nothing changed on the Behringer side (even the version of Sythtool is still 2.5.7) I tried a different virtualization tool. And that did the trick. I downloaded the VMWare Workstation Player and installed a Windows 11 Developer Evaluation VMWare Image (https://developer.microsoft.com/en-u...tual-machines/) As before mentioned by another user I also had suspected the network layer as a root cause of the problem. In virtualbox I tested NAT and bridged mode without success. The VMWare default is also "NAT", which led to the exact same error message. Then I tried the bridge mode (with the checkbox enabled "Replicate physical network connection state") and that finally worked. For the bridged mode I additionaly had to execute the command "sudo vmware-netcfg" to choose the correct "Bridged to" device. |
09-19-2022, 04:06 PM | #8 |
Human being with feelings
Join Date: Nov 2011
Posts: 973
|
Interesting! It makes sense, since the Virtualization in Virtualbox and VMWare are different. It's even possible that KVM/QEMU may work as well, but one would have to try it to find out.
|
Thread Tools | |
Display Modes | |
|
|