View Issue Details

IDCategoryLast Update
0008390other2020-09-10 17:51
ReporterunfaAssigned To 
Status newResolutionopen 
Product Version6.2 
Fixed in Version 
Summary0008390: Ardour comes bundled with proprietary software and plug-in demo versions
DescriptionI've talked about this before, but I guess it got lost, so I'm bringing it up again.

1. Ardour for Linux comes bundled with proprietary Harrison GUIs for some of the stock Ardour plug-ins.

I think the GUIs are nice and all, but I run Ardour *specifically* because it's free software, and I just don't want to have it served with proprietary binary code that I have no idea what is doing.

I'd be most happy to see the Harrison GUIs be open-sourced as contribution to Ardour, but I don't expect that.

Since that's the case, I want to be able to have Ardour install without any proprietary plug-ins or plug-in GUIs.
And since Ardour's big selling point is the open-source nature of the project, I'd rather have these as opt-in than opt-out.
I guess the unofficial builds available in various Linux distributions will come without them, but I'd like to not be forced to use these to get a 100% free-software package.

2. Ardour for Windows comes bundled with demo versions of proprietary Harrison plug-ins.
I guess Windows users aren't complaining about it, but honestly this is nothing more than an annoying advertisement for Harrison software - these plug-in are near useless unless the user purchases a license. The Harrison plug-in GUIs are at least fully functional. I think it'd be best to get rid of this stuff, or at least provide an opt-out during installation. Or better: an opt-in.

3. There's also useless demo versions of paid x42 plug-ins bundled, which at least are free software, but still this is shovelware, becasue they are useless unless the user purchases a license.

I have nothing against paid FOSS plug-ins, and I think the x42 plug-ins are of great quality, but I'd highly prefer if Ardour bundled only fully functional plug-ins, not placeholders asking for a license.


One of the first things I do on any fresh Ardour installation on Windows is to mark all the useless demo plug-ins as hidden. This doesn't create a good user experience where 90% of the stock plug-ins turn out to be just cardboard cut-outs asking for more money (the user has already paid *something* to get the Windows build of Ardour).

I know this is done to help fund Ardour's development and support it's creators (x42 plug-ins etc.) and you probably have a deal with Harrison to bundle their demo versions, but it's not looking good for the users, especially those who are sensitive to software freedom.

Please provide users with a choice to *not* install proprietary GUIs or demo versions of plug-ins with Ardour.
Instead - please consider bundling fully functional plug-ins like x42 MIDI Filters, x42 DPL, x42 Tuna and x42 Autotune - these would greatly compliment Ardour's stock plug-in set and give users a better experience.
TagsNo tags attached.



2020-08-31 21:10

administrator   ~0024994

> And since Ardour's big selling point is the open-source nature of the project

> and you probably have a deal with Harrison to bundle their demo versions

Only an agreement that we can legally do so. We're glad that Harrison allows those to be bundled.
The main benefit here is that you can load sessions of other using the plugins -- the limitation is only the custom plugin GUI. The DSP is excellent, generally better than free software alternatives and you get it gratis. Even the generic UI works and they're even using a libre standard (LV2), I wish more plugin vendors would follow their lead.

No DRM. No hardware keys, no demo noise. -- I honesty think we should promote this and get more companies to ship cross-platform plugins in similar fashion if they cannot release the software under a free/libre license.

The only reason to not want them is a purism, and I found that best approach is to let those guys weed out files not matching their ideology themselves. Really, they should not trust us in the first place even if we add an opt in/out. :)


2020-08-31 21:12

administrator   ~0024995

> I know this is done to help fund Ardour's development and support it's creators

Actually that's not the reason.
The plugins were added for user's convenience, because users asked if we we can include the plugins that are bundled with Mixbus also with Ardour.


2020-08-31 22:35

reporter   ~0024996

Thanks for clearing this up. I'm gonna read up on Paul's post later as it's quite a lengthy read.

It seems my assumption that the main drive for these plug-ins / GUIs to be included was upselling or product cross-promotion was wrong. And I am glad to be proven wrong there.

