BUGS!!!!! Come into my parlor, said the spider....

Yahtef · Post by **Yahtef** » Thu Jan 08, 2015 8:46 am

I've only had this _Tribe-drum for two days, and havwnt yet diddled OS f/w 1.03 yet enough to discover but heres my list of bugs found:

1. Pad Velocity Spillover - Pads struck in close triggering will spill this parameter to its successor. Pad G is set to velocity = off. Pad Q is set to velocity =On. When played in order Q,G, the velocity data is carried over from Q to G. Thankfull, this is not chiral, and G will not negate velocity of Q.

2. Loss of Amp EG occuring in reppetion of note data. Notes played too near lose adherence to set AMp (primaeily attack)

3. Lack of running lights, or ability to turn them on. S/N 001075.

Hopefuly, this is remedied since i now have os 1.03

What have y'all found?

Ted3000 · Post by **Ted3000** » Thu Jan 08, 2015 2:17 pm

I started a "glitch list" but it never took off. Most complaints are about features that don't work like we want, rather than obvious bugs or mistakes in the OS.
http://www.korgforums.com/forum/phpBB2/ ... hp?t=94354

My main bug is the metronome falling out of time/internal sync being shuffled by the use of the odd stepper/even stepper style master effects. If you hit record after using those things the metronome will be shifted off beat.

Others have complained about lots of clicking when playing chords (some clicking is normal on any synth, analog or digital - when amps or oscillators are starting off the zero crossing)

And of course, there are some real problems that look like they were intentional - like not being able to adjust the volume post-distortion on the insert effect, giving you one really loud distorted part that overwhelms the others. (Due to a single parameter on effects) or effects that are preset in ways that make them far too tame (like short delay being incredibly quiet, tape delay not doing limiter-protected self-oscillation, overdrive never crunching, auto-wah not having a smooth wah-like attack and release, filters dropping way too much volume as resonance is raised, anti-alising filters too steep, etc.

Are you running your electribe from battery power? The underlighting only works when using the power adapter.

Tarekith · Post by **Tarekith** » Thu Jan 08, 2015 3:32 pm

2. It's because the Electribe is paraphonic, not polyphonic.

3. Do you have power saving mode on?

Spheric El · Post by **Spheric El** » Thu Jan 08, 2015 6:48 pm

Nice list of gripes Ted3000 . Pointing out its shortcomings plainly for those who haven't bought one yet.
I must add to this list of glitches the unstable clock signal that Tarekith has recently documented .-Korg does it again!
Some people suggest this is Abletons fault, but it was the same with iOS. I need to see this clock some hardware before I commit £.

Ted3000 · Post by **Ted3000** » Thu Jan 08, 2015 8:02 pm

Spheric El wrote:Nice list of gripes Ted3000 . Pointing out its shortcomings plainly for those who haven't bought one yet.
I must add to this list of glitches the unstable clock signal that Tarekith has recently documented .-Korg does it again!
Some people suggest this is Abletons fault, but it was the same with iOS. I need to see this clock some hardware before I commit £.

I really like my electribe and I'm glad I bought it - but I know it won't improve unless people talk about the cons.

About the sync - I trust Tarekith's judgement. The tempo is pretty closely matched but the kicks never line up perfectly. Hard to say what would cause a one-directional misalignment. Play not resetting the clock on the electribe? Freerunning clock pulses?

When you get a computer involved, things can get complicated. There's latency in the DAW, minus your compensation or plus overcompensation, plus hardware issues. Even hardware synth-to-synth, you can get dropped clock pulses or drift, or a BPM that never sits still - flickering between 119 and 120 when the master never budges. (If you have tempo-synced digital delay, you'll get crackling as the delay time jumps around.)

Re-Member · Post by **Re-Member** » Thu Jan 08, 2015 8:39 pm

Spheric El wrote:Nice list of gripes Ted3000 . Pointing out its shortcomings plainly for those who haven't bought one yet.
I must add to this list of glitches the unstable clock signal that Tarekith has recently documented .-Korg does it again!
Some people suggest this is Abletons fault, but it was the same with iOS. I need to see this clock some hardware before I commit £.

I was the person whom suggested it was a problem with Ableton, but I also said it's a problem with the computer being used as well. Syncing a computer to any MIDI device results in "jitter," but the level of jitter varies based on the computer's processing speed and program being used.
You can read about MIDI jitter here:
http://www.soundonsound.com/sos/dec07/a ... h_1207.htm
http://www.e-rm.de/data/ERM_Jitter_Report_02_14_EN.pdf

An iOS device has to continuously process and convert the MIDI signal just as it does on a computer, so the same rules apply.

Yahtef · Post by **Yahtef** » Fri Jan 09, 2015 5:58 am

Hehe. I love it when I am humbled by my own Scoobiness. It was nice to laugh at my lights (and self) when I plugged in.
I'm hoping very much that we will be able to assign our own shortcuts to the shift pads.
And my biggest complaints so far are the lack of menu titles, or bullets, or numbering or ANY thing to let on to navigation. Argh.
And I am a bit disappointed there is no *original value.

(Really, KORG?!)

dutchcow · Post by **dutchcow** » Fri Jan 09, 2015 10:25 am

I have an odd issue with motion recording. When I record some knob turns the motion record mode shuts off after one complete set of bars. This is good. But when I turn knobs again it still says it;s motion recording even though record is off.

Has anyone else ran into this?