qtractor-devel — Qtractor development discussion

Re: [Qtractor-devel] Inserts and synth plugins

[Holger M. <ho...@ma...>]

On Wed, 13 Aug 2014, Ralf Mardorf wrote:

> Hi,
> 
> now I can underpin my claim with routing issues. It was a long time ago,
> that I used the computer and Qtractor to make music, so I don't remember
> all the details, but at least yesterday night/this morning I experienced
> one of the uncountable issues.
> 
> hexter plugin -> [  i  n  s  e  r  t  ] Fons' parametric eq
>                  |                    ^
>                  -> external 19" gear-|
> 
> fluid plugin  -> [  i  n  s  e  r  t  ] Fons' parametric eq
>                  |                    ^
>                  -> external 19" gear-|
> 
> If I use hexter, the insert does _not_ work correctly, resp. Qtractor's
> channel fader 0 setting or any value close to 0 doesn't work, so a
> silent mix is impossible.

The fader is not an audio fader and the panner is not an audio panner.
They are sending MIDI commands. Maybe Hexter doesn't honor it.

I don't use the faders at all, not for MIDI tracks and not for audio
tracks because AUX send are pre fader.

I use a simple LADSPA stereo amplifier and CALF stereo tools to handle
stereo signals and pan them:

http://www.marzen.de/tmp/qtractor-mixer.png

I can't say anything about Wet/Dry issues in Inserts because I use AUX
sends only.

[Qtractor-devel] Inserts and synth plugins

[Ralf M. <ral...@al...>]

Hi,

now I can underpin my claim with routing issues. It was a long time ago,
that I used the computer and Qtractor to make music, so I don't remember
all the details, but at least yesterday night/this morning I experienced
one of the uncountable issues.

hexter plugin -> [  i  n  s  e  r  t  ] Fons' parametric eq
                 |                    ^
                 -> external 19" gear-|

fluid plugin  -> [  i  n  s  e  r  t  ] Fons' parametric eq
                 |                    ^
                 -> external 19" gear-|

If I use hexter, the insert does _not_ work correctly, resp. Qtractor's
channel fader 0 setting or any value close to 0 doesn't work, so a
silent mix is impossible.
If I use fluid, the insert is ok, IOW the mixer's fader does work about
the full range from 0 to 100. Btw. in this case I'm using 100% of the
inserted signal, no mixing with the original signal and I noticed that
the labelling is wrong. It's "Dry / Wet", but with the fader to the
left, position 0.000 I get the wanted 100% signal from the external
gear, so the labelling should be "Wet / Dry", resp. it's completely
nonsense. An insert shouldn't have an option for mixing, it would be
better for a virtual mixer to follow the way a real mixer does work.
Inserts are inserts, no way to mix. For mixing dry and wet signals aux
sends and sub routs are used. Oh, I'm missing an option to give tracks a
negative delay in < ms steps, moving MIDI tracks isn't good for several
reasons.

"Fortunately" (I'm sarcastic) the driver for my RME audio card is
ridiculous, since still only 2 of the 8 ADAT channels are routed to jack
IOs, IOW I anyway can't use all my external gear, so inserts are less
important, instead of professional external synth and effects I need to
use crappy virtual synth and bad programmed effect plugins, such as the
Calf multi band gate, that very often cause Qtractor to crash, if I
close the GUI, Hexter (I described the issue above) instead of my real
DX7. Btw. for Calf monosynth Qtractor's mixer fader completely doesn't
work and Qtractor always crashes when closing the monosynth GUI.

Completely OT: Loop play to practise and when ready to push record,
doesn't work for the new version of Qtractor anymore? Or am I missing
something?

Regards,
Ralf

Re: [Qtractor-devel] Qtractor 0.6.2 audio and MIDI output issue

[Holger M. <ho...@ma...>]

On Tue, 12 Aug 2014, Ralf Mardorf wrote:

> 
> On Tue, 2014-08-12 at 18:48 +0200, Holger Marzen wrote:
> > > Is there a way to send MIDI data from several tracks to the synth plugin
> > > of one track?
> > 
> > Should work if you put the synth plugin into a bus and route the tracks
> > there.
> > 
> > > Is there a way to get sub groups for mixing the audio signals of MIDI
> > > and audio tracks?
> > 
> > You should be able to manually connect the tracks' output to a subgroup
> > bus. Alternatively you can use an aux send to the subgroup bus. It's
> > pre-fader, so you can put the track's fader down.
> 
> All those routing tricks cause issues in the past and I doubt it will
> work without issues nowadays. I didn't use the computer for music for a
> while, now I'm trying to make a song using Qtractor again and I already
> experienced all the IO issues I experienced in the past that already
> happened and happen without tricky routing, such as MIDI in is ignored
> for a while and suddenly speaker damaging noise appears and after that
> MIDI does work again. Or after a while of usage MIDI in is delayed etc.
> pp..

I can't see a problem here. To use JACK for audio routing is the
designed way to go.

Ansicht
-> Optionen
-> Plugins
-> Instrumente
[X] Dedicated audio outputs

Restart Qtractor. Then newly created tracks have their own outputs that
you can route to buses. Those buses are your subgroups.

If that's not what you want then you might try Rosegarden. It has a
built-in subgroup concept. You assign each instrument to Master or a
Subgroup.

Re: [Qtractor-devel] System lock-up on MIDI clocking

[Ralf M. <ral...@al...>]

On Tue, 2014-08-12 at 21:29 +0200, Ralf Mardorf wrote:
> On Tue, 2014-08-12 at 18:49 +0200, Holger Marzen wrote:
> > On Mon, 11 Aug 2014, oli_kester wrote:
> > 
> > > Thanks for the responses Ralf, they've pointed me in the right direction :)
> > > 
> > > What solved this for me was setting the queue timer resolution to
> > > "system timer (1000Hz)". When I switch to "HR timer (1000000000Hz)" ,
> > > which I presume is the default, the system locks up after a short play
> > > time - even in the first bar! I'm not surprised this is what was
> > > causing issues - a billion Hz is gigantic! Surprised any computer can
> > > send MIDI signals that fast. 
> > 
> > This seems to be a still existent ALSA problem in the kernel. It happens
> > with Rosegarden, too.
> 
> No problem here. HPET and Qtractor do work. IIRC in the past, I might
> confuse it with another issue, there was the need to launch Qtractor
> with the session file, IOW
> 
> qtractor /path/file.qtr
> 
> IIRC when not doing this there was an error, "HPET already in use" or
> similar. Again, I might confuse it with another issue. Btw. I start my
> sessions with a script IOW I still launch Qtractor with the .qtr file.
> 
> JFTR I don't use jackd with HPET/HR Timer, perhaps there are only issues
> when using jackd and the sequencer with HPET?! Another issue might be
> caused by the kernel tickless options (NO_HZ).
> 
> [rocketmouse@archlinux ~]$ zgrep HZ /proc/config.gz
> CONFIG_HZ_PERIODIC=y
> # CONFIG_NO_HZ_IDLE is not set
> # CONFIG_NO_HZ_FULL is not set
> # CONFIG_NO_HZ is not set
> # CONFIG_HZ_100 is not set
> # CONFIG_HZ_250 is not set
> # CONFIG_HZ_300 is not set
> CONFIG_HZ_1000=y
> CONFIG_HZ=1000
> CONFIG_MACHZ_WDT=m
> [rocketmouse@archlinux ~]$ uname -rm
> 3.10.47-rt50-1-rt-lts x86_64
> 
> JFTR this 3.10 kernel with patch _50_ is the one and only
> kernel > 3.8 PREEMPT RT that doesn't lock my machine.
> Kernels <= 3.8 PREEMPT RT are ok, kernels >= 3.8 PREEMPT RT usually lock
          <= 3.8 is correct, but  :D       ^^^ > 3.8 ;), not >= ;)
