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

Re: [seq24-users] Is the project still going?

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

Hi Loz,

I recently made (a false) bug report on the Launchpad site, and people 
where reactive, I also give a feature request, but nobody gives a 
comment, try here and perhaps seeing peoples wanted improvment would 
give motivation to the staff

here is my feature request : 
https://answers.launchpad.net/seq24/+question/105177

does your improvment concern this ?

Best

Philippe


Loz a écrit , Le 31.03.2010 11:46:
> Hi,
>
> I was just wondering if this project was still being developed? I
> really like Seq24, but there are a few things which I think could be
> done to improve it.
>
> It would be a shame if Seq24 died off.
>
> Loz
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>   

[seq24-users] Is the project still going?

[Loz <mis...@gm...>]

Hi,

I was just wondering if this project was still being developed? I
really like Seq24, but there are a few things which I think could be
done to improve it.

It would be a shame if Seq24 died off.

Loz

Re: [seq24-users] seq24-users Digest, Vol 26, Issue 1

[Gommaar D. <del...@gm...>]

Thank you, Kevin.

Is the older pthreadGC2.dll suitable for this release too? (As it is not
included)


Date: Thu, 14 Jan 2010 15:21:54 -0600
> From: Kevin Meinert <ke...@su...>
> Subject: Re: [seq24-users] win32 beta builds?
> To: Gommaar Delneste <del...@gm...>
> Cc: seq...@li...
> Message-ID:
>        <f97...@ma...
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> you can download a win32 build here:
>  http://www.subatomicglue.com/seq24/
>
> I would use my self-named
> beta4<
> http://www.subatomicglue.com/seq24/seq24-0.9.0-win32-beta-4-subatomic-src+bin.tgz
> >version...
>
> this "beta4" was checked into the main bazaar source repos at one time,
> though the midi clock sync has had work done since then (last i saw it was
> checked in broken, but maybe it's been fixed since then, I haven't been
> staying informed lately...).
>
> so... not sure what the current state in the bazaar source code is...
> but the link above works well for me.
>
> http://www.codinghorror.com/blog/images/works-on-my-machine-starburst.png
>
> :-)
>
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Thu, Jan 14, 2010 at 3:00 PM, Gommaar Delneste <del...@gm...
> >wrote:
>
> > Hi, are there any win32 (exe) releases of the latest (4) beta
> > announcements?
> >
> > Thanks in advance,
> > G
>

Re: [seq24-users] win32 beta builds?

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

get
*seq24-0.8.7-win32-beta-1-subatomic-src+toolchain+binary.rar*<http://www.subatomicglue.com/seq24/seq24-0.8.7-win32-beta-1-subatomic-src+toolchain+binary.rar>(everything
to build/run)

then overwrite the src with this to update it to the latest.
*seq24-0.9.0-win32-beta-4-subatomic-src+bin.tgz*<http://www.subatomicglue.com/seq24/seq24-0.9.0-win32-beta-4-subatomic-src+bin.tgz>(seq24.exe
- adds keybinding GUI patch)


the DevCpp compiler and all the libraries are included in the 1st link.
click the openproject.bat file to open it.
feel free to ask me questions.

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


On Thu, Jan 14, 2010 at 6:11 PM, Garett Michael Shulman <
shu...@co...> wrote:

> Thanks, Kevin!  I have been looking for win32 builds of recent seq24 also.
>  Do you know if there is documentation anywhere detailing the win32 build
> process?  I wouldn't mind hacking on the source a bit and then compiling
> myself.  Thanks! -Garett
>
> Kevin Meinert wrote:
>
>>
>> you can download a win32 build here:
>>  http://www.subatomicglue.com/seq24/
>>
>> I would use my self-named beta4 <
>> http://www.subatomicglue.com/seq24/seq24-0.9.0-win32-beta-4-subatomic-src+bin.tgz>
>> version...
>>
>>
>> this "beta4" was checked into the main bazaar source repos at one time,
>> though the midi clock sync has had work done since then (last i saw it was
>> checked in broken, but maybe it's been fixed since then, I haven't been
>> staying informed lately...).
>>
>> so... not sure what the current state in the bazaar source code is...
>> but the link above works well for me.
>>
>> http://www.codinghorror.com/blog/images/works-on-my-machine-starburst.png
>>
>> :-)
>>
>> ---
>> kevin meinert | http://www.subatomicglue.com
>>
>>
>> On Thu, Jan 14, 2010 at 3:00 PM, Gommaar Delneste <del...@gm...<mailto:
>> del...@gm...>> wrote:
>>
>>    Hi, are there any win32 (exe) releases of the latest (4) beta
>>    announcements?
>>
>>    Thanks in advance,
>>    G
>>
>>
>>  ------------------------------------------------------------------------------
>>    Throughout its 18-year history, RSA Conference consistently
>>    attracts the
>>    world's best and brightest in the field, creating opportunities
>>    for Conference
>>    attendees to learn about information security's most important
>>    issues through
>>    interactions with peers, luminaries and emerging and established
>>    companies.
>>    http://p.sf.net/sfu/rsaconf-dev2dev
>>    _______________________________________________
>>    seq24-users mailing list
>>    seq...@li...
>>    <mailto:seq...@li...>
>>
>>    https://lists.sourceforge.net/lists/listinfo/seq24-users
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
>> Conference
>> attendees to learn about information security's most important issues
>> through
>> interactions with peers, luminaries and emerging and established
>> companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> seq24-users mailing list
>> seq...@li...
>> https://lists.sourceforge.net/lists/listinfo/seq24-users
>>
>>
>
>

Re: [seq24-users] win32 beta builds?

[Garett M. S. <shu...@Co...>]

Thanks, Kevin!  I have been looking for win32 builds of recent seq24 
also.  Do you know if there is documentation anywhere detailing the 
win32 build process?  I wouldn't mind hacking on the source a bit and 
then compiling myself.  Thanks! -Garett

Kevin Meinert wrote:
>
> you can download a win32 build here:
>   http://www.subatomicglue.com/seq24/
>
> I would use my self-named beta4 
> <http://www.subatomicglue.com/seq24/seq24-0.9.0-win32-beta-4-subatomic-src+bin.tgz> 
> version...
>
> this "beta4" was checked into the main bazaar source repos at one 
> time, though the midi clock sync has had work done since then (last i 
> saw it was checked in broken, but maybe it's been fixed since then, I 
> haven't been staying informed lately...).
>
> so... not sure what the current state in the bazaar source code is...
> but the link above works well for me.
>       
> http://www.codinghorror.com/blog/images/works-on-my-machine-starburst.png
>
> :-)
>
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Thu, Jan 14, 2010 at 3:00 PM, Gommaar Delneste <del...@gm... 
> <mailto:del...@gm...>> wrote:
>
>     Hi, are there any win32 (exe) releases of the latest (4) beta
>     announcements?
>
>     Thanks in advance,
>     G
>
>     ------------------------------------------------------------------------------
>     Throughout its 18-year history, RSA Conference consistently
>     attracts the
>     world's best and brightest in the field, creating opportunities
>     for Conference
>     attendees to learn about information security's most important
>     issues through
>     interactions with peers, luminaries and emerging and established
>     companies.
>     http://p.sf.net/sfu/rsaconf-dev2dev
>     _______________________________________________
>     seq24-users mailing list
>     seq...@li...
>     <mailto:seq...@li...>
>     https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>   

Re: [seq24-users] win32 beta builds?

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

you can download a win32 build here:
  http://www.subatomicglue.com/seq24/

I would use my self-named
beta4<http://www.subatomicglue.com/seq24/seq24-0.9.0-win32-beta-4-subatomic-src+bin.tgz>version...

this "beta4" was checked into the main bazaar source repos at one time,
though the midi clock sync has had work done since then (last i saw it was
checked in broken, but maybe it's been fixed since then, I haven't been
staying informed lately...).

so... not sure what the current state in the bazaar source code is...
but the link above works well for me.

http://www.codinghorror.com/blog/images/works-on-my-machine-starburst.png

:-)

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


On Thu, Jan 14, 2010 at 3:00 PM, Gommaar Delneste <del...@gm...>wrote:

> Hi, are there any win32 (exe) releases of the latest (4) beta
> announcements?
>
> Thanks in advance,
> G
>
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

[seq24-users] win32 beta builds?

[Gommaar D. <del...@gm...>]

Hi, are there any win32 (exe) releases of the latest (4) beta announcements?

Thanks in advance,
G

Re: [seq24-users] Quantize the activation of patterns

[Esben S. <b0...@es...>]

Kjo Hansi Glaz <kj...@a4...> writes:

> I'm trying to find a good software sequencer to act as theses boxes
> called "groovebox". I want to be able to trigger sequences live.

As nothing seems to happen here, I'd like to point you to supercollider
for this kind of stuff.

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

[seq24-users] Quantize the activation of patterns

[Kjo H. G. <kj...@a4...>]

Hi !

I'm trying to find a good software sequencer to act as theses boxes
called "groovebox". I want to be able to trigger sequences live. So I
found seq24 a while ago, which seems me great, but I can't find a key
function : I'd like the activation of the loops to be quantized to
either the next bad (as on many hardware drum machines) ou to a division
of a bar (1/4, 1/16, ...). Is that possible with seq24 ? And if it is
not, would it be difficult to implement ?

Thanks by advance,

Kjö

Re: [seq24-users] buffer overflows

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

I didnt do any jack work in win32, so I'm pretty sure it's compiled out in
win32...
someone will need to reenable it, I believe.

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


On Fri, Aug 21, 2009 at 12:35 AM, Amir Hirsch <am...@ca...> wrote:

> the binary works. thank you for hosting the entire dev environment too.
> i'll try to get it to compile
>
> i'm having trouble getting seq24 to see JACK midi ports in win32 even
> though JACK 1.9.3 apparently uses winMME
>
>
> On Thu, Aug 20, 2009 at 9:42 AM, Kevin Meinert <ke...@su...>wrote:
>
>>
>> binary:
>>
>>    http://www.subatomicglue.com/seq24/
>>
>> i don't know if it was fixed or not, but midi clock sync (input to seq24
>> from external) was broken in bazaar last I looked (a few weeks ago)...
>> may have been fixed by now, but something to be aware of.
>> the win32 binary above has it from before it was broken...
>>
>>
>> ---
>> kevin meinert | http://www.subatomicglue.com
>>
>>
>> On Thu, Aug 20, 2009 at 1:36 AM, Amir Hirsch <am...@ca...> wrote:
>>
>>> Running on Ubuntu 9.04, 2.6.27-7
>>>
>>> seq24 0.8.7 was generating a "buffer overflow" error and crashing when
>>> attempting to add a new track.
>>>
>>> removed 0.8.7, installed 0.9.0 from source and now i get a "buffer
>>> overflow" when attempting to click on the "tools" icon in the sequence edit
>>> window.
>>>
>>> only version that works on my machine is 0.8.7 under windows xp. what
>>> happened to 0.9.0 compiling on win32 back in may?  is there a binary
>>> distribution or do i just need to suck it up and get all the dependencies to
>>> compile in windows?
>>>
>>> Amir
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>>> 30-Day
>>> trial. Simplify your report design, integration and deployment - and
>>> focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> _______________________________________________
>>> seq24-users mailing list
>>> seq...@li...
>>> https://lists.sourceforge.net/lists/listinfo/seq24-users
>>>
>>>
>>
>

Re: [seq24-users] buffer overflows

[Amir H. <am...@ca...>]

the binary works. thank you for hosting the entire dev environment too. i'll
try to get it to compile

i'm having trouble getting seq24 to see JACK midi ports in win32 even though
JACK 1.9.3 apparently uses winMME

