SYSEX behaviour

jimDicken

When I use Forscore and when I am in the midi section of Forscore and use the Learn feature for capturing midi data, Forscore receives the hex code which is the path to the song. This works great. However, in ST4 when I use the learn function I get nothing from the keyboard when I press a song title (registration bank). I do get the individual registration buttons (Voices) but not the registration BANK (Song). I've been getting round this by using Forscore to capture the path and then pasting the path after the SX in ST4. This works, but I'm puzzled as to why ST4 doesn't receive the hex path (hex codes). I have ALL PART selected as midi setup in the Yamaha which sends and receives everything and, as mentioned, works with Forscore but no ST4. Any ideas?

AnthonyB

jimDicken I'm wondering if there is a receive event size limit in ST4 causing this issue (SYSEX Learn)? With ST3 it was only ever receiving smaller MIDI events but now with SYSEX, there is the possibility of MUCH larger chunks of data.

Voice select is nice and small - F0 43 73 01 52 25 11 00 02 00 02 F7 - which probably explains why that one works
Song select is not so small - F0 43 73 01 52 26 03 00 00 00 55 73 65 72 3A 2F 48 41 52 4D 4F 4E 59 20 47 55 59 53 20 53 4F 55 4E 44 53 2F 41 72 6D 73 20 4F 66 20 4D 61 72 79 5F 47 2D 41 5F 48 47 2E 54 31 37 34 2E 72 67 74 00 F7

I suspect (touch wood) that will be an easy fix when Peter gets back from holidays.

peter

Most likely just a buffering problem. I will take a look at it.