Request-Ardour 2.8.16 & CALF LV2 Plugins > 0.19 (Mepis 12)

[Rott3nHippi3]

This is a request to have both Ardour and the Calf Plugins added to the test repo (maybe). I tried adding the debian experimental repos, but the installation had a lot of dependency issues. Not sure if there's other repos I can add to get it to upgrade with all the other required files.

As for the CALF plugins, I know they're available in the old Mepis 11 repos, but I ran into dependency issues with that as well. It was a long shot!

[Stevo]

Will give them a shot. We're kind of busy with the MX 14.1 point release coming soon, but will try and make some time.

[Rott3nHippi3]

That actually brings up a good point. Is MX the 'future' sort of speak? Will Ardour even run in that? Since my Mepis 12 machine is more or less for playing around... I have no issues rebuilding this to MX if Ardour and all the related plugins can be packaged for it. My Mepis 11 machine (my actual production machine) is pretty solid and I have no plans on upgrading that until 12 is final. Of course, Ardour/Jack/Lv2 Plugins being available will dictate that just as much as 12 being 'official.'

[Stevo]

I've got the 64-bit version of both built on M12, and Ardour comes up and runs. I'm using my Liquorix kernel, and it says the latency is 42.7 ms, whatever that means. Now starting the 32-bit builds. I used the Experimental version because they FINALLY fixed the debug package problem on 64-bit.

MX should run any application that will run on M12, including Ardour, maybe even faster due to the lightweight xfce desktop. It shares wheezy-backports and the M12 CRs by default, so that part makes it closely related to M12. I use M12 as my everyday desktop, because I'm used to KDE and have several custom desktop actions that help with package building, and it's very stable. I could switch to my MX install and get by very easily with that, though.

[lucky9]

I've been surprised at the responsiveness of MX14 with KDE-Standard. It's very snappy compared to my Mepis 11 installation. (I've never been able to get Mepis 12 to boot on my PC. I do have a VM of it.)

[Stevo]

I've uploaded the packages for the CR--they aren't difficult to do a manual install, too. The plugins are just a single deb, Ardour will need libaubio4 (included) installed first. The 64-bit package of Ardour is just ardour, there's a choice of debs for 32-bit, but most everyone can use ardour-i686, I believe the 32-bit "ardour" is for very old machines.

https://drive.google.com/file/d/0B1UMhs ... sp=sharing

about 41 MB

[joany]

Is MX the 'future' sort of speak? Will Ardour even run in that? Since my Mepis 12 machine is more or less for playing around... I have no issues rebuilding this to MX if Ardour and all the related plugins can be packaged for it. My Mepis 11 machine (my actual production machine) is pretty solid and I have no plans on upgrading that until 12 is final. Of course, Ardour/Jack/Lv2 Plugins being available will dictate that just as much as 12 being 'official.'

Ardour and Calf are already available through Synaptic on my MX-14/KDE installation. I haven't installed either of them -- I'm satisfied with Audacity -- but I don't see why they wouldn't run.

[Stevo]

Is MX the 'future' sort of speak? Will Ardour even run in that? Since my Mepis 12 machine is more or less for playing around... I have no issues rebuilding this to MX if Ardour and all the related plugins can be packaged for it. My Mepis 11 machine (my actual production machine) is pretty solid and I have no plans on upgrading that until 12 is final. Of course, Ardour/Jack/Lv2 Plugins being available will dictate that just as much as 12 being 'official.'

Ardour and Calf are already available through Synaptic on my MX-14/KDE installation. I haven't installed either of them -- I'm satisfied with Audacity -- but I don't see why they wouldn't run.

Yes, but these are the newest versions from upstream Debian.

[Jerry3904]

That actually brings up a good point. Is MX the 'future' sort of speak? Will Ardour even run in that? Since my Mepis 12 machine is more or less for playing around... I have no issues rebuilding this to MX if Ardour and all the related plugins can be packaged for it. My Mepis 11 machine (my actual production machine) is pretty solid and I have no plans on upgrading that until 12 is final. Of course, Ardour/Jack/Lv2 Plugins being available will dictate that just as much as 12 being 'official.'

It is very likely at this point that MX Linux is the future, since development on MEPIS 12 stopped some time ago and Warren has made it clear that he has no intention of moving forward.

[Rott3nHippi3]

I've uploaded the packages for the CR--they aren't difficult to do a manual install, too. The plugins are just a single deb, Ardour will need libaubio4 (included) installed first. The 64-bit package of Ardour is just ardour, there's a choice of debs for 32-bit, but most everyone can use ardour-i686, I believe the 32-bit "ardour" is for very old machines.

I changed my Distros prefs to use Mepis.. and I can see the 2.8.16 version available, but when I try to 'upgrade,' it changes the package to 'broken' (red square) without specifiying where the issue is. It does the same thing on the libaubio4 file as well. Is there something I'm doing wrong? The newer calf plugins installed fine.

Here's the output for 'Fix Broken Packages'
E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies