Electribe2 1.05 OS
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
KnowingWhatTheButtonDoes
- Junior Member
- Posts: 55
- Joined: Wed Dec 17, 2014 11:25 pm
- Location: Sydney
Yep, but on the right pattern it works (just dont have the kick assigned to it). If you want it back to the original sequence, make a copy without the MFX on to flick to.Groovesoul666 wrote:Some odd behaviour on the MFX.
When using the MFX 16. Odd Stepper on the touch pad. On activation the effect is cool but loop goes out of sync when touch pad is deactivated.
What The Fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuck??RedHouse wrote:So, I emailed Korg UK about v1.05, and this is the reply....
Electribes are actually shipping with V1.07 now, but having checked there are no differences between this and V1.03, currently available to download. We currently are recommending that users with pre version V1.03 update to this version.
-------------------------------------------------------------
Owner of the Korg Electribe 2!
Owner of the Korg Electribe 2!
-
Poumtschak
- Senior Member
- Posts: 295
- Joined: Sat Jan 06, 2007 11:20 pm
- Location: GMT+1
Maybe 1.05 and 1.07 are specific to a new hardware revision? Hence Korg not making these available for the early adopters.
OTOH, there's this 1.15 r8 USB Driver only available at Korg.jp
OTOH, there's this 1.15 r8 USB Driver only available at Korg.jp
Weird.ARP ODYSSEY, SQ-1, littleBits W5 MIDI, MS-20M Kit, electribe, electribe sampler
My electribe2 lousy patterns and stuff | KORG gear: NTS-1, nanoKEY2, electribe2/2S, WS/SR, WS/EX (on storage)
That's damn odd.
Many companies have infrequent public OS updates that land on whole numbers . OS 2.0, 2.5, etc.)
Often there will be a semi-public beta page where you get a lot of things like named 2.03b. Sometimes these skip around, so there could be builds that were internal.
But in every case, each OS upgrade represents some kind of change or fix. And sometimes previously stable features will break in a beta.
Change Logs can be useful but are often vague. It will say something like "Fixes an issue where some users experience a problem when doing X while Y is running, plus other fixes."
It's possible the change log for 1.05 and 1.07 was missing or was so vague there is no info to share. Support reps are emailing someone else, who might email someone else. There was certainly a change.
But the change could have been something specific to a region like a change in spelling in the menu. Are any US/Can. people on 1.05 or 1.07, ur is that all Euro?
However, these incremental OS changes don't usually get installed at the factory. If I recall, the KP3 had an OS upgrade advertised ON THE BOX that you had to download install yourself! Incremental OS builds tend to be DIY.
It's possible it was related to a hardware revision, but I doubt it. It WOULD explain the strange rollout and radio silence, but I doubt something as QC'd and committee-designed would go out of the factory needing a hardware recall and a custom OS. (Then again, the Volca Beats was missing a snare voice component and Korg pretended it was intentional with a straight face.)
I think we'll all be on 2.0 (or whatever they name it) this spring - and I'd wager we'll have a few more features and the obvious fixes, and maybe something more exciting.
Shifting hardware is the main deal for them - OS upgrades don't get 'em a ROI unless it's a much-discussed and much-loved feature addition - or if it keeps a fickle customer base from badmouthing the line on forums and comment sections.
Many companies have infrequent public OS updates that land on whole numbers . OS 2.0, 2.5, etc.)
Often there will be a semi-public beta page where you get a lot of things like named 2.03b. Sometimes these skip around, so there could be builds that were internal.
But in every case, each OS upgrade represents some kind of change or fix. And sometimes previously stable features will break in a beta.
Change Logs can be useful but are often vague. It will say something like "Fixes an issue where some users experience a problem when doing X while Y is running, plus other fixes."
It's possible the change log for 1.05 and 1.07 was missing or was so vague there is no info to share. Support reps are emailing someone else, who might email someone else. There was certainly a change.
But the change could have been something specific to a region like a change in spelling in the menu. Are any US/Can. people on 1.05 or 1.07, ur is that all Euro?
However, these incremental OS changes don't usually get installed at the factory. If I recall, the KP3 had an OS upgrade advertised ON THE BOX that you had to download install yourself! Incremental OS builds tend to be DIY.
It's possible it was related to a hardware revision, but I doubt it. It WOULD explain the strange rollout and radio silence, but I doubt something as QC'd and committee-designed would go out of the factory needing a hardware recall and a custom OS. (Then again, the Volca Beats was missing a snare voice component and Korg pretended it was intentional with a straight face.)
I think we'll all be on 2.0 (or whatever they name it) this spring - and I'd wager we'll have a few more features and the obvious fixes, and maybe something more exciting.
Shifting hardware is the main deal for them - OS upgrades don't get 'em a ROI unless it's a much-discussed and much-loved feature addition - or if it keeps a fickle customer base from badmouthing the line on forums and comment sections.
-
Steinberger
- Full Member
- Posts: 228
- Joined: Tue Jan 17, 2012 3:00 am
Agreed. A rev can happen with anything. There doesn't ever have to be any functionality or bug fix involved. Some things to consider are additions for localization like language support for a new target region or even headers in the code to comply with certain country-specific retail laws. You might also get different build numbers from different factories.
Nokia used to do this with their phones where different colors had different firmware build numbers which seemed crazy until you realized that each color was made on a completely different production line. So it wasn't really the color it was the factory line.
At my job, it seems like every time a software developer sneezes the build server goes off
Nokia used to do this with their phones where different colors had different firmware build numbers which seemed crazy until you realized that each color was made on a completely different production line. So it wasn't really the color it was the factory line.
At my job, it seems like every time a software developer sneezes the build server goes off