Frameserving?

Comments

NormanPCN wrote on 5/2/2014, 9:47 PM
Will it work with one pass at a slightly higher bit rate?

Sorry for using the term "pass". In the video encoder context it can be taken differently. Let me rephrase.

Handbrake is designed to randomly access/read its input file and/or sequentially read from of the file more than once.
Hulk wrote on 5/2/2014, 10:19 PM
Norman,

Still strange that it works in Ripbot, even in the two-pass mode. Furthermore you can preview the file in Ripbot and scroll anywhere you want and Vegas will follow.
musicvid10 wrote on 5/2/2014, 11:15 PM
"Scan Pass" and "Encoding Pass" are two completely different functions.
Handrake can do two-pass encoding. That makes three passes in total.

I don't know what ripbot does or what module(s) are used during the initial scan.
I'm reluctant to install it because it wants k-lite under the hood.
NormanPCN wrote on 5/3/2014, 12:39 AM
Still strange that it works in Ripbot, even in the two-pass mode. Furthermore you can preview the file in Ripbot and scroll anywhere you want and Vegas will follow.

Okay. That sounds like more than a generic pipe like interface. Given what you say it specs like more of a special protocol specific on Windows.
wwaag wrote on 5/3/2014, 11:44 AM
Handbrake is designed to make more than one pass over the input file. That is the sole reason why it cannot work with a frameserver.

Don't think this is correct. E.g. you can frameserve to a signpost avi file which will open in Virtudaldub. You can then apply the Deshaker filter, which is a two-pass operation. On pass 1, select "Run video analysis pass" and it will process the entire file. Then change the filter to Pass 2, Save as AVI and it will process the file again and save the results. If your're not happy with the results, you can change the Pass 2 parameters and process the file again. Clearly, the frameserver supports multi-pass.

On a simpler level, you can simply select points in the displayed file with Vdub, go back and forth, or whatever, and you can see the fame number displayed in the Vegas preview change.

To me, this suggests that the problem lies in the application (e.g. Handbrake), and not in the frameserver itself.

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.

Red Prince wrote on 5/4/2014, 10:14 AM
Just letting you all know, I downloaded the 32-bit Virtual Dub, and now I can frameserve to it. So, the 64-bit version of VD does not support frameserving but the 32-bit version does, even if the source is 64-bit Vegas.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

skeeter123 wrote on 5/9/2014, 11:29 PM
...with VP 13?

Any update on frameserving? Just curious....

ChrisDolan (SCS) wrote on 5/12/2014, 10:20 AM
I just got an email from Satish this morning in which he says he's still working on it.
Chris
skeeter123 wrote on 5/12/2014, 10:45 AM
Thanks, Chris! You da man!!

(Seriously, your feedback is GREATLY appreciated!)




dxdy wrote on 5/12/2014, 11:11 AM
Indeed, totally awesome.

Thanks, Chris.
NickHope wrote on 5/22/2014, 10:23 PM
Satish posted a few hours ago to the frameserver-discuss Google group:

Sorry its taken so long. Its more work than I expected because frameserver installer today includes so many different plugins that supporting both 32 bit and 64 bit plugins is complicated. I'm having to build a separate installer for Vegas now to simplify things, and I expect to release something mid next week. Thanks for your patience in the mean time.

With luck, it might even be available before the VP13 upgrade offer closes.
skeeter123 wrote on 5/24/2014, 12:27 AM
Thanks for the update, Nick!

..
NickHope wrote on 6/12/2014, 8:34 PM
Satish is now looking for beta testers for his Frameserver build for VP13.

[url=https://groups.google.com/d/msg/frameserver-discuss/4Oo5dLRuvPM/J_pZH3ZMebsJ]
john_dennis wrote on 6/14/2014, 7:02 PM

From Satish:

"Satish Sampath

2:31 PM (2 hours ago)

Thanks Dennis! That was a pretty exhaustive test. Looks like its working in the typical use case of frameserving to an external encoder but fails in many cases when frameserving to another version of Vegas. I haven't specifically tested that case in any version or specifically made it work, so I'll go ahead and release this version to the public.

Thanks for your help again. Much appreciated."


The results of my tests:


DVD Architect

Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

DVD Architect 6.0 (237) recognized the signpost.avi file and was able to render to a Blu-ray image.

(Admittedly, not a common workflow.)



Image sequence Output didn't work in this release.




TMPGEnc

Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

TMPGEnc-2.524.63.181-Plus recognized the signpost.avi file and was able to render to DVD elementery stream files.



VirtualDub

I was able to open the signpost file in VirtualDub-1.10.4-32 bit) but not VirtualDub-1.10.4-AMD64.



