Hi Alex,

I would like to comments on this. However, first I would like to say that I understand, why you are frustrated and upset, beacuse you can't use the instrument in the way you had anticipated. I think that everyone understands this - including Diki and myself. And I want to say two thing about is:

1. The "New functionality forum board" on the G-70 user club website is dedicated to address such wishes for new functionality. If you in that forum board state, why you need this feature, then you can be sure that Roland will get the information. I hope - for you and others, who suffer from this - that your arguments are so significant that Roland sees no choice but to implement the feature.

2. Nothing can change the fact that Roland has not promised us that we could save the Keyboard mode in the OTS registrations. The manual says nothing about this! Therefore we can't really blame Roland for it... my neighbour just bought a new car. It has 6 gears. I went for a test drive earlier today. It a really nice car Let's say that I went out tomorrow to buy myself a new car too and I realized - after taking it home - that it only had five gears - would that be a "bug"? Well, that would depend on what the car salesman have told me, wouldn't it? My point is that you and the rest of us were not promised that the G-70 would have 6 gears.... I mean....!?! follow me?

Now, this lead me to my comment: During the dialogue about this issue you have several times called the issue a bug, and you seem to have insisted on that - until in your latest post, where you surprisingly write "I don't care whether it is called a bug, a design flaw, "product anomaly" or any other name". Now that is surprising to me (especially taken into consideration that you work with computer software), beacuse to me it is of essential importance, what we call the observations. It is only a bug, if you discover something that run counter to the manual! I work myself as a manager in one of the worlds largest software companies. My employees respond to incidents from the end users every day! The first thing our 1st level service desk personel determines, when a new incident is received is, whether the incident in question runs counter to the manual of the product that they support. Only if they can answer "yes" to that question they can register the incident as a bug! So this is of significant importance! A bug can cost the company thousands or even millions of dollars! In the case of Roland the situation is of no difference. If a severe bug is found, then Roland needs to fix it. And thats can be pretty expensive! Just look at the OS2.01 for the Roland G-70 - it's a perfect example... That OS update came out only because the G-70 user club members found a really severe bug (all LED turned out while playing midi files) after the release of OS2 to G-70. After we told Roland that this bug existed, Roland quickly fixed the bug and released the OS2.01, which had to be sent out to every Roland customer and every Roland dealer in the world.... think about that! Can you see the dollar signs? So my point is that bugs (especially severe bugs) are something you dislike, when you are in the business of producing e.g. electronic instruments like the G-70

A consequence of this is: when we in the G-70 user club community observe something that looks strange, we always call it "an observation", and after that we thorougly examine, whether they observation is a bug, a design flaw or whatever. We typically have a dialogue with Roland before categorizing the observation to be sure. On the G-70 user club website we have a database containing bugs in the G-70 found by the user club members. So you see - I certainly do care, whether you find a bug or not!

Good luck with your G-70!

/Søren

[This message has been edited by weissefar (edited 08-05-2006).]