> Hello,
>
> cutting a TS recording, where two cut points are joined, always leads to
> some artifacts at this join when playing the cutted result.
This is not a new issue and is true for all types of recordings.
Not far ago I did some test on encoding quite old vdr-recordings (saved uncut)
wit
Hello,
cutting a TS recording, where two cut points are joined, always leads to
some artifacts at this join when playing the cutted result.
When VDR cuts only at I-Frames, shouldn't the cut point be unnoticeable in
the output?
Checking the cutted result with TS-Doctor shows a bunch of errors, wh
On 25/01/2012 14:59, Tobi wrote:
On 25.01.2012 13:24, Tobi wrote:
Did this now. The info file says 25 fps, the index files is 179512 bytes
big, VDR says the recording is 15min long, but the recording was 10
minutes.
TSDoctor says 25fps interlaced and gives a length of 09:47
Tobias
Sorry to in
On 25.01.2012 13:24, Tobi wrote:
> Did this now. The info file says 25 fps, the index files is 179512 bytes
> big, VDR says the recording is 15min long, but the recording was 10
> minutes.
TSDoctor says 25fps interlaced and gives a length of 09:47
Tobias
___
On Wednesday 25 January 2012 10:29:16 Klaus Schmidinger wrote:
> On 17.01.2012 14:26, sundararaj reel wrote:
> > Hi,
> >
> > I am attaching a patch for vdr 1.7.23 for the problem described here:
> > http://www.vdr-portal.de/board1-news/board2-vdr-news/p1047199-announce-vdr-developer-version-1-7-23/
On 24.01.2012 10:40, Klaus Schmidinger wrote:
> Does this also happen if you make a recording directly with VDR 1.7.22?
Did this now. The info file says 25 fps, the index files is 179512 bytes
big, VDR says the recording is 15min long, but the recording was 10
minutes. The raughly calculated fram
On 17.01.2012 14:26, sundararaj reel wrote:
Hi,
I am attaching a patch for vdr 1.7.23 for the problem described here:
http://www.vdr-portal.de/board1-news/board2-vdr-news/p1047199-announce-vdr-developer-version-1-7-23/#post1047199
There appears to be a problem in listing recordings due to a bug