Windows Media Player

Windows Media Player worked on the local machine but played with audio only on another machine on the network.

The same was true whether the signpost file was being served to a file on the local or remote machine.



Frameserving from Vegas Pro 13
RGB24
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 12-770 64-bit could not identify the file:G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi on a local disk.



Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 12-770 64-bit could not identify the file:G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi on a local disk.
Msg: File G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi could not be opened.


Frameserving from Vegas Pro 13
YUY2
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 12-770 64-bit could not identify the file:G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi on a local disk.
Msg: File G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi could not be opened.



Frameserving from Vegas Pro 13
RGB24
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 13-310 64-bit could not identify the file:G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi on a local disk.


Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 13-310 64-bit could not identify the file:G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi on a local disk.


Frameserving from Vegas Pro 13
YUY2
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 13-310 64-bit could not identify the file:G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi on a local disk.
Msg: File G:\Frameserve This\2014-05-03 Angelica's Baby Shower v3.avi could not be opened.



Vegas Pro 9.0e 64 bit

Frameserving from Vegas Pro 13
RGB24
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 9.0e 64-bit could open the audio but not the video.


Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 9.0e 64-bit could open the audio but not the video.


Frameserving from Vegas Pro 13
YUY2
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 9.0e 64-bit could open the audio but not the video.


Vegas Pro 10.0e 64 bit


Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 10.0e 64-bit could open the audio but not the video.



Vegas Pro 11-701 64 bit

Frameserving from Vegas Pro 13
RGB32
Write audio as PCM samples in the signpost file is checked.
Enable Network Frameserving is checked.
Network Port to use 8278

Result: Vegas Pro 11-701 64-bit couldn't open the signpost file.

 

Tom Pauncz wrote on 6/15/2014, 1:48 PM
That's a great amount of work & good testing @john_dennis.

I did reply to Satish about volunteering, but never heard back.

Any idea when the update will be up for general use?

Tom
john_dennis wrote on 6/15/2014, 3:17 PM

"Any idea when the update will be up for general use?"

He didn't say. I suspect when he gets a round tuit.

Tom Pauncz wrote on 6/15/2014, 4:01 PM
"a round tuit"

I have a few of those to spare I could send him. LOL!

Tom
Satish [Debugmode] wrote on 6/16/2014, 9:09 AM
Hi all,

Thanks for your patience, I've released a new version of Debugmode Frameserver 2.15 specifically for Vegas Pro 13. More info at https://groups.google.com/forum/#!msg/frameserver-discuss/4Oo5dLRuvPM/C4cHc1U6wn4J

Thanks
Satish
Tom Pauncz wrote on 6/16/2014, 9:57 AM
Thanks for all your hard work Satish... I assume that 2.14 and 2.15 cannot co-exist.

So if we still want to able to frameserve from VP12, as well as from VP13, how??
Tom
Satish [Debugmode] wrote on 6/16/2014, 8:28 PM
I'm not sure to be honest.. you could try installing both versions one after the other, but give different install paths for the frameserver "core" module (default is Program Files\debugmode\frameserver, so just change it to something else).
Satish [Debugmode] wrote on 6/16/2014, 8:30 PM
Interestingly, someone in my user groups wrote:

"It seems there are no problems using Frameserver 2.15 in combination with Vegas Pro12 because I de-installated Frameserver 2.14 at first and even now I'm able to use the combination in Pro12."
NickHope wrote on 6/16/2014, 10:20 PM
Thank you Satish.

Has anyone tested this to see if it works from Vegas Pro 13 to AviSynth?
wwaag wrote on 6/16/2014, 10:30 PM
Has anyone tested this to see if it works from Vegas Pro 13 to AviSynth?

I have using one of your AVS scripts for Megui encoding. No problem.

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.

john_dennis wrote on 6/16/2014, 10:32 PM
My test bed never had 2.14 installed. When testing I installed 2.15 for Vegas Pro 13 in the defaults.

Just now I went back and installed 2.14 in a directory with a different name. I put the 64 bit in the Vegas Pro 12 directory.

I was able to frame serve from Vegas 12 and 13 at the same time. Vegas Pro 9.0e on a different machine saw the audio from both signpost files on different hard drives over the network. I was able to run two instances of TMPGEnc and render at the same time.

I can't promise that it can't be messed up, but it seems to work with both versions installed on the same machine.