Re: [ubuntu-studio-users] Keyboard is seen but won't connect
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 -- 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 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
On Mon, 26 Dec 2016 19:26:13 +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. It might be that nothing ALSA MIDI related is part of a _jack_ log file ;). -- 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
Is there anything useful in the log file? Please run grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50 and post the output. -- 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 18:32 +0100, Ralf Mardorf wrote: > On Mon, 26 Dec 2016 17:05:08 +, 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
On Mon, 26 Dec 2016 17:05:08 +, 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 -- 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
I've had a similar issue some time ago (trying to use midi in Pure Data) and my workaround was to make the connections through Patchage. It just worked, don't ask me why, and I've given it no thought ever since. But I think it would be nice to post the output and see if there is anything to be fixed.Best regards,Pietro Em Segunda-feira, 26 de Dezembro de 2016 14:02, Ralf Mardorf escreveu: 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. -- 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 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 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.) 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 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. -- 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
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
Re: [ubuntu-studio-users] Converting a recorded track to a timing track
On Mon, 26 Dec 2016 12:32:01 + (UTC), Pietro Bergamo wrote: >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. Full acknowledgement. The OP could either record sequencer music with a simple tempo map or record just audio tracks, disable measure lines if possible, for Qtractor simply ignore them, since disabling them seems to be impossible and only care about the timecode, resp. the OP could record MIDI tracks without using quantization and by using as much ticks as possible, Qtractor > File > Properties > Ticks/Beat and then use a MIDI track quasi in the same way as an audio track. -- 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
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 Em Segunda-feira, 26 de Dezembro de 2016 10:09, Ralf Mardorf escreveu: Hi, you need a sequencer that records a tempo map following you tapping a key. This automatically would set the tempo, BPM in relation to the time code position. This works very well to sync a sequencer to "averaged normal music" played by real musicians. After or before doing this you still need to manually edit the signature. No software is able to detect if you are playing 3/4 followed by 2/4 or if you are playing 5/4. Apart from this, if you are really playing by pulse, recording a tempo map might be more or less impossible, since when you actually wouldn't count, you need to count, resp. tap, so that the sequencer knows at what tempo you are, where quasi no tempo exists. In short, a feature to sync a MIDI sequencer to human played audio tracks by tapping a key does exist since decades, even to analog audio tapes where the sequencer is synced by SMPTE. I guess you won't find this feature provided by Qtractor. There only seems to be View > Tempo Map > Tap to set a tempo at a given position, not to generate a tempo map while playing the song. Maybe Ardour, Rosegarden or another Linux sequencer provides it. I suspect that assuming Ardour's Rhythm Ferret should still exist and assuming it should work, it just would work for "averaged normal music", https://community.ardour.org/a3_features_ferret . However, beat detection is for sure less good than tapping, if you are playing by pulse. Sync is an issue for all computer platforms, but Linux for sure is by far the weakest platform in this domain. 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 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
Hi, you need a sequencer that records a tempo map following you tapping a key. This automatically would set the tempo, BPM in relation to the time code position. This works very well to sync a sequencer to "averaged normal music" played by real musicians. After or before doing this you still need to manually edit the signature. No software is able to detect if you are playing 3/4 followed by 2/4 or if you are playing 5/4. Apart from this, if you are really playing by pulse, recording a tempo map might be more or less impossible, since when you actually wouldn't count, you need to count, resp. tap, so that the sequencer knows at what tempo you are, where quasi no tempo exists. In short, a feature to sync a MIDI sequencer to human played audio tracks by tapping a key does exist since decades, even to analog audio tapes where the sequencer is synced by SMPTE. I guess you won't find this feature provided by Qtractor. There only seems to be View > Tempo Map > Tapto set a tempo at a given position, not to generate a tempo map while playing the song. Maybe Ardour, Rosegarden or another Linux sequencer provides it. I suspect that assuming Ardour's Rhythm Ferret should still exist and assuming it should work, it just would work for "averaged normal music", https://community.ardour.org/a3_features_ferret . However, beat detection is for sure less good than tapping, if you are playing by pulse. Sync is an issue for all computer platforms, but Linux for sure is by far the weakest platform in this domain. 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] Converting a recorded track to a timing track
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] Adding flowblade to Ubuntu studio
Hi Auro, Thanks for reaching out, and for the suggestions. On 25/12/16 03:58, AURO KUMAR SAHOO wrote: In 16.10 I am happy to see graphics and photo editing part is been looked into. So can we add some well established video editing software to enrich the Ubuntu studio for editors like flowblade in addition to kdenlive, pitivi, openshot. Flowblade seems to already exist in Ubuntu (http://packages.ubuntu.com/zesty/flowblade), so we could easily add this to our seeds so it was installed automatically. But we have to be careful that we don't just install everything and have a carefully selected set of packages. Not having much time for playing with video stuff at the moment, what extra features, or workflow support would flowblade add on top of the other video applications? Previous I have requested to add photoflow to gimp. Photoflow is a bit harder, as it has not been packaged for Debian yet (Debian is normally where our packages come from). It looks like it almost made it in 2014 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774005). Maybe you could reply to that bug (copying in Laszlo), to chase up the status and give a friendly push? Maybe if he is no longer interested, he has some basic packaging that someone could take forward? Regards, Ross -- 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
