I said "except for MIDI controllers" which, in my mind anyway, also includes pitch bend.

As far as I know, the controller and pitchbend opcodes can be used in an ordinary score-driven performance without anything bad happening. If something bad does happen in that case, we should fix it.

In other words:

If you use the command-line MIDI to pfield assignments for key number and velocity, and if you use the midi controller and pitchbend opcodes, then you can use the same instrument definitions for both score-driven and MIDI-driven performance. The note on and off stuff will work the same way in both cases. The controller and pitch bend opcodes should do nothing in the score-driven performance.

Regards,
Mike

-----Original Message-----
>From: victor 
>Sent: Jan 23, 2008 10:42 AM
>To: Michael Gogins , Developer discussions 
>Subject: Re: [Cs-dev] how to start using the cSound API
>
>What about pitchbend and controller messages?
>
>Victor
>----- Original Message ----- 
>From: "Michael Gogins" 
>To: "Developer discussions" 
>Sent: Wednesday, January 23, 2008 3:31 PM
>Subject: Re: [Cs-dev] how to start using the cSound API
>
>
>> As I said to the guys who wrote Cabel, only they didn't do it:
>>
>> PLEASE DO NOT USE THE MIDI OPCODES (except for the MIDI controllers).
>> USE THE MIDI-INTEROP COMMAND LINE FLAGS INSTEAD.
>>
>> Then your orchestra will work BOTH FOR MIDI-CONTROLLED LIVE PERFORMANCE
>> AND ALSO WITHOUT CHANGE FOR SCORE-DRIVEN NON-REAL-TIME PERFORMANCE.
>>
>> In other words, MIDI events will come in as regular pfields if you use 
>> those flags, and you can write ordinary score-drive-type instrument 
>> definitions that can work also for live performance.
>>
>> If you do this, then I can use your patcher myself, and it can be built 
>> into things like blue, and everyone will love you.
>>
>> If you use the MIDI input opcodes instead, I will not be able to use your 
>> work, and it will have limited use in blue or anything else.
>>
>> ALSO, your work will be much more useful if it is a component that can be 
>> used in other applications, and not a stand-alone application itself. The 
>> way to do this is write the thing as a panel, and then write a shell 
>> application to host the panel to make your patcher into a stand-alone 
>> application.
>>
>> Good luck!
>>
>> Best,
>> Mike
>>
>>
>> -----Original Message-----
>>>From: Rory Walsh 
>>>Sent: Jan 23, 2008 7:48 AM
>>>To: Developer discussions 
>>>Subject: Re: [Cs-dev] how to start using the cSound API
>>>
>>>Sound interesting. Good luck with the wiring between opcodes. I had to
>>>do this once and it was a real pain, although I went along the route of
>>>MAX/MSP style connections that users could alter. Unfortunately I didn't
>>>do it with wxWidgets. How easy is drag and drop to implement in
>>>wxWidgets? this is all getting a little off topic.... I might email you
>>>directly..
>>>
>>>
>>>
>>>Carsten Høyer wrote:
>>>> Rory Walsh skrev:
>>>>> It should really, I keep meaning to update the code but never get 
>>>>> around
>>>>> to it.... with regards to wxWidgets have you starting building your own
>>>>> custom widgets yet? I'm working on a Csound/wxWidgets project at the
>>>>> moment, that's why I'm asking.
>>>>>
>>>> I am making a university project where i wish to create a _simple_  buzz
>>>> clone (reaktor) with drag/drop from a treectrl. I know its been made
>>>> before (like Cable: http://cabel.sourceforge.net/screenshots.html), and
>>>> really the points/grades in this project is not about csound/wxwidgets
>>>> but more the algorithm to control the wires between opcodes. I´m
>>>> thinking of using some derived Dijkstras shortest path, and make the
>>>> wires angled (that is, not straight like in reaktor). I got a long way
>>>> to go :)
>>>>
>>>> Carsten
>>>>
>>>> -------------------------------------------------------------------------
>>>> This SF.net email is sponsored by: Microsoft
>>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>-------------------------------------------------------------------------
>>>This SF.net email is sponsored by: Microsoft
>>>Defy all challenges. Microsoft(R) Visual Studio 2008.
>>>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>_______________________________________________
>>>Csound-devel mailing list
>>>Csound-devel@lists.sourceforge.net
>>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
http