Re: [ubuntu-studio-users] Anomalous handling of tempo changes in Qtractor

2017-01-03 Thread David Sumbler 
On Tue, 2017-01-03 at 17:26 +0100, Ralf Mardorf wrote:
> Hi,
> 
> you should get in contact with Rui, the developer of Qtractor.
> 
> There's only a devel list, but it's for user requests, too.
> 
> https://lists.sourceforge.net/lists/listinfo/qtractor-devel
> 
> Regards,
> Ralf

Thanks for that suggestion - I would have hesitated to contact that
list as I am not a developer nor ever likely to be, I'm afraid!

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Anomalous handling of tempo changes in Qtractor

2017-01-03 Thread David Sumbler 
For some reason, my version of the tempo map in my previous email got
garbled, even though it was formatted with spaces.  Perhaps this will
get through better:

Bar  Time Tempo Marker
  1  1.1.000 104.0 4/4
  4  4.1.000  95.0 4/4
  4  4.2.000  86.0 4/4
  4  4.3.000  77.0 4/4
  5  5.1.000 104.0 4/4
 13 13.1.000  97.0 4/4
 13 13.2.000  90.0 4/4
 13 13.3.000  83.0 4/4
 13 13.4.500 104.0 4/4
 14 14.2.000 109.0 4/4

David

On Tue, 2017-01-03 at 15:48 +, David Sumbler wrote:
> Bar  Time     Tempo Marker
>   1  1.1.000 104.0 4/4
>   4  4.1.000  95.0 4/4
>  
> 4  4.2.000  86.0 4/4
>   4  4.3.000  77.0 4/4
>   5  5.1.000 104.0 4/4
>  13
> 13.1.000  97.0 4/4
>  13 13.2.000  90.0 4/4
>  13 13.3.000  83.0 4/4
>  13
> 13.4.500 104.0 4/4
>  14 14.2.000 109.0 4/4

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

[ubuntu-studio-users] Anomalous handling of tempo changes in Qtractor

2017-01-03 Thread David Sumbler 
I have been experimenting with Qtractor, and I find that its handling
of tempo changes in imported midi files is rather odd (to say the
least).  My first realization was that it seems only to allow tempo
changes at the start of a bar.  Well, OK, I can probably live with that
if I start a project by recording new stuff into Qtractor, but it's no
good when importing midi.

The reason I am writing this is not to have a moan about Qtractor, but
because it may be that there is some setting that I need to change
which would correct this behaviour, although I have not managed to find
anything yet using trial and error.

To give one specific example, I have a midi file of a saxophone
quartet.  The original midi file was generated by Lilypond, which is a
music engraving program.  The file was then converted to csv using
midicsv, edited to produce some needed tempo changes, ritardandos etc.,
and then converted back to midi using csvmidi.

The file plays well in timidity, and I was able to generate an
acceptable mp3 from it.

But if I import the file (or one of its 4 tracks) into Qtractor the
tempo map (and therefore the performance) is complete nonsense.

Firstly, even though the tempo map (see below) gives the position as
Qtractor sees it of the tempo change accurate to 1/1000 of a beat, this
is completely pointless if Qtractor insists that the changes all happen
precisely on the first beat of the bar.  Secondly, the bar in question
is not even the correct one in most cases.  And some tempo changes are
ignored altogether where there are several close to each other.

The first 10 lines of the tempo map as shown by Qtractor are these:

Bar  Time     Tempo Marker
  1  1.1.000 104.0 4/4
  2  2.1.000  77.0 4/4
  3  3.1.000 104.0 4/4
  6  6.1.000 109.0 4/4
  7  7.1.000 134.0 4/4
  8  8.1.000 159.0 4/4
  9  9.1.000 189.0 4/4
 10 10.1.000 200.0 4/4
 11 11.1.000 104.0 4/4
 20 20.1.000  84.0 4/4

If Qtractor were reading the files correctly, they should look like
this:

Bar  Time     Tempo Marker
  1  1.1.000 104.0 4/4
  4  4.1.000  95.0 4/4
 
4  4.2.000  86.0 4/4
  4  4.3.000  77.0 4/4
  5  5.1.000 104.0 4/4
 13
13.1.000  97.0 4/4
 13 13.2.000  90.0 4/4
 13 13.3.000  83.0 4/4
 13
13.4.500 104.0 4/4
 14 14.2.000 109.0 4/4

Even if Qtractor does not like so many tempo changes in one bar, I cannot see 
why it puts, for instance, the tempo change which should happen at bar 14 at 
the start of bar 6.  The tempo change Qtractor shows for bar 20 should actually 
occur in bar 50!

The fact that the tempo map quotes "Time" to 3 decimal places of a beat 
suggests that Qtractor ought to accept a change at any time.  Perhaps the 
design of the tempo map window is ahead of the actual capabilities of the 
program, but I hope that there is something I can alter which will change 
things.

On the other hand, if I try to add new items in the Tempo Map window, it does 
seem that Qtractor will only allow 1 marker in a bar.  Furthermore if I specify 
a position which is not the beginning of the bar, then Qtractor insists on 
putting it on the first beat of the following bar.

I emphasize that timidity reads this file perfectly satisfactorily and responds 
to all the tempo changes correctly.

Can anyone make any useful comments or suggestions about this?

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect solved (I think!)

2016-12-28 Thread David Sumbler 
I seem to have solved this problem.

In the Settings dialogue of qjackctl I changed MIDI driver from "raw"
to "seq", and now I can connect the keyboard to tractor etc.  It seems
to work, although I have not done very much with it yet.

I confess I hadn't tried messing about with this setting before,
because I don't remember ever having altered it, yet the keyboard used
to work OK with the computer.  But logically, I suppose it must have
been changed at some point.