> my machine.

Re: [Qtractor-devel] System lock-up on MIDI clocking

[Ralf M. <ral...@al...>]

On Tue, 2014-08-12 at 18:49 +0200, Holger Marzen wrote:
> On Mon, 11 Aug 2014, oli_kester wrote:
> 
> > Thanks for the responses Ralf, they've pointed me in the right direction :)
> > 
> > What solved this for me was setting the queue timer resolution to
> > "system timer (1000Hz)". When I switch to "HR timer (1000000000Hz)" ,
> > which I presume is the default, the system locks up after a short play
> > time - even in the first bar! I'm not surprised this is what was
> > causing issues - a billion Hz is gigantic! Surprised any computer can
> > send MIDI signals that fast. 
> 
> This seems to be a still existent ALSA problem in the kernel. It happens
> with Rosegarden, too.

No problem here. HPET and Qtractor do work. IIRC in the past, I might
confuse it with another issue, there was the need to launch Qtractor
with the session file, IOW

qtractor /path/file.qtr

IIRC when not doing this there was an error, "HPET already in use" or
similar. Again, I might confuse it with another issue. Btw. I start my
sessions with a script IOW I still launch Qtractor with the .qtr file.

JFTR I don't use jackd with HPET/HR Timer, perhaps there are only issues
when using jackd and the sequencer with HPET?! Another issue might be
caused by the kernel tickless options (NO_HZ).

[rocketmouse@archlinux ~]$ zgrep HZ /proc/config.gz
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_MACHZ_WDT=m
[rocketmouse@archlinux ~]$ uname -rm
3.10.47-rt50-1-rt-lts x86_64

JFTR this 3.10 kernel with patch _50_ is the one and only
kernel > 3.8 PREEMPT RT that doesn't lock my machine.
Kernels <= 3.8 PREEMPT RT are ok, kernels >= 3.8 PREEMPT RT usually lock
my machine.

Re: [Qtractor-devel] Qtractor 0.6.2 audio and MIDI output issue

[Ralf M. <ral...@al...>]

On Tue, 2014-08-12 at 18:48 +0200, Holger Marzen wrote:
> > Is there a way to send MIDI data from several tracks to the synth plugin
> > of one track?
> 
> Should work if you put the synth plugin into a bus and route the tracks
> there.
> 
> > Is there a way to get sub groups for mixing the audio signals of MIDI
> > and audio tracks?
> 
> You should be able to manually connect the tracks' output to a subgroup
> bus. Alternatively you can use an aux send to the subgroup bus. It's
> pre-fader, so you can put the track's fader down.

All those routing tricks cause issues in the past and I doubt it will
work without issues nowadays. I didn't use the computer for music for a
while, now I'm trying to make a song using Qtractor again and I already
experienced all the IO issues I experienced in the past that already
happened and happen without tricky routing, such as MIDI in is ignored
for a while and suddenly speaker damaging noise appears and after that
MIDI does work again. Or after a while of usage MIDI in is delayed etc.
pp..

Btw. how can I cancel MIDI editing, when leaving the editor?

