Is there a reason why I am receiving no answer to Support ticket#: 3615 Tracking ID: SVZ-XSY-XN2Z ?

Official support for: bluecataudio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

The question is pretty much in the subject line:

Is there a reason why I am receiving no answer to Support ticket#: 3615 Tracking ID: SVZ-XSY-XN2Z ?

I put a ticket in, requesting information on what best to purchase, on: 2025-08-14 17:36:34

I haven't heard anything back at all. Not a single peep. This is VERY unusual for Blue Cat Audio, who is always very helpful and prompt. Is there some holiday going on over there? I don't want to be impatient if there is something going on. :) I'm just a bit surprised and concerned. :)

For the curious, this is what I asked:

Hello,

I have some questions about using your products. I currently have Patchwork, and I am determining what else I need to buy (ie Connector and/or FaderHub).

I use Linux. I've messaged you guys before, and you have told me that your software should be able to work ok with WINE. I have some things that I want to try to see how well they work as solutions. Here's what I am trying to do:

As you probably know, Linux doesn't have a lot of pro audio software. More and more developers are supporting it, but I still have some very niche plugins and software that I need that Linux does not have in native binaries. I am hoping to be able to use your products to bridge that gap. Because WINE is more efficient than virtual machines, I will be trying to run most of what I need through WINE and WINEASIO (or the ASIO driver that comes with connector). For any remaining applications that I can't get to run sufficiently on WINE, I plan to use a virtual machine (Windows 11) as a guest OS on my Linux OS (host).

My current thinking is that I could run an instance of Patchwork in the Windows virtual machine, and an instance of Patchwork in WINE, and send the output to a windows host in WINE that connects to Pipewire-JACK through WINEASIO (or connector's ASIO driver), and connect from that host to my Linux DAW (Reaper - Native Linux version).

I'm wondering if Fader Hub would be a good solution for receiving the audio from the two instances of Patchwork. Would I still need Connector if I was communicating between PatchWork and FaderHub?

Also, can FaderHub handle two ASIO devices? For example, I would need FaderHub to connect to WINEASIO so that it can be connected to JACK and routed to my Linux Reaper DAW that would be using JACK.

Or, would I need to connect FaderHub to the WINEASIO Jack connection, and then I would have to use Connector inside of FaderHub to route the audio from the two PatchWork instances to FaderHub?

Or maybe I'm not understanding everything. What do you think would be best to set up this kind of topology, all on one machine?

Can FaderHub save configured settings as a preset so that I can recall it without having to set it all up again?

I know this is a lot of questions, and I know that it isn't officially supported, but I would really appreciate your guidance and opinion on all of this.

Thank you,

xxxxx
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
:roll:

Post

Hi,

Sorry for the delay! There have indeed been a few days off lately, and quite a bit of emails/tickets, but I'm still alive and kicking. I have replied in the ticket! But we can also follow up on the forum when we have a working solution to share it with others!

I have personally tried to setup a working Linux real-time workstation running Windows apps a few months ago but gave up because of WINEASIO issues and other way too large latency. So if we can come up with a setup that works, I would be happy to get rid of a couple of old Windows 10 installs...

Post

Thank you for getting back to me!! I figured something must be going on, because you guys have always been so helpful and quick to respond! :)

I did indeed see your email this morning, and I did respond there as well. I love the fact that you guys are so open to assisting us with getting your products to work in harmony with WINE on Linux!!

I pointed out briefly (in my ticket) that there are a couple of well known bridging projects that allow Windows VST instruments and effects to be seen and used by Linux DAWs as if they are Linux native VST plugins. A change in WINE broke these tools a couple of months ago, but they’ve almost got it fixed. We’ll soon have these tools working again. This is the easiest solution for Linux users. WINEASIO is (in my opinion) a great secondary method—which is again being supported and updated by FalkTX in his repositories and on GitHub. You ought to join LinuxMusicians.com. We’d love to have you there, and we would be happy to help you with any Linux testing or experimenting you might want to try. I’m quite confident you would have had a better experience with your testing of Linux if we were helping you. :)
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
:roll:

Post

Thanks for the info. Glad to see that WineASIO is back! I have a couple of old Windows10 machines I'd like to convert to Linux workstations. I'll check out LinuxMusicians.com too!

Post Reply

Return to “Blue Cat Audio”