2015/12/04 04:52:37
LAGinz25
Everything was fine with my BFD3 until I had to disconnect the hard drive and then re-connect it some time later. Because, in the interim, I had another component connected, it renamed my hard drive from D to G. Ok, so I just went into BFD 3 and renamed the paths. But here's the weird part---now when I play many of the included grooves, they are generating random and occasional PIANO!! hits instead of drum hits! What in the world is going on?
2015/12/04 09:50:24
MachineClaw
check registry for BFD, maybe paths are still screwed.
 
you know you can swap the devices lettering right? 
 
add new hardware, change hardware to some other drive letter, put the original D hard drive back to D then name put the new hardware at whatever you want.
 
this should allow BFD to operate normally and let you use the new hardware - unless I am missing something.
2015/12/04 11:44:16
twaddle
LAGinz25
Everything was fine with my BFD3 until I had to disconnect the hard drive and then re-connect it some time later. Because, in the interim, I had another component connected, it renamed my hard drive from D to G. Ok, so I just went into BFD 3 and renamed the paths. But here's the weird part---now when I play many of the included grooves, they are generating random and occasional PIANO!! hits instead of drum hits! What in the world is going on?




 
When you say "it renamed my hard drive" you mean windows and NOT BFD3 surely?
And when you say you went to BFD3 and, 'renamed the paths' I'm assuming you mean you pointed BFD3 to the new location on drive G?
 
That should have worked but did you rescan "all content paths" afterwards?
 
What you could, and probably should have done was simply to rename drive G back to drive D but that's probably not going to change anything now. If you haven't re-scanned all content paths then doing so may fix it but can't guarantee it I'm afraid.
 
I'm not sure why some only some grooves and not all of them are playing random piano notes.
Does it do this in stand alone as well as in sonar?
I would suggest checking the midi outputs in BFD3 and see if they have changed but it's very odd that it would happen on some grooves and not others.
 
Steve
2015/12/04 11:54:49
twaddle
Contrary to MachineClaws advice, I don't think you assign drive letters via the add new hardware ?
 
At least that's never been the way I have done it in the last 18 years.
 
You've not said what version of windows you're on but you need to get to your computer management page then disk management and there you'll see your drives, right clicking on a drive you'll see, "change drive letter and paths".
Click on that and choose the letter you want from the drop down list. If it shows another drive listed as D, then you'll need to change that to another letter but be warned if other programs need stuff on that drive to run as they will have the same problem. I store all my samples on internal drives for that reason.
 
Steve
2015/12/04 11:57:11
bapu
twaddle
I store all my samples on internal drives for that reason.

+ya
2015/12/05 17:06:24
LAGinz25
Changed the drive designation and did a reinstall.  Problem still there though!, and I'm beginning to think it has something to do with the way BFD 3 treats MIDI. At low volumes you can actually hear piano notes playing the MIDI, which effect recedes as the volume is turned up. Hmmm... I'm thinking that an incorrect MIDI format sounds like it might be the issue, but how can this be the case for BFD 3's own groove library?
2015/12/06 13:42:38
twaddle
I'll ask you again
 
What is your audio/midi interface and what is it set to in BFD3's midi settings.
Also (again) does it do it in both sonar and stand alone or just in sonar?
 
BFD3 doesn't handle midi any differently than any any other vst.
 
Steve
2015/12/07 14:25:04
ampfixer
Sounds like the track that's generating the BFD notes is also sending midi out to other VST's that are set to omni and triggering them.
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account