Does Arp Odyssei have a tuning problem?

db909

One of the reviews describes an oscillator being permanently out of tune and you have to adjust it by cents to get it right. Is this true or has it been fixed? Been thinking about picking it up, but that seems annoying. Thoughts?

srcer

Link to review?

jrjulius

I assumed it was modelled drift like the Model 15 has but yes, the Init patch has a nice chorusing effect due to a subtle Osc2 detune. It's rare/impossible for analogue oscillators to stay perfectly in tune so I consider the detune "authentic," but if it bothers you, the sync control removes all chorusing/beating.

hacked_to_pieces

@srcer said:
Link to review?

http://musicappblog.com/arp-odyssei-update/

Somebody in the comment section is alluding to the tuning issue. There's also a thread on the korg forum
about the tuning issue with very few post.

I can't hear it, if you use the init patch and play the keys they are in tune with each other . When I check the tuning with the tunable app every thing is in tune.. When I play chords in another app and notes in Arp they are in tune.

Plus have not heard @Samu mention it .

[Deleted User]

Yes there is some issues. Now I'm not quite sure if it's tuning itself, or the relative values of the tuning sliders being off at times.

db909

@hacked_to_pieces thanks that's what I wanted to know

[Deleted User]

@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

hacked_to_pieces

@Fruitbat1919 said:
@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

I'm able to reset to 0 but its not easy and takes several attempts and extreme concentration and patiences. I trying it on my iPhone 6s may be easier on the iPad. Seems like they need to implement a tap to reset to default setting or allow numeric entry.

FRibeiro

I've noticed this and it's really a bit annoying. I have an Odyssey reissue and had an original MkII in the past. Oscillator 2 on the new Odyssey is far more "in tune" with the keyboard than the on the app, if you compare. The problem seems to be Keyboard Tracking for Oscillator 2, which is too "stretched". On the new Odyssey, both oscillators are well tunded to the keyboard on all regions. My old MkII had some of those issues, but not as "stretched" like on the app neither. Yes, Korg should take a look at this.

hacked_to_pieces

Here's the post on the korg forum
http://www.korgforums.com/forum/phpBB2/viewtopic.php?t=107005&start=0&postdays=0&postorder=asc&highlight=

[Deleted User]

@hacked_to_pieces said:

@Fruitbat1919 said:
@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

I'm able to reset to 0 but its not easy and takes several attempts and extreme concentration and patiences. I trying it on my iPhone 6s may be easier on the iPad. Seems like they need to implement a tap to reset to default setting or allow numeric entry.

I can't reset to 0 on the full app on my iPad no matter how long I try.

hacked_to_pieces

@Fruitbat1919 said:

@hacked_to_pieces said:

@Fruitbat1919 said:
@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

I'm able to reset to 0 but its not easy and takes several attempts and extreme concentration and patiences. I trying it on my iPhone 6s may be easier on the iPad. Seems like they need to implement a tap to reset to default setting or allow numeric entry.

I can't reset to 0 on the full app on my iPad no matter how long I try.

It took me about 3 or 4 min it's really hard plus I may have just gotten lucky.

[Deleted User]

@hacked_to_pieces said:

@Fruitbat1919 said:

@hacked_to_pieces said:

@Fruitbat1919 said:
@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

I'm able to reset to 0 but its not easy and takes several attempts and extreme concentration and patiences. I trying it on my iPhone 6s may be easier on the iPad. Seems like they need to implement a tap to reset to default setting or allow numeric entry.

I can't reset to 0 on the full app on my iPad no matter how long I try.

It took me about 3 or 4 min it's really hard plus I may have just gotten lucky.

Are you using the stand alone app? As once you move the slider, the initial increments change.

jrjulius

Ah, seems I misunderstood what people were asking about. Resetting to zero is definitely more difficult than it needs to be. I have the same issue with iMS-20, the trick is to use as light of a touch as possible so that your finger doesn't compress against the screen. This makes finer adjustments possible and it protects against the value jumping when you lift your finger. Start from about +3 semitones and move slowly down; you should be able to find zero. It's far from perfect -- it works maybe 40% of the time for me on an iPad Mini. Korg would do well to implement some sort of two-finger fine-adjustment gesture (like Moog) or some sort of double-tap to initialize (like Moog).

FWIW I've not noticed the stretch tuning issue but I always just sync the oscillators if I don't want chorusing.

hacked_to_pieces

@Fruitbat1919 said:

@hacked_to_pieces said:

@Fruitbat1919 said:

@hacked_to_pieces said:

@Fruitbat1919 said:
@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

I'm able to reset to 0 but its not easy and takes several attempts and extreme concentration and patiences. I trying it on my iPhone 6s may be easier on the iPad. Seems like they need to implement a tap to reset to default setting or allow numeric entry.

I can't reset to 0 on the full app on my iPad no matter how long I try.

It took me about 3 or 4 min it's really hard plus I may have just gotten lucky.

Are you using the stand alone app? As once you move the slider, the initial increments change.

Yes standalone on the iPhone. ios 9.3.5

[Deleted User]

@hacked_to_pieces said:

@Fruitbat1919 said:

@hacked_to_pieces said:

@Fruitbat1919 said:

