Does Mutools have a crash log?
-
- KVRist
- 179 posts since 26 Feb, 2007
Hey all,
I am experiencing some strange crashes. When dragging sequences around it crashes hard to desktop immedialty without even a crashmessage from OSX .
(with playback stopped and nothing really going on in the project, everything muDevices and Midi-only.)
I can completely recreate this everytime.
(This is on OSX 10.9.5, Intel 3.33 Ghz 6-Core Xeon machine)
I was searching for some kind of crash-log, but can't find one. Is there some kind of log-file somewhere?
(I also have uploaded a small video to show the issue. You might have to press the HD button to get a better quality.)
https://vid.me/Spda
Ay ideas on that one?
Thanks,
tL.
I am experiencing some strange crashes. When dragging sequences around it crashes hard to desktop immedialty without even a crashmessage from OSX .
(with playback stopped and nothing really going on in the project, everything muDevices and Midi-only.)
I can completely recreate this everytime.
(This is on OSX 10.9.5, Intel 3.33 Ghz 6-Core Xeon machine)
I was searching for some kind of crash-log, but can't find one. Is there some kind of log-file somewhere?
(I also have uploaded a small video to show the issue. You might have to press the HD button to get a better quality.)
https://vid.me/Spda
Ay ideas on that one?
Thanks,
tL.
Professional.
-
- KVRian
- 855 posts since 3 Mar, 2009
Mulab/Help/Start Logging
After activating i would propose you close and restart Mulab first with 'Continue Logging: Yes'.
Then do your crash procedure.
No idea where the log can be found on OSX. It's in Mulab's main folder on WIN.
After activating i would propose you close and restart Mulab first with 'Continue Logging: Yes'.
Then do your crash procedure.
No idea where the log can be found on OSX. It's in Mulab's main folder on WIN.
-
- KVRist
- Topic Starter
- 179 posts since 26 Feb, 2007
Okay thanks. Not much in there however.
I waited a little bit and at time of the crash, there is only one line added to the log:
FlFndr[287] -36
Hope that helps.
tL.
I waited a little bit and at time of the crash, there is only one line added to the log:
FlFndr[287] -36
Hope that helps.
tL.
Professional.
-
- KVRAF
- 1925 posts since 29 Mar, 2013
That looks similar to what l was experiencing not long ago, didnt find out what it was, just seemed to stop. Maybe one of the updates sorted it.
Im on win 7
Im on win 7
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
No MuLab proprietary crash log.
About the crash itself: Is that with any project or only with that specific project?
Which MuLab version?
About the crash itself: Is that with any project or only with that specific project?
Which MuLab version?
-
- KVRist
- Topic Starter
- 179 posts since 26 Feb, 2007
It looks like only with that specific project. I had that issue before with another project,
I just went on dragging and copying stuff part-per-part and then everything went okay from there.
Actually everything is usually very stable, this time I just could pinpoint it exactly.
When dragging and copying not everthing at once, theres no problem.
The muLab version is the latest AFAIK: MuLab UL 6.4.18
tL.
I just went on dragging and copying stuff part-per-part and then everything went okay from there.
Actually everything is usually very stable, this time I just could pinpoint it exactly.
When dragging and copying not everthing at once, theres no problem.
The muLab version is the latest AFAIK: MuLab UL 6.4.18
tL.
Professional.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Yes that's the latest version indeed. Please email me that (zipped) MuProject exactly as in the video so that i can try to repeat the crash.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Thanks for the MuProject.
It turned out that it contains a bunch of parts on track(s) above the very first track = unexisting track(s).
I don't know how that is possible, lets keep an eye on how this can happen.
Now to rescue that project:
It turned out that it contains a bunch of parts on track(s) above the very first track = unexisting track(s).
I don't know how that is possible, lets keep an eye on how this can happen.
Now to rescue that project:
- Open that project
- Select all parts using Apple+A
- Apple+X = cut them all.
- Position the mouse at position 1.1.0 and press Apple+V = paste them all.
-
- KVRist
- Topic Starter
- 179 posts since 26 Feb, 2007
I think I know now why that happened. When you have subtracks with content and the maintrack which "houses" the subtracks is folded, so that the subtracks are not visible anymore,mutools wrote:Thanks for the MuProject.
It turned out that it contains a bunch of parts on track(s) above the very first track = unexisting track(s).
I don't know how that is possible, lets keep an eye on how this can happen.
Now to rescue that project:That will make them all visible & valid again.
- Open that project
- Select all parts using Apple+A
- Apple+X = cut them all.
- Position the mouse at position 1.1.0 and press Apple+V = paste them all.
you do the following:
You rectangle select *wide enough* to include the subtracks, even if they are not visible.
When you start to drag you will likely see the white visual guide box two times, also on top of the arrangerpage. Thats potentially why this will create some havoc with invisble tracks.
If thats not clear, or you can't recreate it, I can make a video.
Best,
tL.
Professional.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Ok, so far so good. And indeed i see that the hidden parts are also selected which is not ok.LYTZ wrote:I think I know now why that happened. When you have subtracks with content and the maintrack which "houses" the subtracks is folded, so that the subtracks are not visible anymore,
you do the following:
You rectangle select *wide enough* to include the subtracks, even if they are not visible.
No i don't see that.When you start to drag you will likely see the white visual guide box two times, also on top of the arrangerpage.
Yes please. Or mail me a simple example project where that situation occurs.If thats not clear, or you can't recreate it, I can make a video.
-
- KVRist
- Topic Starter
- 179 posts since 26 Feb, 2007
Here is a short video that shows it.
It is just the default start project with three empty sequences. This behaviour is in *every* project when theese steps are recreated.
Potentially sometimes the sequences get even out of bounds of the arrangerpage, which would explain the invisible tracks.
I guess you only see the boxes on top of the arrangement when there are (enough?) tracks above them.
https://vid.me/ZMOO
It is just the default start project with three empty sequences. This behaviour is in *every* project when theese steps are recreated.
Potentially sometimes the sequences get even out of bounds of the arrangerpage, which would explain the invisible tracks.
I guess you only see the boxes on top of the arrangement when there are (enough?) tracks above them.
https://vid.me/ZMOO
Professional.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
