re-organize In and Output sections of Audio and Midi

[tjingboem]

re-organize the In and Output sections of Audio and Midi:

///Linux specific Audio & Midi /// Mac specific Audio & Midi /// Windows specific Audio & Midi///

PortAudio & PortMidi is the standard driver for all these platforms so info on it should be copied in all sections of the different platforms Link to page about Jack, that is (in principle) available for all platforms https://jackaudio.org/downloads/

[tjingboem]

• [x] separate Audio and Midi sections

• [x] section PortAudio/PortMidi for Linux, Mac, Windows

• [x] Also, add to all: With PortMIDI, DEVICE is either a number for single port input, 'a' for listening to all input ports, or 'm' for mapping ports to MIDI channels above 16. In this case, device 0 uses 1-16, device 1 uses 17-32, ... device N uses (N+1)*channel. The options 'a' and 'm' are also convenient when you don't have devices as they will not generate an error.

• [x] add list of jack midi ports to RealTimeJack page

• [x] Link on https://csound.com/manual/RealTimeJack.html to page about Jack, that is (in principle) available for all platforms https://jackaudio.org/downloads/

• [x] on the manual pages: The granularity of timing is Csound's kperiod. Isn't that true for all Midi handling opcodes of Csound? ANSWER: YES

• [x] the sample-accurate command-line option might also impact the granularity of the resolution of the midi handling in Csound. Is this true? ANSWER: NO

[tjingboem]

done

[csounder]

NiceDr. Richard BoulangerProfessorElectronic Production and DesignBerklee College of MusicOn May 31, 2024, at 2:25 AM, Menno Knevel @.***> wrote:

done — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>