Page 3 of 4

Posted: Mon Oct 15, 2007 12:38 am
by KSR80
I too loaded the official 1.3 into my until now perfect Oasys. I have never had a freeze or a hic cup of any kind on my baby, but now it is unplayable.

I have reburnt the iso onto a new disk three times on two different writers and still the problem persists like:

1. locking up for up to a minute after pressing locate in seq mode.
2. FX assings disappearing while recording.
3. Left channel out cuts out and the sound I was playing is replaced with a flat piano wave with no EG or VCA setting just like the init sound you get on an M1 when the factory's are lost.
4. Combi's have some sounds missing using Karma but if you stop Karma and restart it again the missing sounds return.
5. In program mode sound names are blank from time to time but return if you switch to combi and then back to program again.

I must admit, I am expecting Viagra popup windows to appear on the touch screen next. :)

This is in no way a "Have A Go At Korg" post. I still love my Oasys as much as I love my CS80, and that's saying something as the guy's who know who I am will know what CS80's are for me.

Does anyone else have these kind of problem too or am I doing something really really stupid here

Posted: Mon Oct 15, 2007 2:57 am
by Lou
I have tried to enjoy the 1.3 update, but it's been a struggle from day one to present. I've been from 123-1.3 and back twice.
Same problems here. The last install of 1.3 was sent to me by Korg, so I believe the image was good.

Program/Combi mode work.

Sequencer mode has rendered itself useless.
While in stand-by, after hitting the Record/Write, all is still ok, but once the Play/Stop button is pressed all hell breaks loose.

To many things wrong and no control over it. Lights that blink, Karma scenes cannot be accessed by front panels button pushes,
Karma and Latch do what they want. So for now I cannot do any recording Internally or Externally because of this.

Where to from here, back to 123? :roll:

Posted: Mon Oct 15, 2007 6:10 pm
by Lou
I feel so silly. After the 1.3 install I loaded the MOD-7 and KGE file as per the Instructions.
Since then, and having so much trouble in the sequencer, I called Korg. All he had me do was reload the Preload PCG and KCG files
and all was back to normal. The O is constantly making me feel :oops:

Thanks guys! :D

Posted: Mon Oct 15, 2007 7:05 pm
by danatkorg
KSR80 wrote:I too loaded the official 1.3 into my until now perfect Oasys. I have never had a freeze or a hic cup of any kind on my baby, but now it is unplayable.
I'm sorry to hear that you are experiencing difficulties.

Have you installed additional RAM in the OASYS? If so, you might try removing it to return to the stock 1GB, and see if the problems persist.

- Dan

Posted: Mon Oct 15, 2007 8:32 pm
by sebbytriton
danatkorg wrote:
KSR80 wrote:I too loaded the official 1.3 into my until now perfect Oasys. I have never had a freeze or a hic cup of any kind on my baby, but now it is unplayable.
I'm sorry to hear that you are experiencing difficulties.

Have you installed additional RAM in the OASYS? If so, you might try removing it to return to the stock 1GB, and see if the problems persist.

- Dan
During the boot, the memory isn't checked by the bios ?

Posted: Mon Oct 15, 2007 9:19 pm
by danatkorg
sebbytriton wrote:
danatkorg wrote:
KSR80 wrote:I too loaded the official 1.3 into my until now perfect Oasys. I have never had a freeze or a hic cup of any kind on my baby, but now it is unplayable.
I'm sorry to hear that you are experiencing difficulties.

Have you installed additional RAM in the OASYS? If so, you might try removing it to return to the stock 1GB, and see if the problems persist.

- Dan
During the boot, the memory isn't checked by the bios ?
Running a comprehensive memory check on 2 GB of RAM takes a *long* time. If we did this at startup, the gig would be over by the time the tests finished.

- Dan

Memory

Posted: Mon Oct 15, 2007 9:31 pm
by rkarlberg
"Running a comprehensive memory check on 2 GB of RAM takes a *long* time. If we did this at startup, the gig would be over by the time the tests finished."

That is a good point. How hard would it be to add a memory check utility to the Global interface?

I would also wonder how hard it would be to expand the Oasys up to 3 or 4 GB of RAM?

Posted: Mon Oct 15, 2007 9:49 pm
by Sina172
...........

Re: Memory

Posted: Mon Oct 15, 2007 10:00 pm
by danatkorg
The motherboard supports a maximum of 2GB of RAM.

Best regards,

Dan

Re: Memory