On Thu, Aug 20, 2009 at 9:42 AM, Kevin Meinert <ke...@su...>wrote:

>
> binary:
>
>    http://www.subatomicglue.com/seq24/
>
> i don't know if it was fixed or not, but midi clock sync (input to seq24
> from external) was broken in bazaar last I looked (a few weeks ago)...
> may have been fixed by now, but something to be aware of.
> the win32 binary above has it from before it was broken...
>
>
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Thu, Aug 20, 2009 at 1:36 AM, Amir Hirsch <am...@ca...> wrote:
>
>> Running on Ubuntu 9.04, 2.6.27-7
>>
>> seq24 0.8.7 was generating a "buffer overflow" error and crashing when
>> attempting to add a new track.
>>
>> removed 0.8.7, installed 0.9.0 from source and now i get a "buffer
>> overflow" when attempting to click on the "tools" icon in the sequence edit
>> window.
>>
>> only version that works on my machine is 0.8.7 under windows xp. what
>> happened to 0.9.0 compiling on win32 back in may?  is there a binary
>> distribution or do i just need to suck it up and get all the dependencies to
>> compile in windows?
>>
>> Amir
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> seq24-users mailing list
>> seq...@li...
>> https://lists.sourceforge.net/lists/listinfo/seq24-users
>>
>>
>

Re: [seq24-users] buffer overflows

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

binary:

   http://www.subatomicglue.com/seq24/

i don't know if it was fixed or not, but midi clock sync (input to seq24
from external) was broken in bazaar last I looked (a few weeks ago)...
may have been fixed by now, but something to be aware of.
the win32 binary above has it from before it was broken...


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


On Thu, Aug 20, 2009 at 1:36 AM, Amir Hirsch <am...@ca...> wrote:

> Running on Ubuntu 9.04, 2.6.27-7
>
> seq24 0.8.7 was generating a "buffer overflow" error and crashing when
> attempting to add a new track.
>
> removed 0.8.7, installed 0.9.0 from source and now i get a "buffer
> overflow" when attempting to click on the "tools" icon in the sequence edit
> window.
>
> only version that works on my machine is 0.8.7 under windows xp. what
> happened to 0.9.0 compiling on win32 back in may?  is there a binary
> distribution or do i just need to suck it up and get all the dependencies to
> compile in windows?
>
> Amir
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

[seq24-users] buffer overflows

[Amir H. <am...@ca...>]

Running on Ubuntu 9.04, 2.6.27-7

seq24 0.8.7 was generating a "buffer overflow" error and crashing when
attempting to add a new track.

removed 0.8.7, installed 0.9.0 from source and now i get a "buffer overflow"
when attempting to click on the "tools" icon in the sequence edit window.

only version that works on my machine is 0.8.7 under windows xp. what
happened to 0.9.0 compiling on win32 back in may?  is there a binary
distribution or do i just need to suck it up and get all the dependencies to
compile in windows?

Amir

[seq24-users] Midi bindings for Queue can be enabled, but not disabled

[<tyr...@fr...>]

Hello,

I'm experiencing some problem with mode QUEUE and midi bindings. Actually, what
I want is to open the Mode Queue mode, then select my sequence/group of
sequences, then close the Queue Mode.
I'm using program changes to control it.
So I've tried different approaches :
1. toggle (the left brackets column of the .seq24rc file) : it simply doesn't
work at all. Nor the mode queue on neither the off
2. mode on + off (center and right brackets of the .seq24rc file) : I can enable
the mode queue, it works, but I cannot disable it with the off binding (as it's
program change, I cannot bind the same controller with different value, it has
to be two separate program changes). The only solution to get out of queue mode
is to press the Ctrl key one or two times, so that the key binding tell seq24
the queue is over.
Did someone experience the same problem? How can it be fixed?


Note: I've merked that using both control change + other midi controls (note on,
program changes) in seq24 works not very well. I've not had the time to go
further, but, basically, when pressing the control change button, the action to
which it is bind is done, and then you cannot do anything more with MIDI.

Thanks a lot.
Aurélien

Re: [seq24-users] WIN32 patch for seq24 (patch against the latest (rev 48) code from bazaar)

[Jonny S. <jst...@je...>]

On Tue, Jul 07, 2009 at 04:32:22PM -0700, Alex wrote:
> so has anyone tried seq24 on osx yet?
> I don't have an osx box but i have a few friends who would really love
> to use something like seq24, though they aren't developers..

I've had a go at compiling one of the recent versions on OSX but it
fails because of some non-POSIX code that's used to do high resolution
timing.  I haven't had time yet to work out a suitable replacement yet.
If anyone working on Seq24 on Linux knows of a POSIX approved way of
doing high resolution timers so that the amount of platform specific
code can be minimised then that'd be a great help.

Cheers,
Jonny

Re: [seq24-users] WIN32 patch for seq24 (patch against the latest (rev 48) code from bazaar)

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

so has anyone tried seq24 on osx yet?
I don't have an osx box but i have a few friends who would really love
to use something like seq24, though they aren't developers..

-Alex

On Mon, May 25, 2009 at 8:21 PM, Kevin Meinert<ke...@su...> wrote:
>
> verified... seq24 latest from bazaar works on WIN32!!!
>
> congrats, seq24 is on a new platform (or you're back on it?  whatever...)
> :-)
>
>
> cool.
>
> Guido, want to check out the other patches next?   I noticed you cleaned up
> some stuff in seqroll, with the mouse interaction patch of mine, we may get
> a few conflicts, not sure...
>
> also notice you ifdef WIN32'd the whole midibus_portmidi...   as I
> understand portmidi is on multiple platforms other than WIN32...  though it
> may be good with WIN32 until it's actually tested...   for example, you may
> be able to be on OSX now with portmidi...  just need someone to try it
> there...
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Fri, May 22, 2009 at 2:24 PM, Guido Scholz <gui...@ba...>
> wrote:
>>
>> Am Fri, 22. May 2009 um 18:29:22 +0200 schrieb Guido Scholz:
>>
>> Hi all,
>>
>> > 3) The background repainting (optimization) is still not in. This should
>> > be the next feature to work on.
>>
>> this is also applied now. I do not see a huge difference, but anyway...
>>
>> Guido
>>
>>
>> --
>> http://www.bayernline.de/~gscholz/
>> http://www.lug-burghausen.org/
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFKFvv2k6cKJms5yBsRArq2AJ9doWMUg2GtN8nXklm5gQ2/jQyDdgCcDKQR
>> fuCuD0+KCz9NPIDYCgIWZkU=
>> =KdaK
>> -----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 asthey present alongside digital heavyweights like Barbarian
>> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
>> _______________________________________________
>> seq24-users mailing list
>> seq...@li...
>> https://lists.sourceforge.net/lists/listinfo/seq24-users
>>
>
>
> ------------------------------------------------------------------------------
> 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 asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>

Re: [seq24-users] Sync Problem using Sooperlooper as jack master and seq24 as slave

[Aurelien <tyr...@fr...>]

Hello again,

I've found today the reason of all this these troubles. It was pure
"hasard". I'm using netjack with this machine. The fact is that the
script runs jack_netsource on the master machine even if the slave
machine is not there. If the slave machine is not connected, I get this
weird latency, when it's connected, everything turns back well.
Couldn't say why, but if someone has the same problem, here is a way to
explain it.

On Thu, Jul 02, 2009 at 10:12:29AM +0200, Aurelien wrote :
> Hello
> (First of all, sorry, I didn't find the time to write my patch files and
> send them here)
> 
> I'm exepriencing some troubles, quite weird and not so reproductible,
> with MIDI synchronization between seq24 and other stuffs.
> 
> I've got to describe a bit my setup to make this mail understandable.
> 
> So, I use Sooperlooper as Jack Timebase Master, and as a live-looper, of
> course.
> I then use seq24 as a a sequencer controlling several instances of
> AlsaModularSynth, and one of Tapeutape (a sampler), and also Q Light
> Controller (a light controller package).
> 
> I've made some patches in seq24 so that I can bind a MIDI control to
> start and stop playback.
> 
> Now, here is the problem:
> Sometimes, all work fine, when I hit the playback MIDI binding or the
> space key, sequences begin to play with tempo given by SooperLooper. I
> can change SooperLooper tempo, it works really fine.
> I mean, starting playback is "instantaneous" (as much as possible) with
> the MIDI Signal.
> 
> Some other times, it's not the same. When I hit the playback MIDI
> binding, there is a really big delay (like 5-10s) before it begins to
> start playback.
> 
> One important thing is that everything is launched using a bash script,
> so that the init sequence is the very same each time I power up the
> computer. The only thing changing from one session to another is the
> time when I've to unplug/plug my MIDISPORT interface as it's not
> detected by udev when plugged at boot.
> Another important thing is that when it doesn't work, it doesn't work
> until I powercycle the COMPUTER!!!
> 
> I know you probably cannot give me a solution or answer with so
> "etheral" informations, but I first would like to know in which
> direction I should look. I'm not very used with MIDI synchro, and
> perhaps it's a really basic error, but I cannot figure out what it deals
> with.
> 
> Thanks a lot.
> Aurélien
> 
> -- 
> Aurélien
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
> 

-- 
Aurélien

[seq24-users] Sync Problem using Sooperlooper as jack master and seq24 as slave

[Aurelien <tyr...@fr...>]

Hello
(First of all, sorry, I didn't find the time to write my patch files and
send them here)

I'm exepriencing some troubles, quite weird and not so reproductible,
with MIDI synchronization between seq24 and other stuffs.

I've got to describe a bit my setup to make this mail understandable.

So, I use Sooperlooper as Jack Timebase Master, and as a live-looper, of
course.
I then use seq24 as a a sequencer controlling several instances of
AlsaModularSynth, and one of Tapeutape (a sampler), and also Q Light
Controller (a light controller package).

I've made some patches in seq24 so that I can bind a MIDI control to
start and stop playback.

Now, here is the problem:
Sometimes, all work fine, when I hit the playback MIDI binding or the
space key, sequences begin to play with tempo given by SooperLooper. I
can change SooperLooper tempo, it works really fine.
I mean, starting playback is "instantaneous" (as much as possible) with
the MIDI Signal.

Some other times, it's not the same. When I hit the playback MIDI
binding, there is a really big delay (like 5-10s) before it begins to
start playback.

One important thing is that everything is launched using a bash script,
so that the init sequence is the very same each time I power up the
computer. The only thing changing from one session to another is the
time when I've to unplug/plug my MIDISPORT interface as it's not
detected by udev when plugged at boot.
Another important thing is that when it doesn't work, it doesn't work
until I powercycle the COMPUTER!!!

I know you probably cannot give me a solution or answer with so
"etheral" informations, but I first would like to know in which
direction I should look. I'm not very used with MIDI synchro, and
perhaps it's a really basic error, but I cannot figure out what it deals
with.

Thanks a lot.
Aurélien

-- 
Aurélien

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

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

I started looking at the code to see why it keeps running, even after
recv'ing a stop message from the rm1x.
2 things:

1.)
I think the bug is with this code in the "STOP" conditional:
    m_usemidiclock = false;

this disables MIDI control.   which we don't want.   seq24's running loop
still runs while stopped.  but it relys on the fact that there's 0 song
position increments....
commenting it out isn't enough to fix it however... I'm still tracking that
down.
But the code here is certainly not going to work, as it allows the
non-midi-controlled seq24 to run willy nilly. :-)

2.)
I don't think we should "start" the sequencer on a CLOCK tick...     there's
time delay in that method.
I think that sets seq24 maybe 2 ticks behind... (there's a delay until the
seq24 actually starts incrementing the song ptr after looping around a
couple times - then actually starting....)


