Adding neon light [ANSWER]
Posted: Tue, 11th Dec 2007, 12:09pm
Post 1 of 13
I've just upgraded to Vision Lab from EffectsLab Pro and CompositeLab Pro.
I am now getting a "Director player error" String expected <void>. Followed by "Property not found" #scroll start.
This happens when I try and add a Neon light.
I have had this happen everytime with one of my projects and it has happened with an example project as well.
I am running a Pentium D 2.8
Geforce 6200 video card
Posted: Tue, 11th Dec 2007, 12:11pm
Post 2 of 13
Sounds like you need to do a clean reinstall.
Posted: Tue, 11th Dec 2007, 12:16pm
Post 3 of 13
Thanks for quick reply schwar.
I did do that already.
Followed instruction I found in the forums.
Unstalled program. Deleted fxhome directory from my documents. and the directorys in "local settings".
Posted: Wed, 12th Dec 2007, 12:29am
Post 4 of 13
I'm thinking that nobody else is having this problem?
Can anyone suggest anything else I can try?
Posted: Wed, 12th Dec 2007, 9:43am
Post 5 of 13
Sorry to hear you're having this problem, I've just tried the example lightsword project, and it seems to render fine, even adding more neon light objects, the program performs as it should.
Firstly, we uploaded a new update yesterday, so I'd do a clean reinstall, then install the new update so that you're working on the latest program.
Also make sure you are running the latest version of QuickTime
. This will ensure that your computer is up-to-date to run the software. I've not heard of anyone else having this problem, let me know if you are still having the issue after doing the above.
Posted: Wed, 12th Dec 2007, 9:58pm
Post 6 of 13
I have updated quicktime and directx. I believe I was already on the lastest version of directx. My quicktime version was 7.1.3, I have now updated to 7.3.
I still received the error when adding a neon light. I have then re-created the project, using the same video files and effects. I can now add a neon light without the crash! Maybe something was up with the conversion from compositelab?
One other thing... Now that I have upgraded quicktime, etc. I can no longer render to a quicktime file! I select render but, right has the quicktime options screen is displaying, visionlab crashes and closes down! No problems with AVI file creation.
Posted: Thu, 13th Dec 2007, 9:22am
Post 7 of 13
Do you have a NVidia graphics card?
If so there is a bug with the latest driver that has caused a conflict with Quicktime on your computer. We found that rolling back to a previous NVidia driver fixed the problem.
Hopefully NVidia and Apple can find a fix for their problem.
Posted: Thu, 13th Dec 2007, 11:41pm
Post 8 of 13
Yes. I'm guessing that is it.
I updated the NVidia video driver when I was doing the quicktime and directx updates.
So...I've worked around one problem and created another
I will just stick with AVI until quicktime or nvidia sort it out.
Thanks everyone for their help.
Posted: Sun, 3rd May 2009, 5:26am
Post 9 of 13
I am getting this same sequence of errors when I try adding a neon glow to a project; also get similar error messages when I try adding optic effects, though I can use laser effects no problem. I am currently trialling VisionLab Studio after checking out CompositeLab and EffectsLab and realising that to do everything I want it would be easier with VisionLab.
The common issue between the original post and my problem is that the file I am using is the original CompositeLab file. I tried opening the Lightswords example file and this opens fine, so perhaps this issue is actually nothing to do with drivers and is a problem with using CompositeLab files in VisionLab..?
I really like this product and am seriously considering purchasing VisionLab but with all the green-screen tweaks I have made I'm not keen on the idea of having to re-do all this - can someone please help?
Posted: Sun, 3rd May 2009, 5:40am
Post 10 of 13
I'm pretty sure there have been some significant changes to the program in the year and a half since the last post in this thread. Its probably best to treat it as a separate issue at this point.
Have you tried following these instructions?
Which CompositeLab file did you try to open? Can you explain the comment about the greenscreen tweaks a bit more? I'm pretty sure we can get you sorted in short order.
Posted: Sun, 3rd May 2009, 7:39am
Post 11 of 13
Thanks for the quick reply. The tweaks I'm speaking of are just a whole bunch of masks and garbage mattes I've added to my video to fix areas where the green screen didn't fully cover the subjects. In other words, I've spent hours cleaning up my greenscreen footage to be ready to start putting in light sabres so I don't want to lose all that hard work.
I followed the instructions in the link you gave me (including the Quicktime and DX drivers) and it made no difference. Again, I am able to open the example files without a problem so it seems to just be an issue with my file. I notice the filename has both file extensions on it: "Kids.clab.vlab". I tried dropping the ".clab" out of the file name but this made no difference.
Any other thoughts?
Posted: Sun, 3rd May 2009, 7:45am
Post 12 of 13
Hmm, having both extensions is odd; probably your best bet is to send an email to email@example.com
explaining the situation, and attach the project file so they can have a look at it. However, I think it will be Tuesday before they are back in the office, so it will probably be a few days before you get a reply.
If you need to resolve it sooner than that, you could try starting a new project. If you create a preset for each layer in the timeline, then all of the masks, garbage mattes and key settings can be saved, so you can apply them to the footage in a new project quite quickly, though it may still take a few minutes to import your footage and place it all on the timeline again. the preset system makes that kind of transfer much much easier and quicker though, so that is an option if you need to resolve this right away.
Posted: Sun, 3rd May 2009, 9:12am
Post 13 of 13
Thanks for your help, Axeman. I've shot through an email to support and will see how it goes. FYI, the "create preset" option isn't an option for me as it's unavailable in the trial version.