WDM Recorder using Software Compression

[Kevl]

Hi Norman

Have experimented further with your fine software.

Noticed that the plugin seems particularly fond of the "medium" record setting. On my setup it defaults back to this when closed and then reopened even if I set the quality to "LiveTV" or even "low"

Tried various colour settings. 480 lines is the most that was allowed.

Have edited recorder-config.xml and changed the res values to 720x576 in the sections where the resolution is specified.

The xml file had lots of stuff in it that was incorrect e.g country code 1 etc (rather than 44) in some sections - eg. capture source oid :0. Whereas in capture source oid:6 (presumably the RGB input) the values were correct and as per the setup form.

Hand corrected this and some other info. Ran GBPVR and got a better picture than before but still not as good as dScaler. When I then attempted to edit card info (to see what if any of my changes had been accepted) the plugin driver generated an exeption and complained about 576 being > 480. Probably this is due to parameter validation in your code. I can see why good code might take exeption to values outside its range. You probably put extra effort in to check values :-).

Begs the question as to why 480 lines is being reported by my device driver. dScaler seems to think that 720x576 is right and proper.

As a side note . The OSD is still very poor. It looks like the resolution of the OSD is still very low. If I had the wherewithall I would post screen shots to show you.

All of the above is with the v18 of your SW. havent yet tried the v19.


Best regards

Kev

[normanr]

Noticed that the plugin seems particularly fond of the "medium" record setting. On my setup it defaults back to this when closed and then reopened even if I set the quality to "LiveTV" or even "low"

The selection doesn't actually change the recording quality, it's just used to choose which one you want to modify. (The other recording plugins work in the same way.)

Tried various colour settings. 480 lines is the most that was allowed.

This is pulled directly from the capture card drivers.

The xml file had lots of stuff in it that was incorrect e.g country code 1 etc (rather than 44) in some sections - eg. capture source oid :0. Whereas in capture source oid:6 (presumably the RGB input) the values were correct and as per the setup form.

hmm, it shouldn't have let you save oid:0 (maybe due to an older version), it'll be ignored anyways. Only the capture source with the same oid as defined in the database will be used.

When I then attempted to edit card info (to see what if any of my changes had been accepted) the plugin driver generated an exeption and complained about 576 being > 480. Probably this is due to parameter validation in your code. I can see why good code might take exeption to values outside its range. You probably put extra effort in to check values :-).

nope, no validation in my code. I can guess that the WDM drivers might be kicking it out though. Can you supply the log files from during configuration and from during you testing, they might explain where stuff is breaking, and what's supported by your card. (I've found some cases of where the same color space is listed twice with different capabilites)

Begs the question as to why 480 lines is being reported by my device driver. dScaler seems to think that 720x576 is right and proper.

Does dScaler also use the WDM drivers? Maybe it's scaling up the video from 360x288?

As a side note . The OSD is still very poor. It looks like the resolution of the OSD is still very low. If I had the wherewithall I would post screen shots to show you.

did you try VMR9 vs VMR7 vs Overlay?

[Kevl]

Hi

Tried VRM9, VRM7 and overlay mode.

VRM9 and 7 give a transparent osd which is of low resolution but the pixels appear smoothed. Overlay mode gives non transparent osd and the resolution is clearly very low. Fonts appear to be made from distinct large blocks. My graphics card is a 9600xt so is VRM9 compliant.

Dscaler can use the wdm model but has its own drivers also which are configured through the dscaler front end. When in dscaler using dshow WDM driver then it is possible to set a 720 x 576 screen resolution and picture is very high quality.

Wondered if the sweetspot wdm driver was to blame so uninstalled the open source driver and installed the sweetspot WDM driver supplied with the card.

No difference in display.

The video does actually seem to work when viewing the live TV it is just that the video is low res and the osd is really poor.


Kev

[bentheo]

i've installed the version 19, and when i go to edit the settings for the wdm software encoder, it freezes and crashes when i choose my video capture card (wintv-go). i can't even save my settings.

any advice?

[normanr]

any advice?

zip up all your log files, and attache them here. Not much I can do without them.

[bentheo]

sorry, i should have done that to begin with

[normanr]

Can you supply the log files from during configuration and from during you testing, they might explain where stuff is breaking, and what's supported by your card. (I've found some cases of where the same color space is listed twice with different capabilites)

Woops, your logs are missing all the capture card details. When you open the configuration window, can you reselect your video capture card. This should make it parse all the options and log them. Then resend the logs. Thanks!

[normanr]

i've installed the version 19, and when i go to edit the settings for the wdm software encoder, it freezes and crashes when i choose my video capture card (wintv-go). i can't even save my settings.

argh, my support of cards without crossbar is less than great so far, basically it means that I need to ignore errors generated by a missing crossbar. (that's what the log files tell me). Do you have a more detailed error log of exactly where it breaks, or does it freeze before that's generated?

Otherwise I'll try and ignore any errors generated during crossbar detection, but I'm worried that the detection might be breaking it so badly that it can't recover.

[bentheo]

argh, my support of cards without crossbar is less than great so far, basically it means that I need to ignore errors generated by a missing crossbar. (that's what the log files tell me). Do you have a more detailed error log of exactly where it breaks, or does it freeze before that's generated?

Otherwise I'll try and ignore any errors generated during crossbar detection, but I'm worried that the detection might be breaking it so badly that it can't recover.

those are the logs right after i tried to select my capture card. like is said it crashes right when i select it, so i guess it doesn't get generated

[normanr]

those are the logs right after i tried to select my capture card. like is said it crashes right when i select it, so i guess it doesn't get generated

what's displayed when it crashes? is there any text then?