Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MusE 2.2 Drum maps
#1
Hi all,

Been using MusE for a little bit now and want to start creating some custom drum mappings for my kit to a sound source.

Compiled the 2.2 src from the muse-2.2.tar.gz on Fedora 20. I actually got a source code compile error but it looks correct. I commented out the code starting
at line 415 and ending on 419 in helper.cpp. Even though the dependency for LV2 seemed to be resolved it was not included anyway. But the error is with a ')' according
to the compiler on both lines below (i'll try to recompile after work and capture the exact message) :

if (type == MusECore::Synth:Big GrinSSI_SYNTH && ((MusECore:Big GrinssiSynth*) synth)->isDssiVst() ) // Place Wine VSTs in a separate sub menu
type = MusECore::Synth::VST_SYNTH;

if (type == MusECore::Synth::LV2_SYNTH && !((MusECore::LV2Synth*) synth)->isSynth() ) // Place LV2 effects in a separate sub menu
type = MusECore::Synth::LV2_EFFECT;

After commenting out the above line and re-building i got a successful muse.

Questions :

Any tutorials on how to create and use different drum maps? I have had no luck. Tried the gui and copying an existing map (the addictive_drums.map) but without sucess.
After modifying the XML for a custom drum map, MusE reads the mapping in fine and displays the new note names and assignments but does not trigger the actual note(s).
I verified the enote and anote tag values and they look correct, actually I have mapped them to the same values. I tried creating the <entry> elements from 0 thru 127 with
empty names for notes that do not map to a sound and tried leaving out <entry> elements for notes that do not actually map to a sound but it did not seem to make a difference.

Sometimes the notes do not produce a sound and sometimes the actual note events are removed from the track (yep, removed).

If I try the re-map menu option or move one of the note mappings in the gui a crash occurs.

What is the difference between old drum track and new? If I were to use the new style I can't seem to find anyway to provide a new drum map.

For notes that are not really mapped to a sound i see the option to hide them. When I do this a red symbol appears but they are still shown, is that correct?

I was thinking maybe to modify the drummap.cpp defaults to the actual mapping I am trying to create and re-build but it seems a bit drastic. I'm wondering if the
lines I commented out are the cause of my problems. If I get some time I may try running the version from the distro repository and see if I get the same behaviour.

Also, not related to drum maps exactly, I sometimes need to split drum tracks by notes to individual tracks, Each event with the same note value on the same track
does this already exist?
Also, filtering. The events recorded from my Roland e-drum kit brain into MusE need to be fixed up (note to note mapping, note + foot controller value to different hi-hat sound)
does this already exist?
I have some custom code that does the last 2 for me but if I can do it inside of MusE that would be nice. Is that something the python scripts could do?

Anyway, Thanks, I think MusE is great!
Reply


Messages In This Thread
MusE 2.2 Drum maps - by sfdadds - 01-22-2015, 06:25 PM
RE: MusE 2.2 Drum maps - by danvd - 01-22-2015, 07:09 PM
RE: MusE 2.2 Drum maps - by sfdadds - 01-22-2015, 07:15 PM
RE: MusE 2.2 Drum maps - by sfdadds - 01-23-2015, 02:53 AM
RE: MusE 2.2 Drum maps - by danvd - 01-23-2015, 05:54 AM
RE: MusE 2.2 Drum maps - by sfdadds - 01-23-2015, 02:07 PM
RE: MusE 2.2 Drum maps - by spamatica - 01-24-2015, 12:20 AM
RE: MusE 2.2 Drum maps - by sfdadds - 01-24-2015, 03:08 AM
RE: MusE 2.2 Drum maps - by spamatica - 01-24-2015, 05:32 PM
RE: MusE 2.2 Drum maps - by sfdadds - 01-24-2015, 06:53 PM
RE: MusE 2.2 Drum maps - by spamatica - 01-25-2015, 09:16 PM
RE: MusE 2.2 Drum maps - by sfdadds - 01-26-2015, 06:46 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)