Hopefully, not a dumb question. I couldn't find this in the available lit. Can the BC transmit the default values of the newly selected patch? This would be very useful for using the thing as a lighting controller or for synth programming when you want a basic synth patch to start programming ffrom. Thanks Stublito Quoting rpcfender <rpcfender@...>: >> If I'm understanding Royce correctly, you still need to correct many > of your buttons. For example -- >> >> $button 48 >> .showvalue on >> .mode incval 32 >> .default 1 >> .minmax 0 3 >> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7 ; MKS 70 Tone A DCO >> Env Mode <33,<65, <93, <127 > > adding 32 gives > Env Mode <33,<65, <97, <129 > but we can't have a data byte of 129 > Are these the correct values?? > >> >> Firstly, the command ".mode incval 32" will make values jump by 32 at > a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc. But as you've > set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33... > > Not quite > You are correct when you say ".mode incval 32" will make values jump by > 32 at a time > > .default 1 just means 'the first time this preset is selected after > power on the control will have the value 1' > After you have pressed or twisted the control the BC remembers the value > even if you change presets and come back again. > > When the BC loops back it always goes to the Min value > .minmax 0 127 > 33 > 65 > 97 > 00 > 32 > 64 > 96 > 00 > > Although it started on 1 (default) it returns to the Min value. For 1 33 > 65 97 you need... > .minmax 1 97 (I choose 97 because it tells me what the last value > is but 127 is OK) > 33 > 65 > 97 > 01 > 33 > 65 > 97 > 01 > 33 > 65 > 97 > > Is you head hurting yet?? > > >> Setting incval to jump by 32 while only having minmax's max at 3 will > not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0..., > because 3 is your max. Correct, Royce? > > Absolutely > > All the best > > Royce > >
Message
Re: [bc2000] Re: MKS-70 Sysex Script
2010-01-03 by ogusa@lava.net
Attachments
- No local attachments were found for this message.