Timeline and Neon Question [ANSWER]
Posted: Wed, 8th Aug 2007, 8:04pm
Post 1 of 12
hello i was wondering something..
i am an absoloute beginner to Vision lab The timeline seems to go weird. I get my footage and place it onto the timeline but it plays like so much faster and i thought it was just for this program so i rendered it and it stayed fast.. i know how to change the speed but is that the only way because it adds lots of the same keyframe to get it normal.
The Neon light. Do i have to place it into the timeline and move it frame by frame or can i lock it onto an object?
Thanks for your help
Posted: Wed, 8th Aug 2007, 8:13pm
Post 2 of 12
Fxhome products are not meant for final-rendering; they are used solely for effects and all of that fun stuff.
To properly render it, you would need to use an NLE (Non-Linear Editor). Given that you are running Windows, you could use Windows Movie Maker, which is already installed on your machine.
After you render in VisionLab Studio and save your video, open up that video in Windows Movie Maker, and just save that video as your final video.
As for the neon light, if you are referring to lightsabers and the like, yes; you would need to move it frame-by-frame... Fxhome products have not *yet* achieved the capability to lock on to an object.
Posted: Wed, 8th Aug 2007, 8:21pm
Post 3 of 12
oooooh ok! yeah i knew i had to fully render the video in movie maker and such and thanks for getting back to me.
but im still uncertain why the clip is played very fast. would i need to change the speed manually?
Posted: Wed, 8th Aug 2007, 9:59pm
Post 4 of 12
Wait... does it still play fast after you've rendered it? (In WMM)
Posted: Wed, 8th Aug 2007, 11:23pm
Post 5 of 12
yeah before and after ive renedered it but the sound stays normal speed and causes the picture to freeze till the sound stops
Posted: Thu, 9th Aug 2007, 12:59am
Post 6 of 12
It could also be that the file size is too big... if you have a video that's 200MB, and uncompressed, it'll most likely speed up, freeze, and stop.
You should try scaling the file size down, and see if that works... that always solved the problem for me.
Posted: Thu, 9th Aug 2007, 1:20am
Post 7 of 12
ok ill try it now thanks very much
Posted: Thu, 9th Aug 2007, 2:27am
Post 8 of 12
It seems unlikely that this is the problem, but if you were to set up an interlaced project and import progressive footage into it, it would render out at double speed.
kingofbladeslv wrote:As for the neon light, if you are referring to lightsabers and the like, yes; you would need to move it frame-by-frame... Fxhome products have not *yet* achieved the capability to lock on to an object.
In fact, there isn't a program in existance that can motion track a lightsaber blade perfectly. Once they start moving fast, the blur is often so much that the blade itself almost disappears, and is basically rendered un-trackable. Even ILM, to the best of my knowledge, rotoscopes their lightsabers frame by frame.
Posted: Thu, 9th Aug 2007, 5:01am
Post 9 of 12
Axeman wrote:Even ILM, to the best of my knowledge, rotoscopes their lightsabers frame by frame.
Nah, ILM is too "magical" to have to rotoscope frame-by-frame...
Posted: Thu, 9th Aug 2007, 7:49pm
Post 10 of 12
lol ok so i checked and my videos are less than 5 mb and AVI. im still uncertain as to whats wrong also when you make a video at right speed (by editing) is it normal to have 3 or 4 frames the same at each movement?
Posted: Thu, 9th Aug 2007, 9:40pm
Post 11 of 12
For video playing at normal speed, each frame should be unique.
What program are you exporting the video from, before it goes into VisionLab? What specific settings are you using when you export?
In VisionLab, what render settings are you using?
Posted: Fri, 10th Aug 2007, 12:20am
Post 12 of 12
I was sending the video s straight from the camera. but i found out how to fix it! if i put the video onto a local folder and publish it in movie maker it plays normal speed and normal size so yeah...!
Thank you all for all your help
its great to know there are people that can help you so thanks.