Posted: Tue Oct 16, 2007 6:01 am
by mdh
rkarlberg wrote: I would also wonder how hard it would be to expand the Oasys up to 3 or 4 GB of RAM?
As a professional geek I can tell you that's probably not a good idea. The motherboard most likely does not have sufficient L2/L3 cache to support that amount of memory; otherwise there would be no reason for Korg to impose this artificial 2Gb limit. The processor is 32-bit so it can address 4Gb max anyway.
(Apple has used 64-bit processors since 1993 or so, hence why Xserve will address 32Gb ;)

The reason the cache is important is that with a realtime OS, latencies become a huge issue. In muso terms, your sound will likely cut out or artificially delay. ie your $10k OASYS just became a pretty, and pretty expensive, paperweight on the stage.

That being said, the inside of the OASYS is laid out very well and has ample airflow so there's no particular technical reason why Korg shouldn't be able to offer every 3-5 years to upgrade the commodity parts inside while retaining backwards compatibility with the OS. Six authorized modules and an 8-way processor come Christmas sounds pretty sweet to me ;)

Re: Memory

Posted: Tue Oct 16, 2007 7:00 am
by vEddY
mdh wrote: As a professional geek I can tell you that's probably not a good idea. The motherboard most likely does not have sufficient L2/L3 cache to support that amount of memory; otherwise there would be no reason for Korg to impose this artificial 2Gb limit. The processor is 32-bit so it can address 4Gb max anyway.
(Apple has used 64-bit processors since 1993 or so, hence why Xserve will address 32Gb ;)
That being said, the inside of the OASYS is laid out very well and has ample airflow so there's no particular technical reason why Korg shouldn't be able to offer every 3-5 years to upgrade the commodity parts inside while retaining backwards compatibility with the OS. Six authorized modules and an 8-way processor come Christmas sounds pretty sweet to me ;)
In general, motherboards don't have L2/L3 cache onboard, L2/L3 cache is something CPU-related, so - again, in general - L2/L3 cache are usually on a CPU. Perhaps you spelled it wrong :-) There are motherboards with cache memory onboard, but this is something completely different. OASYS's motherboard is not one of those.

This AOPEN motherboard inside the OASYS has Intel 845GV chipset, which is the primary reason why "only" 2GB of memory are supported. Again, in 2005. when OASYS was introduced, this was a mainstream/integrated graphics best-buy chipset (and CPU, for that matter). As for the airflow, let's see what happens. This kind of service would _surely_ require Korg service support (local distributors, repair shops and stuff).

That being said, it would be hell-a-cool to have a quad-core inside, something from the lower range. Penryns are just about to come out, with lower-end models to come after New Year :-)

Cheers,
vEddY.

Re: Memory

Posted: Wed Oct 17, 2007 12:54 am
by mdh
vEddY wrote: In general, motherboards don't have L2/L3 cache onboard
True, L2 has been on-die since P2 days, some high-end server boards have added L3 but the new Xeons have L3 on-die now too. On the AMD side, they don't have L3 however their L1 and L2 caches are significantly larger which is why 1.3Ghz AMD chips outperform 3.16Ghz Intel chips in many operations :)

My point was, especially running a realtime OS, its not quite as simple as "chuck some more ram in". There's reasons why its limited to 2Gb, especially coming out of the fact its 2004/5 vintage. But these are not insurmountable issues. The underlying architecture both physically and in software supports hardware upgrades, and in a year or three when there's significant Exi's and EXf's to warrant it there's not really any technical obstruction to bring the system up to date with 2008/9 technology instead of 2004/5, without having to start from scratch with "OASYS mk2" or whatever. (have they found a way to turn "billabong" into an acronym? ;)
vEddY wrote: That being said, it would be hell-a-cool to have a quad-core inside, something from the lower range. Penryns are just about to come out, with lower-end models to come after New Year :-)
I think there needs to be a) sufficient user demand b) reasonable proof such an upgrade satisfies said user demand - and the demand must be real-world application, like the inability of the current platform to accurately execute the eight or so EXi's available by that time - not simply "hell-a-cool"
:3dcool:

Posted: Fri Oct 19, 2007 6:54 pm
by MarcOne
I have commented on this elsewhere, by since it's a poll, it seems valuable to mention it here. My upgrade went flawlessly. I am looking forward to licensing the MOD-7 too. However, OS 1.3 has introduced ocassional freezes, which it never did before. A couple of times, it froze during control surface use (which might indicate a bug), but two other times, it froze simply after saving a combi to memory. Not a good thing.

Posted: Sun Oct 21, 2007 5:56 pm
by zrapa
Upgrade from 1.2.2 (booted from the CD-ROM) was simple and successful. MOD-7 cooks!

Posted: Sun Oct 21, 2007 6:38 pm
by Lou
zrapa wrote:Upgrade from 1.2.2 (booted from the CD-ROM) was simple and successful. MOD-7 cooks!
Just curious, Do you have 2g ram and are both EXs loaded?