Hi Tim,

> Also, in your first message I'm unable to reproduce the
>  importing bug thing. I'll keep trying though.
> I hate to ask, but... video?
> Seems impossible that moving a part onto a drum track would
>  suddenly 'GM-ify' the track's drum map permanently.
> Check that the track's patch (program) number really does
>  correspond to a patch that the drum map is for.
> If all else fails, try 'reset track's drum list'.

I did some more research and what looks weird to me is that the drummap 
file is different and lacks information.

E.g. old drummap from 2.2.1:
   <entry>
       <name>Kick Emad Head</name>
      <vol>100</vol>
       <quant>16</quant>
       <len>32</len>
       <channel>-1</channel>
       <port>-1</port>
       <lv1>70</lv1>
       <lv2>90</lv2>
       <lv3>110</lv3>
       <lv4>127</lv4>
       <enote>36</enote>
       <anote>36</anote>
       </entry>
     <entry>
       <name>PantherSnareCentre</name>
       <vol>100</vol>
       <quant>16</quant>
       <len>32</len>
       <channel>-1</channel>
       <port>-1</port>
       <lv1>70</lv1>
       <lv2>90</lv2>
       <lv3>110</lv3>
       <lv4>127</lv4>
       <enote>38</enote>
       <anote>38</anote>
       </entry>

The problematic drummap:


  <entry idx="36">
       <name>Kick Emad</name>
     </entry>
     <entry idx="37">
       <name>PSnare Sidestick</name>
     </entry>
     <entry idx="38">
       <name>PSnare Centre</name>
     </entry>

So the whole information didn't get stored somehow.

I have now played around a bit and it seems that if I store it from the 
track view with right click on track and save drumlist, it hasn't the 
full information inside and cannot be loaded, hence the default (GM) is 
kept.

Weird is that sometimes it does load the new map and sometimes it 
doesn't and just keeps GM (I had both cases today).

Also currently I always get the semaphore assertion error when clicking 
on load drumlist, so unfortunately, on the video you see only Muse crash:

https://youtu.be/XWi4TORuiWw

I did now a complete clean and rebuild, still the assertion on load 
drumlist.

Drumgizmo is 0.9.11.


Not a bug, but a question:
As you can see also in the videos I connected the drumgizmo outputs to 
different wave tracks, that works fine.
Just I need to have the record button armed on the tracks to hear the 
actual drums (input monitoring). This is not a problem for only drum 
editing, but could be a problem when I want to record another track as 
the drums would also be recorded.
Ardour has the "In" button for this prupose, for directly monitoring the 
input of a track, but I haven't found anything similar in MusE. Is there 
a possibility to just monitor the input to wave tracks?

Alternative is to use outs but then the routing gets a bit more 
complicated because of mono/stereo outputs and also when finished with 
MIDI editing for recording the result to audio this needs to be changed 
back to wave tracks somehow.



Sorry to not have better news. If I have some more information I will 
send a message.

lg,
Michael



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer

Reply via email to