seq24-users — A place for seq24 users to ask questions and share ideas.

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Alex <x37...@gm...>]

Yeah, I'll check it out soon..
I have a 707 which sends midi clock messages out even when the
sequence isn't "running"

-Alex

On Fri, Jun 26, 2009 at 9:29 AM, Guido Scholz<gui...@ba...> wrote:
> Am Thu, 25. Jun 2009 um 18:37:43 -0700 schrieb Alex:
>
> Hi Alex,
>
>> > MIDI Clock:
>> >  * if not running, start running
>
>> This is incorrect.  Masters may send clock messages even if slaves
>> shouldn't be syncing... before a start or continue message is sent or
>> after a stop message is sent.
>
> Sorry, my description was too short. The current implementation does
> something like this:
>
> MIDI Clock:
>   * if not running, but prepared to run by "Start" or "Continue" then
>    start running
>
> This should comply to the text below (as far as I understand):
>
>> "A master stops the slave simultaneously by sending a MIDI Stop
>> message. The master may then continue to send MIDI Clocks at the rate
>> of its tempo, but the slave should ignore these, and not advance its
>> "song position". Of course, the slave may use these continuing MIDI
>> Clocks to ascertain what the master's tempo is at all times. "
>
>
>> MIDI sync in for seq24, awesome!
>
> Are you able to run tests of the current code with your hardware?
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKRPdPk6cKJms5yBsRAgx7AJ4y2V+VR/9SzTagYMWF+yr/Q9cWCwCfUlwq
> 3gjrKWhG9r4hDU3biWSgsKQ=
> =q1/X
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

>> It is already fixed (rev 71).

ah, bazaar must be slow then, as I checked and it was still at rev70 when I
made my recent email
sorry for the confusion.
i'll check out the latest tonight when i'm home.

thanks for following up on all this Guido,
---
kevin meinert | http://www.subatomicglue.com


On Fri, Jun 26, 2009 at 12:36 PM, Guido Scholz
<gui...@ba...>wrote:

> Am Fri, 26. Jun 2009 um 11:56:35 -0500 schrieb Kevin Meinert:
>
> Hi Kevin,
>
> > Your code breaks continue support.  I verified this by testing with a
> yamaha
> > rm1x.
>
> yes, I understood this fact from your previous e-mail. It is already fixed
> (rev 71).
> This bug was caused by usage of the "stop()" function in the "MIDI stop"
> action
> (stop() does also a reset).
>
> The "continue" should work again now (untested).
>
> > start/stop worked.
> > I didn't have a device that spams clock messages to see what happens in
> the
> > case of STOP then CLOCKs with your code, but from reading the code, I
> don't
> > know that what you have would be desireable (to start the sequencer on a
> > CLOCK message while STOPped...)
>
> I found also other literature pointing out a "start" needs at least two
> MIDI RT messages: "Start" and the first "Clock". Same with "Continue".
>
>
> The current user interface of seq24 is missing a "stop" button acting only
> as
> a stop, not stop + reset. This fact was already complained about by other
> users
> and is clearly a disadvantage if one plays around with this kind of MIDI
> signals.
>
> May be we should add a reset button "|<", resetting the position to the
> very beginning and the stop button should be changed to only make a
> stop, but nothing more.
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKRQcCk6cKJms5yBsRAgm1AJ9AZsrO2zcmxgKUR3qP0lALExK26gCghhGz
> hJeaT73M84yKDci8WYiJisU=
> =Y93k
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Guido S. <gui...@ba...>]

Am Fri, 26. Jun 2009 um 11:56:35 -0500 schrieb Kevin Meinert:

Hi Kevin,

> Your code breaks continue support.  I verified this by testing with a yamaha
> rm1x.

yes, I understood this fact from your previous e-mail. It is already fixed (rev 71).
This bug was caused by usage of the "stop()" function in the "MIDI stop" action
(stop() does also a reset).

The "continue" should work again now (untested).

> start/stop worked.
> I didn't have a device that spams clock messages to see what happens in the
> case of STOP then CLOCKs with your code, but from reading the code, I don't
> know that what you have would be desireable (to start the sequencer on a
> CLOCK message while STOPped...)

I found also other literature pointing out a "start" needs at least two
MIDI RT messages: "Start" and the first "Clock". Same with "Continue".


The current user interface of seq24 is missing a "stop" button acting only as
a stop, not stop + reset. This fact was already complained about by other users
and is clearly a disadvantage if one plays around with this kind of MIDI signals.

May be we should add a reset button "|<", resetting the position to the
very beginning and the stop button should be changed to only make a
stop, but nothing more.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

#1
>> MIDI Clock:
>>  * if not running, but prepared to run by "Start" or "Continue" then
>>  start running

