timeshift record problem

#1
I have a problem with the recording function. The problem is that I can not obtain a synchronous registration when i move backwards the cursor in the timeshift bar, although the "Synchronous record" mode is enabled.
Is it only my problem? I use ProgDVB 4.91 - ProgDVB 4.85.3 and earlier are OK. Why?
Thank you.

Re: .

#3
Prog wrote:Sorry I am not good undarstand this.
What is "synchronous registration " ?
Please click on the clock icon placed at the bottom-right of the program window...

#5
No answer? So, I put the question in a different way: what's the use of the "Synchronous recording" option in the "timeshift buffer status"?

#6
AFAIK, you can select recording either from input (direct) or output (delayed) of the timeshift buffer.
My signature:

Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!



I don't give support by e-mail or PM.

And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!

NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.

Please keep it in English here, or Russian in the Russian section, or German in the German section.

I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!


1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode

19.2°,13°,28.x°E,30°W, DiSEqC 1.0


Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>

#7
Thanks for the answer.
The problem is that the [start-end] time of the recorded file is not accurate, if I use the timeshift.
To better understand what I mean please do this test (whith "synchronous record" on):
-start ProgDVB
-wait 1-2 min. for the filling of the buffer
-put back the cursor of the timeshift (to the start or in the middle, it's doesn't care)
-now try to record a 30 sec. TV spot.
Close the program and watch the 30 sec. recorded file. Does it correspond to what you tried to record? In my case, the answer is no.

#9
When not using timeshift, ProgDVB records pretty precise.
Then, cutting with an external application is not really hard. I am always recording several minutes before and after an event, to be able, to cut perfect later on.

However, if you are watching over timeshift, you will always have to wait until the buffer minimum is filled.
If you want to record from the shifted signal, it's highly recommended, to provide a second physical HDD (not just partition), to place either the timeshift file or the recording on. Else your disk will be extremely busy, resulting in a lot of possible trouble.
If using timeshift in RAM, you MUST have pretty much of that, to 100% avoid swap file use.
My signature:

Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!



I don't give support by e-mail or PM.

And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!

NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.

Please keep it in English here, or Russian in the Russian section, or German in the German section.

I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!


1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode

19.2°,13°,28.x°E,30°W, DiSEqC 1.0


Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>

#10
I always use timeshift in RAM, this is more efficient and the HDD is not busy for this function.
@ Prog: I don't require editing features, only a good working recording feature.
Since ProgDVB offers recording features, I'd like it were the most accurate possible.
I don't understand why recording during timeshift view has not the same precision of recording in direct view.
In my opinion this problem could be fixed working on the code of ProgDVB. Is it possible?

note: In ProgDVB 4.xx ther's an error in the "timeshift buffer status": in the word synch_onous the "r" is missing.