LinuxMusicians

runiq wrote: ↑Fri Oct 13, 2023 7:08 am

Judging by the rest of the supported devices, I wouldn't hold my breath, to be honest…

WTF is that supposed to mean?

Interesting, looks like a feature packed release. I hope they extend the launchpad support beyond the new ones - I do need to upgrade my mk2 but would be nice to have that supported as well. No plans to implement support for the old ones. Someone with a bit of code familiarity will likely be able t...

There is not a single bug report about this in the Ardour issue tracker, except one from Unfa that has been resolved subsequently thanks to JUCE fixing a bug in their toolkit. It is entirely possible for a plugin to be at fault yet crash in only a single DAW (just as it is possible for the same bloc...

An increasing number of plugin devs now use JUCE to do their work. JUCE means they can generate plugins in a multitude of formats, include VST2, VST3, LV2, AU, etc. with almost no extra work. Adding CLAP to the things that JUCE supports will do almost nothing to see more plugins available on Linux. ...

as all efforts made to CLAP will benefit to us (more DAWs/plugins/users). The fact the CLAP could be used on Linux isn't going to do much to get Izotope (for example) to release plugins for Linux. VST3 is already designed with Linux in mind, and although it has resulted in a small increase in the r...

Right, excellent point. That's just a MIDI connection and the audio I/O side of things is not (as) relevant there. Sorry I forgot about those devices

If they are other JACK clients, then you'll have to use JACK. If they are plugins, they run inside Ardour, and you don't have to do anything (this is one of the big reasons why DAW+plugin approaches are so much easier for most users). If they are neither plugins nor JACK clients, then (a) I don't kn...

I cannot answer your question about Ardour since I do not use it (I've that read new versions of it output project files that are not compatible with old versions. NO WAY I'm gonna produce files that I can not easily use in a few years/versions). We work hard to ensure back-compatibility, even back...

Ardour and JACK are intended to be used for professional audio & music creation workflows. In such cases, control of the audio interface hardware needs to belong to Ardour (or JACK), and it should not be available for arbitrary use by random desktop noise-making. Consequently, both Ardour and JA...

I haven't noticed any of your bug reports on tracker.ardour.org, or any presence on discourse.ardour.org or IRC. Did you expect us to fix or know about every single plugin issue, without anyone reporting them? Did I overlook those bug reports? I'm not a regular user of Ardour, so I didn't report th...

I haven't noticed any of your bug reports on tracker.ardour.org, or any presence on discourse.ardour.org or IRC.

Did you expect us to fix or know about every single plugin issue, without anyone reporting them? Did I overlook those bug reports?

It isn't intentional, but is a side-effect of the (old) version of Mantis we use. We allow (and intend for) "reporters" to close their own issues. But in the version of Mantis we have, there's nothing to limit that to their own issues. When we upgrade Mantis, this should "improve".

I am the original/lead developer of Ardour. 42low, you are being misleading. The version of Ardour distributed by every Linux distribution (except the KXAudio add-ons) is not an official version of Ardour. It may be based on the source code that we provide, but it is an unofficial build from the per...

This is an extraordinarily bad idea. The fact that git master is working "fine" for someone right now doesn't obscure the fact that: it will save your work in a session format that is neither back-compatible with 5.x nor likely to be the format used by 6.0 may not allow your work to be ope...

How about "today" ?

http://ardour.org/whatsnew.html

Enjoy!