Thread: [Qmidiarp-devel] Some feedback on QMidiArp 0.4.1
Linux MIDI arpeggiator, phrase generator and controller LFO
Status: Alpha
Brought to you by:
emuse
Menu
▾
▴
qmidiarp-devel
|
From: Louigi V. <lou...@gm...> - 2011-06-02 12:45:16
|
Hey everybody! Just got my hands on QMidiArp 0.4.1, using it on Ubuntu 10.04. This is a fantastic piece of software, however, lack of stability and a "random stop" bug make it virtually unusable in its current state. I would like to report both problems. 1. Random crashes. QMidiArp crashes often, in my experience always as a reaction to an action, not by itself. Actions, however, are different - it may be moving a slider or creating a new module. Crashes happen fairly often, rarely have I closed QMidiArp myself, usually it just crashes within 3-5 minutes of work. 2. Random stops. QMidiArp, after playing for 15-30 seconds would suddenly stop. The play button is pressed, so in order to restart you have to click on Play to change it to stopped state and then press play again. After 15-30 seconds QMidiArp stops again. In case this info could be useful, the first time I started QMidiArp, it did not stop and I actually played with it for several minutes until it crashed due to me moving a slider in one of the modules, but all subsequent uses of the program featured random stopping. I am available to test the app. It is a very promising tool and I would be happy to help out any way I can. I do dream to actually start using QMidiArp on stage as soon as possible. -- Louigi Verona http://www.louigiverona.ru/ |
|
From: Brendan J. <bre...@gm...> - 2011-06-02 13:37:49
|
On 06/02/2011 10:45 PM, Louigi Verona wrote: > Hey everybody! > > Just got my hands on QMidiArp 0.4.1, using it on Ubuntu 10.04. > This is a fantastic piece of software, however, lack of stability and a > "random stop" bug make it virtually unusable in its current state. I > would like to report both problems. > > 1. Random crashes. > QMidiArp crashes often, in my experience always as a reaction to an > action, not by itself. Actions, however, are different - it may be > moving a slider or creating a new module. Crashes happen fairly often, > rarely have I closed QMidiArp myself, usually it just crashes within 3-5 > minutes of work. > > 2. Random stops. > QMidiArp, after playing for 15-30 seconds would suddenly stop. The play > button is pressed, so in order to restart you have to click on Play to > change it to stopped state and then press play again. After 15-30 > seconds QMidiArp stops again. In case this info could be useful, the > first time I started QMidiArp, it did not stop and I actually played > with it for several minutes until it crashed due to me moving a slider > in one of the modules, but all subsequent uses of the program featured > random stopping. > > Hi guys, great program - thanks again. I can confirm on Fedora 15, JAck 1.9.7. As Lougi mentioned it does seem to be to do with interaction with the GUI. I was able to play without stoppage when using the sequencer and a midi controller (not touching the GUI). regards, Brendan |
|
From: Frank K. <goe...@ya...> - 2011-06-02 15:47:50
|
Hi Louigi, hi Brendan, >________________________________ >De : Louigi Verona <lou...@gm...> >À : qmi...@li... >Envoyé le : Jeudi 2 Juin 2011 14h45 >Objet : [Qmidiarp-devel] Some feedback on QMidiArp 0.4.1 > > >Hey everybody! > >Just got my hands on QMidiArp 0.4.1, using it on Ubuntu 10.04. >This is a fantastic piece of software, however, lack of stability and a "random stop" bug make it virtually unusable in its current state. I would like to report both problems. > >1. Random crashes. >QMidiArp crashes often, in my experience always as a reaction to an action, not by itself. Actions, however, are different - it may be moving a slider or creating a new module. Crashes happen fairly often, rarely have I closed QMidiArp myself, usually it just crashes within 3-5 minutes of work. > >2. Random stops. >QMidiArp, after playing for 15-30 seconds would suddenly stop. The play button is pressed, so in order to restart you have to click on Play to change it to stopped state and then press play again. After 15-30 seconds QMidiArp stops again. In case this info could be useful, the first time I started QMidiArp, it did not stop and I actually played with it for several minutes until it crashed due to me moving a slider in one of the modules, but all subsequent uses of the program featured random stopping. > > >I am available to test the app. It is a very promising tool and I would be happy to help out any way I can. I do dream to actually start using QMidiArp on stage as soon as possible. Thanks for your reports, this is very important, alas I cannot reproduce crashes on my system. I cannot remember a single one actually, so Louigi does this happen in a situation of sync to jack transport or even when running with the internal clock? Does it crash even with stopped transport ? Brendan, do you get crashes, too or only the random stop thing? on 2) I've pushed a fix for a transport sync problem that was present when only arp modules were in the setup, which was definitely a bug that came in since 0.3.9 I've had a discussion with Jeremy "Autostatic" on the IRC, and he found that a 1000Hz system timer (kernel option) and lower jack latencies (around 256 points, 2 periods) worked quite well for jack transport sync. So could you guys please checkout from git repo and tell me if this solves some issues? I'd like to know more about the crashes, maybe we'll have to go through gdb etc... Cheers and thanks again for reporting so far Frank |
|
From: Louigi V. <lou...@gm...> - 2011-06-02 17:02:31
|
Hey Frank! 1. Crashes were on internal clock. In my case it crashed each time it was playing, I will test more tomorrow. 2. I experienced random stops using only lfos or using only step sequencer or using lfos and step sequencer. So I was NOT using arpeggios at all. Louigi. -- Louigi Verona http://www.louigiverona.ru/ |
|
From: Frank K. <goe...@ya...> - 2011-06-02 22:37:43
|
Hi Louigi and Brendan, > De : Louigi Verona <lou...@gm...> > À : Frank Kober <goe...@ya...> > Cc : "qmi...@li..." <qmi...@li...> > Envoyé le : Jeudi 2 Juin 2011 18h55 > Objet : Re: Re : [Qmidiarp-devel] Some feedback on QMidiArp 0.4.1 > > Hey Frank! > > 1. Crashes were on internal clock. In my case it crashed each time it > was playing, I will test more tomorrow. > > 2. I experienced random stops using only lfos or using only step > sequencer or using lfos and step sequencer. So I was NOT using > arpeggios at all. I have pushed another fix to qmidiarp git that should solve at least issue 2. This was due to a change in data queueing to ALSA since 0.3.9 and I'm really glad you insisted on this. The problem didn't expose when arp modules were involved, too. It all went past my testing since my testing setup here has all three modules in... I'll do better in the future. May I ask you to build qmidiarp from git again and let me know if these issues are solved? Thanks for your patience Frank |
|
From: Louigi V. <lou...@gm...> - 2011-06-03 07:20:16
|
Hey guys! Frank! Gave git version a try - no more stops!!! No crashes so far, I will report if any. As proof, I've recorded a hypnotic tune. Some rough spots there due to live recording and no attention to levels peaking at times, but in general I think it is listenable: http://www.louigiverona.ru/seascape.ogg -- Louigi Verona http://www.louigiverona.ru/ |
|
From: Brendan J. <bre...@gm...> - 2011-06-02 20:47:45
|
On 06/03/2011 01:47 AM, Frank Kober wrote:
> Hi Louigi, hi Brendan,
>
> Thanks for your reports, this is very important, alas I cannot reproduce crashes on my system. I cannot remember a single one actually, so Louigi does this happen in a situation of sync to jack transport or even when running with the internal clock? Does it crash even with stopped transport ?
> Brendan, do you get crashes, too or only the random stop thing?
>
> on 2) I've pushed a fix for a transport sync problem that was present when only arp modules were in the setup, which was definitely a bug that came in since 0.3.9
>
> I've had a discussion with Jeremy "Autostatic" on the IRC, and he found that a 1000Hz system timer (kernel option) and lower jack latencies (around 256 points, 2 periods) worked quite well for jack transport sync.
>
Cheers Frank - I will test the SVN version over the weekend. The
following is from 0.4.1
I did manage to catch one backtrace. In this session seq playback
randomly stopped a couple of times when I was not using jack transport.
I turned it on played around for a while and turned jack transport off
and crashed. This does not occur all of the time.
( Previous crash to this was somewhat diffrent - QVector index out of
range error IIRC )
Alsa Queue stopped
[JackTransportStopped]
[JackTransportStarting]
Alsa Queue started
Jack: JackClient::Deactivate
Jack: JackClient::Deactivate res = 0
Jack: JackPosixThread::Kill
[Thread 0x7fffe93a7700 (LWP 6592) exited]
jack client deactivated
Jack: jack_client_close
Jack: JackClient::Close ref = 7
Jack: JackClient::Deactivate
Jack: JackSocketClientChannel::Stop
Jack: JackPosixThread::Kill
[Thread 0x7fffe9428700 (LWP 6591) exited]
Jack: JackClientSocket::Close
Jack: JackClientSocket::Close
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_qmidiarp
Jack: JackLibClient::~JackLibClient
Jack: JackShmReadWritePtr1::~JackShmReadWritePtr1 7
Jack: Succeeded in unlocking 384 byte memory area
Jack: JackLibGlobals Destroy a56050
Jack: ~JackLibGlobals
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_system
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_freewheel
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_qjackctl
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_jackctlmmc
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_LASH_Server
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_a2j
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_yoshimi
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_Hydrogen
Jack: no message buffer overruns
Jack: ThreadHandler: exit
[Thread 0x7fffe94a9700 (LWP 6590) exited]
Jack: JackPosixThread::Stop
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 1
Jack: Succeeded in unlocking 1040 byte memory area
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 0
Jack: Succeeded in unlocking 82246176 byte memory area
Jack: jack_client_close res = 0
Jack: jack_client_open qmidiarp
Jack: JackLibGlobals Init 0
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffebbc5700 (LWP 6566)]
jack_transport_query (ext_client=0x30003000300030, pos=0xa97a68) at
../common/JackAPI.cpp:1611
1611 return client->TransportQuery(pos);
(gdb) backtrace full
#0 jack_transport_query (ext_client=0x30003000300030, pos=0xa97a68) at
../common/JackAPI.cpp:1611
client = 0x30003000300030
#1 0x000000000044ed17 in SeqDriver::handleEcho (this=0x8e5f40,
inEv=...) at seqdriver.cpp:214
note_tick = 0
l1 = <optimized out>
seqtransp = <optimized out>
isNew = <optimized out>
frame_nticks = 0
l2 = <optimized out>
note = {{d = 0x679960, p = 0x679960}}
velocity = {{d = 0x679960, p = 0x679960}}
length = <optimized out>
outport = <optimized out>
outEv = {type = 6, channel = 1, data = 41, value = 111}
#2 0x000000000044f0bf in SeqDriver::run (this=0x8e5f40) at
seqdriver.cpp:152
evIn = 0x8fa220
unmatched = <optimized out>
fallback = false
inEv = {type = 50, channel = 0, data = 0, value = 0}
pollR = <optimized out>
nfds = 1
pfds = 0x7fffebbc4db0
#3 0x00000037fea74125 in QThreadPrivate::start (arg=0x8e5f40) at
thread/qthread_unix.cpp:320
__clframe = {__cancel_routine = 0x37fea731c0
<QThreadPrivate::finish(void*)>, __cancel_arg = 0x8e5f40, __do_it = 1,
__cancel_type = <optimized out>}
thr = 0x8e5f40
data = 0x8e6300
#4 0x00000037f4207cd1 in start_thread (arg=0x7fffebbc5700) at
pthread_create.c:305
__res = <optimized out>
pd = 0x7fffebbc5700
now = <optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {1,
1739847356571702538, 140737488344288, 140737148377536, 0, 3,
-1739802828983249654, 1750428778229257482}, mask_was_saved = 0}}, priv =
{pad = {0x0, 0x0, 0x0, 0x0}, data = {prev =
0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
pagesize_m1 = <optimized out>
sp = <optimized out>
freesize = <optimized out>
__PRETTY_FUNCTION__ = "start_thread"
#5 0x00000037f3ae046d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115
No locals.
(gdb)
|
|
From: Louigi V. <lou...@gm...> - 2011-06-03 07:20:42
|
Correction: http://www.louigiverona.ru/files/seascape.ogg On Fri, Jun 3, 2011 at 11:20 AM, Louigi Verona <lou...@gm...>wrote: > Hey guys! Frank! > > > Gave git version a try - no more stops!!! > > No crashes so far, I will report if any. > > As proof, I've recorded a hypnotic tune. Some rough spots there due to live > recording and no attention to levels peaking at times, but in general I > think it is listenable: > http://www.louigiverona.ru/seascape.ogg > > > > > -- > Louigi Verona > http://www.louigiverona.ru/ > -- Louigi Verona http://www.louigiverona.ru/ |
|
From: Brendan J. <bre...@gm...> - 2011-06-03 10:58:22
|
On 06/03/2011 05:20 PM, Louigi Verona wrote: > Correction: http://www.louigiverona.ru/files/seascape.ogg > > On Fri, Jun 3, 2011 at 11:20 AM, Louigi Verona <lou...@gm... > <mailto:lou...@gm...>> wrote: > > Hey guys! Frank! > > > Gave git version a try - no more stops!!! > > No crashes so far, I will report if any. > > As proof, I've recorded a hypnotic tune. Some rough spots there due > to live recording and no attention to levels peaking at times, but > in general I think it is listenable: > http://www.louigiverona.ru/seascape.ogg That's awesome Louigi... I'll have to check out your other stuff... I can confirm that the stoppage issue has also been fixed with the latest git snap shot. Been running now for over an hour with a mix of arsps lfo's and sequencers. I'm pretty bowled over by this piece of software - the possibilities are endless with that LFO ... time to dig out those MIDI control codes... Frank, I noticed the autoconf stuff is not in the tree I cloned. I just pulled em in from the release source. I've packaged here if anyone wants to test on Fedora: http://bsjones.fedorapeople.org/qmidiarp-0.4.1-2.git20110602.fc15.src.rpm and http://bsjones.fedorapeople.org/qmidiarp-0.4.1-2.git20110602.fc15.x86_64.rpm |
|
From: Frank K. <goe...@ya...> - 2011-06-03 11:10:43
|
>________________________________ >De : Louigi Verona <lou...@gm...> >À : Frank Kober <goe...@ya...> >Cc : "bre...@gm..." <bre...@gm...>; "qmi...@li..." <qmi...@li...> >Envoyé le : Vendredi 3 Juin 2011 9h20 >Objet : Re: Re : Re : [Qmidiarp-devel] Some feedback on QMidiArp 0.4.1 > > >Correction: http://www.louigiverona.ru/files/seascape.ogg > > >On Fri, Jun 3, 2011 at 11:20 AM, Louigi Verona <lou...@gm...> wrote: > >Hey guys! Frank! >> >> >>Gave git version a try - no more stops!!! >> >>No crashes so far, I will report if any. >> >>As proof, I've recorded a hypnotic tune. Some rough spots there due to live recording and no attention to levels peaking at times, but in general I think it is listenable: Hi Louigi, an awesome piece! You already know that I do like your music a lot, much of the ambient stuff is on my mp3 player already and I'm a fan of "Inside an Echo chamber". This seascape piece is wonderful and I think about "Brave old sequence" by the old german guy :D, it's a bit what I wanted to use qmidiarp for, too, very nice play with filter-lfos! Thanks so much for sharing this. BTW, there is a small demo piece I did quite some time ago, it is much too overloaded and aggressive, but....it's only a demo piece :) http://www.linuxmao.org/tikiwiki/tiki-download_file.php?fileId=189 Frank |
|
From: Frank K. <goe...@ya...> - 2011-06-03 11:27:54
|
----- Mail original ----- > De : Brendan Jones <bre...@gm...> > Frank, I noticed the autoconf stuff is not in the tree I cloned. I just > pulled em in from the release source. I've packaged here if anyone wants > to test on Fedora: > http://bsjones.fedorapeople.org/qmidiarp-0.4.1-2.git20110602.fc15.src.rpm and > > http://bsjones.fedorapeople.org/qmidiarp-0.4.1-2.git20110602.fc15.x86_64.rpm > > Brendan, this is normal, when building from git, a autoreconf -i before ./configure should create all needed files. For distribution, maybe the best for now would be to apply the patch I just dropped in the release folder... I'd like to wait a bit and collect more possible issues before a new version. Thanks for the fedora rpms, btw I have updated the mandriva rpms with the patches, if you're interested in the specs, look here, but you won't learn much new there :) http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages?revision=682625&view=revision Cheers Frank |
|
From: Brendan J. <bre...@gm...> - 2011-06-03 11:55:51
|
On 06/03/2011 09:27 PM, Frank Kober wrote: > ----- Mail original ----- > >> De : Brendan Jones<bre...@gm...> > >> Frank, I noticed the autoconf stuff is not in the tree I cloned. I just >> pulled em in from the release source. I've packaged here if anyone wants >> to test on Fedora: >> http://bsjones.fedorapeople.org/qmidiarp-0.4.1-2.git20110602.fc15.src.rpm and >> >> http://bsjones.fedorapeople.org/qmidiarp-0.4.1-2.git20110602.fc15.x86_64.rpm >> >> > > Brendan, this is normal, when building from git, a > > autoreconf -i > before ./configure > > should create all needed files. Of course. I won't be pushing any updates (other than rawhide) until we've given it a touch more time... Thanks again B |
|
From: Brendan J. <bre...@gm...> - 2011-06-03 21:58:45
|
On 06/03/2011 09:10 PM, Frank Kober wrote: > > > >> ________________________________ >> De : Louigi Verona<lou...@gm...> >> À : Frank Kober<goe...@ya...> >> Cc : "bre...@gm..."<bre...@gm...>; "qmi...@li..."<qmi...@li...> >> Envoyé le : Vendredi 3 Juin 2011 9h20 >> Objet : Re: Re : Re : [Qmidiarp-devel] Some feedback on QMidiArp 0.4.1 >> >> >> Correction: http://www.louigiverona.ru/files/seascape.ogg >> >> >> On Fri, Jun 3, 2011 at 11:20 AM, Louigi Verona<lou...@gm...> wrote: >> >> Hey guys! Frank! >>> >>> >>> Gave git version a try - no more stops!!! >>> >>> No crashes so far, I will report if any. >>> >>> As proof, I've recorded a hypnotic tune. Some rough spots there due to live recording and no attention to levels peaking at times, but in general I think it is listenable: > > > Hi Louigi, > > an awesome piece! You already know that I do like your music a lot, much of the ambient stuff is on my mp3 player already and I'm a fan of "Inside an Echo chamber". > > This seascape piece is wonderful and I think about "Brave old sequence" by the old german guy :D, it's a bit what I wanted to use qmidiarp for, too, very nice play with filter-lfos! > > Thanks so much for sharing this. > > BTW, there is a small demo piece I did quite some time ago, it is much too overloaded and aggressive, but....it's only a demo piece :) > > > http://www.linuxmao.org/tikiwiki/tiki-download_file.php?fileId=189 > > > Frank > Powerful stuff Frank! Love to hear where you end up with that one. Just an update - I have not experienced any crashes or stoppages - only one very minor issue with the Transpose slider in the sequencer. It only works with the mouse if you drag on the slider knob directly - if you click anywhere on the slider the slider knob itself moves but the key is uchanged. As I said minor - I can't really see why you'd want to control the key by sight in this way. Dragging the knob, or using the textbox or ext. MIDI controller works as expected. |
|
From: Frank K. <goe...@ya...> - 2011-06-05 08:30:43
|
Thanks Brendan, ----- Mail original ----- > De : Brendan Jones <bre...@gm...> > À : qmi...@li... > Cc : > Envoyé le : Vendredi 3 Juin 2011 23h53 > Objet : [Qmidiarp-devel] Re : Some feedback on QMidiArp 0.4.1 > Just an update - I have not experienced any crashes or stoppages - only > one very minor issue with the Transpose slider in the sequencer. It only > works with the mouse if you drag on the slider knob directly - if you > click anywhere on the slider the slider knob itself moves but the key is > uchanged. As I said minor - I can't really see why you'd want to control > > the key by sight in this way. Dragging the knob, or using the textbox or > ext. MIDI controller works as expected. > This is fixed on git now, it was supposed to be a "feature" but it didn't work with MIDI CC... Good catch Cheers Frank |
Thanks for helping keep SourceForge clean.
X