BFD dropouts

[matt]

Well, this worked for a few minutes...

Start > Control Panel > Sounds and Audio Devices > Hardware tab > highlight sound card > Properties > Properties tab > Audio devices > highlight sound card > Properties > check Do Not map through soundcard

Sample rates of 44.1, 88.2 seem to have fewer issues.

Anyone have this working consistently?

[Rail Jon Rogut]

Which version of BFD? Is this BFD Standalone or as a plug-in? What kind of drive (SATA, IDE, FW400, FW800, USB2, eSATA) are the samples on? How much physical RAM does your PC have?

Rail

[matt]

Ver. 1.5.46 B10
This has been an issue with all versions.
I have tested different songs and it only happens with the 48k/96 session sample rates. Maybe it has something to do with BFD using 44.1k for it's library files.

[studio-c]

Just to throw an uneducated 2 cents in... it seems that anytime you're asking an app to resample on the fly, especially in the case of rapidly comin' atcha percussive hits from multiple soundfiles, you're asking for trouble.

It seems in the same category as the folks asking for SAWStudio to translate MonkeysAudio or Lossless filetypes to wav, then record as wav, then convert them back. Keep the thing streamlined. Just an observation. I don't know much about BFD specifically. But it makes sense that the fallout of not keeping up would be firing blanks.

Cheers,
Scott

[Rail Jon Rogut]

You shouldn't try to run BFD at a non native sample rate if possible - BFD2 has been rewritten and instead of sample rate converting when reading in the samples, they only do it at the end of the process --- so performance is about 50% better when used in a 96kHz session. FXpansion have always suggested you create your drum tracks in a 44.1kHz session and then render your drums and use a better application to do the sample rate conversion.

Rail