Korg Forums

Hi,
Today I was just playing with Program USER-D 005 Peanut Lead, Korg Polysix Exi and pressing the switches on the control surface rapidly to see which switch was assigned to the switches on the GUI and it completely froze the keyboard.

I'm begining to think that the OASYS O/S is starting to become the Microsoft Windows 3.1 of the synth world. It's really fustrating, I mean can't Korg release a stable version of the OASYS O/S?

Elvis Dowson

Hi
I was thinking the same thing myself regarding the MS comparison. However, we should remember that this is the first synth of this type by any of the main synth manufacturers and i guess its only to be expected that bugs are going to exist with so much code being writen for the various parts of this synth and getting it all to run smoothly.

I'm not going to vote on this poll ( pzl note I'm not having a shot at you ) -i think the best thing we can do is take a pad and paper to the synth and write down any issues and report them to Korg. I'm sure this is what helped MicroSoft move along and get to Vista ( which i believe still has bugs?? MS is over 20yrs in the making isnt it? Remember the O s/w develpment has just started so to speak ). Oasys clients need to report back to the developers. Software developers are just people - there will always be errors. Repairs cant be made over night.



Billy

I couldn't vote even if I wanted to really; I'm learning fast but am still only using like 5% of this machine currently. I have not experienced any freezes or unexpected behaviour so far.

Although I had the luck that a Korg engineer upgraded the machine before I bought it So that mustve gone the way it should.

Perhaps the further I delve into the deeper ranges of the O that some bugs might appear; but as billysynth1 already said: something without bugs is practically non-existant and it's a process of sorts to get the less hidden bugs out. I'm confident this will all go smoothly for the O.

Brad

elvisjohndowson wrote:Hi,
to see which switch was assigned to the switches on the GUI and it completely froze the keyboard.

I also had same kind of freezing on Oasys, a couple of times: " pressing the switches on the control surface rapidly"......and then freeze...........
Frankly speaking I tried to replicate it, unsuccessfully
- may be I did not remember well the sequence of the operations
- may be I made it too slow.......
- may be I made something "veeeeeeeery wrong"

Stating what's above I cannot call it a bug or even an erratic behaviour of oasys OS.

........mmmmmmmmh thinking about my erratic behavior.......

While some are experiencing genuine difficulties which are no doubt very frustrating (and I personally ave had no such difficulties but confess to not digging as deep in to OASYS as others), it's probably fair to say that overall OASYS is a very stable machine. It really does operate very well, over all.

When you factor in the specific nature of the beast and the relatively small number of users and developers, I think it fairs remarkably well. I remember reading somewhere that there's some sort of bug in one of every ten lines of code. I don't know if that is actually the case, but having worked as a developer (a very average one I can tell you), it became very clear just how 'human' computer code is. The logic is only as good as the design process and those doing the coding. Anyway, while your poll may reveal a genuine issue, I'd suggest that if you poll any software product you'll find a similar, if not worse, scenario. But - to suggest that the OASYS OS is akin to Windows 3.1 is surely pushing the point?

(At least Windows for Workgroups surely? )

Kevin.

Excuse my probably stupid question: what is your quest?
And probably most important: what is your favorite color?

tonybanks wrote:I also had same kind of freezing on Oasys, a couple of times: " pressing the switches on the control surface rapidly"......and then freeze...........
Frankly speaking I tried to replicate it, unsuccessfully

Here are the steps for reproducing the freeze.

1. Select Program User-D 005:Peanut Lead, click on the EXi to bring the Main GUI edit screen (Program P4: Polysix Main).

2. Click on the Tone Adjust switch. Play something on the keyboard and simultaneously start pressing the first five switches on the left side, both rows (i.e. Mix Play/Mute, Karma Scenes 1 to 5 and Mix Select, Karma Switches 1 to 5) and rapidly keep pressing these two rows of switches at random. While doing this, stop playing the keyboard and start playing with the touchscreen and select some of the knobs on the touchscreen. For me, it freezes eventually when I select the Resonance knob on the touch screen.

At the end of these two steps, the entire OASYS's control surface has frozen. However, you can still play the keyboard and the program will still sound. And, after this, you'll have to reset the keyboard to bring it back to normal.

Well, for some reason, I see to end up uncovering bugs by accident. Some just straight forward freezes and some implementation flaws, e.g. like the fact that on the OASYS that a sample set to +12db gain, when used as part of a drum kit loses the +12db setting and gets played at 0db.

No need to attack me on this point. I'm calling it as I see it. My Triton Classic has never frozen on me in the 7 years or so that I've had it. You'd expect a keyboard to be rock steady and stable in its operation and don't want to end up rebooting it each time during a freeze during a live performance now, would you.

I am a staunch supporter of Korg and what they do and what they believe in. But I really wish that their test effort is as rigorous as their development effort.

Anyway, it's comforting to know that most people don't seem to be facing this issue and percieve the OS1.3.0 release as being stable. It's good to hear what other think and are experiencing, and hence the poll.

bo.h wrote:Excuse my probably stupid question: what is your quest?
And probably most important: what is your favorite color?

Turquoise. What can you infer from that answer?

You must be searching for the holy grail

I never had any problem with the oasys till 1.2x OS.

Now my oasys freezes on regular base. Switching between patches and pressing buttons ends up in freeze.

Many freezes can not be traced why it freezes, sometimes when i switch banks quickly and move to a new patch quickly ( rapidly pressing buttons ) the system already freezes. It look like every function takes more time to be done then with the earlier OS.



I do not understand what beta testers have been doing while testing this new OS version.

For me 1.3 is the most badly update, and next time with a new 1.4 os i will not install it when it comes available.

Now i still hope there comes an new 1.3

bo.h wrote:You must be searching for the holy grail

Hahaha, that's a good one! Aptly put !!

Hey Paul,

paulifra wrote:I do not understand what beta testers have been doing while testing this new OS version.

I don't know if you remember my early experiences with the Oasys, but I used to be plagued with freezes and became quite upset with it. So you have my sympathies for sure. Also you can imagine that when I was testing, this was something I was very sensitive to; however my Oasys running 1.3 is actually very stable. There is something else going on here, something I can't put my finger on it, it's something more complex.

Daz.

All i want now is a korg publication on how to recover an oasys system to a state as delivered when i bought it.

i only can read messages do not install an older OS system, do not this do not that.

But when i get constantly freezes what do to in such a situation.

My oasys and its harddisk are in retail status, i never saved anything to the harddisk. Update in all situations from a bootable cd's in the cd rom player.

I am absolutely sure i did nothing wrong, just doing the procedure for updating, now i have problems.

For me i wanted to prefer the 1.2x situation.

Where can i find the information to fully rebuild my system from scratch ?, in the exactly order of all handling to do

You can add my Oasys 76 to this list. Ever since I updated to OS 1.3, just a week ago it has frozen on me four times, twice when I used the control surface, and twice when I wrote combinations to memory. My only choice is to reboot the Oasys. It never did that pm earlier OS versions.