Is there any logic when an edited file automatically is saved as a new
file or when the edited file is overwritten? When working with Qtractor
this seems to be a total mess. I run a script to make snapshots, so that
I'm able to restore broken work, OTOH importing and pasting an imported
clip seldom does work, there are a few bugs. For my workflow non of the
new features is useful, but non of the old bugs is fixed and many things
that worked in the past are broken now.

:(

Re: [Qtractor-devel] System lock-up on MIDI clocking

[Holger M. <ho...@ma...>]

On Mon, 11 Aug 2014, oli_kester wrote:

> Thanks for the responses Ralf, they've pointed me in the right direction :)
> 
> What solved this for me was setting the queue timer resolution to
> "system timer (1000Hz)". When I switch to "HR timer (1000000000Hz)" ,
> which I presume is the default, the system locks up after a short play
> time - even in the first bar! I'm not surprised this is what was
> causing issues - a billion Hz is gigantic! Surprised any computer can
> send MIDI signals that fast. 

This seems to be a still existent ALSA problem in the kernel. It happens
with Rosegarden, too.

Regards
Holger

Re: [Qtractor-devel] Qtractor 0.6.2 audio and MIDI output issue

[Holger M. <ho...@ma...>]

On Sun, 10 Aug 2014, Ralf Mardorf wrote:

> before I added 24 MIDI and 8 audio tracks "Dedicated MIDI player
> outputs" and for plugins "Dedicated audio outputs" was enabled, then I
> disabled both, but the "empty song" doesn't get rid of the dedicated
> audio outputs. How can I get rid of those audio outputs?

I once had the same problem. I solved it by editing the .qtr-file
manually. Can't remember the syntax but it wasn't hard to find.

> Is there a way to send MIDI data from several tracks to the synth plugin
> of one track?

Should work if you put the synth plugin into a bus and route the tracks
there.

> Is there a way to get sub groups for mixing the audio signals of MIDI
> and audio tracks?

You should be able to manually connect the tracks' output to a subgroup
bus. Alternatively you can use an aux send to the subgroup bus. It's
pre-fader, so you can put the track's fader down.

Regards
Holger

Re: [Qtractor-devel] System lock-up on MIDI clocking

[Ralf M. <ral...@al...>]

On Mon, 2014-08-11 at 16:54 +0000, oli_kester wrote:

> What solved this for me was setting the queue timer resolution to
> "system timer (1000Hz)". When I switch to "HR timer (1000000000Hz)" ,
> which I presume is the default, the system locks up after a short play
> time - even in the first bar! I'm not surprised this is what was
> causing issues - a billion Hz is gigantic! Surprised any computer can
> send MIDI signals that fast.

On the quick an inaccurate explanation.

The resolution has nothing to do with MIDI data transmission speed and
those ticks are also another thing, than those ticks that are the
minimal selected sequencer quantisation, IOW the quantisation you get,
if you don't quantise.

The timer resolution is important for sync precision of the hardware,
since the IRQs are more flexible, the more ticks there are.

The best choice by theory would be instead of many ticks, to use "full"
tickless, but it could cause issues.

I get less MIDI jitter when using 1000000000Hz instead of 1000Hz. I
heard the pre-build kernels now tend to provide hr timer loaded by
default, but no 1000Hz, just 250Hz or whatever is a common value.

Re: [Qtractor-devel] System lock-up on MIDI clocking

[oli_kester <oli...@zo...>]

Thanks for the responses Ralf, they've pointed me in the right direction :)

What solved this for me was setting the queue timer resolution to "system timer (1000Hz)". When I switch to "HR timer (1000000000Hz)" , which I presume is the default, the system locks up after a short play time - even in the first bar! I'm not surprised this is what was causing issues - a billion Hz is gigantic! Surprised any computer can send MIDI signals that fast. 

Would someone be kind enough to explain (or link to an explanation of) what exactly this setting affects, and what the other settings "PCM capture" etc do? I have a vague idea looking at the name, but I'd like to know for sure. 

To test stability, I've just left the sync running for 2773 bars, at 120bpm! This included lots of pause/play spamming on both the synced device and inside qtractor, along with some recording. No hiccups :)

You may also be pleased to know that sync actually seems to be working marginally better than in Ardrour! For some reason in Ardour (might be a setting), the playback doesn't start with a play, but a pause THEN play. Qtractor works as you'd expect :)

I actually like the portability of storing patterns on hardware - until my RY10 decides to forget them all that is! Worse still, backup is to cassette tape only..... 

I still adore the thing :P

---- On Thu, 07 Aug 2014 22:32:12 +0000 Ralf Mardorf <ral...@al...> wrote ---- 


On Thu, 2014-08-07 at 22:43 +0200, Ralf Mardorf wrote: 
> The only issue seems to be, that the RX21 only follow song positions, 
> when playing or manually moving the play head, but in loop play it's 
> ignored. 
 
I suspect that song position pointer only is send when the play head is 
moved to a position and when starting, but during playing just MIDI 
clock is sent. I didn't check this, but if so, for loop play it should 
be send each time the loop is at the left locator position. 
 
> Qtractor as sync master and a YAMAHA RX21 as sync slave (both tested, 
> RX21 CLOCK: INTERNAL and CLOCK: MIDI) seems to work correctly. 
 
With clock set to internal, song position pointer does work, for correct 
sync there likely is the need to choose MIDI ;). JFTR syncing different 
MIDI gear to each other is a PITA, for some devices combinations it does 
work and for other devices combinations it doesn't work. It has nothing 
to do with bad software and/or bad stand alone devices, it's related to 
the MIDI specifications, we once talked about this at LAD or perhaps 
LAU. If Qtractor does freeze a machine it's a bug, but as already 
pointed out, I don't experience this bug on my machine. 
 
