Korg Forums

I don't think he is talking about IFX of the Synth version. Also reverb doesn't exist as IFX. Notes and IFX tails carrying over would be great. But seeing is believing. I ain't giving Korg my money again until these issues are properly sorted.

Yea I'm happy with notes carrying over. He didn't mentioned IFX's, and thinking about it, I'm gonna say it's just the notes that probably are given a small window to fade out (or something like that), given the limitations of the DSP and all..

Everybody talks about DSP limitations. I didn't realise there where so many embedded device experts here. And even if, Korg could've easily spend a few extra bucks on beefier hardware. I wonder how much more the BOM would be. Curious about the BOM of the current models too.

http://en.wikipedia.org/wiki/Bill_of_materials

There *are* delay IFX, which can linger for quite some time. Also, I've had the MFX cut out abruptly too.

chris1a wrote:
There is a "gap", no you are not thoughtless. Notes, IFX etc don't carry over and so on, which results in this audible glitch. This will be fixed in the June/July update, and the "thoughtless" thing was a remark about that upcoming firmware.

I don't know if the word "gap" is the proper way to describe the current problem though, but in the end that's just semantics. Notes, IFX etc getting cut off is just really, really bad design.

This has been explained many dozens of times on this and other forums.

The word "Gap" is totally incorrect when talking about os 1.03 and up.

When the e2 was in beta and first shipped, when you changed a pattern you got a little blip of silence between patterns. That was a gap - a silent hole between the patterns. This was bad. You could hear it. Everyone noticed it.

The gap has been fixed.

The behavior you'd like is a carryover/tails thing where the old pattern rings out when you switch to another. It was assumed by me and others to be impossible - James Pullen says it's coming in the final update - so we'll see. He's been right before. He's a beta tester and factory pattern programmer.

But right now on good old 1.03, master reverb or master delay have tails if pattern A and B both have the master effect. That, plus the lack of a gap, should be enough to tide you over.

Ted3000 wrote:
But right now on good old 1.03, master reverb or master delay have tails if pattern A and B both have the master effect.

Thans why i / we need a masterfx lock, wich work the same wat as the bpm lock does. So you dont have to reprogram all the Patterson mfx or you can change mfx live without worrying about mfx gaps.

James Pullen wrote:
The notes carry over, the reverb tails carry over, and sounds switch with no gap. It is gone. You can make it glitch if you want by changing lots of values but functionally it's gone.
Now I kind of want to try to make a bunch of 1 and 2 step patterns where I radically change everything and jump back and forth between them.

But delays and other efx tails do not carry over, is this a correct understanding? Even if it's the same IFX in the next pattern?

oh man, if this is true, i'm going to be so happy that i'll slap my grandma so hard that her dentures go flying. i'll pick them up from the ground for her, and apologize to her, of course.

It also could be the gap that occurs when you activate more than 7 parts at once and there's a very apparent gap on the 2nd bar

James is talking about the sampler, not the synth version. Didn't he also say the firmware would be swappable? I think he does a lot of wishful thinking.

If only Korg had selected some random people from this forum they would've had some great testers.

I hope that in June/July (6-7 months after release) a new firmware will really fix stuff and not introduce new bugs and issues.

Hugo wrote:But delays and other efx tails do not carry over, is this a correct understanding? Even if it's the same IFX in the next pattern?

Yes, even though the first Sonicstate review said otherwise. Long note decays, IFX, or anything else that could carry over will be broken off when changing patterns.

You either have to work around it or get something else.

22tape wrote:oh man, if this is true, i'm going to be so happy that i'll slap my grandma so hard that her dentures go flying. i'll pick them up from the ground for her, and apologize to her, of course.

dutchcow wrote:Everybody talks about DSP limitations. I didn't realise there where so many embedded device experts here.

I don't call myself an expert but I've spend some years around DSPs. Besides me there could be 2-3 other guys over here that could have mentioned DSP.. not everybody . The architecture of the effects of this unit tells you they're pushing the DSP to the limits. POPS/Cracks on low frequency notes is related to buffers size (memory of DSP), poor modulation effects is another indicator of: "....hey there is not enough DSP power." I could go on but really I'm not an expert.

dutchcow wrote:And even if, Korg could've easily spend a few extra bucks on beefier hardware.

No they couldn't, the battery life is the first biggest factor to put limits of what DSP can do. The second would be the price. Which as you mentioned with BOM would be + $10 or $20 per unit.

dutchcow wrote: I wonder how much more the BOM would be. Curious about the BOM of the current models too.

I would like to mention here that the half of the cost of this gizmo goes to the firmware development (not to mention the R&D).
That cost include both the UX programming and the DSP programming. Since korg claims that E2 sounds similar/same as the korg-king they need a lot of "cojones" (cahoonas) to get king-korg-analog-sounds using 1/3 of DSP power that of korg-king.
Lastly as all we know both the UX and DSP coding efforts on E2 are only 75% done ... so the "google beta" sticker would be appropriate. I was looking for one in the E2 box but I couldn't find one.

How do you get to know all this stuff?!?!? What goes on under the hood is just bad juju to me... Thanks for the insights, everybody.