@hacked_to_pieces said:

@Fruitbat1919 said:
@db909 go to an initial program. Both course tuning sliders start at a value of 0.00. Now slide osc 2 course up to its maximum value. On sliding it down, you will find that you can no longer get the value 0.00. It's a definite bug.

I'm able to reset to 0 but its not easy and takes several attempts and extreme concentration and patiences. I trying it on my iPhone 6s may be easier on the iPad. Seems like they need to implement a tap to reset to default setting or allow numeric entry.

I can't reset to 0 on the full app on my iPad no matter how long I try.

It took me about 3 or 4 min it's really hard plus I may have just gotten lucky.

Are you using the stand alone app? As once you move the slider, the initial increments change.

Yes standalone on the iPhone. ios 9.3.5

Maybe just an iPad problem then, as once I've moved it up to full, the initial values change when sliding back down, so no way to reach 0

FRibeiro

A gentle and quick sweep up or down on sliders helps to change the value step by step, like on the iMS-20.

[Deleted User]

@FRibeiro said:
A gentle and quick sweep up or down on sliders helps to change the value step by step, like on the iMS-20.

That's great. Works here. I can't go direct to the zero value in one movement ever, but if I get it to the nearest value either side and do 'the flick', it will go to zero value. Thanks that's saved the day.

Audiohub

The tuning problem (actually a tracking problem) is a fairly serious one.
Although I haven't broken out the strobotuner to figure out just how bad things are, the two oscillators seem to be mistracking each other by about 10-15 cents per octave, both via the built-in keyboard, and via Midi. I'm not sure if either oscillator actually tracks the keyboard correctly, but they do not track together.

Play the lowest note and fine tune the two sawtooth oscillators together (turn off all the effects) then play the highest note three octaves up and the oscillators are now beating furiously against each other, and about 30 cents or more apart, which is a LOT.

Looking at the various presets I wondered why they didn't seem to show this, and I noticed that a lot of the presets just use the first oscillator, and add thickness through the effects, or use things like the spread and detune controls or pulse width modulation to mask the overall tuning discrepancy.

I've noticed that Korg hasn't responded to this here or on their own forum, so I called them this morning and was referred to their customer service email. I sent a report about this and the touchy editing and got an automated reply that they would respond in three days.

I'll post again if I get any more info on this.

db909

@Audiohub good work! Do report back if you hear anything.

oat_phipps

Yeah, i've only used it for single note sequences til now. Flipped the 8-voice poly mode on just now and yeesh. Disappointed that something that big would make it through testing.

RedSkyLullaby

@Fruitbat1919 said:

@FRibeiro said:
A gentle and quick sweep up or down on sliders helps to change the value step by step, like on the iMS-20.

That's great. Works here. I can't go direct to the zero value in one movement ever, but if I get it to the nearest value either side and do 'the flick', it will go to zero value. Thanks that's saved the day

That's been driving me nuts too. But not sure what they have against double tap to zero like almost every other music app

Audiohub

Looking at the oscillators on my strobotuner this evening, I discovered that neither oscillator accurately tracks the keyboard.

Oscillator 1 is 20 cents flat over 3 octaves, while oscillator 2 is 20 cents sharp over 3 octaves.
Maybe this was a bug introduced by the latest software update? It seems unlikely that it could pass QC and be released with a problem like this.

I keep thinking that there must be some panel setting that's causing this offset, but so far I haven't been able to find anything that makes a difference. I've got all modulation and effects off, just monitoring the sawtooth waves through an open filter.
Hopefully Korg can fix this quickly. I like the app, but don't want to put any time in programming it or recording with it until it actually plays in tune.

[Deleted User]

@RedSkyLullaby said:

@Fruitbat1919 said:

@FRibeiro said:
A gentle and quick sweep up or down on sliders helps to change the value step by step, like on the iMS-20.

That's great. Works here. I can't go direct to the zero value in one movement ever, but if I get it to the nearest value either side and do 'the flick', it will go to zero value. Thanks that's saved the day

That's been driving me nuts too. But not sure what they have against double tap to zero like almost every other music app

Yep DTTZ is such a simple yet brilliant concept . They surely must know about it?

id_23

That is a big bug so let's hope for a fix in the next update!!!
On a related but slightly OT note, back in the 80's I played a couple of notes on an original Korg MS20 in a band...(spacey noises and washes etc...!) But the synth drove the guitarists and bass player crazy as it's tuning changed the warmer the synth got!

u0421793

Update has arrived, tuning has had attention.

kobamoto

@u0421793 said:
Update has arrived, tuning has had attention.

meaning that it's fixed?

ExAsperis99

So the update claims.

Audiohub

And it's true.
In settings, there is now two selections for tuning behavior...the previous one with neither oscillator tracking the keyboard correctly, now labeled "Analog" and a new one where both oscillators correctly track the keyboard in tune labelled "Equal". A huge improvement!

There's no apparent change in the tuning sensitivity of the various sliders in this update...hopefully this will happen in the next one.

AndyPlankton

This setting has not helped me, my playing still sounds just as bad

[Deleted User]

@AndyPlankton said:
This setting has not helped me, my playing still sounds just as bad

Mine sounds worse