WM Errors

Noolmusic.com
Nool's Blog
Nool's Music Page
Nool's MySpace Page

Noolmusic.com - 2006 BuzzTracker Buzzmachines.com Bulletin Board Frequently Asked Topics (BBB FAT - FAQ)

Nool's
Radio

Buzz FAT
Fat HomePage
Automation of Parameters
Copyright
CPU Fixer
Crashes - Bugs
Fixing Broken Bmx Files
Hexidecimal
Humanization - Groove - Timing
Index.txt
Lee Dragon's Stereo Wrapper
Machine Development
Machines
Master Machine
Multipattern Sequencer
Mutex Errors
Noisebursts
OMG - A Machine Stops Working
OMG - A Machine Wont Stop Making Sound
OMG - I Cant Hear Any Sound
OMG - I Cant Open My Bmx File
Opening Bmx Downloads
OS - Operating System
Overloader FAQ
Overloader Specifications
Peerchord
Piano Roll
Polac VST FAQ
Presets
RnZnAnF
Soundfonts
Templates
Tick Subdivision
Time Signatures
TPB Changes
Tuning
Tutorials - Help
USB CRASH
Using Midi Files
Visual Aides
Volume Fades
Why Does A Sample Get Cut Off
WM Errors
XS-1

BuzzFAT > > > Machine HelpFiles > > > Forums Sorted > > >
Reviews Sorted > > > BuzzMusic > > > BuzzMachines > > >
BuzzManual > > BuzzWiki > > BuzzChurch > > BuzzRadio > >

WM = Work Mode
---
Remove wm errors - "cheapo fixer pro set to infinite"
---
I've never really paid much attention to the cpu monitor, but now i have. i realised when you go into debug mode, wm errors occur. what is a "wm error" anyway?
---
Wm errors might increase cpu usage, but will NOT affect signal quality.
But, the workmode approach, when properly implemented by one plugin and improperly implemented by the following plugin, might actually cause undesired effects.

Imagine a echo which works only when it has input. the sound will echo properly when there is input, but when input stops, the delay buffer won't get cleaned and when next sound comes in, the delayed data will play from the buffer, with wrong timing. -apo
---
Another example of plugins with workmode related problems could be filters which feed the filtering algorithm only when the workmode indicates there's signal.

Here's how it might break: If the filter was fed with a high volume signal when the workmode changes to "no signal" and if the next signal which is fed to the filtering code is very silent you might get an audible snap, depending on the algo. The algo would produce a smooth continous output if it was fed continous data. I've had to fix a few little snaps&crackles this way so the problem is real.

And now we get to "how to fix the problem". I do it by using cheapo fixer pro before such a "broken" plugin set to "infinite". Simple as that.