relpipe-data/examples-jack-midi-monitoring.xml
branchv_0
changeset 297 192b0059a6c4
parent 296 418e11eb6fea
child 313 a43265235e5a
equal deleted inserted replaced
296:418e11eb6fea 297:192b0059a6c4
    21 		<p>
    21 		<p>
    22 			We can join the JACK graph with <code>relpipe-in-jack</code> command.
    22 			We can join the JACK graph with <code>relpipe-in-jack</code> command.
    23 			It does not consume STDIN, it gets events from JACK instead, so no other input data are needed.
    23 			It does not consume STDIN, it gets events from JACK instead, so no other input data are needed.
    24 		</p>
    24 		</p>
    25 		
    25 		
    26 		<m:pre jazyk="bash">relpipe-in-jack | relpipe-out-gui</m:pre>
    26 		<m:pre jazyk="bash">relpipe-in-jack | relpipe-out-csv</m:pre>
    27 		
    27 		
    28 		<p>
    28 		<p>
    29 			We are connected to the JACK daemon now, but no data are routed to us.
    29 			We are connected to the JACK daemon now, but no data are routed to us.
    30 			So we need to direct some MIDI streams to our input:
    30 			So we need to direct some MIDI streams to our input:
    31 		</p>
    31 		</p>