You are viewing an archive of the old fxhome.com forums. The community has since moved to hitfilm.com.

Director Player Error

Posted: Sat, 17th Apr 2010, 7:22pm

Post 1 of 12

Fudge Dog

Force: 1955 | Joined: 17th May 2009 | Posts: 80

VisionLab User FXpreset Maker FXhome Movie Maker

Gold Member

Every time i start Vision Lab i get to the credit thing about FXHome Team and quality assurance. But then this message comes up "Director Player Error. Script Error, Continue? When you click yes it does nothing and stays on the screen and then say it not responding. If you press no it turns off the program. I've reinstalled the program twice, i've scanned it for virus's with two programs. And i was wondering what i should do now? It just happened suddenly.
Posted: Sat, 17th Apr 2010, 9:45pm

Post 2 of 12

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

Knowledgebase'd!!!

There are very specific steps that have to be followed when re-installing to perform a clean re-install. Otherwise, the re-install won't have the desired effect. Double-check to make sure you aren't overlooking or skipping any of the steps in the process.
Posted: Sat, 17th Apr 2010, 10:31pm

Post 3 of 12

alienux

Force: 1050 | Joined: 6th Jan 2010 | Posts: 299

CompositeLab Pro User EffectsLab Pro User Windows User

Gold Member

Axeman wrote:

Knowledgebase'd!!!
For some reason, every time I see that, I hear it in my head in Strong Bad's voice a la the www.homestarrunner.com 404 error page:

http://www.homestarrunner.com/404d.htm
Posted: Sun, 18th Apr 2010, 12:15am

Post 4 of 12

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

That's cause that's the voice I use when I type it.

Arrow'd!!!

Aaaaagghhh! My most of me!!!
Posted: Sun, 18th Apr 2010, 2:15am

Post 5 of 12

alienux

Force: 1050 | Joined: 6th Jan 2010 | Posts: 299

CompositeLab Pro User EffectsLab Pro User Windows User

Gold Member

I suspected that was that case smile

Sorry Fudge Dog, didn't mean to hi-jack your thread whistle
Posted: Thu, 29th Apr 2010, 10:23pm

Post 6 of 12

jamesnatale

Force: 1000 | Joined: 16th Jul 2008 | Posts: 1

VisionLab User

Gold Member

I get a Director Player Error too, first one says, Property not found #icon, I click OK, it says String Expected <viod>, if I click OK the first error comes up, if i click Cancel it does the same thing, it just does this over and over again.
Posted: Thu, 29th Apr 2010, 10:31pm

Post 7 of 12

rogolo

Force: 5436 | Joined: 29th May 2005 | Posts: 1513

VisionLab User VideoWrap User PhotoKey 4 User MacOS User

Gold Member

Have you tried all of the steps in the Knowledgebase article that is linked above?
Posted: Fri, 30th Apr 2010, 7:05pm

Post 8 of 12

Jabooza

Force: 2743 | Joined: 21st Jul 2006 | Posts: 1446

VisionLab User VideoWrap User FXpreset Maker FXhome Movie Maker MacOS User

Gold Member

I'm having a similar problem. I get director player messages whenever I open a specific project, after clicking ok or cancel on the messages the project just looks like a blank timeline, then more director play messages come up anytime I click anything on the timeline.
And yes, I did a clean reinstall exactly following the given instructions. I was also using an admin account if that matters.

I have to say, it's highly annoying that VisionLab has been persistently having these kinds of problems, requires a clean reinstall at least once a month, and even when it is working, has very poor performance because of FXhome's apparent inability to make it universal binary.
Posted: Fri, 30th Apr 2010, 7:32pm

Post 9 of 12

Fxhome Dude

Force: 996 | Joined: 1st Jun 2009 | Posts: 927

CompositeLab Pro User FXpreset Maker FXhome Movie Maker Windows User

Gold Member

Jabooza, someone actually posted about how they fixed the damaged project file issue. Linky I have no idea if your case is the same or if it'll work but if your careful it's worth a shot. Very careful.
Posted: Fri, 7th May 2010, 4:13pm

Post 10 of 12

Jabooza

Force: 2743 | Joined: 21st Jul 2006 | Posts: 1446

VisionLab User VideoWrap User FXpreset Maker FXhome Movie Maker MacOS User

Gold Member

Mm, I don't know anything about code though. I don't think I'd trust myself even if I did know how to do that.

Alright, so if project files can randomly corrupt, what am I expected to do when I'm working on something important and it corrupts? I'd lose the whole project.
Posted: Fri, 7th May 2010, 11:58pm

Post 11 of 12

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

You would only lose the whole project if you only save one iteration of it (never a good idea in video work, or any work involving large files and extensive periods of editing), don't have a backup (never a good idea with anything on your computer), and don't save regularly.

The potential for a project file to develop errors over time is one of the reasons that it is recommended, with pretty much any video app, that you save multiple versions of the project, at different stages, and backup those versions along with everything else on your machine. Then when something does happen, you can take one step back, and continue from there, rather than having to go back to square one.

What would be rad is if Vlab automatically handled iterations and older versions for you, like Final Cut does.
Posted: Fri, 14th May 2010, 1:15am

Post 12 of 12

Jabooza

Force: 2743 | Joined: 21st Jul 2006 | Posts: 1446

VisionLab User VideoWrap User FXpreset Maker FXhome Movie Maker MacOS User

Gold Member

Well, I understand that files should be backed up and everything, but I'd still feel a lot more secure if VisionLab actually worked properly and didn't corrupt projects in the first place.