from one of the authors of avisynth...:
*****************************
DirectShowSource (DSS) creates 2 graphs, one for video and one for audio and uses AudoDub() to join them. We do this because we need the audio and video timing to be independant. A Directshow graph only has 1 clock source and 1 current position for all streams.
DSS works by adding our custom renderer for Video or Audio and calling RenderFile. This creates a default graph connected to our renderer. The Video renderer accepts Video streams of subtypes RGB24, RGB32, ARGB, YUY2 and YV12. The Audio renderer accepts Audio streams of subttypes PCM 8bit, 16bit, 24bit, 32bit and IEEE Floating point.
When Loading saved .GRF files you must set either Audio=False or Video=False to match the Video or Audio only graphs loaded respectivly. You have to do the AudioDub() manually. The .GRF file must have 1 only open pin that will directly offer one of the formats and subformats our renderer will accept. We do not negotiate for format converters to be added.
*****************************
EDIT: you have to create 2 graphs, 1 for audio,1 for video...probably not really usable for tuner capture..
so for example:
you could create a graphedit graph with your capture card and save it, [all the way up to capture device raw output + filters[pre-compression/mux] but no output file filter] and make a .avs file with directshowsource inputting video, another DSS inputting audio, and a line AudioDub-ing them together, and open that with ffmpeg and encode and save to a mpeg file....
or possibly create a whole encoding graph,and just dump output with ffmpeg to file..creating a command line use of directshow filters..with piping ability no less...lol
not sure how sync would work,but that could be adjusted in .avs...
then a single ffmpeg line could capture a channel to mpeg from external recorder plugin...
i have a feeling the tuning won't happen tho, cuz even tho it saves channel in graph, graph usually won't actually change channel unless told to separately..
just some interesting info i thought i'd share...
*****************************
DirectShowSource (DSS) creates 2 graphs, one for video and one for audio and uses AudoDub() to join them. We do this because we need the audio and video timing to be independant. A Directshow graph only has 1 clock source and 1 current position for all streams.
DSS works by adding our custom renderer for Video or Audio and calling RenderFile. This creates a default graph connected to our renderer. The Video renderer accepts Video streams of subtypes RGB24, RGB32, ARGB, YUY2 and YV12. The Audio renderer accepts Audio streams of subttypes PCM 8bit, 16bit, 24bit, 32bit and IEEE Floating point.
When Loading saved .GRF files you must set either Audio=False or Video=False to match the Video or Audio only graphs loaded respectivly. You have to do the AudioDub() manually. The .GRF file must have 1 only open pin that will directly offer one of the formats and subformats our renderer will accept. We do not negotiate for format converters to be added.
*****************************
EDIT: you have to create 2 graphs, 1 for audio,1 for video...probably not really usable for tuner capture..
so for example:
you could create a graphedit graph with your capture card and save it, [all the way up to capture device raw output + filters[pre-compression/mux] but no output file filter] and make a .avs file with directshowsource inputting video, another DSS inputting audio, and a line AudioDub-ing them together, and open that with ffmpeg and encode and save to a mpeg file....
or possibly create a whole encoding graph,and just dump output with ffmpeg to file..creating a command line use of directshow filters..with piping ability no less...lol
not sure how sync would work,but that could be adjusted in .avs...
then a single ffmpeg line could capture a channel to mpeg from external recorder plugin...
i have a feeling the tuning won't happen tho, cuz even tho it saves channel in graph, graph usually won't actually change channel unless told to separately..
just some interesting info i thought i'd share...
Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie