#include <MIDIClocker.hxx>
You can specify a device (string), which will be used by the MIDIManager, when creating the MIDIDevice objects. When you don't specify a concrete device, or specify "default", the MIDIManager will choose the default device for your setup. For multichannel MIDI, you need to configure each in/out with it's own channel id, typically 0 for left, and 1 for right.
Definition at line 40 of file MIDIClocker.hxx.
Public Member Functions | |
DYNAMIC_TYPE_USING_INTERFACE (MIDIClockerConfig, 1, ProcessingConfig) | |
DYN_ATTRIBUTE (0, public, std::string, Device) | |
The Device that will be used by this MIDIClocker or MIDIOut instantiation, if it is not indicated, or its value is "default:default", system will choose the best device for this object. | |
Protected Member Functions | |
void | DefaultInit (void) |
The concrete dynamic type constructor calls DefaultInit(). |
CLAM::MIDIClockerConfig::DYNAMIC_TYPE_USING_INTERFACE | ( | MIDIClockerConfig | , | |
1 | , | |||
ProcessingConfig | ||||
) |
CLAM::MIDIClockerConfig::DYN_ATTRIBUTE | ( | 0 | , | |
public | , | |||
std::string | , | |||
Device | ||||
) |
The Device that will be used by this MIDIClocker or MIDIOut instantiation, if it is not indicated, or its value is "default:default", system will choose the best device for this object.
void CLAM::MIDIClockerConfig::DefaultInit | ( | void | ) | [inline, protected] |
The concrete dynamic type constructor calls DefaultInit().
This allows user to initialize his/her object. But we define DefaultInit() here because we don't want to force writting one DefaultInit() function for each concrete dynamic type. If a dynamic type concrete class defines some (not-default) constructors, this should also call the DefaultInit().
Reimplemented from CLAM::DynamicType.
Definition at line 49 of file MIDIClocker.hxx.
References CLAM::DynamicType::UpdateData().