jgaudin

I was using a patch both in Max 6 and 7 to send midi tick (248) values through midi out.

It stopped working and I cannot figure out. Midi notes pass through midi out, but just the message (decimal) or the INT does not (no 248 no 250 etc...)

Even the most easy patch {248} to {midiout} doesnt work, while {240 0 0} to {midiout} works

It stopped working and I cannot figure out. Midi notes pass through midi out, but just the message (decimal) or the INT does not (no  248 no 250 etc...)

I was using a patch both in Max 6 and 7 to send midi tick (248) values through midi out.
It stopped working and I cannot figure out. Midi no

midiout-not-sending-clock-tick-message-«248»

Probably there is an invalid message confusing [midiout].

Can you post a patch to reproduce the issue?

Probably there is an invalid message confusing [midiout].
Can you post a patch to reproduce the issue?

fails when doing a midi loopback (it sends 248 0 0, but not 248)

Midiout sends realtime messages allright.

Midiin is not receiving them, You can use rtin instead.

If You need any other than midi specified messages,

If You send 248 0 0, one Tick gets sent out,

Midiin spits only 0 0 out, Tick 248 gets ignored.

If midi string You send does not fall into specified

midi message cathegories, like notes , CC etc

it might work for some "private" messaging system,

but I don't know if all midi interfaces would let that happen,

and also it can lead to confusion, because some systems try to thin out

midi stream, and accept sending / receiving of repeating midi messages

by droping the status byte, like 176 1 nn, followed by another 176 1 nn

Thats why it is better to stay within specs.

Midiout sends realtime messages allright.
Midiin is not receiving them, You can use rtin instead.
If You need any other than midi specified messages,
You have to use sysex I am afraid.
If You send 248 0 0, one Tick gets sent out,
followed by 2 zeroes.
Midiin spits only 0 0  out, Tick 248 gets ignored.
If midi string You send does not fall into specified
midi message cathegories, like notes , CC etc
it might work for some "private" messaging system,
but I don't know if all midi interfaces would let that happen,
and also it can lead to confusion, because some systems try to thin out
midi stream, and accept sending / receiving of repeating midi messages
by droping the status byte, like 176 1 nn, followed by another 176 1 nn
would send just 1 nn.
Thats why it is better to stay within specs.


Ok, thank you @Broc and @ Source Audio, I figured it out now.

midiout not sending clock tick message (248)