#2
>> The master may then continue to send MIDI Clocks at the rate
> of its tempo, but the slave should ignore these, and not advance its
> "song position".


These two statements are different.   In #1 You say (and your code change
reflected this) that on a midi clock message, it "prepares to start ... then
start(s) running"...      But the spec you pasted in #2 says that the slave
should ignore the clock messages until it's actually running...  (which
makes a lot more sense in practice, from observing what devices do, and
thinking about what they could do incorrectly)...

Your code breaks continue support.  I verified this by testing with a yamaha
rm1x.
start/stop worked.
I didn't have a device that spams clock messages to see what happens in the
case of STOP then CLOCKs with your code, but from reading the code, I don't
know that what you have would be desireable (to start the sequencer on a
CLOCK message while STOPped...)

---
kevin meinert | http://www.subatomicglue.com


On Fri, Jun 26, 2009 at 11:29 AM, Guido Scholz
<gui...@ba...>wrote:

> Am Thu, 25. Jun 2009 um 18:37:43 -0700 schrieb Alex:
>
> Hi Alex,
>
> > > MIDI Clock:
> > >  * if not running, start running
>
> > This is incorrect.  Masters may send clock messages even if slaves
> > shouldn't be syncing... before a start or continue message is sent or
> > after a stop message is sent.
>
> Sorry, my description was too short. The current implementation does
> something like this:
>
> MIDI Clock:
>   * if not running, but prepared to run by "Start" or "Continue" then
>    start running
>
> This should comply to the text below (as far as I understand):
>
> > "A master stops the slave simultaneously by sending a MIDI Stop
> > message. The master may then continue to send MIDI Clocks at the rate
> > of its tempo, but the slave should ignore these, and not advance its
> > "song position". Of course, the slave may use these continuing MIDI
> > Clocks to ascertain what the master's tempo is at all times. "
>
>
> > MIDI sync in for seq24, awesome!
>
> Are you able to run tests of the current code with your hardware?
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKRPdPk6cKJms5yBsRAgx7AJ4y2V+VR/9SzTagYMWF+yr/Q9cWCwCfUlwq
> 3gjrKWhG9r4hDU3biWSgsKQ=
> =q1/X
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Guido S. <gui...@ba...>]

Am Thu, 25. Jun 2009 um 18:37:43 -0700 schrieb Alex:

Hi Alex,

> > MIDI Clock:
> >  * if not running, start running
 
> This is incorrect.  Masters may send clock messages even if slaves
> shouldn't be syncing... before a start or continue message is sent or
> after a stop message is sent.

Sorry, my description was too short. The current implementation does
something like this:

MIDI Clock:
  * if not running, but prepared to run by "Start" or "Continue" then
    start running

This should comply to the text below (as far as I understand):

> "A master stops the slave simultaneously by sending a MIDI Stop
> message. The master may then continue to send MIDI Clocks at the rate
> of its tempo, but the slave should ignore these, and not advance its
> "song position". Of course, the slave may use these continuing MIDI
> Clocks to ascertain what the master's tempo is at all times. "


> MIDI sync in for seq24, awesome!

Are you able to run tests of the current code with your hardware?

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

tested using x0xb0x -> seq24

and yamaha rm1x -> seq24

appears to work...


however, neither of these tests continue, or set song position   (i tried
the << and >> on the rm1x but it simply restarted the se24 at the beginning
of the loop....   no idea what it's supposed to do, i didn't trace the
messages......)

Looking at the code, I don't think CLOCK should start the sequencer.   I'd
do something more like this, much less drastic change to the old code too
(should be safer):


                    // Obey MidiTimeClock:
                    if (ev.get_status() == EVENT_MIDI_START)
                    {
                        if (!m_midiclockrunning)
                        {
                            stop();
                            start( false );
                            m_midiclockrunning = true;
                            m_usemidiclock = true;
                            m_midiclocktick = 0;
                            m_midiclockpos = 0;
                        }
                    }
                    // midi continue: start from current pos.
                    else if (ev.get_status() == EVENT_MIDI_CONTINUE)
                    {
                        if (!m_midiclockrunning)
                        {
                            m_midiclockrunning = true;
                            start( false );
                            //m_usemidiclock = true;
                        }
                    }
                    else if (ev.get_status() == EVENT_MIDI_STOP)
                    {
                        // no harm stopping again, if there's a stuck note,
it could be useful to reissue...
                        //if (m_midiclockrunning)
                        //{
                            // do nothing, just let the system pause
                            // since we're not getting ticks after the stop,
the song wont advance
                            // when start is recieved, we'll reset the
position, or
                            // when continue is recieved, we wont
                            m_midiclockrunning = false;
                            all_notes_off();
                        //}
                    }
                    else if (ev.get_status() == EVENT_MIDI_CLOCK)
                    {
                         if (m_midiclockrunning)
                            m_midiclocktick += 8;
                    }
                    // not tested (todo: test it!)
                    else if (ev.get_status() == EVENT_MIDI_SONG_POS)
                    {
                         unsigned char a, b;
                         ev.get_data( &a, &b );
                         m_midiclockpos = ((int)a << 7) && (int)b;
                    }

