Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #40667 > unrolled thread

Why does clock midi "synch" give overload error?

Started byJonas Thörnvall <jonas.thornvall@gmail.com>
First post2021-12-17 16:51 -0800
Last post2021-12-18 01:45 -0800
Articles 9 — 2 participants

Back to article view | Back to comp.lang.javascript

Contents

  Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-17 16:51 -0800
    Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-17 17:54 -0800
      Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-17 18:25 -0800
        Re: Why does clock midi "synch" give overload error? luserdroog <luser.droog@gmail.com> - 2021-12-17 20:06 -0800
          Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-18 01:32 -0800
            Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-18 01:47 -0800
              Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-18 02:17 -0800
                Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-18 23:56 -0800
          Re: Why does clock midi "synch" give overload error? Jonas Thörnvall <jonas.thornvall@gmail.com> - 2021-12-18 01:45 -0800

#40667 — Why does clock midi "synch" give overload error?

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-17 16:51 -0800
SubjectWhy does clock midi "synch" give overload error?
Message-ID<85243597-8640-4975-843b-827061de368cn@googlegroups.com>
https://jtmidi.000webhostapp.com/

[toc] | [next] | [standalone]

#40668

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-17 17:54 -0800
Message-ID<4144b16d-5d83-4403-b9cc-e09a8abc5db7n@googlegroups.com>
In reply to#40667
lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall:
> https://jtmidi.000webhostapp.com/

Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API,

https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes

So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent?
I did see luser wrote some midi code maybe he could look at it.

[toc] | [prev] | [next] | [standalone]

#40669

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-17 18:25 -0800
Message-ID<f092584e-fac1-416c-9732-b714d39d46afn@googlegroups.com>
In reply to#40668
lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall:
> lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > https://jtmidi.000webhostapp.com/ 
> 
> Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> 
> https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> 
> So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> I did see luser wrote some midi code maybe he could look at it.
Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module.

[toc] | [prev] | [next] | [standalone]

#40670

Fromluserdroog <luser.droog@gmail.com>
Date2021-12-17 20:06 -0800
Message-ID<dfc4e1f8-d2de-414a-b851-63ba88242ffcn@googlegroups.com>
In reply to#40669
On Friday, December 17, 2021 at 8:25:12 PM UTC-6, jonas.t...@gmail.com wrote:
> lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall: 
> > lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > > https://jtmidi.000webhostapp.com/ 
> > 
> > Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> > 
> > https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> > 
> > So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> > I did see luser wrote some midi code maybe he could look at it.
> Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module.

Hmm. I don't know. You're kind of off of the map of anything I've actually done with MIDI.
248 is "Timing Clock" but I don't know what that means or how to use it. 250 is "Start" 
presumably as a command to a sequencer, accompanied by 251 "Continue" and 252
"Stop". 

So you're actually sending these messages over a wire (or 9, or 5, or whatever)
to a sound gizmo?

If these messages are causing problems with the sound module, then you could
add a box in the middle to filter them out. Or, maybe re-think why they're needed
in the first place. Maybe it's an X/Y problem and it doesn't need to be done that
way because of the problems it causes.

But I'm just shooting in the dark. Which is probably dangerous.

[toc] | [prev] | [next] | [standalone]

#40671

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-18 01:32 -0800
Message-ID<9d367889-c385-49bd-a667-b15f2569baa4n@googlegroups.com>
In reply to#40670
lördag 18 december 2021 kl. 05:06:13 UTC+1 skrev luser...@gmail.com:
> On Friday, December 17, 2021 at 8:25:12 PM UTC-6, jonas.t...@gmail.com wrote: 
> > lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall: 
> > > lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > > > https://jtmidi.000webhostapp.com/ 
> > > 
> > > Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> > > 
> > > https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> > > 
> > > So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> > > I did see luser wrote some midi code maybe he could look at it. 
> > Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module.
> Hmm. I don't know. You're kind of off of the map of anything I've actually done with MIDI. 
> 248 is "Timing Clock" but I don't know what that means or how to use it. 250 is "Start" 
> presumably as a command to a sequencer, accompanied by 251 "Continue" and 252 
> "Stop". 
> 
> So you're actually sending these messages over a wire (or 9, or 5, or whatever) 
> to a sound gizmo? 
> 
> If these messages are causing problems with the sound module, then you could 
> add a box in the middle to filter them out. Or, maybe re-think why they're needed 
> in the first place. Maybe it's an X/Y problem and it doesn't need to be done that 
> way because of the problems it causes. 
> 
> But I'm just shooting in the dark. Which is probably dangerous.
I think i  did imagine to hear those clicks within signal because earlier problems, when i changed song i do not hear them.
It actually seem to work know just sending the status byte.

