MuTools

MuTools · Post by **MuTools** » Mon Feb 15, 2010 4:11 pm

NBV wrote:I had this composition with just two MIDI sequences. Then I highlighted the second sequence to copy and paste it (after I defined shortcuts Ctrl+C and Ctrl+V in the shortcut editor) then I pressed Ctrl+C and Mu.Lab showed this prompt which says "A serious error has occured. This may be caused by the applicaton or by any plugins! ..."

I'm running Windows XP SP2 on a Intel CPU 2140 @ 1.60 GHz
2 Gb RAM. At the point the bug occured, I was employing a Line 6 Guitar Port interface, with the latest drivers, and Pod Farm, the Line 6 amp simulation software. But I reproduced the bug with a Sound Blaster Live! and ASIO4all driver.

Here is the log of the last time it happened, a few minutes ago. It has happened four times, exactly the same way. If you need the other logs, just let me know:

So you can repeat this crash?

Can you give me the exact steps how to repeat it?

Eventually email me a MuSession with which i can repeat it.

Thanks.

MuTools · Post by **MuTools** » Mon Feb 15, 2010 4:12 pm

Bonteburg wrote:When I only record a MIDI sequence but the Audio button (little wave thingie) is also active, instead of saying "recording too silent" like it used to, MU.LAB creates a sequence with a very low metronome sound drowned out by a big noise floor. Is this meant to happen?

afterthought:
Maybe "Audio Recording Threshhold" defaults to another value now, will check.

Sounds like you're recording what you hear, i mean: isn't there a mic (computer built-in?) that is picking up your speakers?

NBV · Post by **NBV** » Mon Feb 15, 2010 4:39 pm

mutools wrote:
NBV wrote:I had this composition with just two MIDI sequences. Then I highlighted the second sequence to copy and paste it (after I defined shortcuts Ctrl+C and Ctrl+V in the shortcut editor) then I pressed Ctrl+C and Mu.Lab showed this prompt which says "A serious error has occured. This may be caused by the applicaton or by any plugins! ..."

I'm running Windows XP SP2 on a Intel CPU 2140 @ 1.60 GHz
2 Gb RAM. At the point the bug occured, I was employing a Line 6 Guitar Port interface, with the latest drivers, and Pod Farm, the Line 6 amp simulation software. But I reproduced the bug with a Sound Blaster Live! and ASIO4all driver.

Here is the log of the last time it happened, a few minutes ago. It has happened four times, exactly the same way. If you need the other logs, just let me know:
So you can repeat this crash?

Can you give me the exact steps how to repeat it?

Eventually email me a MuSession with which i can repeat it.

Thanks.

Just deleted the added shortcuts for copy and paste, and everything is OK againt. False alarm.

NBV · Post by **NBV** » Mon Feb 15, 2010 5:15 pm

mutools wrote:
NBV wrote:I had this composition with just two MIDI sequences. Then I highlighted the second sequence to copy and paste it (after I defined shortcuts Ctrl+C and Ctrl+V in the shortcut editor) then I pressed Ctrl+C and Mu.Lab showed this prompt which says "A serious error has occured. This may be caused by the applicaton or by any plugins! ..."

I'm running Windows XP SP2 on a Intel CPU 2140 @ 1.60 GHz
2 Gb RAM. At the point the bug occured, I was employing a Line 6 Guitar Port interface, with the latest drivers, and Pod Farm, the Line 6 amp simulation software. But I reproduced the bug with a Sound Blaster Live! and ASIO4all driver.

Here is the log of the last time it happened, a few minutes ago. It has happened four times, exactly the same way. If you need the other logs, just let me know:
So you can repeat this crash?

Can you give me the exact steps how to repeat it?

Eventually email me a MuSession with which i can repeat it.

Thanks.

Hi Jo. I was tweking around and it seems it is a plugin-related crash, not a Mu.Lab generated crash. It happens with always with the same plugin: the old drum sampler packed in the Computer Music's DVD, SR202.

cytone · Post by **cytone** » Mon Feb 15, 2010 5:25 pm

Instant crash if you start with an empty song then issue Tracks - Delete unused tracks.

