PLEASE NOTE : These are the Community Forums (user-to-user), the Hauppauge team try to assist as
time allows. Please use the email or telephone support if necessary as their tickets
have priority!
-
Release 2.4d seems to have screwed up the Tuner occupied status
Release 2.4d seems to have screwed up the Tuner occupied status again. I'm getting failed recordings from time to time. I also experienced this with 2.4c too.
Release 2.4b was the last time I got perfect recordings. I remember before 2.4b, there was also a time the Tuner occupied status was not properly implemented.
Please fix this urgent problem cos missing recordings means missing programmes to watch. This is exasperating especially for episodic programmes.
...
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
can you post the logs showing the issue? What tuners do you have? What programme was missed? On which source? Can you give me a step by step idea of the issue?
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status

Originally Posted by
Mr X
can you post the logs showing the issue? What tuners do you have? What programme was missed? On which source? Can you give me a step by step idea of the issue?
Ok I will try to provide the logs the next time this occurs. But I really can't afford the time to test it out, and will be reverting to 2.4b after tonight.
As for the rest of your questions:
2 x HVR2200
Regular Daily/Weekly programmes (input manually, cos they are analog PAL)
PAL analog source
Step by step? How about it just failed? I dun understand why there would be step-by-step.
...
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
Anyway I have a feeling that the problem might also be due to the drivers which are Hauppauge-signed and not Microsoft-signed for the previous versions.
I know my reporting isn't very scientific, but still it could be a direction to look into.
Thanks.
...
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
I just don't understand your exact issue thats the point. When does it not record? What are the exact circumstances? I need a decription like this example:
a) Schedule a recording from 5pm - 6pm
b) Schedule a recording from 5.15pm - 6pm.
c) The 5.15pm recording fails.
This would allow us to try and reproduce your issue, as I'm not aware of any such issue that you mention.
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
Have you tried installing the drivers from 2.4b and then the latest application?

Originally Posted by
Kiwi
Anyway I have a feeling that the problem might also be due to the drivers which are Hauppauge-signed and not Microsoft-signed for the previous versions.
I know my reporting isn't very scientific, but still it could be a direction to look into.
Thanks.
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status

