Avermedia M150-D Delay/Lag on Start of Recording

[uniontown]

I am a long time user of GBPVR and think it is an excellent program. Over the years I have run the following cards in the program, Emuzed Maui I(HP), Emuzed Maui III(G), Hauppauge PVR-150, Hauppauge HVR-1250, Hauppauge HVR-850, Avermedia Volar Max, and have never had any trouble setting them up and using them. My problem is with a reently acquired Avermedia M150-D that works fine when viewing live TV, but does not record correctly. If viewing live tv and pausing it, the program stops functioning for approximately 3 & 1/2 to 4 & 1/2 minutes, and then commences to start to record. The same is true if one manually schedules a recording of a program. GBPVR will start on time but the actual recording service will not start (and the icon will not turn green indiating that it is recording) for approximately 4 minutes. In looking at a salient log of a test recording I made a few days ago in the XW4100 the following appears:


2010-01-31 18:20:54.000 INFO Log started
2010-01-31 18:20:54.000 VERBOSE getSetting(LoggingLevel)
2010-01-31 18:20:54.000 INFO Logging Level is Debug
2010-01-31 18:20:54.000 VERBOSE getSetting(LoggingForceFlush)
2010-01-31 18:20:54.015 INFO Log flushing enabled
2010-01-31 18:20:54.015 VERBOSE Asking Windows to be awake for recording (oid: 1) at 2010-1-31 18:19:30 (UTC 2010-1-31 23:19:30)
2010-01-31 18:22:00.093 VERBOSE ConexantRecorder::StartRecording('AverMedia M150', 1, 1, 3, 1)
2010-01-31 18:22:00.093 VERBOSE target filename: D:\Manual Recordings\test_20100131182200.mpg
2010-01-31 18:22:00.093 VERBOSE Capture Device is based on BlackBird architecture
2010-01-31 18:22:00.093 VERBOSE Capture Device is using Conexant (derived) drivers
2010-01-31 18:22:00.093 VERBOSE Loading filter names
2010-01-31 18:22:00.093 VERBOSE Found names:
2010-01-31 18:22:00.093 VERBOSE AVerMedia AVerTV MPEG Crossbar
2010-01-31 18:22:00.093 VERBOSE AVerMedia AVerTV MPEG Video Capture
2010-01-31 18:22:00.109 VERBOSE AVerMedia AVerTV Tuner
2010-01-31 18:22:00.109 VERBOSE AVerMedia AVerTV TvAudio
2010-01-31 18:22:00.140 VERBOSE ConnectPins: 'Analog Audio' to 'TVAudio In'
2010-01-31 18:22:00.156 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Input1'
2010-01-31 18:22:00.171 VERBOSE Looking for encoder filter
2010-01-31 18:22:00.171 VERBOSE - AVerMedia AVerTV MPEG Encoder
2010-01-31 18:22:00.171 VERBOSE GetMedium(pCapturePin) returns: {72647BEE-5C11-4D39-81DF-EE1D529EBED7}-00050002-00000000
2010-01-31 18:22:00.171 VERBOSE getSetting(AutoDetectEncoderMethod)
2010-01-31 18:22:00.171 VERBOSE About try all encoders until we find one that works...
2010-01-31 18:22:00.171 VERBOSE AVerMedia AVerTV MPEG Encoder
2010-01-31 18:22:00.187 VERBOSE using instance: 1
2010-01-31 18:25:36.171 VERBOSE ConnectPins failed: hr = 80040217
2010-01-31 18:25:36.171 VERBOSE VFW_E_CANNOT_CONNECT
2010-01-31 18:25:36.218 VERBOSE put_Mode(AMTUNER_MODE_TV)
2010-01-31 18:25:36.218 VERBOSE put_CountryCode(1)
2010-01-31 18:25:36.218 VERBOSE put_TuningSpace(1)
2010-01-31 18:25:36.218 VERBOSE put_InputType(0, 1)
2010-01-31 18:25:36.218 VERBOSE put_ConnectInput(0)
2010-01-31 18:25:36.218 VERBOSE put_Channel(3, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)
2010-01-31 18:25:36.453 VERBOSE get_VideoFrequency() returns 61250000
2010-01-31 18:25:36.453 VERBOSE get_CountryCode() returns 1
2010-01-31 18:25:36.453 VERBOSE About to query available formats
2010-01-31 18:25:36.453 VERBOSE Set to MPEG2 width:720 height:480
2010-01-31 18:25:36.453 VERBOSE ConexantRecorder::SetConfigurationDefault()
2010-01-31 18:25:36.453 VERBOSE About to set BITRATE MODE
2010-01-31 18:25:36.453 VERBOSE requesting variable encoding
2010-01-31 18:25:36.468 VERBOSE About to set BITRATE
2010-01-31 18:25:36.468 VERBOSE device minimum bitrate: 2500000
2010-01-31 18:25:36.468 VERBOSE device maximum bitrate: 15000000
2010-01-31 18:25:36.468 VERBOSE device bitrate step size: 400
2010-01-31 18:25:36.468 VERBOSE trying to request bitrate: 8500000
2010-01-31 18:25:36.484 VERBOSE device confirms bitrate as: 8500000
2010-01-31 18:25:36.484 VERBOSE About to set PEAK BITRATE
2010-01-31 18:25:36.484 VERBOSE device minimum peak bitrate: 2500000
2010-01-31 18:25:36.484 VERBOSE device maximum peak bitrate: 15000000
2010-01-31 18:25:36.484 VERBOSE device peak bitrate step size: 400
2010-01-31 18:25:36.484 VERBOSE trying to request peak bitrate: 10000000
2010-01-31 18:25:36.515 VERBOSE device confirms bitrate as: 10000000
2010-01-31 18:25:36.515 VERBOSE getSetting(EnableTeleText)
2010-01-31 18:25:36.593 VERBOSE getSetting(ListGraphFilters)
2010-01-31 18:25:36.593 VERBOSE Graph contains the following filters:
2010-01-31 18:25:36.593 VERBOSE - GB-PVR Writer
2010-01-31 18:25:36.593 VERBOSE - Encoder
2010-01-31 18:25:36.593 VERBOSE - Capture
2010-01-31 18:25:36.593 VERBOSE - AVerMedia AVerTV MPEG Crossbar
2010-01-31 18:25:36.593 VERBOSE - TV Audio
2010-01-31 18:25:36.593 VERBOSE - TV Tuner
2010-01-31 18:25:36.593 VERBOSE getSetting(SaveGraphFiles)
2010-01-31 18:25:36.593 VERBOSE ConexantRecorder::StartRecording() done
2010-01-31 18:26:00.109 VERBOSE ConexantRecorder::StopRecording()
2010-01-31 18:26:00.218 VERBOSE ConexantRecorder:one()