---
kevin meinert | http://www.subatomicglue.com


On Thu, Jun 25, 2009 at 3:19 PM, Guido Scholz <gui...@ba...>wrote:

> Am Thu, 25. Jun 2009 um 12:45:35 -0500 schrieb Kevin Meinert:
>
> Hi all,
>
> > Let me know if you were planning to do it yourself and I'll ignore it. :)
> > Should be an easy change either way.
>
> done, but completely untested. Does anybody have spare time (and
> equipment) for a test?
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKQ9vek6cKJms5yBsRAknOAKCcHwLhqJUDU6vmj1KjTpyR47ORAwCghRPZ
> KoBuuwxOJtRILv9g3Txdnys=
> =El6s
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

going back to my old code, yeah, the rm1x seems to send CONTINUE with the
play button, and stop with the stop button.   then you can start over by
hitting the < back button, then play again...

Your new code in rev70 broke at least the continue functionality.    The
code I pasted below works with start/stop/continue/clock with rm1x, and
start/stop/clock on x0xb0x (no continue there as far as i can tell)...   not
sure about pos... or how to test that.

---
kevin meinert | http://www.subatomicglue.com


On Thu, Jun 25, 2009 at 11:26 PM, Kevin Meinert <ke...@su...>wrote:

>
> tested using x0xb0x -> seq24
>
> and yamaha rm1x -> seq24
>
> appears to work...
>
>
> however, neither of these tests continue, or set song position   (i tried
> the << and >> on the rm1x but it simply restarted the se24 at the beginning
> of the loop....   no idea what it's supposed to do, i didn't trace the
> messages......)
>
> Looking at the code, I don't think CLOCK should start the sequencer.   I'd
> do something more like this, much less drastic change to the old code too
> (should be safer):
>
>
>                     // Obey MidiTimeClock:
>                     if (ev.get_status() == EVENT_MIDI_START)
>                     {
>                         if (!m_midiclockrunning)
>                         {
>                             stop();
>                             start( false );
>                             m_midiclockrunning = true;
>                             m_usemidiclock = true;
>                             m_midiclocktick = 0;
>                             m_midiclockpos = 0;
>                         }
>                     }
>                     // midi continue: start from current pos.
>                     else if (ev.get_status() == EVENT_MIDI_CONTINUE)
>                     {
>                         if (!m_midiclockrunning)
>                         {
>                             m_midiclockrunning = true;
>                             start( false );
>                             //m_usemidiclock = true;
>                         }
>                     }
>                     else if (ev.get_status() == EVENT_MIDI_STOP)
>                     {
>                         // no harm stopping again, if there's a stuck note,
> it could be useful to reissue...
>                         //if (m_midiclockrunning)
>                         //{
>                             // do nothing, just let the system pause
>                             // since we're not getting ticks after the
> stop, the song wont advance
>                             // when start is recieved, we'll reset the
> position, or
>                             // when continue is recieved, we wont
>                             m_midiclockrunning = false;
>                             all_notes_off();
>                         //}
>                     }
>                     else if (ev.get_status() == EVENT_MIDI_CLOCK)
>                     {
>                          if (m_midiclockrunning)
>                             m_midiclocktick += 8;
>                     }
>                     // not tested (todo: test it!)
>                     else if (ev.get_status() == EVENT_MIDI_SONG_POS)
>                     {
>                          unsigned char a, b;
>                          ev.get_data( &a, &b );
>                          m_midiclockpos = ((int)a << 7) && (int)b;
>                     }
>
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Thu, Jun 25, 2009 at 3:19 PM, Guido Scholz <gui...@ba...>wrote:
>
>> Am Thu, 25. Jun 2009 um 12:45:35 -0500 schrieb Kevin Meinert:
>>
>> Hi all,
>>
>> > Let me know if you were planning to do it yourself and I'll ignore it.
>> :)
>> > Should be an easy change either way.
>>
>> done, but completely untested. Does anybody have spare time (and
>> equipment) for a test?
>>
>> Guido
>>
>> --
>> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
>> http://www.lug-burghausen.org/
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFKQ9vek6cKJms5yBsRAknOAKCcHwLhqJUDU6vmj1KjTpyR47ORAwCghRPZ
>> KoBuuwxOJtRILv9g3Txdnys=
>> =El6s
>> -----END PGP SIGNATURE-----
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> seq24-users mailing list
>> seq...@li...
>> https://lists.sourceforge.net/lists/listinfo/seq24-users
>>
>>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

