John Rofrano
3
COW Coins
Forum Replies Created
-
Wow, I’m glad it’s working. You could try a batch converter like Super(c) to convert all of the WMV’s to DV. WMV is really an output format and it’s very good for editing. It works, but DV AVI is much more efficient for editing.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Yes, I believe you understood the “intent” of my directions. For DV AVI use the AVI type with the NTSC DV or PAL DV (or their widescreen counterparts) templates depending on the attributes of your project.
It is odd that these clips work in other projects. Perhaps it’s not the clips themselves. It could be a corrupt project file. You could try opening a new project simultaneously and cutting and pasting the events between them.
I’m just trying to thing of things to try to get you around this.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
With that processor I assume this is a laptop. That’s not a lot of computing power for a heavily compositied project. Perhaps the CPU is overheating? This could cause memory READ errors.
> What do you mean/How would I render some of the source files to a different format and replace them in the media pool?
What I mean is start a new project and take the video that is the source of the first event and drop it on the timeline and render it to a DV AVI file. Then load the original project back up and go to the Project Media tab and find the video for the first event and right-click and select Replace… and point to the DV AVI file that you just rendered. This will replace the file everywhere that it is used in the project. Then try and render the project and see if it gets past the first event. If it does (and it didn’t before) take more of the WMV source files and render them one at a time to DV AVI files. Then replace them one at a time in the Project Media. If this allows the render to continue then you know it’s something about the WMV files that is causing the problem. Since you couldn’t render even a minute it shouldn’t take too long to tel if this approach is working.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
So… what FX are on the clip? Because that’s where your problem lies.
Make a timeline selection of a section that flickers (I only saw a brief green screen section at the end of the second clip that flickered) and do a RAM Preview (Shift+B). If the RAM preview flickers it has nothing to do with the render. The problem is the FX on the clip.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
If you step through the rendered video frame by frame you will see that the flicker is caused by your subject disappearing from the frame. In other words, the person and the console they are standing in front of is obviously on one track while the gray wall that says “Rewind” with the video screen in the upper left is on another. The track with the person is what’s flickering on and off. I assume that whatever you used to key them is causing the problem. I would start there.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
These problems are usually very hard to find. How much memory do you have? What format are you rendering to? Have you tried rendering to a different format? Also what format are the clips on the timeline? I can see both Quicktime and Windows Media in the dump you posted. Make sure you have the latest versions of Quicktime and Windows Media Player if that’s what you are using. You can also try rendering some of your source files to a different format that doesn’t cause the error and replace them in the media pool. There is something about the combination of source types and render type that is causing the problem and you just have to figure out what that combination is and avoid it.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
-
You could make the mask on the lower track where you can see the glass sections of the window and then cut and paste those keyframes into the flame track. You could also render to new track and make the keyframes there and then cut and paste back to the flame track.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
The texture that you see are static textures that can be used in Vegas. The real power is when you add Boris as an FX or Transition. The “timeline” error that you received is because Boris wants to take a snapshot of the event that it’s being applied to so that it can be used as a reference within the Boris FX interface. Simply make sure that your timeline cursor in Vegas is placed over the event that you added Boris FX to and then open the Vegas plug-in properties window and click the Boris logo to launch the Boris application.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Stop using Track Motion. Use Pan/Crop instead.
Track Motion will take your image and scale it down to the output resolution BEFORE it starts to zoom so you will always get inferior results. Pan/Crop maintains the full resolution so you can zoom way in and still have pristine images.
~jr
http://www.johnrofrano.com
http://www.vasst.com