Sysex in XT2 ?

[basic channel]

hi

Will XT2 support sysex recording ?

Only a "select" gathering of hosts do and I use this a lot for my sw1000 and plugstation...

BC

[-PIKU-]

a great function that would be very useful for me and for all the external synth users is the ability to send different program change messages to different midi channels and ports when a project is loaded...

i use xt in stndalone mode... and i relly like the live section of the sequencer.

i'll try to explain better (i'm not good in english)
i wish to have a functin that sends a list of messages to different midi ports and channels automatically when xt opens a new project or when this function is triggered is some way...

another great function that i rellay like in audiomulch and that is missing in xt is the document switching... this allows the user to load a new project by simply pressing a button on a controller... grat for live performances

[mbncp]

If eXT would:

1) Support sysex to and from VSt plugs
2) Preserve deltaframe from live midi
3) fill the nanoSeconds field of VstTimeInfo (QueryPerformanceCounter/QueryPerformanceFrequency *10^9) , time of the next buffer swap
4) syncronise midi incoming timestamp (timeGetTime clock) with the QueryPerformanceCounter clock (used by ext, I guess), but preserving incoming queue order when syncronising.

Then it would be a perfect vst host for midi and vst-midi.

[MotorsKill23]

If eXT would:

1) Support sysex to and from VSt plugs
2) Preserve deltaframe from live midi
3) fill the nanoSeconds field of VstTimeInfo (QueryPerformanceCounter/QueryPerformanceFrequency *10^9) , time of the next buffer swap
4) syncronise midi incoming timestamp (timeGetTime clock) with the QueryPerformanceCounter clock (used by ext, I guess), but preserving incoming queue order when syncronising.

Then it would be a perfect vst host for midi and vst-midi.

++1 ...seriously on the top of my wishlist for XT2.
Unless #'s 1&2 are addressed I'll be stuck hosting XT VSTi in another host forever. And the only reason I use the other host now is Automap(RemoteSL), sysex, and live MIDI input....and I could live without Automap.

the biggie for me is the live MIDI deltaframe issue(unlike other hosts XT records the events with flawed timing to the tracks...so even proper playback isn't possible). Forces you to run very small latencies on your audio buffer wasting resources...and even then it's no fun having your external MIDI input quantised to your buffersize.

[mbncp]

If eXT would:

1) Support sysex to and from VSt plugs
2) Preserve deltaframe from live midi
3) fill the nanoSeconds field of VstTimeInfo (QueryPerformanceCounter/QueryPerformanceFrequency *10^9) , time of the next buffer swap
4) syncronise midi incoming timestamp (timeGetTime clock) with the QueryPerformanceCounter clock (used by ext, I guess), but preserving incoming queue order when syncronising.

Then it would be a perfect vst host for midi and vst-midi.

++1 ...seriously on the top of my wishlist for XT2.
Unless #'s 1&2 are addressed I'll be stuck hosting XT VSTi in another host forever. And the only reason I use the other host now is Automap(RemoteSL), sysex, and live MIDI input....and I could live without Automap.

the biggie for me is the live MIDI deltaframe issue(unlike other hosts XT records the events with flawed timing to the tracks...so even proper playback isn't possible). Forces you to run very small latencies on your audio buffer wasting resources...and even then it's no fun having your external MIDI input quantised to your buffersize.

If eXT would do point 3) I could use my plug that does 2) and 4) and even convert sysex to some CC. But I would prefer that the host deals with that.
Otherwise, eXT is a very good vst-midi host, all events make it in the same buffer.
Though, when used as a VST and sending the midi back to the host, but I noticed that the midi is delayed by one buffer if the audio out of the plug is connected, weird.

Until the vst-midi routing is fixed in vsthost, my best bet for a live host or for playback of midi only apps (using a large buffer), is to have an instance of eXT in vsthost when I need vst-midi plugs.
I also need ext vst-midi capabilities when using vst-midi in sx, which will often delay the midi to the next buffer with a null timestamp, and this even on playback.

