ISt das echt so? Dachte alle Apps könnten die Midi Daten unabhängig voneinander lesen. Wenn nicht... dann gibt es sicherlich "Splitter" in Software.

du kannst ( laut meiner erfahrung) pro midi controller nur ein programm benutzen.... ich kann zb serato & ableton live auch nicht gleichzeitig per midi ansteuern !

Ja wirklich! Sonst ist das blöd :D

jaaa aber der behringer is sowohl midi controller als auch steuerelement... ich zb steuer per djm 800 und 1x1 midi controller...

@nik39
ne kleine erkläreung wäre nicht schlecht für die, die des englischen nicht mächtig sind.

Ich glaub bei Dir hackt es. Wenn Du kein englisch kannst, ist das DEIN Problem. Bin ich Dein persönlicher Übersetzer, oder was?

*Kopfschüttel*

mich ärgert bloß, dass anstatt richtiger hilfe nur ein paar links gestreut werden

das sich hier scheinbar auf kosten des fragenden lustig gemacht wird anstelle von konstruktiver hilfestellung find ich echt keimig.

Ich glaub bei Dir hackt es. Wenn Du kein englisch kannst, ist das DEIN Problem. Bin ich Dein persönlicher Übersetzer, oder was?

*Kopfschüttel*

mich ärgert bloß, dass anstatt richtiger hilfe nur ein paar links gestreut werden, die mich nicht weiterbringen. wär es so einfach würde ich hier echt keine frage posten! das sich hier scheinbar auf kosten des fragenden lustig gemacht wird anstelle von konstruktiver hilfestellung find ich echt keimig. aber das ist wohl ein generelles problem in den foren dieser welt!

Using MIDI Yoke

MIDI Yoke is not a normal driver! It is a like a MIDI Patch Cable: it takes any data that shows up at its MIDI Yoke Output port and spits it out of its MIDI Yoke Input port! This seems to be really counterintuitive to people, but it's the only way that it can work as a patch cable. Imagine setting up a hardware loopback: you attach one end of a normal MIDI cable to your MIDI Interface Output port, and the other end back to the Input Port. This is exactly what MIDI Yoke accomplishes in software (and frees up your MIDI hardware interface for other use). MIDI Yoke is used to attach different MIDI applications together -- it links them via MIDI. One applications MIDI Output is directed to the next applications MIDI Input.

This also means that you should never, ever, open the same MIDI Yoke port number as both input and output within a single application -- it is suicidal to do so. When this happens, any MIDI message sent to the output port is immediately routed back to the input port, which is then sent out the output port and immediately routed back to the input port... I think you get the idea: MIDI Feedback! This all happens very, very fast (at interrupt time), and if it is not stopped, your machine will appear to be hung. MIDI Yoke attempts to detect this condition and will break the connection when it is detected. It is also possible to setup a feedback loop among several applications, so be careful and think about what you are doing -- draw the circuit on a piece of paper if necessary.

After a MIDI feedback report, you need to close and reopen the driver in each application that has opened it. You can usually do this by opening the applications MIDI devices dialog (MIDI-OX and Cakewalk each have these), unselecting the MIDI Yoke port, and Press OK. The driver is now closed. Now do the same in the other application (if there's more than one application). Next figure out how you want the driver to be routed (avoiding feedback scenarios). Open the MIDI devices dialog and reselect the MIDI Yoke driver. Press OK. Do the same in the second application. The driver should now be re-enabled and operational.

You can use MIDI Yoke to communicate between applications by having then share a single MIDI Yoke port. The first application (the Master) opens a MIDI Yoke port as an Output port, the second application (the Slave) opens the same numbered MIDI Yoke port as an Input port. With this configuration, MIDI data (and System Exclusive) is passed in one direction from Master to Slave. The Master might be Cakewalk or Cubase or MIDI-OX. The Slave might be Rebirth or Cakewalk or MIDI-OX: it depends on what you want to do.


MIDI Connections

MIDI Yoke is normally used to connect two applications together. The first application will open MIDI Yoke 1 as an output port, and the 2nd application will open MIDI Yoke 1 as an input port. MIDI data will travel from the 1st applications output to the 2nd's input.

Single Client to Multi-Client: You can use MIDI-OX in conjunction with MIDI Yoke to achieve a virtual multi-client input. Launch an instance of MIDI-OX. In MIDI Devices... dialog, select the single client hardware driver as input and select MIDI Yoke 1 as output. In each application that you wish to share the driver, open MIDI Yoke 1 as input. Although I mention MIDI Yoke 1, it can be any MIDI Yoke port as long as they all use the same port number.

Multi-Client to Single Client output: The reverse scenario is a mirror image of the previous paragraph. You can use MIDI-OX in conjunction with MIDI Yoke to achieve a virtual multi-client output. Launch an instance of MIDI-OX. In MIDI Devices... dialog, select MIDI Yoke 1 driver as input and select your single client hardware port as output. In each application that you wish to share the output driver, open MIDI Yoke 1 as output. Although I mention MIDI Yoke 1, it can be any MIDI Yoke port as long as they all use the same port number.

wer sowas nicht wirklich alleine hinbekommt sollte es eh besser sein lassen..

da sind ja die nächsten 5 threads mit schwachsinnsfragen vorprogrammiert

A demonstration of my new instrument ammobox. ammobox allows you to scratch audio by triggering samples asyncronously with MIDI, the turntable provides velocity and rotation control.

What you see on the screen is me dropping MIDI notes into an Ableton Live MIDI loop, as each note is hit, it injects the sample into the stream allowing me to scratch it.

It should be noted that this is a pretty unique method in that it allows you to 'latch' sounds and hold on to them after they would have terminated due to the note-off event or the sample being over, you can then overlay samples and build up layers of them while scratching.

pad-midi-controller? Der würde mich aber interessieren!

Ich finde die Pad-Alternativen aber auch nicht gerade klein