Forum Replies Created

Page 4 of 83
  • Bob Peterson

    August 30, 2015 at 2:46 am in reply to: Recording VIA HDMI for Vegas 12

    I checked before I posted my response. He did not mention HD at all. I interpreted that to mean that SD is sufficient. Your interpretation is different than mine. Enough said.

    I have never seen any quality problems with this approach, and we use the little box I mentioned to interface our Tivo box to our TV. Again, I have seen zero problems with the image. I stand by my response as the one which addresses his question of a good, low cost and low cpu overhead way to capture HDMI in a video file. Certainly, DV quality has been quite good for a lot of years. It is what Vegas assumed a few years ago, and what Vegas still supports. Not everyone needs a state of the art solution.

  • Bob Peterson

    August 29, 2015 at 9:05 pm in reply to: Require assistance PLEASE SONY VEGAS PRO 13

    A first guess is that you have a region, or selection, established on the time line. If you do, Vegas will default to “render loop region only” which is a check box on the render screen. Uncheck that box, and it should render whatever is on your timeline.

  • Bob Peterson

    August 29, 2015 at 8:45 pm in reply to: Recording VIA HDMI for Vegas 12

    To capture from HDMI, what I would do is get an ETEKCITY Mini HDMI2AV for $25 at Amazon. It is a little box which converts HDMI to composite video including both video and stereo audio. Feed that into an old DV camera which has a passthrough capability. The camera will convert the analog composite video to a DV digital format, and push it out through its firewire port. Connect the camera to your computer via firewire, and Vegas will capture the data and store it on disk. Once it is captured, you can begin editing.

    If you don’t have a suitable camera, I’m sure you can get one on ebay. The camera does not have to shoot video or write it to tape. All it needs to do is the passthrough operation. I have a Sony DCR-TRV17 that I use in this way.

  • Bob Peterson

    August 29, 2015 at 4:01 pm in reply to: Editing on Surface Pro 3

    If you do it, I’m sure many people here would like to hear how it works. You would be a true pioneer.

  • I hope so as well.

  • Bob Peterson

    August 29, 2015 at 3:55 pm in reply to: rolling lines on footage

    I agree the plug-in is a good way to go as long as the only thing in the video image is the PP. Otherwise, the only obvious solution is to display the screen capture over the video. I don’t think a mask is needed. You can simply superimpose screen captures from the PP.

  • Good tip. I seem to learn something every day.

  • Bob Peterson

    August 29, 2015 at 3:39 am in reply to: OT: Stopping Windows from installing updates

    I’m sure you know this to John, but I think the point is worth making. Malware can invade a PC if it can exploit a vulnerability in a program which is running on a PC. It is not always dependent on tricking the user into downloading and running it. It can lurk on an otherwise legitimate, but infected site, exploit the vulnerability, and install itself. Things like Flash or Java are a bit notorious for such weaknesses. Windows itself has this type of vulnerability within its many programs which is why security updates need to be applied to protect against attack.

  • Bob Peterson

    August 29, 2015 at 3:25 am in reply to: Getting Vegas to see iZotope mastering tools

    Yes, Sound Forge can be called from Vegas, but is not a plug in. What happens is Vegas passes the audio file to Sound Forge, Sound Forge operates on it, and saves it before exiting and leaving you back in Vegas. Sound Forge can also create a new file which is called a “Take” in Vegas. Since your Izotope functions are accessible in Sound Forge, I think your problem is solved. They do not have to be accessible in Vegas since you can get to Sound Forge from within Vegas. I don’t think it is a 32 bit vs 64 bit issue. Both Sound Forge and Izotope are destructive editors. That means they actually change the source file. In contrast, Vegas is a non-destructive editor because it never changes a source file. It maintains meta data which describe the changes which must be made to source files when processing them. Those two ideas are quite incompatible.

  • Bob Peterson

    August 28, 2015 at 2:32 pm in reply to: Getting Vegas to see iZotope mastering tools

    In my work, it is not necessary for Vegas to see or invoke Izotope. Within Vegas, and after I have the editing of my time line complete, I render the audio to a wav file which is a lossless way to place it in an external file. Then, I read the wav file into Izotope, perform all the operations I want to do in Izotope, and write it back out again. The edited file is then imported back into Vegas, and replaces the original audio in the project. By replace, I mean that it is dropped into a new track, and the old audio tracks are either deleted or nulled out. It is easy to position the audio in the new track because I know exactly where the render started.

    After these steps are complete, I can go back to Izotope as often as I like, make changes, save the file, and the updated audio is back in Vegas where Vegas reanalyzes the updated file.

    BTW, you say you have a Mastering and Repair Suite. That does not sound like a plug-in for Vegas, so, even if Vegas could call it, it would still not be working within Vegas like an Fx would.

Page 4 of 83

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy