Hi everyone. Lots of reading hear so your choice to read or have musical fun instead. I did say that I would have some information for you today and here it is.
Ok. Acting on Lacko’s great suggestion, I managed to set up a number of testing
Scenarios to see how this keyboard software reacts to them and hoping that maybe it could generate some kind of meaning error message which can be helpful in zeroing on perhaps the software logic area of the search instruction(s).
TEST #1
1. As you know had restored and customized my keyboard after the last rest.
2. Now I deleted everything in my USER area which was quick seconds in fact
3. Loaded my Live USB1 with all my files and did a “Select All” delete on the keyboard. Execution
time was 19 minutes for the delete. BTW did this multiple times and the execution time was
very consistent. And a power off was performed every time as well.
4. Disconnected the USB and connected a small 4gb 2.0 USB formatted on the keyboard of
course, then same with a 3.0 32gb and a 3.1 64gb USB, all with only three styles, three
midi,
three voices, three pads and three registration. Note that each USB had an error check
performed on them as well as all the USBs used for any of my previous tests. This is a good
practice to do all the time for any USB to ensure that they are always in good status.
5. Performed a search and non were retrieved. The old list kept coming up.
6. Disconnected the USB and got nothing popping up on the screen.
7. Appears that there is logic which first acknowledges the external device status and then reverts
to the storage list from the last refresh load.
8. So, no device loaded, the program does not do a Fetch to the stored list.
9. I plug the USB back in and is connected as USB1 and the list is populated on the screen again.
10. Yamaha how much more obvious can it be to find this area of code and work on this
logic?
??
TEST #2
The next testing scenario was to Factory Rest. Did it 10 times for the heck of it as I had nothing better to do right? Testing out the logic consistency of this Factory Reset.
1. Powered off the keyboard. Even added a soft reset to the mix.
2. Performed the same testing sequence as described in points #4,5,6,9
3. Results were the same.
Next test was to take the clone of the the USB which had everything deleted in point #3 of my first test, populate it back to what it was by using the keyboard to do the copy from USB1(loaded clone) to USB2 empty formatted one. So using my keyboard to do a PC copy like function I would expect some kind of an error message if there was something wrong with a folder, file or even the USB. This is a data and external integrity check as well. Nope all copied well in 65 minutes of execution. So good there.
1. Powered off the keyboard
2. Did a soft reset
3. Inserted the newly populated USB and connected fine as USB1
4. Tapped on the screen USB1 so the keyboard would read It and it did as it went through it’s
“checking” process. All was normal there.
5. Did a search for a name and the old list keeps popping up and like before the whole list of 10
pages of styles in this case along with the max limit message populate my screen.
6. NOW, I start selecting the styles on the list and while some have redundant entries, I select
each one to see if I get the famous message related to fine file name not found, or filename is
inappropriate or the other one No USB flash drive is connected.
7. When I get to the one that does load, I DELETE it to a point that I deleted everything on my
list, all 100 entries
8. Entries were in fact deleted from the USB folders but the entry names on the list still remained.
9. This time if I try to select the name that was deleted it says no USB flash drive is connected.
So tells me that the actual search function is still working. Just using the old list which it
should not.
10. Note that my Registration folders all except one had 10-165 entries. Only one had 284. Style
folders are the only ones with hundreds of files in folders and those I got from the forum
populated with many files in folders and folders within folders. .
OBSERVATION:
During my last test, I did note some strange and interesting things.
1. Those redundant entries are there because them came from a different USB connected to the
keyboard with the same path name.
2. One of those in fact was never connected at the same time when I connected multiple USBs, so
it’s not in issue related to multiple USBs at this time from what I can deduce.
3. When I connected one of the 4 USBs that I have used, and select one of those redundant
entries that I spoke of previously, as soon as I connected the keyboard registered on
the list, it actually found the style in my case and brought me to the folder and page containing
the file and ready to play the style which it did.
4. Note that the keyboard recognized this USB connection as USB1.
5. Went through the deletion process again like I did before for everything on all my 4 USBs that
the keyboard did find and the end result was always the same.
6. So, no mater what I do that list can not be cleared, the list does have good data that can be
retrieved and utilized.
Conclusion :
1. My USBs with my data is good
2. Don’t have anything on there that the keyboard got upset with as it read, played and even
moved things around from USER to multiple USB storage
3. Connected 4 USBs at one time and everything was all usable as normal
4. Don’t suspect data corruption in the Internal Storage Memory where this list is residing
because if anything there was corrupted I could not have been able to select and load up the
styles or Registration
5. Note that each file type has it’s own list so there has to be some partitioning in this memory,
but somehow the brick wall limit is NOT affecting the VOICE, PAD, MINI or Audio
regardless of where the files reside, Expansion, User or USB. Very Very Interesting.
6. I did have issues before with all my searches and now it’s only STYLES and REGITS. So
something good has happened so far. Not sure what or why?
7. Also for those of you that use separate USBs for let's say Styles to keep things to a minimum I
would be curious to know what your results are if you put a style for example, call it Dom.sty
on say 2 or 3 of your USBs. Play it each time. Do a search and see if it works. Then Power
off/on the keyboard, however this time ensure that NO USB is connected. Then go into your
style function and search for Dom. See how many entries are on your list. I am assuming that
the list would contain multiple Dom styles(speculating again). And the only way to play them
would be to connect the respective USB for each separate Dom entry in your this. Only for
SX700. I don't want any other instrument because the SX900 and up although it is said that
the operating system is the same, to me it's NOT. SX900 has Chord Looper so obviously the
software logic can be different. Maybe the seach could be the same, don't know. This info will
help level set some things in my mind. Thanks in advance.
For those of you who do not understand why some programs can go flaky and why it can be a point of reluctance for that software to be fixed, keep this in mind.
1. If you write a program from scratch you will then see the whole picture and be able to build and
repair very easily. Generally the programs are not very big at the time of creation.
2. Now you want to add some additional controls or functionality to that program and it grows in
size, like writing a book.
3. During the evolution of this program you need to engage others to take what is existing and
add/append some new controls or functionality and this comes in the form of add program logic
code.
4. As the program grows and starts to become a monster size, there are many people/programmers
all doing their little part to help it evolve while integrating things as seamless as possible.
5. While this adds many layers of complexity in reality, each control and functionality can still for
the most part be identified and isolate. At that point you just dump that section of the program
logic using specialized tools(can be proprietary tools-Yamaha internal diagnostic software) and
put a fix which is generally some program lines of code, and once in place, you have your new
upgrade version.
6. For this reason I can't understand why Yamaha knows about this issue and can't just address it.
Not expensive as one would think in the scheme of things. I don't think I am in left field on this one.
Not sure what else to test. Been at it all day with many factory resets, and finally got this thing restored to how I want again.
All I have for you now. Hope that I have not confused anyone as my head is spinning on this subject.
My last comment is to YAMANA to step up to the plate and review how their software logic does the
"FETCH", "LOAD" and "STORE" of the data in this storage location. IT'S SIMPLE GUYS!!!!!!!!!!!!
Dom