Do we have a channel where we can receive news about it?
Even in beta mode, how big tech companies work. Give beta users the chance to try new deployments and give Yamaha a stronger response because of the amount of data they would get from those users.
Since we are being invited to participate in the new concept of synthesizer, it would be interesting that Yamaha also joins the new way of working on these firmware updates. Today, end-user feedback is very important and greatly speeds up the implementation process of new features as well as bug fixes.
I have followed the forum and it is very clear that Montage is an incredible synthesizer. It brought a lot of wonderful features. But it lacks some minor adjustments and implementations of some features, many of them even very simple as I see it. I'll point two for example:
* Transpose information on the screen
* KDB CTRL records on scene buttons
I really hope that Yamaha and its programmers are looking at everything that is being discussed in this forum and are looking for the best way to satisfy everyone in full!
This is the best channel. Historically, there has been little-to-no advance schedule information given for firmware releases. In keeping with your "channel" lingo: "stay tuned" (here).
Regarding the programmers and what direction they're fed - I think, perhaps, some ideas migrate from the message board to the programmers' workload. I've seen ideas I presented end up as firmware updates -- however, in most of these cases I believe it was "luck" that this happened and feel more that it took a "big fish" to happen to present the same idea and that this 3rd party's presentation is more the reason why the firmware is updated. Being able to disconnect common (global) assignable knobs is one example. If the post is still up on the forum - you can see that Yamaha scoffed at this idea (from me) - so I take it something outside had to push this through.
I do think ideas with wider appeal to make their way up the chain.
Current Yamaha Synthesizers: Montage Classic 7, Motif XF6, S90XS, MO6, EX5R
This has been discussed previously... Again KBD CTRL is a function of the KEYBOARD (transmitting), SCENEs document conditions of the TONE GENERATOR (receiving).
When making/considering a request to memorize KBD CTRL, it’s good to think about the components involved as separate devices...
Keyboard > Tone Generator
If you had a keyboard controller connected to a tone generator via a MIDI cable... (this is not a 1:1 example, but will serve as a general way to think about it theoretically) you are asking that the tone generator *store* the MIDI transmit channel of the keyboard... what a SCENE “remembers” is the settings of the tone generator. If your ultimate goal is to stop a particular tone generator Part from receiving, this accommodated in the current system by a (tone generator) MUTE.
MUTE status is documented in the Scene... it is accomplished because Scene parameters are on the tone generator side of functions.
That said, it is what must be considered. Understanding that the request is to allow the player to conveniently switch which Parts are being communicated with at any particular time. This is full of several potential problems... back to our basic two separate components, imagine hitting a chord on the keyboard, and during its sustaining portion, you disconnect the cable... what happens to held notes? what happens to sustain pedal On messages? all setting will persist in their current condition if the MW was last at 89, cc01 will remain there... could be chaos.
Okay before we get too literal, these things can probably be dealt with if we are in control of the receiving tone generator, as well as the transmitting keyboard... but what about Out via MIDI... The best most efficient way is to MUTE the tone generator. Hope that makes sense.
Can KBD CTRL be memorized in a Scene? Never say never, but since the goal of what is sounding, is easily accomplished by the tone generator MUTE... it may not.
Alternate method (Not SCENEs) to accomplish KBD CTRL status recall: How KBD CTRL is currently memorized is per Performance.
The SSS function allows you to move from one Performance to another with a minimum of disruption, when 8 or less Parts are involved. That being the case if you need to change which of KBD CTRL items are selected, you can simply transition to another Performance - the new Performance setup with the KBD CTRL you require.
The reason most items like firmware updates are not announced can vary company to company, but in the scheme of things they happen when they are ready. Rather than disappointing the waiting end user if, for whatever reason, the release is delayed, gets you nothing and does nothing for the company. Even if the delay means they can improve the firmware further, the disappointment of being late persists. “I didn’t need that feature anyway, they could have left it out” grumble, grumble.
Show me an upside to pressuring oneself to meet a deadline like that? Generally, they arrive when they get posted...
Don’t take it personally if your particular idea of what would make the keyboard (or whatever product) better, is not implemented. The process of how or if something is implemented is something not privilege to anyone outside of the design team. Anyone can speculate about how that works... I’m not on the design team, and I don’t know, so I doubt anyone posting here really “knows” either. Just FYI.
Bad Mister wrote:
This has been discussed previously... Again KBD CTRL is a function of the KEYBOARD (transmitting), SCENEs document conditions of the TONE GENERATOR (receiving).
When making/considering a request to memorize KBD CTRL, it’s good to think about the components involved as separate devices...
Keyboard > Tone Generator
Now I understand the question "kdb ctrl"! A feather! It would be a great feature and would greatly facilitate the keyboard life of the shows (like me, for example).
What can be done then is that when using scenes with MUTEs in the PARTS, this change takes effect when we release the keyboard keys. Simulating the SSS feature. That would help a lot! Because today the sound is interrupted "abruptly" and with that we do not have the ideal experience mainly for users who play with live bands.
Thank you Yamaha for fulfilling my request! Finally KDB CTRL records on scene buttons!! 😀 😀 😀
Yes, that was also my #1 request. So glad that it was fulfilled with this firmware update. Thank you Yamaha for making this happen.
Two of the ideas I had contributed on Ideascale have been realized with this firmware update: this one and the rhythm pattern addition to Montage (okay, the latter was kind of obvious because it was in the MODX already ?). Great stuff!
One thing I mentioned in the Ideascale idea for the KbdCtrl was to apply the existing sustain state to parts which newly get keyboard control when switching to a scene. Did someone check if this is the case? I cannot check right now because I am on a business trip ?. That would make this perfect!!!
Yes, that was also my #1 request. So glad that it was fulfilled with this firmware update. Thank you Yamaha for making this happen.
Two of the ideas I had contributed on Ideascale have been realized with this firmware update: this one and the rhythm pattern addition to Montage
I had also added the same idea to ideascale several months back and I'm sure there were others that wanted KBD CTRL in Scenes.
My feeling is that if enough of us add the same idea to ideascale and Up Vote these same ideas enough, they will become priority for Yamaha when choosing which features to release in the next OS update...
Yamaha are watching and listening to us. On the forum, on ideascale and other forums, such as Yamahamusicians.com!
The lack of this feature complicated my performance so much that I found a way to make the scene buttons as I wanted.
But it was a lot of work. I converted the scene button CC command to SysEx messages, where I turned the KBD CTRL I wanted on and off, and so repeat this process on all the presentations added to my setlist, it was work but still worth the benefit.
Now save this learning and use the native mode feature. 😉