[PlanetCCRMA] Qtractor 0.4.5svn1517

Niels Mayer nielsmayer at gmail.com
Tue May 18 18:40:38 PDT 2010


On Tue, May 18, 2010 at 2:23 PM, Rui Nuno Capela <rncbc at rncbc.org> wrote:
 thanks for testing and harnessing this out.

Thanks for filling my desktop and hard-disk with the coolest, well-conceived
& well-written software!

re. (1) Track Properties Plugins Freeze
>
> it turns out that choosing the "(Any)" plugin type is not /that/ all
> recommended, specially if you have some ill behaved plugins around and
> it takes only one to make it all compromised. notably, if you just
> happen to have some native VST plugins around you're better off never
> use this plugin listing option
>

It wasn't something I'd normally do, more of a "testing" thing. I did
install just about every lv2/dssi/ladspa plugin I could find on CCRMA and
set qtractor's plugin options pointing to /usr/lib64/ladspa/ ,
/usr/lib64/dssi/ , and /usr/lib64/lv2/ . The issue didn't come up on any of
the other options. "lv2" "dssi" "ladspa" , just "(any)" .

Now on second look, its clear the problem is in one of my DSSI or LADSPA
plugins. If I select  between options "ladspa" and "lv2", no problem. But if
I select between "dssi" and "ladspa" it core dumps. Erasing
dssi-vst-wine-0.8-4.fc12.i686  and  dssi-vst-0.8-4.fc12.x86_64   didn't
help, and I don't have any other VST's....

Poking around some more, the LV2 Calf Organ (
lv2-calf-plugins-0.0.18.5-3.fc12.x86_64 )causes qtractor to hang in the
exact same way as the LV2 LinuxSampler
( lv2-linuxsampler-plugins-1.0.0-2.fc12.ccrma.x86_64 ).

However, why would a midi plugin need LADSPA anyways? I don't see any LADSPA
plugins with midi ins. Likewise, many of the entries in LV2 and DSSI have no
MIDI input, yet are presented in a long list in the midi plugins selection.
Perhaps it makes sense, in the context of choosing a midi plugin, to filter
out the plugins that don't provide MIDI input?

 Similarly, does it make sense for a midi output (in the mixer-panel) to
have a plugin that outputs Audio? I tried putting synth plugins in the
mixer's midi outputs,  but couldn't get them to produce sound on midi input
("send test note" in FluidSynth DSSI works); I could get midi-input plugin
working only when invoked on a track as an instrument, and connected to an
input..

re. (2) Track Properties Plugins Freeze
>
> linuxsampler plugins (lv2 or dssi) don't connect directly to alsa nor
> jack, ie. device types should be set to "plugin" and not "alsa" (midi)
> nor "jack" (audio), while on channel setup in qsampler. anyway, don't
> push it so hard if you're not knowing how to do. linuxsampler plugins
> are bleeding-edge anyway, so you better do one step at a time :)
>

w/r/t my comments on jack vs alsa -- that was for setting up qsampler, which
I used because I figured it would better guide me than running Linuxsampler
on the command-line. I was getting LinuxSampler plugins to freeze both in
dssi and lv2, so I figured it might have something to do w/ the linuxsampler
server not running, and after failing to change qtractor's behavior by
running linuxsampler on the command-line,I tried getting it working directly
inside qsampler, only to find that .SFZ isn't supported in the CCRMA
version....

The first step: Update Linuxsampler and plugins. I'm using what CCRMA
has: linuxsampler-1.0.0-2.fc12.ccrma.x86_64,
 lv2-linuxsampler-plugins-1.0.0-2.fc12.ccrma.x86_64,
linuxsampler-dssi-1.0.0-2.fc12.ccrma.x86_64
. it looks like I'll need to get LinuxSampler off CVS anyways,  give that
the SalamanderGrand is in sfz format:

alexander <axeldenstore <at> gmail.com> wrote:
>s I reported earlier I ditched the giga format and went
>for *sfz*, you will need linuxsampler cvs to load the *sfz* file.

What version of LinuxSampler do you recommend using? Anybody have up-to-date
or qtractor-compatible LinuxSampler as an RPM (SUSE rpms work fine too)?

re. (3)
>
> well, tinkering with random plugins is risky business after all :) no
> plugin is trustable before hand, if you know what i mean ;)
>

Yep. Qtractor held up quite nicely through all the fidding, so I'd say this
release works well, and it's very solid & ready to supersede the
current&buggy rpmfusion release. I just wanted to make sure that I tested
out most of it's functionality, and the plugins is one aspect I hadn't
played with -- after all , I've got a db60xg and qxgedit keeping me busy.
:-)

-- Niels
http://nielsmayer.com

PS: Is there a bug-tracker for qtractor or any of your other software? If
not, you might want to consider applying for a free Jira License (
http://www.atlassian.com/opensource/ ). Jira has done a beautiful job in
bug-tracking an open-source project I'm using ( http://jira.xwiki.org ) that
I've been using as a Java-based web-programming platform for the last few
years and for various projects (coming real soon now
http://trainspodder.com...
http://nielsmayer.com/ra2_residentadvisor_net_audio_RA201_100405_19_454_18_5_25_5_18_residentadvisor_net_mp3.png
<http://nielsmayer.com/ts-episode-timeline.png>
http://nielsmayer.com/ts-episode-evnt-anls.png ).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20100518/11857496/attachment.html 


More information about the PlanetCCRMA mailing list