hashtags/lmms
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 1 Wiki Activity

ZynAddSubFX: forward MidiControlChange events to ZynAddSubFX core

Browse Source 
So far we ignored all events other than MidiNoteOn, MidiNoteOff and
MidiPitchBend. By also processing MidiControlChange events one can
control some basic parameters of ZynAddSubFX via MIDI now.
(cherry picked from commit 49ebb835af)
This commit is contained in:
Tobias Doerffel
2009-08-18 01:29:10 +02:00
parent c355d71716
commit c46c4ff3d1
1 changed files with 12 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
plugins/zynaddsubfx/remote_zynaddsubfx.cpp
View File

@@ -138,8 +138,10 @@ public:
// all functions are called while master->mutex is held
virtual void processMidiEvent( const midiEvent & _e,
const f_cnt_t /* _offset */ )
{
const f_cnt_t /* _offset */ )
{
static MidiIn midiIn;
switch( _e.m_type )
{
case MidiNoteOn:
@@ -174,6 +176,11 @@ public:
_e.m_data.m_param[0] +
_e.m_data.m_param[1]*128-8192 );
break;
case MidiControlChange:
master->SetController( 0,
midiIn.getcontroller( _e.m_data.m_param[0] ),
_e.m_data.m_param[1] );
break;
default:
break;
}
@@ -356,11 +363,11 @@ int main( int _argc, char * * _argv )
remotePluginClient::message m;
while( ( m = __remote_zasf->receiveMessage() ).id != IdQuit )
{
{
pthread_mutex_lock( &master->mutex );
__remote_zasf->processMessage( m );
__remote_zasf->processMessage( m );
pthread_mutex_unlock( &master->mutex );
}
}
__exit = 1;