Xite drivers for linux ?

[spacef]

never know...

Now with more and more people switching to Linux to get away from Microsoft /apple (linux share rising since recently), and being in the same mood, I realize that Xite is one of the few things that would keep me attached to windows. The rest is linux compatible (many plugins and daws too).

I don't hope for Linux drivers (or do I ) and wanted to know if there are ways to make those drivers work on Linux.

Anyone tried ?

[Bud Weiser]

Running Scope standalone on a Linux machine would be a good option,- as the one and only DAW machine w/ ASIO possibly not so much since most native plugins (and bundles,- think NI, Arturia etc.) and DAW apps don´t run on Linux up to now.



Bud

[valis]

Bitwig runs on Linux.

[Bud Weiser]

Bitwig runs on Linux.

Yes, Reaper does too,- but the other big ones don´t,- Logic, Cubase, Nuendo, Studio One, Reason.
And the bundles won´t too, NI Komplete (Ultimate, UCE), Arturia keys and FX Collections, KORG Collection etc., etc..

Most of us already own such products and it would be insane leaving ´em in the dust just only for Linux.



Bud

[sunmachine]

Yes, Reaper does too,- but the other big ones don´t,- Logic, Cubase, Nuendo, Studio One, Reason.

There's a public beta version of Studio One for Linux.
See here: https://support.presonus.com/hc/en-us/a ... ng-Started

[nebelfuerst]

I sometimes used bitwig under linux. One advantage is, that you can use RME-cards, which don't offer a W10 driver anymore.
As I also need melodyne, W10 dominates over linux.
Scope under Linux would be great, if the low level driver comes as opensource. This ways you can hunt some bugs on your own.
Binary blobs (like some board manufactures provide) suck, as they are obsolete within a few months.

[valis]

My Multiface 1 & 2 are both still supported on Win10 with current drivers, which means the PCI HDSP and PCIe HDSPe

[Bud Weiser]

... under linux... you can use RME-cards, which don't offer a W10 driver anymore.

Which ?
In addition to my RME Raydat and Babyface,- I still own RME Hammerfall (non DSP !) Digi 9636 and Nuendo branded Hammerfall Digi 9652.
These usualy work using the "Win2k_211" driver for Win XP, which is the latest release.
It´s confirmed to work in Win 7 32Bit too, w/ the restriction the windows mme drivers won´t work, but ASIO does.

So, you say, this driver works w/ current Linux version(s) too ?



Bud

[spacef]

Yes the offer is scarce and many plugins would be lost but many would work.
I still use a bit of NI, Arturia etc and would be less confortable to do without them, but it does not mean it won't happen if there is a market for those companies. I've read that Linux adoption is rising slowly since windows 11 and microsoft AI and marketing plans. Windows 10 still has a few years until 2035 I think (with payment after 2027 or so).

I've read that Linux has windows emulators or VM, may be they run with hardware drivers and without using too much ressource... I have no idea. I guess I should try on a dual boot drive one day...

would be great though. I imagine it is easier to port to Linux than Mac (the scope app itself) but again, I don't really know what needs to be adapted to linux.

[valis]

Tbh, I wouldn't run linux for commercially available software, at least not that much.

I would also prefer v8 before linux binaries that work.

[Bud Weiser]

I would also prefer v8 before linux binaries that work.

Bingo !

Reality check:

We don´t see much or fast Scope developement since years now and a re-write of Scope ASIO- and Wave- drivers needs years meanwhile.
It´s a very small team and Holger gets older too,- like me.
When updating Scope alone already is a herculean task, porting all over to Linux might be a lot more and needing endless time.

So, in my age, I´m now humble and still hope for the new driver than dream from "all new Scope" or "Scope v8".
In fact,- better total recall, perfect working memorized MIDI CC assignment on device level and "those" 64Bit bug fixes are what I still hope for.
A Scope v7 w/ these fixes and optimizations is possibly the most realistic scenario,- if at all.

And, I´m so old now I don´t care about what happens to Windows or MacOS in a few years.
I dunno if I´ll be still alive or make music anymore then.

And since AI enters almost all of the average music services in no time now and will get better and better doing this, I wonder how many "idealists" will be left over investing their cash in "hi-tech" (home-) studios.
Live gigging "as long as you can",- for a small fee by nature,- might be the only way being "active" in future,- w/ the exception of the big global players (also in the sense of live acts !).

