Ponddude Posted April 14, 2009 Share Posted April 14, 2009 I don't know if anyone else is experiencing this, but I am and it is becoming rather annoying.I don't use my LOR computer for much other then sequencing and the show, so I don't usually close my the SE. However, my computer is set to sleep after 15 minutes and when I wake it up, the SE is completely locked up. So bad that I can't even kill it in the task manager. I end up having to restart the computer. It isn't a huge thing, but it is rather bothersome.LOR 2.1.6Vista Home Premium 32-bit Link to comment Share on other sites More sharing options...
Ponddude Posted April 14, 2009 Author Share Posted April 14, 2009 Actually I really can't. The most I can say is that I it always happens with my computer. I would work on my sequence, leave the window open, step away from computer and it would go into sleep mode. When I return, no matter how long, the SE is locked up. Link to comment Share on other sites More sharing options...
-klb- Posted April 14, 2009 Share Posted April 14, 2009 With, or without the USB-485 adapter installed?The USB adapter/drivers get messed up going in and out of hibernate, so I would expect that suspend would do the same...Without the USB adapter, I can hibernate and resume with the sequence editor up with no problems.. Link to comment Share on other sites More sharing options...
Dr. Jones Posted April 14, 2009 Share Posted April 14, 2009 The sleep issue has been documented. I remember several people discussing it before (myself included)http://lightorama.mywowbb.com/forum72/18415.htmlhttp://lightorama.mywowbb.com/forum71/15518-5.htmltry these - and see if that helps Link to comment Share on other sites More sharing options...
Ponddude Posted April 14, 2009 Author Share Posted April 14, 2009 Hmmm... Kib you are onto something. I tried that today and it was fine. It is certainly interesting that an adapter screws it up. I will have to try it without the adapter and see what happens. Mine is always plugged in because I use it to control my DMX lights.Thanks for the info! Link to comment Share on other sites More sharing options...
George Simmons Posted April 15, 2009 Share Posted April 15, 2009 I had the same problem last fall on my home pc running XP. I never made the connection with it concerning the USB485, but after reading this thread I realized it hasn't happened since the first of the year when I disconnected everything. Hmmmm... now I've gotta reconnect the USB485 and see if it starts again also. Link to comment Share on other sites More sharing options...
Dr. Jones Posted April 15, 2009 Share Posted April 15, 2009 Jeff/ Ponddudedoes your usb adapter have a cable with the ferrite cores? Link to comment Share on other sites More sharing options...
Ponddude Posted April 15, 2009 Author Share Posted April 15, 2009 Well I tried this tonight, and the adapter has everything to do with it. I got the exact same results as Jeff. Certainly is interesting.Dr. Jones...no my usb cable does not have a core on it. Link to comment Share on other sites More sharing options...
Shubb Posted April 16, 2009 Share Posted April 16, 2009 I had the same problem last year. When I connected the USB adapter while the editor was open it would freeze the editor. I had to shut-down and re-start.After 3 or 4 times I would remember to shut down the editor and then plug in the adapter.Scott Link to comment Share on other sites More sharing options...
LightORamaDan Posted April 22, 2009 Share Posted April 22, 2009 We will take a look at it. Most likely it has to do with the USB driver hanging up when the PC goes to sleep. We will see what we can do. Link to comment Share on other sites More sharing options...
bob Posted April 29, 2009 Share Posted April 29, 2009 I just got this to happen on a Vista machine. I noticed that if I unplug the USB adapter (after the computer wakes up), the Sequence Editor "unfreezes". I can then plug the USB adapter back in, and the Sequence Editor can successfully control the lights thereafter.Does this workaround not work for anyone?Thanks. Link to comment Share on other sites More sharing options...
bob Posted April 30, 2009 Share Posted April 30, 2009 I believe this should be fixed in the next release. At least, it's fixed on the machine I tested on. Link to comment Share on other sites More sharing options...
Recommended Posts