MuLab & MUX VST 7.4.6
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
It's still too vague for me, sorry.
Can you repeat the crash each time again using the same steps?
If yes then please remove all VSTs one by one, and each time verify if you can still repeat the crash with the same step by step. Then if you have a project without VSTs with which you can still repeat the crash then please send me the project together with an very precise description of each step i have to take so to repeat that crash. Thanks.
Can you repeat the crash each time again using the same steps?
If yes then please remove all VSTs one by one, and each time verify if you can still repeat the crash with the same step by step. Then if you have a project without VSTs with which you can still repeat the crash then please send me the project together with an very precise description of each step i have to take so to repeat that crash. Thanks.
- KVRist
- 367 posts since 26 Feb, 2017 from Lituania,Vilnius
Hi,mutools wrote: Can you repeat the crash each time again using the same steps?
Yes I can repeat without VST; in the case will send all steps,I make movies;
otherwise We will not send anything
Thenks
p.s.
I also want that your "baby" would be a great! and falling from the carrier
I love him
Orion, Bitwig, Tracktion, Mixbus
Win 10, intel i7, ram 20 steinberg UR22mkII
Win 10, intel i7, ram 20 steinberg UR22mkII
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Imstre, just wondering: Why doesn't the MuLab log file of the 2nd crash (Log-20170413-192417.Txt) start with the normal log file header "OpSys=Windows" etc... Did you truncate it yourself before zipping it?
- KVRist
- 367 posts since 26 Feb, 2017 from Lituania,Vilnius
no no,sending and zipping Original...maybe..after the first crash send txt yes andmutools wrote:Imstre, just wondering: Why doesn't the MuLab log file of the 2nd crash (Log-20170413-192417.Txt) start with the normal log file header "OpSys=Windows" etc... Did you truncate it yourself before zipping it?
then (project was not saved therefore second time clicks in autosave di crashed projeckt and I worked further and occurred next crash - send txt intact.
Thanks
Orion, Bitwig, Tracktion, Mixbus
Win 10, intel i7, ram 20 steinberg UR22mkII
Win 10, intel i7, ram 20 steinberg UR22mkII
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Hm. I just
noticed something. Up until 7.3.12, MuLab audio out to my ASIO driver works perfectly well. 7.3.14 and 7.3.16 produce no audio.
I've reverted to 7.3.2 with no user settings at all, then tried applying the patch files. Changing from 12 to 14 stops the audio. Changing from 14 to 12 makes the audio work again. 16 is as silent as 14. There's nothing obviously not working - no diagnostics, it looks like it's working, just no sound.
I've reverted to 7.3.2 with no user settings at all, then tried applying the patch files. Changing from 12 to 14 stops the audio. Changing from 14 to 12 makes the audio work again. 16 is as silent as 14. There's nothing obviously not working - no diagnostics, it looks like it's working, just no sound.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Are you sure you have the latest version of your driver?
About the difference: Indeed, starting with M7.3.14 it's build on a new system.
But it should not make a difference. At least theoretically.
Pls check the driver version. Thx.
About the difference: Indeed, starting with M7.3.14 it's build on a new system.
But it should not make a difference. At least theoretically.
Pls check the driver version. Thx.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Yes. They don't make newer ones. 2013-01-28 https://echoaudio.com/pages/windows-drivers
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I will but only MuLab is failing out of all my ASIO software.mutools wrote:Please try reinstalling the driver.
--EDIT--
Done -- no difference, 7.3.12 works and 7.3.14 and 16 do not work.
- KVRist
- 367 posts since 26 Feb, 2017 from Lituania,Vilnius
Hi,
Crash
work whit basic step sequonser and...
I repeated but did not crash.
Crash
I repeated but did not crash.
You do not have the required permissions to view the files attached to this post.
Orion, Bitwig, Tracktion, Mixbus
Win 10, intel i7, ram 20 steinberg UR22mkII
Win 10, intel i7, ram 20 steinberg UR22mkII
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Is that both with MuLab 32 bit and 64 bit?pljones wrote:I will but only MuLab is failing out of all my ASIO software.mutools wrote:Please try reinstalling the driver.
--EDIT--
Done -- no difference, 7.3.12 works and 7.3.14 and 16 do not work.
And what exactly is failing?
Do you get an error message?
If not then right-click MuLab's CPU display -> Show Audio Engine Stats
Does the callback counter go up all the time?
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
I don't see crash details (= "Exception" info) in the MuLab log so you didn't get a red alert so pls include the Windows crash details from the event viewer.imstre wrote:Hi,
Crashwork whit basic step sequonser and...
I repeated but did not crash.
Also: The MuLab log tells that the only action you did was minimizing a window.
Are you sure you included the respective MuLab log of the crash?
- KVRist
- 367 posts since 26 Feb, 2017 from Lituania,Vilnius
you are right! not that log !mutools wrote:imstre wrote: Also: The MuLab log tells that the only action you did was minimizing a window.
Are you sure you included the respective MuLab log of the crash?
Orion, Bitwig, Tracktion, Mixbus
Win 10, intel i7, ram 20 steinberg UR22mkII
Win 10, intel i7, ram 20 steinberg UR22mkII
- KVRian
- 1451 posts since 4 Oct, 2012 from Utah
I had a similar issue with my Focusrite Scarlett 2i2 when I upgraded to 7.3.16. The solution for me (after a couple days fighting with it) was a clean Mulab install and an clean ASIO driver install.pljones wrote:I will but only MuLab is failing out of all my ASIO software.mutools wrote:Please try reinstalling the driver.
--EDIT--
Done -- no difference, 7.3.12 works and 7.3.14 and 16 do not work.
This is an odd occurrence as I don't believe Jo changed much to the audio engine in the update. I wonder what's causing the interfacing problem.
Dakkra
Software portfolio
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
It's indeed odd. I'm looking into this with pljones via email. Will post the result here. I'm not sure if it's about a same issue as with your asio driver. Did you download the latest driver? Maybe that fixed it on your system?
