Comments

Skywatcher wrote on 7/29/2015, 10:59 PM
MikeLV,

Yes, that is the message.

We pretty much exhausted this thread on this script. The GREATEST minds in this forum could not resolve our issues. I still use hand brake, but as a stand alone.

Skywatcher
Downunder wrote on 7/30/2015, 5:19 AM
Well I (just recently) did another - start all over again - fresh Win7 OS install, then installed all the latest windows 7 updates, then installed Vegas P13 build 373 as V2H worked perfectly with that build then I installed all the V2H software components with an older Handbrake v 9.6 and Prismo File Mount V172 (again both originally worked perfectly) I installed nothing else including the graphics card drivers. Then I rebooted, fired up Vegas P13 373...and then fired up V2H..... OMG .. it worked...... What the key element to get it working again I have no idea. So I then installed the graphics card drivers then Vegas Build 453 and to my relieve V2H still worked... EXCEPT........ on longer video renders over an hour the audio slowly goes out of syn... ... again tried different configurations but still the same issue. Therefore at this stage V2H is not an option to me. ANY HELP WITH THIS (out of sync) ISSUE WOULD BE MOST APPRECIATED. Next step for me is to uninstall HB 9.6 and try 9.9 to see if that stops the audio going out of sync.

Let the fun begin again..
MikeLV wrote on 7/30/2015, 8:59 AM
I guess the best solution is to just go back to V12, as I remember it worked in that version.
wwaag wrote on 7/30/2015, 9:59 AM
ANY HELP WITH THIS (out of sync) ISSUE WOULD BE MOST APPRECIATED.

I would first try rendering your audio directly from Vegas and then simply remuxing it with your Handbrake file to see if that makes a difference. Because of the Frameserver audio problem of downsampling from 48Khz to 44.1Khz and then Handbrake upsampling back to 48Khz, I always do this. If you still get the out-of-sync problem, then try a direct render from Vegas to see if the problem persists.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 7/30/2015, 12:15 PM
Rather than going back to V12, I also put B373 in, but now I discovered something else that I don't remember happening. I tried to add the one second to the loop region after the end of the timeline, however, I can't drag the right side of the loop region past the end. Is there an option I need to enable or disable somewhere? It wasn't snapping, or quantize to frames. Anyone else run into this?
john_dennis wrote on 7/30/2015, 1:02 PM
I have run into this recently. When I drop the first media on the timeline you can't extend past the end of the last media.

Don't have time to analyze, but here's a workaround.

Strike Control + End

Insert Generated Media Solid Color at the end of one of the video tracks.

Delete the Generated Media.

You should be able to move past the end of the last media, now.
MikeLV wrote on 7/30/2015, 1:22 PM
John, thanks, I played around with it. Discovered that if you remove the generated media, and move the loop region before the end, and then try to go past the end again, it stops.. So weird..

So I put build 373 in, and the file mount error is gone, I see the frameserving file: C:\frameserver\source\vegas.avi so I presume the frameserving is working properly.

However, Handbrake doesn't open up. I'm using the latest version of HB, should I go back to a previous version, if so which one?
john_dennis wrote on 7/30/2015, 1:38 PM
I've been using Handbrake 0.9.9.5330 on two machines.

I created a new topic for others to comment on the timeline limitation. The subject deserves its own thread.
MikeLV wrote on 7/30/2015, 2:29 PM
john_dennis, what version/build of Vegas are you using with HB 0.9.9.5330?

The loop region timeline issue I suppose wouldn't really be an issue for those who don't use the script. I can't imagine an instance where I would render a region longer than the end of the video except for the vegas2handbrake script.
Downunder wrote on 7/31/2015, 5:48 PM
wwaag, thank you for you advice. So that I get it right (not done Remuxing). Do I render out (and save) a separate audio file straight from Vegas, then do the V2H render with both the video and audio. Once HB opens up do I then replace the audio with the (straight from) Vegas audio render file. Then I get HB to render the whole thing with the replaced audio. Is this correct?

Lee
MikeLV wrote on 8/4/2015, 11:54 AM
Think I'm just going to go back to Vegas 12 to use the script again. I find it easier using the script to frameserve, as opposed to creating the giant DNxHD intermediate file. Haven't been able to get the script to work with V13 at all unfortunately.
MikeLV wrote on 8/11/2015, 6:03 PM
Unbelievable, I went back to V12 and the script isn't working; doing the same thing as reported in this thread.

C:\Program Files\Sony\Vegas Pro 12.0>for /F %i in ("C:\frameserver\vegas.avs\vegas.avi") do if %~zi GTR 160000 goto hbstart

C:\Program Files\Sony\Vegas Pro 12.0>if GTR 160000 goto hbstart

C:\Program Files\Sony\Vegas Pro 12.0>ping 1.2.3.4 -n 1 -w 2000 1>nul

over and over again, let even more troubleshooting begin.....
Or_Toltec_Tal wrote on 8/4/2016, 4:18 PM
I followed this super clear Tutorial and all is set and done in 5 Min !!!!!!

http://www.vegasvideo.de/vegas-2-handbrake-en

I no longer needs to render Uncompressed AVI. THANKS GOD !!!!!! saves so much time & space. Works 100% in Windows 10 64bit and Vegas Pro 13.

:)