Hi,
Wouldn't it be easier when Tempo Changes are actually visible in the Composer? There's no Locator being added automatically so I can't see where the Tempo Changes are exactly unless I've added a Locator manually (which I didn't 'cause I'm Mulab noob). Seems to me there's no valid reason not to auto-include a Locator or something else that displays the Tempo Change.
I can't find a way to delete all these invisible Tempo Changes all at once except in the List Editor, which is pretty well hidden from a new user as well as the Tempo Changes themselves. This page describes the List Editor, but not how to actually open the List Editor: http://www.mutools.com/info/docs/mulab/ ... ditor.html
I just figured I should post this as positive criticism. Of course, if I overlooked something, do tell.
Other problems:
re-selecting Rack when testing sounds for Live playing:
When testing out send effects for my midi keyboard, like MuVerb, I keep having to re-select the Rack with the instrument for which I'm testing in order to actually hear the instrument because I got a separate rack for MuVerb. Of course I could use it as an Insert effect on the Instrument's Rack, but I want a send effect... Normally, to click to select the active is indeed very handy, but when testing sounds for Live playing via midi keyboard it would be handy to have some override or toggle option that will enable me to keep playing the sound on midi keyboard after clicking on another rack. Other music apps look at which midi channel is selected on the keyboard. The rack that have this channel set will be heard, which also would mean you can hear several racks at once if desired.
Audio crack:
When started a guitar recording at a specific location, there's a momentary crackling sound in the audio when playing back the recording. I assume this can be avoided when starting the recording earlier, before actually playing. But that's not handy when it comes to recording at specific places. I don't have this problem in Reaper (just to indicate I tested in another app).
(in)Visibility of Tempo Changes & other problems
-
- KVRist
- 83 posts since 19 May, 2012
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
You can set up fixed MIDI Input Channel Targets by using Session->Edit MIDI Input Channel Targets. However, I'd like to agree that a quick'n'easy way (e.g. right-click menu option) of assigning a target would be handy.megalodonnl wrote:Normally, to click to select the active is indeed very handy, but when testing sounds for Live playing via midi keyboard it would be handy to have some override or toggle option that will enable me to keep playing the sound on midi keyboard after clicking on another rack. Other music apps look at which midi channel is selected on the keyboard. The rack that have this channel set will be heard, which also would mean you can hear several racks at once if desired.
All I can think of here is that Reaper's auto-fade in is hiding the problem. I'm imagining it's due to starting in the middle of a wave cycle. (I don't record audio in, so I could be completely wrong!)megalodonnl wrote:Audio crack:
When started a guitar recording at a specific location, there's a momentary crackling sound in the audio when playing back the recording. I assume this can be avoided when starting the recording earlier, before actually playing. But that's not handy when it comes to recording at specific places. I don't have this problem in Reaper (just to indicate I tested in another app).
-
- KVRist
- Topic Starter
- 83 posts since 19 May, 2012
No, I have no (auto)fade-ins.Audio crack:All I can think of here is that Reaper's auto-fade in is hiding the problem. I'm imagining it's due to starting in the middle of a wave cycle. (I don't record audio in, so I could be completely wrong!)
Also:
- When I select midi notes in the Sequencer and choose 'mute' via RMB menu, it mutes ALL notes... So how to specifically mute certain notes and leave the rest untouched?
- When having selected a group of midi notes in the Sequencer and want to get rid of a specific midi note I would expect this to be done with CTRL key, as this is common for Windows apps.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
You edit them out in Reaper? Why on earth do you do that? Or is there some other way to get rid of them that I've not found..? (Wrong forum... sorry...)megalodonnl wrote:No, I have no (auto)fade-ins.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
SESSION menu -> Use Automatic/Manual MIDI Input Focus.megalodonnl wrote:re-selecting Rack when testing sounds for Live playing:
When testing out send effects for my midi keyboard, like MuVerb, I keep having to re-select the Rack with the instrument for which I'm testing in order to actually hear the instrument because I got a separate rack for MuVerb. Of course I could use it as an Insert effect on the Instrument's Rack, but I want a send effect... Normally, to click to select the active is indeed very handy, but when testing sounds for Live playing via midi keyboard it would be handy to have some override or toggle option that will enable me to keep playing the sound on midi keyboard after clicking on another rack. Other music apps look at which midi channel is selected on the keyboard. The rack that have this channel set will be heard, which also would mean you can hear several racks at once if desired.
Also see more detailed info here http://www.mutools.com/info/docs/mulab/main-menu.html
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
That Mute function is under the part sub-menu, it's a sequence part function, so it mutes the whole sequence part. No way yet to mute individual notes.megalodonnl wrote:When I select midi notes in the Sequencer and choose 'mute' via RMB menu, it mutes ALL notes... So how to specifically mute certain notes and leave the rest untouched?
-
- KVRist
- Topic Starter
- 83 posts since 19 May, 2012
OK thanks for the quick replies.
I overlooked the Automatic/Manual MIDI Input Focus - toggle. It works great.
The muting of individual midi notes would be nice to have indeed (but I know it's just one person doing the coding, etc.).
And Peter: no I didn't change anything like that, so perhaps you're correct that it uses some tactic to avoid this problem. I don't know what's under the hood of these apps (I'm no coder). But again, perhaps the workaround I described could work. I've noticed there are more apps that have this crack in the beginning of audio recording, perhaps even Reaper from time to time (I think I've read about it in the manual), but I just didn't notice it in Reaper when I recently did some recordings.
BTW: I think Mulab is bit too addicting
I've been up all night. I've always been a musician that was more interested in physical instrumentation instead of electronic music and now I'm getting interested in doing some of my compositions in Mulab (electronic music) style 
I haven't figured out how to use the 'Mini Arpeggiator' though... Is this the only Arp. in Mulab?
I overlooked the Automatic/Manual MIDI Input Focus - toggle. It works great.
The muting of individual midi notes would be nice to have indeed (but I know it's just one person doing the coding, etc.).
And Peter: no I didn't change anything like that, so perhaps you're correct that it uses some tactic to avoid this problem. I don't know what's under the hood of these apps (I'm no coder). But again, perhaps the workaround I described could work. I've noticed there are more apps that have this crack in the beginning of audio recording, perhaps even Reaper from time to time (I think I've read about it in the manual), but I just didn't notice it in Reaper when I recently did some recordings.
BTW: I think Mulab is bit too addicting
I've been up all night. I've always been a musician that was more interested in physical instrumentation instead of electronic music and now I'm getting interested in doing some of my compositions in Mulab (electronic music) style I haven't figured out how to use the 'Mini Arpeggiator' though... Is this the only Arp. in Mulab?