Ok, i've been thinking some more about this and will remove that MIDI channel appendix as it can be too confusing.mutools wrote:The [1] appendix is about the MIDI channel. It will only be shown for modules that effectively use MIDI channels. All VSTs are using MIDI channels. Most MUX patches do not. The auto-indexing for equal names in the same group is using round brackets (). Yes, that could be confusing. But i don't see a solution for that, except that if you encounter such situation, then practical solution is to use user-defined names to avoid the equal names.
I want to hide MIDI channeling as much as possible where it is redundant. Because it would only add complexity to newbees while it would not add any functionality.
M4 Test
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Jo, I'm OK with all your answers -- I'm easily persuaded on the D'n'D feature but that needs to be a big feature in your pushing of M4 so anyone downloading the free version is not going to have had a chance to miss it 
.
Just one point I think you missed - is there any chance of having multiple instances of a synth given unique names? (Or were you hinting removing the MIDI channel would allow you to append a unique number?)
.Just one point I think you missed - is there any chance of having multiple instances of a synth given unique names? (Or were you hinting removing the MIDI channel would allow you to append a unique number?)
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Happy you like itpljones wrote:Jo, I'm OK with all your answers -- I'm easily persuaded on the D'n'D feature but that needs to be a big feature in your pushing of M4 so anyone downloading the free version is not going to have had a chance to miss it
I can't let the auto-name-indexer work on VSTs in different racks.Just one point I think you missed - is there any chance of having multiple instances of a synth given unique names? (Or were you hinting removing the MIDI channel would allow you to append a unique number?)
So if you have multiple instances of the same VST in different racks, and the VST all have the same name (which is not always the case as M4 prefers to use the VST program name, if relevant), well in that case please manually rename things where appropriate for you. The auto-name-indexer is a little helper function, but it has its limits.
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
From a newcomer or a beginner standpoint a Rack is an unusual name because most of the Daws use more commonly the term Mixer or mixer strip etc. So, Track, Rack are a little close as a spelling and pronunciation goes. To me the Rack is still a mixer in my mind and if I well remember also in your modules the Mixer Strip... Is correctly named.
Beside this, yes I figured out about the target by D&D, cool. I love it.
Another unusual thing for me is that if I'm recording a sequencer and if in the middle of recording I move some of the synth controls a new sequencer is added to a subtrack with the midi notes played from the moment I used the controller in the recording process. This create a split in my recording giving me the whole midi note performance split in two separated sequencers. Not usefull.
What I'm doing wrong?
Beside this, yes I figured out about the target by D&D, cool. I love it.
Another unusual thing for me is that if I'm recording a sequencer and if in the middle of recording I move some of the synth controls a new sequencer is added to a subtrack with the midi notes played from the moment I used the controller in the recording process. This create a split in my recording giving me the whole midi note performance split in two separated sequencers. Not usefull.
What I'm doing wrong?
ABEFLGMOPPRRST 
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
Hold on! I think I'm beginning to see the way it works. Quite flexible indeed! Great work!liquidsound wrote:From a newcomer or a beginner standpoint a Rack is an unusual name because most of the Daws use more commonly the term Mixer or mixer strip etc. So, Track, Rack are a little close as a spelling and pronunciation goes. To me the Rack is still a mixer in my mind and if I well remember also in your modules the Mixer Strip... Is correctly named.
Beside this, yes I figured out about the target by D&D, cool. I love it.
Another unusual thing for me is that if I'm recording a sequencer and if in the middle of recording I move some of the synth controls a new sequencer is added to a subtrack with the midi notes played from the moment I used the controller in the recording process. This create a split in my recording giving me the whole midi note performance split in two separated sequencers. Not usefull.
What I'm doing wrong?
It would help though, if ever possible, to highlight a used parameter of a VST in the long (Damn long in some of them) list. I get that neat feature in Orion and it's very comfortable.
ABEFLGMOPPRRST
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Is the OSX version of M4 ready yet? Thought wanted to test it out...
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
There is a new M4 test version available in http://www.mutools.com/mulab/cedar
Some nice improvements in there (i hope)
OSX version on its way out too, normally later today, if nothing unexpected pops up.
Some nice improvements in there (i hope)
OSX version on its way out too, normally later today, if nothing unexpected pops up.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
The selection for a new Sequencer is based on context (Track Type). Excellent! Very Quick flow.
ABEFLGMOPPRRST
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Updated M4072 in the cedar webfolder.
In M4071 there was something wrong with the MuDrum racks.
Sorry for the double update.
In M4071 there was something wrong with the MuDrum racks.
Sorry for the double update.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Yes i think this new version contains some nice polishingsliquidsound wrote:The selection for a new Sequencer is based on context (Track Type). Excellent! Very Quick flow.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRian
- 731 posts since 25 Oct, 2008 from Holland
Easy sound selection and easy automation..MULAB is finished now
What else more ?
Yes.. two track contrapunt : in one track is in grey not editable visible in th enote roll editor ..and against this track i can a make a another melody track
What else more ?
Yes.. two track contrapunt : in one track is in grey not editable visible in th enote roll editor ..and against this track i can a make a another melody track
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
Can those beautiful new envelope curves made in a dedicated sequencer being copied and pasted in the pianoroll? And if that's possible can that be done also the other way around? From the pianoroll to the new envelop curve sequencer? This will add more flexibility, for precision editing in relationship to the midi notes, n till the time when you will be able to integrate them in the pianoroll (M5?)
ABEFLGMOPPRRST
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Hey! I've been testing MU.LAB 4 on OSX!!
First impression:
Colours.
Second impression:
I love the new saving system. It's a real step forward compared to the old one which was kind of cumbersome.
The three effect slots on the MuSampler are very nice!
The node system on automation subtracks is cool.
_______________________________________________________________
Possible Bugs/non-standard behaviour/Differences from M3:
-I'm having trouble moving the MU.LAB window across the screen. Most notably it refuses to move up unless I'm really pussyfooting. The same thing applies to windows inside MULAB.
-MuDrum: Unless I'm missing something there's a routing error: I put an effect on slot/rack/effects/bus section thing #1 (the first from the left) whilst all the pads were wired to it. Then I disconnected one of the pads and wired it to the second section/slot all by itself, but it was still getting the effect. Interestingly, when I put an effect on the 'singled out' pad, none of the other pads are affected (as you would expect).
-I opened my empty session and put a MuSynth in Rack 1. I could see the volume meter go up and down when I used the little keyboard at the top of the MULAB window but I couldn't hear a sound. Playing it with my MIDI-keyboard wasn't a problem.
-hm no multisampler anymore? I guess it happens via 'Basic Synth' and adding a module and adsr envelope now? If so, I'm not sure if it's an improvement.
-What happened to 'new.musession' being the default session when you place it directly into the MU.LAB folder? That was handy! (Maybe I don't get the session folder thing yet).
-How do I create a track from a rack?* Also, how do I choose a track's target to be anything other than a rack (esp. for automation)? Does automation only work with subtracks now?
*edit: it appears it works automatically (as in M3) sometimes. I don't know yet when this is the case.
-There are no loop points on automation subtracks (bug or feature?)
_______________________________________________________________
Fine Tuning:
-I think there should be a way to tell MULAB how loud the sample preview should be because if you tend to mix with a lot of headroom it can get annoyingly loud depending on the sample. Maybe sample previews could be directly routed to the rack containing the instrument you're loading the samples into.
-How does MULAB Free choose which 8 vst plugs to accept when I add the whole VST folder in one go? I have no way of telling which VST it mightn't like because of incompatibly issues.
_______________________________________________________________
Audio recording seems to work fine - no surprises there!
OSX 10.6.3 Mac Mini.
Marco
First impression:
Colours.
Second impression:
I love the new saving system. It's a real step forward compared to the old one which was kind of cumbersome.
The three effect slots on the MuSampler are very nice!
The node system on automation subtracks is cool.
_______________________________________________________________
Possible Bugs/non-standard behaviour/Differences from M3:
-I'm having trouble moving the MU.LAB window across the screen. Most notably it refuses to move up unless I'm really pussyfooting. The same thing applies to windows inside MULAB.
-MuDrum: Unless I'm missing something there's a routing error: I put an effect on slot/rack/effects/bus section thing #1 (the first from the left) whilst all the pads were wired to it. Then I disconnected one of the pads and wired it to the second section/slot all by itself, but it was still getting the effect. Interestingly, when I put an effect on the 'singled out' pad, none of the other pads are affected (as you would expect).
-I opened my empty session and put a MuSynth in Rack 1. I could see the volume meter go up and down when I used the little keyboard at the top of the MULAB window but I couldn't hear a sound. Playing it with my MIDI-keyboard wasn't a problem.
-hm no multisampler anymore? I guess it happens via 'Basic Synth' and adding a module and adsr envelope now? If so, I'm not sure if it's an improvement.
-What happened to 'new.musession' being the default session when you place it directly into the MU.LAB folder? That was handy! (Maybe I don't get the session folder thing yet).
-How do I create a track from a rack?* Also, how do I choose a track's target to be anything other than a rack (esp. for automation)? Does automation only work with subtracks now?
*edit: it appears it works automatically (as in M3) sometimes. I don't know yet when this is the case.
-There are no loop points on automation subtracks (bug or feature?)
_______________________________________________________________
Fine Tuning:
-I think there should be a way to tell MULAB how loud the sample preview should be because if you tend to mix with a lot of headroom it can get annoyingly loud depending on the sample. Maybe sample previews could be directly routed to the rack containing the instrument you're loading the samples into.
-How does MULAB Free choose which 8 vst plugs to accept when I add the whole VST folder in one go? I have no way of telling which VST it mightn't like because of incompatibly issues.
_______________________________________________________________
Audio recording seems to work fine - no surprises there!
OSX 10.6.3 Mac Mini.
Marco