Forums > MaxMSP

seq object in -1 mode, tick timing issue


March 4, 2006 | 8:27 pm

I am working with 4 seq objects, trying to make them playback at their
proper tempos, with no luck.

I set them in "start -1" mode, and then send ticks driven by a MS clock.

The midi files were originally at 103 bpm. They are playing back all
funky at some arbitrary tempo.

I know the reference manual says 48 ticks/second, for proper playback,
but I am NOT getting that.

Does anyone have some suggestions?

I am totally perplexed.

Thanks,
Computo


MDV
March 4, 2006 | 9:07 pm

What happens when you simply send the seqs a standard "start 1024" message?

March 4, 2006 | 9:55 pm

I dont know, but I dont want them to playback from start to finish.

I need them to run in "start -1" mode, which should advance the files
1/48 of a beat per tick.

I’ll try it anyways when I get home.

Computo

March 5, 2006 | 12:10 am

I can’t really help but I can confirm the seq problems on windows. A while
back I was syncing seq with a host running at 115bpm. After lots of tweaking
around it turned out that I had to set seq at about 113 to get it sync. This
was for short midifiles though. I also remember trying to sync it using
midiclock, but that didn’t work out. Can’t remember why.

If tight timing is important, I think seq~ might be the only solution. You
can record your midifiles into seq~ from cubase or something, and save em as
text for later seq~ recall. You could even write a simple pluggo that
records tracks to seq~.

good luck, Thijs

March 5, 2006 | 8:00 am

Well Im on a mac, and the seq object DEFINETLY isnt acting properly. It is
the ONLY weak link in my patch, and Im not sure how else to do this. I cant
go about recording 4 6 minute long midi tracks, every time I open the
patch.

Any otehr ideas? I’ll do the seq~ if I have to, but Im not gonna like it…

Joe


MDV
March 5, 2006 | 1:06 pm

Are you using a metro 20.83334 to send the "tick" message? Did you check the basic playback speed with a start 1024?

March 5, 2006 | 3:07 pm

On 3/5/06, Joe Caputo wrote:
>
> Well Im on a mac, and the seq object DEFINETLY isnt acting properly. It
> is the ONLY weak link in my patch, and Im not sure how else to do this. I
> cant go about recording 4 6 minute long midi tracks, every time I open the
> patch.
>

You don’t have to. Seq~ reads text files, so you only have to convert your
midi once, if you keep using the same midi sequence ofcourse.

T_

June 14, 2011 | 11:35 am

Is this working ok in 5.1.8?

thanks

June 14, 2011 | 12:36 pm

The start -1 / tick messages do work OK.

p

March 19, 2015 | 4:26 am

Confirmed…

Start -1 and sending a ‘tick’ message allows for the changing of the speed of MIDI playback ‘on the fly’… and that’s great…

BUT!!!!!

And here is the big ‘gotcha’.

The first MIDI note of SEQ will ALWAYS (repeat, ALWAYS) be late!!!!!!

SEQ will try to ‘catch up’ with the following notes… but the first note WILL BE LATE!

Because of this, I have found SEQ to be useless for playing back MIDI files and looping them during playback.

I’m currently investigating alternative solutions for playing back standard MIDI files and looping them IN SYNC and am open to all suggestions on the best way to do this.

Eventually, these MIDI files will need to sync with audio, so probably SEQ~ would be a good choice if it would load a standard MIDI file – but IT DOES NOT!!!

It seems to me that a programming language as powerful as MAX 7 is SHOULD have an easy means to load, play, and loop, standard MIDI files IN SYNC and reliably.

But so far, I haven’t found anything that can do that in MAX.

All of them want some screwy workaround… like converting MIDI data into a text file, or re-recording the MIDI sequence into SEQ~ or something else like that.

I wish there as a simple ‘load a standard MIDI file and play it’ function that actually WORKED and played in TIME when looping the playback.

L

  • This reply was modified 5 months by  larryseyer.
March 20, 2015 | 2:43 am

Try [detonate]. In my experience it provides reliable timing.

March 20, 2015 | 3:00 am

I’ve been looking at that.

But so far have not been able to make it function as I would expect it to.

For instance, how do I translate ‘Delta time’ (whatever that is) into a ‘next’ bang that can change its tempo ‘on the fly’?

There does not seem to be a help file showing how to do this.

Any suggestions?

March 20, 2015 | 3:28 am

For tempo control ‘on the fly’ you just need to multiply the delay times and durations (!) with an appropriate factor. For example, factor 0.5 would double the tempo.

  • This reply was modified 5 months by  broc.
March 20, 2015 | 4:11 am

And would that playback stay in sync with an audio file?

March 20, 2015 | 5:16 am

Not sample accurate since [detonate] has resolution of 1ms.

March 20, 2015 | 12:30 pm

Thanks for the info.

I will look for another solution.

All the best to you!

Larry

Viewing 16 posts - 1 through 16 (of 16 total)

Forums > MaxMSP