LinuxMusicians

Luc wrote: I consider these sarcastic comments rude and pointless. Zero contribution to anything at all.

It did sound that way indeed. However, I would say too that using a platform to run software native for that platform does seems like the most straightforward solution, unless:

• You can't.
• You don't want.

Each one of the above is a good reason. And I get your point about wine developers entirely: they work hard to give us a compatibility layer. They should be rewarded for that really.

As for being actually constructive, I am afraid I will be of little use since a lot of time passed since I last tried to run windows plugins. Nowadays I typically run videogames with wine (like Doom3... for some reason it works better through wine that natively on my machine). If I cannot use wine I usually setup a free windows virtual machine for the task at hand. I used virtualbox in the past to do some not-realtime audio editing and mastering. It sort of worked alright... Of course, if that is not what you need, a virtual machine will be pretty useless to you...

42low wrote: I have linux so use linux build software, and if i want/need win software i will run that under win. I would never combine two systems because that would bite each other.

If you don't use a system with ancient software, like Luc is, then it's really not that much of a problem.

FWIW, I take a pragmatic approach instead of a religious one.

I got into reaper because I liked the routing and many other things, once I realized that I could run it on wine/linux (7-8 years ago) I was on linux.. I've had experience with many OS', and never really liked windows. I think that linux/kde is the bee's knees for a customizable desktop.. Maybe some other WMs too, depending on the application.

I see wine as a dynamic lib, similar to gtk+ or others. I download a plugin (binary blob) for my platform and at runtime it gets to call the functions it needs, that's all.. Sure it doesn't always work as it should, which means I can't run all of them. There is also the question of running them at really low latency, which can be a bit of hit and miss.

I am however convinced of the concept working, afai'm concerned it's just a question of programming hours until it works perfectly. It will probably always have a cost in cpu runtime, due to context switches, but machines get faster..

In the end I just see it all as tools, if they work fine and I can use them to work/play with audio I use them. and if not, I don't...

A wrapper like LinVst works very well for me, at least with most plugins and at mixing latency.

Luc wrote:Qtractor runs Windows/Airwave, but it completely chokes on my large collection of plugins. Whenever I try, I have to kill it. So I can't rely on Qtractor.

latest git head master--coming soon as qtractor v0.8.4--might behave a lot better in this regard.
if you don't want to wait just grab the latest build snapshot from my OBS repositories

stay tuned, don't despair

Jack Winter wrote:In the end I just see it all as tools, if they work fine and I can use them to work/play with audio I use them.

Yes. Yes. Yes...

rncbc wrote:latest git head master--coming soon as qtractor v0.8.4--might behave a lot better in this regard.
stay tuned, don't despair

Great news!

Sadly, qtractor will not be the answer.

I just tried it. Without any Windows plugin. I swear, just native LV2 plugins.

I lost count of how many time qtractor crashed. Once for adding a plugin, then another for adding a synth then loading an sf2 file, then another sf2 file, then switching banks in amsynth, then adding another plugin, then something else... I lost count really.

Even worse, the plugins launched in full screen mode - that may be from my Openbox configuration, but had never happened before - then I would restore them and continue, but zynaddsubfx froze the screen completely, so bad that I had to open another tty and kill openbox entirely and restart my whole session from scratch. That happened twice.

How does anyone put up with that? If it's going to crash that often, I'll just stick to Tracktion.

Oh man, this sounds way more than a misconfiguration of your setup than a problem with the daws themselves.
If ALL daws give you that much trouble, something has gotta be wrong.

Load up a avlinux live iso and try to replicate the issues to rule out software misconfiguration.

rghvdberg wrote:Oh man, this sounds way more than a misconfiguration of your setup than a problem with the daws themselves. If ALL daws give you that much trouble, something has gotta be wrong.

Oh yeah? So you're telling me that Tracktion only crashes on me? Really? Are you really making that bold statement? Do you ever hang around forums?

Then I suppose Windows plugins run over Airwave work just fine in Ardour, and THIS is a figment of my imagination. Maybe my Fight Club alter-ego posted that issue report on github?

Of course, I must have dreamed that Bitwig refused to work until I installed and pinned an old version of ffmpeg, and version 2.0 refused to work in a brand new fresh installation of Debian, where every other audio application ran just fine. In my wildest dreams, there are even emails from Bitwig refusing to provide support sitting right here, in my mailbox. I must be on drugs.

I've been smoking pot so potent that I even imagined that rncbc came along and posted to this very thread and... (gasp) acknowledged the specific problem with qtractor I had described.

Misconfiguration, indeed.

Far out, dude. Far out...

Oops. Derped with buttons. Reply further on in this thread.

Pro tip : get some popcorn

Luc wrote:... I even imagined that rncbc came along and posted to this very thread and... (gasp) acknowledged the specific problem with qtractor I had described.

yes i've kind of acknowledged the old vst scanning problem but NOT any other of the new ones. sorry.

rghvdberg wrote:Dude. Really.

42low wrote: I'm glad to observe that I am not the only one who seems being unreasonably approached. I really thought that i made a huge mistake which made me misunderstood wrong.

Chill Luc. Relax.

You can't expect someone to still be "relaxed" when most replies from the very start to them are confrontational and/or rude.

Oh damn wrote a lengthy reply. Pressed wrong button.

Long story short : bugs, crashes and reproducible? File a bug report with backtrace. Devs love that shit.
Only way to get things fixed. Complaints on forums hardly help.
rnbc is one of the very few devs who are on the forums.

I guess I'm telling nothing new here but ok.

And again man, if you REALLY need those windows plugins and you can't find a way to make it run properly on Linux. Just use Windows then. Makes perfect sense to me. Nothing wrong with that.

Oh and where's the harm of booting avlinux? Just try it.

Oh my. Lots of responses since editing my post.
Luc, It's OK to be frustrated.

I'm not mad. (bit crazy maybe)

rncbc wrote:

Luc wrote:... I even imagined that rncbc came along and posted to this very thread and... (gasp) acknowledged the specific problem with qtractor I had described.

yes i've kind of acknowledged the old vst scanning problem but NOT any other of the new ones. sorry.

In no way should rnbc have to apologize.
He's the author of many great apps and is a great asset to the Linux audio community.
What the hell have you done Luc? Show me you apps, show me your bug fixes, show me your talks al LAC..

I'm very sorry all of his free and opensource software doesn't work perfectly on you computer.

Bye.

Everyone. Let's give Luc some time out to think about what he did.

Now I'm mad.