Page 1 of 1

Posted: Mon Jun 18, 2007 23:04
by suzybee
Hello,
I've been having a similar problem with 2.41.
I trigger my clips with MIDI from Ableton from another computer, and run them using the MIDI clock. I have found that although 2.41 is more stable in general, it has the new problem that the MIDI clock seems to stop unexpectedly, and I have to restart my computer before it will recognise the MIDI clock signal again. This has happened during live sets which is really upsetting! I need to find out how to stop this happening. It would be helpful to know how common this problem is.
(WindowsXP, 3Ghtz Intel Pentium 4, ATI Mobility Radeon 9700)

Posted: Tue Jun 19, 2007 09:07
by bart
hmm strange .. especially that you have to restart your computer for it to work again, this might suggest that the drivers have crashed. Could you please turn on the debug log and send it to us after this has happened again? We might be able to see some errors in the log file.

Here are instructions to turn on error logging:
http://www.resolume.com/forum/viewthread.php?tid=3187

Posted: Tue Jun 19, 2007 22:36
by suzybee
ello,
I'll do the debug log, too.
the problem seems to be quite random, but I'll send the file when it occurs.
Cheers for your help.

Posted: Tue Jul 17, 2007 21:58
by suzybee
I recently did a laid-back gig, where I just used the manual clock instead of using the external midi device which I usually use, and there was no problem. This suggests that the problem I'm having is specific to the external midi clock function.
I don't believe it's my hardware, because the problem doesn't occur with version 2.4, using the same set-up.
Meanwhile, I will do the log when I can.
Cheers:)