Anyway, thanks for all the help you have given.  And I'm sorry to have
made an issue out of something that was, apparently, so simple to fix.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-27 Thread David Sumbler 
On Tue, 2016-12-27 at 17:57 +0100, Ralf Mardorf wrote:
> An example seems to work on my machine:
> 
>   $ amidi -l
>   Dir DeviceName
>   IO  hw:0,0HDSPMx579bcc MIDI 1
>   IO  hw:3,0,0  nanoKONTROL MIDI 1
> 
>   $ pkill -9 jack; pkill a2j
> 
>   $ jackd -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e‬ &
> qjackctl
> 
> In QjackCtl's ALSA tab the device names are the same as displayed by
> the above amidi command, but in the MIDI tab the names are
> 
>   system  system
> midi_capture_1  midi_playback_1
> midi_capture_2  midi_playback_2
> 
> Qtractor only appears in the ALSA tab. While connecting HDSPM and
> nanoKONTROL doesn't work directly in the ALSA tab, connecting MIDI
> Through with Qtractor works. It requires some trail and error, I
> don't
> remember how to use it at the moment. It's a long time ago I used
> Linux
> for MIDI. However, IIRC a2j... is only needed if
> 
> - you are using jack2 with external synth and you want to reduce MIDI
>   jitter by using -Xalsarawmidi
> 
> - you are not necessarily using -Xalsarawmidi, but you are using
> Linux
>   apps, that only support jack MIDI and not ALSA MIDI, while other
> apps
>   only support ALSA MIDI and you want to connect jack and ALSA MIDI
> apps
> 
> If you only want to use ALSA MIDI, no -Xalsarawmidi and no jack MIDI
> apps, simply run
> 
>   $ pkill -9 jack; pkill a2j
>   $ jackd -dalsa -r48000 -p256 & qjackctl
> 
> then you should be able to connect everything by the ALSA tab without
> issues.

I get:

david@eros:~$ jackd -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e‬ &
qjackctl
[1] 6201
[2] 6202
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
a2jmidid: invalid option -- '�'
Usage: a2jmidid [-j jack-server] [-e | --export-hw] [-u]
Defaults:
-j default
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-
|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server

and similar results with the

jackd -dalsa -r48000 -p256 & qjackctl

command.

Nothing appears in the MIDI tab of qjackctl: as ever, the keyboard
appears as both an input and output device in the ALSA tab, but can't
acrually be connected to anything else.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Converting a recorded track to a timing track

2016-12-27 Thread David Sumbler 
On Tue, 2016-12-27 at 17:15 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 15:29:08 +0000, David Sumbler wrote:
> > 
> > I don't really see how an "artificial" pulse can sound more natural
> > than a human one
> In the context of using a sequencer with beats and bars, it sounds
> more
> natural, since it's nearly impossible to fit pulse played music into
> the resolution.
> 
> Another solution would be to record even MIDI tracks by ignoring a
> sequencers measure and tempo, quasi use MIDI in the same way as a
> tape
> recorder.

Yes, that's what I do, and what I intend to do (once I can get the
keyboard linked to my computer again!)

> > What I wanted to acheive was simply to get the midi beats to
> > correspond
> > (roughly) to the actual beats of the music itself - rits,
> > accelerandos
> > and all.  The purpose of this is just to make it easier navigating
> > in,
> > say, qtractor: if I want to make a change at beat 3 of bar 246 then
> > it
> > will be easy to find.
> Use markers. I don't remember in what way markers are supported by
> Qtractor, but usually you could set markers. Name markers "bridge",
> "refrain", "foo" or even "bar_1", "bar_2" and "bar_n".
> 
> > 
> > As I said, I can probably do this with a Python program, but I
> > didn't
> > want to spend time writing that if there is something available
> > already.  The program would need a track consisting only of beats.
> >  This click-track could be recorded before or after the first track
> > of
> > actual music has been recorded - the pros and cons of that choice
> > have
> > nothing to do with what I wanted to do with it.  I wasn't
> > suggesting
> > that I would necessarily want to play by trying to follow an
> > artificial
> > click track: the click track could be recorded before or after the
> > recording of one or more music tracks.
> > 
> > Anyway, thanks for your interest and comments.
> I guess we understand you correctly, but you misunderstand us.
> 
> Regards,
> Ralf
> 
> 

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-27 Thread David Sumbler 
On Tue, 2016-12-27 at 16:20 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 15:06:03 +0000, David Sumbler wrote:
> > 
> > As for audio related auto-starts, do you mean items in /etc/rcS.d ?
> >  The only relevant item there is alsa-utils, which I assume I need.
> I'm thinking of pulseaudio, jackdbus and what ever else could be
> auto-started. I guess those auto-starts happen for the user, when
> starting a user session. Apropos /etc/rcS.d., what release are you
> using?
> 
>   lsb_release -d
> 
> Regards,
> Ralf

> david@eros:~$ lsb_release -d
> Description:  Ubuntu 16.04.1 LTS

This is UbuntuStudio, of course.

David


-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Converting a recorded track to a timing track

2016-12-27 Thread David Sumbler 
On Mon, 2016-12-26 at 12:32 +, Pietro Bergamo wrote:
> Hi.
> In my (not so big) experience, "fluid" tempos and pulses are really
> hard to sync, as Ralf said. 
> I recorded recently a song with many tempo/measure changes and I
> couldn't find any way to make organically. In the end, I kind of
> cheated. On a rallentando, for instance, I split the measures in
> several pieces so that the metronome would count the eight notes or
> the sixteenth notes, thus making it easier to follow the pulse when
> recording. For each situation, I tried to find a (often different)
> solution. But I prepared the whole tempo track all in numbers, not
> through any kind of tapping or beat detection.
> For me, tapping the tempo (or recording an audio with it) doesn't
> work very well because I find it hard to replicate the intention I
> had when I'm playing a different instrument. I find it even harder
> when other people are going to play. An "artificial" tempo is, for
> me, always easier to predict, making the recording more precise and
> demanding less editing. In the end, I think it sounds more natural
> this way.
> But, as I said, I'm not that experienced, so maybe there are better
> solutions out there.
> I hope this was of some help.
> Best regards,
> Pietro

I don't really see how an "artificial" pulse can sound more natural
than a human one, but that isn't really an option for what I am trying
to do in any case.  The pieces I want to record are my own compositions
(dating back half a century in some cases!) and I know exactly how I
want them to be played, much as a conductor will know exactly the
variations and subtleties of tempo (s)he wants.  I don't think I shall
have any difficulty keeping with the recorded pulse - after all, once
one instrument is recorded then playing the second instrument and
staying with the first is only what musicians without a conductor do
all the time.  And, as I said, in my head I know already how this music
"should" go.

What I wanted to acheive was simply to get the midi beats to correspond
(roughly) to the actual beats of the music itself - rits, accelerandos
and all.  The purpose of this is just to make it easier navigating in,
say, qtractor: if I want to make a change at beat 3 of bar 246 then it
will be easy to find.

As I said, I can probably do this with a Python program, but I didn't
want to spend time writing that if there is something available
already.  The program would need a track consisting only of beats.
 This click-track could be recorded before or after the first track of
actual music has been recorded - the pros and cons of that choice have
nothing to do with what I wanted to do with it.  I wasn't suggesting
that I would necessarily want to play by trying to follow an artificial
click track: the click track could be recorded before or after the
recording of one or more music tracks.

Anyway, thanks for your interest and comments.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-27 Thread David Sumbler 
On Tue, 2016-12-27 at 15:01 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 13:40:15 +0000, David Sumbler wrote:
> > 
> > david@eros:~$ killall -9 jackd a2jmidid qjackctl
> > jackd: no process found
> > a2jmidid: no process found
> > qjackctl: no process found
> This kill command doesn't terminate what already might be running on
> your install ;).
> 
> > 
> > ERROR: a2j_alsa_connect_from: can't subscribe to 24:0 - Resource
> > temporarily unavailable
> > port skipped: CASIO USB-MIDI [24] (capture): CASIO USB-MIDI MIDI 1
> > ERROR: a2j_port_create: snd_seq_connect_to() for 24:0 failed with
> > error
> > -11
> > port skipped: CASIO USB-MIDI [24] (playback): CASIO USB-MIDI MIDI 1
> > no message buffer overruns
> > `default' server already active
> > Failed to open server
> I suspect something already grabbed the device, but a short test
> on my machine showed that it's unlikely an a2j vs a2jmidid issue.
> 
> Did you unplug the keyboard, reboot and then plugged in the keyboard?
> 
> Did you disable all audio related auto-starts?
> 
> Regards,
> Ralf

I just tried your first suggestion (reboot etc.) and then ran you
commands again.  Slightly different output, but the same result: the
keyboard appears in the ALSA tab but can't be connected to anything
else.

david@eros:~$ killall -9 jackd a2jmidid qjackctljackd: no process found
a2jmidid: no process found
qjackctl: no process found
david@eros:~$ jackd --sync -Xalsarawmidi -dalsa -r48000 -p256 &
a2jmidid -e & qjackctl
[1] 2416
[2] 2417
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK MIDI <-> ALSA sequencer MIDI bridge, version 8
(7383d268c4bfe85df9f10df6351677659211d1ca) built on Thu Jan  1 01:00:00
1970
Copyright 2006,2007 Dmitry S. Baikov
Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov

Bridge starting...
Using JACK server 'default'
Hardware ports will be exported.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
ERROR: a2j_jack_client_create: Cannot create jack client
ERROR: a2j_start: a2j_new() failed.
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-
|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server


As for audio related auto-starts, do you mean items in /etc/rcS.d ?
 The only relevant item there is alsa-utils, which I assume I need.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-27 Thread David Sumbler 
On Mon, 2016-12-26 at 20:33 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 19:07:41 +0000, David Sumbler wrote:
> > 
> > david@eros:~$ grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail
> > -50
> > [snip]
> > Mon Dec 26 17:09:43 2016: New client 'a2j' with PID 5142
> > Mon Dec 26 17:10:23 2016: Client 'a2j' with PID 5142 is out
> > Mon Dec 26 17:58:42 2016: Client 'qjackctl' with PID 2400 is out
> > Mon Dec 26 17:58:42 2016: Stopping jack server...
> > Mon Dec 26 17:58:42 2016: Client 'system' with PID 0 is out
> > Mon Dec 26 17:58:42 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0-
> > CASIO-USB-MIDI-MIDI-1
> > Mon Dec 26 17:58:42 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0-
> > CASIO-USB-MIDI-MIDI-1
> > Mon Dec 26 17:58:42 2016: Released audio card Audio1
> You are welcome!
> 
> $ apropos a2j
> a2j (1)  - Wrapper script to simulate a2jmidid's non-DBUS 
> behaviour though a2jmidid actually being...
> a2j_control (1)  - utility to control a2jmidid daemon
> a2jmidi_bridge (1)   - static bridge with one ALSA playback port and
> one JACK MIDI input port
> a2jmidid (1) - JACK MIDI daemon for ALSA MIDI
> 
> I'm usually running something similar to
> 
> $ killall -9 jackd a2jmidid qjackctl 
> $ jackd --sync -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e‬ &
> qjackctl
> 
> so, again, I don't know jackdbus. However, I suspect that you try to
> use QjackCtl's ALSA tab to connect MIDI I/Os. Most likely you need to
> connect MIDI I/Os by QjackCtl's MIDI tab.
> 
> Oops, indeed, running "pgrep -a a2j" is useless to see if something
> "a2j" related is active. However, the combination of "-Xalsarawmidi"
> and "a2jmidid -e‬" on my machine enforces to migrate from the ALSA
> tab
> to the MIDI tab. The connections aren't done by ALSA MIDI anymore,
> but
> instead by Jack MIDI. Perhaps you're using a similar setup.
> 
> Regards,
> Ralf

I tried the commands you mentioned.  This is what I got:

david@eros:~$ killall -9 jackd a2jmidid qjackctl
jackd: no process found
a2jmidid: no process found
qjackctl: no process found
david@eros:~$ jackd --sync -Xalsarawmidi -dalsa -r48000 -p256 &
a2jmidid -e & qjackctl
[1] 4820
[2] 4821
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK MIDI <-> ALSA sequencer MIDI bridge, version 8
(7383d268c4bfe85df9f10df6351677659211d1ca) built on Thu Jan  1 01:00:00
1970
Copyright 2006,2007 Dmitry S. Baikov
Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov

Bridge starting...
Using JACK server 'default'
Hardware ports will be exported.
no message buffer overruns
no message buffer overruns
Bridge started
Press ctrl-c to stop the bridge
port created: Midi Through [14] (capture): Midi Through Port-0
port created: Midi Through [14] (playback): Midi Through Port-0
ERROR: a2j_alsa_connect_from: can't subscribe to 24:0 - Resource
temporarily unavailable
port skipped: CASIO USB-MIDI [24] (capture): CASIO USB-MIDI MIDI 1
ERROR: a2j_port_create: snd_seq_connect_to() for 24:0 failed with error
-11
port skipped: CASIO USB-MIDI [24] (playback): CASIO USB-MIDI MIDI 1
no message buffer overruns
`default' server already active
Failed to open server

The keyboard still appears on the ALSA tab and is unconnectable, and
does not appear on the MIDI tab - hardly surprising since the commands
failed.  All very frustrating!

David


-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-26 Thread David Sumbler 
On Mon, 2016-12-26 at 19:26 +0100, Ralf Mardorf wrote:
> Is there anything useful in the log file?
> 
> Please run
> 
>   grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
> 
> and post the output.

Here goes - not sure that there's anything helpful there.  The whole
section represents repeated attempts to connect things, switching
keyboard off and on, rebooting computer etc.

david@eros:~$ grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
Mon Dec 26 14:51:31 2016: graph reorder: new port 'system:playback_1'
Mon Dec 26 14:51:31 2016: graph reorder: new port 'system:playback_2'
Mon Dec 26 14:51:31 2016: graph reorder: new port
'system:midi_capture_1'
Mon Dec 26 14:51:31 2016: graph reorder: new port
'system:midi_playback_1'
Mon Dec 26 14:51:33 2016: Saving settings to
"/home/david/.config/jack/conf.xml" ...
Mon Dec 26 14:51:34 2016: New client 'qjackctl' with PID 2400
Mon Dec 26 14:51:54 2016: New client 'Qtractor' with PID 2453
Mon Dec 26 14:51:54 2016: Connecting 'system:capture_1' to
'Qtractor:Master/in_1'
Mon Dec 26 14:51:54 2016: Connecting 'system:capture_2' to
'Qtractor:Master/in_2'
Mon Dec 26 14:51:54 2016: Connecting 'Qtractor:Master/out_1' to
'system:playback_1'
Mon Dec 26 14:51:54 2016: Connecting 'Qtractor:Master/out_2' to
'system:playback_2'
Mon Dec 26 15:17:16 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:17:16 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: added port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: added port hw:2,0,0 out-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: opened port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: opened port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:53:13 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:53:13 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:53:25 2016: Disconnecting 'system:capture_1' from
'Qtractor:Master/in_1'
Mon Dec 26 15:53:25 2016: Disconnecting 'system:capture_2' from
'Qtractor:Master/in_2'
Mon Dec 26 15:53:25 2016: Disconnecting 'Qtractor:Master/out_1' from
'system:playback_1'
Mon Dec 26 15:53:25 2016: Disconnecting 'Qtractor:Master/out_2' from
'system:playback_2'
Mon Dec 26 15:53:25 2016: Client 'Qtractor' with PID 2453 is out
Mon Dec 26 15:53:39 2016: scan: added port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:53:39 2016: scan: added port hw:2,0,0 out-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:53:39 2016: scan: opened port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:53:39 2016: scan: opened port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:54:27 2016: New client 'ardourprobe' with PID 4094
Mon Dec 26 15:54:27 2016: Client 'ardourprobe' with PID 4094 is out
Mon Dec 26 15:54:27 2016: New client 'ardourprobe' with PID 4094
Mon Dec 26 15:54:27 2016: Client 'ardourprobe' with PID 4094 is out
Mon Dec 26 15:57:38 2016: New client 'Qtractor' with PID 4328
Mon Dec 26 15:57:38 2016: Connecting 'system:capture_1' to
'Qtractor:Master/in_1'
Mon Dec 26 15:57:38 2016: Connecting 'system:capture_2' to
'Qtractor:Master/in_2'
Mon Dec 26 15:57:38 2016: Connecting 'Qtractor:Master/out_1' to
'system:playback_1'
Mon Dec 26 15:57:38 2016: Connecting 'Qtractor:Master/out_2' to
'system:playback_2'
Mon Dec 26 16:00:14 2016: Disconnecting 'system:capture_1' from
'Qtractor:Master/in_1'
Mon Dec 26 16:00:14 2016: Disconnecting 'system:capture_2' from
'Qtractor:Master/in_2'
Mon Dec 26 16:00:14 2016: Disconnecting 'Qtractor:Master/out_1' from
'system:playback_1'
Mon Dec 26 16:00:14 2016: Disconnecting 'Qtractor:Master/out_2' from
'system:playback_2'
Mon Dec 26 16:00:14 2016: Client 'Qtractor' with PID 4328 is out
Mon Dec 26 17:09:43 2016: New client 'a2j' with PID 5142
Mon Dec 26 17:10:23 2016: Client 'a2j' with PID 5142 is out
Mon Dec 26 17:58:42 2016: Client 'qjackctl' with PID 2400 is out
Mon Dec 26 17:58:42 2016: Stopping jack server...
Mon Dec 26 17:58:42 2016: Client 'system' with PID 0 is out
Mon Dec 26 17:58:42 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 17:58:42 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 17:58:42 2016: Released audio card Audio1

Thanks for all your help.

David



-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-26 Thread David Sumbler 
On Mon, 2016-12-26 at 18:32 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 17:05:08 +0000, David Sumbler wrote:
> > 
> > On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> > > 
> > > On Mon, 26 Dec 2016 15:40:00 +, David Sumbler wrote:  
> > > > 
> > > > 
> > > > I click to connect the keyboard input (or output) to qTractor
> > > > or
> > > > something else, and the Messages window in qJackCtl shows an
> > > > ALSA
> > > > connection change.
> > > > 
> > > > But no change is shown in the Connections window, and it seems
> > > > that
> > > > the connection is not made because nothing gets through to
> > > > qTractor.  
> > > Please copy and post the message window output, also run
> > > 
> > >   amidi -l
> > >   pgrep -a jack
> > >   pgrep -a a2j
> > > 
> > > and post it.  
> > I get:
> > 
> > david@eros:~$ amidi -l
> > Dir DeviceName
> > IO  hw:2,0,0  CASIO USB-MIDI MIDI 1
> > david@eros:~$   pgrep -a jack
> > 2324 /usr/bin/jackdbus auto
> > 2400 /usr/bin/qjackctl
> > david@eros:~$   pgrep -a a2j
> > david@eros:~$
> > 
> > (No output from the 3rd command.)
> That's ok, I only wanted to ensure that you do or don't run a command
> containing "a2j".
> 
> You have forgotten to post the output from the message window.
> 
> I can't help you with jackdbus. IMO dbus is a PITA and shouldn't be
> used
> with jack. I'm only running jackd.
> 
> I even don't understand why on my machine alsarawmidi is part of what
> seems to be the jackdbus config, but the log doesn't mention it [1].
> 
> However, assuming you would launch jackdbus with xalsarawmidi, it
> could
> be the culprit. Btw. xalsarawmidi is very good to reduce MIDI jitter,
> but using it is tricky.
> 
> Regards,
> Ralf
> 
> [1]
> [rocketmouse@archlinux ~]$ grep alsarawmidi ~/.config/jack/conf.xml
>   
> [rocketmouse@archlinux ~]$ grep Dec\ 26 ~/.log/jack/jackdbus.log
> Mon Dec 26 18:16:43 2016: --
> Mon Dec 26 18:16:43 2016: Controller activated. Version 1.9.11
> (0+f2ece2418c875eb7e7ac3d25fbb484ddda47ab46) built on Thu Jan  1
> 01:00:00 1970
> Mon Dec 26 18:16:43 2016: Loading settings from
> "/home/rocketmouse/.config/jack/conf.xml" using expat_2.2.0 ...
> Mon Dec 26 18:16:43 2016: setting parameter
> 'engine':'driver':'(null)' to value "alsa"
> Mon Dec 26 18:16:43 2016: setting parameter
> 'engine':'realtime':'(null)' to value "true"
> Mon Dec 26 18:16:43 2016: setting parameter 'drivers':'alsa':'device'
> to value "hw:0"
> Mon Dec 26 18:16:43 2016: setting parameter 'drivers':'alsa':'rate'
> to value "48000"
> Mon Dec 26 18:16:43 2016: setting parameter 'drivers':'alsa':'period'
> to value "256"
> Mon Dec 26 18:16:43 2016: setting parameter
> 'drivers':'alsa':'nperiods' to value "2"
> Mon Dec 26 18:16:43 2016: Listening for D-Bus messages
> 

Sorry I forgot the message window, but it isn't very informative!

17:59:04.754 ALSA connection graph change.
17:59:04.939 ALSA connection change.
17:59:37.698 ALSA connection graph change.
17:59:37.857 ALSA connection change.
18:00:04.185 ALSA connection change.

The first 2 lines appeared when I switched on the keyboard.  The next 2
were when I started qtractor.  And the last line is when I attempted to
connect the keyboard output to qtractor's input in the connections
window.  But it wouldn't connect, of course, despite the fact that
there is no error printed.  Weird.

Not sure where to go from here.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-26 Thread David Sumbler 
On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 15:40:00 +0000, David Sumbler wrote:
> > 
> > I click to connect the keyboard input (or output) to qTractor or
> > something else, and the Messages window in qJackCtl shows an ALSA
> > connection change.
> > 
> > But no change is shown in the Connections window, and it seems that
> > the
> > connection is not made because nothing gets through to qTractor.
> Please copy and post the message window output, also run
> 
>   amidi -l
>   pgrep -a jack
>   pgrep -a a2j
> 
> and post it.

I get:

david@eros:~$ amidi -l
Dir DeviceName
IO  hw:2,0,0  CASIO USB-MIDI MIDI 1
david@eros:~$   pgrep -a jack
2324 /usr/bin/jackdbus auto
2400 /usr/bin/qjackctl
david@eros:~$   pgrep -a a2j
david@eros:~$

(No output from the 3rd command.)

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

