Re: [ubuntu-studio-users] Keyboard is seen but won't connect
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] Keyboard is seen but won't connect
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'm sorry, I even don't understand it at the meoment, by takiong a look at old ja-snapshot files. [rocketmouse@archlinux ~]$ grep -i MIDI -B8 -A8 /home/music/arch2014.1/.tmp.03.01.ajs -- [rocketmouse@archlinux ~]$ grep -i MIDI -B8 -A8 /home/music/arch2014.1/.tmp.0 .tmp.01.05.ajs .tmp.02.00.ajs .tmp.02.01.ajs .tmp.02.02.ajs .tmp.02.03.ajs .tmp.03.00.ajs .tmp.03.01.ajs [rocketmouse@archlinux ~]$ grep -i MIDI -B8 -A8 /home/music/arch2014.1/.tmp.01.05.ajs -- [rocketmouse@archlinux ~]$ -- 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
On Tue, 2016-12-27 at 17:15 +0100, Ralf Mardorf wrote: > On Tue, 27 Dec 2016 15:29:08 +, 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] Converting a recorded track to a timing track
On Tue, 27 Dec 2016 15:29:08 +, 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. >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
On Tue, 2016-12-27 at 16:20 +0100, Ralf Mardorf wrote: > On Tue, 27 Dec 2016 15:06:03 +, 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
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
On Tue, 27 Dec 2016 15:06:03 +, 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 -- 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
On Tue, 2016-12-27 at 15:01 +0100, Ralf Mardorf wrote: > On Tue, 27 Dec 2016 13:40:15 +, 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
On Tue, 27 Dec 2016 13:40:15 +, 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 -- 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
On Mon, 2016-12-26 at 20:33 +0100, Ralf Mardorf wrote: > On Mon, 26 Dec 2016 19:07:41 +, 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
