WDM Recorder using Software Compression

[pBS]

heyas,thanx for the update trying to edit the recorders xml and think i know now what you meant about the crossbars, yes it does find 2 but there's another little thing that is messing me up,seems there are 2 ouput pins on my video capture device with the same name! if you look at the jpg graph i posted, the video capture device has 2 'capture' pins,first one i video,second one is audio output,but when i try to connect,it keeps thinking they are the same one...
attaching a pic of preview graph that works...

when i set it up as i thought it should be,i almost got it going,but it kept assigning the output3 -> ati audio encoder -> acm wrapper -> sound card instead of 'capture' [second one] -> acm wrapper ->sound card..
i tried specifying preview pin to capture video,and capture pin to capture audio, video worked but audio would attach to video's capture pin instead of the second one...

i noticed graphedit uses pin #'s to specify pins intead of names to keep it from getting confused..[it has pin 2-7 routing on video capture device,would this make it like a crossbar?]

also,i noticed the generic-graph capture plugin, is this available anywhere?

[pBS]

i believe it wold work if i were able to select the second capture pin [it selects the second one by default when i select ati card as audio device] but when i hit 'ok' it says i can't select the same pin for audio and video..but they're not the same pin! [just the same name]
any ideas?

[normanr]

also,i noticed the generic-graph capture plugin, is this available anywhere?

I've seen it before, but I'm not sure if the developer actually coded anything, or released anything. I search for around 30 minutes on the forums for it, but it eluded me. If you find it (or a post about it) please post a link to it. We can at least create a wiki page saying it's work-in-progress.

i believe it wold work if i were able to select the second capture pin

yes, it would. I never would have thought that two pins with the same name were allowed. Unfortunaly I just detect the name and pass it to GB-PVR for rendering, so the fix needs to be made in the core GB-PVR code. (Fix to detect pin type?)

This fix is only required for preview mode, so if you disable preview and force timeshifting mode it should work.

An alternative would be to load up the card's drivers in a hex-editor, and search for 'Capture' and replace it with 'Captur1', 'Captur2', etc. Then the two pins would be called different names, and GB-PVR core would be able to tell the difference.

[pBS]

thanx...i thought about that but wanted to see if a better fix were available...
will report back..i think i remember Sub [or someone] saying the generic graph plugin wasn't ever finished so has never been available...but wanted to make sure...i believe whoever wrote the recorder test was working on it but never finished...
will try the hexeditor and let you know..

[pBS]

no luck finding the capture driver's pin assignments...searched the entire install and nothing jumps out, can't even figure out where the names are coming from...[stupid usb driver!]
guess i'll have to do some searches,or try to find if older driver has different names for pins..bummed..
wish i knew of a way to load the graph and have it play automatically...
[pretty sure there's no command line opts for graphedit]
will look in registry...may be in there...
thanx for the help..

will look into making the ati encoders properties work when i get this going..
not sure why but it seemed to take defaults when i used them even after my graphedit graph was retaining bitrate settings even after reboot...

[pBS]

well looks like the naming of pins is obsolete thesedays...probably why they didn't care if it had the same name, MS says you're supposed to call the pin by pin# and not name as it doesn't check to see if the names are unique..
from the directshow docs..:
Members

strName - Name of the pin. (Obsolete.)

oh well....back to using the pctv rave...
thanx for the help...maybe now all-in-wonder cards may work...[although,now that i think about it,they use the same drivers! lol no wonder everyone has such a hard time with them!]

[normanr]

Well I wrote the RecorderTest, RecorderHelper, DShowNet, SoftwareRecorder and ExternalRecorder modules. I do remember someone saying they wanted to write the generic graph plugin, but I didn't hear any more feedback after that.

I could just write one myself from scratch to read the xml files generated by Graph Edit, but wouldn't have terribly much use for it, so there's little motivation.

[normanr]

Ha ha! I found the Generic Graph plugin reference, and my reply to it. Basically it's a recording source that's inside of the gb-pvr core, but it's non-functional.

[collindv]

collindv, DeepSpace1, pBS: this build supports multiple crossbars, but there's no frontend for it yet! Please can you try the following:
- install new version
- go into the 'software recorder configuration' window (just open window, and close it again)
- look in config.exe.log at how many crossbars were detected, and what mappings were found.
- edit the config_recorders.xml's crossbarRoutings manually.

The enhanced crossbarRoutings format is take each crossbar routings you want and seperate them with a semi-colon. e.g. it might look something similar to: 0-0,1-1;1-0,3-1 (your cards will be different). The items should be listed in the same order as the config log file detected them.

I will give this a shot when I get home this evening and post my results. Thanks for the new build!

[collindv]

Normanr, I have attached my config.exe.log file. Looks like it detected 2 crossbars. Based on this, how should I edit my config_recorders.xml's crossbarRoutings? Thanks.