Electribe Update 1.17

apapdop · Post by **apapdop** » Fri Oct 30, 2015 3:19 pm

Frenzies wrote:
apapdop wrote:Anybody notice anything different on the touchpad behaviour? It would be good if it quantized your first touch in line with the sequencer (I'm at work right now sans electribe)...

From first impressions though, that is one embarrassing upgrade...
Seems to be really hard to get a gate arp to play out of time on the touch pad.
Also a bit of a bigger gap between notes in a scale, maybe.

Well at least that sounds like an improvement...

thesigma · Post by **thesigma** » Fri Oct 30, 2015 3:23 pm

colulizard wrote:
Pygmy wrote:Waiting to see if the firmware hack still works with this firmware version.

It could be they just released a firmware with bullshit fixes/features like these and something to block OS switching..
Risky.... in case the firmware hack block introduces other performance issues.
I wonder how bothered they are about the hack? I'm not sure how many people this will dissuade from buying a synth and sampler? It may be that a certain proportion of people going ahead with the hack would actually never buy the two machines anyway and so just because they've hacked a machine doesn't mean Korg lost any money.
Just speculating anyway - i haven't got a clue. I've got no real urge to hack my sampler to a synth... i have enough synths anyway (hardware and software) but had no sampler.

The hack could even increase sales. People who may not have bought the sampler can get a taste. Then when they decide they'd like the capabilities of both at the same time in a song, they'll pick up a sampler, or a second synth and hack it......

Then there will still be people like me who aren't interested in its current state, and this update sadly hasn't changed that, not that I expected it to.

Automageddon · Post by **Automageddon** » Fri Oct 30, 2015 3:29 pm

I tried the hack and was not worth the hassle, but I've had so much fun with the ES2 that I might sell the E2 to buy one...

Philternaut · Post by **Philternaut** » Fri Oct 30, 2015 3:45 pm

In my brief time since updating to v1.17: The XY pad seems to require a firmer touch to stay active than before. Previously it only needed a light touch and I could glide a finger around without much effort. Now it seems to have a higher pressure threshold before it engages, so I'm finding I'm accidentally turn off MFX during, say, a LowPass sweep, or retriggering the start of a gate arp. When it happens it sounds quite sloppy so I'll have to work on my habits. Not much more force is needed so it's not a strain, just seems weird that it (feels like it) changed.

I did try new feature for recalibrating the XY pad using a few different approaches with no notable difference, but then again I didn't expect it to do anything since it just shows trim values for X/Y coordinates: The pad feels like a bog-standard resistive touchpad. If there's a pressure threshold, looks like it's hard-coded. Wish the release notes were just a teeeeensy bit more verbose on "XY-pad behavior has been improved."

Minor gripe, but it's catching me off-guard often.

SMK · Post by **SMK** » Fri Oct 30, 2015 4:29 pm

Philternaut wrote:In my brief time since updating to v1.17: The XY pad seems to require a firmer touch to stay active than before. Previously it only needed a light touch and I could glide a finger around without much effort. Now it seems to have a higher pressure threshold before it engages, so I'm finding I'm accidentally turn off MFX during, say, a LowPass sweep, or retriggering the start of a gate arp. When it happens it sounds quite sloppy so I'll have to work on my habits. Not much more force is needed so it's not a strain, just seems weird that it (feels like it) changed.

I did try new feature for recalibrating the XY pad using a few different approaches with no notable difference, but then again I didn't expect it to do anything since it just shows trim values for X/Y coordinates: The pad feels like a bog-standard resistive touchpad. If there's a pressure threshold, looks like it's hard-coded. Wish the release notes were just a teeeeensy bit more verbose on "XY-pad behavior has been improved."

Minor gripe, but it's catching me off-guard often.

Hmmm since the X/Y pad is one of my favorite features, in fact I use it the most, reading that it takes greater pressure to activate tells me I'm not going to upgrade.

That's really SAD

Can any one else who have upgraded address this concern...talk more about the change in the use of the X/Y pad?

The X/Y was perfect after 1.10 and exactly like any Kaossilator you own. There was no need for improvements...korg finally nailed it!

There's nothing in the new update that I need, in the new update, that's worth losing the sensitive and highly responsive Kaossilator on my Electribes.

Philternaut · Post by **Philternaut** » Fri Oct 30, 2015 4:52 pm

The usual caveat: This is only my personal impression and I knew the usual risks in updating right away.

More accurately, the XY pad seems to require more (edit: MORE force, not less as the original post said, my bad) force to keep it engaged. I can bounce the MFX on/off/on/off without removing my finger from the pad with less effort than before. Sometimes I get a retrigger by rolling my finger left & right. Sometimes the retrigger is fast enough it can sound like an audio crackle.

I hope that I'm just missing something obvious here. There is no firmware downgrade option so I'll have to adapt for now. Trying to reload 1.10 or even all the way back to 1.03 gave me an invalid file error.

(* edited to say 'more' force, not 'less'.)

SMK · Post by **SMK** » Fri Oct 30, 2015 5:01 pm

Philternaut wrote:The usual caveat: This is only my personal impression and I knew the usual risks in updating right away.

More accurately, the XY pad seems to require less force to keep it engaged. I can bounce the MFX on/off/on/off without removing my finger from the pad with less effort than before. Sometimes I get a retrigger by rolling my finger left & right. Sometimes the retrigger is fast enough it can sound like an audio crackle.

I hope that I'm just missing something obvious here. There is no firmware downgrade option so I'll have to adapt for now. Trying to reload 1.10 or even all the way back to 1.03 gave me an invalid file error.

Now I am confused.

In your original post you say it takes more pressure to use the X/Y...which to me would be VERY BAD!

Now I am reading that it takes less pressure which for me would awesome!

I am about to make a serious post on another forum to warn those who love the X/Y feature, not to upgrade because of what you said about needing more pressure to engage the X/Y...so which is it?

After the 1.17 upgrade does the X/Y pad need more finger pressure to engage the X/Y?

Or

After 1.17 upgrade the X/Y pad is more sensitive and takes less to no pressure to engage the X/Y?

Please clarify, thanks!

Philternaut · Post by **Philternaut** » Fri Oct 30, 2015 5:28 pm

Yes, sorry... bad explanations I guess and I should have used the phrase "requires more force". Serves me right for rushing. Let me try again:

1. It seems to take more downward pressure on the XY pad to engage MFX/arp gate.

2. It seems to take more continuous pressure to KEEP it engaged.

3. As a result of #2, I have to keep more pressure on the pad at all times to keep an effect on or not stop a note/gate arp before I intend. The XY pad is disengaging sooner than I have come to expect in previous firmware versions, most noticeable as I glide my finger around the pad.

Put another way: More pressure downward is needed to turn the XY pad ON, but more importantly I have to keep more continuous pressure to prevent the XY pad from going OFF. When playing, I'm messing this up and mis-triggering gate arp notes or disengaging MFX before I thought it would when lessening my finger pressure on the XY pad.

For my approach to playing, #2 is the bigger issue (needing more continuous pressure), not #1 (needing a bit more initial pressure). But I can't gauge that threshold very well for other people; please don't base any recommendation on just my posts alone

SMK · Post by **SMK** » Fri Oct 30, 2015 5:37 pm

Philternaut wrote:Yes, sorry... bad explanations I guess and I should have used the phrase "requires more force". Serves me right for rushing. Let me try again:

1. It seems to take more downward pressure on the XY pad to engage MFX/arp gate.

2. It seems to take more continuous pressure to KEEP it engaged.

3. As a result of #2, I have to keep more pressure on the pad at all times to keep an effect on or not stop a note/gate arp before I intend. The XY pad is disengaging sooner than I have come to expect in previous firmware versions, most noticeable as I glide my finger around the pad.

Put another way: More pressure downward is needed to turn the XY pad ON, but more importantly I have to keep more continuous pressure to prevent the XY pad from going OFF. When playing, I'm messing this up and mis-triggering gate arp notes or disengaging MFX before I thought it would when lessening my finger pressure on the XY pad.

For my approach to playing, #2 is the bigger issue (needing more continuous pressure), not #1 (needing a bit more initial pressure). But I can't gauge that threshold very well for other people; please don't base any recommendation on just my posts alone

Well this kind of input helps and as you know downgrading a firmware is a pain in the ass. I just read another user reported the same thing. So I have to post about it.

SMK · Post by **SMK** » Fri Oct 30, 2015 7:12 pm

Philternaut wrote:
I hope that I'm just missing something obvious here. There is no firmware downgrade option so I'll have to adapt for now. Trying to reload 1.10 or even all the way back to 1.03 gave me an invalid file error.

Have you tried a factory reset and then loaded up the updates 1.10?

Philternaut · Post by **Philternaut** » Fri Oct 30, 2015 7:14 pm

For the record I'd love to be wrong about this!

Looking back at the e2 tear-down album (http://imgur.com/a/xfox2) the touchpad appears to be a bog-standard, 4-wire, X-Y only, gets-the-job-done component. Why finger pressure to keep the pad engaged would now feel like it's playing by different rules in v1.17 versus v1.10 is a mystery to me.

Nonetheless... the touchpad pressure response on v1.17 today 'feels' different from just last night on v1.10... although no, I don't have quantifiable evidence since none of my attempts to downgrade firmware have worked so far. Oh well, so much for posing a quick, harmless "does this feel different to anyone else?" question

SMK · Post by **SMK** » Fri Oct 30, 2015 7:28 pm

Philternaut wrote:For the record I'd love to be wrong about this!

Looking back at the e2 tear-down album (http://imgur.com/a/xfox2) the touchpad appears to be a bog-standard, 4-wire, X-Y only, gets-the-job-done component. Why finger pressure to keep the pad engaged would now feel like it's playing by different rules in v1.17 versus v1.10 is a mystery to me.

Nonetheless... the touchpad pressure response on v1.17 today 'feels' different from just last night on v1.10... although no, I don't have quantifiable evidence since none of my attempts to downgrade firmware have worked so far. Oh well, so much for posing a quick, harmless "does this feel different to anyone else?" question

I chatted with another user on the E2/ES2 facebook page and they reported that the sensitivity is definitely different from the KP3. I own a KP3 and the thing I love about the XY pad on the E2 is the sensitivity is the same as the KP3. So at least one other person can confirm that there is a difference.

Regarding downgrading the OS, did you try a factor reset?

You should join the group: https://www.facebook.com/groups/1587573334805635/

Philternaut · Post by **Philternaut** » Fri Oct 30, 2015 7:35 pm

Thanks for the suggestion. No, factory reset + retry firmware didn't work (for me). Reformatting the SD card & retrying with v1.10 didn't work, neither did formatting & trying another SD card (just in case). Each time: "Error / Invalid file".

I'm sure down the road other useful info will pop up as more people share their own impressions and approach this from other angles.

(Thanks for the invite; I'm weird and don't really do Facebook.)

SMK · Post by **SMK** » Fri Oct 30, 2015 7:48 pm

It's been confirmed, you can not downgrade the firmware once you install 1.17.

Ted3000 · Post by **Ted3000** » Fri Oct 30, 2015 7:52 pm

I don't notice a difference in the pad pressure needed to engage an effect.

I believe you guys, but I can't tell. Generally OS updates can help with weird encoder behavior - jittery pots are scanned and averaged, small jitters ignored, etc.

Since the XY pad isn't measuring depth of pressure I'm not sure how they'd make it more or less sensitive.

The hazy language used in these release notes is the cause of half the world's problems.