I just tried with Zebra and both works as expected...
I can use my mousewheel to scroll in the browser and the arrow up/down keys to step through the presets
Personal thoughts after trying Mulab for some weeks....
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Are we talking Mac version because mine doesn't...
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
I checked using the mousewheel in VST editors on OSX and indeed see that there is an issue. Unbelievable that OSX is causing so many difficulties 
The mousewheel events should simply be sent to the UI component below the mouse, of course, but there seems to be a problem somewhere. I've taken note and will evaluate further when working on MuLab 5/MUX 2, as that R&D stage will include a deep review of the OSX abstraction layer.
The mousewheel events should simply be sent to the UI component below the mouse, of course, but there seems to be a problem somewhere. I've taken note and will evaluate further when working on MuLab 5/MUX 2, as that R&D stage will include a deep review of the OSX abstraction layer.-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Sometimes it's the little things... Crazy thing is, I still prefer MuLab to anything else I've used lately and I'm still putting off purchasing Logic 9. I used to use various drum plugs to do beats in Logic, because I don't like the matrix for drums... (control adjustment is crap) and the hyper editor is pretty awful. MuLabs editor just seems to be "right" to me and makes drum programming pretty painless. Plus the MuDrum is very capable if not awesome. So, I'm holding out for the Mac fixes which I'm sure are coming. Thanks!
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Another question I'm trying to figure out... is it possible to do a bass line with one pad of the MuDrum... i.e. have pitch editable per hit??? I was thinking this was possible, but can't seem to make this work.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
You could automate the pitch parameter(s) of the MuPad.
Drag-drop a parameter on the the [+] track button, double-click-drag in the composer on that track to create a new automation part, double-click to edit it and have fun
Drag-drop a parameter on the the [+] track button, double-click-drag in the composer on that track to create a new automation part, double-click to edit it and have fun
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
I was trying to do that in the midi editor with the controller window at the bottom. Is that not possible? By drawing in the changes.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
NB: You can also simply record any parameter tweaks of course: Hit record and tweak the parameter(s).
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
You can draw parameter automations using breakpoint envelopes, cfr my description above. If you would really want to draw it using a MIDI controller you could setup a MIDI controller mapping towards that parameter and then automate that MIDI controller. So yes it's possible too, but it's less direct.DHR53 wrote:I was trying to do that in the midi editor with the controller window at the bottom. Is that not possible? By drawing in the changes.
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Hmmm... I must be doing something wrong then. I have a Bass preset loaded into element 3, then I add a map controller for mod wheel to parameter tone. Then go to a sequence and select the "mod wheel" at the bottom of the sequence editor window. If I draw in changes it's not affecting the controls for that element in the MuDrum?
-
- KVRist
- Topic Starter
- 54 posts since 5 Sep, 2012
This has been a great thread to follow and I must say that I am a bit surprised over the positive tone here. If you are in a forum and you dare to criticize, even if you do it in a constructive way, my experience is that it can be seen as provoking by some. I am really pleased that my post got this kind of constructive response here… ;o)
As I did assume not many like all my suggestions for Mulab development and I analyze it like this:
If you are using Mulab as you primarily DAW at this moment, you are probably not into loops. That might be the reason that the answers in the thread don't think suggestions 1 and 2 are of any value for them. But I might be crucial for somebody that has not decided yet. If Mulab is to be a bigger DAW, and I dont know if that is a goal or not, then the feature list can not only be based on the current users.
When it comes to number 3 it is a bit harder to understand as that is probably more easy to implement. If you mostly play keyboard it might be easier to click on the keyboard to turn recordinng on and of but as a guitarist for example it is a bit more fiddly maybe. I am not sure but for me it would be real handy and I can't see it spoil the simplicity of the interface to put two other markers on the timeline.
Number 4 and 5 seems to be recognized as important by more people. That might because most people switch computers now and then and suddenly has a multicore machine and would like for Mulab to support that. Freeze i also about maintaining the computer resources in a way... and if you are using a lot of VST:s that can be vital and for newcommers that it can be done in an intuitive way.
As I did assume not many like all my suggestions for Mulab development and I analyze it like this:
If you are using Mulab as you primarily DAW at this moment, you are probably not into loops. That might be the reason that the answers in the thread don't think suggestions 1 and 2 are of any value for them. But I might be crucial for somebody that has not decided yet. If Mulab is to be a bigger DAW, and I dont know if that is a goal or not, then the feature list can not only be based on the current users.
When it comes to number 3 it is a bit harder to understand as that is probably more easy to implement. If you mostly play keyboard it might be easier to click on the keyboard to turn recordinng on and of but as a guitarist for example it is a bit more fiddly maybe. I am not sure but for me it would be real handy and I can't see it spoil the simplicity of the interface to put two other markers on the timeline.
Number 4 and 5 seems to be recognized as important by more people. That might because most people switch computers now and then and suddenly has a multicore machine and would like for Mulab to support that. Freeze i also about maintaining the computer resources in a way... and if you are using a lot of VST:s that can be vital and for newcommers that it can be done in an intuitive way.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Make sure you're targetting the module that contains the mapping.DHR53 wrote:Hmmm... I must be doing something wrong then. I have a Bass preset loaded into element 3, then I add a map controller for mod wheel to parameter tone. Then go to a sequence and select the "mod wheel" at the bottom of the sequence editor window. If I draw in changes it's not affecting the controls for that element in the MuDrum?
Anyway, i'm wondering: If you want to sequence a bass sound, why don't you simply sequence it directly using a sequence part and the note editor?
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Well, since I can load an instrument into the pads... it seemed like a good idea to create a bassline within the drum track. A number of drum synths let you adjust pitch of notes by beat so I was looking into what I could do that way.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Great that you take the time to constructively feedbackvoidpipe wrote:This has been a great thread to follow and I must say that I am a bit surprised over the positive tone here. If you are in a forum and you dare to criticize, even if you do it in a constructive way, my experience is that it can be seen as provoking by some. I am really pleased that my post got this kind of constructive response here… ;o)
I'm always eager to learn what's really important to you to make MuLab and the MUX the musical tools you want. Of course this differs from person to person, and so that's why there already is a looong wishlist. But then it becomes a matter to know what's wanted most by most people. So there again: Good that you let us know Your most wanted feature requests.
Indeed. Yes it's definitely the goal to let grow MuLab and the MUX, both commercially (in a respectful way) and creatively.If you are using Mulab as you primarily DAW at this moment, you are probably not into loops. That might be the reason that the answers in the thread don't think suggestions 1 and 2 are of any value for them. But I might be crucial for somebody that has not decided yet. If Mulab is to be a bigger DAW, and I dont know if that is a goal or not, then the feature list can not only be based on the current users.
About working with loops: Did you already try out the "Import Sample Loop" function in the Session menu? This function auto splits up a sample loop and creates a sequence that plays the slices. If you change the tempo the sliced loop will follow the tempo. And you can rearrange the slices as you want.
What about that? If it's not what you're looking for feel free to point to another music app that has implemented it the way you want.
As i wrote before i do already have an initial design of MuLab 5/MUX 2 and i'll tell you that your FR #2 (custom grooves/grids), FR #4 (track freeze) and FR #5 (multi-core support) are all on that initial M5 wishlist.
I need to further work out that initial M5 design though (want to keep it compact so that M5 will be available sooner), so nothing is definitive yet. Which is a nice state because things are very open atm. Listening to a lot of music these days, doing jams myself, explore other music tools etc... all very fascinating
By the way: Any of your musics online?
Last edited by MuTools on Sun Oct 07, 2012 10:42 pm, edited 1 time in total.