My clock synch "track"  just start as one push play or record of song.
I will add the start pause and resume messages today.

http://jtmidi.000webhostapp.com/


function renderSynch(){
	currentTime=0;
	track[444].midiMess.length=0;
	synchClockInterval=(timePerBAR/4)/24;
	track[444].midiMess.push({
		time: currentTime,
		data0: 250
	});
	currentTime=currentTime+synchClockInterval;
	while (currentTime<600000){
	track[444].midiMess.push({
		time: currentTime,
		data0: 248
	});	
	currentTime=currentTime+synchClockInterval;	
	}
}

[toc] | [prev] | [next] | [standalone]

#40673

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-18 01:47 -0800
Message-ID<59915378-d932-4ed0-930b-0c2c5b4a32b5n@googlegroups.com>
In reply to#40671
lördag 18 december 2021 kl. 10:32:31 UTC+1 skrev Jonas Thörnvall:
> lördag 18 december 2021 kl. 05:06:13 UTC+1 skrev luser...@gmail.com: 
> > On Friday, December 17, 2021 at 8:25:12 PM UTC-6, jonas.t...@gmail.com wrote: 
> > > lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall: 
> > > > lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > > > > https://jtmidi.000webhostapp.com/ 
> > > > 
> > > > Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> > > > 
> > > > https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> > > > 
> > > > So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> > > > I did see luser wrote some midi code maybe he could look at it. 
> > > Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module. 
> > Hmm. I don't know. You're kind of off of the map of anything I've actually done with MIDI. 
> > 248 is "Timing Clock" but I don't know what that means or how to use it. 250 is "Start" 
> > presumably as a command to a sequencer, accompanied by 251 "Continue" and 252 
> > "Stop". 
> > 
> > So you're actually sending these messages over a wire (or 9, or 5, or whatever) 
> > to a sound gizmo? 
> > 
> > If these messages are causing problems with the sound module, then you could 
> > add a box in the middle to filter them out. Or, maybe re-think why they're needed 
> > in the first place. Maybe it's an X/Y problem and it doesn't need to be done that 
> > way because of the problems it causes. 
> > 
> > But I'm just shooting in the dark. Which is probably dangerous.
> I think i did imagine to hear those clicks within signal because earlier problems, when i changed song i do not hear them. 
> It actually seem to work know just sending the status byte. 
> 
> My clock synch "track" just start as one push play or record of song. 
> I will add the start pause and resume messages today. 
> 
> http://jtmidi.000webhostapp.com/ 
> 
> 
> function renderSynch(){ 
> currentTime=0; 
> track[444].midiMess.length=0; 
> synchClockInterval=(timePerBAR/4)/24; 
> track[444].midiMess.push({ 
> time: currentTime, 
> data0: 250 
> }); 
> currentTime=currentTime+synchClockInterval; 
> while (currentTime<600000){ 
> track[444].midiMess.push({ 
> time: currentTime, 
> data0: 248 
> }); 
> currentTime=currentTime+synchClockInterval; 
> } 
> }
You probably need a midicable connected, i am not sure script start fully without it. I can't jank it out and in to see if it work all the time.

[toc] | [prev] | [next] | [standalone]

