Hi everyone,
I'm using progdvb 6.63.5 under win XP SP3 but already had the problem with previous versions.
I have problems with the end time of some records.
Typically, the last record I have done was scheduled to end at 0h30 and actually ended at 22h30.
I was wondering if it could not be a problem with summer time, or time zone (I live in France)...
Thanks in advance.
ArnaudN
Re: Record duration problem
#3I have not exactly checked for the previous too short records but I think yes.
By the way, I can say that if the record end time is after 1h00 or 2h00 (to be confirmed) (I can make tests next night) the record is OK.
By the way, I can say that if the record end time is after 1h00 or 2h00 (to be confirmed) (I can make tests next night) the record is OK.
Re: Record duration problem
#4In case it would help, the scheduler options are :
- Use microsoft scheduler to start progdvb
- sleep timer disabled.
But my records are done while progdvb is running.
Records options are: no option checked.
- Use microsoft scheduler to start progdvb
- sleep timer disabled.
But my records are done while progdvb is running.
Records options are: no option checked.
Re: Record duration problem
#5I did several recording tests to try to have a better description of the problem:
- With 6.63.5 : recording ending after 2.00
- With 6.63.5 : recording ending between 1.00 and 2.00
- With 6.63.6 : recording ending between 0.00 and 1.00
All these recordings ended at the right time and had the right length.
Maybe the previous wrong recordings were due to bad quality signal...
- With 6.63.5 : recording ending after 2.00
- With 6.63.5 : recording ending between 1.00 and 2.00
- With 6.63.6 : recording ending between 0.00 and 1.00
All these recordings ended at the right time and had the right length.
Maybe the previous wrong recordings were due to bad quality signal...
Re: Record duration problem
#7Hi everyone,
I think I have found the cause for the short records.
I have seen that when the progvdvb engine restarts (message in the status line), the record stops!
Don't you think that it should not ?
I understand that the record should be stopped while the engine restarts, but maybe it could be possible to restart the record in a new file, with an index, or something...
Anything would be better than nothing.
I think I have found the cause for the short records.
I have seen that when the progvdvb engine restarts (message in the status line), the record stops!
Don't you think that it should not ?
I understand that the record should be stopped while the engine restarts, but maybe it could be possible to restart the record in a new file, with an index, or something...
Anything would be better than nothing.
Re: Record duration problem
#81. Please start with /EngineLog send send me two files ProgDVBEngine*.log.
2. You can disable stability mode for fix that.
2. You can disable stability mode for fix that.
Re: Record duration problem
#9OK, here are the logfiles.
The engine has restarted at 20h35'29"
What is the impact of disabling the stability mode on the records ? (glitch in the file ? sound/image desynchronisation ? ... )
The engine has restarted at 20h35'29"
What is the impact of disabling the stability mode on the records ? (glitch in the file ? sound/image desynchronisation ? ... )
- Attachments
-
- ProgDVB.zip
- Logfiles
- (141.13 KiB) Downloaded 354 times
Re: Record duration problem
#10No restarting engine...
ps: My log too bad for this situation. I try more tests on my PC.
ps: My log too bad for this situation. I try more tests on my PC.
Re: Record duration problem
#13I have already done 3 records with 6.63.07 and turned off stability mode.
Two out of them ended normally and the third one ended after about 9 minutes.
Two out of them ended normally and the third one ended after about 9 minutes.
Re: Record duration problem
#15I have installed 6.63.8 in stability mode.
I have scheduled a 2h30 record which stopped after about 11 minutes.
I'm using a USB pinnacle PCTV 320e, in case it helps...
I have scheduled a 2h30 record which stopped after about 11 minutes.
I'm using a USB pinnacle PCTV 320e, in case it helps...