[Wayne Waag]

Glad you found a solution. Bear in mind that the procedure of taking an MP4, re-rendering it in Handbrake, bringing into Vegas for editing and then re-rendering again to an MP4 will result in a generational loss of quality. However, if you’re happy, then it really doesn’t matter. However, if you want to maintain the best quality in the future, capture using as close to lossless as possible, bring into Vegas for editing and then do a final render. Again, glad your problem is solved.

wwaag

[Wayne Waag]

Since I don’t know how long your files are or anything about your PC, I have no idea. The ts file you uploaded was 2:06 long and took 1:59 to encode to XAVC-S on my system–a little bit faster than real-time.

wwaag

[Wayne Waag]

I use screen recording software quite often including 1080 60P captures and have never had a problem with Vegas. The software is Action by Mirilli. Rather than saving as an mp4, I save it as an avi file which includes wav audio. The bit rate is pretty high–about 270 Mbps and does produce large files, but as I’ve said before–never a problem with Vegas. It does have the option for saving as an MP4 including Intel Quick-sync as the encoder, although I have never tried it. In the future you might want to try it or at least find something that is “vegas-friendly” and not use something that comes as a freebie with one’s video card and leads to problems down the road when trying to edit.

wwaag

[Wayne Waag]

My suggestion is for you to record a short session using the same settings and then upload that file to Dropbox or something so others might have a look at it. It seems that screen recording software is notorious for presenting problems in Vegas. Just because it plays OK in WMP doesn’t mean it’s not corrupted in terms of what Vegas requires. The problem seems to be that some software uses variable framerate recording. My suspicion is that you will have to transcode your files using a 3rd party application into a Vegas friendly format. But again, first upload a short sample file.

wwaag

[Wayne Waag]

[Gary Burns}

The idea behind proxy editing is pretty simple. Take your 4000 x 3000 media. Each frame has 12 million pixels. I suspect that even the most high power systems would choke on attempting to preview such media. Suppose that at the beginning of my project, I render the original media down to a 640 x 480 MPEG file. Now each frame has 307K pixels, a reduction of 39 fold. Now, even the most modest system can easily preview such media. If you’re using a single display, this permits you to still have a reasonable size preview window. So at this point, you do your editing using these down-sized files. Once you’re happy and want to render, you simply replace the proxy files you’ve been using for editing with the original files.

Vegas 13 already has a proxy capability built in. In your project window, if you select a media file and right-click, there is an option to build a proxy. Once the file is built, if you use draft or preview quality, then Vegas uses the proxy file for preview. If Best or Full, it uses the original file. Once its time to render, it automatically uses the original file. While this is really pretty easy to use, I found that in my laptop example, the resulting files were still too large to be previewed well. For that reason, I created my own render template and manually created my own proxy files, which is what I would probably recommend that you do. If you have Vegasaur, there is a proxy builder function included that lets you specify what render template you want to use for your proxies. This can be very useful if you have lots of media files. However, if you have only a few, just doing it manually will work just as well. Hope this gives you a little better understanding of using proxies.

Regarding hardware, my only suggestion would be to an add additional hard drive to your system that is dedicated for your video work. Two would be even better to avoid having to read and then render to the same hard drive. SSD’s are great as a system drive, but are still too expensive (IMHO) for use as a project drive involving large media files. JR is the guy to give video card suggestions.

wwaag

[Wayne Waag]

JR is right. You really do have a low spec system that doesn’t appear worth attempting to upgrade. Having said that, you can still do some pretty decent editing using proxies. It might be worth trying to do some test renders of proxies at differing resolutions to find a spot that your existing system might handle. 4000 x 3000 might seem daunting, but it’s still a very basic 4:3 aspect ratio and there are lots of rendering possibilities. The first couple of months this year, I was forced to use an 8yr old Core 2 duo laptop on a 3 camera 1080 HD project. Preview using original footage was around 2 fps. However, using proxies, it was possible to bring that number to the upper 20’s–good enough for completing the project. If rendering time isn’t much of a concern, then you might give some thought to this approach. Just an idea. Good luck.

wwaag

[Wayne Waag]

Why do you need a script? Just select events (which you would need to do for a script anyway), then Ctrl-X (cut), Ctrl-end (takes you to end of project), and Ctrl-V (paste). Takes a few seconds at most.

wwaag

[Wayne Waag]

Since you have Vegasaur installed, you can do a batch replace. There is also a standalone Batch Replace script available.

wwaag

[Wayne Waag]

Finally, a solution that I think will work. You will need to download TMPGEnc’s Mastering Works 6. There is a 30 day free trial. Or perhaps, you already version 5. In any case, you can convert to XAVC-S which also converts the audio to PCM. After conversion, it imports just fine into Vegas with the proper frame rate.

Those ts files are really screwy. For one, it seems as if they use mp3 audio. If you import the original file into Vegas, it shows a frame rate of 119 fps and also a duration of 2:04. If you simply demux, the file the audio length is 2:06, although the video is 2:04. The converted file using TMPGEnc shows a frame rate of 59.94 fps and a duration of 2:06. It seems as if the video is using some type of variable frame rate. Regardless, this seems to be a solution that will work.

Patrick. Two things. In the future. First, don’t use the Haupaugge PVR if you do your editing in Vegas. Or if you do, convert the files using TMPGEnc or something else before importing. And second, always provide as much detailed info as you can including sample media. Once you finally uploaded the file, it was a relatively short time before a solution was found. It seems that we all wasted a lot of time. But hopefully, your problem is on the way to being solved. Good luck.

wwaag

[Wayne Waag]

Good. Downloaded your ts file and I think that is your problem. According to Mediainfo and what you say, it is NTSC 59.94 fps. However, when imported into Vegas, it shows as 119.88 fps or double the frame rate. Can you confirm this? Hopefully, Graham will also download and have a look, since he is really the expert in these matters. If indeed Vegas thinks its 120 fps, this may explain why the long transcoding. Perhaps we can find another way of transcoding–Vegas is definitely not the way to do it. Just tried TSMuxer which simply remuxes and not transcodes (very fast). The video is now correct, but Vegas doesn’t like the audio. Regardless, it seems there is little doubt that your ts files are the problem. I’ll try some other software that I have.

wwaag