Bug in OS V1.2.3? (AL-1)

BartVH · Post by **BartVH** » Mon Apr 02, 2007 6:01 pm

Hi everybody,

I just upgraded my Oasys from V1.1.1 to V1.2.3, and I encountered a problem.
I detected it when I heard that some of my programs were not sounding
the same anymore after the upgrade.
I just want to check if you experience the same problem as described
below:

In the AL-1 (program mode), some parameters are not working anymore.
The ones I know for sure are: Osc1 and Osc2 Pulse Width Modulation
Intensity
(I didn't check all parameters, maybe more could have this problem).
The problem occurs when you select the program. Pulse Width modulation
does not work, until you go to the Osc basic page and edit the parameter
one way or another (for instance, increase or decrease it with 1). Then
suddenly the parameter takes effect. The parameter also stops working
whenever you write the program.

You can easily check this by making a simple program:

- create a new program containing 1 AL-1
- In page 4-3 (Mixer), set volume of Osc1 to maximum and volume of
Osc2 to 0
- In page 4-1 (Osc basic) select waveform "Pulse" for Osc1
- For Osc1, set Pulse width to 50
- For Osc1, set AMS for pulse width to LFO1 and intensity to 50
- Set LFO1 frequency to 20

=> now you should hear the characteristic sound of a modulated pulse
width wave.

- Write the program and check the sound again

=> the pulse width modulation disappeared

- select another program and then go back to the program you have
saved

=> still the pulse width modulation is not there

- Go back to page 4-1 (Osc basic), and change the intensity of pulse width
AMS source with +/- 1

=> suddenly the pulse widht modulation is again present.

Looks like a serious bug to me.It means that none of the AL-1 programs,
using modulation of a pulse wave, sounds as it should.

Did anybody else detect this problem, or am I the only one?

BartVH

Daz · Post by **Daz** » Mon Apr 02, 2007 6:40 pm

You're not the only one !

Exact same thing happens here. I also went back to some of my old AL-1 programs that use PWM and those are effected too. Doh !

Daz.

Daz · Post by **Daz** » Mon Apr 02, 2007 6:46 pm

Same result with OSC2 and also when the oscillator type is Saw/Pulse. I can't believe I missed this ... d'oh !

I also tried starting from an initialized bank and that made no difference.

____

Youch, I just tried using the Double Saw osc type for OSC1 instead of Pulse. If I assign LFO1 to modulate the phase of the two saws (Intensity 50/LFO1 Speed 20) that dissapears when I save the program too.

I just don't understand how I've missed this ... scrolling through my programs a lot more of the recent ones seems to be MS20 based, but still.

Daz.

sebbytriton · Post by **sebbytriton** » Mon Apr 02, 2007 6:50 pm

1.2.X ----> Better polyphony but AL-1 bugs ?

BartVH · Post by **BartVH** » Mon Apr 02, 2007 7:02 pm

I'm glad I'm not the only one. At least this is not an esotheric bug that is only present in my Oasis

Is there a way to report bugs to Korg formally?
I would like to make sure that they include the fix for this one in the next version (V1.2.4?). Or is there some kind of patch mechanism possible?

BartVH.

Daz · Post by **Daz** » Mon Apr 02, 2007 7:10 pm

I suspect Dan and/or Brandon from Korg will most likely spot this post before the hour is over and will let us know what the story is

They're remarkably attentive.

Daz.

Daz · Post by **Daz** » Mon Apr 02, 2007 7:23 pm

Here is a workaround remove the Tone Adjust assignment from the Pulse Width AMS Intensity fields for OSC1 and OSC2 and then all is well.

Go to Play->Control Surface->TONE ADJ and set the assignment for Knob 1 and 2 to Off.

Daz.

Daz · Post by **Daz** » Mon Apr 02, 2007 7:46 pm

If you leave that Tone Adjust assignment in place and try turning Knob1 through its full range it behaves rather oddly. It's range is only 0 - 76, rather than -100 to +100 (note that TA param type is Absolute) and also it only functions between 12 o'clock and 5 o'clock. Very odd.

This problem only seems to affect this specific parameter. I cleared down the TA routing and re-assigned Knob 1 to Wave Morph AMS Intensity and that behaved fine.

Daz.

danatkorg · Post by **danatkorg** » Mon Apr 02, 2007 8:52 pm

Yup - as Daz notes, the problem is in Tone Adjust; the workaround is to remove the Tone Adjust assigments for these specific parameters. This bug has been identified, and the fix will be available in a future update. Sorry for the hassle.

- Dan

Daz · Post by **Daz** » Mon Apr 02, 2007 9:00 pm

Thanks Dan.

Daz.

p.s. thanks Bart, for providing notes on reproducing the problem.

Brandon Daniel · Post by **Brandon Daniel** » Mon Apr 02, 2007 9:38 pm

Sorry for the bug... it's a side effect of the bug reported here, and is one we'll have fixed in the next release.

In the meantime, assigning the two tone adjust controllers to a different parameter will make the problem go away.

BartVH · Post by **BartVH** » Tue Apr 03, 2007 7:40 pm

Ok, thanks for providing the workaround.

BartVH.

Daz · Post by **Daz** » Tue Apr 03, 2007 8:18 pm

You're welcome ... I was keen to find a workaround for that as you can imagine.

Daz.

rbox · Post by **rbox** » Fri Dec 14, 2007 10:49 pm

It is fixed with 1.3.1??

danatkorg · Post by **danatkorg** » Sat Dec 15, 2007 12:10 am

rbox wrote:It is fixed with 1.3.1??

This was fixed with 1.3.0.

- Dan