FR theme: External MIDI Hardware
-
- KVRist
- Topic Starter
- 88 posts since 28 Jun, 2006
I just placed the payment for eXT2 with the hope that MIDI Out will be supported soon. Until then I'll use NicFits midi out.
-
- KVRian
- 795 posts since 2 Apr, 2006
+1 for multiple midi outs
I'd also like a store sysex patch on a sequencer midi track. It would dump the patch to the port it's assigned to. This way I could save hardware patches in the project.
Podium kind of allows you to do this.
I'd also like a store sysex patch on a sequencer midi track. It would dump the patch to the port it's assigned to. This way I could save hardware patches in the project.
Podium kind of allows you to do this.
-
- KVRist
- 285 posts since 17 Mar, 2004 from Denmark
+1Kyran wrote:I'd also like a store sysex patch on a sequencer midi track. It would dump the patch to the port it's assigned to.
Yamaha RM1X,Akai S2000,TQ5,CME UF5,Waldorf blofeld,Compact4,Yamaha A3k, Variax300, Yamaha MU10, Korg Padkontrol,Bidule.UAD1, Liveslice,Delta 1010,Delta 66 x2.
-
- KVRAF
- 5350 posts since 8 Aug, 2003 from Berlin Germany
I'd like support for relative controllers (dials) on the input.
(I've also been interested in Novation's Automap but haven't tried it yet)
(I've also been interested in Novation's Automap but haven't tried it yet)
-
- KVRist
- 333 posts since 23 Apr, 2003
Support for syncing master & slave to MTC, MMC or MIDI clock as noted in this FR thread. 
Why?
-synching to my hardware sequencer (which simply has a different workflow than software as a composition & live improv tool)
-sync with my friend's computer & sequencers when jamming with people
-syncing LFO's on my hardware synths
Why?
-synching to my hardware sequencer (which simply has a different workflow than software as a composition & live improv tool)
-sync with my friend's computer & sequencers when jamming with people
-syncing LFO's on my hardware synths
-
- KVRist
- 55 posts since 25 Dec, 2006
Yes, please!lung wrote:Support for syncing master & slave to MTC, MMC or MIDI clock as noted in this FR thread.
I NEED to be able to sync my MPC to XT2 or vice versa.
-
- KVRAF
- 4340 posts since 8 Mar, 2005
-
- KVRAF
- 7017 posts since 28 Apr, 2004 from france
If i didn't already said it : +1
ANd if i already said it : +1 too !
ANd if i already said it : +1 too !
-
- KVRian
- 1239 posts since 17 Jul, 2003
Here is a MIDI IO, the inside is a little complex, locks and/or crashes are not impossible.
Midi In/Out : Host, midi Port, Both, None
In/Out Port: first 32 available ports
*In/Out Mode: Immediate(cheap way, à la xt, cubase, .., stamp = 0), Stamped: keeps relative timestamp, a must with larger audio buffers
*OutDelay: you can add a delay to MIDI out: 0-100 msec
*Applies only to Midi Ports
http://homepage.hispeed.ch/mbncp/midiio100/MIDIIO.zip
As ext doesn't call suspend when it should, a timer checks the connections. When it's detected (after about 2-3 seconds) ports are closed and buffer are flushed to prevent unlimited buffer growth.
Avoid playing MIDI when changing settings (the first 4), as currently it just flushes the buffers and may result in hanging notes.
Also some MIDI ports (ex: loopbe) don't allow more than one instance of the same port per process. As the plug is running in the same process than the host, you may have to disable the port in the host.
Edit:
And it supports sysex (max 64 bytes) but as xt is throwing them away
Midi In/Out : Host, midi Port, Both, None
In/Out Port: first 32 available ports
*In/Out Mode: Immediate(cheap way, à la xt, cubase, .., stamp = 0), Stamped: keeps relative timestamp, a must with larger audio buffers
*OutDelay: you can add a delay to MIDI out: 0-100 msec
*Applies only to Midi Ports
http://homepage.hispeed.ch/mbncp/midiio100/MIDIIO.zip
As ext doesn't call suspend when it should, a timer checks the connections. When it's detected (after about 2-3 seconds) ports are closed and buffer are flushed to prevent unlimited buffer growth.
Avoid playing MIDI when changing settings (the first 4), as currently it just flushes the buffers and may result in hanging notes.
Also some MIDI ports (ex: loopbe) don't allow more than one instance of the same port per process. As the plug is running in the same process than the host, you may have to disable the port in the host.
Edit:
And it supports sysex (max 64 bytes) but as xt is throwing them away
-
- KVRist
- 35 posts since 7 Apr, 2007
-
- KVRian
- 1239 posts since 17 Jul, 2003
Updated MIDI IO same link:
http://homepage.hispeed.ch/mbncp/midiio100/MIDIIO.zip
Host In Channel and Port In Channel act like input filters.
Host Out Channel and Port Out Channel act like a transformer.
And most important, now all instance of the plug within the same process (host) share the same hardware ports connection.
(Usefull as some ports allow only a limited connections)
Btw, speaking about the MIDI in mode (stamped or not):
http://homepage.hispeed.ch/mbncp/images ... e-test.jpg
Off course this is less important when using a small aiso buffer, but to use ext with VSTi plugs from another host or external hardware, it can make a difference.
EDIT:
Removed the (unused) audio out except when run from Cubase(needs it).
Ans as I had to clean the buffer this one takes even less processing time.
Same link.
http://homepage.hispeed.ch/mbncp/midiio100/MIDIIO.zip
Host In Channel and Port In Channel act like input filters.
Host Out Channel and Port Out Channel act like a transformer.
And most important, now all instance of the plug within the same process (host) share the same hardware ports connection.
(Usefull as some ports allow only a limited connections)
Btw, speaking about the MIDI in mode (stamped or not):
http://homepage.hispeed.ch/mbncp/images ... e-test.jpg
Off course this is less important when using a small aiso buffer, but to use ext with VSTi plugs from another host or external hardware, it can make a difference.
EDIT:
Removed the (unused) audio out except when run from Cubase(needs it).
Ans as I had to clean the buffer this one takes even less processing time.
Same link.
-
- KVRist
- 443 posts since 13 Feb, 2006
requests for hardware controller handling:
1- the same cc coming from different channels or prts cannot be confused. this has to be fixed
2- soft takeover function (like in traktor) to avoid bad effects while playing live
3- support for relative controllers + midi feedback to control leds (solo\mute\ledrings)
4- support for incremental encoders (like in traktor) with sensitivity and acceleration
5- cc inertia. and conversion in high resolution (14bit) for better results tweaking filters
6- recallable snapshot function
7- morph between snapshots
1- the same cc coming from different channels or prts cannot be confused. this has to be fixed
2- soft takeover function (like in traktor) to avoid bad effects while playing live
3- support for relative controllers + midi feedback to control leds (solo\mute\ledrings)
4- support for incremental encoders (like in traktor) with sensitivity and acceleration
5- cc inertia. and conversion in high resolution (14bit) for better results tweaking filters
6- recallable snapshot function
7- morph between snapshots
Last edited by -PIKU- on Fri Jul 06, 2007 3:23 pm, edited 1 time in total.
-
- KVRist
- 443 posts since 13 Feb, 2006
8- and the possibility to control mute\solo or other swithes usinf note on\off messages
-
hesnotthemessiah hesnotthemessiah https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7516 - KVRian
- 986 posts since 6 Jun, 2003 from Reading UK. (U rrrrrrs)
I want to dump my crappy Cubase VST5 completely but can't until eXT features support for multiple MIDI out. Does eXT support MIDI out at all at the moment?
Windows 10. Asus X99-Pro i7 6950X 10 Core 3GHz (Overclocked to 3.5GHz). Corsair DDR4 64GB Vengeance LPX 2400MHz. RME RayDAT. NVIDIA GeForce GTX 970. UAD2 Quad+Octo. Reaper. A couple of plugins.