Yahoo Groups archive

Emax

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

Message

Re: [emax] Memory Management problems?

2010-05-03 by Mike Dundas

I haven't used my emax in some time, but I recall similar problems at times... typically I would save pretty much constantly and if I even saw the slightest beginnings of keymapping oddity I would turn off and redo the actions from where I had last saved, which typically worked. I don't recall it happening as often later on when I had upgraded to Emax SE OS, but I can't be 100% sure as I haven't used it in about a year now, though I get more tempted to each tiem I get more dissapointed by vsts these days...
~AJB



________________________________
From: nsputnik <nick@...>
To: emax@yahoogroups.com
Sent: Sun, May 2, 2010 8:18:09 PM
Subject: [emax] Memory Management problems?

  
I have a problem with my Emax.

When I assign and sample the first sound, everything is fine. When I assign and sample the 2nd or 3rd sound, for some reason the key assignment jumps up to a key several octaves up along with the pitch. If I delete this sample, sometimes it deletes parts of the other sounds I have sampled, and some keys will now contain more than one of the sampled sounds. It is like a game of wack-a-mole. I can keep sampling new sounds, sometimes it takes correctly, sometimes it does not sample, sometimes a previously sampled sound will get messed up with pieces in the sound missing. Is this a software bug, a hardware failure? Is this a known problem in one of the OS versions? I am not with it right now so I can't see what the software version is. Somehow I managed to fill an entire bank of very short drum sounds (0.5 sec) while bearing with this problem and not have the problem on any keys. Now I am trying to do 3.5 second drum loops and it seems the longer the sound,
 the less forgiving. Saving on a floppy.


 



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

Attachments

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.