IMO using a sequencer is more comfortable, than using menus of drum 
machines, so using a drum machine as a MIDI drum sound player IMO is 
better, than to sync the machines sequencer with the computer's 
sequencer. 
 
 
------------------------------------------------------------------------------ 
Infragistics Professional 
Build stunning WinForms apps today! 
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future. 
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk 
_______________________________________________ 
Qtractor-devel mailing list 
Qtr...@li... 
https://lists.sourceforge.net/lists/listinfo/qtractor-devel 

[Qtractor-devel] Qtractor 0.6.2 and fluidsynth 1.1.6

[Ralf M. <ral...@al...>]

Track 1 MIDI ch 1 fluidsynth dssi = ok
+ Track 2 MIDI ch 2 fluidsynth dssi = Qtractor crashes
               ^^^^
Track 1 MIDI ch 1 fluidsynth dssi = ok
+ Track 2 MIDI ch 1 fluidsynth dssi = Qtractor crashes
               ^^^^

Re: [Qtractor-devel] Qtractor 0.6.2 and fluidsynth 1.1.6

[Ralf M. <ral...@al...>]

On Sun, 2014-08-10 at 21:52 +0200, Ralf Mardorf wrote:
> Track 1 MIDI ch 1 fluidsynth dssi = ok
> + Track 2 MIDI ch 2 fluidsynth dssi = Qtractor crashes
>                ^^^^

A new song and now it works :(.

[Qtractor-devel] Qtractor 0.6.2 audio and MIDI output issue

[Ralf M. <ral...@al...>]

Hi,

before I added 24 MIDI and 8 audio tracks "Dedicated MIDI player
outputs" and for plugins "Dedicated audio outputs" was enabled, then I
disabled both, but the "empty song" doesn't get rid of the dedicated
audio outputs. How can I get rid of those audio outputs?

I need more than 16 MIDI output channels, but I can't add a new MIDI
bus, the create button is shadowed. How can I get several MIDI out
buses? "Dedicated MIDI player outputs" seems not to do the trick either.

Is there a way to send MIDI data from several tracks to the synth plugin
of one track?

Is there a way to get sub groups for mixing the audio signals of MIDI
and audio tracks?

A long time ago I used cheap tricks to e.g. get sub groubs, but those
tricks always caused issues.

Muting clips still isn't possible, resp. only by using the automation,
but not by a simply mouse action?

Regards,
Ralf

[Qtractor-devel] [solved] Setting up an empty Qtractor default session - #1 How to disable "Auto connect" for "Audio Master"?

[Ralf M. <ral...@al...>]

My bad, I disconnected the audio connections, saved the Qtractor
session, closed Qtractor and opened it by loading the session file, no
unwanted auto connections anymore. IOW by accident I saved the
connections.

[Qtractor-devel] Setting up an empty Qtractor default session - #1 How to disable "Auto connect" for "Audio Master"?

[Ralf M. <ral...@al...>]

Hi :)

after not using Linux pro-audio for a while, I'll give it another
chance. First I'll set up an empty default session, with a few empty
MIDI and audio tracks.

Before adding any track I already encountered an old issue. I don't know
how to disable auto connection for the audio IOs.

This is what I did until now:

[rocketmouse@archlinux ~]$ jackd -dalsa -dhw:0 -r48000 -p256 -n2
jackdmp 1.9.9.5
[rocketmouse@archlinux ~]$ qtractor -v
Qt: 4.8.6
Qtractor: 0.6.2
[rocketmouse@archlinux ~]$ qtractor

1. File > Properties
Name:      arch2014
Directory: /home/music/arch2014

2. Save
File name: arch2014

3. View > Options...
General
Session: nothing is checked
         Default session file format: XML Default (*.qtr)
Options: Checked are: Confirm removals
                      Show complete path of session files
                      Auto-remove audio peak files
                      Keep tool windows always on top
         Number of recent files: 5
Transport: Transport mode: None
           Loop recording mode (takes): None
Audio
Capture/Export
File type: WAV Microsoft
Sample format: Float 32-Bit
Playback
Nothing is checked, Sample-rate convert type: Sinc (Best Quality)
Metronome
Nothing is checked
MIDI
Capture/Export
File format: SMF Format 1
Quantize: None
Playback
Queue timer (resolution): HR timer (1000000000 Hz)
Checked: Dedicated MIDI player outputs
Control
MMC: None   SPP: None   Clock: None
Nothing is checked
Metronome
Nothing is checked
Display
Time display format: BBT   Base font size: (default)
Meters
Audio: 10 dB #28a028   MIDI: Over #a0a028
Messages
Sand Serif 10, Checked: Messages limit: 1000 lines
Transport
Nothing is checked
Dialogs
Checked: Use native dialogs
Logging
Nothing is checked
Plugins
Instruments
Checked: Dedicated audio outputs
Editor
Checked: Open plugin's editor (GUI) by default
Experimental
Checked: Dummy VST plugin scan (RECOMMENDED)

3. Save, Closed ...
[rocketmouse@archlinux ~]$ qtractor /home/music/arch2014/arch2014.qtr

4. View > Busses
Audio Master: Unchecked and updated "Auto connect" = Nothing is checked
              Mode: Duplex   Channels: 2
MIDI Master : Nothing is checked
              Mode: Duplex

5. Save, Closed ...
[rocketmouse@archlinux ~]$ qtractor /home/music/arch2014/arch2014.qtr

_Audio channels still are auto connected_

Regards,
Ralf

Re: [Qtractor-devel] System lock-up on MIDI clocking

[Ralf M. <ral...@al...>]

On Thu, 2014-08-07 at 22:43 +0200, Ralf Mardorf wrote:
> The only issue seems to be, that the RX21 only follow song positions,
> when playing or manually moving the play head, but in loop play it's
> ignored.

I suspect that song position pointer only is send when the play head is
moved to a position and when starting, but during playing just MIDI
clock is sent. I didn't check this, but if so, for loop play it should
be send each time the loop is at the left locator position.

> Qtractor as sync master and a YAMAHA RX21 as sync slave (both tested,
> RX21 CLOCK: INTERNAL and CLOCK: MIDI) seems to work correctly.

With clock set to internal, song position pointer does work, for correct
sync there likely is the need to choose MIDI ;). JFTR syncing different
MIDI gear to each other is a PITA, for some devices combinations it does
work and for other devices combinations it doesn't work. It has nothing
to do with bad software and/or bad stand alone devices, it's related to
the MIDI specifications, we once talked about this at LAD or perhaps
LAU. If Qtractor does freeze a machine it's a bug, but as already
pointed out, I don't experience this bug on my machine.

IMO using a sequencer is more comfortable, than using menus of drum
machines, so using a drum machine as a MIDI drum sound player IMO is
better, than to sync the machines sequencer with the computer's
sequencer.

Re: [Qtractor-devel] System lock-up on MIDI clocking

[Ralf M. <ral...@al...>]

Hi Oliver,

Qtractor as sync master and a YAMAHA RX21 as sync slave (both tested,
RX21 CLOCK: INTERNAL and CLOCK: MIDI) seems to work correctly.

[rocketmouse@archlinux ~]$ uname -a
Linux archlinux 3.10.47-rt50-1-rt-lts #1 SMP PREEMPT RT
Thu Jul 17 23:36:36 CEST 2014 x86_64 GNU/Linux
[rocketmouse@archlinux ~]$ qtractor -v
Qt: 4.8.6
Qtractor: 0.6.2
[rocketmouse@archlinux ~]$ jackd -dalsa -dhw:0 -r48000 -p256 -n2
jackdmp 1.9.9.5

Readable client
  129:Qtractor, 1:Control
is connected to writeable client
  16:RME AIO_579bcc, 0:HDSPMx579bcc MIDI 1
connected to MIDI in of a YAMAHA RX21.

Qtractor View > Options... (F12) > MIDI tab

File format: SMF Format 1
Quantize: None
Queue timer (resolution): HR timer (1000000000 Hz)
[ ] Dedicated MIDI player outputs
MMC: Duplex  Device: (Any)    SPP: Duplex  Clock: Output
[x] Dedicated MIDI control input/output
[ ] Enable MIDI metronome

However, I only made a very quick and short test, without listening, I
just watched the sync. Sync seems to be ok, it at least is visible ok,
perhaps not when listening, anyway, the computer stays responsive, no
freeze, or other issues.

The only issue seems to be, that the RX21 only follow song positions,
when playing or manually moving the play head, but in loop play it's
ignored.

https://archive.org/stream/synthmanual-yamaha-rx-21-owners-manual/yamaharx-21ownersmanual#page/n57/mode/2up

Regards,
Ralf

[Qtractor-devel] System lock-up on MIDI clocking

[oli_kester <oli...@zo...>]

Hi again

So I've been using qtractor for a while now and know my way around it rather well - still surprises me how lightweight it is for a capable piece of software!

Anyway today I've been trying to use it to MIDI clock a drum machine, with sadly devastating results :(

I've previously used Ardour to MIDI clock some drum machines I own, and it works really well. In qtractor, however when I try and do this a system-wide lockup occurs. I've had no other program do this to me before - I can't even open a terminal to kill the process. The only way out is to hold down the power button for a hard reset...

The drum machine is an Korg ER-1, with MIDI clock enabled, and I've tried various combinations of settings inside qtractor. Interestingly with SPP output enabled, when I press play no lockup occurs and the play button lights up on the ER-1 - but the sequence doesn't start playing. It only works with MIDI clock set to output - the drums start playing as you'd expect... but after a few bars the whole PC, including audio, freezes. 

This problem occurs both in an empty project, and inside the one in which I want to record the drums. 

Some system details - 

--------
  p, li { white-space: pre-wrap; }  qtractor Version: 0.6.2 Build: Jul 10 2014 15:17:05


M-Audio 192 PCI interface - > Korg Electribe ER-1 



$ cat /proc/version
Linux version 3.13.0-32-lowlatency (buildd@kissel) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #57-Ubuntu SMP PREEMPT Tue Jul 15 04:08:59 UTC 2014

$ cat /etc/issue
Ubuntu 14.04.1 LTS \n \l

$ jackd --version
jackdmp 1.9.10

--------

Thanks again for your always first-class assistance :)

Oliver

Re: [Qtractor-devel] Perception - Was: Measuring the acoustical characteristics of my studio using FLOSS software?

[Ralf M. <ral...@al...>]

On Wed, 2014-08-06 at 03:57 +0200, Ralf Mardorf wrote:
> PS: I see colours, when I listen to music, but I wouldn't call it real
> synesthesia.

PPS: I don't see always the same colour for an oboe playing one tone,
but I see coloured films about the content. It's a pity that e.g. for
Qtractor it's impossible to select a wanted colour for tracks, it's only
possible to select a vague colour. For me, it would be very informing,
if I really would get a colour of choice.

