Korg Forums

There might be a HUGE problem. I've only got a few hours into my Sampler, and have not yet loaded any user samples. Last night Shawn Rudiman from Detroit Techno Militia posted on facebook that with user samples loaded and running on all 16 parts, if you scroll through oscillator selections while playing, then the timing lags and gets off from any externally synced gear. Even does it on its own internal clock.

Any Sampler owners out there that can confirm this? If it's true, the Korg has a major problem on their hands. I will try to confirm myself tonight.

Might just be a typo. There's an article or 2 out on the web, including Korg's own website that claim it has a 48/16bit sample rate, when it is in fact 44.1/16 like the old ESX. I can't find any mention of sample rate quality in the manual.

Hitting "Write" while a pattern is running can also glitch your sync.

I wouldn't call this a huge warning.

I used my own samples for a show last week and I was surprised how well they loaded up and how efficient it was. Maybe load up the "Blank" samples bank that's on the forum? This might help?

Also everything was always in time. No issues there.

Lastly the sound quality of the sampler sounds a hell of a lot better than 44.1/16. I had a miceSampler which was 48/16 and the ES2 sounds exactly the same.

Can anyone post something awesome about the ES2 instead of these worry based threads? Sorry it's not an ESX...and it is not! But, this is still a great tool.

Can some one tell me the last time they have modulated the beginning point of a sample in their gear, live, with out menu diving?

Oh, Trust me. I love the thing. Just trying to figure out if anyone else has seen the behavior. Only a mad, PA savant like Rudiman would even attempt to change the samples on a pad during a live set. But if it's caused by loading 48kHz samples, like their site suggest you should, instead of 44.1, then that should be noted.

That's a pretty extreme circumstance. But perhaps the CPU just can't handle the load? I mean, it stutters when saving while it's running. That to me says the CPU is rather weak. But always stays synced up.

It's confirmed on 3 machines. Very, very few people would encounter it during normal use, but it's there. If you change a sample while its playing, it will lag. It's only noticeable on 16th notes, like hats. The first note will hit perfect, then the 8/16 and 12/16 are off before they line up again at the end. Sounds like it's swinging out a little. Even happens if the part is muted. Not a deal breaker for me at all. I'll probably never run into it without trying to make it happen, but it's def there, and needs to be fixed.

You all and especially Ted3000 are using the machine wrong. Try to read the manual for once.

If you can call it a manual.

If the machine cannot change samples on the fly running
..as both predecessors did) withOut lagging..its no small issue. Don't bill it as a performance machine then. I'm not crazy... I just want a machine that does what it claims. Simple. I'd like to see it fixed and be a great machine.!

This is an issue that is really sad, I hope this is fixed asap. I don't understand who wouldn't want to change a sample live from time to time?! And having that option completely removed as it will throw the midi sync out is terrible, what if you acidently change the sample? Instant trainwreck

Buska wrote:I don't understand who wouldn't want to change a sample live from time to time?!

Even working with 8 bars, and even with Pattern Chaining on the ESX, I still change samples quite frequently. It is essential to my performance workflow.

Don't change samples. You need to work within the box constraints, it's part of the beauty right?

dutchcow wrote:Don't change samples. You need to work within the box constraints, it's part of the beauty right?

If I may chime in, I would normally agree with you but... In a creative sense I'm not sure it qualifies as a constraint or limitation. It's clearly a fault. A limitation would be to not be able to change samples/oscillators at all while the sequencer is running, not for it to misbehave while you do.

sauce wrote:

Buska wrote:I don't understand who wouldn't want to change a sample live from time to time?!

Even working with 8 bars, and even with Pattern Chaining on the ESX, I still change samples quite frequently. It is essential to my performance workflow.

Im not sure if you're agreeing with my point, or you've misread my comment