View Full Version : Wierd Playback
Sharkey
12-28-2009, 12:47 PM
Hey guys,
Sometimes when I play some of my sequences, especially parts where it's blinking fairly fast, it stops for a second or too, and gets off beat, or some other times it stays on for too long.
At other times, channels that shouldn't come on come on at times during a sequence. For a split second.
Maybe this is what "Misfires" are?
Is there a way to reduce this? My cable from my computer to my grinch board is only about 2-4 feet.
Virtus
12-28-2009, 01:42 PM
It sounds like you are running the adjustable preview and the output plugin both at the same time. Depending on how detailed (large) you photo in the preview is it can become very CPU intensive/consuming. If you are using both at the same time, try unchecking the adjustable preview and see if it still 'stutters' outside.
XmasInGalt
12-28-2009, 03:23 PM
I also had the same problem when I was running a sequence and moving the mouse around to scroll up/down/left/right. When I stopped messing with the mouse, it ran fine. I assumed it was some kind of video refresh / cpu issue.
dirknerkle
12-28-2009, 04:41 PM
Other things that can cause this are background operations such as Windows update, an anti-virus software update, or even a Flash update. If the computer is also connected to the Internet, I'd suggest the following:
1. Disconnect the network cable so it cannot use the Internet at all.
2. Dedicate the computer to running the show. Make sure the performance is set to accentuate foreground operations.
3. Uninstall any games or other unnecessary software. If the PC is dedicated to your show, you won't need them anyway.
4. Uninstall any anti-virus, anti-spam or spyware software. You won't need it if your PC isn't on the Internet or connected to a network at all.
5. Run a hard disk defrag.
You won't believe how fast it will run afterward. It probably won't lag at all anyplace.
The best of all fix is:
1. Reformat your hard disk
2. Install a fresh copy of XP SP3.
3. Install any other drivers as may be necessary for your motherboard, video card and sound card. None of the other drivers are necessary at all.
4. Install the appropriate dot net framework for Vixen.
5. Install Vixen.
Sharkey
12-28-2009, 05:16 PM
I should of included some more info, this PC in the basement is dedicated to the show.
It does connect to my network, but I like that because I can do a remote connection with my laptop outside when testing things. (Is there a way to connect to the local network but not the internet?)
no other software is installed. But after this year's show I'll reinstall Windows XP.
Thanks for the help guys :D
dirknerkle
12-28-2009, 05:30 PM
It does connect to my network, but I like that because I can do a remote connection with my laptop outside when testing things. (Is there a way to connect to the local network but not the internet?)
You could try blocking port 80, unless you remote into it that way. If you're just using remote desktop, take a look at the following link -- might be helpful to you for changing RDC's port.
http://www.me.gatech.edu/support/computer/xp_remote_access/index.html
You also likely have a router on your home network. You can assign an IP address to the show computer and then block that IP address from using the internet in the router's firmware -- that will solve any outgoing attempts from the computer. Of course, you need to turn off any auto-updates, etc. from everything.
Then of course, turn up the firewall to "TALIBAN" level so nothing goes through, disable file/printer sharing, and only allow RDC through it. Those are a few starters, but anytime you hang the PC on the network, you're exposing it to the Internet and "stuff" can happen. I choose to keep the PC pristine and clean and not hook it up to anything. If it were on my network, then I'd have to do firewalls, all those screwy settings, etc. and the more of that thing you do, the more you're asking Windows to do things in the background that takes away processor cycles.
Sharkey
12-28-2009, 05:55 PM
Okay, maybe next year i'll be more prepared and not need to do remote desktop ;)
Once again, thank you!
Powered by vBulletin® Version 4.1.10 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.