Live data from Hacker News

Ardour 8.0

ardour.org

101–110 of 156 posts

Re: Ardour 8.0

#101

As usual, the lead developer (c'est moi) is happy to answer any questions.

What was the main reason for keeping the select-groups from applying to control surfaces? I'm not sure what would be the point of multi-selecting otherwise.

As an aside, is there any way I can add functionality to a control surface (that isn't writing C)? I use a behringer X-Touch (heavily) and moved to Reaper because there were plugins that provided much deeper integration with my X-Touch (which as a result has me working a lot faster in certain areas).

Re: Ardour 8.0

#102

As usual, the lead developer (c'est moi) is happy to answer any questions.

How is the MPE work going? What about MIDI 2.0?

MPE: nothng is required to record and playback MPE, it's just MIDI 1.0. There's no "nice" way to edit MPE at this time. I can't say right now what priority we attach to this.

MIDI 2.0: no plans at this time.

Re: Ardour 8.0

#103

Earlier quoted context omitted.

How is the MPE work going? What about MIDI 2.0?

MPE: nothng is required to record and playback MPE, it's just MIDI 1.0. There's no "nice" way to edit MPE at this time. I can't say right now what priority we attach to this. MIDI 2.0: no plans at this time.

The tempo mapping grid tool looks super super cool, I look forward to trying it out.

Re: Ardour 8.0

#104

Congratulations Paul. For those who don't know, the creator of Ardour is active here and was (historically) very active and helpful on Linux audio lists. I learnt a lot from dicussions on there on the intracies of audio programming. While my work has shifted from Linux audio to Max/MSP these days (I wrote Scheme for Max), in the mid 2000s linux audio hacking was my gateway to the world of programming, eventually lead…

Thank you for the self-promotion, Scheme for Max looks like something I’ve been wishing for for a long time!

Re: Ardour 8.0

#105

Earlier quoted context omitted.

Plugins themselves never require admin access to run, the installer does.

Unless you are running your plugins in a sandbox or have different profiles for different usages, this doesn't make any difference as what is more important, your personal data is accessible from your main user. Anyone producing music from qubesOS?

Are you saying it makes no difference whether process runs as root or normal user in whatever OS you're on?

Re: Ardour 8.0

#106

Earlier quoted context omitted.

100 USD a year (more in Switzerland because Apple doesn't even pay for the taxes) is not nothing. Why should I pay to place apps that I spend my free time to develop and offer for free? Apple should at least not charge a recurring fee if all apps posted are open source and free. At least over at Google it is a one time fee.

I'd also prefer if there was no $100 to pay. But it is a fair price, and I find the attitude of programmers that everything should be free quite damaging. If you want to donate your free time, that's really up to you. Don't construe constraints for other people or companies from that.

> I find the attitude of programmers that everything should be free quite damaging.

Many dead UNIX vendors agree.

Re: Ardour 8.0

#107

As usual, the lead developer (c'est moi) is happy to answer any questions.

What was the main reason for keeping the select-groups from applying to control surfaces? I'm not sure what would be the point of multi-selecting otherwise. As an aside, is there any way I can add functionality to a control surface (that isn't writing C)? I use a behringer X-Touch (heavily) and moved to Reaper because there were plugins that provided much deeper integration with my X-Touch (which as a result has me w…

We're still debating the control surface decision. There are two reasons for leaving things alone:

1. hardware surfaces have had different use conventions for a long time (certainly things that look like mixing consoles). They are effectively multitouch devices, and human interaction with them just isn't the same as with a mouse & GUI.

2. for Mackie Control Protocol devices, we already provide a nifty multi-target action there where you just press and hold one eg. solo button and then press another, to apply it to the range that was pressed.

We do not providing scripting for developing control surface support. I've written extensively about my thoughts on Reaper's scripting [0] and I remain conflicted by the questions it raises. There's nothing that can be done in Reaper via scripting that can't be done in Ardour via C++, and a huge amount that theoretically could be done in Ardour via C++ that cannot be done in Reaper. I know this is not a satisfactory answer for people who do not want to master (a) C++ (b) the build environment.

[0] https://discourse.ardour.org/t/is-open-source-a-diversion-fr...

Re: Ardour 8.0

#108

As usual, the lead developer (c'est moi) is happy to answer any questions.

This looks absolutely amazing. Thank you! Totally minor feedback in case you value this kind of feedback: the website’s layout is freaking out on my iOS Safari. I can scroll sideways like four page widths and then see nothing at all. Same with the front page. A short video if it helps: https://youtube.com/shorts/2dItDk_FtkI?si=WSsM2fgWR91IR7wU

It's an old version of bootstrap. Probably too old.

Re: Ardour 8.0

#109

Earlier quoted context omitted.

MPE: nothng is required to record and playback MPE, it's just MIDI 1.0. There's no "nice" way to edit MPE at this time. I can't say right now what priority we attach to this. MIDI 2.0: no plans at this time.

The tempo mapping grid tool looks super super cool, I look forward to trying it out.

One thing we have discovered/realized since tagging 8.0 is that the grid tool will misbehave if you do "wild dragging" with it between existing tempo markers. It is intended to "tweak" the grid in that situation, and is designed around small, "subtle" mouse movement. We may be able to come up with some fixes that make it more robust in the face of users deliberately or accidentally going "wild" with the mouse.

Re: Ardour 8.0

#110

The screenshot features the excellent Surge synth. Check it out if you don't know it, it's an excellent sounding synth with a gorgeous oscillators section.

It's three times the size of the DAW itself, and unlike the DAW it requires using an installer during which it asks for admin password. Wow. Wonder what happened to "just drop this file into that dir" README.txt...

Users want an installer. You can see what the installers are doing by looking at the scripts in the repo (this is an open source project). Admin permission is necessary to write to the Global VST folder. You can direct your "Wow" at Steinberg if you want. The spec was recently updated to allow for a User install location which has been considered: https://steinbergmedia.github.io/vst3_dev_portal/pages/Techn...

If you don't want an installer, you can download the pluginsonly bundle on the release page and do it yourself: https://github.com/surge-synthesizer/releases-xt/releases

Post reply on HN