In this particular instance the lag was approximately 3 and a half minutes between
2010-01-31 18:22:00.187 VERBOSE using instance: 1
2010-01-31 18:25:36.171 VERBOSE ConnectPins failed: hr = 80040217
2010-01-31 18:25:36.171 VERBOSE VFW_E_CANNOT_CONNECT
2010-01-31 18:25:36.218 VERBOSE put_Mode(AMTUNER_MODE_TV)

Once the recording starts it is fine. I have tried the card in two machines. Originally a hp XW4100, p4 2.8HT, with a ATI 9550 256mb video card running GBPVR 1.4.7, and later in a HP DX5150, AMD x2, 4400+, ATI HD4350 512mb video card, with the same version of GBPVR, with both machines running XP Pro SP3. Each machine has the latest video drivers and both are up to date with windowns updates.

I also hooked up a vcr to the card's s-video input to see if it was something to do with the tv tuner, set it up to run as a s-video device, and it exhibits the same behavior. The following is part of a log of a 2 hour recording using the s-video connection on the card:
2010-02-14 16:12:00.296 VERBOSE About try all encoders until we find one that works...
2010-02-14 16:12:00.296 VERBOSE AVerMedia AVerTV MPEG Encoder
2010-02-14 16:12:00.296 VERBOSE using instance: 1
2010-02-14 16:15:16.000 VERBOSE ConnectPins failed: hr = 80040217
2010-02-14 16:15:16.000 VERBOSE VFW_E_CANNOT_CONNECT
2010-02-14 16:15:16.062 VERBOSE About to query available formats
2010-02-14 16:15:16.062 VERBOSE Set to MPEG2 width:720 height:480
2010-02-14 16:15:16.062 VERBOSE ConexantRecorder::SetConfigurationDefault()
2010-02-14 16:15:16.062 VERBOSE About to set BITRATE MODE
2010-02-14 16:15:16.062 VERBOSE requesting variable encoding
2010-02-14 16:15:16.078 VERBOSE About to set BITRATE
2010-02-14 16:15:16.078 VERBOSE device minimum bitrate: 2500000
2010-02-14 16:15:16.078 VERBOSE device maximum bitrate: 15000000
2010-02-14 16:15:16.078 VERBOSE device bitrate step size: 400
2010-02-14 16:15:16.078 VERBOSE trying to request bitrate: 8000000
2010-02-14 16:15:16.093 VERBOSE device confirms bitrate as: 8000000
2010-02-14 16:15:16.093 VERBOSE About to set PEAK BITRATE
2010-02-14 16:15:16.093 VERBOSE device minimum peak bitrate: 2500000
2010-02-14 16:15:16.093 VERBOSE device maximum peak bitrate: 15000000
2010-02-14 16:15:16.093 VERBOSE device peak bitrate step size: 400
2010-02-14 16:15:16.093 VERBOSE trying to request peak bitrate: 10000000
2010-02-14 16:15:16.109 VERBOSE device confirms bitrate as: 10000000
2010-02-14 16:15:16.109 VERBOSE getSetting(EnableTeleText)
2010-02-14 16:15:16.187 VERBOSE getSetting(ListGraphFilters)
2010-02-14 16:15:16.187 VERBOSE Graph contains the following filters:
2010-02-14 16:15:16.187 VERBOSE - GB-PVR Writer
2010-02-14 16:15:16.187 VERBOSE - Encoder
2010-02-14 16:15:16.187 VERBOSE - Capture
2010-02-14 16:15:16.187 VERBOSE - AVerMedia AVerTV MPEG Crossbar
2010-02-14 16:15:16.187 VERBOSE getSetting(SaveGraphFiles)
2010-02-14 16:15:16.187 VERBOSE ConexantRecorder::StartRecording() done
2010-02-14 18:12:00.046 VERBOSE ConexantRecorder::StopRecording()
2010-02-14 18:12:00.218 VERBOSE ConexantRecorder:one()