[ubuntu-studio-users] Keyboard is seen but won't connect

2016-12-26 Thread David Sumbler 
It's a few months since I used my midi keyboard with the computer.  I
want to get back to that project now, hence my email earlier today.

But now I have a bigger problem: I can't connect the keyboard to
qTractor (or anything else), although I had all of this working before.

In qJackCtl the keyboard shows up in the ALSA tab as both an input and
an output device.  I click to connect the keyboard input (or output) to
qTractor or something else, and the Messages window in qJackCtl shows
an ALSA connection change.

But no change is shown in the Connections window, and it seems that the
connection is not made because nothing gets through to qTractor.

I can't imagine why this is, especially as I know it all worked a few
months ago.  I have tried with pulseaudio running and with it disabled,
in case that had something to do with it, but it makes no difference.

So far as I can think, I haven't changed anything of significance on
the computer or the keyboard.

Can anyone suggest what might be the problem?

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

[ubuntu-studio-users] Converting a recorded track to a timing track

2016-12-26 Thread David Sumbler 
This may well be a completely daft question, but if so, please tell me
nicely.

I want to record a track (using a midi keyboard and qtractor, probably)
as a control track for performing subsequent tracks.  So this first
track would perhaps simply be a wood-block or cow bell voice marking
the beats of my intended performance, complete with idiosyncrasies and
variations of pulse.

What I would like to do then is to convert that track to an actual
timing track, so that the beats (and bars) shown in qtractor etc.
correspond to the actual beats and bars of the performance.  This will
make it much easier to navigate around the file later on.  The timing
track would consist of a new tempo every beat, reflecting the detailed
timing of the original track.

I can probably do this with a Python program in conjunction with
midicsv.

But I am sure other people must want to do this sort of thing at times,
so perhaps there is already something I could use to achieve what I
want without having to write my own program.  Perhaps the facility is
already there in qtractor or some other application.

Suggestions, please.

David



-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] aarrgghh

2016-12-07 Thread David Sumbler 
On Tue, 2016-12-06 at 23:37 -0800, Charlie wrote:
> I'm getting so tired of the software center crashing and closing by 
> itself. I can't even download a piece of software I need to make 
> business cards. Can somebody please fix this? It's really getting on
> my 
> nerves. Thanks!
> 
> Charlie Luna

I agree - the software centre is completely unusable, because it
doesn't work!  I don't understand why it is even packaged with this (or
any) distro.

Try using Synaptic Package Manager, or apt-get from the command line.

To install Synaptic from the command line (in a terminal), type

sudo apt-get install synaptic

press Enter, then enter your password as requested.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] {SPAM 03.4} Re: Default sound settings

2016-11-04 Thread David Sumbler 
On Fri, 2016-11-04 at 20:53 +0100, Ralf Mardorf wrote:
> 
> 
> > On 04 Nov 2016, at 17:53, David Sumbler  wrote:
> 
> -rw-r--r-- 1 root root 2507 Nov  3 15:42 alsa-base.conf
> 
> -rw-r--r-- 1 root root 2541 Nov  3 15:33 alsa-base.conf~
> Run
> 
>   aplay - l
> 
> Is the wanted card hw: 1?
> 
> If so, move both files to /root
> 
>   sudo mv -i  /etc/modprobe.d/alsa-base.con* /root
> 
> and generate a new file, with no other content, but 'options snd
> slots=snd_hda_intel'
>   echo "options snd slots=snd_hda_intel" |  sudo
> tee /etc/modprobe.d/alsa-base.conf
> reboot and run
>    aplay -l
> the sound device now must be hw:0. If no sound server runs, neither
> pulseaudio, nor jack and you didn't setup ALSA to some custom
> setting, then it should be available for all apps using plain ALSA
> and that usually try to connect with the default device. If an app
> grabbed the device, no other app could access it at the same time. To
> make it available for another app, you first need to close the app
> using the sound device, before you open the other app.
> If more than one app should use the device at the same time, you need
> to use a sound server or dmix.
> Regards,
> Ralf

Thank your for all your help, although so far I haven't got any
positive result.

I did all of the above - replacing /etc/modprobe.d/alsa-base.conf with
the single line and then rebooting.

