LinuxMusicians

When I load the Linuxsampler LV2-plugin into a midi-track then I have to start a Linuxsampler frontend like Jsampler fantasia to load a soundfont, adjust midi channel and so on. The frontend can save this state but then you have to
1.) start Qtractor
2.) load Qtractor's session file
3.) start Jsampler fantasia
4.) load Jsampler fantasia's configuration script

Is it possible that Qtractor stores Linuxsampler's configuration in Qtractor's session file?

bluebell wrote:Is it possible that Qtractor stores Linuxsampler's configuration in Qtractor's session file?

it used to, at least last time i've tried it (uh a year ago or so o.O), that linuxsampler-lv2 plugin should save its state within the qtractor session and restored on load.

are you saying that it doesn't anymore?

that would be a shame on don't know what, either in qtractor, lv2, lilv, or linuxsampler-lv2... or in the specific packaging of each and what not...:/

cheers

Seems to be an issue in my linuxsampler-lv2. Ardour doesn't save its state, either.

linuxsampler-lv2 1.0.0+svn2325-0~oneiric1

Edit:
I compiled the svn-version and got the same result.

Edit:
Not really the same result. With my brand new svn-linuxsampler LV2 plugin Ardour opens 32 jack outputs whenever I create a midi track with that plugin.

i've just tested now, with linuxsampler-lv2 svn trunk rev.2481 and it's working as it was like i said, a year ago added a midi track, inserted a linuxsampler-lv2 instance, loaded a .gig using qsampler as usual; saved the simple session; quit, restart and reloaded it again--all seems to work as advertised: linuxsampler-lv2 plugin state is saved/restored properly into/from a qtractor session.

bluebell wrote:Not really the same result. With my brand new svn-linuxsampler LV2 plugin Ardour opens 32 jack outputs whenever I create a midi track with that plugin.

that's probably because ardour opens up a stereo (2ch) audio JACK port pairs, one for each of the 16 addressable MIDI channels.

qtractor doesn't open any JACK ports for plugins on itself and that's because all signal flow, be that audio or MIDI, is internal and only exposed at the in/out buses level; in qtractor MIDI tracks only addresses one (1) MIDI channel vs. ardour's MIDI tracks which addresses the whole 16 bunch)

a qtractor MIDI bus is probably the the best place to insert a multi-timbral MIDI instrument plugin, as it then can address all converging 16 MIDI channels into one plugin instance.

hth.
cheers

rncbc wrote: that's probably because ardour opens up a stereo (2ch) audio JACK port pairs, one for each of the 16 addressable MIDI channels.

qtractor doesn't open any JACK ports for plugins on itself and that's because all signal flow, be that audio or MIDI, is internal and only exposed at the in/out buses level; in qtractor MIDI tracks only addresses one (1) MIDI channel vs. ardour's MIDI tracks which addresses the whole 16 bunch)

a qtractor MIDI bus is probably the the best place to insert a multi-timbral MIDI instrument plugin, as it then can address all converging 16 MIDI channels into one plugin instance.

Qtractor does it right in its midi-tracks. Please don't change it

BTW: I managed to get the menu bar vanished. I could display it again by editing Qtractor.conf and setting View\Menubar=true.
Is there a way to achieve this without a text editor, just by clicking?

bluebell wrote:BTW: I managed to get the menu bar vanished. I could display it again by editing Qtractor.conf and setting View\Menubar=true.
Is there a way to achieve this without a text editor, just by clicking?

Ctrl+M

rncbc wrote:

bluebell wrote:BTW: I managed to get the menu bar vanished. I could display it again by editing Qtractor.conf and setting View\Menubar=true.
Is there a way to achieve this without a text editor, just by clicking?

Ctrl+M

Thanks. I swear to read Help->Shortcuts carefully

rncbc wrote:i've just tested now, with linuxsampler-lv2 svn trunk rev.2481 and it's working as it was like i said, a year ago added a midi track, inserted a linuxsampler-lv2 instance, loaded a .gig using qsampler as usual; saved the simple session; quit, restart and reloaded it again--all seems to work as advertised: linuxsampler-lv2 plugin state is saved/restored properly into/from a qtractor session.

bluebell wrote:Not really the same result. With my brand new svn-linuxsampler LV2 plugin Ardour opens 32 jack outputs whenever I create a midi track with that plugin.

that's probably because ardour opens up a stereo (2ch) audio JACK port pairs, one for each of the 16 addressable MIDI channels.

qtractor doesn't open any JACK ports for plugins on itself and that's because all signal flow, be that audio or MIDI, is internal and only exposed at the in/out buses level; in qtractor MIDI tracks only addresses one (1) MIDI channel vs. ardour's MIDI tracks which addresses the whole 16 bunch)

a qtractor MIDI bus is probably the the best place to insert a multi-timbral MIDI instrument plugin, as it then can address all converging 16 MIDI channels into one plugin instance.

hth.
cheers

I tested it again and yes, it works. I created 2 midi tracks with a linuxsampler-lv2, configured them, stored the Qtractor session, and the settings got restored. Don't know what I did wrong.

Placing the multitimbral linuxsampler-lv2 in a MIDI bus is possible but if all instruments get mixed to the same JACK outputs you can't mix them separately (pan, reverb and so on).