From: . T. <ter...@ro...> - 2012-10-10 20:09:55
|
(CC'd to dev list in case they're snoozing...) Hello Kaya! Quote: "first up MIDI note/event velocities.... I'm currently using the 'Piano Role' editor to input note events into the system for base and drums. I haven't however found anywhere to edit individual note velocities by value." I bet you found this already, but look on the 'note info' toolbar. You'll see boxes for setting notes start time, length, pitch, on velocity and off velocity, as well as a 'relative or absolute' mode icon/button. "There is a portion of the window which shows the velocities as bars: http://muse-sequencer.org/index.php/Window_Reference_Guide however, these bars are difficult to select and edit (especially on a 12" screen using a track pad" Oh no, my condolences. Don't get me started on those touch pads. Actually there is a design flaw in those velocity bars: It is practically impossible to select from more than one note if they are all at the same time. Typically one does the opposite: Select the note then modify the bar, but I'm not sure that even works very well - I think moving the mouse affects all the bars at that spot, whether they are selected or not. "with no scroll). If I use the 'modify velocity' menu then I only get a percentage instead of the 'true' values 0-127." Hm, the quickest route there is that'd be one for Florian, I think he added that but it looks easy enough for anyone to change. Flo ...? I also noticed when you close the dialog the Arranger becomes active hiding the pianoroll - would be a real annoyance for anyone trying to work quickly... "Is there anywhere I can just input the actual value??" See above: Re the Note Info toolbar. "At the same time which is weird is that if I 'modify velocity' to say 40%, the next time I input a note in the piano role editor the velocity is at a really low level and not at 100% or whatever the default gets set to? 100 or whatever?? Again numerical values would be useful here." Tested: That is not the 'modify velocity' box's fault. It appears to be the LAST note that was selected governs the new note's velocity. Yet there seems to be no way to reset this 'running' value back to some default other than entering a new value in the Modify Velocity box or Note Info toolbar (see above). So good catch! Our drum editor has predefined 'levels' depending on accelerator keys pressed at the time of drawing, so is not affected by this. Could you possibly perhaps enter that as a bug in the tracker, seems we could do a wee bit better, there in the pianoroll ... "In the drum editor mode the velocities don't seem to show up at all?? Though I think that I have seen that it is a bug while searching Google." Ah, you need to actually select a drum note in the left-hand drum map panel. For the drum editor the velocity graph only shows velocities for the currently selected drum note. (Which in some ways is superior to the pianoroll in that it DOES allow to select velocities of same-time notes.) Thanks for reminding us. If you could enter that as a bug as well, because I'd long planned to change that, possibly making it an option. I observed the other day in MusE's older (er, 'newer') branch muse-evolution, that ALL the velocities are shown, but there's no option. I still hold out hope there must be an intelligent way to select same-time velocity bars "sans user-option"... Ha. "Also in the drum editor I'm currently using the Roland MC303 instrument program definition, and all works really well bar the grid and the actual values on the left don't seem to match up. If input something under 'kick drum' nothing is played - switching to the piano role I can see that it's on a note which has no sound assigned to it internally on the MC303. Of course moving it to the proper note works but it just means that I can't use the drum editor due to confusion. Left clicking the sound name in the drum editor does play the sound however; so is there anyway to align them?" Ooh, sounds like a drum map problem, will check. Hm, off the top of my head I'd say the drum map mechanisms should be working so is it possible our MC303 map file is wrong? I'll have to grab the MC303 manual... "Additionally the 'seek forward'/'seek backward'/'record' controls don't seem to function from MMC..... while running from command line, text pops up claiming "not yet implemented". It would be really great to get the transport controls of my Novation Remote working with Muse, though 'play' and 'stop' do work." Right, my department. Let's see if we can change that to "implemented"... I fixed a lot of the sync stuff and I recall researching that particular code and I'm sure I would have tried to implement them so there may be a reason (possibly involving frame time via tempo maps instead of straight ticks, which I think plagued me on one of those MMC locate commands). "Lastly, there seems to be a bug with MIDI clock and start/stop information getting sent together..... while running my Roland MC303 in sequencer mode, if set to 'slave mode' (listen to midi clock and start/stop events) I get clock input showing up on the MC303 but no starting or stopping of the sequencer?? In 'remote mode' start and stop works but the box is clocked internally.... this is kind of odd as checking the same thing using Seq24 all seems fine so I'm not sure where the issue lies?? --in both cases Muse has been instructed to send out MMC/clock and timecode data to the MC303." Mm, should be OK. Are you sure MC303 accepts MMC commands? I think what you want is the "Send midi realtime output" column ("tr") in the sync settings dialog. These are realtime transport commands built in to midi - different from MMC or MTC commands. Should work on virtually all devices. No troubles with my Roland TR-505 or Ensoniq ESQ1 keyboard... FYI: If using Jack midi devices in MusE currently the actual clock signal output may not be very accurate when MusE is Master - ALSA midi devices may give better results ATM. (I need to get in there and put the clock events into Jack properly.) "Apart from these little issues I must say that I'm really impressed and having a lot of fun learning this new software. It's got a lot of potential and character and I'm hoping to start integrating it into a larger setup running with my Mackie DXB and other sound modules and synths." Careful, familiarity breeds contempt. Or an overwhelming obsession to make it better - look at us. Ha! "Just wish that there was support for MOTU audio interfaces on Linux but they don't seem to like the platform :-( I'm personally not a big fan of Apple after the switch from PowerPC processors to Intel and I don't like Windowz either." Hm, FFADO site says that company is "hostile" which is pretty strong. So you really do mean "don't like" not as in "doesn't work well with"... Oh well, each company has their reasons... Tim. |
From: Florian J. <flo...@we...> - 2012-10-11 14:46:46
Attachments:
signature.asc
|
about the "modify velocity" dialog: > I also noticed when you close the dialog the Arranger becomes active > hiding the pianoroll - would be a real annoyance for anyone trying > to work quickly... I cannot reproduce that here. Note that both the arranger and the piano roll offer this menu entry; you probably want to use the piano roll's entry! > "At the same time which is weird is that if I 'modify velocity' to say > 40%, the next time I input a note in the piano role editor the velocity > is at a really low level and not at 100% or whatever the default gets > set to? 100 or whatever?? Again numerical values would be useful here." This dialog is actually intended for quickly altering a whole bunch of notes' velocities, keeping their ratio. That is, you can use it to make a passage more quiet, still keeping "louder" and "quieter" notes in it. The "100%" or "70%" mean: The new velocity will be 70% of the old velocity. (You could reach what you want to do by using 0% and an offset of what you want. "Offset" is in real velocity levels, from 0 to 127; but that's not what the dialog was made for. Like Tim said, there's a toolbar which does what you want.) hope this helps. greetings flo |
From: Kaya S. <kay...@gm...> - 2012-10-11 23:23:38
|
Hi florian, On 10/11/2012 03:46 PM, Florian Jung wrote: > about the "modify velocity" dialog: > >> I also noticed when you close the dialog the Arranger becomes active >> hiding the pianoroll - would be a real annoyance for anyone trying >> to work quickly... > I cannot reproduce that here. Note that both the arranger and the piano > roll offer this menu entry; you probably want to use the piano roll's entry! Tim, actually claimed this and I can reproduce it. While in Piano Roll window selecting the "modify velocity" menu minimizes the Piano Roll window and goes in the "Arrange" window. > > > >> "At the same time which is weird is that if I 'modify velocity' to say >> 40%, the next time I input a note in the piano role editor the velocity >> is at a really low level and not at 100% or whatever the default gets >> set to? 100 or whatever?? Again numerical values would be useful here." > This dialog is actually intended for quickly altering a whole bunch of > notes' velocities, keeping their ratio. That is, you can use it to make > a passage more quiet, still keeping "louder" and "quieter" notes in it. > > The "100%" or "70%" mean: The new velocity will be 70% of the old velocity. > (You could reach what you want to do by using 0% and an offset of what > you want. "Offset" is in real velocity levels, from 0 to 127; but that's > not what the dialog was made for. Like Tim said, there's a toolbar which > does what you want.) Yep, I've managed to start getting the toolbar to work minus the little bug which I posted in my response to Tim; of multiple notes being selected and edited maxes out the velocity to 127. > > > hope this helps. > > greetings > flo Regards, Kaya > > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > > > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: Kaya S. <kay...@gm...> - 2012-10-11 23:18:40
|
On 10/10/2012 09:09 PM, . TERMTECH wrote: > (CC'd to dev list in case they're snoozing...) > > Hello Kaya! Hi Tim, > > Quote: > > "first up MIDI note/event velocities.... I'm currently using the 'Piano > Role' editor to input note events into the system for base and drums. I > haven't however found anywhere to edit individual note velocities by > value." > > I bet you found this already, but look on the 'note info' toolbar. > You'll see boxes for setting notes start time, length, pitch, > on velocity and off velocity, as well as a 'relative or absolute' > mode icon/button. I wasn't quite sure what the velocity on and velocity off meant but now I get it. It works fine... however, perhaps I should post a bug report as when multiple notes are selected and the velocity is changed to say 70, the note velocities end up maxing out to 127?? > > ... > I also noticed when you close the dialog the Arranger becomes active > hiding the pianoroll - would be a real annoyance for anyone trying > to work quickly... Yeah I noticed this too..... that is quite weird. > > "Is there anywhere I can just input the actual value??" > See above: Re the Note Info toolbar. > > "At the same time which is weird is that if I 'modify velocity' to say > 40%, the next time I input a note in the piano role editor the velocity > is at a really low level and not at 100% or whatever the default gets > set to? 100 or whatever?? Again numerical values would be useful here." > > Tested: That is not the 'modify velocity' box's fault. > It appears to be the LAST note that was selected governs the new > note's velocity. Yet there seems to be no way to reset this 'running' > value back to some default other than entering a new value in the > Modify Velocity box or Note Info toolbar (see above). > > So good catch! > Our drum editor has predefined 'levels' depending on accelerator > keys pressed at the time of drawing, so is not affected by this. > Could you possibly perhaps enter that as a bug in the tracker, > seems we could do a wee bit better, there in the pianoroll ... Bug opened. > > "In the drum editor mode the velocities don't seem to show up at all?? > Though I think that I have seen that it is a bug while searching Google." > Ah, you need to actually select a drum note in the left-hand > drum map panel. For the drum editor the velocity graph only shows > velocities for the currently selected drum note. > (Which in some ways is superior to the pianoroll in that it DOES > allow to select velocities of same-time notes.) > Thanks for reminding us. If you could enter that as a bug as well, > because I'd long planned to change that, possibly making it an option. Bug opened. > I observed the other day in MusE's older (er, 'newer') branch > muse-evolution, that ALL the velocities are shown, but there's > no option. I still hold out hope there must be an intelligent way > to select same-time velocity bars "sans user-option"... Ha. > "Also in the drum editor I'm currently using the Roland MC303 instrument > program definition, and all works really well bar the grid and the > actual values on the left don't seem to match up. If input something > under 'kick drum' nothing is played - switching to the piano role I can > see that it's on a note which has no sound assigned to it internally on > the MC303. Of course moving it to the proper note works but it just > means that I can't use the drum editor due to confusion. Left clicking > the sound name in the drum editor does play the sound however; so is > there anyway to align them?" > Ooh, sounds like a drum map problem, will check. > Hm, off the top of my head I'd say the drum map mechanisms should be > working so is it possible our MC303 map file is wrong? > I'll have to grab the MC303 manual... On left shows as "Kick Drum" "Note C2" but then directly right of that nothing plays? If note entered then shows up as C-2 in piano role editor. Does look like a map alignment issue: http://www.rolandus.com/products/details/171/support/ for manual ;-) > > "Additionally the 'seek forward'/'seek backward'/'record' controls don't > seem to function from MMC..... while running from command line, text > pops up claiming "not yet implemented". It would be really great to get > the transport controls of my Novation Remote working with Muse, though > 'play' and 'stop' do work." > Right, my department. > Let's see if we can change that to "implemented"... > I fixed a lot of the sync stuff and I recall researching that > particular code and I'm sure I would have tried to implement them > so there may be a reason (possibly involving frame time via tempo maps > instead of straight ticks, which I think plagued me on one of those > MMC locate commands). > "Lastly, there seems to be a bug with MIDI clock and start/stop > information getting sent together..... while running my Roland MC303 in > sequencer mode, if set to 'slave mode' (listen to midi clock and > start/stop events) I get clock input showing up on the MC303 but no > starting or stopping of the sequencer?? > > In 'remote mode' start and stop works but the box is clocked > internally.... this is kind of odd as checking the same thing using > Seq24 all seems fine so I'm not sure where the issue lies?? > > --in both cases Muse has been instructed to send out MMC/clock and > timecode data to the MC303." > Mm, should be OK. Are you sure MC303 accepts MMC commands? > I think what you want is the "Send midi realtime output" > column ("tr") in the sync settings dialog. These are realtime > transport commands built in to midi - different from > MMC or MTC commands. Should work on virtually all devices. Setting tr worked. It's strange as I had everything checked but I'm sure MMC and MTC caused a conflict somewhere.... the MC303 can be a bit buggy at times. For some reason the Novation Remote 25 won't change the program/bank value either as it simply resets the tone to t-/-- ??? Luckily the "instrument map" in Muse works brilliantly.... oh but another small issue: when selecting a sound, they select correctly but seem labeled wrongly in the arrange window after being set? > > No troubles with my Roland TR-505 or Ensoniq ESQ1 keyboard... Nice kit ;-) > > FYI: If using Jack midi devices in MusE currently the actual clock > signal output may not be very accurate when MusE is Master - > ALSA midi devices may give better results ATM. > (I need to get in there and put the clock events into Jack properly.) Hmm..... I use NTP to clock my system perhaps it would be a good idea to tie the clock from Muse to something like that? Say a publicly available NTP server then calculate the tempo from there? Maybe I'm going a bit too nutty professor on that one though?? Would be kinda funny if NTP server was clocked to GPS effectively making the tempo clocked to a satellite :-) > "Apart from these little issues I must say that I'm really impressed and > having a lot of fun learning this new software. It's got a lot of > potential and character and I'm hoping to start integrating it into a > larger setup running with my Mackie DXB and other sound modules and > synths." > > Careful, familiarity breeds contempt. > Or an overwhelming obsession to make it better - look at us. Ha! I actually prefer things running on Linux and am a real fan of opensource software which is why I've practically moved my whole setup over to it. I'm not a fan of softsynths either so as long as I have a decent sequencer to interface MIDI outboard it's cool. Audio is another issue in terms of hardware support.... ---> > > "Just wish that there was support for MOTU audio interfaces on > Linux but they don't seem to like the platform :-( I'm personally not a > big fan of Apple after the switch from PowerPC processors to Intel and I > don't like Windowz either." > Hm, FFADO site says that company is "hostile" which is pretty strong. > So you really do mean "don't like" not as in "doesn't work well with"... > Oh well, each company has their reasons... Exactly, though would be cool to get Pro Tools or MOTU hardware working with ALSA.... doubt it will ever happen though. M-Audio do seem to work well though not sure about Focusrite though? > > Tim. > Regards, Kaya |
From: Florian J. <flo...@we...> - 2012-10-12 14:31:54
Attachments:
signature.asc
|
Am 12.10.2012 01:18, schrieb Kaya Saman: > I wasn't quite sure what the velocity on and velocity off meant but now > I get it. It works fine... however, perhaps I should post a bug report > as when multiple notes are selected and the velocity is changed to say > 70, the note velocities end up maxing out to 127?? velo on is "the note velocity", this is how hard you pressed the key. velo off is, on (rare) devices which support it, the speed you released the key. with some synthes, you can control the decay phase of the sound by this. yes, the valid range for velocities is 0-127, this is a MIDI limitation. > On left shows as "Kick Drum" "Note C2" but then directly right of that > nothing plays? If note entered then shows up as C-2 in piano role > editor. Does look like a map alignment issue: > > http://www.rolandus.com/products/details/171/support/ > > for manual ;-) are you using old-style or new-style drumtrack? (with a default MusE install, new-style are called "drum track" and old-style are called "old-style drum track", you can change this in GUI options. possibly but unlikely, this can be a problem with my new drumtracks (?) greetings flo |
From: Kaya S. <kay...@gm...> - 2012-10-12 16:21:09
|
On 10/12/2012 03:31 PM, Florian Jung wrote: > Am 12.10.2012 01:18, schrieb Kaya Saman: >> I wasn't quite sure what the velocity on and velocity off meant but now >> I get it. It works fine... however, perhaps I should post a bug report >> as when multiple notes are selected and the velocity is changed to say >> 70, the note velocities end up maxing out to 127?? > velo on is "the note velocity", this is how hard you pressed the key. > velo off is, on (rare) devices which support it, the speed you released > the key. with some synthes, you can control the decay phase of the sound > by this. You mean touch sensitivity and aftertouch? > > yes, the valid range for velocities is 0-127, this is a MIDI limitation. Of course as only possible values can be 0-127 or -63-64 in MIDI. MIDI 1 as it (was) known came about during the 80s when the protocol hadn't really been developed 100%, Microchips where still new and computing had just kicked in - or should that be the 'digital age'? -- additionally MIDI is only 8-bit. MIDI 2 was also developed but I'm not sure if it ever kicked in 100%?? I think mLAN (developed by Yamaha amongst others) was more popular as a sort of 'newer' protocol. --digression aside! > > > >> On left shows as "Kick Drum" "Note C2" but then directly right of that >> nothing plays? If note entered then shows up as C-2 in piano role >> editor. Does look like a map alignment issue: >> >> http://www.rolandus.com/products/details/171/support/ >> >> for manual ;-) > are you using old-style or new-style drumtrack? (with a default MusE > install, new-style are called "drum track" and old-style are called > "old-style drum track", you can change this in GUI options. New style drum editor : Edit -> Drum Track Need to search for the old one as haven't seen it? > > possibly but unlikely, this can be a problem with my new drumtracks (?) Perhaps?? > > > greetings > flo > Regards, Kaya |
From: Kaya S. <kay...@gm...> - 2012-10-13 19:28:26
|
On 10/13/2012 08:04 PM, Tim E. Real wrote: > On October 13, 2012 04:15:11 PM Florian Jung wrote: >> Am 12.10.2012 18:20, schrieb Kaya Saman: >>> You mean touch sensitivity and aftertouch? >> no, i definitely don't mean aftertouch. >> >> i don't know what you mean with "touch sensitivity", probably "the speed >> you press down the key". in that case, this is velo on. >> >> velo off is "the speed you release the key". >> >>> New style drum editor : Edit -> Drum Track >>> >>> Need to search for the old one as haven't seen it? >> i did not mean edit -> drum editor, but the "edit -> add track -> >> new|old style drumtrack". >> >>>> possibly but unlikely, this can be a problem with my new drumtracks (?) >>> Perhaps?? >> well, such a thing actually (tm) cannot happen, because i make no >> mistakes. ;) >> but from time to time, some small undocumented features slip in ;) >> >> open the drum track in question ina drum editor (or rather, some drum >> part on it.) >> >> then click "window configuration" menu. which menu entries do you see? >> if it's only "as subwin", "shares menu+toolbar, "fullscreen", then >> you're facing an old-style drumtrack. >> if there are additionaly a "group" submenu and a "show/hide" submenu, >> then you've a new-style drum track; i'll have a look at this in that case. >> >> greetings >> flo > Confusion alert. > I think Kaya is using release 2.0.1not SVN trunk, > so there's no new drums in the release. > > This problem would be with the 'old' drums. > > Tim. > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user Thanks Tim, yes I did specify my version previously which used the RPM Fusion repo to get it for Fedora 17. I didn't build Muse from the SVN trunk. However, should I try the SVN trunk? I am really after stability which currently I'm getting :-) however, I don't mind trying out something new and helping with debug...... Though I don't know if it will compile with only 512MB RAM? Regards, Kaya |
From: Kaya S. <kay...@gm...> - 2012-10-14 14:46:15
|
On 10/14/2012 02:35 PM, Florian Jung wrote: >> Thanks Tim, >> >> yes I did specify my version previously which used the RPM Fusion repo >> to get it for Fedora 17. I didn't build Muse from the SVN trunk. >> >> However, should I try the SVN trunk? >> >> I am really after stability which currently I'm getting :-) however, I >> don't mind trying out something new and helping with debug...... >> >> Though I don't know if it will compile with only 512MB RAM? >> > > trunk is pretty stable these days. when we do new, experimental > features, we do that on branches, away from trunk; trunk is supposed to > only have working-and-a-bit-tested code, so it should be okay. > > uhm, 512MB RAM is a bit few, but it should work i think. be sure to have > a swap partition enabled, you might need it. > > (btw, i've a 1,4GHz pentium M, and building MusE in debug mode (release > is even slower, because it does optimisations) takes ~15 minutes; with > less RAM (when your system starts swapping), better drink a coffee ;) ) > > > > greetings > flo > Thanks Flo, as long as it's not going to seg-fault every two seconds I will try. I hope it will work as I have allocated 3GB swap on it but in normal runtime mode, XDM/fluxbox/qjackctl/muse2 - the system already uses a lot of swap. Btw did I mention that 8MB is used for video and additionally the system has memory leak problems :-( It's a 1.xGHz Centrino...... Hmm cup of coffee sounds sounds nice, care to join for a remote or virtual cup?(I'm buying/or making!) :-) Regards, Kaya |
From: Florian J. <flo...@we...> - 2012-10-14 15:03:33
Attachments:
signature.asc
|
Am 14.10.2012 16:46, schrieb Kaya Saman: > On 10/14/2012 02:35 PM, Florian Jung wrote: >>> Thanks Tim, >>> >>> yes I did specify my version previously which used the RPM Fusion repo >>> to get it for Fedora 17. I didn't build Muse from the SVN trunk. >>> >>> However, should I try the SVN trunk? >>> >>> I am really after stability which currently I'm getting :-) however, I >>> don't mind trying out something new and helping with debug...... >>> >>> Though I don't know if it will compile with only 512MB RAM? >>> >> >> trunk is pretty stable these days. when we do new, experimental >> features, we do that on branches, away from trunk; trunk is supposed to >> only have working-and-a-bit-tested code, so it should be okay. >> >> uhm, 512MB RAM is a bit few, but it should work i think. be sure to have >> a swap partition enabled, you might need it. >> >> (btw, i've a 1,4GHz pentium M, and building MusE in debug mode (release >> is even slower, because it does optimisations) takes ~15 minutes; with >> less RAM (when your system starts swapping), better drink a coffee ;) ) >> >> >> >> greetings >> flo >> > > Thanks Flo, > > as long as it's not going to seg-fault every two seconds I will try. it certainly won't ;) > > I hope it will work as I have allocated 3GB swap on it but in normal > runtime mode, XDM/fluxbox/qjackctl/muse2 - the system already uses a lot > of swap. i can compile with a total of 1.5GB memory usage. it you're getting problems, then don't compile with the -DCMAKE_RELEASE_TYPE option. > > Btw did I mention that 8MB is used for video and additionally the system > has memory leak problems :-( > > It's a 1.xGHz Centrino...... > you need a new machine ;) (i'm sitting on such a laptop too. terrible :D ) > Hmm cup of coffee sounds sounds nice, care to join for a remote or > virtual cup?(I'm buying/or making!) :-) unfortunately, i don't drink coffee. But tea ;)) xD greetings and good luck with compiling flo |
From: Florian J. <flo...@we...> - 2012-10-13 14:15:25
Attachments:
signature.asc
|
Am 12.10.2012 18:20, schrieb Kaya Saman: > You mean touch sensitivity and aftertouch? no, i definitely don't mean aftertouch. i don't know what you mean with "touch sensitivity", probably "the speed you press down the key". in that case, this is velo on. velo off is "the speed you release the key". > New style drum editor : Edit -> Drum Track > > Need to search for the old one as haven't seen it? i did not mean edit -> drum editor, but the "edit -> add track -> new|old style drumtrack". >> possibly but unlikely, this can be a problem with my new drumtracks (?) > Perhaps?? well, such a thing actually (tm) cannot happen, because i make no mistakes. ;) but from time to time, some small undocumented features slip in ;) open the drum track in question ina drum editor (or rather, some drum part on it.) then click "window configuration" menu. which menu entries do you see? if it's only "as subwin", "shares menu+toolbar, "fullscreen", then you're facing an old-style drumtrack. if there are additionaly a "group" submenu and a "show/hide" submenu, then you've a new-style drum track; i'll have a look at this in that case. greetings flo |
From: Tim E. R. <ter...@ro...> - 2012-10-13 19:04:38
|
On October 13, 2012 04:15:11 PM Florian Jung wrote: > Am 12.10.2012 18:20, schrieb Kaya Saman: > > You mean touch sensitivity and aftertouch? > > no, i definitely don't mean aftertouch. > > i don't know what you mean with "touch sensitivity", probably "the speed > you press down the key". in that case, this is velo on. > > velo off is "the speed you release the key". > > > New style drum editor : Edit -> Drum Track > > > > Need to search for the old one as haven't seen it? > > i did not mean edit -> drum editor, but the "edit -> add track -> > new|old style drumtrack". > > >> possibly but unlikely, this can be a problem with my new drumtracks (?) > > > > Perhaps?? > > well, such a thing actually (tm) cannot happen, because i make no > mistakes. ;) > but from time to time, some small undocumented features slip in ;) > > open the drum track in question ina drum editor (or rather, some drum > part on it.) > > then click "window configuration" menu. which menu entries do you see? > if it's only "as subwin", "shares menu+toolbar, "fullscreen", then > you're facing an old-style drumtrack. > if there are additionaly a "group" submenu and a "show/hide" submenu, > then you've a new-style drum track; i'll have a look at this in that case. > > greetings > flo Confusion alert. I think Kaya is using release 2.0.1not SVN trunk, so there's no new drums in the release. This problem would be with the 'old' drums. Tim. |
From: Florian J. <flo...@we...> - 2012-10-14 13:35:21
Attachments:
signature.asc
|
Am 13.10.2012 21:28, schrieb Kaya Saman: > On 10/13/2012 08:04 PM, Tim E. Real wrote: >> On October 13, 2012 04:15:11 PM Florian Jung wrote: >>> Am 12.10.2012 18:20, schrieb Kaya Saman: >>>> You mean touch sensitivity and aftertouch? >>> no, i definitely don't mean aftertouch. >>> >>> i don't know what you mean with "touch sensitivity", probably "the speed >>> you press down the key". in that case, this is velo on. >>> >>> velo off is "the speed you release the key". >>> >>>> New style drum editor : Edit -> Drum Track >>>> >>>> Need to search for the old one as haven't seen it? >>> i did not mean edit -> drum editor, but the "edit -> add track -> >>> new|old style drumtrack". >>> >>>>> possibly but unlikely, this can be a problem with my new drumtracks (?) >>>> Perhaps?? >>> well, such a thing actually (tm) cannot happen, because i make no >>> mistakes. ;) >>> but from time to time, some small undocumented features slip in ;) >>> >>> open the drum track in question ina drum editor (or rather, some drum >>> part on it.) >>> >>> then click "window configuration" menu. which menu entries do you see? >>> if it's only "as subwin", "shares menu+toolbar, "fullscreen", then >>> you're facing an old-style drumtrack. >>> if there are additionaly a "group" submenu and a "show/hide" submenu, >>> then you've a new-style drum track; i'll have a look at this in that case. >>> >>> greetings >>> flo >> Confusion alert. >> I think Kaya is using release 2.0.1not SVN trunk, >> so there's no new drums in the release. >> >> This problem would be with the 'old' drums. >> >> Tim. >> >> ------------------------------------------------------------------------------ >> Don't let slow site performance ruin your business. Deploy New Relic APM >> Deploy New Relic app performance management and know exactly >> what is happening inside your Ruby, Python, PHP, Java, and .NET app >> Try New Relic at no cost today and get our sweet Data Nerd shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> _______________________________________________ >> Lmuse-user mailing list >> Lmu...@li... >> https://lists.sourceforge.net/lists/listinfo/lmuse-user > > Thanks Tim, > > yes I did specify my version previously which used the RPM Fusion repo > to get it for Fedora 17. I didn't build Muse from the SVN trunk. > > However, should I try the SVN trunk? > > I am really after stability which currently I'm getting :-) however, I > don't mind trying out something new and helping with debug...... > > Though I don't know if it will compile with only 512MB RAM? > trunk is pretty stable these days. when we do new, experimental features, we do that on branches, away from trunk; trunk is supposed to only have working-and-a-bit-tested code, so it should be okay. uhm, 512MB RAM is a bit few, but it should work i think. be sure to have a swap partition enabled, you might need it. (btw, i've a 1,4GHz pentium M, and building MusE in debug mode (release is even slower, because it does optimisations) takes ~15 minutes; with less RAM (when your system starts swapping), better drink a coffee ;) ) greetings flo > > Regards, > > Kaya > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user > |
From: Tim E. R. <ter...@ro...> - 2012-10-20 07:17:06
|
Hello. I meant to send this last week. A bit rambling but FWIW try some of the suggestions. Also I just updated the SVN trunk with some related fixes. How's it going with that SVN, did you try it? Tim. . . . On October 10, 2012 01:09:46 PM . TERMTECH wrote: Quote: "Also in the drum editor I'm currently using the Roland MC303 instrument program definition, and all works really well bar the grid and the actual values on the left don't seem to match up. If input something under 'kick drum' nothing is played - switching to the piano role I can see that it's on a note which has no sound assigned to it internally on the MC303. Of course moving it to the proper note works but it just means that I can't use the drum editor due to confusion. Left clicking the sound name in the drum editor does play the sound however; so is there anyway to align them?" "Ooh, sounds like a drum map problem, will check. Hm, off the top of my head I'd say the drum map mechanisms should be working so is it possible our MC303 map file is wrong? I'll have to grab the MC303 manual..." My mistake sorry, you said the MC303 instrument, not drum map. So the drum map's Port and Channel columns are the same for all drums? And the Channel column says all 10? For MC303 this column must say ch 10. And the sequence of note names in the 'anote' column is correct? No duplicates? If in doubt, execute 'reset GM map' from the Function menu. Quote: "On left shows as "Kick Drum" "Note C2" but then directly right of that nothing plays? If note entered then shows up as C-2 in piano role editor. Does look like a map alignment issue" Huh? C-2 should be Hi-Mid Tom in the default GM map. What is kick drum? I don't see it in the GM map. I see Acoustic Bass Drum and Bass Drum 1. Not attempting to use the SC-88 map I hope... Are you in fact using a drum map? Did you at some point 'Load' one of MusE's drum maps? Ah... Then it may have been saved with your song that way! Again, if in doubt, execute 'reset GM map' from the Function menu. . . . If the MC303's drum notes do not conform to the standard default GM map, you need a drum map for the MC303 and load that drum map into the drum editor. There's menu items for loading and saving. Er, but strangely there IS NO MC303 drum map in our little MusE. However according to the MC303 manual the drum maps are all pretty much GM compatible so there shouldn't be a need for a custom map for now... So what's wrong then ? I'm looking at the actual patch numbers for for our MC303 instrument def file they seem suspicous. The drums are all at High Bank = 65. The manual does not mention any specific bank number for drums, only that they be on channel 10. According to http://www.synthman.com/roland/support/supplementalnotes/SUPNOTES/MC303MID.html The rhythm sets in the MC-303 are assigned to MIDI channel 10. There is a list of the rhythm sets on pages 90-93 in your Owner's Manual. You do not need to send a bank message (CC0/32) to select the different sets - only a program change message on MIDI channel 10. So I wonder if actually sending that 65 bank number is selecting the wrong sounds? On your drum tracks, what instrument patch name and number is being shown in the midi track info panel? It should say 808 or 909 etc. and the HBank number should say 65 and the LBank number should say 1. Can you try changing that to both bank numbers 'off' and leave the Prog number at 1, 9, 17, 25 etc whatever the number of the selected kit name? (You can also view and edit our MC303 Instrument in the Instrument Editor.) Also ensure that in the drum list panel on the left of the drum editor, all the notes say channel 10, because MC303 only does drums on 10. Now, I should say that the next upcoming release has a new drum track made by Flo, it is substantially different from the current drum tracks and supports creating drum ranges and maps right in the Instrument Editor itself - so you'll be able to create them for your MC-303. And... contribute them back to MusE ;-) Anyway it's more straightforward to use than current drum maps, you just dial in the port and channel in the track list and there's no such columns to worry about in the drum editor itself. But then, having said all that, you can actually hear the drum sounds when clicking the names in the drum list. Strange. But not when playing notes. Tim. |
From: Kaya S. <kay...@gm...> - 2012-10-24 16:30:13
|
Hi Tim, sorry for the late response! See comments in line: On 10/20/2012 08:02 AM, Tim E. Real wrote: > Hello. > I meant to send this last week. > A bit rambling but FWIW try some of the suggestions. > Also I just updated the SVN trunk with some related fixes. > How's it going with that SVN, did you try it? > Tim. I downloaded the SVN version after Florian's last mail. Installation wasn't an issue... mainly I thought I would run out of RAM and that the system would overheat but it seemed to be fine. Am just using it now :-) It's good though I don't see many changes to what I was using previously. > > . . . > On October 10, 2012 01:09:46 PM . TERMTECH wrote: > > Quote: > "Also in the drum editor I'm currently using the Roland MC303 instrument > program definition, and all works really well bar the grid and the > actual values on the left don't seem to match up. If input something > under 'kick drum' nothing is played - switching to the piano role I can > see that it's on a note which has no sound assigned to it internally on > the MC303. Of course moving it to the proper note works but it just > means that I can't use the drum editor due to confusion. Left clicking > the sound name in the drum editor does play the sound however; so is > there anyway to align them?" > > "Ooh, sounds like a drum map problem, will check. > Hm, off the top of my head I'd say the drum map mechanisms should be > working so is it possible our MC303 map file is wrong? > I'll have to grab the MC303 manual..." > > > My mistake sorry, you said the MC303 instrument, not drum map. > > So the drum map's Port and Channel columns are the same for all drums? > And the Channel column says all 10? For MC303 this column must say ch 10. > And the sequence of note names in the 'anote' column is correct? > No duplicates? If in doubt, execute 'reset GM map' from the Function menu. Sorry if I was unclear. I have connected my MC303 to my Emagic MT4's port 1. So for that specific port I selected the MC303 instrument. My MC303 is running in Module Mode and not Sequencer Mode..... I then created a MIDI track and selected the "drum editor" from the Edit menu. On the left pane the sound values were correct but the grid didn't seem to match up. Hence your comment below: > > Quote: > "On left shows as "Kick Drum" "Note C2" but then directly right of that > nothing plays? If note entered then shows up as C-2 in piano role > editor. Does look like a map alignment issue" > > Huh? C-2 should be Hi-Mid Tom in the default GM map. > What is kick drum? I don't see it in the GM map. I see > Acoustic Bass Drum and Bass Drum 1. Not attempting to use the > SC-88 map I hope... > Are you in fact using a drum map? Did you at some point 'Load' one of > MusE's drum maps? > Ah... Then it may have been saved with your song that way! > Again, if in doubt, execute 'reset GM map' from the Function menu. > > . . . > > If the MC303's drum notes do not conform to the standard default GM map, > you need a drum map for the MC303 and load that drum map into the > drum editor. There's menu items for loading and saving. > > Er, but strangely there IS NO MC303 drum map in our little MusE. > > However according to the MC303 manual the drum maps are all pretty much > GM compatible so there shouldn't be a need for a custom map for now... > > So what's wrong then ? > > I'm looking at the actual patch numbers for for our MC303 instrument > def file they seem suspicous. > > The drums are all at High Bank = 65. > > The manual does not mention any specific bank number for drums, > only that they be on channel 10. I think it's only program change that the MC303 responds to on channel 10. Hmm.... looks like I might have to attempt to create a map then. > > According to > http://www.synthman.com/roland/support/supplementalnotes/SUPNOTES/MC303MID.html > > The rhythm sets in the MC-303 are assigned to MIDI channel 10. There is a > list of the rhythm sets on > pages 90-93 in your Owner's Manual. You do > not need to send a bank message (CC0/32) to select the > different sets - > only a program change message on MIDI channel 10. > > So I wonder if actually sending that 65 bank number is selecting the wrong > sounds? > > On your drum tracks, what instrument patch name and number is being shown > in the midi track info panel? > It should say 808 or 909 etc. and the HBank number should say 65 > and the LBank number should say 1. HBank and LBank are both off while program is set to 10..... (not sure in Module mode if this has any affect though) And per the above I think that the "Drum Editor" from the Edit menu is using a GM map. The MC303 in either Sequencer or Module mode doesn't conform to GM standards at all..... I am even unable to change program/bank from my Novation Remote 25 controller as attempting to do so just resets the sound to 00 and nothing gets played. > > Can you try changing that to both bank numbers 'off' and leave the Prog > number at 1, 9, 17, 25 etc whatever the number of the selected kit name? > > (You can also view and edit our MC303 Instrument in the Instrument Editor.) I think I will have to try looking at the instrument editor and seeing if I can mend anything from there. It will also be a good precursor to setting up a Novation Nova instrument too amongst others. > > Also ensure that in the drum list panel on the left of the drum editor, > all the notes say channel 10, because MC303 only does drums on 10. The instrument/track itself was put onto 10 so I'm sure that will be sufficient unless I am missing anything else? > > Now, I should say that the next upcoming release has a new drum track > made by Flo, it is substantially different from the current drum tracks > and supports creating drum ranges and maps right in the Instrument > Editor itself - so you'll be able to create them for your MC-303. > And... contribute them back to MusE ;-) > > Anyway it's more straightforward to use than current drum maps, > you just dial in the port and channel in the track list and there's no > such columns to worry about in the drum editor itself. > > But then, having said all that, you can actually hear the drum sounds > when clicking the names in the drum list. Strange. > But not when playing notes. I will take a look at the relevant places and see if I can edit any of them as per above. The good thing is that I could create a few new instruments and upload them to the trunk of send it to someone to evaluate and check. This is a great idea! Outside of the Novation Nova and Roland MC303 I have quite a few more pieces of kit which would be great to have instruments for. Just need to get them out of their boxes in order to start playing again (lack of space at home caused me to have to pack most things up). Stuff like: Yamaha S80 Yamaha CS6r Yamaha VL70m Quasimidi Quasar Akai S5000 Alesis QS6 EMU Audity 2000 And probably even the DAW mode on my Mackie DXB would be great to integrate!! Anyway, will start to look at the MC303 now and see what I can come up with. :-) Regards, Kaya > > > Tim. > |