In the above instance the lag is about 3 minutes and 16 seconds. See entries:
2010-02-14 16:12:00.296 VERBOSE using instance: 1
2010-02-14 16:15:16.000 VERBOSE ConnectPins failed: hr = 80040217
2010-02-14 16:15:16.000 VERBOSE VFW_E_CANNOT_CONNECT

I have tried three different sets of drivers for the card, v1.0.5.9. v1.0.5.12, and 1.0.6.14 [all of which appeared to work - other than the lag problem] and even the latest one [which did not work] from avermedia's website 2.1.0.41, with no difference.

Is there something that can be changed in the direct.ini file for this particular card that will get rid of the lag.

I have attached the filtercheck log and a set of logs right after finishing a 3 hour recording via the s-video input to the M150-D card (again there was a delay but after accounting for the delay, the recording was excellent)

[sub]

The big delay looks like it happens when connecting to the device's encoder filter. I can only guess this is some bug in it's drivers. If live tv is working, but recording is failing, this also sounds like something going wrong with the device's encoder filter. Unfortunately I'm not familiar with this device, and not sure what would cause this issue.

[uniontown]

First of all thank you very much for the reply. This program is a work of art and I have th highest respect for you and your continued development of the program. The time lag is only a problem if one wants to record scheduled programs one right after the other which I will often do when recording a sports program, i.e. a basketball game. I often will record the scheduled 2 hour time frame and then an extra half hour time frame in case it runs over (i.e. overtime). Then if it does not I'll delete the extra half hour.
Anyway thank you for your attention to the query and the quick response.

[uniontown]

Inasmuch as Sub has indicated that there is a problem with the drivers, [or the encoder] I was wondering if anyone had drivers that were newer than v1.0.6.14. I have seen on this forum (I think) someone that indicated that they had downloaded v1.0.6.20 from avermedia's global site and they even had the link on the page. The link is dead. If someone could point me in the right direction or post them somewhere. The earlier versions have an exe file in them "installdriver.exe" and consequently are difficult to e-mail [at least I have difficulty in emailing anything with a executable file in it].
I am also wondering if anyone has had some success using the card [avermedia M150-D] and if so what did you do to make it work up to what one might call normal. (e.g. no time lag on recording]

[uniontown]

Finally found the v1.0.6.20 driver for the M150 card, but it [like the earlier drivers] did not solve the delay-lag on recording alluded to above. I realize that this is an old card, but surely the guru's that use gbpvr have found a way to make it function properly. Please, share your expertise and wisdom for all the world to know.

[Jaggy]

I'm not sure if the revision "-D" is the same as mine but I have been running M150's for years without any lag (I know of) when starting to record, the only problem I had was early on when I found the later drivers I was running were giving me "timestamp" issues like the analogue Hauppauge cards of the time were suffering from so I rolled back to the drivers that were supplied when I purchased the cards & thankfully that problem disappeared.

I have just checked & they are 1.0.6.12 dated 20-01-2005 I am running XPSp2 on my server.

[uniontown]

The driver that I loaded last night is version 1.0.6.20 dated 11-24-2005. As previousloy stated I have tried now foiur different sets of drivers for the card, v1.0.5.9. v1.0.5.12, and 1.0.6.14 They all exhibit the same behavior. I have not been able to locate 1.0.6.12 that you mention.
I am beginning to think that it is something else, [other than the driver] but given my limited knowledge it is beyond my capabilities to figure it out. Could you zip up you log that shows the encoder pin connecting. Just curious to see it working and see if there is something different. [the recordingservice.exe-native.log]

