Hi list,
I've uploaded the final patch version of the h.264 NALU fill removal for VDR 1.7.16.
The patch deletes NALU fill data from h.264 streams while recording. The overall stream structure isn't modified, only complete TS packets of NALU fill data are dropped. On HD TV channels that use fixed video bandwidth, this can save 40-60% file size without loosing any data.
The patch must be enabled at settings -> recordings, and can be activated/deactivated individually for each recording by adding the keyword NALUDUMP or NALUKEEP to the recording name.
Also available is the standalone tool that processes ts files. The new version uses the same buffering as the patch, and should otherwise produce identical output compared to the 0.0.1 tool.
Get it at: http://www.udo-richter.de/vdr/naludump.html (de) http://www.udo-richter.de/vdr/naludump.en.html (en)
Cheers,
Udo
On 20.02.11 21:31, Udo Richter wrote:
I've uploaded the final patch version of the h.264 NALU fill removal for VDR 1.7.16.
which config parameter I must set in the setup.conf to enable this patch? (I have no video output on my recording machine, so OSD is not working)
Thanks, Matthias
Am 22.03.2011 09:16, schrieb Matthias Fechner:
On 20.02.11 21:31, Udo Richter wrote:
I've uploaded the final patch version of the h.264 NALU fill removal for VDR 1.7.16.
which config parameter I must set in the setup.conf to enable this patch? (I have no video output on my recording machine, so OSD is not working)
The setup.conf option is DumpNaluFill=0 or 1.
However I'd suggest you should run your VDR with something like skincurses in a screen session, or some other remote controlling system, so you have at least some control over the menu. Makes things a lot easier.
Cheers,
Udo
On 22.03.11 21:03, Udo Richter wrote:
The setup.conf option is DumpNaluFill=0 or 1.
thanks, I will give it a test phase.
One question here, if I shrink already existing recordings with the command line tool, is it necessary to delete the index?
However I'd suggest you should run your VDR with something like skincurses in a screen session, or some other remote controlling system, so you have at least some control over the menu. Makes things a lot easier.
yes, good idea, but it works and I have currently no time to fiddle around with changes on the system :)
Matthias
Am 23.03.2011 07:58, schrieb Matthias Fechner:
One question here, if I shrink already existing recordings with the command line tool, is it necessary to delete the index?
The command line tool just processes a single .ts file. You have to process each file of the recording, and you have to regenerate (delete) the index file.
There's a sample script at VDR Portal that automates this.
Cheers,
Udo
On Wed, Mar 23, 2011 at 2:37 PM, Udo Richter udo_richter@gmx.de wrote:
One question here, if I shrink already existing recordings with the command line tool, is it necessary to delete the index?
The command line tool just processes a single .ts file. You have to process each file of the recording, and you have to regenerate (delete) the index file.
I was interested to see how your patch works but after running the command line tool on a few recordings, none of them shrunk so I can only assume that my provider doesn't include such fill data. I like the idea however and appreciate your time in developing it.
There's a sample script at VDR Portal that automates this.
It may be wise to post that script along with your next patch update. There are a lot of NA users who have trouble trying (and consequently stop) to navigate german-based vdr portal.
Best regards
-
Matthias Fechner -
Udo Richter -
VDR User