lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #4745 Add


From: Auto mailings of changes to Lily Issues
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #4745 Add Staff.midiCC context property, refactor handling of MIDI control changes
Date: Wed, 16 Mar 2016 21:30:55 +0000

In a few days, master should have reached the state where something like
\override Staff.MidiCC.7 = #100
would become possible for setting a MidiCC alist. I could see how to fudge something similar into \set in general (likely without the revert and property combining machinery of grob properties), or make the Performer_group pass along actual override/revert commands.

However, I consider it prudent to not use this as the user interface since it does not lend itself to continuous change of the continuous controllers. So if we decide to make this roll via context properties, we still should provide some wrapper commands as user interface.


[issues:#4745] Add Staff.midiCC context property, refactor handling of MIDI control changes

Status: Started
Created: Sat Jan 16, 2016 06:01 PM UTC by H T LilyPond
Last Updated: Tue Feb 02, 2016 07:58 PM UTC
Owner: H T LilyPond

Add Staff.midiCC context property, refactor handling of MIDI control changes

Setting the Staff.midiCC context property to a list of (control number,
control value) pairs, where every control number and control value must
be an integer between the inclusive range from 0 to 127, will send the
corresponding raw control changes to the MIDI output on the MIDI channel
associated with the current context. For example,
\set Staff.midiCC = #'((7 . 100)) will set the MIDI volume control (#7)
to 100.

Most of the logic for handling MIDI control value initialization from
context properties (in Staff_performer::new_audio_staff),
changes (in
Midi_control_function_performer::announce_function_value_change), and
value conversion for output (in
Midi_control_function_value_change::to_string), was moved into the new
Midi_control_change_announcer class. All MIDI control changes are now
encoded using {Audio,Midi}_control_change items. This change makes the
old {Audio,Midi}_control_function_value_change classes obsolete.

http://codereview.appspot.com/284280043


Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

reply via email to

[Prev in Thread] Current Thread [Next in Thread]