MuLab 9.0.59 App + Plugin
- KVRAF
- 3204 posts since 17 Apr, 2010 from Slovenia
Dang, that sounds brilliant! I love it when things are open like that. Fantastic idea with the drag'n'drop into the track itself. I will definitely play with that. 
- KVRist
- 212 posts since 14 Feb, 2021
That's a very nice tip. I would recommend add it to documentationmutools wrote: Sat Jun 11, 2022 10:28 am Tip: You can also drag-drop a parameter onto a track, that will create an automation clip for that parameter. This can be done on any track that targets that module. (that module itself, not a parent module or rack)
All MuLab tracks are hybrid.
You can put audio + events + automation onto it.
It is the track's target module that will receive + process the track's audio + events + automation.
If you put audio on a track that targets a module without an audio input, that track audio won't have any effect. You can intermix audio + events + automation clips on a track as you wish.
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 434 posts since 17 Nov, 2020
With the latest update Mulab Plugin demo songs lack event input on the project level.
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
The project event input is defined by the project, not by MuLab.
So i don't understand how the latest update can change that.
Can you please elaborate?
So i don't understand how the latest update can change that.
Can you please elaborate?
-
- KVRian
- 552 posts since 22 Jun, 2019
Hi,
I'm trying to use mulab plugin as a poly at midi editor in reaper.
When composer is set to sync to host position, if reaper's playing is stopped, when I click on record (in mulab pugin I mean), composer start recording immediately.
I'd prefer it to 'wait' until I hit play on reaper, so I could record my reaper Midi data in mulab without losing sync. Is there a way to achieve that ?
Note that I'm still on 39 beta. I have yet to test it on 41...
I'm trying to use mulab plugin as a poly at midi editor in reaper.
When composer is set to sync to host position, if reaper's playing is stopped, when I click on record (in mulab pugin I mean), composer start recording immediately.
I'd prefer it to 'wait' until I hit play on reaper, so I could record my reaper Midi data in mulab without losing sync. Is there a way to achieve that ?
Note that I'm still on 39 beta. I have yet to test it on 41...
-
- KVRist
- 434 posts since 17 Nov, 2020
Fair enough, I just had the expactation to select a rack and play with midi keyboard. It definitely isn't a result of recent update.mutools wrote: Sat Jun 11, 2022 4:44 pm The project event input is defined by the project, not by MuLab.
So i don't understand how the latest update can change that.
Can you please elaborate?
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
That's not yet supported. Also not in M9.0.41. It won't be an ambition for M9.0.ElVincente wrote: Sat Jun 11, 2022 4:47 pm Hi,
I'm trying to use mulab plugin as a poly at midi editor in reaper.
When composer is set to sync to host position, if reaper's playing is stopped, when I click on record (in mulab pugin I mean), composer start recording immediately.
I'd prefer it to 'wait' until I hit play on reaper, so I could record my reaper Midi data in mulab without losing sync. Is there a way to achieve that ?
Note that I'm still on 39 beta. I have yet to test it on 41...
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
Ok, thx for elaborating. There indeed is a difference between playing live MIDI in MuLab App and MuLab Plugin because of the different context. Essentially it all works the same, the "Project MIDI Input Targets" define how MIDI input is handled, but there is a different default in App vs Plugin, but you can edit it as you wish.humanboeing wrote: Sat Jun 11, 2022 5:12 pm Fair enough, I just had the expactation to select a rack and play with midi keyboard. It definitely isn't a result of recent update.
See https://www.mutools.com/info/M9/docs/mu ... uting.html
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
MuLab App 9.0.42 is available in https://www.mutools.com/mulab/app/latest-binary
MuLab Plugin 9.0.42 is available in https://www.mutools.com/mulab/plugin/latest-binary
This update fixes a recent new bug regarding window sizing.
MuLab Plugin 9.0.42 is available in https://www.mutools.com/mulab/plugin/latest-binary
This update fixes a recent new bug regarding window sizing.
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRian
- 552 posts since 22 Jun, 2019
Ok, anyway I can still press play on reaper before hitting record on mulab, a little less convenient but seems to be working fine.mutools wrote: Sat Jun 11, 2022 6:05 pmThat's not yet supported. Also not in M9.0.41. It won't be an ambition for M9.0.ElVincente wrote: Sat Jun 11, 2022 4:47 pm Hi,
I'm trying to use mulab plugin as a poly at midi editor in reaper.
When composer is set to sync to host position, if reaper's playing is stopped, when I click on record (in mulab pugin I mean), composer start recording immediately.
I'd prefer it to 'wait' until I hit play on reaper, so I could record my reaper Midi data in mulab without losing sync. Is there a way to achieve that ?
Note that I'm still on 39 beta. I have yet to test it on 41...
-
- KVRist
- 434 posts since 17 Nov, 2020
There's a visual glitch on the rack desk when triggering it via a shortcut (mine is F10), Mulab App
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 434 posts since 17 Nov, 2020
After triggering either project modular area or the browser via a shortcut, the rack desk cannot be triggered through a shortcut, I have to click anywhere first to be able to do it.
This is seems to be only true for new composers, that is:
1. Open new project
2. Delete the composer
3. Create a new composer and make it project default module
This is seems to be only true for new composers, that is:
1. Open new project
2. Delete the composer
3. Create a new composer and make it project default module
