Every time I follow this process MuLab crashes, however it may be due to the problem I'm having with my MiniNova not working on this PC properly. Thought I'd post and see if anyone could do a quick test to see if the problem is at my end or with MuLab.
1. Start MuLab and current project.
2. Click on keyboard at top right. Not sure if that bit is necessary.
3. Open MIDI devices from MuLab Menu and then click OK.
4. MuLab crashes or maybe after again clicking the top right keyboard.
v6.5.33
Can someone please check.
Thanks
Possible crash in Mulab
-
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I just tried and couldn't get a crash - but it's worth checking:
Windows 32, Windows 64 or Mac?
When you say "current project" is that important -- does it also crash in a completely empty new project from template?
Does the keyboard click have to play anything? If so, does it make any difference what it plays?
When I open MULAB->MIDI Setup, I just click OK? No changing the MIDI devices inside MuLab or the actual devices connected?
When you say "crashes" do you mean closes completely without prompt or pops up a serious error box or freezes or something else specific?
Windows 32, Windows 64 or Mac?
When you say "current project" is that important -- does it also crash in a completely empty new project from template?
Does the keyboard click have to play anything? If so, does it make any difference what it plays?
When I open MULAB->MIDI Setup, I just click OK? No changing the MIDI devices inside MuLab or the actual devices connected?
When you say "crashes" do you mean closes completely without prompt or pops up a serious error box or freezes or something else specific?
-
- KVRAF
- Topic Starter
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Win8.1 x64 16GBRAM i74770K
Current Project: Unknown. Will test more tomorrow if I can.
The focus was on a VST Superwave P8. Did I need to play a note? Don't know.
MIDI Setup: I was trying to solve a different issue and first clicked MIDI Input 1 to set to None then back to MiniNova, then OK. Another attempt I simply clicked OK. Both caused a crash.
Crashes: MuLab freezes, then I get error message from Windows saying the program is not responding and a choice to wait or close. Waiting simply prolongs the agony!
I have been having minor issues with this setup since putting together but have no idea what the problem is
Current Project: Unknown. Will test more tomorrow if I can.
The focus was on a VST Superwave P8. Did I need to play a note? Don't know.
MIDI Setup: I was trying to solve a different issue and first clicked MIDI Input 1 to set to None then back to MiniNova, then OK. Another attempt I simply clicked OK. Both caused a crash.
Crashes: MuLab freezes, then I get error message from Windows saying the program is not responding and a choice to wait or close. Waiting simply prolongs the agony!
I have been having minor issues with this setup since putting together but have no idea what the problem is
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Missed one obvious question 
. What if you leave the screen keyboard alone entirely - can you continue working, write a new sequence and playback, etc?
. What if you leave the screen keyboard alone entirely - can you continue working, write a new sequence and playback, etc?-
- KVRAF
- Topic Starter
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- Topic Starter
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Can you think if there's something you might have stopped doing, without really noticing?
Otherwise it gets blamed on UFOs or Windows Update...
Otherwise it gets blamed on UFOs or Windows Update...
-
- KVRAF
- Topic Starter
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
No, to be honest it could be my MiniNova causing it? It's starting to tick me off why it ain't working even though it shows up in any midi app.
You wouldn't be nice enough to help would you?
You wouldn't be nice enough to help would you?
-
- KVRAF
- 1925 posts since 29 Mar, 2013
Do you turn on the keyboard before or after opening Mulab, it used to be that some daws wouldnt recognise them if turned on afterwards, just a thought
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Are you using it via USB? If so, do you have a MIDI In port you could use instead to see if it's the USB MIDI driver? Oh, did it come with its own USB MIDI driver and have you checked for updates for it?sl23 wrote:No, to be honest it could be my MiniNova causing it? It's starting to tick me off why it ain't working even though it shows up in any midi app.
You wouldn't be nice enough to help would you?
-
- KVRAF
- Topic Starter
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Yes, via USB. No, I don't have midi in port. Yes, it came with midi driver and yes it's been updated.
I've done everything I can think of except update bios as recommended by novation, though not so sure about that. I have had problems updating the firmware, couple times it hangs but won't update, or even show on MiniNova display.
I've installed MiniNova software, it worked until next used it, so tried re-installing. It worked, but again, only until next use. Then I cottoned on to what was happening. But now a reinstallation won't work at all.
Each installation requested update of firmware, I accepted, sometimes worked sometimes it would hang. I also tried the beta installer but same issues.
Is it windows 8? Or have I screwed up something in windows maybe that would interfere with communication? Turned off service or uninstalled something though doubtful might be that?
It's driving me nuts!
I've done everything I can think of except update bios as recommended by novation, though not so sure about that. I have had problems updating the firmware, couple times it hangs but won't update, or even show on MiniNova display.
I've installed MiniNova software, it worked until next used it, so tried re-installing. It worked, but again, only until next use. Then I cottoned on to what was happening. But now a reinstallation won't work at all.
Each installation requested update of firmware, I accepted, sometimes worked sometimes it would hang. I also tried the beta installer but same issues.
Is it windows 8? Or have I screwed up something in windows maybe that would interfere with communication? Turned off service or uninstalled something though doubtful might be that?
It's driving me nuts!
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Hm, could be. Have you tried installing and running the software from somewhere outside Windows' control (say "C:\My Software")? It could just be that Windows' system protection is confusing the software somehow.sl23 wrote:Is it windows 8?
-
- KVRAF
- Topic Starter
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
It doesn't give the option to change location except for the VST's.
I think I've solved it but am going to test a bit more first. As explained here, it was probably caused by my USB2 extension cable or maybe the USB3 port actually? As that's where it's plugged in, just noticed!
Thanks for your help pljones
I think I've solved it but am going to test a bit more first. As explained here, it was probably caused by my USB2 extension cable or maybe the USB3 port actually? As that's where it's plugged in, just noticed!
Thanks for your help pljones