Bug report

Official support for: mutools.com
RELATED
PRODUCTS

Post

Hello, everybody.

I was recording a guitar line with mulab 1.1, thought "great take" and hit the space bar to stop recording, and then mulab just quit without any previous prompt or anything. Happened twice tonight, but when it happened by the second time I was ready, the first time I just lost the take and few more I had recorded before the last one.

Working on a dual core, 2Gb RAM, Windows XP SP2, running Line6 GuitarPort software when the bug happened but not recording through it.

Best.

Post

Can you find a repeatable pattern in when it crashes?

Post

Hello,
Mulab is very pleasant so I go on exploring it (free version 1.1).
I have found some bugs so I report them here, in case they have not been reported yet :
1) when I am on the Racks window and press TAB, it toggles to the Modular Plugin Area but then I loose the size and position I have given to the Racks window, and the Composition window is affected too if I have resized it before.
If I use the menu to select "Show Composer only" it also loose the size and position I have given to this window when I was in "Composer and Racks" mode.
If I use TAB when I am on the Composition window, all is right : no change in size and position.
2) I create a sequence on track 5 of composition B, select this sequence and copy it. When I paste it in the composition A, the sequence doesn't appear because composition A has 4 tracks only. If I create a new track in composition A, now the sequence I've pasted appears. I think that Mulab must add the tracks automaticaly.
3) I put a MuSynth in a rack slot and choose a preset. When I put the mouse over the slot, a tooltip appears with the name of the preset. Great. But now, I choose another preset for the MuSynth. When I put the mouse over the slot, the tooltip still shows the name of the ancient preset.
4) When I rename a Send slot, the slot doesn't show the new name and the tooltip doesn't show it too, it's always the old name.
5) In the Plugin Modular Area, I click on a plugin and have a message "Nothing to edit". Now I go to another plugin that have something to edit and it always say "Nothing to edit". If I toggles to Racks view, I have the message when I click on any slot. I have to close and reopen Mulab to be safe. Well, I can't always reproduce this but it happens !
6) I have also taken a look at the deep editor in MuSynth and Mux and sometimes I don't know why, I have no more sound because of an CPU overload, I have to click on the Overload message to restore the sound. Well, here too, I can't always reproduce it.

Voilà, that's all for the moment...

Post

pquenin wrote:Hello,
Mulab is very pleasant so I go on exploring it (free version 1.1).
I have found some bugs so I report them here, in case they have not been reported yet :

1) when I am on the Racks window and press TAB, it toggles to the Modular Plugin Area but then I loose the size and position I have given to the Racks window, and the Composition window is affected too if I have resized it before.
If I use the menu to select "Show Composer only" it also loose the size and position I have given to this window when I was in "Composer and Racks" mode.
If I use TAB when I am on the Composition window, all is right : no change in size and position.
This is not a bug but a feature.

In fact there are 3 'views':

Composer Only
Composer + Racks
Composer + MPA

Each of these 3 views memorizes the position + size of the windows.

So if you press TAB to switch to the MPA, and then press TAB again to switch to the Racks, then the windows should be at their original position again.

Hope i explained well.
2) I create a sequence on track 5 of composition B, select this sequence and copy it. When I paste it in the composition A, the sequence doesn't appear because composition A has 4 tracks only. If I create a new track in composition A, now the sequence I've pasted appears. I think that Mulab must add the tracks automaticaly.
You're right on this.

Will be fixed in the next version.
3) I put a MuSynth in a rack slot and choose a preset. When I put the mouse over the slot, a tooltip appears with the name of the preset. Great. But now, I choose another preset for the MuSynth. When I put the mouse over the slot, the tooltip still shows the name of the ancient preset.
True.

Will be fixed in the next version.
4) When I rename a Send slot, the slot doesn't show the new name and the tooltip doesn't show it too, it's always the old name.
True; this is the same bug as in 3) though.

=> Fixed in the next version.
5) In the Plugin Modular Area, I click on a plugin and have a message "Nothing to edit". Now I go to another plugin that have something to edit and it always say "Nothing to edit". If I toggles to Racks view, I have the message when I click on any slot. I have to close and reopen Mulab to be safe. Well, I can't always reproduce this but it happens !
You mean when doing "Embed Editor", right?

Yes, that's a known issue which is already fixed in the hot lab version here.

There should be a "Known Issues" page on the website. Will do!
6) I have also taken a look at the deep editor in MuSynth and Mux and sometimes I don't know why, I have no more sound because of an CPU overload, I have to click on the Overload message to restore the sound. Well, here too, I can't always reproduce it.
Please let me know if you could find a repeatable pattern in it.
Voilà, that's all for the moment...
Thanks!

