My experience with the new Electribe 2 (aka Mr.Clipper)

Ted3000 · Post by **Ted3000** » Tue Mar 31, 2015 10:48 pm

1_inch_punch wrote:=The only way any improvements will proceed is through inspiration provided by consumer backlash

Korg is aware of the feedback (which was also internal - they're users as well as designers) and are working on a new OS.

Seriously, how many development man-hours do you think will be spent by Korg if comment section tantrums scare off the customers? That's when they'll fix it - when sales flop?

Future development follows the money - the gear that people champion and buy. It's a platform more than a static object. Let's not help stink up the joint.

I'm not saying don't discuss the shortcomings. Just avoid all the angry wounded declarations that it's useless junk. It's not. And that's with 1.3.

Andrew_OM · Post by **Andrew_OM** » Wed Apr 01, 2015 9:27 am

Thank you everybody for your replies, you really made me feel a liiiiiiiitle bit more optimistic that in the future things will improve with our E2. This is a swell community, I don't know how I didn't take part until now.

The new electribe is not useless junk at all!!

Only, that it clicks / clips / cracks very bad.

VERY VERY VERY bad.

EXTREMELY bad.

Other than that, it's cool.

wasstof · Post by **wasstof** » Wed Apr 01, 2015 10:37 am

And the Voice Stealing can be a bit annoying and confusing at Times!

roblabs · Post by **roblabs** » Wed Apr 01, 2015 3:14 pm

I think one way Korg could help users regarding the voice stealing/poly limit is to include a small graphics icon or percentage of cpu load. at least then you'd know when you're pushing it too close.

Tarekith · Post by **Tarekith** » Wed Apr 01, 2015 4:04 pm

The problem with that is that scanning for CPU load incurs quite a bit of CPU load itself unfortunately.

roblabs · Post by **roblabs** » Wed Apr 01, 2015 4:23 pm

Tarekith wrote:The problem with that is that scanning for CPU load incurs quite a bit of CPU load itself unfortunately.

Ah, didn't know that. Well, scratch that one, then!
It'd be nice, then, if Korg could include some type of document that detailed how these things factor in to the poly limit. I recall you saying that you had some voice drops with something like only 5 or 6 parts playing. A situation like that really leaves users in the dark as to what is going on...

piscue · Post by **piscue** » Wed Apr 01, 2015 6:04 pm

Tarekith wrote:The problem with that is that scanning for CPU load incurs quite a bit of CPU load itself unfortunately.

This also happens on regular computers.

Poumtschak · Post by **Poumtschak** » Wed Apr 01, 2015 8:43 pm

roblabs wrote:I think one way Korg could help users regarding the voice stealing/poly limit is to include a small graphics icon or percentage of cpu load. at least then you'd know when you're pushing it too close.

I've asked this before, and second that.

Heck, even my 18 years old Roland JV-2080 tells me how many voices are in use. Per part. Realtime.

With Korg, it feels like driving a car without a dashboard.

dutchcow · Post by **dutchcow** » Thu Apr 02, 2015 9:42 am

According to the majority on this forum the clipping is fine, you just need to work around it, and if you can't then you're not worthy of the E2 in their eyes. I hope you still have the receipt.

apapdop · Post by **apapdop** » Thu Apr 02, 2015 10:21 am

I ran into tome real nasty clicking on a part using a PCM sample last night, caused by mildly rapid retriggering, i intended the part to be mono, but i switched it to poly and the clicking vanished. So its worth experimenting, switching from mono to poly and vice-versa.

deep88 · Post by **deep88** » Thu Apr 02, 2015 2:46 pm

receive today, unpacked, nice machine, feels nice
connected, try some things, then try to play keyboard and...what the f*ck is this...
then i come here
then i'll send it back immediately

thesigma · Post by **thesigma** » Thu Apr 02, 2015 3:17 pm

apapdop wrote:I ran into tome real nasty clicking on a part using a PCM sample last night, caused by mildly rapid retriggering, i intended the part to be mono, but i switched it to poly and the clicking vanished. So its worth experimenting, switching from mono to poly and vice-versa.

How does this impact your polyphony? Do you now have fewer voices to use, for what you intended to be a mono part?

apapdop · Post by **apapdop** » Thu Apr 02, 2015 7:37 pm

thesigma wrote:
apapdop wrote:I ran into tome real nasty clicking on a part using a PCM sample last night, caused by mildly rapid retriggering, i intended the part to be mono, but i switched it to poly and the clicking vanished. So its worth experimenting, switching from mono to poly and vice-versa.
How does this impact your polyphony? Do you now have fewer voices to use, for what you intended to be a mono part?

My music is generally quite minimal, so a part or two set to poly with a few overlapping notes here and there hasn't made a negative impact, as far as i can tell. BUT.... sticking to the electribe flavours of filter rather than using the fancy ones has reduced note stealing by a considerable amount. I was using the MS20 filters alot and sometimes the thing nearly ground to a halt!!

dutchcow · Post by **dutchcow** » Sat Apr 04, 2015 11:11 am

When a product is buggy due bad testing and bad software and/or hardware a company has choice to ship it or not. Korg choose to ship. I find it funny that people defend Korgs decision to release too early. It's plain to see they didn't test it properly.

The argument I hear is that it's normal nowadays. It's not normal, it becomes normal when customers swallow the BS and stick with an unfinished product. You're too nice.

What do you think Korg would've done if everybody returned their unit cuz of the clicking, anti-aliasing, bad software design or something else? They would've gotten a clear signal. The signal they get now is that they can simply release another unfinished product. According to the consensus here users shouldn't whine about half baked products and wait and hope issues will get sorted after paying up

deep88 · Post by **deep88** » Mon Apr 06, 2015 12:44 pm

dutchcow wrote:When a product is buggy due bad testing and bad software and/or hardware a company has choice to ship it or not. Korg choose to ship. I find it funny that people defend Korgs decision to release too early. It's plain to see they didn't test it properly.

The argument I hear is that it's normal nowadays. It's not normal, it becomes normal when customers swallow the BS and stick with an unfinished product. You're too nice.

What do you think Korg would've done if everybody returned their unit cuz of the clicking, anti-aliasing, bad software design or something else? They would've gotten a clear signal. The signal they get now is that they can simply release another unfinished product. According to the consensus here users shouldn't whine about half baked products and wait and hope issues will get sorted after paying up

+1