MU.LAB 1.0 bugs and observations

[Bonteburg]

Thought I'd put this in a new thread ...

It seems that when you accidentally try to 'embed' the editor of a plugin that doesn't have an editor, MU.LAB goes wild with the error message, making further work in the plug area very hard because of incessant warnings, flickering dialogues and Mac alert sounds .
Re-openng the project fixes this.

Marco


Nice new edges on the modular plugs btw



edit: changd title from "MU.LAB 1.0 bug - "Nothing to edit' Mac OSX 10.4.8" as I considered it prudent not to start a new thread for every little bug

[muzycian]

Thanks for reporting this Marco!

pljones, this reminds me to something similar you reported some time ago. Could it have been this issue then?

[Bonteburg]

Crossfade Loopsynth (very simple sampler) crashes MU.LAB *zap* style randomly on opening or changing a program.

Weird - I don't know if I'm imaginig this but it seems that the bug only occurs if you click the plugin or play your keybord immediatley after loading the .fxp.

edit: Not so sure about that either, though it seems vaguely related to mouse movement.

I'll post it in the Expert Sleepers forum as well


Mac Mini intel, OSX 10.4.8

[pljones]

pljones, this reminds me to something similar you reported some time ago. Could it have been this issue then?

I don't remember a swarm of popups... That doesn't mean it didn't happen, though!

[Bonteburg]

This modular thing is growing on me, I find myself using rack view less and less.
Seems to me like he hanging note issues had to be solved for me to really delve into this.

What do you have to call your project again for it to be your defaults?
I seem to remember it had been implemented at some point?

[muzycian]

Crossfade Loopsynth (very simple sampler) crashes MU.LAB *zap* style randomly on opening or changing a program.

Weird - I don't know if I'm imaginig this but it seems that the bug only occurs if you click the plugin or play your keybord immediatley after loading the .fxp.

edit: Not so sure about that either, though it seems vaguely related to mouse movement.

I'll post it in the Expert Sleepers forum as well


Mac Mini intel, OSX 10.4.8

Not sure if i already did or not, but will check Crossfade Loopsynth (again).

[muzycian]

What do you have to call your project again for it to be your defaults?
I seem to remember it had been implemented at some point?

Euh, not in the office at the moment, can't check it for sure. But i think it's not yet in there. You could try "startup.musession" or "default.musession" or "new.musession", the last 2 being used when you do "New Session". If it's not yet there i'll add it in the next version.

[davidweese]

BUG - there seems to be some pretty good confusion on mulab's part about locations when you edit midi. For example, in the main timeline I am on bar 27. I want to edit a long sequence that crosses bar 27; that is, the sequence does not start or end at bar 27.

I double click the sequence strip. In the midi editor view I am now at bar 25. The transport time readout says I am at bar 27 but the editor grid (based on the playback position line) says bar 25. The music does start playing in the right spot, so clearly it's the edit-view/grid that's boogered.

Furthermore, if I click along the grid (to relocate) the playback indicator jumps to positions that are 10 bars offset from where I clicked. So if I click bar 3, the playback head goes to bar 13, etc.

[funkychickendance]

I'm starting to like this rig, for a number of reasons. First, it doesn't take half-an-hour to load every time, just because I have a fat folder of VST/VSTis. It lets me pick which ones I want it to consider. Doh!

Second, it's not buried in features that I won't use. End-result: I can see how I might spend more time doing music and less time reading manuals and tinkering.


//fnx

[funkychickendance]

Ah, here's an interesting bug. Mu does not seem to like LinPlug's SaxLab at all, and disables it. No issues with their other products. Wonder what this is about?

Edit: And, does the same to SampleTank 2.2 and Sonic Synth2. "Caused a problem during scan, will be disabled"

//fnx

[MachFront]

Ok, not a big deal, but...
There must be a quicker way to browse presets than is already implemented.
Now that the vst stays "on top", I really miss the preset browser that was added to the gui of each vst. It was ugly, but it was useful, and would be welcome now... expecially if it was 'prettied up' a bit.

Not a priority or anything, but...


By the way, I am loving this version. It's a pleasure to work with.

[AMG]

Ah, here's an interesting bug. Mu does not seem to like LinPlug's SaxLab at all, and disables it. No issues with their other products. Wonder what this is about?

Edit: And, does the same to SampleTank 2.2 and Sonic Synth2. "Caused a problem during scan, will be disabled"

//fnx

I got the same error during a VST scan. It does this on Emulator X and Wave13. Now for Emulator X I have to verify it(meaning put the CD-rom in), but I'm not using Emulator X, so MU disabling it isn't a problem. Now the other plugin, I found that I didn't have the file in my VST folder. So I dwnld it again and re-scanned it and it worked perfectly.

problem solved

[funkychickendance]

Ah, here's an interesting bug. Mu does not seem to like LinPlug's SaxLab at all, and disables it. No issues with their other products. Wonder what this is about?

Edit: And, does the same to SampleTank 2.2 and Sonic Synth2. "Caused a problem during scan, will be disabled"

//fnx

I got the same error during a VST scan. It does this on Emulator X and Wave13. Now for Emulator X I have to verify it(meaning put the CD-rom in), but I'm not using Emulator X, so MU disabling it isn't a problem. Now the other plugin, I found that I didn't have the file in my VST folder. So I dwnld it again and re-scanned it and it worked perfectly.

problem solved

Interesting. That's not it for me: all three .dlls are where (I think) they're supposed to be, in the root of the VST folder.

//fnx

[muzycian]

What do you have to call your project again for it to be your defaults?
I seem to remember it had been implemented at some point?

Euh, not in the office at the moment, can't check it for sure. But i think it's not yet in there. You could try "startup.musession" or "default.musession" or "new.musession", the last 2 being used when you do "New Session". If it's not yet there i'll add it in the next version.

Checked it: If you save a "New.musession" in the mulab folder, this one will be opened whenever you do "New Session".

So it can act as a default session

[muzycian]

BUG - there seems to be some pretty good confusion on mulab's part about locations when you edit midi. For example, in the main timeline I am on bar 27. I want to edit a long sequence that crosses bar 27; that is, the sequence does not start or end at bar 27.

I double click the sequence strip. In the midi editor view I am now at bar 25. The transport time readout says I am at bar 27 but the editor grid (based on the playback position line) says bar 25. The music does start playing in the right spot, so clearly it's the edit-view/grid that's boogered.

Furthermore, if I click along the grid (to relocate) the playback indicator jumps to positions that are 10 bars offset from where I clicked. So if I click bar 3, the playback head goes to bar 13, etc.

The time bar in the Sequence Editor shows the sequence time, not the part time!

So in the above last situation, the part will have started on bar 10, so that's why you see an 'offset' of 10 bars.