true, I didn't notice this part.   some devices send clocks all the time...
so you only want to act on them if you got a start...

midi sync works already, Alex.  though like guido points out, it may be
lacking some checks.   Another person verified it maybe a month ago as
well...
I've tested x0xb0x -> seq24 as well as  seq24 -> seq24

---
kevin meinert | http://www.subatomicglue.com


On Thu, Jun 25, 2009 at 8:37 PM, Alex <x37...@gm...> wrote:

> > MIDI Clock:
> >  * if not running, start running
> >
>
> This is incorrect.  Masters may send clock messages even if slaves
> shouldn't be syncing... before a start or continue message is sent or
> after a stop message is sent.
>
> "A master stops the slave simultaneously by sending a MIDI Stop
> message. The master may then continue to send MIDI Clocks at the rate
> of its tempo, but the slave should ignore these, and not advance its
> "song position". Of course, the slave may use these continuing MIDI
> Clocks to ascertain what the master's tempo is at all times. "
>
> The clock ticks are simply for syncing, the start/stop/continue are
> what you use to initiate or end playback.
>
> MIDI sync in for seq24, awesome!
>
> -Alex
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Alex <x37...@gm...>]

> MIDI Clock:
>  * if not running, start running
>

This is incorrect.  Masters may send clock messages even if slaves
shouldn't be syncing... before a start or continue message is sent or
after a stop message is sent.

"A master stops the slave simultaneously by sending a MIDI Stop
message. The master may then continue to send MIDI Clocks at the rate
of its tempo, but the slave should ignore these, and not advance its
"song position". Of course, the slave may use these continuing MIDI
Clocks to ascertain what the master's tempo is at all times. "

The clock ticks are simply for syncing, the start/stop/continue are
what you use to initiate or end playback.

MIDI sync in for seq24, awesome!

-Alex

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

would be happy to try it tonight, but it'll probably be around 6-7hrs from
now, i have a dorkbot meeting i'm attending tonight...

---
kevin meinert | http://www.subatomicglue.com


On Thu, Jun 25, 2009 at 3:19 PM, Guido Scholz <gui...@ba...>wrote:

> Am Thu, 25. Jun 2009 um 12:45:35 -0500 schrieb Kevin Meinert:
>
> Hi all,
>
> > Let me know if you were planning to do it yourself and I'll ignore it. :)
> > Should be an easy change either way.
>
> done, but completely untested. Does anybody have spare time (and
> equipment) for a test?
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKQ9vek6cKJms5yBsRAknOAKCcHwLhqJUDU6vmj1KjTpyR47ORAwCghRPZ
> KoBuuwxOJtRILv9g3Txdnys=
> =El6s
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Guido S. <gui...@ba...>]

Am Thu, 25. Jun 2009 um 12:45:35 -0500 schrieb Kevin Meinert:

Hi all,

> Let me know if you were planning to do it yourself and I'll ignore it. :)
> Should be an easy change either way.

done, but completely untested. Does anybody have spare time (and
equipment) for a test?

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

sounds reasonable.   Without looking at the code - I think you're pointing
out that I don't do the "if running" checks.

I can add that.   I will try to get it done within the next week...   Or...
Let me know if you were planning to do it yourself and I'll ignore it. :)
Should be an easy change either way.

---
kevin meinert | http://www.subatomicglue.com


On Thu, Jun 25, 2009 at 12:31 PM, Guido Scholz
<gui...@ba...>wrote:

> Am Tue, 14. Apr 2009 um 21:43:24 -0500 schrieb Kevin Meinert:
>
> > Hello Everyone,
>
> Hi Kevin,
>
> > Attached is a patch to upgrade perform.cpp and perform.h to have the Midi
> > Clock Sync feature.   Test it out and tell me how it goes.
>
> [...]
>
> > documentation:
> > ==============================================================
> > Midi Clock input:
> >
> > seq24 will slave off of incoming MidiClock messages
> > 0xfc 0xfa 0xf8   (start stop and tick)
> >
> > This has been tested with another seq24 instance (stop/start works)
> > This has been tested with a x0xb0x in (start/stop works)
> >
> > It will also pay attention to 0xfb (continue) and 0xf2 (Midi Song Pos)
> but
> > these aren't tested...
>
> I would like to come back to this topic. Some weeks ago I followed a
> discussion on the Linux Audio User (LAU) mailinglist, dealing with MIDI
> clock support:
>
> http://lists.linuxaudio.org/pipermail/linux-audio-user/2009-May/060534.html
>
> Reading our code I found the current implementation in seq24 is not at a
> perfect state. I spend some time to look for an internet resource about
> this topic and found this article, giving some clear statements about
> how a "MIDI clock client" should behave:
>
>  http://home.roadrunner.com/~jgglatt/tech/midispec/seq.htm<http://home.roadrunner.com/%7Ejgglatt/tech/midispec/seq.htm>
>
> The current code is not so far away from the theory, but there are some
> basic differences. As I understand the MIDI events should trigger
> actions like this:
>
> MIDI Start:
>  * Prepare for a start at the very beginning of the song
>  * if running, ignore this event
>
> MIDI Continue:
>  * Prepare for a start at the current position
>  * if running, ignore this event
>
> MIDI Clock:
>  * if not running, start running
>
> MIDI song position:
>  * if running, ignore event else update position
>
> MIDI Stop:
>  * if running, stop else ignore event
>
> Do you agree?
> Guido
>
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKQ7R6k6cKJms5yBsRAgkyAJ9+99uiiWmdRUJ84LSPddQR/tByOwCeM7X0
> QZZaAx4t/RDyRHr1s70yXRY=
> =uQgE
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Guido S. <gui...@ba...>]

