Login / Register  0 items | $0.00 New#KVRDeals

Which CC is the source here?

User avatar
EvilDragon
KVRAF
 
15117 posts since 6 Jan, 2009, from Croatia

Postby EvilDragon; Sun May 21, 2017 1:07 pm Which CC is the source here?

Image

As you can see, it's impossible to know which CC is the source for a modulation slot until you click on the menu. I recommend using a shorter name without any words (just CC #xyz will suffice)!

Thanks :)
elcallio
KVRian
 
1287 posts since 27 May, 2005, from Stockholm

Postby elcallio; Sun May 21, 2017 3:49 pm Re: Which CC is the source here?

Suggestion noted. Not sure whether it will make it into the 2.x series.
TX16Wx Software Sampler:
http://www.tx16wx.com/
User avatar
EvilDragon
KVRAF
 
15117 posts since 6 Jan, 2009, from Croatia

Postby EvilDragon; Sun May 21, 2017 11:33 pm Re: Which CC is the source here?

It looks like all that's needed is replacing some strings, which is like a one minute thing to do? :)
elcallio
KVRian
 
1287 posts since 27 May, 2005, from Stockholm

Postby elcallio; Mon May 22, 2017 12:41 am Re: Which CC is the source here?

Well, it needs to render differently in the menu and the box, and then I need to make sure I don't screw up the parser/saver strings (which are almost, but not exactly what you see in the interface). So seemingly trivial, but with screwup-potential. And I'm lazy. And you can use the extra clicking to check. Or learn to use low-numbered (short names) midi controls. :-) I can go all day. :-D
TX16Wx Software Sampler:
http://www.tx16wx.com/
User avatar
EvilDragon
KVRAF
 
15117 posts since 6 Jan, 2009, from Croatia

Postby EvilDragon; Mon May 22, 2017 12:53 am Re: Which CC is the source here?

elcallio wrote:And I'm lazy. And you can use the extra clicking to check. Or learn to use low-numbered (short names) midi controls. :-) I can go all day. :-D


Those are not really good arguments when good UI/UX is concerned. But hey, it's your call - I just reported an issue that seemed like an easy enough fix. :) I can understand the screwup potential, but you're a good programmer ;)

In fact, I don't think that showing the General MIDI names of CCs is of any help in a product that doesn't HAVE to conform to General MIDI at all, which is where TX16Wx falls, IMHO.
elcallio
KVRian
 
1287 posts since 27 May, 2005, from Stockholm

Postby elcallio; Mon May 22, 2017 1:36 am Re: Which CC is the source here?

Midi CC names have nothing to do with General Midi (or any other officer). General Midi is a sound layout standard for playback of Midi files with semi-similar sound across devices, created at ~1986 or so. The Midi CC names are canonical names for the control usage assignments as defined in the original standard, existing to ensure interoperability between devices such as pedals and dial controllers vs. synths from different manufacturers (i.e. sustain on/off is always sustain, etc, and the external device/sequencer/synth all agree). While the names might be of less importance nowadays, with everything assignable anyway, for old shaggy people like me it still feels like a big deal. :-)

My point is that while I agree that the "Midi Continuous Controller #123" names are way to long (these are the unnamed controllers btw), I really like having canonical names when available. So there is the issue of consistency also.
TX16Wx Software Sampler:
http://www.tx16wx.com/
User avatar
Michael L
KVRAF
 
1827 posts since 25 Jan, 2014, from the End of the World as we Knowit

Postby Michael L; Sun Jun 04, 2017 4:12 am Re: Which CC is the source here?

On another midi topic, how can I use a modwheel to dynamically crossfade between layers in the x- or y-axis in the wave matrix, or to control group cross-fading?
"As the artist goes deeper into his own thing, he learns what works and then needs fewer tools."

Moderator: elcallio

Return to CWITEC