Bonteburg · Post by **Bonteburg** » Mon Feb 15, 2010 5:27 pm

mutools wrote:
Bonteburg wrote:When I only record a MIDI sequence but the Audio button (little wave thingie) is also active, instead of saying "recording too silent" like it used to, MU.LAB creates a sequence with a very low metronome sound drowned out by a big noise floor. Is this meant to happen?

afterthought:
Maybe "Audio Recording Threshhold" defaults to another value now, will check.
Sounds like you're recording what you hear, i mean: isn't there a mic (computer built-in?) that is picking up your speakers?

I guess there would have been my electric guitar going straight into the Mini Mac...

what do you think. Could a guitar pickup be enough for such an artefact to happen? I think it's conceivable!

The only really curious thing is it wouldn't have happened in any of MU.LAB's previos builds.

MuTools · Post by **MuTools** » Mon Feb 15, 2010 5:31 pm

cytone wrote:Instant crash if you start with an empty song then issue Tracks - Delete unused tracks.

Yes, fixed in the next version, thanks!

MuTools · Post by **MuTools** » Mon Feb 15, 2010 5:36 pm

Bonteburg wrote:
mutools wrote:
Bonteburg wrote:When I only record a MIDI sequence but the Audio button (little wave thingie) is also active, instead of saying "recording too silent" like it used to, MU.LAB creates a sequence with a very low metronome sound drowned out by a big noise floor. Is this meant to happen?

afterthought:
Maybe "Audio Recording Threshhold" defaults to another value now, will check.
Sounds like you're recording what you hear, i mean: isn't there a mic (computer built-in?) that is picking up your speakers?
I guess there would have been my electric guitar going straight into the Mini Mac...

what do you think. Could a guitar pickup be enough for such an artefact to happen? I think it's conceivable!

To be honnest: I don't know, but i would doubt it.

The only really curious thing is it wouldn't have happened in any of MU.LAB's previos builds.

So that's using 3.0.20, right?

Can you please redo the exact same thing with 3.0.18 and make sure there is a difference between 3.0.18 and 3.0.20 using the exact same setup.

If you need 3.0.18 again, please let me know.

Bonteburg · Post by **Bonteburg** » Mon Feb 15, 2010 5:43 pm

Not a problem - I'll post the results tonight. (hopefully!)

Jazz Franco · Post by **Jazz Franco** » Mon Feb 15, 2010 9:40 pm

Xils 3 Le works just fine here (OSX10.4). Nowhere to rewire though.

fceramic · Post by **fceramic** » Mon Feb 15, 2010 10:51 pm

Damn why am I so unlucky? I even installed the latest version (1.04a?) of Xils 3 LE.
It's just completely f**ks up both in AUlab and Mulab.

liquidsound · Post by **liquidsound** » Tue Feb 16, 2010 4:27 am

fridtjof wrote:Damn why am I so unlucky? I even installed the latest version (1.04a?) of Xils 3 LE.
It's just completely f**ks up both in AUlab and Mulab.

Let me ADD two more victims:
Just downloaded the 1.1.0 demo (or about)
MuLab froze after about 5 minutes.
AND
energyXt got into coma after no more than two minutes.
FL no chance, I had to Hard Reboot.

Maybe a nice synth but... man, a nasty attitude!
(and a CPU Anaconda)

fceramic · Post by **fceramic** » Tue Feb 16, 2010 11:19 am

They did state this was a bug, but would only be fixed in the full version of the synth! Damn them!

MuTools · Post by **MuTools** » Tue Feb 16, 2010 12:25 pm

fridtjof, do you have any news on the MIDI output issue you reported?
(cfr my question on this some posts ago)

Curious for your answer.

liquidsound · Post by **liquidsound** » Tue Feb 16, 2010 1:05 pm

fridtjof wrote:Damn them!

You're Damn Right! (Full version Only?!!!)

This is why I like the MUX.

I can trow in there anything and the only limit is the CPU. Better than the Reason's Combinator (which you are limited to the built-in synths...).

MuTools

KVR Audio

M3 Tests