Rob Mack
Forum Replies Created
-
Okay, you can’t just type in the edit details window but you can paste from the clipboard. in your case that might be better!
I just took a tab delimited file, copied contents to the cliboard, set edit details window to “Markers”, clicked the top-left grid button to select all rows, and pasted.
It’s not perfect. You can’t paste into individual cells, but you can do whole rows, and once a value is present then you can edit it. But this will place markers on the timeline, or regions if that’s the sort of data you have.
Oh, and for regions, you don’t need start, end, and length. Any two will do and Vegas will calculate the rest. Not too bad!
Rob Mack
-
I don’t have Vegas on this machine so I can’t check, but can you type them in in the edit details window?
Rob Mack
-
Normally we record mic and boom on channels 1-2. I’ve never seen anyone use a stereo mic professionally, but then I’m usually lighting and stay out of the sound person’s business (Don’t want to be sucked in, too many hats for one head.)
As leslie points out, if you record 4-channel audio on DV25 you take a sample rate hit on all channels.
Most modern NLEs that target the consumer DV25 market don’t really give you many professional audio options. You can’t choose which channels to take when you capture, instead you’re forced to take 1&2 as a stereo track. This is true in PPro even if you capture over SDI. The Vegas capture tool for SDI interfaces doesn’t seem to give you any audio options either.
I have to assume that the design is strictly DV25-centric, where channels 1&2 are embedded in the DV stream as a stereo track. If you capture DV, you have to take the audio too.
The solution is to use a thrid party capture tool like Scenalyzer.
Rob Mack
-
Looking around at descriptions of overwrite mode, The idea appears to be that it replaces the footage you’ve dropped it over and there is no ripple of the events on the timeline.
So here’s what Vegas doesn’t do. Suppose you drop some footage over two clips, so that it would have to overwrite the end of clip A and the beginning of clip B. Vegas can’t do that. It can be added as a take to one of the events, and it can seem to overwrite an area in a single clip, but it isn’t really overwriting. If you right-click the track header and enable “Expand track layers” you’ll see that what you’re really getting is an A/B track effect.
The closest thing to overwrite is to drag the new material into a track above the one you wanted to drop it into. This has the same visual effect but is a sloppy way to work when you’re hell-bent on pretending you have an overwrite mode.
With Vegas, I guess you have to cut out the hole and then drop the footage into it. That’s as close as you get to overwrite mode. Maybe the lack of overwrite mode comes from a lack of emphasis on the trimmer, since most overwrites would start there.
Rob Mack
-
Oh, and Dcus’s notebook is probably just fine for Vegas. He just wont be able to use the media manager.
Rob
-
Most of the “buzz” has been noise. People saying “no way will I ever use Vista and you’re a fool if you do you so-and-so”
What I’ve read on the Sony forum is that the few people who tried it found their render times were comaprable. Most of the drm issues have been hypothetical or on principle. Commercial HD titles generally don’t have the worrisome tags set on them-not yet anyway and presumably not for a couiple of years. Generally, users who can find their backsides without help have been okay with Vista.
Vista is not 64-bit unless you buy a 64-bit version (or, I gather if you buy it in a box you can install the 64bit version) this means you’re still limited to 2GB per program unless you install 64bit.
Graphics drivers are still in their infancy for Vista.
Personally, I’d wait. Last I checked you could still buy business laptops with WinXP, which is the safer course for now. One thing I think we’ll see is hardware manufacturers missapplying some of the hardware restrictions of HDCP – making hardware refuse to play full rez when they didn’t have to. So I’d wait quite a while.
Rob Mack
-
Arthur,
I also see frame recompressed when outputting to seconadry monitor, but not when playing a straight DV clip out via firewire. The firewire behavior is as it should be. I don’t know about the recompression when playing to the secondary screen, I don’t see the reason for it, assuming its just a frame buffer. Still, for me, Vegas itself is running at 9% CPU. There’s another 6 or 7% on top of that that seems to be the OS.
I’m wondering if the driver for your card is somehow also using the CPU? perhaps there are settings in it’s video overlay control panel, or color correction, or something…
Rob Mack
-
Well, what I’m assuming is that when you go off to other programs, windows stashes Vegas off to the swap file onthe hard drive. In my day to day I run with a lot of piggish software open so I see this sort of behavior a lot, but mostly in Dreamweaver.
I was seeing trouble with Nested veg files in V7 in that I’d go off to work in the subproject, come back to the main project, and have really bad performance for a while.
Sometimes software trains you not to do certain things. It shouldn’t but it does. Looks like V7 is training you to use V6, but if you could pin down what it’s doing you might be able to avoid the problem in V7.
Rob Mack
-
Looks like great hardware…
There’s lots of rabid complaining about Vista but several people over at the Vegas forum have tried it with Vista and are happy. Some have claimed that they actually get faster renders. (crazytalk, all of it! 😉 )
Here are the gotchas:
The media manager doesn’t work, but there are some workarounds, I think. The components just aren’t available in vista.
I have an HP destop system with a Vista build on it. I attached a USB drive to it and formated it, and found that there were no usable permissions set on the new drive. So you have to set permissions on some folders before Vegas can save media and project files. Not hard at all.
Rob Mack
-
What’s your preview RAM set to? If it’s really high windows may spend more time swapping to the page file than it spends rendering.
Another possibility might be the types of media on the timeline. Things that rely on quicktime (esp. Tiff files) can really slow things down.
Rob Mack