On Saturday, December 10, 2016 2:07:14 PM EST Michael Oswald wrote: > Hello Tim, > > I would have some remarks. To explain a bit: since Muse currently only > supports stereo tracks and the Drumgizmo plugin has 16 outs I normally > use it within Carla to route it's outputs into stereo.
Howdy Michael. MusE supports multi-channel synths. All 16 DrumGizmo outputs can be routed in MusE to individual stereo or mono tracks. It is true that other Track types in MusE, such as the Wave Track, are not yet true multi-channel, thus you must route the extra 14 synth outputs to say, fourteen other separate mono tracks or six other separate stereo tracks. Still, it's workable for many cases. > Because Carla is > quite versatile I use it also for a lot of other stuff (Windows-VSTs, > complex guitar reamping things etc). You can see my workflow and how I > use Drumgizmo inside Carla in Muse on the first vid in my tutorial > series on LMP > (http://libremusicproduction.com/tutorials/complete-audio-production-workflo > w-muse-and-ardour). > > > So if I understand correctly, then the new drum tracks have a kind of > fixed assignment of instrument/maps. This now doesn't play nice with > Carla, as it can literally contain anything from different instruments > (even Kontakt Player works nice from within) to processing plugins and > so a fixed mapping for Carla (which I would need for Drumgizmo wrapped > in Carla with the new drum tracks) would not make much sense. That's why > I always used the old drum tracks as they don't have this fixed mapping. > I admit that my use-case not a very common one, but I liked the > flexibility of the old drum track approach. > > So a question: is it possible to get this working with the new drum > tracks without disturbing other usages of Carla? If not, I would vote > for letting the old drum tracks in (if there are no serious technical > issues why they should go). Trust me: There is nothing old drums could do, that can't be done now. Period. MusE will automatically convert existing projects from using old drums to using new drums. If you are worried, don't hit 'Save', or save under another name until the dust settles. Comparison: ------------------- Old drums: Limited to just one editable map for ALL patches. Suitable for old General Midi 1 specification - just one drum kit. See the GM instrument for example. New drums: Supports per-patch maps. Suitable for General Midi 2 specification - many drum kits. See the GM2, GS, and XG instruments for example. Loading and saving an external map file: ----------------------------------------------------------- Old drums: 'Load' and 'Save' in the Drum Editor. New drums: In the Arranger Track List, right-click a new drum track's name field to popup a menu with 'Load' and 'Save'. Also contains 'Reset' and other goodies. These items are related to a track's ENTIRE drum list(s). Specific patch drum list items are edited in Drum Editor. * A word about synths capable of drum sounds: Synths are a challenge. Some plugin architectures do not support any concept of passing the names of the individual per-note drum sounds to the host. (I must research LV2. Does it support drum maps? Anyone know?) Thus currently in MusE you must load an external drum map file suitable for the particular synth track being driven. Otherwise MusE uses the default GM map, which might be unsuitable. For example our Addictive Drums external map can be loaded for the Addictive Drums VST plugin. For DrumGizmo someone would have to write some external drum maps for MusE - unless LV2 supports passing drum names to the host. Some good news: 1) If LV2 supports drum names - I will support it. Lemme at it! 2) I am working on supporting SoundFont drum names! I use the Swami InstrPatch library to get the names. Thus when you use our Fluidsynth MESS synth plugin to load a SoundFont file, MusE will automatically show the correct drum names! 3) If it turns out LV2 does NOT support passing drum names, then I am working on supporting assigning external drum maps persistently to synth plugins. So give 'er a try. I'll be here most of the weekend ready to talk and fix. Can't get something to work? Shout. There are still a few loose ends in this commit to take care of... Tim. > Anyway, I really appreciate your work! > > lg, > Michael > > On 2016-12-10 09:51, termtech wrote: > > Just now pushed to the git master. > > About 99% functional and usable. > > > > Many changes. Attention to detail. I will elaborate later > > > > with ChangeLog and will try to include a README-drums > > for later inclusion into the help file. > > > > Explore. Enjoy. Feedback. > > > > Quickly though, just keep these in mind: > > ----------------------------------------------------------------- > > Drum map lists are PER PATCH NUMBER now. > > See the Instrument Editor for BIG changes, and subtle ones too. > > - A default patch number is allowed now. That is, in the Patch List Editor > > > > panel, all THREE HBank, LBank, and Program can be 'don't care'. > > > > See the GM Instrument for an example of that. > > > > - When you hit 'Save' in the Instrument Editor, it updates the rest > > > > of the song immediately. > > > > - ALL Instrument Editor drum list item fields are editable, including > > > > Hide, Mute, Channel, and Port. > > > > - Drum Tracks can 'override' any drum list field, row, column, list. > > > > Right-click any drum list field to see options. > > > > - Since a default patch is allowed now, the default patch has its > > > > OWN drum list which can be manipulated, both in the > > Instrument Editor and the Drum Track overrides popup menu. > > > > Thanks. > > Tim. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
