Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Thread

General Sampling question

General Sampling question

2012-11-12 by freddy1771994

Hi,

I have to admit that I simply don't fully understand the sampling and the looping process on the Emax. I don't understand at all how the EMU engineers managed to create 'The Bliss Disk' bank for the Emax I for instance. I mean they saved incredibly much information in that small memory.

How can I work that efficient as they did?
I just sampled a bit again. Recorded the Arturia ARP2600 in audacity, saved that as a wav and loaded that via the EMuSer into the Emax. The result is amazing since there is no data lost, but I had to waste almost the half of the memory.

Everytime when I try to loop something, let's say I loaded a single waveform into the Emax, I get a horrible detuned dental drill and I can do what I want, it doesn't get better.

Does anyone knows the 'trick' how to choose the loop points so that I can work memory efficient, maybe you have also other hints.

Thank you very much,
Freddy

Re: [emax] General Sampling question

2012-11-12 by jammie

yes single cycle loops

but one thing you have to learn about the emax is that you need samples before the loop cant loop from sample 1 and also you need samples after the loop it does not like zero samples after loop you must have a least 1 or 2 samples 

it also needs this if you are going to cross fade loops

also with the emax it wont transpose up that much like the EII does its something todo with the limitations of the e chip

but down sampling is fine the bliss disk they used a lot of the additive synthesis of the emax have a go uyou get some really good sound if you want it to loop smoothly you need to have the same partial on the first slot and the last and use several different ones as they go allong just make sure the setting for slot 1 and the end slot are identical then you interpolate between all additive slots this will give you a spectral blend that loops perfectly

with single cycle waves cut up 3 loops of the same sample 

then you can set the loop to the middle single cycle when looped exact you then trim the third single cycle back to the loop end leaving enough after the loop end to keep the emax happy about 5 samples will do it

i do pcm samples for the t series which has the same size memory as the emax and i can get 28 multisamples with 5 samples each in that memory using this type of method

and i dont even use the full memory up

another tip is keep the sample frequency low 32khz less aliasing in the uptranspose engine

also when we used todo samples on the EII we used todo it by frequency in hz for the note we were sampling

no point in using 44.1 when recording bass as there are no hi frequency content in there this saves lots of memory

but we did this using sounddesigner2
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: freddy1771994 
  To: emax@yahoogroups.com 
  Sent: Monday, November 12, 2012 9:24 PM
  Subject: [emax] General Sampling question


    
  Hi,

  I have to admit that I simply don't fully understand the sampling and the looping process on the Emax. I don't understand at all how the EMU engineers managed to create 'The Bliss Disk' bank for the Emax I for instance. I mean they saved incredibly much information in that small memory.

  How can I work that efficient as they did?
  I just sampled a bit again. Recorded the Arturia ARP2600 in audacity, saved that as a wav and loaded that via the EMuSer into the Emax. The result is amazing since there is no data lost, but I had to waste almost the half of the memory.

  Everytime when I try to loop something, let's say I loaded a single waveform into the Emax, I get a horrible detuned dental drill and I can do what I want, it doesn't get better.

  Does anyone knows the 'trick' how to choose the loop points so that I can work memory efficient, maybe you have also other hints.

  Thank you very much,
  Freddy



  

[Non-text portions of this message have been removed]

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.