Rob Mack
Forum Replies Created
-
In general with any video file, if Vegas can play it’s audio but not it’s video then you’re missing a codec needed for Vegas to play it. If some other player can play the file then it’s using a CODEC that Vegas can’t use (or access).
Rob Mack
-
The trimmer either saves the markers within the media file or in a sidecar .SFL file. You need to preserve those SFL files when you move or back up your media.
Yes, if you save markers and regions for a clip in the trimmer then they’ll come along to the next project.
Rob
-
I don’t know if we’re seeing the same thing but it’s similar. If you float and doc the trimmer a few times you might see it being redrawn inconsistently. Sometimes the tracks are small, sometimes the monitor portion of the window is small or completely collapsed. For me, it’s always there, just sometimes collapsed down to a height of zero.
Part of it is that the docked window and the floated window are different sizes, so the adjustable parts of the window need to be resized, and I think their method of deciding on the sizes is buggy.
Rob
-
The button allows you to manually save the regions and markers. There’s a preference setting that turns off the automatic saving of trimmer marks. If you turn that function off then you’d need to use the button.
Rob Mack
-
It couldn’t be this easy, but…
I just tried dragging the trimmer out to float freely and sure enough all I could see was the audio track. Then I rolled my mouse up above the edge of the audio track and the cursor changed to indicate a draggable border. I pulled that border down to reveal the video portion of the tracks. So it seems like Vegas just set the video track height to Zero when I floated the window.
Rob Mack
-
I’ve seen this happen on laptops that have been running with a second monitor. The laptop gets moved somewhere, a new monitor is attached but configured to be on the left rather than the right, and all your dialogs are appearing in the right-hand area where the second screen used to be. Or something like that. Is that ringing a bell?
Rob Mack
-
I’ve spent the last 10 years peering pretty closely at frames of DV. It’s awful stuff. Your reds look about like what I’d expect in a DV codec.
The problem isn’t Vegas, it’s DV. Yes DVCPro would be an improvement since it’s a double-DV codec and has 4:2:2 sampling…but it’s a proprietary Panasonic codec and Vegas can’t control the deck, nor can it write the files without buying a Raylight Encoder codec.
You probably need to start delivering files on hard disk. Sinking money into a tape deck is probably not a great proposition at this stage of the game.
And you also need to bone up on color for video.
Rob Mack
-
This post is pretty far in the past but we just ran across something similar and I was searching around for others with similar problems.
We have a mix of CS2 and CS4 suites. Photoshop CS4 defines a D1 PAR as 0.91. Photoshop CS2 defines a D1 PAR as 0.9.
PPro CS2 assumes a PAR of 0.9. PPro CS4 assumes a PAR of 0.91. I don’t think any of these uses 0.9091 (Vegas does, though).
PPro takes these numbers very literally. If you create an image in Photoshop CS4 that is D1/0.91, PPro CS2 will treat it as “not quite right” and you can have poor image quality when you are fitting an image to your frame size.
The image itself is still 720×486 but you have to make the PARs match in all three applications.
Rob Mack
-
One thing to keep in mind is that if your 1.96 GB of files on disc are compressed images they need to be uncompressed to RAM as Vegas works with them. In other words they’re probably bigger than you think, byte-wise.
Reducing their physical dimensions to what you need ought to be a help. Reducing your preview RAM setting to a low number would also free up some memory.
Still, you’d hope that VP9 could do better at this with it’s supposed support for larger images.
Rob Mack
-
You would probably need a special codec. Normally, media from the XDCAM EX cameras shouldn’t be a problem for Vegas but FCP needs to convert them to a quicktime format to use them. Sometimes once FCP has had its hands on media they’re hard to use elsewhere.
The cameras should have included a disk with XDCAM Explorer software on it for both Mac and PC. This might help. Maybe. That disk also would have included a file converter for FCP.
Sometimes a qucktime file will play fine in their player but not in Vegas. One option might be to export it from the QT player in a usable format.
If they happened to save the camera-original media Vegas might have an easier time of it. In fact, Vegas Pro 9 is supposed to be able to use the camera-original files on the timeline. VP8 has to use MXF files.
I don’t have direct experience with this. Hopefully someone will come along with clearer information.
Rob Mack