#40674

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-18 02:17 -0800
Message-ID<2a174c2d-447b-42c5-a62c-f394a1a28605n@googlegroups.com>
In reply to#40673
lördag 18 december 2021 kl. 10:47:59 UTC+1 skrev Jonas Thörnvall:
> lördag 18 december 2021 kl. 10:32:31 UTC+1 skrev Jonas Thörnvall: 
> > lördag 18 december 2021 kl. 05:06:13 UTC+1 skrev luser...@gmail.com: 
> > > On Friday, December 17, 2021 at 8:25:12 PM UTC-6, jonas.t...@gmail.com wrote: 
> > > > lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall: 
> > > > > lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > > > > > https://jtmidi.000webhostapp.com/ 
> > > > > 
> > > > > Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> > > > > 
> > > > > https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> > > > > 
> > > > > So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> > > > > I did see luser wrote some midi code maybe he could look at it. 
> > > > Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module. 
> > > Hmm. I don't know. You're kind of off of the map of anything I've actually done with MIDI. 
> > > 248 is "Timing Clock" but I don't know what that means or how to use it. 250 is "Start" 
> > > presumably as a command to a sequencer, accompanied by 251 "Continue" and 252 
> > > "Stop". 
> > > 
> > > So you're actually sending these messages over a wire (or 9, or 5, or whatever) 
> > > to a sound gizmo? 
> > > 
> > > If these messages are causing problems with the sound module, then you could 
> > > add a box in the middle to filter them out. Or, maybe re-think why they're needed 
> > > in the first place. Maybe it's an X/Y problem and it doesn't need to be done that 
> > > way because of the problems it causes. 
> > > 
> > > But I'm just shooting in the dark. Which is probably dangerous. 
> > I think i did imagine to hear those clicks within signal because earlier problems, when i changed song i do not hear them. 
> > It actually seem to work know just sending the status byte. 
> > 
> > My clock synch "track" just start as one push play or record of song. 
> > I will add the start pause and resume messages today. 
> > 
> > http://jtmidi.000webhostapp.com/ 
> > 
> > 
> > function renderSynch(){ 
> > currentTime=0; 
> > track[444].midiMess.length=0; 
> > synchClockInterval=(timePerBAR/4)/24; 
> > track[444].midiMess.push({ 
> > time: currentTime, 
> > data0: 250 
> > }); 
> > currentTime=currentTime+synchClockInterval; 
> > while (currentTime<600000){ 
> > track[444].midiMess.push({ 
> > time: currentTime, 
> > data0: 248 
> > }); 
> > currentTime=currentTime+synchClockInterval; 
> > } 
> > }
> You probably need a midicable connected, i am not sure script start fully without it. I can't jank it out and in to see if it work all the time.
Ok now i implemented them, i but i don't know how to set up my Kurzweil K2000 into receive synch signal.

[toc] | [prev] | [next] | [standalone]

