MU.LAB 1.0 has been pre-released.
This PreRelease version has a couple of fixes and tunings, and includes updated documentation:
* New: Event Value 2 editor: Right-click on the leftside definition area -> popup menu -> "Select All"
* Tuned: Inserting the very first sequence part in the composer automatically creates a new sequence
* Tuned: Inserting a new part in the composer selects that part
* Tuned: Renamed the MuSynth & MUX "Edit Editor" to "Deep Editor"
* Tuned: On new session, an MIDI Output is created for each opened MIDI Port
* Tuned: Modular areas: better looking plug boxes
* Tuned: Modular areas: a tool tip gives more info about the in/out jacks
* Fixed: Clicking the close button of the sequence editor window had different behaviour depending on whether the focus was on the note editor or the value editor
* Fixed: Event List Editor: Could only insert notes, no other types of events (bug since in closed beta B)
* Updated documentation
Download links on http://www.mutools.com
MU.LAB PreRelease
-
- KVRAF
- 1645 posts since 24 May, 2002
-
- KVRist
- 357 posts since 5 Aug, 2006 from St. Louis
Wishlist item
One thing lacking in MULAB is a 'VU' meter to give you an indication of the level of your recording signal. Most recording programs feature a 'VU' meter that tells you how hot your input signal is. Then it can be adjusted on the fly.
This would be a handy feature when recording Audio.
One thing lacking in MULAB is a 'VU' meter to give you an indication of the level of your recording signal. Most recording programs feature a 'VU' meter that tells you how hot your input signal is. Then it can be adjusted on the fly.
This would be a handy feature when recording Audio.
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
It's in there:jpumphandle wrote:Wishlist item
One thing lacking in MULAB is a 'VU' meter to give you an indication of the level of your recording signal. Most recording programs feature a 'VU' meter that tells you how hot your input signal is. Then it can be adjusted on the fly.
This would be a handy feature when recording Audio.
Just route your audio input signal thru a rack and the rack meter will show your input level.
How to route your audio input signal thru a rack: 2 ways:
-> right-click a (new) rack's background and choose "Monitor Audio Input"
or
-> right-click the Record button in the Transport Panel, that pops up the Recording Options, there you can choose a rack for "Audio Input Monitor".
I'll update the docs on this, as this was not yet fully clear.
-
- KVRer
- 20 posts since 9 Jul, 2003
Jo
It's not super clear where exactly to post bugs so I assume in response to the beta announcement makes sense. I trust you looked over my obnoxiously lengthy email a couple days back.
please check this scenario :
1. record a soft wynth track
2. record audio
3. cut the audio in half
4. edit one of the two pieces in the audio editor
5. mute part of it
Now the soft wynth still plays but the audio is ALL muted
I recorded another audio track, doublechecked routing, etc. and the new track plays. I moved the offending clip around and the half I did NOT edit now plays partially then mutes. weird...
It appears the internals are losing track of some data during destructive editing operations
As I alluded to in my email, in addition to opening up all the file formats by making them text based (and hence open to third party tools for, say, patch generation), I think it would be really, really smart to generate a textfile log of all program operations and results. Even if it were quite cryptic, it might shed light on weird bugs like this. Of course it would affect performance, but whoop-de-doo. Stability is the top priority right?
Dave
It's not super clear where exactly to post bugs so I assume in response to the beta announcement makes sense. I trust you looked over my obnoxiously lengthy email a couple days back.
please check this scenario :
1. record a soft wynth track
2. record audio
3. cut the audio in half
4. edit one of the two pieces in the audio editor
5. mute part of it
Now the soft wynth still plays but the audio is ALL muted
I recorded another audio track, doublechecked routing, etc. and the new track plays. I moved the offending clip around and the half I did NOT edit now plays partially then mutes. weird...
It appears the internals are losing track of some data during destructive editing operations
As I alluded to in my email, in addition to opening up all the file formats by making them text based (and hence open to third party tools for, say, patch generation), I think it would be really, really smart to generate a textfile log of all program operations and results. Even if it were quite cryptic, it might shed light on weird bugs like this. Of course it would affect performance, but whoop-de-doo. Stability is the top priority right?
Dave
-
- KVRer
- 13 posts since 4 Sep, 2006
I have been working with ML1.0 prerelease and found a file saving problem Tech support has been notified, so this FYI if you are working with it or planning to.
If you craate a new session and then try to "save as" to create a file for it, you have to either overwrite an existing file or use the box at the bottom left corner of the file browser window ("new file") to name it. The problem is it saves the file in your main MuLab directory but ignores the name you give it and saves it under the name "MULAB free" followed by a sequential number (e.g., MULAB free 1.musession). The file is intact, you just need to go to the main directory folder (it doesn't remember where you have other session files) and change the name before you lose track of what it is. This same procedure also applies to fxp or fxb files you save. They will also be saved as MULAB free #.fxp/fxb.
Other than that, everything is pretty much rocking so far. I've been running it using a multitimbral patch in Wusikstation, to my mind a real high-powerd commercial VSTi, and it is handling it fine. Plus, rack instrument/effect assignment makes it very easy to set up. I am having trouble getting the FX send to work right, though. If I assign a send in rack A to rack B, turn the feed knob all the way up, and B has an effect in it, it doesn't seem to be on the rack A signal in the output mix. Anyone tried that?
Best, Bruce
If you craate a new session and then try to "save as" to create a file for it, you have to either overwrite an existing file or use the box at the bottom left corner of the file browser window ("new file") to name it. The problem is it saves the file in your main MuLab directory but ignores the name you give it and saves it under the name "MULAB free" followed by a sequential number (e.g., MULAB free 1.musession). The file is intact, you just need to go to the main directory folder (it doesn't remember where you have other session files) and change the name before you lose track of what it is. This same procedure also applies to fxp or fxb files you save. They will also be saved as MULAB free #.fxp/fxb.
Other than that, everything is pretty much rocking so far. I've been running it using a multitimbral patch in Wusikstation, to my mind a real high-powerd commercial VSTi, and it is handling it fine. Plus, rack instrument/effect assignment makes it very easy to set up. I am having trouble getting the FX send to work right, though. If I assign a send in rack A to rack B, turn the feed knob all the way up, and B has an effect in it, it doesn't seem to be on the rack A signal in the output mix. Anyone tried that?
Best, Bruce
-
- KVRer
- 20 posts since 9 Jul, 2003
If I set a midi controller with my ozone, it "takes", yet with my XBoard it does not. With the XBoard, it auto-detects the midi controller (to control rack volume, btw) but after ok-ing it, the physical controller has no effect.
Dave
Dave
-
- KVRer
- 13 posts since 4 Sep, 2006
Hey Dave, I tried the same thing with a MIDI controller but I can't duplicate the problem. Mine is working fine. MuLab detected the controller and I assigned it as a MIDI in. Then I created a plug (MIDI in) for it and connected it to Rack A. I inserted MuSynth into the rack and set it up with the MIDI controller as source and CC7 (volume) as the MIDI parameter. Everything seems to be working OK. (???) It's a little glitchy (clicks in the audio) when I do it live, but it's functional.
Like Ozone, my controller is also M-Audio (Keystation 49e). Do you think you might be having software/hardware interface problems with the other controller?
Cheers, Bruce
Like Ozone, my controller is also M-Audio (Keystation 49e). Do you think you might be having software/hardware interface problems with the other controller?
Cheers, Bruce
Last edited by hermit01 on Mon Dec 17, 2007 11:07 pm, edited 1 time in total.
-
- KVRer
- 20 posts since 9 Jul, 2003
Bruce
Doubtful. The XBoard25 works flawlessly with all my other apps......
?!?
Dave
Doubtful. The XBoard25 works flawlessly with all my other apps......
?!?
Dave
-
- KVRer
- 13 posts since 4 Sep, 2006
Dave: Yup, not likely. Sounds like a hole in the MuLab net for the workings of that controllers particular tech. Bless M-Audio, hunh? :-)
Folks, I've spent about 10 hours on MuLab 1.0 prerelease and, oh wow, do I second the merge track function need. I've done OK copying and pasting sequences but...I keep looking for merge thinking it's hidden in there somewhere. :-))
Folks, I've spent about 10 hours on MuLab 1.0 prerelease and, oh wow, do I second the merge track function need. I've done OK copying and pasting sequences but...I keep looking for merge thinking it's hidden in there somewhere. :-))
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
If it's about something that may interest more users, then please post it here.davidweese wrote:Jo
It's not super clear where exactly to post bugs so I assume in response to the beta announcement makes sense.
If it's more personal, private or business oriented, please email me directly.
Sure, replied.I trust you looked over my obnoxiously lengthy email a couple days back.
Interesting discussion!
Can't repeat this here...please check this scenario :
1. record a soft wynth track
2. record audio
3. cut the audio in half
4. edit one of the two pieces in the audio editor
5. mute part of it
Now the soft wynth still plays but the audio is ALL muted
Which edit did you do in the Audio Lab?
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
As emailed: Very Strange Thing!!! Almost sounds like a virus to mehermit01 wrote:I have been working with ML1.0 prerelease and found a file saving problem Tech support has been notified, so this FYI if you are working with it or planning to.
If you craate a new session and then try to "save as" to create a file for it, you have to either overwrite an existing file or use the box at the bottom left corner of the file browser window ("new file") to name it. The problem is it saves the file in your main MuLab directory but ignores the name you give it and saves it under the name "MULAB free" followed by a sequential number (e.g., MULAB free 1.musession). The file is intact, you just need to go to the main directory folder (it doesn't remember where you have other session files) and change the name before you lose track of what it is. This same procedure also applies to fxp or fxb files you save. They will also be saved as MULAB free #.fxp/fxb.
Anyone else experiencing this?
Eventually post the musession file somewhere so we can have a look at the routing.Other than that, everything is pretty much rocking so far. I've been running it using a multitimbral patch in Wusikstation, to my mind a real high-powerd commercial VSTi, and it is handling it fine. Plus, rack instrument/effect assignment makes it very easy to set up. I am having trouble getting the FX send to work right, though. If I assign a send in rack A to rack B, turn the feed knob all the way up, and B has an effect in it, it doesn't seem to be on the rack A signal in the output mix. Anyone tried that?
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
Do you set "Global" on or off?davidweese wrote:If I set a midi controller with my ozone, it "takes", yet with my XBoard it does not. With the XBoard, it auto-detects the midi controller (to control rack volume, btw) but after ok-ing it, the physical controller has no effect.
Dave
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
It's on the whishlistBonteburg wrote:fine tuning idea: MU:LAB doesn't have a 'merge parts' option yet.
