Cubase 14 btw. . .
I have been creating drum maps from instruments for quite some time. As recently as 1 week ago. Generally, I add the instrument and select the kit. Go to the drum editor pane or inspector pane and use the dropdowns to select create map from instrument. . .
Updated my BFD to 3.5 found that it’s now broken (i.e. greyed out) I do have a ticket in with the BFD folks but I can’t be sure it’s that as other drum software is also misbehaving as such. I can, however, create a drum map from any groove agent kit I wish.
I really don’t want to have to go back to the 80s and create these by hand - just non-productive busy work I have read, re-read, and read some more in the forums, manual and google searches to no avail.
Begging for help or ideas here.
I know as a temp workaround I can import a csv file (which bfd does export) but I can’t find a way to properly import them.
It broke for me - I’m sure others aren’t having a prob with it yet. This 3.5 version update is new. I’m hopeful that they’ll fix it. Good news is that they’re aware and my ticket has been escalated.
Importing an older drum map (or even some of the generic drum maps floating around) does work but with some big issues.
okay , however its just third party vst that are affected so it seems…at least on my system, groove agent works fine… but i dont use groove agent
i ran a test last night and can confirm that this problem also is there in cubase 14+15
hi Johnny
no it wont work no matter what chan i have or input device.
groove ageant works on all chans and has no problems..
All my 3rd party vst have the problem.
fact of the matter for me at least i recently brought a lot more libraries for my bfd 3,5, i also use slate DD5.5 but not so much , that wont work either.
ii wonder if cubase has changes that they forgot to tell the other vendors about or the other partys have not implimented the changes .. i find the latter hard to believe …some may but not all of them ???
The sad news is that the feature has been dropped from BFDs’ side, at least from 3.5. It sucks thoroughly, as this was an extremely useful and time saving feature.
I wonder if this has to do with adapting to MIDI 2.0.
Could be we’ll see a return of the feature via a new protocol that utilizes MIDI 2.0. I’m pretty sure MIDI 2.0 would support such a data exchange although I’m not certain.
I don’t think slate ever used this. In fact, apart from Steinberg and BFD (fxpansion days), I don’t think anyone else used this feature. Which is astonishing, considering how useful it is. I miss it A LOT.
No , this has to do with the fact that plugin developers use frameworks like JUCE or iPlug , which makes it easy to create VST, AU and AAX plugins from a single source, but has the drawback that those frameworks only supports a subset of the plugin format’s capabilities. JUCE is by far the dominant framework that perhaps 80% of plugin developers use (wild guess…), and afaik it doesn’t support many VST3 features like Note expression, sample accurate automation, dynamic input/output configuration and “create drump map from…”.
i am talking about the Cubase menue “make drum map from instrument”
as i grew up on the cubase drum editor instead of the piano roll i used it all the time “workflow habbit”
i find the drum editor simple fast and very effective , but no longer usable … i guess i will wait ten years and maybe steinbergs programmers might give us back a feature that worked well in the first place… just like the “quit cubase” in the version 14 it worked so why did they remove it ?
i must confess over the decades of using cubase i have never had anything to moan about …untill these last couple of versions , i now have had install problems, i now have ARA crashing cubase, color schemes doing what it wants, settings no longer being kept and this with the drum map…
i guess i will have to be patient and wait maybe a fix or a new version feature that makes these problems obsolete.
money is tight for most of us and after investing in a new machiene due to the windows 10 thing and new vsts due to vst3 etc.. to find my system and its add ons are not stable as the older one was makes me feel very disheartend.
ican still work but due to crashes and freezes etc i now have to hope and prey i dont lose too much time and more importantly data…
cheers guys for your input.
kindest regards
T
hmmm not really , and i am not certain why i would do that, after all BFD 3.5 has been around long enough i think at least two cubase versions, i worked like so many other users in the BFD Beta testing program also the SDD5 Beta versions the issue of drum mapping inside of cubase was not an issue, which makes me think it could indeed be a cubase code not being shared or not being implimented.. it just does not add up why all my third party vendors have the same problem but the cubase stock (GA) has no trouble what so ever
anyeay thanks bro.
Have a great day.
T
I have read, re-read, and read some more in the forums, manual and google searches to no avail.