[Jaggy]

Log attached

[uniontown]

This is really interesting: your log shows:
2010-02-20 17:15:15.992 VERBOSE Looking for encoder filter
2010-02-20 17:15:16.012 VERBOSE - AVerMedia AVerTV MPEG Encoder
2010-02-20 17:15:16.693 VERBOSE GetMedium(pCapturePin) returns: {72647BEE-5C11-4D39-81DF-EE1D529EBED7}-00000005-00000000
2010-02-20 17:15:16.693 VERBOSE getSetting(AutoDetectEncoderMethod)
2010-02-20 17:15:16.693 VERBOSE About try all encoders until we find one that works...
2010-02-20 17:15:16.693 VERBOSE AVerMedia AVerTV MPEG Encoder
2010-02-20 17:15:16.723 VERBOSE using instance: 1
2010-02-20 17:15:16.733 VERBOSE ConnectPins failed: hr = 80040217
2010-02-20 17:15:16.733 VERBOSE VFW_E_CANNOT_CONNECT
2010-02-20 17:15:16.843 VERBOSE put_Mode(AMTUNER_MODE_TV)
2010-02-20 17:15:16.843 VERBOSE put_CountryCode(64)
2010-02-20 17:15:16.843 VERBOSE put_TuningSpace(64)
2010-02-20 17:15:16.843 VERBOSE put_InputType(0, 0)
2010-02-20 17:15:16.843 VERBOSE put_ConnectInput(0)
2010-02-20 17:15:16.843 VERBOSE put_Channel(76, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)

My log shows:

2010-01-31 18:22:00.171 VERBOSE Looking for encoder filter
2010-01-31 18:22:00.171 VERBOSE - AVerMedia AVerTV MPEG Encoder
2010-01-31 18:22:00.171 VERBOSE GetMedium(pCapturePin) returns: {72647BEE-5C11-4D39-81DF-EE1D529EBED7}-00050002-00000000
2010-01-31 18:22:00.171 VERBOSE getSetting(AutoDetectEncoderMethod)
2010-01-31 18:22:00.171 VERBOSE About try all encoders until we find one that works...
2010-01-31 18:22:00.171 VERBOSE AVerMedia AVerTV MPEG Encoder
2010-01-31 18:22:00.187 VERBOSE using instance: 1
2010-01-31 18:25:36.171 VERBOSE ConnectPins failed: hr = 80040217
2010-01-31 18:25:36.171 VERBOSE VFW_E_CANNOT_CONNECT
2010-01-31 18:25:36.218 VERBOSE put_Mode(AMTUNER_MODE_TV)
2010-01-31 18:25:36.218 VERBOSE put_CountryCode(1)
2010-01-31 18:25:36.218 VERBOSE put_TuningSpace(1)
2010-01-31 18:25:36.218 VERBOSE put_InputType(0, 1)
2010-01-31 18:25:36.218 VERBOSE put_ConnectInput(0)
2010-01-31 18:25:36.218 VERBOSE put_Channel(3, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)

You have the same entry that the connect pin failed at 17:15:16 but your configuration only takes 1 millisecond to fail and thereafter moves right along [to connect] whereas my configuration takes 3 minutes and 36 seconds to fail before it moves along and eventually connects.
Thank you for the post of the logs, you are a good person!

[uniontown]

Reloaded xp pro sp3, and started from scratch with the M150-D version 1.0.6.20 drivers and now I do not have a delay the relevant entries are now:

2010-02-20 20:36:19.796 VERBOSE Looking for encoder filter
2010-02-20 20:36:19.796 VERBOSE - AVerMedia AVerTV MPEG Encoder
2010-02-20 20:36:19.796 VERBOSE GetMedium(pCapturePin) returns: {72647BEE-5C11-4D39-81DF-EE1D529EBED7}-00030005-00000000
2010-02-20 20:36:19.796 VERBOSE getSetting(AutoDetectEncoderMethod)
2010-02-20 20:36:19.796 VERBOSE About try all encoders until we find one that works...
2010-02-20 20:36:19.796 VERBOSE AVerMedia AVerTV MPEG Encoder
2010-02-20 20:36:19.812 VERBOSE using instance: 1
2010-02-20 20:36:20.453 VERBOSE ConnectPins failed: hr = 80040217
2010-02-20 20:36:20.453 VERBOSE VFW_E_CANNOT_CONNECT
2010-02-20 20:36:20.468 VERBOSE About to query available formats

The encoder appears to fail to connect, but now it moves along [appears to be within a half a second] and connects and records without the long lag. No Idea why it works now. I have had so many different cards in the machine, maybe there was some kind of a leftover driver conflict.