I know most users will not complain about it, or even notice - but for people like me who have decided on principle to run as little proprietary software as possible - this is a bummer.
Yes, we can dig files up, ask around and delete what we don't want after the installation, or just depend on unofficial builds where package maintainers have stripped this out for us.
Yet - it's not convenient and it's creating a suboptimal experience for a certain group of Ardour users if they choose to use official Ardour binaries.
I'd expect these should give the best possible experience to all users, shouldn't they?

It's not far away to say "if you don't like that just make your own build" - and it's not reasonable to expect regular users to be able to jump such hoops. And digging into program files to weed out proprietary plug-in binaries is far beyond the reach of an average non-savvy user. Should these people be forced to use proprietary software when they download Ardour (and open a-EQ), when it's advertised as a free/libre program? It's a bit misleading and I am surprised nobody has raised this issue before me.

I understand that it wasn't done viciously, but I think a clear information and a checkbox or two in the installer would go a long way here.

[ x ] Install additional open-source x42 plug-in demo versions
[ x ] Install additional proprietary Harrison plug-in demo versions

What do you think?


2020-09-09 19:44

reporter   ~0025022

I started using Ardour mainly as a political/ethical reason -political in an general/wide/'ancient' sense: politike techne, how we (want to) treat each other on a community. I was taught audio processing on an institution using proprietary software, but I wanted to prove (myself) I could be able to perform similar tasks with a more politically committed software.

And I see it's a difficult topic what Paul posted. I couldn't contribute as a developer as I don't know any program language. As far as I can get is reporting bugs, supporting as I can, spreading among my contacts, learning how to use the software and using it. I think that we all are influenced by conservative ideas (we are born in between them) so there are great chances that we get more "advices" to do it the way it is supposed to (as many users would ask too, mainly in DAW stuff). I know you know that, otherwise you wouldn't keep working on the projects and wouldn't have written all those post stating your point of view.

On the other hand, what you call "gratis" (in term of money), is not in other aspects. For example, the company is getting advertising as an exchange (the logo is there and I guess you could not remove it). Is it necessary to apply the proprietary GUI on Ardour's native plugins? I don't understand how is that allowing to load sessions that use Mixbus plugins; or I got it wrong?

We do put trust in many projects, not only Ardour. A community is based on trust, any relation is based on trust. And one obviously get some clues, judge, pre-judge, based on what others do... Think about food: there's a long chain that's imposible to be verified by 'external' people.

I agree that there would be fair not to include proprietary software by default, and a good approach could be what unfa proposes about extra demo plugins. And what about native plugins (a-EQ, a-Compressor, a-Delay)? Why do they have to use Mixbus GUI?


2020-09-09 23:52

reporter   ~0025023

>best approach is to let those guys weed out files

Sorry, never thought you were being literal :)


2020-09-10 00:01

administrator   ~0025024

just delete the LV2/Harrison.lv2 folder


2020-09-10 00:03

administrator   ~0025025

> And what about native plugins (a-EQ, a-Compressor, a-Delay)? Why do they have to use Mixbus GUI?

The LV2 plugin standard allows separate 3rd party GUIs for any plugin. In the last 3 years nobody stepped up and provided commercial-quality cross-platform UIs.
Ben at Harrison eventually volunteered to make some (a-eq is done, the others are functional but still being worked on).

If someone creates a better GUI, we'll happily ship that instead.

The goal of the Ardour bundles from is to create a good out-of-the-box experience for typical users.


2020-09-10 17:51

reporter   ~0025026

I see the point, thanks for clarifying.

Issue History

Date Modified Username Field Change
2020-08-31 20:10 unfa New Issue
2020-08-31 21:10 x42 Note Added: 0024994
2020-08-31 21:12 x42 Note Added: 0024995
2020-08-31 22:35 unfa Note Added: 0024996
2020-09-09 19:44 jumase Note Added: 0025022
2020-09-09 23:52 jumase Note Added: 0025023
2020-09-10 00:01 x42 Note Added: 0025024
2020-09-10 00:03 x42 Note Added: 0025025
2020-09-10 17:51 jumase Note Added: 0025026