(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. ------------------------------------------------------------------------------ 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-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