Well, by properly spotting and reporting these bugs, you certainly also won your MU.LAB Unlimited User License!

Email me your name and address and i'll send you your license :)

Post

Great ! Nice to see that bug reports are taken into consideration.
And of course thank you for the license, you're a nice guy !
I have notice 2 other things that are not bugs but are feature requests :
a) I can't change the order of the racks in the racks window.
b) when I export to midi file a composition with several tracks, when I import this file, the tracks have no name. Maybe it can be a good thing to give tracks the name of the first sequence found on them. So when you import the midi file, the tracks have significant names.

Post

Hi can you please look into my Mulab post when you have the time Jo :D
Link: http://www.kvraudio.com/forum/viewtopic.php?p=2968061

Post

pquenin wrote:Great ! Nice to see that bug reports are taken into consideration.
And of course thank you for the license, you're a nice guy !
License sent ;)
I have notice 2 other things that are not bugs but are feature requests :
a) I can't change the order of the racks in the racks window.
Is on the whishlist.
b) when I export to midi file a composition with several tracks, when I import this file, the tracks have no name. Maybe it can be a good thing to give tracks the name of the first sequence found on them. So when you import the midi file, the tracks have significant names.
MU.LAB does write the track names into the MIDI file. (track name)

And it also writes the name of the first sequence into the MIDI file. (sequence name)

And so if you save a MIDI file from MU.LAB, and reload it, then everything is neatly preserved.

Not sure if you know, but if you want to name tracks in MU.LAB, drag the track header splitter a bit more to the right, so you see the tracks names ;)

By default this splitter is positioned so that you only see the track mutes, because this way the composer has more editing room, and because naming tracks is not regarded as essential i.e. more optional as you can already name each part.

Post

Not sure if you know, but if you want to name tracks in MU.LAB, drag the track header splitter a bit more to the right, so you see the tracks names
Ok, I've missed that...

Post

And so if you save a MIDI file from MU.LAB, and reload it, then everything is neatly preserved.
I have tried to rename the tracks and the sequences and save to midi file.
When I import this midi file in a new session, the tracks and sequences names are lost.

I've tried to open this midi file in others host (traction and reason) but with the same result...

Post

I'm sorry man, also here i mismatched versions.

It all will be OK in the next version, but indeed MU.LAB 1.1 is not yet doing this.

Post

Jo, you're piling a tonne into that next version; no wonder it's going to be beta'd...

Post

Yes, it seems to becoming a BIG update... :o

And as quite some things have changed/added internally too, beta testing will certainly be necessary!

And fun :band:

Post

Hello, so here I am once more...
I want to report a new bug.
Well, it's not an application bug, but a documentation bug.
In the index.html file of the doc, the href are local references (fine...).
But in other html files, they are web references.
An exemple : in tt_qa.html, the links to the composer, audiolab, racks and skin sdk are not local href : they don't work if you don't have an internet connexion.

Plus : the link to the skin sdk is not a valid URL.

Now just a question :
why is the pan control on a rack is not assignable to a midi CC ?

And last but not least : if you are searching for beta-testers, I will be happy to help...

Post

pquenin wrote:Hello, so here I am once more...
I want to report a new bug.
Well, it's not an application bug, but a documentation bug.
In the index.html file of the doc, the href are local references (fine...).
But in other html files, they are web references.
An exemple : in tt_qa.html, the links to the composer, audiolab, racks and skin sdk are not local href : they don't work if you don't have an internet connexion.
OK, fixed in the next release. Thanks for reporting!
Plus : the link to the skin sdk is not a valid URL.
Also fixed in the next release.
Now just a question :
why is the pan control on a rack is not assignable to a midi CC ?
Will be automatable in the next version ;)
And last but not least : if you are searching for beta-testers, I will be happy to help...
Please send me an email and i'll add you to the group.

Post

muzycian wrote:
pquenin wrote:why is the pan control on a rack is not assignable to a midi CC ?
Will be automatable in the next version ;)
Euh, to be correct: It IS automatable in MU.LAB 1.1.

And you CAN also assign a MIDI controller to a rack panner, but to do this, you have to make a little detour:

* right-click the volume slider
* choose "Assign MIDI Controller"
* now choose the other parameter "Stereo Panning" or "Stereo Width"

In the next MU.LAB, the rack panner will have it's own context menu, so you don't have to make the little detour via the volume slider anymore ;)

Post Reply

Return to “MuTools”