Request for native Linux Support

[urlwolf]

+1. Would buy diva for linux straight away...

[pc999]

I am getting pretty close to Linux too, lately,

Bitwig and/or others may very well get me a fulltime linux user, it would be very nice to see ACE and other plugs in a native linux version.

[pc999]

Just to point that Tracktion will be joining Linux too !

And it seems that Reaper devs have something in the works (started almost as long as this thread ).

[fedexnman]

+1 Linux

[masterhiggins]

I guess that I'm in the minority of users that just wish for them to focus on the two main established OSs rather than divert r&d and funds to superserve a small base of users and driving up the cost for everyone else. If u-he can magically keep the cost the same than I'd say have at it. But I'd say seeing as how there hasn't been any official news that the plugins are being ported to *nix, it probably reflects on their priority (and demand) to actually do so. My 2 cents.

-Sam

[Urs]

Well, we did a few things to make them work better with Wine, i.e. Receptor.

I have no idea what a full fledged Linux port would entail, and atm we have more pressing issues (AAX, Satin, Bazille, Diva 1.3, Zebra3). The three main problems with platform support are mousing, drawing and file system access. The drawing side is getting easier since we're doing more and more of it ourselves and leave less to the system. But even then it sounds like a major job.

[ras.s]

^
There's a crazy possibility with Linux that no developer has taken advantage of yet. That is, imagine tailoring the operating system to run only your software, then installing that OS on a tablet, then taking that tablet on stage. It would be the hardware for the software.

Now THAT sounds like a major job, but might be something truly fantastic .. Put it in your thinking cap ..

[wasi]

^
There's a crazy possibility with Linux that no developer has taken advantage of yet. That is, imagine tailoring the operating system to run only your software, then installing that OS on a tablet, then taking that tablet on stage. It would be the hardware for the software.

You can do this with Renoise under Linux. Set Renoise as your session's window manager and boot straight into Renoise. No tailoring of the OS required, aside from creating a new user session category and assigning the window manager.

Also not much gained over just booting your regular OS and running it though. But it's still cool in a geeky way.

[pc999]

Well, we did a few things to make them work better with Wine, i.e. Receptor.

I have no idea what a full fledged Linux port would entail, and atm we have more pressing issues (AAX, Satin, Bazille, Diva 1.3, Zebra3). The three main problems with platform support are mousing, drawing and file system access. The drawing side is getting easier since we're doing more and more of it ourselves and leave less to the system. But even then it sounds like a major job.

Mousing really?!?!

I would suggest that any new code is as OS agnostic as possible, not only would make future transitions easier, but also a possibility of new platforms.

I imagine that when ARM is powerful enough there will be lot of user wanting stuff for, not only Ubuntu, but android, or even Jolla shelfish.

[Urs]

Mousing really?!?!

Windows, MacOS and Linux offer different event models - I call it "mousing", but there's more to it such as timers, window events, key strokes. The layer between this and our code can not be platform agnostic. One can "wrap" this using 3rd party libraries, but those often evolve quicker than OSes, so there's actually more work to kep them alive than to write our own layer. Hence we write our own layers.

[pc999]

Mousing really?!?!

Windows, MacOS and Linux offer different event models - I call it "mousing", but there's more to it such as timers, window events, key strokes. The layer between this and our code can not be platform agnostic. One can "wrap" this using 3rd party libraries, but those often evolve quicker than OSes, so there's actually more work to kep them alive than to write our own layer. Hence we write our own layers.

Thanks, that really interesting.

BTW (rereading my post it may look like that but I) didn't meant to say how to do your work, just that lately I have seen many developers having to work much harder for multiplatform releases of established products, from FLStudio to Digital Performer to open source Linux software ( http://www.openshotvideo.com/2013/04/de ... funds.html )

Just to make sure you guys keep around and setting a high benchmark for synths! Even if I am not using them on Linux.

[abique]

I could port them on Linux. Anyway if they pop on Linux, I'll buy them.

[danboid]

+1 for Linux-native Uhe plugs!

The growing amount of people unhappy with Windows direction combined with the continual improvement of Linux, the increase in (semi) pro DAWs for Linux (Bitwig, Tracktion, Renoise, Mixbus, EnergyXT, maybe REAPER soon...) and the dearth of pro-quality plugins for Linux (I count a whole 3 commercial plugin vendors who support Linux) SHOULD make this a no-brainer!

[abique]

Windows, MacOS and Linux offer different event models - I call it "mousing", but there's more to it such as timers, window events, key strokes. The layer between this and our code can not be platform agnostic. One can "wrap" this using 3rd party libraries, but those often evolve quicker than OSes, so there's actually more work to kep them alive than to write our own layer. Hence we write our own layers.

Do you use directly Windows and Mac API or a portable layer?
People seems to be happy with Qt or Juce.

[Burillo]

that's actually exactly the problem with Linux. with Mac or Windows, they have different events systems, but at least they have *ONE* event system and *ONE* way of doing things that's guaranteed to be supported on any system. with Linux you're forced to either support multiple (GTK and Qt/KDE, maybe something more exotic), or shut yourself out of one of the markets. granted, software works in different environments, and audio plugins probably have less problems with feeling native on the OS since UI's are completely custom in the first place and the rest is provided by the DAWs, but still there's two popular UI toolkits and desktop environments (and quite a bunch of not-so-popular ones), there's a few DSP plugin formats (VST, LADSPA, LV2), and, most importantly, lots of distributions that are slightly (or substantially) incompatible with each other for no apparent reason, with different versions of desktop environment, or different versions of libabc and libxyz (or worse, libabc compiled with different compilation flags), and the kernel and the sound drivers, and with or without JACK or realtime kernel support, or this, or that. in other words, while i would love to see some great quality Linux plugins, truth is that for a developer, unless your target market is other developers, Linux is a nightmare.