Kommentare

OldSmoke schrieb am 04.10.2014 um 23:47 Uhr
Works great on my system.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Tom Pauncz schrieb am 05.10.2014 um 16:08 Uhr
+1 here...
Rv6tc schrieb am 05.10.2014 um 16:51 Uhr
Mine won't open Handbrake.

:-(
Grazie schrieb am 05.10.2014 um 16:52 Uhr
Like a charm. No more spending time doing interim renders to HB.

"MARCO FOR KING OF THE UNIVERSE!"

Grazie

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

Marco. schrieb am 05.10.2014 um 19:01 Uhr
On some systems with the given batch file "start_vegas2handbrake.bat" there is a problem caused by the ping commands. VidMus offered a modified version of that batch file which gets rid of the ping commands.

So in case the given batch file causes a problem, you should try replacing it with VidMus' version. I still haven't had the time to update the webpage but you can download VidMus corrected version of the batch file -> here (download, unzip and replace).
Marc S schrieb am 05.10.2014 um 19:04 Uhr
This script process Marco came up with is amazing! Really brings Vegas into new territory and it's 100% reliable on my system.
Erni schrieb am 06.10.2014 um 01:41 Uhr
+1 here!

Amazing and very generous work!!!

Erni
riredale schrieb am 06.10.2014 um 04:55 Uhr
Still back here with V9. So the scripting language changed somewhere around 10-11? Oh, well.
MikeyDH schrieb am 06.10.2014 um 23:30 Uhr
Can anyone decipher where I went wrong?

Microsoft.JScript.Vsa.JSVsaException: UnknownError (0x801330FF): System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
Marco. schrieb am 07.10.2014 um 09:36 Uhr
Which Vegas version do you use?
MikeyDH schrieb am 08.10.2014 um 03:27 Uhr
Sorry I didn't mention that, Marco. I'm using Vegas Pro 13. Thanks.
Marco. schrieb am 08.10.2014 um 11:12 Uhr
To me this then sounds like a .Net Framework issue. Do other Vegas Pro scripts work fine? Maybe reinstalling .Net Framework helps (but this is just a guess).
SecondWind-SK schrieb am 08.10.2014 um 17:35 Uhr
Having trouble with this install. I have Handbrake installed. I downloaded and installed Debugmode. It doesn't show up in the Render As dialogue as indicated in the install instructions. I get a install box during the install process with several boxes that can be checked including: choosing Vegas Pro 32 or 64 bit, install Vegas plug-in, etc. I checked Vegas 64-bit and install the Vegas plug-in. Then launched Vegas and tried to render a project (to set the Debugmode parameters) but no Debugmode choice shows up in the render choices. Uninstalled and reinstalled a couple of times. Still no joy. What am I doing wrong?

i7 5930K
C-drive 256 MB SSD
16 MB RAM
Sapphire R9 280x graphics card
Vegas Pro 12 64-bit

Thanks for some help.
Marco. schrieb am 08.10.2014 um 20:04 Uhr
It looks like you either installed the wrong FrameServer version (it should be version 2.14 for Vegas Pro 12) or you installed into the wrong program folder path. You must be careful with FrameServer 2.14 because if you don't modify the installation path it will use a path for Vegas Pro 11.
fldave schrieb am 09.10.2014 um 00:08 Uhr
Point the 64bit Debugmode install to the C:\Program Files\Sony\Vegas Pro 12.0, not the "Program Files(x86)" folder.
My scripts aren't showing up, but haven't rebooted yet. Not sure if I should copy the contents of the "frameserve_scripts" folder or the folder itself to the Script Menu folder.
SecondWind-SK schrieb am 09.10.2014 um 01:19 Uhr
I'll try that. Thanks.
MikeyDH schrieb am 09.10.2014 um 01:49 Uhr
Same result after reinstall of NET Frameserver. I'm going to uninstall all and try again. Maybe I tripped up somewhere.
Rv6tc schrieb am 09.10.2014 um 03:03 Uhr
Mine will start frameserving correctly, but it never opens up Handbrake. When I open Handbrake manually, I cannot force it to open the framserve .avi file.

What am I doing wrong.

Also, virtualdub will open the frameserve file.

Thanks,

Keith
Marco. schrieb am 09.10.2014 um 21:03 Uhr
Did you try using the new modified batch file linked in my first post of this thread?
Rv6tc schrieb am 10.10.2014 um 19:28 Uhr
I've tried both.

Thanks.
Byron K schrieb am 11.10.2014 um 19:47 Uhr
I had similar issues, I was installing the FrameServer app in the default path but needed to install it in the Vegas 12 folder.

- At DebugMode FrameServer Setup: Installation Options screen, Select: Sony Vegas (64-bit) Plugin. Click: Next
- Install FrameServer in the root "C:\Program Files\Sony\Vegas Pro 12.0" folder.
- Install frameserve_scripte in the "C:\Program Files\Sony\Vegas Pro 12.0\Script Menu\" folder.

Also, depending on which batch file you're using you'll need to have a network connection for it to work or use VidMus' revised script that doesn't need an internet connection:

timeout /t 2 /nobreak
start "" "C:\frameserver\batch\enter.exe"
timeout /t 2 /nobreak
:vegasavi
for /f %%i in ("C:\frameserver\source\vegas.avi") do if %%~zi gtr 160000 goto checkframeserver
timeout /t 2 /nobreak
goto vegasavi
:checkframeserver
for %%F in ("C:\frameserver\source\vegas.avi") do set filesize1=%%~zF
timeout /t 2 /nobreak
for %%F in ("C:\frameserver\source\vegas.avi") do set filesize2=%%~zF
if %filesize2% gtr %filesize1% goto checkframeserver
:avfs
pfm register C:\frameserver\avfs.dll
timeout /t 2 /nobreak
pfm mount C:\frameserver\vegas.avs
timeout /t 2 /nobreak
:handbrake
for /f %%i in ("C:\frameserver\vegas.avs\vegas.avi") do if %%~zi gtr 160000 goto hbstart
timeout /t 2 /nobreak
goto handbrake
:hbstart
start handbrake "C:\frameserver\vegas.avs\vegas.avi"
:waitforhandbrake
timeout /t 2 /nobreak
tasklist | findstr /i "Handbrake.exe"
if %errorlevel%==0 goto stop
goto waitforhandbrake
:stop
start "" "C:\frameserver\batch\stop_render.exe"
dingus schrieb am 04.01.2015 um 18:57 Uhr
I am trying to frameserve (version 2.15 ) a 4K xavc s file (3840 X 2160/ 29.970 fps) to handbrake via VP13 to resize to 1920 X 1080 for Blu Ray mpeg2. Handbrake opens, receives and scans the incoming info from frameserve, then goes into a "ready" state, but there is nothing available to render. When I click Start (in Handbrake), the error message reads: You must first scan a source and set up your job before starting an encode. Anyone know what I am missing or doing wrong?
MTuggy schrieb am 04.01.2015 um 19:42 Uhr
I don't think Handbrake will encode to mpeg 2 - I think it only puts out MP4 or M4v files.

Mike
dingus schrieb am 04.01.2015 um 20:01 Uhr
Thanks, I understand that. Handbrake provides superior image quality when resizing. I intend to import the rendered MP4 file from handbrake into Vegas for final render to MPEG 2. I currently do this using an intermediate, but frameserving would eliminate that time consuming step.