#40679

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-18 23:56 -0800
Message-ID<31f84dad-f832-4ab0-990f-00a27f7df2e1n@googlegroups.com>
In reply to#40674
lördag 18 december 2021 kl. 11:18:05 UTC+1 skrev Jonas Thörnvall:
> lördag 18 december 2021 kl. 10:47:59 UTC+1 skrev Jonas Thörnvall: 
> > lördag 18 december 2021 kl. 10:32:31 UTC+1 skrev Jonas Thörnvall: 
> > > lördag 18 december 2021 kl. 05:06:13 UTC+1 skrev luser...@gmail.com: 
> > > > On Friday, December 17, 2021 at 8:25:12 PM UTC-6, jonas.t...@gmail.com wrote: 
> > > > > lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall: 
> > > > > > lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > > > > > > https://jtmidi.000webhostapp.com/ 
> > > > > > 
> > > > > > Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> > > > > > 
> > > > > > https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> > > > > > 
> > > > > > So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> > > > > > I did see luser wrote some midi code maybe he could look at it. 
> > > > > Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module. 
> > > > Hmm. I don't know. You're kind of off of the map of anything I've actually done with MIDI. 
> > > > 248 is "Timing Clock" but I don't know what that means or how to use it. 250 is "Start" 
> > > > presumably as a command to a sequencer, accompanied by 251 "Continue" and 252 
> > > > "Stop". 
> > > > 
> > > > So you're actually sending these messages over a wire (or 9, or 5, or whatever) 
> > > > to a sound gizmo? 
> > > > 
> > > > If these messages are causing problems with the sound module, then you could 
> > > > add a box in the middle to filter them out. Or, maybe re-think why they're needed 
> > > > in the first place. Maybe it's an X/Y problem and it doesn't need to be done that 
> > > > way because of the problems it causes. 
> > > > 
> > > > But I'm just shooting in the dark. Which is probably dangerous. 
> > > I think i did imagine to hear those clicks within signal because earlier problems, when i changed song i do not hear them. 
> > > It actually seem to work know just sending the status byte. 
> > > 
> > > My clock synch "track" just start as one push play or record of song. 
> > > I will add the start pause and resume messages today. 
> > > 
> > > http://jtmidi.000webhostapp.com/ 
> > > 
> > > 
> > > function renderSynch(){ 
> > > currentTime=0; 
> > > track[444].midiMess.length=0; 
> > > synchClockInterval=(timePerBAR/4)/24; 
> > > track[444].midiMess.push({ 
> > > time: currentTime, 
> > > data0: 250 
> > > }); 
> > > currentTime=currentTime+synchClockInterval; 
> > > while (currentTime<600000){ 
> > > track[444].midiMess.push({ 
> > > time: currentTime, 
> > > data0: 248 
> > > }); 
> > > currentTime=currentTime+synchClockInterval; 
> > > } 
> > > } 
> > You probably need a midicable connected, i am not sure script start fully without it. I can't jank it out and in to see if it work all the time.
> Ok now i implemented them, i but i don't know how to set up my Kurzweil K2000 into receive synch signal.
Got around to test the midi beat sync signal, the only software that i could easily configure was the old Propeller heads Rebirth "TB-303".
Free downloadable from Internet Archive.
https://www.facebook.com/jonas.thornvall/videos/287212996687954/

[toc] | [prev] | [next] | [standalone]

#40672

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2021-12-18 01:45 -0800
Message-ID<03914fa6-d30f-4c83-9d8c-c2b38802a071n@googlegroups.com>
In reply to#40670
lördag 18 december 2021 kl. 05:06:13 UTC+1 skrev luser...@gmail.com:
> On Friday, December 17, 2021 at 8:25:12 PM UTC-6, jonas.t...@gmail.com wrote: 
> > lördag 18 december 2021 kl. 02:54:40 UTC+1 skrev Jonas Thörnvall: 
> > > lördag 18 december 2021 kl. 01:52:01 UTC+1 skrev Jonas Thörnvall: 
> > > > https://jtmidi.000webhostapp.com/ 
> > > 
> > > Here is the spec for the message, "note i included a first data byte" somewhere someone wrote it would be necessary with the midi API, 
> > > 
> > > https://www.midi.org/specifications-old/item/table-2-expanded-messages-list-status-bytes 
> > > 
> > > So does javascript not support statusbyte 250 and 248 or can't in hand the rate is it sent? 
> > > I did see luser wrote some midi code maybe he could look at it. 
> > Ok got messages to pass only using the status byte, but i hear some strange glitchy noice from my soundcanvas when clock messages within stream, they should not be there recognised at module.
> Hmm. I don't know. You're kind of off of the map of anything I've actually done with MIDI. 
> 248 is "Timing Clock" but I don't know what that means or how to use it. 250 is "Start" 
> presumably as a command to a sequencer, accompanied by 251 "Continue" and 252 
> "Stop". 
> 
> So you're actually sending these messages over a wire (or 9, or 5, or whatever) 
> to a sound gizmo? 
> 
> If these messages are causing problems with the sound module, then you could 
> add a box in the middle to filter them out. Or, maybe re-think why they're needed 
> in the first place. Maybe it's an X/Y problem and it doesn't need to be done that 
> way because of the problems it causes. 
> 
> But I'm just shooting in the dark. Which is probably dangerous.

248 actual clcok "timings" that you have to send out at intervals

clock (decimal 248, hex 0xF8)
start (decimal 250, hex 0xFA)
continue/resume (decimal 251, hex 0xFB)
stop (decimal 252, hex 0xFC)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web