qmidiarp-devel — discussion on qmidiarp development

[Qmidiarp-devel] Re : Re : Some feedback on QMidiArp 0.4.1

[Frank K. <goe...@ya...>]

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

Re: [Qmidiarp-devel] Re : Some feedback on QMidiArp 0.4.1

[Brendan J. <bre...@gm...>]

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)

Re: [Qmidiarp-devel] Re : [LAU] Re : Fixed QMidiArp 0.4.1 released

[Jeremy J. <je...@au...>]

On 06/02/2011 05:08 PM, Frank Kober wrote:
>
>
> Hello,
>
>
> ----- Mail original -----
> De : michael noble<lo...@gm...>
> À : Frank Kober<goe...@ya...>
> Cc :
> Envoyé le : Jeudi 2 Juin 2011 8h41
> Objet : Re: [LAU] Re : Fixed QMidiArp 0.4.1 released
>
> Hi Frank,
>
> Thanks for the reply. I tried the new release last night and the new
> features are great. I'm really happy you are working on this app. I
> still had some issues with transport stopping and some other random
> crashing issues. I don't have time to give detailed info until the
> weekend, but I'll try to give you usable debug info then.
>
> -Michael
>
> ----------------
>
> I think I've found the error causing this when syncing externally and only arps present. I've pushed a fix to the git repo, which you can obtain using
>
> git clone git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp
>
> When building for the first time after git checkout please do
> autoreconf -i
> before ./configure --blahblah
>
> Jeremy also found that the sync globally improves when using not too high jack latencies. Please report on the 'random crashes' as well
>
> Frank

Hello Frank,

