MIDI bug with v1.1.0

[red]

As noted in pre v1.0.7 versions there are some midi problems with external devices - especially in the init phase (power on sequence). So I have to reset the external device before it works properly. Sometimes there are also some hanging notes...

In v1.0.7 midi with external devices was running stable without any problems.

I'm not able to reproduce this effect to 100% but in most cases it fails.


Thanks for solving

[_DemonDan_]

Hi red,

Have you used MIDI Monitor (Mac) or MidiOx (PC) to see exactly what messages are being sent on power up?

[red]

Hi Daniel

Here are three power-on-sequences, each a bit different (no idea what they could provocate...)








Thanks

[_DemonDan_]

Hmmm...

What is it that's sending CC#s 15 & 79 on MIDI Channel 8?

I don't think that's coming from the Sub 37.

[red]

The Sub 37 is the only device connected to the MAC (via Scarlett interface and Roland A-880)...

The Voyager (to compare) sends an ALL NOTE OFF and a NOTE OFF on every single note.
I think in best case no midi messages should be send (or with a delay, so that other devices are ready to communicate...)

[Kollektor]

Hmmm...

What is it that's sending CC#s 15 & 79 on MIDI Channel 8?

I don't think that's coming from the Sub 37.

It's actually a Program Change message. The Sub37 possibly sends the currently selected patch 15 and 79 in those cases. It's a bit strange that it sends PC on channel 8 and that its happening intermittently though.

Red, what is your SEND PGM CHG (MIFI MENU 1.3) setting? If it was ON try switching it OFF and monitor MIDI again and see if something changed.

/Andy

[red]

also a statement from Moog side would be heartily welcome! I'm sure Amos could explain this behavior...

Thanks in advance

[red]

Thanks Andy

I set SEND PGM CHG to OFF - but the MIDI sequence is still the same:



Would it be possible to disable MIDI output during the power on sequence (in a future update)?




[ strange - your answer was posted before my request, so I didn't check it... ]

[Kollektor]

[ strange - your answer was posted before my request, so I didn't check it... ]

I hadn't posted enough to go past the initial moderation so it took a while before my posts showed up.

Reading your original post again made me recall something about the Monomachine and the Machinedrum. When you switch those on they init by sending 0 on CC7 (Volume) which generated quite a bit if frustration from users. The workaround I used to overcome this problem was to take particular care to the boot order of my MIDI connected devices. It might not work with your setup though but starting the Sub37 first of all devices might be a feasible workaround.

/Andy

[_DemonDan_]

What is it that's sending CC#s 15 & 79 on MIDI Channel 8?
I don't think that's coming from the Sub 37.

I still don't think that the Data coming in on MIDI Channel 8 is from the Sub 37.

I just tried this myself and am only getting CC#1 (Mod Wheel) and CC# 7 (Volume).

The Volume CC reflects the current position of the Sub 37's OUTPUT VOLUME knob.

{The Mod Wheel CC, strangely, is always sending 127 regardless of its position. Why is that?}

Try this:

Borrow a simple MIDI/USB interface (instead of the Scarlett) and do the test again.

First, set the Sub 37 to an INIT PRESET. Then power off.

Make sure your MIDI monitoring app is seeing the MIDI/USB interface.

Power on. Let me know if you're still seeing anything other than CC#1 and CC#7.

[DaveBee]

This may be totally unrelated, but I am having strange results at times with my daw (Sonar X1) and the Sub37. Sometimes for no reason I can discern ... the Sub37 loses audio output ... both playing keyboard and for recorded midi. It is not a local control being set off ... because that is still on when I check settings. Other midi settings also look normal. In the other direction sometimes midi just seems to stop outputting to the daw. Again a repower is required. When I repower the Sub37 I usually also need to restart my daw so it recognizes the Sub37. It's workable but extremely annoying when simply trying to create. My guess is some midi CCs from the daw might be having some adverse effect on the Sub37. In a few cases the SUb37 controls themselves appeared to be frozen.

[red]

Daniel, I have no access to an other MIDI interface...
As I wrote before, I tested the power on sequence with other devices, and they are not sending additional midi bytes.
The only action is coming from the Sub 37, the other devices are passive at that moment and can not produce any bytes in addition to the Sub 37 MIDI signals...
The data on channel 8 are always in the same place in the sequence, only the value can be different.

[_DemonDan_]

As I wrote before, I tested the power on sequence with other devices, and they are not sending additional MIDI bytes.

Yeah, but I'm wondering if something from the Sub 37 is making the Scarlett send something on Channel 8.

[_DemonDan_]

I have no access to another MIDI interface.

In all of Switzerland, there isn't a single USB/MIDI interface that someone can loan you?

[red]

It's a question of the effort...