The New Electribes

Re-Member · Post by **Re-Member** » Sun Dec 14, 2014 1:26 am

DrHoo wrote:I was attempting to event record a long filter sweep while doing some mutes & unmutes at the same time but i just kept messing it up haha....

Furthermore, following that i decided to just stack a load of cloned patterns together in numerical order so i could edit each one individually & then make a pattern set with all mutes already done, then i could event record again with just the knob action to consider. Well, i switched it off because there's a blatant stop-restart for every pattern change even though they are all the same pattern.

My MC-505 functions this way as well when using Song Mode. Each time a pattern is changed, the machine will load whatever parameter settings were saved within that specific pattern. Even if it's an exact copy, it will reboot the position of every parameter as it was saved. It does indeed make filter sweeps between patterns a pain.

One trick I do for filter sweeps is have a sine or triangle LFO to sweep the filter, but have the LFO synced to the clock. Listen to how it's going to sound right as that pattern ends, then use that as a reference point to adjust how it's going to sound on the next pattern.

Another thing you might be able to try is setting the knobs to be in "Jump Mode." This should make it so that if you're manually tweaking a sound by hand and the machine changes patterns, it will immediately adjust that parameter to match the position of the knob.

DrHoo · Post by **DrHoo** » Sun Dec 14, 2014 1:33 am

sauce wrote:
DrHoo wrote:
sauce wrote: What?! You have *got* to be kidding me..
If you mean 'That's a bit crappy' then yeah, i think so too.
Yep. That's what I mean. Your posts regarding this have sealed the deal.. I will not be an Electribe2 owner until they are (inevitably) *dirt cheap* second-hand. The specs and features vs limits has just tipped too far into the red.. I hope the person responsible for calling this unit an Electribe gets relocated to a more-suitable position.

I am just one user with one perspective & i'm sharing my thought s here but we're all different & just because i have hang ups with this unit doesn't mean others should have. I'm a straight talker but that doesn't make me the voice of this box. I spent my cash & tried it, no sweat.... It has something, something... !

DrHoo · Post by **DrHoo** » Sun Dec 14, 2014 1:36 am

roblabs wrote:maybe you'll get a sneak peak of the new sampler @ namm.

Even with all the limitations, i swear the sampler should be the one out of the two to get. I only bought the synth vers' because of impatience...

Ok it'll still have the same hang-ups or i will about it but a good hardware sampler is worth its weight me thinks.

DrHoo · Post by **DrHoo** » Sun Dec 14, 2014 1:42 am

Re-Member wrote:
DrHoo wrote:I was attempting to event record a long filter sweep while doing some mutes & unmutes at the same time but i just kept messing it up haha....

Furthermore, following that i decided to just stack a load of cloned patterns together in numerical order so i could edit each one individually & then make a pattern set with all mutes already done, then i could event record again with just the knob action to consider. Well, i switched it off because there's a blatant stop-restart for every pattern change even though they are all the same pattern.
My MC-505 functions this way as well when using Song Mode. Each time a pattern is changed, the machine will load whatever parameter settings were saved within that specific pattern. Even if it's an exact copy, it will reboot the position of every parameter as it was saved. It does indeed make filter sweeps between patterns a pain.

One trick I do for filter sweeps is have a sine or triangle LFO to sweep the filter, but have the LFO synced to the clock. Listen to how it's going to sound right as that pattern ends, then use that as a reference point to adjust how it's going to sound on the next pattern.

Another thing you might be able to try is setting the knobs to be in "Jump Mode." This should make it so that if you're manually tweaking a sound by hand and the machine changes patterns, it will immediately adjust that parameter to match the position of the knob.

I totally get what you're suggesting, i thought about just using the motion sequence digital numeric display as reference to continue into the next pattern but this synth part i'm editing is already patched to filter - mod generator & the break at pattern change makes it unusable in that way. I'm hoping for firmware fixes at best.

The jump mode.... Cool, food for thought. Cheers.

Kilko · Post by **Kilko** » Sun Dec 14, 2014 12:51 pm

So Korg has just released the 1.03 firmware on their US site (and probably other international sites).

http://i.korg.com/uploads/Download/USA_ ... ate_EN.zip

Here's the changelog!:

electribe 2 Ver 1.03 Release Information

Changes in Ver1.03 from Ver.1.00

- Reduced gap on Pattern changing.
- Audio exporting function been improved.
- Short cut with Trigger pads has been implemented (Please refer to the “Parameter Guide”).
- A few low-level software bugs have been fixed.

I can confirm it's exactly the same 1.03 Japanese System File (as the date is 30th of October). It's just the changelog that's translated correctly.

I can't really say they've fixed "gap"-problem on the 1.03 (though I've never tried the 1.0-version (maybe it was worse)), so "reduced" is probably the right term for it.

DrHoo · Post by **DrHoo** » Sun Dec 14, 2014 6:04 pm

Kilko wrote:So Korg has just released the 1.03 firmware on their US site (and probably other international sites).

http://i.korg.com/uploads/Download/USA_ ... ate_EN.zip

Here's the changelog!:

electribe 2 Ver 1.03 Release Information

Changes in Ver1.03 from Ver.1.00

- Reduced gap on Pattern changing.
- Audio exporting function been improved.
- Short cut with Trigger pads has been implemented (Please refer to the “Parameter Guide”).
- A few low-level software bugs have been fixed.

I can confirm it's exactly the same 1.03 Japanese System File (as the date is 30th of October). It's just the changelog that's translated correctly.

I can't really say they've fixed "gap"-problem on the 1.03 (though I've never tried the 1.0-version (maybe it was worse)), so "reduced" is probably the right term for it.

The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.

MatGreGor · Post by **MatGreGor** » Sun Dec 14, 2014 8:30 pm

DrHoo wrote:The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.

I second that

apapdop · Post by **apapdop** » Sun Dec 14, 2014 10:17 pm

MatGreGor wrote:
DrHoo wrote:The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.
I second that

That b**tard gap issue is raising it's head again. Getting a bit nervous!!

SMK · Post by **SMK** » Mon Dec 15, 2014 7:22 am

apapdop wrote:
That b**tard gap issue is raising it's head again. Getting a bit nervous!!

Since this happens when changing patterns and not with in the pattern I'm not that disappointed. However I would like to see this resolved soon as I am sure when I expand my playing style changing patterns will be come a part of the live song creation.

DrHoo wrote:The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.

Can you explain this in better detail, DrHoo? Maybe I am reading this wrong ( really hope so) but it reads like that if you copy an existing pattern, then that copy gets worse...meaning that it is better to use a brand new created pattern instead of ones that are copied from an original pattern you made. From what it sounds, this looks like a serious work flow headache for some.

Is there a degradation of the sounds or something?

apapdop · Post by **apapdop** » Mon Dec 15, 2014 8:55 am

SMK wrote:
apapdop wrote:
That b**tard gap issue is raising it's head again. Getting a bit nervous!!
Since this happens when changing patterns and not with in the pattern I'm not that disappointed. However I would like to see this resolved soon as I am sure when I expand my playing style changing patterns will be come a part of the live song creation.

DrHoo wrote:The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.
Can you explain this in better detail, DrHoo? Maybe I am reading this wrong ( really hope so) but it reads like that if you copy an existing pattern, then that copy gets worse...meaning that it is better to use a brand new created pattern instead of ones that are copied from an original pattern you made. From what it sounds, this looks like a serious work flow headache for some.

Is there a degradation of the sounds or something?

I've heard plenty of fantastic music built live within a single 4 (or 2) bar pattern in my time and that is kind of what i'm aiming for. But i'm sure every now and again i'll want to change pattern and i'm damn sure i'll want it to sound smooth. Maybe a bit of master fx delay/reverb will ease the transition, as i understand that the mfx carries over smoothly. Still, it's nagging at me, is there any comment from Korg on the matter?

DrHoo · Post by **DrHoo** » Mon Dec 15, 2014 9:35 am

SMK wrote:
apapdop wrote:
That b**tard gap issue is raising it's head again. Getting a bit nervous!!
Since this happens when changing patterns and not with in the pattern I'm not that disappointed. However I would like to see this resolved soon as I am sure when I expand my playing style changing patterns will be come a part of the live song creation.

DrHoo wrote:The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.
Can you explain this in better detail, DrHoo? Maybe I am reading this wrong ( really hope so) but it reads like that if you copy an existing pattern, then that copy gets worse...meaning that it is better to use a brand new created pattern instead of ones that are copied from an original pattern you made. From what it sounds, this looks like a serious work flow headache for some.

Is there a degradation of the sounds or something?

It makes no difference, it's exactly as i explained it. I have a pattern with 13 different parts in use, i copy it to the next pattern location & then to the next one again & so on.. They're all the same pattern with all the same parameter settings.
I go to the first pattern & solo 1 synth sound & then in the second pattern i unmute a second part (Hi-hat) . In the third patttern i unmute two more parts & so on. When the pattern changes there is a stop - start gap ! , very audiable & unwanted. This is all on the latest firmware. When all the parts are playing the change is not too bad.

What's happening is very obvious at the time, there is a distinct program stop & program restart occurring. The fact they havn't sorted this out yet suggests that it's a tricky one to get round & while i hope they can fix it, i somehow don't believe they will be able to.
For me , i have no interest in daw workflow so it just renders this a jam box for fun & tinkering. It still sounds damn nice, just a total pussy at seamless pattern change.

apapdop · Post by **apapdop** » Mon Dec 15, 2014 9:57 am

DrHoo wrote:
SMK wrote:
apapdop wrote:
That b**tard gap issue is raising it's head again. Getting a bit nervous!!
Since this happens when changing patterns and not with in the pattern I'm not that disappointed. However I would like to see this resolved soon as I am sure when I expand my playing style changing patterns will be come a part of the live song creation.

DrHoo wrote:The version 1 gap was dreadful, the version 1.03, better but not fixed. I found that playing a lot of parts was not bad but when i attempted playing a single synth part & copying the pattern to a different number, changing was just as bad as the version 1 firmware.
Can you explain this in better detail, DrHoo? Maybe I am reading this wrong ( really hope so) but it reads like that if you copy an existing pattern, then that copy gets worse...meaning that it is better to use a brand new created pattern instead of ones that are copied from an original pattern you made. From what it sounds, this looks like a serious work flow headache for some.

Is there a degradation of the sounds or something?
It makes no difference, it's exactly as i explained it. I have a pattern with 13 different parts in use, i copy it to the next pattern location & then to the next one again & so on.. They're all the same pattern with all the same parameter settings.
I go to the first pattern & solo 1 synth sound & then in the second pattern i unmute a second part (Hi-hat) . In the third patttern i unmute two more parts & so on. When the pattern changes there is a stop - start gap ! , very audiable & unwanted. This is all on the latest firmware. When all the parts are playing the change is not too bad.

What's happening is very obvious at the time, there is a distinct program stop & program restart occurring. The fact they havn't sorted this out yet suggests that it's a tricky one to get round & while i hope they can fix it, i somehow don't believe they will be able to.
For me , i have no interest in daw workflow so it just renders this a jam box for fun & tinkering. It still sounds damn nice, just a total pussy at seamless pattern change.

Sorry to keep banging on and I really do appreciate the time you are taking to reply to these points, but does a dose of MFX delay on some parts mask the transition a bit?

DrHoo · Post by **DrHoo** » Mon Dec 15, 2014 10:07 am

The master fx doesn't display any of the same issue. I don't see what difference that makes though because when making a pattern i would be very unlikely to want to send all parts to the one mfx. In fact there are only about 3 or 4 parts sent to the mfx in this pattern.

wasstof · Post by **wasstof** » Mon Dec 15, 2014 10:21 am

Just wondering, and it's probably going to be hard to tell without a separate metronome or exporting to a DAW,....
Is this gap caused by pattern 1 ending fractionally early or does pattern 2 start slightly late?

Buska · Post by **Buska** » Mon Dec 15, 2014 11:41 am

wasstof wrote:Just wondering, and it's probably going to be hard to tell without a separate metronome or exporting to a DAW,....
Is this gap caused by pattern 1 ending fractionally early or does pattern 2 start slightly late?

Heres a picture I took of a patter change recorded from a electribe emx 2 demo. It clearly cuts to zero signal before pattern change. This is from a v1.0 firmware electribe.