search

schasan / androvdr

Automatically exported from code.google.com/p/androvdr
0 stars 0 forks source link

record parsing must be adopted for vdr >1.7.20 #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. updating vdr to newest version
2. each recording is preceeded by record length(+new recording mark)

What is the expected output? What do you see instead?
- now you get 1 entry for each existing record length 
(grouped below are the recordings with corresponding length)
- device should get a checkbox for "new version" enabling new parsing method
- see screenshots

What version of the product are you using? On what operating system?
- 1.4.2 with G2VDR3 (vdr 1.7.21 from 2011/09/04)

Please provide any additional information below.
- The Recordings menu now displays the length (in hours:minutes) of each 
recording
  (thanks to Rolf Ahrenberg). Note that the "new" indicator has been moved from the
  recording time to the length column. This new format is also used by the SVDRP
  command LSTR, so in case you have an application that parses the LSTR output,
  you will need to adjust it to the new format.

Original issue reported on code.google.com by grrr...@gmail.com on 26 Nov 2011 at 11:39

Attachments:

GoogleCodeExporter commented 9 years ago 
...the way it should look (corrected in vdradmin-am 3.6.9)...

Original comment by grrr...@gmail.com on 26 Nov 2011 at 11:43

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed in version 1.4.3

Original comment by andro...@googlemail.com on 31 Dec 2011 at 12:22