x264farm-sp - single-pass distributed encoding

[Quark.Fusion]

I provided AVFS as example of custom file system — it can retrive data from anywhere.

You can write custom AviSynth source plugin, that will request file over network. SMB isn't good enough for it?

I still think that using shared folder is best way to go. In Vista you can drop symbolic links to network folders (junctions doesn't work). So you set up shared folders with «net share», create link with «mklink ‹file› "\\‹ip-address›\‹Share›\‹file›"» and don't need to change avs :)

[Audionut]

Hi Omion,

Everything is working great, cept the controller doesn't read the FPS from a server 2008 machine.
It picks it up from the XP machines fine.

Any ideas?

[popper]

Well, it looks like TCPserver does basically what controller-based encoding does, so I don't think it would help too much. AVFS is similar too -- I want to avoid transferring the uncompressed data if at all possible.

What I really want is when the script says something like
SomeInputFunction("c:\file.d2v")
I want to capture the actual file lookup and send it to the controller's system. But to do that I would need to get something in between the AVS DLL and the Windows system call.

Doing it this way has the networking advantages of agent-based encoding with shared folders, but you wouldn't have to set up any sharing or even change the AVS file. The source files wouldn't have to use absolute paths anymore either, since it only does a lookup in the controller's computer.

I've been looking into Google Chrome, since it looks like the sandbox uses DLL function redirection. Chrome is where I got the idea to use jobs to contain the child processes, and it looks like there are a lot of other clever things in it. The biggest problem is that I don't really know how to read C++.

perhaps im misreading your intent, but given your good at scripting (and thanks for taking current powerful apps already available and wrapping them into this great LAN/WAN based encoder) and yet reading C++ is not your favourate thing ;) then rebol scripting will be perfect for you and your app(s) and any new related prototyping you might want to do later.

it seems your after taking the these AVS scripts etc and parsing them for actions then manipulate them to your/our current wishes and pass it along to and from your controller farm scripts etc.

if thats the case, you REALLY should take a look at "Rebol view" and "rebol core" cross platform lightwight Gui and Ip networking scripting app etc ,written by carl Sassenrath of amigaOS lead programmer fame so you know its small ,good and fast.

and more than that, it would allow you to make a very simple or complicated GUi for any platform that can run your controller x264farm scripts already, load scripts/parts off the LAN or the web directly and so much more.

seriously take a look while rebol 3 is taking shape
http://www.rebol.net/cgi-bin/r3blog.r
for several working Gui examples and script parsing in general.

http://www.rebol.net/r3blogs/0154.html
"Even though these two images use the same GUI panel for layout, note the difference between these skins is more than just a change of colors. It includes differences in shading, rounding, highlights, coloration, and much more.

Note it should be mentioned that these GUI's are built descriptively in R3 scalar vector graphics (SVG) DRAW format. Neither one of these uses a single image file.
"

http://www.rebol.net/r3blogs/0129.html
http://www.rebol.net/


rebol would be just so much better than the current crop of static OS GUIs we are seeing for all the x64 front ends, and its about time some good advanced scripters took rebol view and make far better and versitile Gui's and control apps, perfect for your cross platform encoding farm, powerful and yet simple for the likes of you omion, and easy to copy and run anywere you like.

hell you might even find rebol so good you re-code your farm in rebol core (the cli version) script as its got every single IP protocol you might want to ever use, includeing tuneling ,multicast, http,and many others.....and yet its free for personal use etc.

i would really like to see your app be the very first mainstream video app to advantage of and use rebol view 2 and/or 3 and all it's power in a 600kbyte cross platform self contained binary.....+script OC.

you can also load dll's if you want to go that far, and wrap them up in rebol scripting, and parse all your input/outputs
http://www.rebol.org/view-script.r?script=web-cam.r gives you a simple working example sending messages for instance.

see also Steeve's code
http://www.rebol.net/cgi-bin/r3blog.r?view=0155#comments
"...
Steeve
6-Nov-2008 12:09:01 10 months ago, i tryed to develop an async parser (parsing of stream files). IMHO, a major improvement of parse would be this: to be able to parse data ports.
* Pending this day, i reposted my last version of async-parser here: "About the parse evolution" thread

http://www.digicamsoft.com/cgi-bin/rebelBB.cgi?thread=<6Nov200818052719372100>

* Currently, it can parse a file without the need to load the whole file in memory.
"