jorge.boos

I am searching for 'SeqPlayer' windows version 

of Eric Singer component, or other Max object 

that can do the same on windowsXP platform.

Can anyone please help me with some links?

I am searching for 'SeqPlayer' windows version 
of Eric Singer component, or other Max object 
that can do the same on windowsXP platform.
Can anyone please help me with some links?

seqplayer-on-windows-platform

I'm happy to open source the code and hand it off to someone to port 

to Windows. Email me offlist (and remove [maxmsp] from the subject so 

At 2:24 PM -0600 10/15/07, jorge.boos wrote:

>I am searching for 'SeqPlayer' windows version

>of Eric Singer component, or other Max object

>that can do the same on windowsXP platform.

>Can anyone please help me with some links?

I'm happy to open source the code and hand it off to someone to port 
to Windows. Email me offlist (and remove [maxmsp] from the subject so 
it goes to my main inbox).

At 2:24 PM -0600 10/15/07, jorge.boos wrote:
>Hi,
>
>I am searching for 'SeqPlayer' windows version
>of Eric Singer component, or other Max object
>that can do the same on windowsXP platform.
>Can anyone please help me with some links?
>
>Best regards,
>Jorge
>


I would just add that, having ported SeqPlayer for UB, on Intel you do have to watch out for byte-order gotchas.

I think I sent Eric my modifications, so if those are included in the upload the port to Windows should be pretty straight-forward.

Thanks to both, Eric and Peter, 
I will wait the link to download 
SeqPlayer for windows, if you are 
going to implement this version.

I've found 'midiparty' from Topher Lafata,

and I made this patcher to give it a try.

I've found 'midiparty' from Topher Lafata,
and I made this patcher to give it a try.
Are there other Max objects, externals, 
patches about midi, midifiles, looping?
While winXP 'seqplayer' is cooking,
please let me know about them...

In principle I would be happy to do the Windows port, but I don't see it realistically fitting into my schedule in the near future.

I just saw some mail from Eric in my inbox... we're moving towards a solution for you. Stay tuned.

In principle I would be happy to do the Windows port, but I don't see it realistically fitting into my schedule in the near future. 

> I just saw some mail from Eric in my inbox... we're moving 

> towards a solution for you. Stay tuned. Peter

Meanwhile, as a workaround solution, I wrote this patch to loop 

midifile bars; the only drawback is that it always start at 

bar=1, beat=1, tick=1, so you need to cut previously your

midifile so that it starts correctly. Now I'm working 

in a new patch that will correct this, I hope...

a realtime composition library by Karlheinz Essl.

Fileparser uses 'midiparty', from Topher Lafata.

> I just saw some mail from Eric in my inbox... we're moving 
> towards a solution for you. Stay tuned. Peter

Meanwhile, as a workaround solution, I wrote this patch to loop 
midifile bars; the only drawback is that it always start at 
bar=1, beat=1, tick=1, so you need to cut previously your
midifile so that it starts correctly. Now I'm working 
in a new patch that will correct this, I hope...

fileparser.pat
--------------
previously 
published

Midiclock uses 'count-bang' from RTC, 
a realtime composition library by Karlheinz Essl.
Fileparser uses 'midiparty', from Topher Lafata.

Many thanks to all.
Share knowledge.
Stay in peace.
Regards,

If you want loop-bang syncronized not to the last tick 

of the last bar to loop, but to the first tick of the 

next bar instead, then replace the patch 'midiclock' 

by 'midiclock1' in the patch 'looping.pat'.

It seems to be some limitations in tempo object.

BPM (beats per minute) and ticks per whole note,

or PQN (pulses per quarter note) are limited.

PQN limitation is more restrictive, since

If you want loop-bang syncronized not to the last tick 
of the last bar to loop, but to the first tick of the 
next bar instead, then replace the patch 'midiclock' 
by 'midiclock1' in the patch 'looping.pat'.

It seems to be some limitations in tempo object.
BPM (beats per minute) and ticks per whole note,
or PQN (pulses per quarter note) are limited.
PQN limitation is more restrictive, since
there are midifiles with resolutions of 
more than 240 pulses per quarter note.

To bypass the limitations of the tempo object as pointed out

previously, some modifications where made, resulting in a

better clock range and control, and higher PPQN also.

The patches and a test midifile are included.

To bypass the limitations of the tempo object as pointed out
previously, some modifications where made, resulting in a
better clock range and control, and higher PPQN also.
The patches and a test midifile are included.

i'm bumping this because i am desperatingly searching for an equivalent of the Seqplayer object for windows, and i can't find any solution .....

I need a midifile to be played following a (changing) bpm, but also triggered so that it jumps to the next beat when it gets a bang. So i can get a midifile played and stay synchro even with strange rythms / quantizations.

Seems that the Seqplayer wasn't ported on windows

Hello people,
i'm bumping this because i am desperatingly searching for an equivalent of the Seqplayer object for windows, and i can't find any solution .....

I need a midifile to be played following a (changing) bpm, but also triggered so that it jumps to the next beat when it gets a bang. So i can get a midifile played and stay synchro even with strange rythms / quantizations. 

Seems that the Seqplayer wasn't ported on windows 

SeqPlayer on windows platform