Yet when I enter 'aplay -l' I still get:

 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 0: ALC3227 Analog [ALC3227 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

which is exactly the same output as I had before.  As I understand it,
this means that the required sound card is hw:1,0.

As well as booting into Ubuntu with low latency, I also tried rebooting
and choosing the grub menu option with normal latency, to see if this
made any difference, but it didn't.

David



-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Default sound settings

2016-11-04 Thread David Sumbler 
On Fri, 2016-11-04 at 14:20 +0100, Ralf Mardorf wrote:
> On 03 Nov 2016, at 16:49, David Sumbler  wrote:
> 
> > 
> > Thanks for the suggestion.  Unfortunately adding 
> > 'options snd slots=snd_hda_intel' (as it would be in my case) to
> > /etc/modprobe.d/alsa-base.conf has not made any difference, even
> > after
> > rebooting the computer.
> What isn't different?
> 
> The issue that you can't hear audio of all apps or that the device
> still is hw:1 instead of hw:0?

Both - as I said, the edit of alsa-base.conf hasn't made any
difference.  I have reverted back to the original version.

> Regarding the application sound issue I can't help, because I'm not
> using a default with pulseaudio. If the device still shouldn't be
> hw:0, then post your complete /etc/modprobe.d/alsa-base.conf and the
> output of
> 
>    ls -l /etc/modprobe.d/
> 
> ,too

I am not running pulseaudio.

'cat /etc/modprobe.d/alsa-base.conf' gives:

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --
quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss 
; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ;
/sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi
; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-
synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it
anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2




'ls -l /etc/modprobe.d/' gives:

total 60
-rw-r--r-- 1 root root 2507 Nov  3 15:42 alsa-base.conf
-rw-r--r-- 1 root root 2541 Nov  3 15:33 alsa-base.conf~
-rw-r--r-- 1 root root  154 Mar 23  2016 amd64-microcode-blacklist.conf
-rw-r--r-- 1 root root  325 Mar 13  2016 blacklist-ath_pci.conf
-rw-r--r-- 1 root root 1603 Mar 13  2016 blacklist.conf
-rw-r--r-- 1 root root  210 Mar 13  2016 blacklist-firewire.conf
-rw-r--r-- 1 root root  697 Mar 13  2016 blacklist-framebuffer.conf
-rw-r--r-- 1 root root  156 Jul 31  2015 blacklist-modem.conf
lrwxrwxrwx 1 root root   41 Aug 20 16:16 blacklist-oss.conf -> 
/lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r-- 1 root root  583 Mar 13  2016 blacklist-rare-network.conf
-rw-r--r-- 1 root root 1077 Mar 13  2016 blacklist-watchdog.conf
-rw-r--r-- 1 root root  390 Apr 12  2016 fbdev-blacklist.conf
-rw-r--r-- 1 root root  347 Mar 13  2016 iwlwifi.conf
-rw-r--r-- 1 root root  104 Mar 13  2016 mlx4.conf
-rw-r--r-- 1 root root   68 Dec 28  2015 osspd.conf
-rw-r--r-- 1 root root   30 Mar  3  2016 vmwgfx-fbdev.conf

Yes, there are only 16 items, despite the line saying "total 60".


On Fri, 2016-11-04 at 16:54 +0100, Ralf Mardorf wrote:
> I don't have access to xfce at the moment. Instead of using a right
> click menu, did you try running xfce4-settings-manager? The right
>

Re: [ubuntu-studio-users] Default sound settings

2016-11-03 Thread David Sumbler 
Thanks for the suggestion.  Unfortunately adding 
'options snd slots=snd_hda_intel' (as it would be in my case) to
/etc/modprobe.d/alsa-base.conf has not made any difference, even after
rebooting the computer.

David


On Thu, 2016-11-03 at 14:48 +0100, Ralf Mardorf wrote:
> Hi,
> 
> get the driver name of that device by lshw like this
> 
> ubuntu-mate@ubuntu-mate:~$ sudo lshw -C sound | grep driver
>   configuration: driver=snd_hdspm latency=0
>   configuration: driver=snd-usb-audio maxpower=100mA speed=12Mbit/s
> 
> On my machine the wanted sound card's driver is snd_hdspm.
> 
> Then generate a file, resp. add to an existing file, that ensures
> that
> the wanted sound card always is hw:0 after startup. The below
> commands
> first tries to make a copy, assuming /etc/modprobe.d/alsa-base.conf
> should already exist.
> 
> ubuntu-mate@ubuntu-mate:~$ sudo -i
> root@ubuntu-mate:~# cp -ai /etc/modprobe.d/alsa-base.conf /root/alsa-
> base.conf.backup
> root@ubuntu-mate:~# echo "options snd slots=snd_hdspm" >>
> /etc/modprobe.d/alsa-base.conf
> 
> Just replace snd_hdspm with your driver. On my machine this does
> cause
> that the device that belongs to the driver snd_hdspm is always hw:0
> and
> the other device becomes hw:1.
> 
> This might solve your issue, if not you simply could delete the file
> or
> replace a file that already existed with the backup.
> 
> Regards,
> Ralf
> 
> 
> 

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

[ubuntu-studio-users] Default sound settings

2016-11-03 Thread David Sumbler 
I have UbuntuStudio 16.04 installed on my laptop.  It would nice if I
could get my default sound settings arranged so that sound works
reliably in all (or at least most) programs.  At present I can choose
the correct sound card  by altering settings in some programs (e.g. VLC
and Audacity), but not in others (e.g. Parole).

At the moment, I have no graphical sound setting option.  When I open
Settings from the main menu, I get the usual window with lots of
options under the main headings Personal, Hardware, Audio Production,
System and Other, but nowhere is there a general sound setting option
that I can see.  How can I enable this?

Fortunately, I can run 'alsamixer' from a terminal emulator.  Using
this shows me that the sound card I need to address is no. 1 "HD-Audio
Generic", and not no. 0 "HDA ATI HDMI".  The first item listed,
"Default", appears to be pointing to the HDMI output.  How can I change
this?

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Tempo changes in qTractor

2016-09-15 Thread David Sumbler 
On Thu, 2016-09-15 at 01:49 +0200, Ralf Mardorf wrote:
> On Thu, 15 Sep 2016 01:45:47 +0200, Ralf Mardorf wrote:
> > 
> > On Thu, 15 Sep 2016 01:31:02 +0200, Ralf Mardorf wrote:
> > > 
> > > A workaround could be to chose different meters, even
> > > asymmetrical
> > > meters seem to be possible.  
> > And I'm not thinking about 1/4 or 3/4, but e.g. 7/8, which
> > seemingly
> > is possible. I didn't test, but perhaps even 1/8 or 1/16 are
> > possible.
> PPS:
> 
> Btw. when you mentioned tempi within a bar, my google search was
> 
> https://www.google.de/?gws_rd=ssl#q=qtractor+tempo+ramp
> 
> since this is the only reason IMO, when it makes sense to change
> tempi
> within a bar.

Thanks again for all your help.  I have read the manual, and even have
a printed copy here.

The problem is having to define the time in terms of beats, which are
largely irrelevant to my project.  I want to be able to define these
points at any time, regardless of the notional beat.  This can, of
course, be done in a midi file - I can do it using midicsv and then
csvmidi, but that is not nearly so easy to do as I hoped it would be in
qTractor - not easy, for instance, to try something and then undo it
and try a slightly different version.

Perhaps I need to experiment with other editors, which may have the
facility I want.

In case you're wondering why the midi beats are irrelevant, what I have
done (and want to do with quite a lot of other music) is to enter
tracks from a midi keyboard, with all the subtleties of timing that a
live performance can have and should have for certain types of music.
 I can then tweak details.  The actual "beats" in the midi file are
irrelevant except as a means of controlling the timing of the output -
the actual notes will only be approximately with those beats, or
perhaps not at all.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Tempo changes in qTractor

2016-09-14 Thread David Sumbler 
On Wed, 2016-09-14 at 22:33 +0200, Ralf Mardorf wrote:
> On Wed, 14 Sep 2016 20:40:11 +0100, David Sumbler wrote:
> > 
> > On Wed, 2016-09-14 at 19:04 +0200, Ralf Mardorf wrote:
> > > 
> > > On Wed, 14 Sep 2016 13:32:50 +0100, David Sumbler wrote:  
> > > > 
> > > > 
> > > > Using qTractor, how can I change the tempo for a short section
> > > > of a
> > > > piece?  
> > > With the mouse chose the menu
> > > 
> > >   View > Tempo Map / Markers ...
> > > 
> > > or push
> > > 
> > >   Alt + V
> > > 
> > > and then
> > > 
> > >   a
> > > 
> > > then edit e.g.
> > > 
> > >   Bar: 1 / Tempo: 90.0 4/4
> > >   Bar: 2 / Tempo: 120.0 4/4
> > > 
> > > don't forget to push the
> > > 
> > >   Add-button
> > > 
> > > That's it.
> > When I do that, the dialogue lists the start of the piece but
> > doesn't
> > show the location of my markers, even when I have selected a
> > section.
> >  The track display also jumps to the start of the piece.
> > 
> > This makes it very difficult to insert a time change just where I
> > want
> > it.  Of course, I can type a different value into the "Time" box
> > under
> > "Location", and the display will then show me the correct section
> > of
> > the piece, but there is nothing to show precisely where that time
> > point
> > is within the section of music displayed.
> > 
> > I think I must be missing something here...
> I never used it myself, but it took me less then a minute by trail
> and
> error to find out, that if you open the tempo map, you could chose a
> colour for a marker and give it a name. Then push the add button.
> With the mouse move one of the blue markers (edit head and tail)
> above
> your marker and then you can move the marker that was added by the
> tempo
> map dialog, to any position you like. After that select the marker in
> the tempo map and add what ever tempo you want at this position. You
> could move the play head from one marker to another by using the |<
> and
> > 
> > > 
> > > buttons. IMO it's self-explaining. There might be some features
> > > that
> aren't self explaining or that require more than less than a minute
> of
> trail and error. I don't know if the Qtractor Wiki / online manual
> informs about those features. I never read it.
> 
> https://sourceforge.net/p/qtractor/wiki/Manual%20-%204%20Qtractor--An
> %20Overview/#4-qtractor-an-overview
> http://qtractor.sourceforge.net/qtractor-index.html#Support
> https://sourceforge.net/p/qtractor/wiki/Home/
> 
> Users could ask for help at Qtractor devel mailing list.
> 
> https://lists.sourceforge.net/lists/listinfo/qtractor-devel
> 
> If you should be subscribed to Linux audio user mailing list, you
> also
> could ask there. Rui, the coder is subscribed to Linux audio user.
> However, he usually replies faster, if you send a request to Qtractor
> devel.
> 
> http://lists.linuxaudio.org/listinfo/linux-audio-user
> 
> Regards,
> Ralf

Thanks for your help on this.  Perhaps I'm a bit thick, but I had been
fiddling around for hours, never mind minutes, and hadn't managed to
work out how to do it.

I've now managed to create markers, but it took me a long time to work
out how to move them.  I eventually discovered that this is because
they can only be positioned on bar boundaries, or so it seems.  This
isn't any good at all for what I want to do.

If anyone can tell me how they can be positioned at arbitrary points in
time, I'll be very grateful!

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: [ubuntu-studio-users] Tempo changes in qTractor

2016-09-14 Thread David Sumbler 
On Wed, 2016-09-14 at 19:04 +0200, Ralf Mardorf wrote:
> On Wed, 14 Sep 2016 13:32:50 +0100, David Sumbler wrote:
> > 
> > Using qTractor, how can I change the tempo for a short section of a
> > piece?
> With the mouse chose the menu
> 
>   View > Tempo Map / Markers ...
> 
> or push
> 
>   Alt + V
> 
> and then
> 
>   a
> 
> then edit e.g.
> 
>   Bar: 1 / Tempo: 90.0 4/4
>   Bar: 2 / Tempo: 120.0 4/4
> 
> don't forget to push the
> 
>   Add-button
> 
> That's it.
> 
> Regards,
> Ralf

When I do that, the dialogue lists the start of the piece but doesn't
show the location of my markers, even when I have selected a section.
 The track display also jumps to the start of the piece.

This makes it very difficult to insert a time change just where I want
it.  Of course, I can type a different value into the "Time" box under
"Location", and the display will then show me the correct section of
the piece, but there is nothing to show precisely where that time point
is within the section of music displayed.

I think I must be missing something here...

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

[ubuntu-studio-users] Tempo changes in qTractor

2016-09-14 Thread David Sumbler 
Using qTractor, how can I change the tempo for a short section of a
piece?

I have tried various things, including splitting a clip, selecting it,
and then using the Clip - Tempo Adjust dialogue.

But every attempt I make changes the tempo of the whole piece, not just
the section I want changed.

At the moment the piece consists of just a single track with (until I
split it) a single midi clip.

David

-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users