Also,  I'm not sure why the CLOCK need to be changed to start().
was there a reason for this?   or did it just seem cleaner?








here's some debugging using printf and your code:

I get a constant stream of  1's (yamaha rm1x must be spamming CLOCK even
when stopped)...

upon startup of seq24, and the rm1x.   I see 1 1 1 1 1 1 1 1 1
when press start on rm1x, I get 5 6 1 3  then   1 2 1 2 1 2 ....
when I hit stop on rm1x,  I get 7 8 then 1 1 1 1 1 1 1


looks like maybe we miss a tick or two here, since CLOCK calls start(false)
on the 2nd time around, after getting the start msg, and then on the 3rd
time around we actually increment the song pointer...   so, does that mean
we're running 2 ticks behind?

stopped...   spamming clocks  1 1 1 1 1 1
start 5 6
running 1 3 1 2 1 2 1 2 1 2 1 2 1 2 1 2
stop 7 8
stopped... spamming again... 1 1 1 1 1 1


                    /* start propagation if not already running*/
                    if (ev.get_status() == EVENT_MIDI_CLOCK)
                    {
                         printf( "1\n" );
                         if (m_midiclockrunning)
                        {
                             printf( "2\n" );
                            m_midiclocktick += 8;
                        }
                        else if (m_usemidiclock)
                        {
                             printf( "3\n" );
                            start(false);
                            m_midiclockrunning = true;
                        }
                    }

                    /*prapare for MIDI clock usage at song position 0*/
                    else if (ev.get_status() == EVENT_MIDI_START)
                    {
                         printf( "4\n" );
                         if (!m_midiclockrunning) {
                            m_usemidiclock = true;
                            m_midiclocktick = 0;
                            m_midiclockpos = 0;
                        }
                    }

                    /*prapare for MIDI clock usage at current song
position*/
                    else if (ev.get_status() == EVENT_MIDI_CONTINUE)
                    {
                         printf( "5\n" );
                            if (!m_midiclockrunning) {
                         printf( "6\n" );
                                m_usemidiclock = true;
                        }
                    }

                    /*stop MIDI clock usage*/
                    else if (ev.get_status() == EVENT_MIDI_STOP)
                    {
                         printf( "7\n" );
                         if (m_midiclockrunning)
                        {
                            printf( "8\n" );
                            m_midiclockrunning = false;
                            m_usemidiclock = false;
                            all_notes_off();
                        }
                    }

                    /*adjust position if not in MIDI clock run mode*/
                    else if (ev.get_status() == EVENT_MIDI_SONG_POS)
                    {
                         printf( "9\n" );
                         if (!m_midiclockrunning) {
                          printf( "10\n" );
                               unsigned char a, b;
                            ev.get_data(&a, &b);
                            m_midiclockpos = ((unsigned int)a << 7) | b;
                        }
                    }

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


On Tue, Jun 30, 2009 at 7:17 PM, Kevin Meinert <ke...@su...>wrote:

>
> With the latest bazaar revision...
> Stop on my yamaha rm1x no longer causes seq24 to stop...   (I can't get
> seq24 to stop using the rm1x now).
>
> the back button on the rm1x rests the song pointer to the beginning (while
> sitll running)
> the play button on the rm1x does start the sequence in seq24
>
> (Same with x0xb0x.   Start on x0xb0x, starts the seq24.   Stop does
> nothing...  Start again on x0xb0x, and the sequence resets on seq24 (but
> continues to run.
> I cannot stop seq24...)
>
>
> is there something wrong with using this code?   It's updated to the newer
> ideas you've put on the list...   let me know if I've missed one.
>
>
>                     // 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 Fri, Jun 26, 2009 at 4:09 PM, Alex <x37...@gm...> wrote:
>
>> 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.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
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> 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...>]

yes, the rm1x sends continue, always...   if stopped, continue just
starts...

you hit the <| back button to reset the position....


Alex, what you say sounds interesting, and sounds like the way it is perhaps
intended to be coded in the latest revision, but I think that to get any
notes to process, you have to tick by one.   i.e. if you just "start"
without advancing the position you wouldn't get a tick...    that's
essentially "stop" mode in my old revision of the code.   when you hit stop,
the main loop just spins at position 0 without any notes being hit.
I could be wrong though.    the code's complex.

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


On Tue, Jun 30, 2009 at 9:13 PM, Alex <x37...@gm...> wrote:

> I'm not an expert on the seq24 source code.. though i did hack on it a
> little a while ago.
>
> I know MIDI pretty well though... on the first clock tick _after_
> start you want to start your sequence.. which i assume means you
> wouldn't increment your song position because you're already at the
> start.  on the next tick you'd increment the song position.
>
> It looks to me like the output you've been printing indicates that
> you're using 'continue' and not 'start' as when you say 'start' you
> see a 5, 6, which is in your continue handler.
>
> On Tue, Jun 30, 2009 at 6:59 PM, Kevin Meinert<ke...@su...>
> wrote:
> >
> > I started looking at the code to see why it keeps running, even after
> > recv'ing a stop message from the rm1x.
> > 2 things:
> >
> > 1.)
> > I think the bug is with this code in the "STOP" conditional:
> >     m_usemidiclock = false;
> >
> > this disables MIDI control.   which we don't want.   seq24's running loop
> > still runs while stopped.  but it relys on the fact that there's 0 song
> > position increments....
> > commenting it out isn't enough to fix it however... I'm still tracking
> that
> > down.
> > But the code here is certainly not going to work, as it allows the
> > non-midi-controlled seq24 to run willy nilly. :-)
> >
> > 2.)
> > I don't think we should "start" the sequencer on a CLOCK tick...
> there's
> > time delay in that method.
> > I think that sets seq24 maybe 2 ticks behind... (there's a delay until
> the
> > seq24 actually starts incrementing the song ptr after looping around a
> > couple times - then actually starting....)
> >
> >
> > Also,  I'm not sure why the CLOCK need to be changed to start().
> > was there a reason for this?   or did it just seem cleaner?
> >
> >
> >
> >
> >
> >
> >
> >
> > here's some debugging using printf and your code:
> >
> > I get a constant stream of  1's (yamaha rm1x must be spamming CLOCK even
> > when stopped)...
> >
> > upon startup of seq24, and the rm1x.   I see 1 1 1 1 1 1 1 1 1
> > when press start on rm1x, I get 5 6 1 3  then   1 2 1 2 1 2 ....
> > when I hit stop on rm1x,  I get 7 8 then 1 1 1 1 1 1 1
> >
> >
> > looks like maybe we miss a tick or two here, since CLOCK calls
> start(false)
> > on the 2nd time around, after getting the start msg, and then on the 3rd
> > time around we actually increment the song pointer...   so, does that
> mean
> > we're running 2 ticks behind?
> >
> > stopped...   spamming clocks  1 1 1 1 1 1
> > start 5 6
> > running 1 3 1 2 1 2 1 2 1 2 1 2 1 2 1 2
> > stop 7 8
> > stopped... spamming again... 1 1 1 1 1 1
> >
> >
> >                     /* start propagation if not already running*/
> >                     if (ev.get_status() == EVENT_MIDI_CLOCK)
> >                     {
> >                          printf( "1\n" );
> >                          if (m_midiclockrunning)
> >                         {
> >                              printf( "2\n" );
> >                             m_midiclocktick += 8;
> >                         }
> >                         else if (m_usemidiclock)
> >                         {
> >                              printf( "3\n" );
> >                             start(false);
> >                             m_midiclockrunning = true;
> >                         }
> >                     }
> >
> >                     /*prapare for MIDI clock usage at song position 0*/
> >                     else if (ev.get_status() == EVENT_MIDI_START)
> >                     {
> >                          printf( "4\n" );
> >                          if (!m_midiclockrunning) {
> >                             m_usemidiclock = true;
> >                             m_midiclocktick = 0;
> >                             m_midiclockpos = 0;
> >                         }
> >                     }
> >
> >                     /*prapare for MIDI clock usage at current song
> > position*/
> >                     else if (ev.get_status() == EVENT_MIDI_CONTINUE)
> >                     {
> >                          printf( "5\n" );
> >                             if (!m_midiclockrunning) {
> >                          printf( "6\n" );
> >                                 m_usemidiclock = true;
> >                         }
> >                     }
> >
> >                     /*stop MIDI clock usage*/
> >                     else if (ev.get_status() == EVENT_MIDI_STOP)
> >                     {
> >                          printf( "7\n" );
> >                          if (m_midiclockrunning)
> >                         {
> >                             printf( "8\n" );
> >                             m_midiclockrunning = false;
> >                             m_usemidiclock = false;
> >                             all_notes_off();
> >                         }
> >                     }
> >
> >                     /*adjust position if not in MIDI clock run mode*/
> >                     else if (ev.get_status() == EVENT_MIDI_SONG_POS)
> >                     {
> >                          printf( "9\n" );
> >                          if (!m_midiclockrunning) {
> >                           printf( "10\n" );
> >                                unsigned char a, b;
> >                             ev.get_data(&a, &b);
> >                             m_midiclockpos = ((unsigned int)a << 7) | b;
> >                         }
> >                     }
> >
> > ---
> > kevin meinert | http://www.subatomicglue.com
> >
> >
> > On Tue, Jun 30, 2009 at 7:17 PM, Kevin Meinert <ke...@su...>
> > wrote:
> >>
> >> With the latest bazaar revision...
> >> Stop on my yamaha rm1x no longer causes seq24 to stop...   (I can't get
> >> seq24 to stop using the rm1x now).
> >>
> >> the back button on the rm1x rests the song pointer to the beginning
> (while
> >> sitll running)
> >> the play button on the rm1x does start the sequence in seq24
> >>
> >> (Same with x0xb0x.   Start on x0xb0x, starts the seq24.   Stop does
> >> nothing...  Start again on x0xb0x, and the sequence resets on seq24 (but
> >> continues to run.
> >> I cannot stop seq24...)
> >>
> >>
> >> is there something wrong with using this code?   It's updated to the
> newer
> >> ideas you've put on the list...   let me know if I've missed one.
> >>
> >>                     // 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 Fri, Jun 26, 2009 at 4:09 PM, Alex <x37...@gm...> wrote:
> >>>
> >>> 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.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
> >>> >
> >>> >
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> _______________________________________________
> >>> 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...>]

Yeah, the 707 sending a 'stop' message does not cause seq24 to stop as
it should.  start and continue work for me.. and if i press stop on
seq24 the sequence will stop..
this is my first test with the seq24 slave to midi clock syncing..

-Alex

On Tue, Jun 30, 2009 at 5:17 PM, Kevin Meinert<ke...@su...> wrote:
>
> With the latest bazaar revision...
> Stop on my yamaha rm1x no longer causes seq24 to stop...   (I can't get
> seq24 to stop using the rm1x now).
>
> the back button on the rm1x rests the song pointer to the beginning (while
> sitll running)
> the play button on the rm1x does start the sequence in seq24
>
> (Same with x0xb0x.   Start on x0xb0x, starts the seq24.   Stop does
> nothing...  Start again on x0xb0x, and the sequence resets on seq24 (but
> continues to run.
> I cannot stop seq24...)
>
>
> is there something wrong with using this code?   It's updated to the newer
> ideas you've put on the list...   let me know if I've missed one.
>
>                     // 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 Fri, Jun 26, 2009 at 4:09 PM, Alex <x37...@gm...> wrote:
>>
>> 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
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> 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...>]

Idea to fix the current code (while keeping the 2 tick delay)...
  add another boolean.   STOP would set it instead of setting m_usemidiclock
to false (because we need our code in the update loop to keep servicing the
song pointer.)
  the CLOCK conditional would check for the new boolean instead...
  START/CONTINUE would also use the new boolean...

