It'd be truly awesome to be able to dump an avs straight into final cut pro, and render it there for realtime playback, especially considering the colour problems with quicktime (ie, if you use quicktime to export a mov, it'll bugger up the colours in a peculiar and unrecoverable way - something like YUV to RGB with made-up coefficients and some kind of gamma "correction"). Would this work over a network? could i for example create an AVFS folder on the SAN here from one computer (an 8-core PC with dual fibre-channel connection to the SAN), and load it on another machine (a mac edit suite)? There should be some useful stuff there about stuffing yuy2 into a mov file, although i think it uses quicktime itself to handle it, so it may not work for virtual filesystem stuff. fabricate any file or frame headers needed for portions of the read buffer.Īnyone interested in working on these remaining bits, send me a PM. read frames and audio from avisynth and fill the read buffer. figure out which frames and audio are needed for a range of bytes in the virtual file. support different media file formats, wav, avi1, avi2.
support spanned media files, for the varios 32 bit file size limitations. use stream info from avisynth and options from avs file to determine appropriate file format for virtual media file. Determine the initial names and sizes of the virtual media file(s). What is finished is a virtual file system that allows you to "mount" an avs script, turning it into a folder that contains an empty virtual media file and an editable copy of the script file.ġ. It builds with MSVC6 and has been through some developer testing. The code is on sourceforge in the module avfs at the root of the avisynth2 CVS repository. I have finished the file system bits for AVFS.
If you are willing to work with me on this, send me a PM and we can continue offline.
The audit package exists and is licensed for free use by individuals, business users, developers, and to be used as an enabling system extension for other freeware and open source projects.
It is a freeware utility that allows mounting if various archive file formats, and includes the PFM development kit. The Pismo File Mount Audit Package can be downloaded from. Tools? (I prefer the SDK compilers myself) I need to know the general parameters first: To start with I can put together the basic AVFS formatter source, minus the actual AVI/Avisynth bits. Still, I can speed up the PFM specific parts of the development, do troubleshooting, etc. This package includes a developer document, headers files, and a few C/C++ sample formatters (user mode file systems). Most of what I'll provide is already included in the Pismo File Mount Audit Package.
What I need to get started is another developer who can do the things you mentioned earlier. If someone is willing to help who has Avisynth/VFWAPI/AVI code experience and resources, I believe things would come together pretty quickly. I have the Windows system extension work completed for this, see.
chaining between 32 bit and 64 bit tools. chaining tools that are running on different systems.
chaining non VFWAPI enabled video processing tools. This would provide alternative solutions for: This would allow a user to mount an Avisynth script, exposing a virtual uncompressed AVI file through the file system. I would like to help build an open source or freeware Avisynth virtual file system. Also, the required Pismo File Mount (PFM) build 174 now implements mounting differently, through a c:\volumes folder instead of a virtual mount point placed over the AVS script. The installation is now simpler, but some explorer integration is lost. The package includes a readme.txt file with installation instructions and release notes.įor users of prior version of AVFS, things have changed. The latest release of Avisynth Virtual File System is available at: