No problem.This is exactly what I needed to know
I hope my reply didn't come across as that maligned RTFM (read the FINE manual?). I posted the link to the doc and references to the block diagram so that people other than you can find all of that info for themselves.
It certainly wasn't meant to suggest that you, or others, could have found the answer just by reading the manual. That usually isn't the case anyway.
But my feeling is that providing a link to the doc, and section, where the info lives serves people better in the long run that may not have downloaded the docs yet.
Thank you for saying this!
So I hadn't yet checked whether you intended that meaning because I got an actual answer I could use.
I actually did take your comment as an RTFM and I suppressed my reactionary urge to point out that Yamaha's documentation has rarely been helpful with the details you need to avoid disaster or figure out what is really going on. There's a very real (non personal) issue here. This documentation, like most other technical documentation, seems to be intended as a reference and not a tutorial. I've learned over the years that reference manuals are hard for the average person to read and then infer what to do.
The issue I (and I suspect many others) have is that we need two things:
a) A good in-depth tutorial AND
b) A "best practices" document that also explains why the best practices are best practices. (e.g. you use two usb sticks to backup because your chances of data corruption are that much less)
The most common issue I've had with synth OSes is that I don't initially know what the best way to do something is. So I forge ahead, and write like 20 patches only to realize that what I did needs to all be redone because of some issue. Then I give up and move to something else. I'd love that to change somehow.
Statistics: Posted by mightyd — Wed Jan 10, 2024 5:08 am