Matilde Crash
Matilde Crash
I been having a problem with matilde tracker. What is the current version? I am using 1.9rc7
All instances crash. Maybe its something to do with a vst I loaded? If I close buzz and reopen the bmx, it works fine for some time. Im gonna investigate it further.
All instances crash. Maybe its something to do with a vst I loaded? If I close buzz and reopen the bmx, it works fine for some time. Im gonna investigate it further.
Re: Matilde Crash
I'm using 1.9rc7 as well and no problems at all with latest version of buzz. Try and recreate what you were doing so we can check it out (:
Re: Matilde Crash
are you using some effect commands in matilde ?
maybe delete everything else in the bmx and upload it so others can test
maybe delete everything else in the bmx and upload it so others can test
Re: Matilde Crash
The 'crash' isn't the "loadlibrary fail" one is it ?
Re: Matilde Crash
Sorry for leaving you speaking alone! Im gonna try to recreate it. I had that before, mixing different versions of matilde in on bmx. I dont have the bmx anymore, because a switched to utrackers and keep on working. But will recreate it.
Re: Matilde Crash
Problems, with Matilde or other trackers in the recent versions of NEW BUZZ often happen to me..
With Buzz 1116 (+Matilde 1,5 and 1,9 rc7) no problem.
With Buzz 1430 (+Matilde 1,5; 1,7; 1,9rc7) : 2 examples :
a/ BD wave (44100Hz 16bits Mono) : all is OK
b/ Drumloop (44100Hz 16bits Stereo) : crash with the 3 Matilde versions
I've tested the 20 first loops of the same Samples collection, no problem with 17 loops but 3 loops crash ( all is OK with Buzz 1116!)
In the past I found a workaround which works: I import samples in Audacity and export them again (in the same format), then Buzz accepts them.
With Buzz 1116 (+Matilde 1,5 and 1,9 rc7) no problem.
With Buzz 1430 (+Matilde 1,5; 1,7; 1,9rc7) : 2 examples :
a/ BD wave (44100Hz 16bits Mono) : all is OK
b/ Drumloop (44100Hz 16bits Stereo) : crash with the 3 Matilde versions
I've tested the 20 first loops of the same Samples collection, no problem with 17 loops but 3 loops crash ( all is OK with Buzz 1116!)
In the past I found a workaround which works: I import samples in Audacity and export them again (in the same format), then Buzz accepts them.
Re: Matilde Crash
can you please try if it works of multithreading is off ?
Re: Matilde Crash
Can you test the problem waves (before you fix them in Audacity) with this tool ?beuze wrote:In the past I found a workaround which works: I import samples in Audacity and export them again (in the same format), then Buzz accepts them.
Re: Matilde Crash
1/ File is OK (just tested on Robot Planet)
2/ How to set the multithreading off ?
3/ (Matilde crash means Matilde makes a noise (instead reproduce correctly the wave) but don't really crashes)
2/ How to set the multithreading off ?
3/ (Matilde crash means Matilde makes a noise (instead reproduce correctly the wave) but don't really crashes)
Re: Matilde Crash
1) can you upload the wav somewhere please, i want to see / hear this
2) view / settings / engine / multithreading
3) thats a different story of course....
2) view / settings / engine / multithreading
3) thats a different story of course....
Re: Matilde Crash
1/ Here is the link : http://www.megaupload.com/?d=T12VPJ0I
2/ Multithreading on False or True, the problem is the same
2/ Multithreading on False or True, the problem is the same
Re: Matilde Crash
ok... here's how you fix this:
1) import the sample as usual into buzz
2) problem: the root note gets set to c-0 (the wav has these wrong attributes)
3) set the root note to c-4 (or whatever sounds right)
4) play the sample in matilde, everything's ok
i'd hardly call this "noise" btw, its just a highpitched drumloop. sorry but this should have been obvious..
1) import the sample as usual into buzz
2) problem: the root note gets set to c-0 (the wav has these wrong attributes)
3) set the root note to c-4 (or whatever sounds right)
4) play the sample in matilde, everything's ok
i'd hardly call this "noise" btw, its just a highpitched drumloop. sorry but this should have been obvious..