Idea to fix the delay...   maybe reorder the conditionals...   however this
might have other side effects...


this is kinda of a can of worms,
and the original code (with the modifications below) was working,
let me know if that original code is missing a feature, and I will develop
it to where you need.    I'm interested in getting this fixed and done with.
:-)
I feel like the current solution is maybe going down a wrong path... or
something...   I'm not really sure what it's trying to do differently, other
than it being different.?   let me know... :)

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


On Tue, Jun 30, 2009 at 8:54 PM, Alex <x37...@gm...> wrote:

> Yeah, the 707 sending a 'stop' message does not cause seq24 to stop as
> it should.  start and continue work for me.. and if i press stop on
> seq24 the sequence will stop..
> this is my first test with the seq24 slave to midi clock syncing..
>
> -Alex
>
> On Tue, Jun 30, 2009 at 5:17 PM, Kevin Meinert<ke...@su...>
> wrote:
> >
> > With the latest bazaar revision...
> > Stop on my yamaha rm1x no longer causes seq24 to stop...   (I can't get
> > seq24 to stop using the rm1x now).
> >
> > the back button on the rm1x rests the song pointer to the beginning
> (while
> > sitll running)
> > the play button on the rm1x does start the sequence in seq24
> >
> > (Same with x0xb0x.   Start on x0xb0x, starts the seq24.   Stop does
> > nothing...  Start again on x0xb0x, and the sequence resets on seq24 (but
> > continues to run.
> > I cannot stop seq24...)
> >
> >
> > is there something wrong with using this code?   It's updated to the
> newer
> > ideas you've put on the list...   let me know if I've missed one.
> >
> >                     // 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 Fri, Jun 26, 2009 at 4:09 PM, Alex <x37...@gm...> wrote:
> >>
> >> 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.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
> >> >
> >> >
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> _______________________________________________
> >> 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...>]

I'm not an expert on the seq24 source code.. though i did hack on it a
little a while ago.

I know MIDI pretty well though... on the first clock tick _after_
start you want to start your sequence.. which i assume means you
wouldn't increment your song position because you're already at the
start.  on the next tick you'd increment the song position.

It looks to me like the output you've been printing indicates that
you're using 'continue' and not 'start' as when you say 'start' you
see a 5, 6, which is in your continue handler.

On Tue, Jun 30, 2009 at 6:59 PM, Kevin Meinert<ke...@su...> wrote:
>
> I started looking at the code to see why it keeps running, even after
> recv'ing a stop message from the rm1x.
> 2 things:
>
> 1.)
> I think the bug is with this code in the "STOP" conditional:
>     m_usemidiclock = false;
>
> this disables MIDI control.   which we don't want.   seq24's running loop
> still runs while stopped.  but it relys on the fact that there's 0 song
> position increments....
> commenting it out isn't enough to fix it however... I'm still tracking that
> down.
> But the code here is certainly not going to work, as it allows the
> non-midi-controlled seq24 to run willy nilly. :-)
>
> 2.)
> I don't think we should "start" the sequencer on a CLOCK tick...     there's
> time delay in that method.
> I think that sets seq24 maybe 2 ticks behind... (there's a delay until the
> seq24 actually starts incrementing the song ptr after looping around a
> couple times - then actually starting....)
>
>
> Also,  I'm not sure why the CLOCK need to be changed to start().
> was there a reason for this?   or did it just seem cleaner?
>
>
>
>
>
>
>
>
> here's some debugging using printf and your code:
>
> I get a constant stream of  1's (yamaha rm1x must be spamming CLOCK even
> when stopped)...
>
> upon startup of seq24, and the rm1x.   I see 1 1 1 1 1 1 1 1 1
> when press start on rm1x, I get 5 6 1 3  then   1 2 1 2 1 2 ....
> when I hit stop on rm1x,  I get 7 8 then 1 1 1 1 1 1 1
>
>
> looks like maybe we miss a tick or two here, since CLOCK calls start(false)
> on the 2nd time around, after getting the start msg, and then on the 3rd
> time around we actually increment the song pointer...   so, does that mean
> we're running 2 ticks behind?
>
> stopped...   spamming clocks  1 1 1 1 1 1
> start 5 6
> running 1 3 1 2 1 2 1 2 1 2 1 2 1 2 1 2
> stop 7 8
> stopped... spamming again... 1 1 1 1 1 1
>
>
>                     /* start propagation if not already running*/
>                     if (ev.get_status() == EVENT_MIDI_CLOCK)
>                     {
>                          printf( "1\n" );
>                          if (m_midiclockrunning)
>                         {
>                              printf( "2\n" );
>                             m_midiclocktick += 8;
>                         }
>                         else if (m_usemidiclock)
>                         {
>                              printf( "3\n" );
>                             start(false);
>                             m_midiclockrunning = true;
>                         }
>                     }
>
>                     /*prapare for MIDI clock usage at song position 0*/
>                     else if (ev.get_status() == EVENT_MIDI_START)
>                     {
>                          printf( "4\n" );
>                          if (!m_midiclockrunning) {
>                             m_usemidiclock = true;
>                             m_midiclocktick = 0;
>                             m_midiclockpos = 0;
>                         }
>                     }
>
>                     /*prapare for MIDI clock usage at current song
> position*/
>                     else if (ev.get_status() == EVENT_MIDI_CONTINUE)
>                     {
>                          printf( "5\n" );
>                             if (!m_midiclockrunning) {
>                          printf( "6\n" );
>                                 m_usemidiclock = true;
>                         }
>                     }
>
>                     /*stop MIDI clock usage*/
>                     else if (ev.get_status() == EVENT_MIDI_STOP)
>                     {
>                          printf( "7\n" );
>                          if (m_midiclockrunning)
>                         {
>                             printf( "8\n" );
>                             m_midiclockrunning = false;
>                             m_usemidiclock = false;
>                             all_notes_off();
>                         }
>                     }
>
>                     /*adjust position if not in MIDI clock run mode*/
>                     else if (ev.get_status() == EVENT_MIDI_SONG_POS)
>                     {
>                          printf( "9\n" );
>                          if (!m_midiclockrunning) {
>                           printf( "10\n" );
>                                unsigned char a, b;
>                             ev.get_data(&a, &b);
>                             m_midiclockpos = ((unsigned int)a << 7) | b;
>                         }
>                     }
>
> ---
> kevin meinert | http://www.subatomicglue.com
>
>
> On Tue, Jun 30, 2009 at 7:17 PM, Kevin Meinert <ke...@su...>
> wrote:
>>
>> With the latest bazaar revision...
>> Stop on my yamaha rm1x no longer causes seq24 to stop...   (I can't get
>> seq24 to stop using the rm1x now).
>>
>> the back button on the rm1x rests the song pointer to the beginning (while
>> sitll running)
>> the play button on the rm1x does start the sequence in seq24
>>
>> (Same with x0xb0x.   Start on x0xb0x, starts the seq24.   Stop does
>> nothing...  Start again on x0xb0x, and the sequence resets on seq24 (but
>> continues to run.
>> I cannot stop seq24...)
>>
>>
>> is there something wrong with using this code?   It's updated to the newer
>> ideas you've put on the list...   let me know if I've missed one.
>>
>>                     // 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 Fri, Jun 26, 2009 at 4:09 PM, Alex <x37...@gm...> wrote:
>>>
>>> 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
>>> >
>>> >
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> 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...>]