And my best solution so far for midi projects (I almost never use audio, singing in my head)
sx+eXT, asio4all, 2048 samples, recording the midi and playing recorded tracks
vsthost+ext, fw asio, 64 or 128 samples, playing the live midi being recorded in sx
That means no need to freeze or turn off plugs with delay when recording and pretty good timing. Maybe one day a single host will do it all, perfect midi and dual buffers, the record enabled track using a special audio routing with a smaller buffer.

[yatzy]

Hi PIKU!

a great function that would be very useful for me and for all the external synth users is the ability to send different program change messages to different midi channels and ports when a project is loaded...

Exactly like my feature request here:
http://www.kvraudio.com/forum/viewtopic.php?t=147310

another great function that i rellay like in audiomulch and that is missing in xt is the document switching... this allows the user to load a new project by simply pressing a button on a controller... grat for live performances

That can be done using the File Mapper.
Just assign an .ext-file to load when receiving a specific program change message.

Regards, Magnus

[plastique]

Hi PIKU!

a great function that would be very useful for me and for all the external synth users is the ability to send different program change messages to different midi channels and ports when a project is loaded...

Exactly like my feature request here:
http://www.kvraudio.com/forum/viewtopic.php?t=147310

Hi ,

there's a plugin I made a few days ago which can autosend one program change message per channel after the plugin has loaded into the project (after a preconfigurable delay).
Let me know if this could be useful and I'll prepare it for release in the next few days.
This is the current state:



Can anyone tell if bank selection will work by sending CC 0 and 32 ? If yes, then I'm going to add this as well (per channel). As I don't have any hardware synths with bank selection, I have to take someone at his word for this.

[yatzy]

Hi ,

there's a plugin I made a few days ago which can autosend one program change message per channel after the plugin has loaded into the project (after a preconfigurable delay).
Let me know if this could be useful and I'll prepare it for release in the next few days.
This is the current state:



Can anyone tell if bank selection will work by sending CC 0 and 32 ? If yes, then I'm going to add this as well (per channel). As I don't have any hardware synths with bank selection, I have to take someone at his word for this.

Yippie kay-oh!!!

Bank selection is done with cc 0 and 32, 0 selecting the MSB (Most significant Byte) and 32 selecting LSB(Least significant byte). Hardware synths behave very different on these values. The order in which LSB and MSB is sent is therefore also important. So you should have a switch to select bank order.

Check out NicFit's nF_PC_CK2 plugin to see one solution:
http://asseca.com/nicfit/pc_ck.html

New idea in my head. Must... give... birth...

The only thing needed actually is a plug that sends one single program change after a certain delay!
You could then insert separate instances of the nF_PC_CK2 plug, representing each hardware synth in your setup. When they receive the auto-PC they send PC/MSB/LSB for each synth.


But sure, if your plug did all the above, there would be more real estate left on screen...


Regards, Magnus

[yatzy]

I couldn't stop thinking about this...

Here's one possible solution:


It would be ideal if you could dynamically add a strip when needed to keep down real estate even further. Like this:



Well, enough brainstroming...

Regards, Magnus

[plastique]

Brilliant, thanks
This will give the right headstart.

The basis is already layed out here, just the gui needs some more work now.

[-PIKU-]

if possible, it could be useful to add the ability to send sysex messages and even cc and notes

and not only at loading of a new project, but even when triggered by a note or cc...
this is useful when you want to make "scenes" for external gear, sending a great number of sound modification commands to may machines on many midi channels...

[plastique]

I'm sure you find the additional possibilities in eXT (not sysex though).

Sysex is not supprted by eXT at the moment, so you gotta keep requesting this one for someone to be able to come up with sysex-supporting VST/i.

[jorgen]

working on it

cheers
jorgen

[asseca]

In the meantime try this: (MidiXbar)

[plastique]

Update:

The developped plugin is almost ready. There are just a few more tests needed before I can make it available - sometimes during tomorrow daytime I would guess ...