Wayne Waag
2
COW Coins
Forum Replies Created
-
Can I safely assume, that whenever you try and do something with audio streams and you are messing about, SVP kind of defaults to Mono audio?
I suspect that this is indeed the case for MXF. Stereo will render as 2 mono channels (left and right). Thus 4 stereo tracks will render as 8 mono tracks. I redid the little test footage. Here is a screenshot of the timeline.
Here is the link to the re-rendered file, showing the 8 mono tracks and not 4 stereo tracks.
https://www.dropbox.com/s/wqnktoytusg1jsp/mxf%20test%20final.mxf?dl=0
Perhaps someone could confirm that this is indeed the way Vegas works and it is the correct way to proceed. You could use FFmpeg to create the 4 stereo tracks, but from what I now see, I wouldn’t recommend it. You might pose your question on the Vegas pro forum. In any case, good luck.
wwaag
-
Sorry, I’m not a Guru or Pro, but I don’t think Vegas will do what you’re asking (hope I’m wrong). It sounds as if you want to render to an MXF container that has 1 video stream and 4 audio streams. If that’s the case, I suspect that you would have to render an MXF file with one of the audio streams and then render the three remaining audio tracks as three separate WAV files. You would then have to remux these into a single MXF file having the 1 video and 4 audio streams. You can use FFmpeg to do this. I tried it and it does work–1 video and 4 audio streams within a MXF container. As an aside, I tried a straight MXF render with your project settings. It produced a single stereo file that combined the 4 audio tracks. Interestingly enough, MediaInfo showed them as two mono audio tracks, although when imported into Vegas, it was a single stereo track. In any case, FFmpeg will work. If interested, I can help you with the necessary Command line.
wwaag
Added: The resulting file may not work for you. It plays OK in VLC, but will NOT open in Vegas. Regardless, here is the link to the test file so you can try it out. https://www.dropbox.com/s/akc4knw4zz8sgf1/output.mxf?dl=0
-
Since DNxHD is in an mov container (I think), you could try FFmpeg. I remux MP4 files with a new audio track all the time. If you’re on a Windows machine, I’d stay away from ProRes that was encoded on a Mac, if at all possible.
wwaag
-
If you want to make your VHS videos look as good as possible, the most important steps really come before deciding whether to upscale or not. First, capture and convert to digital (usually DV). Your VHS deck should have TBC or, if not, your A-D converter should. Second, your captured video should be filtered to reduce noise. There are some excellent Avisynth scripts written by John Meyer on the Vegas Pro Forum that target VHS captures. How well these are accomplished are IMHO more important than deciding whether to upscale. There is a restoration subforum on Videohelp.com that can be of assistance.
Now to your question. Most of my analog collection over the past 30 years is either 8 or Hi8. For my own work using this footage, I almost always upscale to 720P since I usually include stills. I use QTGMC for de-interlacing and another avisynth script for noise filtering and upscalng. Rather than writing the final rendered file onto a shiny disc, I simply stream the video files directly to my Blu-ray player for display on my TV. For me at least, it’s a lot easier than storing and searching for the right disc.
As to the question of how well upscaling works, I suspect that the improvement is on the slight rather than dramatic end of the continuum. Some years ago, I purchased this enhancer https://www.infognition.com/VideoEnhancer/ and found it to have no effect at all on my footage. The latest edition of Photoshop also has a new algorithm for upscaling which can be applied to video. Again, I suspect the effect will not be dramatic.
wwaag
-
I tried once again to replicate your problem. Again, the cursor stays in the trimmer window and does not jump to the timeline. However, the selection remains and if you hit play, it goes back to the start of the selection and does not continue from the end. You have to have to left click on the next frame button and then it will play. Of interest, the keyboard shortcut to move the cursor one frame to the right (Alt-right) does not work for some reason.
Here’s what I do. For basic cuts editing, I simply drag the clip onto the timeline. Begin play (L) and when I get to the first part I want to keep, stop (K). Then Alt-[ which will delete everything to the left of the cursor. (For cuts editing only, I keep Auto-Ripple “on” so everything moves to the left once a cut is made. Otherwise I always leave it “off”.) Then play (L) and when you reach the end of the first part you want to save, stop (K). Then enter S (split). You’ve now defined your first event. Then enter play (L) and continue the process. In other words, two simple keystroke actions (Alt-[ to define the start of an event and S to define the endpoint). Obviously, you can speed things up by either dragging the cursor or hitting L up to 4 times to fast forward. To me at least, this seems a lot simpler than using the trimmer window.
wwaag
-
Me too. It stays in the trimmer window.
wwaag
-
Might very well be, but I prefer to try simple stuff first, then try something else. What’s really perplexing is that it works with V12 OK, but not V13, presumably with the same project files. Having said that, we really don’t know anything about the source material, project or render properties although that probably shouldn’t matter if it works in one version and not the other. Again, if all else fails, there’s always the nuclear option.
wwaag
-
I presume that you’ve already tried turning off your GPU and performed a clean re-install of V13. As I recall, when I went from V12 to V13, I had problems at the outset, finding certain plug-ins like Mercalli and Vegasaur did not work properly. In V13, I believe there was a complete rewrite of Vegas making use of a later version of Microsoft’s DotNet framework, that was included in the Vegas installation file. The solution for me was to remove the older versions and install the newest version which at the time was 4.5.1. There is a diagnostic tool available from MS that will tell you exactly what versions are installed on your system. Supposedly, multiple versions should not be a problem, but in my case it was, although I had to reinstall a very old version 1.1 to support Procoder. If you try this, make sure that you back up your system completely and also create a restore point. As a last resort, you could always do a clean install of the OS and “start from scratch”, although I’d be loathe to do this.
wwaag
-
when you install it, you have to let the PC Phone Home to activate the license, and be locked to the PC
That’s the way it’s always been for ready-built systems or user-built systems using an OEM version of the software. For ready-built systems, they’ve already “phoned home”.
wwaag
-
Like Steve, I’ve never had a problem like you describe with V13 or V12 or any other version. I don’t do production work, but I do a lot of rendering and I’m sure the machine doesn’t know whether I’m a hobbyist or professional. For me, the opposite has been true–V13 has been so much more stable than V12. The conventional wisdom is to disable your GPU in Video Preferences (although I’ve never had a problem) and to render using CPU only. If you are still having problems, then you’ve got some other system problem and/or problems with your source material/project/render settings although that seems a bit unlikely.
wwaag
