Digging into YEM data handling – looking to connect with like minds

[alexandrub]

Hi all,

Over the past months, I've been closely examining how content is prepared and managed for Yamaha arranger keyboards using YEM.

I've managed to uncover quite a bit about how certain pieces are structured and how the overall system works behind the scenes — nothing too fancy, but enough to feel that I'm on the right track.
Interestingly, during this process, I noticed that the tool seems to contain several helpful capabilities that aren't exposed through the normal interface. These hidden or disabled features could greatly streamline the creative workflow, but unfortunately, they seem hidden, but not unusable — making content creation more time-consuming than it arguably needs to be.
I'm now at a point where exchanging thoughts with others who've gone down a similar rabbit hole would be really helpful. To be clear: I fully respect Yamaha's work and this community's rules. My intent is purely technical and educational. Anything discussed or shared would remain private and nondisclosed — out of respect for both Yamaha and those involved. It's important to me that we keep this safe and constructive for everyone.
I'm aware that some users — possibly even members of this forum — have managed to push beyond the standard boundaries of what's possible, with things like user-defined Guests are not allowed to view links. In order to access the links, please Register or Login voices, CPF decrypting and more. That gives me hope that I'm not the only one exploring this area from a technical perspective.
If you've spent time analyzing how content flows into the instruments or how this tool packages things, feel free to drop a message or reply. Would love to share notes and compare perspectives.

Thanks!

[BogdanH]

hi alexandrub,
I think that we have one thing in common: curiosity 
I welcome your initiative, but...

...
My intent is purely technical and educational. Anything discussed or shared would remain private and nondisclosed — out of respect for both Yamaha and those involved. It's important to me that we keep this safe and constructive for everyone.
...

How it can be constructive for everyone, if it's private and non-disclosed? In my opinion,  knowledge can be called private (a secret) only as long only one person has it -otherwise it will sooner or later become a "public secret"... or simply public knowledge.

I can understand "technical and educational" intentions (copyright fear, I assume). But in my opinion, if gathered knowledge isn't shared or made use of it, then I see very little motivation.
For example, if you find out how to create Guests are not allowed to view links. In order to access the links, please Register or Login voices, why wouldn't you share that knowledge?

I'm just thinking aloud here... wish you a lot of fun 

Greetings, Bogdan