Hopefully someone can shed some light on this problem I have! Got a new laptop from Scan the other day and I am in the process of installing all of my software. The machine is ASIO optimised, has an i7, 32gig of RAM and both an NVMe and SSD, so it shouldn't be a system issue.
I have installed BFD3 after a huge headache - none of the links on the product pages work, I had to take the installer from my old machine via Google Drive, hope I have the installers for my expansions - got it to the latest version through the licence manager, but something is up with it.
The cymbals cut short and certain snare hits will play the wrong hit type e.g. a drag instead of a rimshot or just drop completely. I have tried everything on the engine preference window, but nothing has resolved it. It works just fine on my old machine, I have uninstalled and reinstalled without updating to the latest version and still get the same audio issues.
There used to be a forum but all of the Google entries for forum posts go to Roli which seems had no useful info.
Any ideas??
Comments
We're currently in the process of moving everything over to the new inMusic platforms. But that said, the download links should be working - they're working here! Are you using Google Chrome?? I know the fxpansion website is having some problems with Chrome right now.
Cymbals cutting short could be a machine configuration; happy to diagnose, but would need more information about your machine, particularly the hard-drives. If they're older mechanical HDD's then you would definitely benefit from an upgrade to an SSD.
Hits not playing correctly could be a keymap issue, but difficult to know without having something specific to look into.
The laptop is a brand new i7 10750H, 32gig of RAM (DDR4 2666mhz) has a 1TB Samsung NVMe drive and a 500 gig Samsung Evo 870 SATA SSD. It has come from Scan and they set them up for audio before shipping, so I am surprised to see any problem.
Installed the core library from the USB, I have tried moving it from the main drive to the secondary, still getting the same issue. The keymap loaded is BFD 3.0.
Let me know if you need any more info and thanks for looking at my post!
Ping me tomorrow and I can help you diagnose the issue.
In the preferences you'll find a sub-page called Engine. That's where all of the engine parameters are defined - try tweaking the RAM and STREAM buffers to find the right balance. It sounds like those need changing to me.
@WiresDreamDisasters - I have tried every combination of RAM and STREAM buffers; it results in the same issue. I have tried the different kit details and that doe not help either, if anything the economy level detail was dropping out more.
I also uninstalled BFD3 and the content library, re-installed the latest version of BFD3 and downloaded the content library from the website rather than installing from the USB stick like last time, still have the same hits dropping/cutting out at the same time.
I have tried every sample rate and buffer size on my interface, still have the problem. Really not sure what to do next....
If you look in task manager and look at all of the charts for your devices, do you see any spiking or unusual activity that occurs at the same time as the dropouts?
Does it happen inside a DAW?
It definitely sounds like the hard-drive not being able to deliver the data in time to me, but a Samsung 870 should be plenty for BFD3; I have Samsung drives in my machine.
It could also be related to the audient drivers not playing nicely with our standalone. @Cirrus I know you use this combination, have you ever seen anything like the OP's ????
I do sometimes have cut off tails - more obvious on cymbals, if the HDD is running hard eg while stuff's loading in when first opening a project. Always put that down to available hdd bandwidth.
Bandcamp
Spotify, Apple et al
Added a video of the Task Manager, disk use is 0%:
Btw. I recently contacted BFD3 with a minor issue and got very good support. But obviously you've got a BFD3 contact on this thread.
Bandcamp
Spotify, Apple et al
@IMC1980 what articulation on the snare are you triggering? I'll have a listen through them tomorrow and see if any of them are fucked.
Under the drums browser, in the Snare options, I've only got one 'Tama Bell Brass Snare' listed, when I set the Processed selector to 'Off'.
When the Processed selector is 'On', I see options for 'Blues Snare 1 JM' and 'Blues Snare 2 JM', but the latter is 'Tama Tempesta Snare SnOff'.
I've no idea if this is relevant, unless there's might be an issue with duplicate paths perhaps.
I was selecting the snare from the mixer window in the standalone app:
It is the rimshot being triggered in that loop .
https://i.imgur.com/SXLUQ6C.png