![]() ![]() Here are a few quick suggestions in my return to Mixcraft after some time away. Ok, I'm back from my silly previous ask here. This list can be found in Plug-Ins preferences under "Edit VST/VSTi Folders." That means it's better to only have Mixcraft's plugin search look in folders with "VST" in the pathname, like "C:\Program Files\VST" or "C:\Program Files\Steinberg\VSTPlugins." Unfortunately there was no standard folder for older VST formats, and different plugin makers put them in different VST folders.įurther complicating matters is that complex plugins often have both VST DLL files and non-VST DLL files.ĭragging and dropping an audio plugin into Mixcraft just adds the folder that the DLL file is located in to the list of folders Mixcraft searches for plugins. If you set Mixcraft to search a general folder like "\Program Files" for VST audio plugins, it will likely have to sift through thousands upon thousands of DLL files that are not audio plugin files to find the actual VST audio plugin files. Older VST plugin types end in DLL, but so do all sorts of other files that are not audio plugin files. All VST3 plugins have a file extension of ".VST3" and they are all supposed to go into one folder: Let's start with the newer VST3 standard. I always end up moving the existing midi clip down to lane 2 before dropping the new one. ![]() I haven't noticed it dropping behind other clips (though I wouldn't doubt it does, I'm using usually EZDrummer 2 here). ![]() Maybe there are other uses though.Īnyhow, that's the suggestion. Even if I want both drums playing at the same time (say it's a kick snare pattern and I'm adding a tambourine midi track) I'd personally still want them on separate lanes. in any event, dropping the midi behind an existing midi is not a preferred result imho. seems this might be programmatically more complicated to determine if midi overlaps somewhere. alternative: have it create a new lane if one not already there. don't have to worry about potential overlapping midi, and it's my fault if I drop in a bad spot) (best solution imho - I manually create the lanes before I drag and drop. It was be nice if the drum midi drag-and-drop dropped in the lane where it is released. It always places the newly dropped drum midi in lane 1. This occurs even if trying to drag and drop into lane 2, lane 3 or lane n. It can seem like the newly dropped midi disappears. If there's already a drum midi in lane one of the track, the newly dragged-and-dropped midi will still go in lane one, but will drop behind the midi that is currently there. Currently when dragging and dropping drum midi (I've tested in both AD2 and EZdrummer 3) when I drag and drop a drum midi track it always drops in the first lane of the track (regardless of whether something is already there or not). my general case is I often drag several drum midis to my virtual drum track to audition them with my music or as to serve as alternative grooves to something I'm working on. My specific case - but I think may be generalizable: Here's a small change I think would be beneficial regarding lanes and drag and drop. ![]()
0 Comments
Leave a Reply. |