Qtractor 0.4.5 - A Friskier Demivierge is out!

Conforming to LADISH Level 1, an application should save its state in response to SIGUSr1 signal. That's what Qtractor >= 0.4.4 does. Try this:

this should do the same as if you would have asked for File/Save from the main menu. Qtractor should NOT exit (provided you're running 0.4.4 or later).

Byee

@mark,

First, you can try moving the global configuration file away (~/.config/rncbc.org/Qtractor.conf). It has been reported that starting from scratch is kind of a cure for most of similar faulty behavior.

Second, if the previous suggestion doesn't get you any better, you can try building from source without LV2 support (./configure --disable-lv2). Reasons for this are slight suspicions of a particular bad libslv2 delivery or/and one its dependencies (eg. librdf0). I've been told more than once that magic happens when switching one or all of those dependencies, specially on debian based systems.

Third, if you dare, you should still build from source with debug in mind (./configure --enable-debug). Watch then for stack-trace dumps whenever it segfaults and report back. It also helps if you turn off View/Options.../Display/Capture standard output, so that those segfault stack-traces get caught on the terminal console.

Seeya

My turn to say thanks :)

may I ask you to tell about your experience with qtractor in particular? All help is welcome and user manual / documentation writers are godsend ;)

Cheers

There's no such thing like aux-buses in Qtractor. Not quite.

You can however insert a plugin into an audio track. The amount of plugin effect (wet/dry) is usually a plugin parameter.

Track plugins apply to internal track audio outputs before mix-down into the designated output bus. There's the catch: output buses in Qtractor are mix-down devices, not alternate signal paths. Qtractor buses are indeed the interface devices to the outer world.

In the very same way, you can insert plugins into an output bus. That way, it will apply to the audio output after the mix.

Each track or bus has a plugin chain, meaning that you can chain several plugins one after the other. Only activated plugins apply. Non-active plugins are bypassed. There's also this special kind of inserts which function as taps to either a track or bus. This kind does expose send output ports and return input ports, to and from the outside respectively, which may serve to connect stand-alone JACK enabled applications as regular plugins.

HTH
Cheers

You're probably referring to the first dialog that appears asking for a proper session name and then the second one for the actual file name to be written. This second one is often like the native file requester you get from your desktop environment (Nautilus from Gnome?). The first one is actually necessary for having a proper session name. Session name is not always the same as the file name, though. However that initial session name will be indeed the one suggested for the file name in the second dialog. You see, you only get this behavior when saving brand new sessions, untitled scratch sessions so to speak. That's it.

Cheers