Midi: Implementation news?

[Tronic]

I would ask if the new version of FS3 will be implemented
SYSTEM REAL TIME MESSAGES?
If there would be the possibility to set the size of the buffer?
limit is 1024 bytes?
now the existing primitive midi buffer does not collect sysex data?
you will also have in the vst midi sysex?

[Tronic]

I regret that not get a response

[support]

MIDI in FS only currently supports channel and system exclusive messages. This will be the same in FS3. The main difference in FS3 will be that you have precise control over when MIDI messages are sent.

You mentioned the buffer, are you talking about the R&D MIDI Buffer component?

[Tronic]

You mentioned the buffer, are you talking about the R&D MIDI Buffer component?

I meant just that component R&D MIDI Buffer, does not seem to support sysex messages.
FS3 will therefore remain the same, but with a higher accuracy. great news.

I would ask if the System Real Message will be developed in the future,
or there are special reasons could not be implemented?

Thank you for your attention.

[support]

We'd need to look into it Tronic. Without doing some digging it's difficult to say if it can be done easily or not.

You'll be able to use Ruby to manipulate MIDI data (including sysex) in FS3 so you could easily make your own MIDI buffer. The R&D component becomes redundant then.

[Tronic]

Many thanks for the answers.
I made this request to have the full support of the standard midi,
because as you say, Ruby provides a valid management system and precision,
but with the lack of System Realtime Message,
forbid the user the ability to exploit the system synchronization with midi:
MTC Quarter Frame, Song Position Pointer, Song Select, Tune Request
MIDI Clock, MIDI Tick, MIDI Start, Stop MIDI, MIDI Continue, Active Sense Reset All.
Very important in the use of the midi.
For example,
to create a project with DSP software / hardware MIDI controller,it would be my main reason to buy a license.
I hope this is possible.
Anyway thanks again for your support, it's nice to have answers, and contribute to the development of ideas.

[Tronic]

no chance to know if you work on this?

[Tronic]

add to the request, will be provided support for sysex in vst?

[support]

Sorry Tronic, with everything else we want to do it's not likely to be top of the list I'm afraid.

For sysex in VST do you want to send sysex to the host or external synths?

[Tronic]

Sysex to host and external synth.

I made all possible tests on existing components,
and it seems that we can send midi realtime messages with both primitive 'MIDI EVENT' and 'STRING TO SYSEX',
but you can not receive.
I think the most immediate solution is to manage, with the primitive 'SYSEX TO STRING'.
Because it seems that the input waste the opportunity to show values ​​after F7,
and always adds to the string that you receive F0F7 and F0 for the one sent.
Would be nice to see this work in both standalone and in vst.