I just tried muting and unmuting Fab Filter One on it's own and it exhibits the same bug.
On the other hand, Free Alpha and Cheeze Machine behave correctly in the MuPad.
That puts the ball in the Fab Filter court, unless you think something of interest could be happening in the MuPad when this problem occurs.
BTW just discovering the sheer awesomeness of the factory sounds (AD module). Amazing piece of work!
Edit: It also appears that after a while, the sound will kick back in on it's own. I'm not sure if Fab Filter/MU.LAB 'waits' for a certain note-on event or the point where a part repeats itself.)
M4 Test
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
But if it's also happening when FF1 is used outside a MuPad, eg in the rackdesk, then it's not MuPad related, right? (or maybe my head is not yet clear again after the beers of last night?Bonteburg wrote:I just tried muting and unmuting Fab Filter One on it's own and it exhibits the same bug.
On the other hand, Free Alpha and Cheeze Machine behave correctly in the MuPad.
That puts the ball in the Fab Filter court, unless you think something of interest could be happening in the MuPad when this problem occurs.
)Yeah Andreas made wonderful patches!BTW just discovering the sheer awesomeness of the factory sounds (AD module). Amazing piece of work!
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
The newes M4.0.76 test packages are available http://www.mutools.com/mulab/cedar
What's changed since M4.074:
* Further finetuned track/rack/module coloring.
* When choosing a color for a MUX Play Editor frame, also the session color palette is available now.
* Fixed a rare but possible crash bug in the oscillators.
* Fixed a crash bug when replacing modules in the MuPad slots.
* When saving MuSynth/MuPad patches with in the slots any MUX patches that use samples, these samples were not reloaded when loading the patch. Fixed.
* Whenever poping up the sequence list, MuLab first auto deletes any unused empty sequences so to avoid that the sequence list is populated with redundant sequences.
* Dropping a MuSequence file on the composer = add sequence part.
* When drag-dropping a rack slot within a session, any track targets to that rack slot are preserved now, as in M3.
* Session menu now also contains "Open Demo".
* Track context menu contained 2 x "Delete", one of which was not working properly. All ok now.
* Further finetuned the top panels positioning/sizing.
* MuDrum & MuPad files didn't show up in the 'Add Instrument Track' dialog.
* Fixed several probs wrt MuDrum E3 editors.
* Finetuned some graphics.
What's changed since M4.074:
* Further finetuned track/rack/module coloring.
* When choosing a color for a MUX Play Editor frame, also the session color palette is available now.
* Fixed a rare but possible crash bug in the oscillators.
* Fixed a crash bug when replacing modules in the MuPad slots.
* When saving MuSynth/MuPad patches with in the slots any MUX patches that use samples, these samples were not reloaded when loading the patch. Fixed.
* Whenever poping up the sequence list, MuLab first auto deletes any unused empty sequences so to avoid that the sequence list is populated with redundant sequences.
* Dropping a MuSequence file on the composer = add sequence part.
* When drag-dropping a rack slot within a session, any track targets to that rack slot are preserved now, as in M3.
* Session menu now also contains "Open Demo".
* Track context menu contained 2 x "Delete", one of which was not working properly. All ok now.
* Further finetuned the top panels positioning/sizing.
* MuDrum & MuPad files didn't show up in the 'Add Instrument Track' dialog.
* Fixed several probs wrt MuDrum E3 editors.
* Finetuned some graphics.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
When a specific rack slot is focussed, its contour is colored now:mutools wrote:* Further finetuned track/rack/module coloring.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Wrt emphasizing the difference between the New/Open Session menu options in the MULAB and SESSION menus, i've been thinking about this:
MULAB -> New Extra Session
MULAB -> Open Extra Session
SESSION -> New
SESSION -> Open
SESSION -> Open Recent
SESSION -> Open Demo
It's close to janamdo's idea (New Multi Session) but when i read "Open Multi Session" i think i'm going to open a Multi-Session, that's what was obstructing me. To me "Open Extra Session" is more clear.
In the MULAB menu, no 'open demo session' here.
And "Open Extra Session" will also show the recent ones, with an "Open ..." options below, as on startup.
That could make things less ambiguous and more polished.
What do you think?
MULAB -> New Extra Session
MULAB -> Open Extra Session
SESSION -> New
SESSION -> Open
SESSION -> Open Recent
SESSION -> Open Demo
It's close to janamdo's idea (New Multi Session) but when i read "Open Multi Session" i think i'm going to open a Multi-Session, that's what was obstructing me. To me "Open Extra Session" is more clear.
In the MULAB menu, no 'open demo session' here.
And "Open Extra Session" will also show the recent ones, with an "Open ..." options below, as on startup.
That could make things less ambiguous and more polished.
What do you think?
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
mutools wrote:When a specific rack slot is focussed, its contour is colored now:mutools wrote:* Further finetuned track/rack/module coloring.
ABEFLGMOPPRRST 
-
- KVRAF
- 1736 posts since 19 May, 2006 from Nomadic (Chicago and San Francisco mostly)
So I saw the upload this morning and played around with it a bit.
Holy crap its deep. It's all deceptive and stuff, looking all simple like that, but it's like falling down the rabbit hole.
I need to find tutorials or something, there's a lot going on here. *lost*
Is there a step/drum sequencer anywhere? Or an arpeggiator?
I see there's a way to select skins.. how much control does a skin have over the look and feel?
How do you delete notes? I have to select them and hit the delete key right now.
I'm used to dragging the edge of a note to extend/shrink it, but there's a wide area on either side where the cursor changes into a.. scalpel? pencil? in mulab that you can drag. It's just something I'll have to get used to, but I'd really like a <-> cursor so I know whats going on.
Holy crap its deep. It's all deceptive and stuff, looking all simple like that, but it's like falling down the rabbit hole.
I need to find tutorials or something, there's a lot going on here. *lost*
Is there a step/drum sequencer anywhere? Or an arpeggiator?
I see there's a way to select skins.. how much control does a skin have over the look and feel?
How do you delete notes? I have to select them and hit the delete key right now.
I'm used to dragging the edge of a note to extend/shrink it, but there's a wide area on either side where the cursor changes into a.. scalpel? pencil? in mulab that you can drag. It's just something I'll have to get used to, but I'd really like a <-> cursor so I know whats going on.
liquidsound wrote:Nice to see you around here xybre!
noise and beats: Negutyv Xeiro do people actually click these?
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Nope - it needn't even be MU.LAB-related is what I meant to say.mutools wrote:But if it's also happening when FF1 is used outside a MuPad, eg in the rackdesk, then it's not MuPad related, right? (or maybe my head is not yet clear again after the beers of last night?
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
When the pencil appears on either side of the note you can double click to delete it or use the pencil to drag and change the length of that note. Holding Ctrl turns the pencil into an eraser in the side hot spots of the note, then it's only a click!xybre wrote:So I saw the upload this morning and played around with it a bit.
Holy crap its deep. It's all deceptive and stuff, looking all simple like that, but it's like falling down the rabbit hole.
I need to find tutorials or something, there's a lot going on here. *lost*
Is there a step/drum sequencer anywhere? Or an arpeggiator?
I see there's a way to select skins.. how much control does a skin have over the look and feel?
How do you delete notes? I have to select them and hit the delete key right now.
I'm used to dragging the edge of a note to extend/shrink it, but there's a wide area on either side where the cursor changes into a.. scalpel? pencil? in mulab that you can drag. It's just something I'll have to get used to, but I'd really like a <-> cursor so I know whats going on.
liquidsound wrote:Nice to see you around here xybre!
If multiple notes are selected those functions (delete, length) it's applied to all of them. When multiple notes are selected and you change their length by dragging, a dialog will appear with several choices to apply to the selection.
Here is a page of instruction for M3 about navigation and it's still valid for M4.
http://www.mutools.com/mulab/docs/edito ... ation.html
Yes it is quite deep and Jo, the developer, is going deeper and deeper
Your inputs are welcome. MuLab is skinnable, and in the past some designer made some really cool themes and we expecting more coming.
And don't forget to Right Click anywhere. It's full of options. I mean EVERYWHERE!
ABEFLGMOPPRRST
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
A glimpse of the modularity can be seen if you for example click on the arrow next to the Smooth Bass slot in the Mixer Rack and then when the module appears select the Option Menu on the top right near the number "Zero" and select "Show Deep Editor" and then in the editor double click the the Poly Synth Icon... there you are. There is also a Modular Area at the end of the Session Menu to explore...xybre wrote:Holy crap its deep. It's all deceptive and stuff, looking all simple like that, but it's like falling down the rabbit hole.
ABEFLGMOPPRRST
-
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
Bonteburg wrote:No it doesn't. I think it's supposed to work as of v5. (this thread is about v4).
Ahhh... too bad, otherwise it looks interesting, but that is a huge limitation that cripples computer power. Indeed a showstopper.
-
- KVRer
- 24 posts since 28 Feb, 2005 from Los Angeles
Does Mulab record MIDI output from a loaded VSTi? I still cannot figure out how to capture Jamstix 3 drum performance onto a track. This is in version 3 or 4.Cheers!
-
- KVRian
- 1233 posts since 29 Dec, 2008 from Lithuania
Sorry for the n00b question.
Did the option of "set target module per parts" disappeared or I just can't find it ?
Also, having a pop-up display saying "2.34 DB" Like in M3 to me is better than a long thing like "Gain = 2.34 DB".
Did the option of "set target module per parts" disappeared or I just can't find it ?
Also, having a pop-up display saying "2.34 DB" Like in M3 to me is better than a long thing like "Gain = 2.34 DB".
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
Yes that one is missing. I guess is with D&D.
If I have a Track with no target and I add a new Part/Seq it will no produce any sound because the Track has no target yet, but if a Drag & Drop a VST from a slot into that part then the Part will target that VST (is it?, or is the Track doing it?).
My confusion appears when I take that Part/Seq and I move it on another Track. There, the original Target on that Part/Seq has been replace with whatever is on this other Track I'm moving that part to. So far looks like that the Target is defined by the Track and secondarily from the Part if the Track is target-less (or still is the Track doing this?).
BUT if I create a new Part/Seq on that Target-less track again, the same VST is given to the new Pat/Seq as a Target. It remembers it even though it looks like the Track still is not connected to anything. The color is still gray...
My understanding seems to suggest that Targets are based on Tracks only. Wrong?
Edit: I just realized that the D&D just made the VST in focus and has nothing to do with the Target as I knew from M3
If I have a Track with no target and I add a new Part/Seq it will no produce any sound because the Track has no target yet, but if a Drag & Drop a VST from a slot into that part then the Part will target that VST (is it?, or is the Track doing it?).
My confusion appears when I take that Part/Seq and I move it on another Track. There, the original Target on that Part/Seq has been replace with whatever is on this other Track I'm moving that part to. So far looks like that the Target is defined by the Track and secondarily from the Part if the Track is target-less (or still is the Track doing this?).
BUT if I create a new Part/Seq on that Target-less track again, the same VST is given to the new Pat/Seq as a Target. It remembers it even though it looks like the Track still is not connected to anything. The color is still gray...
My understanding seems to suggest that Targets are based on Tracks only. Wrong?
Edit: I just realized that the D&D just made the VST in focus and has nothing to do with the Target as I knew from M3
ABEFLGMOPPRRST
-
- KVRian
- 1233 posts since 29 Dec, 2008 from Lithuania
If that plugin has MIDI output I think it should. You just have to rout the MIDI output to a track. Put the plugin in the modular area, drag "cables" from the blue "event outputs" and put those to a track... I think.kminardi wrote:Does Mulab record MIDI output from a loaded VSTi? I still cannot figure out how to capture Jamstix 3 drum performance onto a track. This is in version 3 or 4.Cheers!