[Qtractor-devel] [ANN] Qtractor 0.6.2 - The Boson Walk Beta is out!

[Rui N. C. <rn...@rn...>]

So it's summer, they say.

White bright and light pastel colors sparkling on every corner and turn. 
Cheesy and silly season, they say. Alas, southerners don't apply. Sorry 
about that. Of course I mean the hemisphere, obviously.

For whom it might concern, all anxiety has come to an end.

Indeed.

It all relates back to this last May 3, when a not-so-formal meeting 
(aka. workshop) took place while during LAC2014@ZKM-Karlsruhe, where 
some pertinent and undeniable requests were dodged and framed to a 
"soonish" implementation. And guess what?

Yup, the "soonish" are no more, or so I think.

   Qtractor 0.6.2 (boson walk beta) is out!

Perhaps an additional word is due though, about the riddling code-names 
that are branding the post-TYOQA beta releases. They have no personal 
nor logical sense, I assure you. Perfectly arbitrary now. Everything in 
life and the universe is way more unconventional than just a name.

Without further assay.

Qtractor is an audio/MIDI multi-track sequencer application written in 
C++ with the Qt4 framework. Target platform is Linux, where the Jack 
Audio Connection Kit (JACK) for audio and the Advanced Linux Sound 
Architecture (ALSA) for MIDI are the main infrastructures to evolve as a 
fairly-featured Linux desktop audio workstation GUI, specially dedicated 
to the personal home-studio.

Release highlights:
* Plugins activation MIDI controller / automation (NEW)
* LV2 UI Idle and Show (>= Qt5) interface support (NEW)
* Discrete editing of automation curve node velues (NEW)
* Missing audio/MIDI files and plugins warning message (NEW)
* MIDI note drawing on tempo-map changes (FIX)
* Automation curves re-adjusted to tempo-map changes (FIX)


Website:
   http://qtractor.sourceforge.net

Project page:
   http://sourceforge.net/projects/qtractor

Downloads:
   http://sourceforge.net/projects/qtractor/files

- source tarball:
   http://download.sourceforge.net/qtractor/qtractor-0.6.2.tar.gz

- source package (openSUSE 13.1):
 
http://download.sourceforge.net/qtractor/qtractor-0.6.2-12.rncbc.suse131.src.rpm

- binary packages (openSUSE 13.1):
 
http://download.sourceforge.net/qtractor/qtractor-0.6.2-12.rncbc.suse131.i586.rpm
 
http://download.sourceforge.net/qtractor/qtractor-0.6.2-12.rncbc.suse131.x86_84.rpm

- quick start guide & user manual (severely outdated, see wiki):
   http://download.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf

- wiki (help wanted!):
   http://sourceforge.net/p/qtractor/wiki/

Weblog (upstream support):
   http://www.rncbc.org

License:
   Qtractor is free, open-source software, distributed under the terms 
of the GNU General Public License (GPL) version 2 or later.