Originally Posted by
Mr X
I just don't understand your exact issue thats the point. When does it not record? What are the exact circumstances? I need a decription like this example:
a) Schedule a recording from 5pm - 6pm
b) Schedule a recording from 5.15pm - 6pm.
c) The 5.15pm recording fails.
This would allow us to try and reproduce your issue, as I'm not aware of any such issue that you mention.
I see.... will try to provide this information when the next failed recording comes up.
...
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
Might be unrelated and when I find these faults I don't know that I have the logs of exactly what went wrong. A number of recordings don't happen and some are stopping before the time declared to have bee recorded, so I get a file 20 mins not an hour. This one didn't record. Bags of space on the hard drive (over 180Gb), local drive. Earlier and later recordings okay. Previous day recording on same channel okay. {WinTV 2.4c}
2011-11-06 02:58:01.446 [DEBUG][1] Arguments:
2011-11-06 02:58:01.447 [DEBUG][1] -id:49261
2011-11-06 02:58:01.463 [DEBUG][1] Installed ADO.NET Provider: System.Data.Odbc.OdbcFactory
2011-11-06 02:58:01.463 [DEBUG][1] Installed ADO.NET Provider: System.Data.OleDb.OleDbFactory
2011-11-06 02:58:01.463 [DEBUG][1] ...using System.Data.OleDb.OleDbFactory
2011-11-06 02:58:01.498 [DEBUG][1] Recording duration is 7438 seconds
2011-11-06 02:58:01.559 [INFO][1] Channel Name: CBS Drama
2011-11-06 02:58:01.559 [INFO][1] Filename: E:\VideoTV\Moonlighting_20111106_0258.ts
2011-11-06 02:58:06.539 [INFO][1] About to start recording...
2011-11-06 02:58:11.539 [INFO][1] Starting recording...
2011-11-06 02:58:11.542 [DEBUG][1] TVServicesHelper::Initialise()@1
2011-11-06 02:58:11.545 [DEBUG][1] TVServicesHelper::Initialise()@2
2011-11-06 02:58:11.549 [DEBUG][1] TVServicesHelper::Initialise()@3
2011-11-06 02:58:11.550 [DEBUG][1] TVServicesHelper::Initialise()@4
2011-11-06 02:58:11.552 [DEBUG][1] TVServicesHelper::Initialise() complete
2011-11-06 02:58:17.615 [DEBUG][1] Doing second chance start of recording
2011-11-06 02:58:18.900 [ERROR][1] Unable to set database filename to: E:\VideoTV\Moonlighting_20111106_0258.ts (file doesnt exist on disk)
2011-11-06 02:58:18.900 [INFO][1] Started
2011-11-06 02:58:18.902 [DEBUG][1] No stream...
2011-11-06 02:58:18.902 [DEBUG][1] No stream...
2011-11-06 02:58:18.902 [DEBUG][1] No stream...
2011-11-06 02:58:21.538 [DEBUG][1] No stream...
2011-11-06 02:58:26.539 [DEBUG][1] No stream...
2011-11-06 02:58:31.540 [DEBUG][1] No stream...
2011-11-06 02:58:36.541 [DEBUG][1] No stream...
2011-11-06 02:58:41.542 [DEBUG][1] No stream...
2011-11-06 02:58:46.543 [DEBUG][1] No stream...
2011-11-06 02:58:51.544 [DEBUG][1] No stream...
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
In that particular log it attempted to start the recording at the requested time, but no device was available. ie, either it was in use for some other purpose (like streaming to an extend client), or the device wasnt plugged in at time the recording tried to start.
-
Re: Release 2.4d seems to have screwed up the Tuner occupied status
The card is a 4000 - and the computer was running with it plugged in. I don't stream - I don't know how to do that.
Here is another log where it terminated for no apparent reason
2011-10-31 08:58:10.085 [DEBUG][1] Arguments:
2011-10-31 08:58:10.090 [DEBUG][1] -id:38997
2011-10-31 08:58:10.119 [DEBUG][1] Installed ADO.NET Provider: System.Data.Odbc.OdbcFactory
2011-10-31 08:58:10.119 [DEBUG][1] Installed ADO.NET Provider: System.Data.OleDb.OleDbFactory
2011-10-31 08:58:10.119 [DEBUG][1] ...using System.Data.OleDb.OleDbFactory
2011-10-31 08:58:10.176 [DEBUG][1] Recording duration is 3829 seconds
2011-10-31 08:58:10.348 [INFO][1] Channel Name: horror channel
2011-10-31 08:58:10.348 [INFO][1] Filename: E:\VideoTV\War_of_the_Worlds_20111031_0858.ts
2011-10-31 08:58:15.321 [INFO][1] About to start recording...
2011-10-31 08:58:15.326 [INFO][1] Starting recording...
2011-10-31 08:58:15.352 [DEBUG][1] TVServicesHelper::Initialise()@1
2011-10-31 08:58:15.439 [DEBUG][1] TVServicesHelper::Initialise()@2
2011-10-31 08:58:15.640 [DEBUG][1] TVServicesHelper::Initialise()@3
2011-10-31 08:58:15.641 [DEBUG][1] TVServicesHelper::Initialise()@4
2011-10-31 08:58:15.649 [DEBUG][1] TVServicesHelper::Initialise() complete
2011-10-31 08:58:22.937 [DEBUG][1] RenewLease() ok
2011-10-31 08:58:22.938 [INFO][1] Set database filename to: E:\VideoTV\War_of_the_Worlds_20111031_0858.ts
2011-10-31 08:58:23.313 [DEBUG][1] ScheduledRecording updated
2011-10-31 08:58:23.313 [INFO][1] Started
2011-10-31 08:58:23.313 [DEBUG][1] RenewLease() ok
2011-10-31 08:58:23.313 [DEBUG][1] RenewLease() ok
...
2011-10-31 09:44:47.254 [INFO][1] File size: 834144720
2011-10-31 09:44:50.252 [DEBUG][1] RenewLease() ok
2011-10-31 09:44:55.637 [DEBUG][1] RenewLease() ok
2011-10-31 09:45:00.262 [DEBUG][1] RenewLease() ok
2011-10-31 09:45:56.309 [DEBUG][1] RenewLease() failed
2011-10-31 09:46:51.924 [DEBUG][1] Device now used for: ,,,
2011-10-31 09:46:52.901 [DEBUG][1] RenewLease() failed
2011-10-31 09:47:07.428 [DEBUG][1] Updating recording to set status to 'completed' in pre-stop
2011-10-31 09:47:45.809 [DEBUG][1] Recording finished prior to scheduled completion time. (cancelled)
2011-10-31 09:47:58.819 [DEBUG][1] About to stop recording
2011-10-31 09:47:59.121 [DEBUG][1] Recording stopped
2011-10-31 09:47:59.121 [DEBUG][1] Stopping device
2011-10-31 09:48:04.395 [DEBUG][1] Updating recording to set status to 'completed'
2011-10-31 09:48:05.498 [DEBUG][1] (1)no conversion configured
2011-10-31 09:48:05.498 [INFO][1] File size: 838598816
2011-10-31 09:48:06.660 [INFO][1] Final file size: 838598816
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules