rinseout wrote:arebee wrote:hey can someone verify this please.
as mentioned above, my mpc is seizing up asif ive massively overloaded the sequencers realtime playback engine, i mean that its behaving as though its got many more events to play than are actually there. it plays them in os484 fine, but 485 has real problems coping with the sequences.
ive got a sequence running, only a few tracks. a few events in each.
and when i mute them all, the 'voice(polophony) counter' - in Other Page (mode+pad10) clocks up to way over 20!. with nothing actually playing.
i'm assuming that the voice counter isnt supposed to count voice use when no voices are 'used' right?
This has to do with the track mutes, to be able to have an "immediately unmute" the voice have to play even when muted, like muting the audio output from that voice. Now he fixed the "bug" muted events muting other events when set to mono (still with me?), but that has to be some strange workaround i guess.
no, not sure what u mean, but ive had a minor breakthrough, and im a bit miffed to find out it was 95% human error, i had many of my amp envs set to 100/end !! a recipe for disaster, only ok if u aint looping the samples - ahem. but i had loop on all of 'em. phew......but the fact remains that the os 485 plays the sequences worse, ie: it seizes up much quicker than in os 484.
note: i figured i'm often a bit of an untidy worker mostly due to geting wild ideas down before i hammer rigid controls on the method in which i created the ideas, because demo fever sets in as your left with an overly neatened version - and sometimes a more lifeless example of the first flashes of inspiration....but in this case its worth the effort to go in after the main blast is done, and strip fat off whats not needed (ie: 100/end amp env's on any/all sounds - and not JUST the ones that need it), i reckon ive been abusing the global prog edit "whole" button. so in future it'll be all set to very eco programming, then widen out ONLY where its absolutely required.
but soz for bleeting on about the bogus bug i thought i had.
one more thing though - why does the voice/poly meter show voices used even when all tracks are muted. in this way its only showing the overall maximum voices needed IF you've got all tracks on at the same time.
it would be more appropriate (imho) to have it monitoring the voice use at the very last stage of the voice allocation (ie: only voices that are truly playing) no?