Change-log:
- Prevent linear and spline automation curve modes for all integer 
valued subjects. Also, make sure those values are rounded to the nearest 
integer away from zero.
- Fixed save of LV2 Presets for plugins with state files.
- A man page has beed added (making up Gürkan Sengün's work on debian, 
thanks).
- When moving plugins by eg. drag-and-dropping across tracks, automation 
curves were being left behind, maybe leading to unpredictable mistaken 
behavior. Hopefully, not anymore.
- Translations install directory change.
- Automation curves are now automatically re-adjusted to tempo map node 
changes (after a ticket by Holger Marzen, thanks).
- Audio/MIDI files or plugins found missing on session load are now 
subject for an explicit modal warning message and prompt for an 
immediate session backup salvage.
- Changing instrument plugin programs is now an undo/redo-able command 
operation, especially for DSSI but also for plugins that come with the 
LV2 Programs interface extension support 
(http://kxstudio.sourceforge.net/ns/lv2ext/programs).
- Drawing, selecting and/or resizing of MIDI note events that extend 
across tempo/time-signature changes is now made a bit more correctly 
over the MIDI clip editor (aka. piano-roll), especially regarding to 
current snap-to-beat setting (after an outstanding ticket by yubatake, 
thanks).
- Once again, audio frame/MIDI time drift correction has been slightly 
refactored to improve MIDI input monitor and timing.
- Discrete automation curve node values may now be edited via a 
numerical entry floating spin-box on double-click (as yet another 
request by AutoStatic aka. Jeremy Jongepier, thanks).
- Pressing shift/ctrl keyboard modifiers while double-clicking on a 
plugin list entry now briefly reverses the current 
View/Options.../Plugins/Editor/Open plugin's editor (GUI) by default 
option preference.
- Fixed an old crash lurker when switching output buses that implied a 
change on the number of audio channels, while on tracks that have 
(auto-)monitor turned on and at least one active plugin in chain (yet 
another ticket by AutoStatic aka. Jeremy Jongepier, thanks).
- MIDI Controller assignment (aka MIDI learn) and/or automation of 
plugins (de)activation state has been added (as requested by AutoStatic 
aka. Jeremy Jongepier, thanks).
- LV2 UI Idle and Show interfaces support added.
- Allow the build system to include an user specified LDFLAGS (patch by 
Alessio Treglia aka. quadrispro, thanks).


See also:
   http://www.rncbc.org/drupal/node/795


Enjoy && have (lots of) fun.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...

Re: [Qtractor-devel] lv2 issues

[oli_kester <oli...@zo...>]

Thanks for that Rui, I've sorted this now :-)

For the benefit of the archives, the solution involved - 
Installing the "calf-plugins-git" package from the kxstudio repos
Installing the "suil-libs" package from the kxstudio repos 
(I already had "libsuil0-0" installed, they are now side-by-side)

Remove and reinstate all lv2 plugin root folders from qtractor's settings
I had already tried the "calf-plugins-git" package, so I think "suil-libs" is what solved the problem. 

Thanks again
Oliver

---- On Thu, 22 May 2014 18:25:25 +0000 Rui Nuno Capela<rn...@rn...> wrote ---- 


On 05/22/2014 11:07 AM, oli_kester wrote: 
> Hi, I've another issue in qtractor 0.61 for you - this time on Xubuntu 
> 14.04. It's around lv2 plugins, and general instability. LADSPA plugins 
> work very reliably. 
> 
> I've experienced issues with the following plugins, all lv2 - 
> 
> * Hang, then crash on loading 'amsynth' 
> * Crash on plugin UI close on 'abGate' 
> * Immediate crash on loading any of the calf plugins :-( 
> * Immediate crash on loading any of the guitarix 'Gx' plugins :-( 
> * Immediate crash on loading 'Beat Slicer' from avwlv2.sourceforge.net 
> * Immediate crash on loading 'Nordic Meter' from gareus.org 
> * Immediate crash on loading 'True Peak Meter' from gareus.org 
> 
> Many of these aren't essential to me, just randomly testing a few I 
> happen to have installed. I'd love to have the calf plugins working, but 
> I've read on kxstudio somewhere that they removed plugin support - so 
> would this no longer be possible? Do I have to use Calf Rack? I'd like 
> to keep the automation... 
> 
> I've unchecked all of the experimental plugin settings for safety, which 
> hasn't made any difference. Interestingly, the following is dumped in 
> the message box on occasion, I think when loading track properties - 
> 
> 
> (qtractor:21421): Gtk-CRITICAL **: IA__gtk_widget_get_direction: 
> assertion 'GTK_IS_WIDGET (widget)' failed 
> 
> 
> (qtractor:21421): Gtk-CRITICAL **: IA__gtk_widget_get_direction: 
> assertion 'GTK_IS_WIDGET (widget)' failed 
> 
 
calf upstream are notorious to crash qtractor on close or even anytime 
the gui is shown up. the above gtk errors are one of many symptoms of 
calf breakage ever since its in-process gtk gui takes chances on libsuil 
to get shown up on non-gtk hosts. 
 
kxstudio (or is it distrho?) used to ship modified versions that 
presents a lv2_external_ui extension interface and is known to work a 
lot better in qtractor. 
 
if you're actually using the later then i must conclude that something 
is broken on either your system or qtractor or lv2 or suil or calf or 
all at once. 
 
however all the meters.lv2 from rgareus play pretty well here though. 
there must be something broken at your side and i can figure it out what 
then. 
 
> 
> I also get this more rarely (note the colour, it's beige if the list 
> resets it) - 
> 
> 
> error: failed to expand CURIE `pprops:hasStrictBounds' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `pprops:hasStrictBounds' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `units:unit' 
> 
> error: failed to expand CURIE `units:db' 
> 
> error: attempt to add quad with NULL field 
> 
> 
> Or - 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `param:OscillatorControls' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `pprops:hasStrictBounds' 
> 
> error: attempt to add quad with NULL field 
> 
> error: failed to expand CURIE `pprops:hasStrictBounds' 
> 
> error: attempt to add quad with NULL field 
> 
> 
> I presume these would be due to erroneous plugins. Would it be worth me 
> installing the debugging symbols to investigate further? Or is this just 
> a matter of uninstalling all the bad plugins - I've got all the plugin 
> packs from the Ubuntu / kxstudio repos. Can anyone recommend a decent, 
> reliable source that gives me most common functions (decent delay, 
> reverb, filters etc)? Or should I just be using LADSPA? 
> 
 
ask for the latest from kxstudio and/or distrho. ask for the specific 
lv2_external_ui implementations of the calf suite. 
 
hth. 
cheers 
-- 
rncbc aka Rui Nuno Capela 
rn...@rn... 
 
------------------------------------------------------------------------------ 
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE 
Instantly run your Selenium tests across 300+ browser/OS combos. 
Get unparalleled scalability from the best Selenium testing platform available 
Simple to use. Nothing to install. Get started now for free." 
http://p.sf.net/sfu/SauceLabs 
_______________________________________________ 
Qtractor-devel mailing list 
Qtr...@li... 
https://lists.sourceforge.net/lists/listinfo/qtractor-devel 

Re: [Qtractor-devel] lv2 issues

[Rui N. C. <rn...@rn...>]

On 05/22/2014 07:25 PM, Rui Nuno Capela wrote:
> there must be something broken at your side and i can figure it out what

better said, i can't

byee
-- 
rncbc aka Rui Nuno Capela
rn...@rn...

Re: [Qtractor-devel] lv2 issues

[Rui N. C. <rn...@rn...>]

On 05/22/2014 11:07 AM, oli_kester wrote:
> Hi, I've another issue in qtractor 0.61 for you - this time on Xubuntu
> 14.04. It's around lv2 plugins, and general instability. LADSPA plugins
> work very reliably.
>
> I've experienced issues with the following plugins, all lv2 -
>
>   * Hang, then crash on loading 'amsynth'
>   * Crash on plugin UI close on 'abGate'
>   * Immediate crash on loading any of the calf plugins :-(
>   * Immediate crash on loading any of the guitarix 'Gx' plugins :-(
>   * Immediate crash on loading 'Beat Slicer' from avwlv2.sourceforge.net
>   * Immediate crash on loading 'Nordic Meter' from gareus.org
>   * Immediate crash on loading 'True Peak Meter' from gareus.org
>
> Many of these aren't essential to me, just randomly testing a few I
> happen to have installed. I'd love to have the calf plugins working, but
> I've read on kxstudio somewhere that they removed plugin support - so
> would this no longer be possible? Do I have to use Calf Rack? I'd like
> to keep the automation...
>
> I've unchecked all of the experimental plugin settings for safety, which
> hasn't made any difference. Interestingly, the following is dumped in
> the message box on occasion, I think when loading track properties -
>
>
> (qtractor:21421): Gtk-CRITICAL **: IA__gtk_widget_get_direction:
> assertion 'GTK_IS_WIDGET (widget)' failed
>
>
> (qtractor:21421): Gtk-CRITICAL **: IA__gtk_widget_get_direction:
> assertion 'GTK_IS_WIDGET (widget)' failed
>

calf upstream are notorious to crash qtractor on close or even anytime 
the gui is shown up. the above gtk errors are one of many symptoms of 
calf breakage ever since its in-process gtk gui takes chances on libsuil 
to get shown up on non-gtk hosts.

kxstudio (or is it distrho?) used to ship modified versions that 
presents a lv2_external_ui extension interface and is known to work a 
lot better in qtractor.

if you're actually using the later then i must conclude that something 
is broken on either your system or qtractor or lv2 or suil or calf or 
all at once.

however all the meters.lv2 from rgareus play pretty well here though. 
there must be something broken at your side and i can figure it out what 
then.

>
> I also get this more rarely (note the colour, it's beige if the list
> resets it) -
>
>
> error: failed to expand CURIE `pprops:hasStrictBounds'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `pprops:hasStrictBounds'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `units:unit'
>
> error: failed to expand CURIE `units:db'
>
> error: attempt to add quad with NULL field
>
>
> Or -
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `param:OscillatorControls'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `pprops:hasStrictBounds'
>
> error: attempt to add quad with NULL field
>
> error: failed to expand CURIE `pprops:hasStrictBounds'
>
> error: attempt to add quad with NULL field
>
>
> I presume these would be due to erroneous plugins. Would it be worth me
> installing the debugging symbols to investigate further? Or is this just
> a matter of uninstalling all the bad plugins - I've got all the plugin
> packs from the Ubuntu / kxstudio repos. Can anyone recommend a decent,
> reliable source that gives me most common functions (decent delay,
> reverb, filters etc)? Or should I just be using LADSPA?
>

ask for the latest from kxstudio and/or distrho. ask for the specific 
lv2_external_ui implementations of the calf suite.

hth.
cheers
-- 
rncbc aka Rui Nuno Capela
rn...@rn...

[Qtractor-devel] lv2 issues

[oli_kester <oli...@zo...>]

Hi, I've another issue in qtractor 0.61 for you - this time on Xubuntu 14.04. It's around lv2 plugins, and general instability. LADSPA plugins work very reliably. 

I've experienced issues with the following plugins, all lv2 - 
Hang, then crash on loading 'amsynth'
Crash on plugin UI close on 'abGate'
Immediate crash on loading any of the calf plugins :-(
Immediate crash on loading any of the guitarix 'Gx' plugins :-(
Immediate crash on loading 'Beat Slicer' from avwlv2.sourceforge.net
Immediate crash on loading 'Nordic Meter' from gareus.org
Immediate crash on loading 'True Peak Meter' from gareus.org
Many of these aren't essential to me, just randomly testing a few I happen to have installed. I'd love to have the calf plugins working, but I've read on kxstudio somewhere that they removed plugin support - so would this no longer be possible? Do I have to use Calf Rack? I'd like to keep the automation...

I've unchecked all of the experimental plugin settings for safety, which hasn't made any difference. Interestingly, the following is dumped in the message box on occasion, I think when loading track properties - 
  p, li { white-space: pre-wrap; }  

 (qtractor:21421): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
 

 (qtractor:21421): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed


I also get this more rarely (note the colour, it's beige if the list resets it) - 



error: failed to expand CURIE `pprops:hasStrictBounds'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `pprops:hasStrictBounds'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `units:unit'
 error: failed to expand CURIE `units:db'
 error: attempt to add quad with NULL field


Or - 

 
error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `param:OscillatorControls'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `pprops:hasStrictBounds'
 error: attempt to add quad with NULL field
 error: failed to expand CURIE `pprops:hasStrictBounds'
 error: attempt to add quad with NULL field


I presume these would be due to erroneous plugins. Would it be worth me installing the debugging symbols to investigate further? Or is this just a matter of uninstalling all the bad plugins - I've got all the plugin packs from the Ubuntu / kxstudio repos. Can anyone recommend a decent, reliable source that gives me most common functions (decent delay, reverb, filters etc)? Or should I just be using LADSPA?

Thanks

Oliver

Re: [Qtractor-devel] An easy one

[Ralf M. <ral...@al...>]

On Thu, 2014-05-08 at 00:32 +0000, oli_kester wrote:
> I clicked "hide main menu" button. Now how the hell do I get it back?

Ctrl+M if you're using Qtractor.

Or by using an editor, in ~/.config/rncbc.org/Qtractor.conf edit
        View\Menubar=true