With the latest bazaar revision...
Stop on my yamaha rm1x no longer causes seq24 to stop...   (I can't get
seq24 to stop using the rm1x now).

the back button on the rm1x rests the song pointer to the beginning (while
sitll running)
the play button on the rm1x does start the sequence in seq24

(Same with x0xb0x.   Start on x0xb0x, starts the seq24.   Stop does
nothing...  Start again on x0xb0x, and the sequence resets on seq24 (but
continues to run.
I cannot stop seq24...)


is there something wrong with using this code?   It's updated to the newer
ideas you've put on the list...   let me know if I've missed one.

                    // 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 Fri, Jun 26, 2009 at 4:09 PM, Alex <x37...@gm...> wrote:

> 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.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
> >
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>

[seq24-users] seq24 compile error:

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

try adding a #include <sstream>  at the top of mainwnd.cpp


g++.exe -c seq24/src/mainwnd.cpp -o .objs/mainwnd.o
-I"lib/gcc/mingw32/3.4.2/include"  -I"include/c++/3.4.2/backward"
-I"include/c++/3.4.2/mingw32"  -I"include/c++/3.4.2"  -I"include"
-I"./PortMidi/pm_common"  -I"../seq24-3rdParty/include"
-I"../seq24-3rdParty/include/glib-2.0"
-I"../seq24-3rdParty/lib/glib-2.0/include"
-I"../seq24-3rdParty/include/cairo"
-I"../seq24-3rdParty/include/atkmm-1.6"
-I"../seq24-3rdParty/include/gdkmm-2.4"
-I"../seq24-3rdParty/include/gideon"
-I"../seq24-3rdParty/include/glib-2.0"
-I"../seq24-3rdParty/include/glibmm-2.4"
-I"../seq24-3rdParty/include/gtk-2.0"
-I"../seq24-3rdParty/include/gtkmm-2.4"
-I"../seq24-3rdParty/include/libglademm-2.4"
-I"../seq24-3rdParty/include/libxml++-2.6"
-I"../seq24-3rdParty/include/pangomm-1.4"
-I"../seq24-3rdParty/include/sigc++-2.0"
-I"../seq24-3rdParty/lib/gdkmm-2.4/include"
-I"../seq24-3rdParty/lib/glib-2.0/include"
-I"../seq24-3rdParty/lib/glibmm-2.4/include"
-I"../seq24-3rdParty/lib/gtk-2.0/include"
-I"../seq24-3rdParty/lib/gtkmm-2.4/include"
-I"../seq24-3rdParty/lib/libglademm-2.4/include"
-I"../seq24-3rdParty/lib/libxml++-2.6/include"
-I"../seq24-3rdParty/lib/sigc++-2.0/include"
-I"../seq24-3rdParty/include/pango-1.0"
-I"../seq24-3rdParty/include/atk-1.0"  -I"../seq24-3rdParty//include"
-I../seq24-3rdParty/include/gtkmm-2.4
-I../seq24-3rdParty/lib/gtkmm-2.4/include
-I../seq24-3rdParty/include/glibmm-2.4
-I../seq24-3rdParty/lib/glibmm-2.4/include
-I../seq24-3rdParty/include/gdkmm-2.4
-I../seq24-3rdParty/lib/gdkmm-2.4/include
-I../seq24-3rdParty/include/pangomm-1.4
-I../seq24-3rdParty/include/atkmm-1.6  -I../seq24-3rdParty/include/gtk-2.0
-I../seq24-3rdParty/include/sigc++-2.0
-I../seq24-3rdParty/lib/sigc++-2.0/include
-I../seq24-3rdParty/include/glib-2.0
-I../seq24-3rdParty/lib/glib-2.0/include
-I../seq24-3rdParty/lib/gtk-2.0/include
-I../seq24-3rdParty/include/pango-1.0  -I../seq24-3rdParty/include/atk-1.0
-ggdb -Wall   -fexpensive-optimizations -O3 -march=i686 -mmmx

seq24/src/mainwnd.cpp: In member function `virtual bool
mainwnd::on_key_press_event(GdkEventKey*)':
seq24/src/mainwnd.cpp:856: error: aggregate `std::ostringstream os' has
incomplete type and cannot be defined
seq24/src/mainwnd.cpp:874: error: aggregate `std::ostringstream os' has
incomplete type and cannot be defined

make.exe: *** [.objs/mainwnd.o] Error 1

Execution terminated