Am Tue, 14. Apr 2009 um 21:43:24 -0500 schrieb Kevin Meinert:

> Hello Everyone,

Hi Kevin,

> Attached is a patch to upgrade perform.cpp and perform.h to have the Midi
> Clock Sync feature.   Test it out and tell me how it goes.

[...]

> documentation:
> ==============================================================
> Midi Clock input:
> 
> seq24 will slave off of incoming MidiClock messages
> 0xfc 0xfa 0xf8   (start stop and tick)
> 
> This has been tested with another seq24 instance (stop/start works)
> This has been tested with a x0xb0x in (start/stop works)
> 
> It will also pay attention to 0xfb (continue) and 0xf2 (Midi Song Pos) but
> these aren't tested...

I would like to come back to this topic. Some weeks ago I followed a
discussion on the Linux Audio User (LAU) mailinglist, dealing with MIDI
clock support:

http://lists.linuxaudio.org/pipermail/linux-audio-user/2009-May/060534.html

Reading our code I found the current implementation in seq24 is not at a
perfect state. I spend some time to look for an internet resource about
this topic and found this article, giving some clear statements about
how a "MIDI clock client" should behave:

  http://home.roadrunner.com/~jgglatt/tech/midispec/seq.htm

The current code is not so far away from the theory, but there are some
basic differences. As I understand the MIDI events should trigger
actions like this:

MIDI Start:
  * Prepare for a start at the very beginning of the song
  * if running, ignore this event

MIDI Continue:
  * Prepare for a start at the current position
  * if running, ignore this event

MIDI Clock:
  * if not running, start running

MIDI song position:
  * if running, ignore event else update position

MIDI Stop:
  * if running, stop else ignore event

Do you agree?
Guido


-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [seq24-users] save/load for mute-groups patch

[Guido S. <gui...@ba...>]

Am Tue, 23. Jun 2009 um 23:31:57 -0500 schrieb Kevin Meinert:

Hi Kevin,

> Here's the patch:

thanks, patch is applied.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

[seq24-users] save/load for mute-groups patch

[Kevin M. <ke...@su...>]

Here's the patch:

http://www.subatomicglue.com/seq24/mutegroup-saveload-seqrollfix.patch


It includes:
 - save/load for mutegroups into the project file.
 - bugfix for the fruity sequencer.
    Added in missing "break;" that keeps the 2 interaction modes separate.
    Fixes draging while adding (painting notes), and who knows what else...



---
kevin meinert | http://www.subatomicglue.com


On Fri, Jun 19, 2009 at 12:13 PM, Kevin Meinert <ke...@su...>wrote:

>
> Coded up a patch this morning to save/load the mute-groups into the project
> file.
>
> that way ASDFG can control totally different cells in mysong.s24 than in
> myothersong.s24...
> means that your seq cells can be in any slot that you like between project
> to project...
>
>
> the .seq24rc file, as before, will just save the last used configuration of
> mute-groups.    so when starting a new project you'll get the same
> mute-groups as the last file loaded...   a nice side effect that seemed to
> work out well.
>
>
>
> will post it up in the coming days... sometime.   after doing the diff
> dance.
> ---
> kevin meinert | http://www.subatomicglue.com
>

[seq24-users] seq24 error on gentoo amd64

[Dubphil <du...@fr...>]

Hello all,

I'm on gentoo with an amd64 RT kernel and I have those errors whenever I 
try to open a seq24 file :

this one when I run seq24 alone :

GLib-ERROR **: gmem.c:136: failed to allocate 512 bytes
aborting...

this one when ecasoundhas been launch prior to seq24 :

***MEMORY-ERROR***: seq24[30257]: GSlice: failed to allocate 496 bytes 
(alignment: 512): cannot allocate memory