JACK synchronization works fine now with just one arp module! Haven't 
had any crashes yet but as I used QMidiArp from Debian Multimedia git 
(http://anonscm.debian.org/gitweb/?p=pkg-multimedia/qmidiarp.git;a=summary) 
to build QMidiArp the source package also produces a dbg binary.
Speaking of Debian Multimedia, the git repository for QMidiArp contains 
a patch for the man page: 
http://anonscm.debian.org/gitweb/?p=pkg-multimedia/qmidiarp.git;a=blob;f=debian/patches/0001-manpages_fix.patch;h=d0ee087a4ad522e88ee53cf37af34293420951c9;hb=31981d0fe48f614e15b0046a7062739a1a424503
I've also included the patch, maybe it could be fixed upstream? Thanks 
for the fixes and thanks for such a wonderful app!

Best,

Jeremy

Re: [Qmidiarp-devel] Re : Some feedback on QMidiArp 0.4.1

[Louigi V. <lou...@gm...>]

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/

[Qmidiarp-devel] Re : Some feedback on QMidiArp 0.4.1

[Frank K. <goe...@ya...>]

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

[Qmidiarp-devel] Re : [LAU] Re : Fixed QMidiArp 0.4.1 released

[Frank K. <goe...@ya...>]

Hello,


----- Mail original -----
De : michael noble <lo...@gm...>
À : Frank Kober <goe...@ya...>
Cc : 
Envoyé le : Jeudi 2 Juin 2011 8h41
Objet : Re: [LAU] Re : Fixed QMidiArp 0.4.1 released

Hi Frank,

Thanks for the reply. I tried the new release last night and the new
features are great. I'm really happy you are working on this app. I
still had some issues with transport stopping and some other random
crashing issues. I don't have time to give detailed info until the
weekend, but I'll try to give you usable debug info then.

-Michael

----------------

I think I've found the error causing this when syncing externally and only arps present. I've pushed a fix to the git repo, which you can obtain using

git clone git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp

When building for the first time after git checkout please do
autoreconf -i 
before ./configure --blahblah

Jeremy also found that the sync globally improves when using not too high jack latencies. Please report on the 'random crashes' as well

Frank

Re: [Qmidiarp-devel] Some feedback on QMidiArp 0.4.1

[Brendan J. <bre...@gm...>]

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

[Qmidiarp-devel] Some feedback on QMidiArp 0.4.1

[Louigi V. <lou...@gm...>]

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/

[Qmidiarp-devel] Re : [LAU] Fixed QMidiArp 0.4.1 released

[Frank K. <goe...@ya...>]

Hi Jeremy, hi Michael,

I checked this, and I confirm a problem with external sync transport start when only arp modules are present in the setup. It works without glitches here when at least one lfo OR seq module is in the setup, but I need to do fixing. Can you confirm this?


I also remember Torben alerting about changes in the recent jack1 transport interface, which might lead to problems (that was for seq24), and I'd appreciate advice on this if this IS an issue. I use jack2 and have no issues.


Michael, the handling of the sequencer module has been changed so that these 'getting off the hook' issues should not happen anymore, please report if they do.


Could we continue this on either #qmidiarp IRC or qmidiarp-devel sf mailing list?

Cheers
Frank



----- Mail original -----
De : Jeremy Jongepier <je...@au...>
À : lin...@li...
Cc : 
Envoyé le : Mardi 31 Mai 2011 9h49
Objet : Re: [LAU] Fixed QMidiArp 0.4.1 released

On 05/29/2011 09:49 AM, Frank Kober wrote:
> A forgotten entry in the source file lists made that qmidiarp-0.4.0 didn't build.
> 
> Here is an updated version that should be fine, it also contains a Czech translation fix by Pavel
> 
> With my excuses, please try qmidiarp-0.4.1
> 
> Frank
> 
> ----------------------------------
> qmidiarp-0.4.1 (2011-05-29)
> 
> New Features
>   o All modules now have a playhead cursor
>   o LFOs can record controller data by a MIDI-learnable Record button.
>   o Seq modules handle note events at the input for triggering
>   o Spanish translation thanks to Pedro Lopez-Cabanillas (plcl)
>   o Czech translation thanks to Pavel Fric
>   o Functional doxygen documentation available by "make doxygen-doc"
>   o New SVG icon and desktop file
> 
> QMidiArp is available for download at
> 
> http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.1/qmidiarp-0.4.1.tar.bz2/download
> 
> Project page
> 
> http://qmidiarp.sourceforge.net/
> 
> Git repo (developers welcome)
> 
> git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp
> 

Hello Frank,

This is a great app, thanks! Somehow I can't get JACK Sync or MIDI Clock
sync working, sometimes QMidiArp does respond and its transport starts
running but most of the time it does nothing at all. I've tried with
several JACK Transport/MIDI apps (seq24, Qtractor) and on different
machines, to no avail. Hopefully I'm overseeing something and this is
mere PEBKAC.

Best,

Jeremy
_______________________________________________
Linux-audio-user mailing list
Lin...@li...
http://lists.linuxaudio.org/listinfo/linux-audio-user

[Qmidiarp-devel] Fixed QMidiArp 0.4.1 released

[Frank K. <goe...@ya...>]

A forgotten entry in the source file lists made that qmidiarp-0.4.0 didn't build.

Here is an updated version that should be fine, it also contains a Czech translation fix by Pavel

With my excuses, please try qmidiarp-0.4.1

Frank

----------------------------------
qmidiarp-0.4.1 (2011-05-29)

New Features
  o All modules now have a playhead cursor
  o LFOs can record controller data by a MIDI-learnable Record button.
  o Seq modules handle note events at the input for triggering
  o Spanish translation thanks to Pedro Lopez-Cabanillas (plcl)
  o Czech translation thanks to Pavel Fric
  o Functional doxygen documentation available by "make doxygen-doc"
  o New SVG icon and desktop file

QMidiArp is available for download at

http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.1/qmidiarp-0.4.1.tar.bz2/download

Project page

http://qmidiarp.sourceforge.net/

Git repo (developers welcome)

git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp

[Qmidiarp-devel] QMidiArp 0.4.0 released

[Frank K. <goe...@ya...>]

Hello all,

Work is underway, mainly stimulated and supported by Nedko Arnaudov, to 
make this animal handle JACK MIDI natively. It is far from being 
finished, so it is not time for this today, but since January, some 
other handy features have sneaked in making it worth to give an update.

Playhead cursors, waveform-recording MIDI LFOs, some new MIDI 
controllables and a finer step sequencer control by the keyboard are the
 main new features coming with QMidiArp 0.4.0. 

Enjoy!

----------------------------------
qmidiarp-0.4.0 (2011-05-28)

New Features
  o All modules now have a playhead cursor
  o LFOs can record controller data by a MIDI-learnable Record button.
  o Seq modules handle note events at the input for triggering
  o Spanish translation thanks to Pedro Lopez-Cabanillas (plcl)
  o Czech translation thanks to Pavel Fric
  o Functional doxygen documentation available by "make doxygen-doc"
  o New SVG icon and desktop file

QMidiArp is available for download at

http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.0/qmidiarp-0.4.0.tar.bz2/download

Project page

http://qmidiarp.sourceforge.net/

Git repo (developers welcome)

git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp

[Qmidiarp-devel] Re : qmidiarp doxygen

[Frank K. <goe...@ya...>]

Hi Nedko

--- En date de : Ven 25.2.11, Nedko Arnaudov <ne...@ar...> a écrit :

> I've found a small bug with the generation of the
> documentation and i've
> made a fix that can be seen here:
> 
Thank you for having had a look, any other comments welcome!

If you don't mind I've given you commit acces to the sourceforge git repo, so you can commit it yourself, otherwise I'll do it

Be on irc in a cpl of hours

Cheers
Frank



      

[Qmidiarp-devel] Re : Fwd: QMidiArp - Czech translation

[Frank K. <goe...@ya...>]

Hi Pedro and Pavel,

--- En date de : Ven 11.2.11, Pedro Lopez-Cabanillas <ped...@gm...> a écrit :

> Hi Frank,
> 
> Here is the Czech translation of QMidiArp. Pavel is also
> the translator of VMPK and many other music programs. 
> 
> Regards,
> Pedro
> 
> ----------  Forwarded Message  ----------
> 
> Asunto: QMidiArp - Czech translation
> Fecha: Friday 11 February 2011
> De: Pavel Fric <pav...@se...>

>> I translated the file for QMidiArp, but I didn't find any

Thanks very much Pavel for your work, it is on git master now

BTW: you can use either the mailing lists qmi...@li... or the tracker :)

Best
Frank