Analog recordings not working when PC has more than 4gb RAM(ATI Theater Pro 650 PCIe)

[johnsonx42]

<Device filter="ATI AVStream Analog Capture">
<Name>ATI 550 Pro</Name>
<Type>HARD_ENCODE</Type>
<FilterEncoder>ATI AVStream Analog Capture</FilterEncoder>
</Device>

The name is ATI 550 Pro while I've got a 650 Pro, but that shouldn't make a different, right? The "ATI AVStream Analog Capture" is the correct device filter name.

The <Name> field is not used by the program at all; I think sub said he originally planned to use it for something, but never did. Now it's just used for whatever descriptive name the user creating the entry cares to put there.

[johnsonx42]

That analogdevices.xml entry doesn't read right to me though, and that's why the hardware encoder won't hook up. It should be:

Code:

    <Device filter="ATI AVStream Analog Capture">
        <Name>ATI 550 Pro</Name>
        <Type>HARD_ENCODE</Type>
        <FilterEncoder>ATI AVStream MPEG2 Multiplexer</FilterEncoder>
    </Device>

[-stattik-]

That analogdevices.xml entry doesn't read right to me though, and that's why the hardware encoder won't hook up. It should be:

Code:

    <Device filter="ATI AVStream Analog Capture">
        <Name>ATI 550 Pro</Name>
        <Type>HARD_ENCODE</Type>
        <FilterEncoder>ATI AVStream MPEG2 Multiplexer</FilterEncoder>
    </Device>

I updated analogdevices.xml and restarted. Do I need to rediscover and configure my hardware in NPVR?

[-stattik-]

I just looked at the logs you posted earlier, and saw about it being unable to find the pin medium for this device, so couldn't find the hardware encoder.

I could probably hard code some logic to force it to find the hardware encoder for this device, but I suspect it's this device is going to be non functional with that extra ram, so it might be worth you trying to confirm the device is functional before I go to that effort. ie, you might need to download Microsoft AmCap, or try the device in GraphEdit. If it functions in either of those, then I'm happy to spend the adding a work around for the detection of the encoder on this device.

Is there an example graph I could use for reference? I'm not sure how start creating it in Graphedit.

[johnsonx42]

I updated analogdevices.xml and restarted. Do I need to rediscover and configure my hardware in NPVR?

afaik it should start using the hardware encoder without any further reconfiguration. it probably won't address the 4GB issue though.

[johnsonx42]

Is there an example graph I could use for reference? I'm not sure how start creating it in Graphedit.

no point in that until you check whether the new analogdevices.xml entry helps

[mikeh49]

Here's a graph I found from some past experiment.

Also, this card worked for analog back in the gbpvr days. Attached is the direct.ini that contains the settings for it, if that is of any use.

@johnson - the revised analogdevices.xml entry does not help. Nrecord log says it can't find an encoder. And, the encoder section of filtercheck.log is empty. The multiplexer is in the multiplexer section with the name you suggested. This same name is in the wiki example too. I stopped and started the recording service after editing the file. Did not reboot, however.

[johnsonx42]

Here's a graph I found from some past experiment.

Also, this card worked for analog back in the gbpvr days. Attached is the direct.ini that contains the settings for it, if that is of any use.

@johnson - the revised analogdevices.xml entry does not help. Nrecord log says it can't find an encoder. And, the encoder section of filtercheck.log is empty. The multiplexer is in the multiplexer section with the name you suggested. This same name is in the wiki example too. I stopped and started the recording service after editing the file. Did not reboot, however.

the analogdevices.xml entry I provided matches the gb-pvr direct.ini entry (NPVR just does most of that using the pin medium instead of having it all spelled out manually). I vaguely remember something from the early days of NPVR about some change to the code required for devices that listed their encoder only as a MULTIPLEXER filter and not as an ENCODER; this also lead to a change in Filtercheck.exe to list the MULTIPLEXER filters as well, as it previously did not.

In any case I'm pretty sure the entry I provided is correct (despite the fact that it still doesn't work); I don't see how the original one could have ever worked, it would have always failed back to the soft encoder.

[pBS]

i get the same behavior, it always falls back to soft encode...i also have that file updated to proper entries..
yes, i'm thinking that the multiplexer category isn't being looked in for encoder, or something of that nature..

about to try the graph to test the 64bit compatibility..

well, graph didn't load much filters for me, so i just cranked up an old gbpvr and made one..
attached is a graph for graphedit, a pic of it opened, and a list of clsid's from a graphstudio dump to xml...

Sub, if you need any other info just let me know...i have it working on old pvrx2 so no problems with 64bit-ness..

[-stattik-]

Attached are are the graphs I built using pBS's graph for reference. I get as far as the demuxer but it doesn't have any output pins. I'm not sure how to test it. Clicking play doesn't really do anything.