seq24-0.9.0
jack-0.109.2
uname -a => Linux migratis 2.6.29.1-rt7 #1 SMP Mon Apr 13 12:43:01 CEST 
2009 x86_64 AMD Turion(tm) 64 Mobile Technology ML-37 AuthenticAMD GNU/Linux

Thanks for your help.

Philippe

[seq24-users] save/load for mute-groups patch coming...

[Kevin M. <ke...@su...>]

Coded up a patch this morning to save/load the mute-groups into the project
file.

that way ASDFG can control totally different cells in mysong.s24 than in
myothersong.s24...
means that your seq cells can be in any slot that you like between project
to project...


the .seq24rc file, as before, will just save the last used configuration of
mute-groups.    so when starting a new project you'll get the same
mute-groups as the last file loaded...   a nice side effect that seemed to
work out well.



will post it up in the coming days... sometime.   after doing the diff
dance.
---
kevin meinert | http://www.subatomicglue.com

Re: [seq24-users] mute groups feature - first impressions... AND code patch for --show_keys to work....

[Guido S. <gui...@ba...>]

Am Wed, 03. Jun 2009 um 13:20:32 -0500 schrieb Kevin Meinert:

Hi Kevin,

> I have fixed all the warnings, and will post a patch sometime in the next
> couple nights...

thanks, patch is applied.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

[seq24-users] cleanup of warnings, indentation, key2text removed...

[Kevin M. <ke...@su...>]

warnings cleaned up
some indentation problems fixed
removed key2text, replace with GTK version of the same

latest version of bazaar code.
rev63<http://bazaar.launchpad.net/%7Eseq24team/seq24/trunk/revision/63>

patch:
   http://www.subatomicglue.com/seq24/cleanup-patch.patch

Re: [seq24-users] mute groups feature - first impressions... AND code patch for --show_keys to work....

[Kevin M. <ke...@su...>]

I have fixed all the warnings, and will post a patch sometime in the next
couple nights...


---
kevin meinert | http://www.subatomicglue.com


On Fri, May 29, 2009 at 2:19 PM, Kevin Meinert <ke...@su...>wrote:

> I will turn on -Wall, I don't think it's currently in my devcpp project
> file...
>
> >> the current situation is not sufficient.
> just to be clear, I do agree.  see the list below for what i think needs
> improving..
>
> >> handling a proper window/dialog layout (as in Qt).
> >> the other tabs do not expose elegancy
>
> I'm not quite sure what to picture when you say "proper" or "elegancy", at
> least specifically.
>
> so, specifically what do you want to see.  here's what I think you're
> trying to say:
> or at least this is what i think needs to happen to make it better:
> - do you want vertical/horizontal scroll bars in case the GUI widgets get
> too wide or long...
> - smart repositioning of the elements when resizing the window?
> - an apply button (ability to cancel without applying changes)
> - pretty arrangement of the text edit boxes in a regular grid pattern
> (instead of smashed against the left side)
>
> I can't see the problem with the other tabs, they're pretty minimal and
> organized pretty well.  At least when the keyboard tab isn't enlarging the
> options box so much.
>
> maybe I'm missing a feature of Qt that you're thinking of.   I haven't used
> Qt enough to guess what it could be.
>
>
> will clean up the warnings soon, sorry for those,
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Fri, May 29, 2009 at 2:09 PM, Guido Scholz <gui...@ba...>wrote:
>
>> Am Fri, 29. May 2009 um 08:44:24 -0500 schrieb Kevin Meinert:
>>
>> Hi Kevin,
>>
>> > For #3, I don't know what "layout management" is, was just following the
>> > examples in the other tabs (manual placement)...   Are you saying that
>> you'd
>> > rather that the sequence and groups grids be sized more uniformly, i.e.
>> to
>> > resemble a grid.  ?
>>
>> I am not sure about the final design, but the current situation is not
>> sufficient. Also the other tabs do not expose elegancy. I am also no GTK
>> expert and more used to Qt, but there should be some set of classes
>> handling a proper window/dialog layout (as in Qt). I only can start
>> reading here too:
>>
>>  http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/
>>
>> > I can take a stab at improving the Keyboard tab if
>> > you can tell me specifically what you'd like.  Keeping in mind my GTK
>> > experience is all google searches, and looking at other examples in
>> > seq24...  (i have win32, mfc, winforms experience so it's all familier
>> > however).  :-)
>>
>> You will have some time now, give it a go ;-). I guess there are some
>> users on the list, which will test it and give response.
>>
>> BTW: Do you use "-Wall" as a compiler option? At least you should and
>> have a look at the upcomming warnings. A whole bunch of new ones came
>> in with the last patch (I already fixed some of them).
>>
>> Guido
>>
>> --
>> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
>> http://www.lug-burghausen.org/
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFKIDLOk6cKJms5yBsRAvg8AJ0XXYhWdwD8y7i9VCoxnblzKDSAjgCfWWRT
>> OEm143wqvBGTZDsbKXOYufg=
>> =SxC9
>> -----END PGP SIGNATURE-----
>>
>>
>> ------------------------------------------------------------------------------
>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
>> is a gathering of tech-side developers & brand creativity professionals.
>> Meet
>> the minds behind Google Creative Lab, Visual Complexity, Processing, &
>> iPhoneDevCamp as they present alongside digital heavyweights like
>> Barbarian
>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
>> _______________________________________________
>> seq24-users mailing list
>> seq...@li...
>> https://lists.sourceforge.net/lists/listinfo/seq24-users
>>
>>
>

Re: [seq24-users] mute groups feature - first impressions... AND code patch for --show_keys to work....

[Kevin M. <ke...@su...>]

I will turn on -Wall, I don't think it's currently in my devcpp project
file...

>> the current situation is not sufficient.
just to be clear, I do agree.  see the list below for what i think needs
improving..

>> handling a proper window/dialog layout (as in Qt).
>> the other tabs do not expose elegancy

I'm not quite sure what to picture when you say "proper" or "elegancy", at
least specifically.

so, specifically what do you want to see.  here's what I think you're trying
to say:
or at least this is what i think needs to happen to make it better:
- do you want vertical/horizontal scroll bars in case the GUI widgets get
too wide or long...
- smart repositioning of the elements when resizing the window?
- an apply button (ability to cancel without applying changes)
- pretty arrangement of the text edit boxes in a regular grid pattern
(instead of smashed against the left side)

I can't see the problem with the other tabs, they're pretty minimal and
organized pretty well.  At least when the keyboard tab isn't enlarging the
options box so much.

maybe I'm missing a feature of Qt that you're thinking of.   I haven't used
Qt enough to guess what it could be.


will clean up the warnings soon, sorry for those,
---
kevin meinert | http://www.subatomicglue.com


On Fri, May 29, 2009 at 2:09 PM, Guido Scholz <gui...@ba...>wrote:

> Am Fri, 29. May 2009 um 08:44:24 -0500 schrieb Kevin Meinert:
>
> Hi Kevin,
>
> > For #3, I don't know what "layout management" is, was just following the
> > examples in the other tabs (manual placement)...   Are you saying that
> you'd
> > rather that the sequence and groups grids be sized more uniformly, i.e.
> to
> > resemble a grid.  ?
>
> I am not sure about the final design, but the current situation is not
> sufficient. Also the other tabs do not expose elegancy. I am also no GTK
> expert and more used to Qt, but there should be some set of classes
> handling a proper window/dialog layout (as in Qt). I only can start
> reading here too:
>
>  http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/
>
> > I can take a stab at improving the Keyboard tab if
> > you can tell me specifically what you'd like.  Keeping in mind my GTK
> > experience is all google searches, and looking at other examples in
> > seq24...  (i have win32, mfc, winforms experience so it's all familier
> > however).  :-)
>
> You will have some time now, give it a go ;-). I guess there are some
> users on the list, which will test it and give response.
>
> BTW: Do you use "-Wall" as a compiler option? At least you should and
> have a look at the upcomming warnings. A whole bunch of new ones came
> in with the last patch (I already fixed some of them).
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKIDLOk6cKJms5yBsRAvg8AJ0XXYhWdwD8y7i9VCoxnblzKDSAjgCfWWRT
> OEm143wqvBGTZDsbKXOYufg=
> =SxC9
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] mute groups feature - first impressions... AND code patch for --show_keys to work....

[Guido S. <gui...@ba...>]

Am Fri, 29. May 2009 um 08:44:24 -0500 schrieb Kevin Meinert:

Hi Kevin,

> For #3, I don't know what "layout management" is, was just following the
> examples in the other tabs (manual placement)...   Are you saying that you'd
> rather that the sequence and groups grids be sized more uniformly, i.e. to
> resemble a grid.  ?

I am not sure about the final design, but the current situation is not
sufficient. Also the other tabs do not expose elegancy. I am also no GTK
expert and more used to Qt, but there should be some set of classes
handling a proper window/dialog layout (as in Qt). I only can start
reading here too:

  http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/

> I can take a stab at improving the Keyboard tab if
> you can tell me specifically what you'd like.  Keeping in mind my GTK
> experience is all google searches, and looking at other examples in
> seq24...  (i have win32, mfc, winforms experience so it's all familier
> however).  :-)

You will have some time now, give it a go ;-). I guess there are some
users on the list, which will test it and give response.

BTW: Do you use "-Wall" as a compiler option? At least you should and
have a look at the upcomming warnings. A whole bunch of new ones came
in with the last patch (I already fixed some of them).

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [seq24-users] mute groups feature - first impressions... AND code patch for --show_keys to work....

[Kevin M. <ke...@su...>]

I have a fix for 1 and 2, will try to get a patch together this weekend.

For #3, I don't know what "layout management" is, was just following the
examples in the other tabs (manual placement)...   Are you saying that you'd
rather that the sequence and groups grids be sized more uniformly, i.e. to
resemble a grid.  ?     I can take a stab at improving the Keyboard tab if
you can tell me specifically what you'd like.  Keeping in mind my GTK
experience is all google searches, and looking at other examples in
seq24...  (i have win32, mfc, winforms experience so it's all familier
however).  :-)



---
kevin meinert | http://www.subatomicglue.com


On Thu, May 28, 2009 at 4:44 PM, Guido Scholz <gui...@ba...>wrote:

> Am Fri, 24. Apr 2009 um 11:06:54 -0500 schrieb Kevin Meinert:
>
> Hi kevin,
>
> [Mute group feature]
>
> > anyway, on the train this morning, I added in code to let the user know
> that
> > their mapping attempt failed because the key is already bound to a
> > [keyboard-sequencer] item...     it makes a lot more sense now,
> UI-wise...
> > rather than the "learn" action failing silently.
> >
> > I'll try to polish it up a bit and will send the code this weekend.
> > I may try some things with doing a learn mode for the sequencer keys
> also...
> > maybe a "learn" button on the main UI too...  i don't know how far i'll
> > get...
>
> this patch is also applied now, but there are some issues to be solved;
> so it has some kind of preliminary state. Sorry I have no time to care
> for it my self, just preparing for a holiday journey.
>
> 1) perform.cpp: Magic numbers for keys used in set_key_group() must be
>   replaced by names like defined in
>
>   /usr/include/gtk-2.0/gdk/gdkkeysyms.h
>
>
> 2) seq24.cpp: The key2text() function most probably can/should be replaced
>   by a more generic approach "gdk_keyval_name()", see
>
>  http://library.gnome.org/devel/gdk/stable/gdk-Keyboard-Handling.html
>
>  This may also have advantages for key name backward translation.
>
>
> 3) The design of the "keyboard" tab in the options dialog is kind of
>   crude and should be redesigned at least using layout management
>   (and some more user friendly optimizations).
>
> Not to forget: Great work Kevin and N.N., thanks a lot.
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKHwXJk6cKJms5yBsRAgDlAJ9NbPAI/FJInjd9y11xAyw7nxOy2wCfa+Uv
> bbwL4GcXZixS0Zg6HOjyPN0=
> =FsZQ
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] New Mouse Interaction patch (similar to fruityloops pianoroll) (patch against: rev48 source code from bazaar + my win32 patch)

[Guido S. <gui...@ba...>]

Am Thu, 28. May 2009 um 16:33:56 -0500 schrieb Kevin Meinert:

Hi Kevin,

> yeah, i'm using a pretty old GTK,  2.8 or something.

it is not really GTK, but libsigc++, have a look here 

  http://libsigc.sourceforge.net/libsigc2/docs/index.html

Good night.
Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [seq24-users] mute groups feature - first impressions... AND code patch for --show_keys to work....

[Guido S. <gui...@ba...>]

Am Fri, 24. Apr 2009 um 11:06:54 -0500 schrieb Kevin Meinert:

Hi kevin,

[Mute group feature]

> anyway, on the train this morning, I added in code to let the user know that
> their mapping attempt failed because the key is already bound to a
> [keyboard-sequencer] item...     it makes a lot more sense now, UI-wise...
> rather than the "learn" action failing silently.
> 
> I'll try to polish it up a bit and will send the code this weekend.
> I may try some things with doing a learn mode for the sequencer keys also...
> maybe a "learn" button on the main UI too...  i don't know how far i'll
> get...

this patch is also applied now, but there are some issues to be solved;
so it has some kind of preliminary state. Sorry I have no time to care
for it my self, just preparing for a holiday journey.

1) perform.cpp: Magic numbers for keys used in set_key_group() must be
   replaced by names like defined in

   /usr/include/gtk-2.0/gdk/gdkkeysyms.h


2) seq24.cpp: The key2text() function most probably can/should be replaced
   by a more generic approach "gdk_keyval_name()", see

  http://library.gnome.org/devel/gdk/stable/gdk-Keyboard-Handling.html

  This may also have advantages for key name backward translation.


3) The design of the "keyboard" tab in the options dialog is kind of
   crude and should be redesigned at least using layout management
   (and some more user friendly optimizations).

Not to forget: Great work Kevin and N.N., thanks a lot.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/