Arthur Bueno
Forum Replies Created
-
The sounds are under the Creative Commons license. I’m a big fan of the concept.
You can find information about that at https://creativecommons.org/.
Basically it wants to stimulate exchange of material, get people to share their creative work. If you share work you can choose conditions for the license (like: allow modifications, or allow commercial uses). see the faq at creativecommons.org. -
interesting advise. Basically it means you edit a proxy (but why mpeg 1, why not a dv proxy, like gearshift does?). Of course: editing a proxy gets rid of your playback limitations, but that’s not what I want, I’d want to see the HD material in as high a framerate as possible.
-
All this confirms that it is just me, everyone else is happy.
My troubleshooting pretty much narrows the problem down to the Vegas 7 program itself (since the exact same project plays on the exact same computer much better on Vegas6 than on Vegas7 with the exact same program settings).
They must have put something in Vegas 7 that my computer doesn’t like. Or maybe it has some kind of incompatibility with other software I’m running.
Since nobody shares the troubles, I’ll just stick to V6 and wait with V7 till the next computer upgrade. -
m2t is a transportstream for an mpeg2 file.
My V7 plays back m2t in a HDV project very very bad as well (about 3 fps with around 99% cpu use).
So what puzzles me is that I hear everywhere that Vegas 7 handles mpeg2 so well, while on my system performance is lousy, and worse than Vegas 6.My Vegas 7 often doesn’t even play a normal DV file without any fx at full framerate in a standard DV project (yes, when all the settings are correct and opacity is 100% etc.etc.)
I posted on this before, but seem to be the only one for whom Vegas 7 works that bad (of course I’m happy that not everybody is having this problem). -
Done some more troubleshooting: I totally uninstalled the drivers for the Nvidia 6800GT (removing all traces of previous installations), and reinstalled again. unfortunatly: no improvement in playback performance.
I then uninstalled the NVidia drivers again, and replaced the card with an old Radeon 9550, with newest drivers. After this playback to computer monitor remained about just as bad, with just as high cpu use.
This seems to rule out the videocard(drivers) as cause for bad playback. (I’ll probably go back to the NVidia card, since it can do GPU rendering for magic bullet plugins, which works ok).Also tested HDV playback on both cards (m2t file in matching HDV project in V7). They give me around 5fps on to secondary monitor on preview full. Onpreview auto it never goes above something like 18 fps. I’m still wondering what performance other people get from HDV playback with systems like mine, and how they make it workable.
-
Just come from a thread of bad preview frame rates where rob tried to help out as well. Rob: does this mean you have not experienced this behaviour of V7? I know this phenomena it all too well, many restarts of the program nescessary, as I like to work on many programs at the same time; coming back, Vegas is fast asleep.
Can’t remember the slowdown happening in V6. V6 seems to be more reliable/straightforward. This difference in behaviour suggests a change in V7 that compromises performance, so I don’t think the problem lies in page-file settings.
However much I like the snapping feature of V7 (almost the only reason for me to buy it) I tend to go back to V6 most of the time for performance reasons. -
It sounds like you need 3 tracks.
the bottom one is just the bridge. If it isn’t shot from a tripod, make this a still (jpg or png).
Above that there’s your monster
Above that you copy the bridge event again. In this upper one you meticulously mask out the parts of the bridge you want visible. (use mousewheel to zoom in to make the mask points exact. If the bridge is indeed a still, you could do this a lot faster in an image editor like the Gimp (free program that has a very nice option to intelligently find the borders of a mask, called: select shapes from image).that’s the sandwich you need.
Your question about audio isn’t very clear. I think what you imply is you want to use audio fx on an event level, just like the mask you just made. In Vegas audio that is less intuitive than putting fx on track level: give the audio it’s own track, and press the green button in the track header. There you can keyframe and do whatever you want, dependent on the effect you’ve chosen.
-
I feel your pain.
..
try this:put a mediagenerator text in one track. Create event motion to do the zoom-out. Make sure that in Keyframe interpolation the smoothness is set to 0.
Then in the same menu, mask out one of the characters in the event motion menu (draw a line around it and choose Mask/Path/negative).make a new track above that, copy the text event you just created to the new track (choose: create a copy of the source media). Change the mask in event motion to Mask/path/positive. You now have the whole text zooming out. The large part is in the underlying track, and the odd character in the upper track.
Go to the event in the upper track, select the first motion keyframe and make this character bigger.
Works great. Don’t forget to give both events some gaussian blur (mainly horizontal and keyframed so that the text becomes readable after about 10 frames.
It’s easy to do in vegas, looks the same as in the clip.
Don’t forget to overcharge. -
sorry, I made a mistake. When outputing through firewire with “recompress edited frames” set to “on” I do indeed NOT get the “frame recompressed” message in the preview window, and the cpu usage is around a acceptable 20%.
So I get that message (and the high cpu use) only when outputting to a computer monitor or preview window. -
Rob, what you tell me about recompression really surprises me. For as long as I know Vegas (since version 3), or for as far as I remember (even on another computer), it allways gave the message “frame recompressed” when I outputted either through firewire or to a secondary monitor.
I might remember it wrong (no I don’t), but it definitely shows the message now (that is: as soon as I set “Options/Preferences/PreviewDevice/Recompress edited frames” to “on”).
I never understood why it was so, since if you play a simple dv file in a simple dv project nothing seems to need recompression.To sum up some possibile culprits for the high cpu use:
– as Rick Mac suggested it might have something to do with the video driver since cpu use only occurs when playing to a computer monitor. I have a Nvidia 6800GT, updated the driver regularly and last time less than a month ago. Don’t see how I can do better.– One other possible difference in my workflow: I allways capture with scenalyzer live (I love that program and wouldn’t want to miss it). Just tested playback with a clip captured by the Vegas Capture program, but playback gives the same high CPU use.
– I have a standalone mainconcept dv codec installed to render from VirtualDub (but in Vegas I setting the tag “ignore third party codecs” to on or off makes no difference in playback performance). For testing I just uninstalled the standalone MC-codec, no difference, still around 97 % cpu.
– The project format could be different from the media format, but I checked so many times all the settings of both media and project that I started to have dreams about them (PAL, 25 fps, 720 x 576, lower first, ratio 1.0926), they’re identical.
What I’d really like to know from other users: Am I the only one who