And all this is also not a good sign for the MI.

YMMV ...



Bud

[Bud Weiser]

I've read that Linux has windows emulators or VM, may be they run with hardware drivers and without using too much ressource... I have no idea.

Linux runs in many hardware instruments already,- see Yamaha Montage M, which is one of the latest devices running on Linux.
It seems to be relatively humble on CPU when "specialized" and when running on the ideal processor(s).
It also seems, ARM is one of these processors, but up to now I have no knowledge about if a SHARC belongs to that "family" too.

But for the usual DAW usage w/ so-to-say "stock" PCs / PC components, Windows Emulator (WINE) is needed.
In fact an additional layer emulating a Windows registry,- otherwise native VST plugins cannot run.
We´ve already seen in the tiny SM Pro Audio VMachine running VST plugins on Linux.
Well, just only a 1GHz machine w/ 500MB of now "slow" RAM.
But has a good audio interface where VMachine optimized Sonic Projects 32Bit "OP-X" or alternately "Stringer" and 2 humble delay & reverb plugins seem to run best and still sound great,- which is at least my experience w/ this machine which I still own and can use on demand.

I only know,- any additional processes need CPU cycles and time too,- and that also rules for WINE.
Well, there a dedicated plugins developed for Linux,- but these most often aren´t on par w/ the cohortes of native VST/AU plugins, their standard being developed and existing since about 20+ years now.

The CLAP plugins might change something,- when being standardized.
But also there, not everything is like I hoped for.
Some behave like VST3 plugins and don´t allow usage of MIDI PrgChanges p.ex..
Why ?
I hoped for FULL MIDI implementation and more (MIDI 2.0),- but again, everyone does ... more or less ... his own thing.

Conclusion:
I can imagine nothing will change significantly in my life anymore and the grass won´t be greener on the other side "very soon".
So, I better use "as it is" what I have already and don´t dream too much.



Bud

[nebelfuerst]

More detail on my RME statement:
I own Digi96 and HDSP cards. Using Bitwig under Linux, the Digi96 works like charm, but the HDSP adds some crackling noise. This noise is correlated to the buffersize selected in Bitwig, but it cannot be removed.
The same machine is also used with W10. So I cannot use the Digi96 because of lacking Windowsdrivers, but the HDSP suxx under linux.
As I have some knowledge in software, I can look into the sourcecode of the hdsp-driver and do some expriments to fix this issue.
(I didn't succeed yet, but the level of motivation to get it working is not on an urgend level, yet
For a scope-driver under linux, priority would be top .

[valis]

That's a linux issue, not a driver issue. I have the same problem in many other linux applications, a fixed buffer of 512 samples is set unless *both* the driver and *software* have a flag set to allow other sample buffer sizes. For instance on the Raspberry Pi you almost always need either Pisound or another Pi specific hat, for most USB "class compliant" drivers will act as you demonstrate.

I have had the same issue on desktop with my PCI HDSP (Hammerfall) card that my Multiface I connects to, but the Multiface II does not. The former dates back to 2003, the latter to 2007. So 20 year old drivers and soundcards, yes your mileage may vary. The PCIe variants of other RME cards are going to be the same, they will work where the legacy cards will be limited to "class compliant" operation.

Using a 512 sample buffer size usually solves this, as would getting a used card off ebay/reverb/etc.

[nebelfuerst]

Not sure, if it's linux. Other apps like audacity work flawless. Maybe bitwig uses some extended feature.
My idea was to make the HDSP-driver "stupid", but I didn't succeed yet.

[astroman]

I‘ve had really good results running the Crossover flavor of WINE on a MacMini M1 (Monterey).
SAW Studio performed exactly like my 3 Ghz i5, even visually, no flaws as experienced in previous versions.
Which was surprising, as the Rosetta translator from X86 to ARM was active (of course) and it was an early release.
Latency wasn‘t a problem, probably due to a thing called WINE Core Audio.

Imho it might be a rather compact process a to make the XITE „visible“ in that environment, opposed to PCI cards.
Of course you have to deal with evil Apple...
I‘m not amused about some of their hardware/security features myself.
Atm using a Motu 828 USB with the Mini, which is completely hidden from the system unless one reduces global security level.
Only then the (rather old) Motu kernel extension is loaded, but some websites will trigger „security alerts“ and refuse service
(that‘s my only complaint about Monterey in 2 years)