Am 17.04.2014 22:28, schrieb Ville Skyttä: > On Thu, Apr 17, 2014 at 6:57 PM, Alexander Kniwel > <vdr-mailinglist@xxxxxxxxxx> wrote: >> Hi, >> >> I had exactly the same errors on my VDR (2.1.6): >> >> ERROR: invalid sat cable number in '°$Q‘ >> >> In my case the „binary junk“ is always °$Q, and the message appears also in a 30 min interval. >> >> After deactivating/removing the naludump patch, I can’t find the messages in the logs anymore. But this is just a guess and I don’t know if this is really related…. > > Bingo, same thing here. Rebuilding VDR without the NALU dump patch > gets rid of the error -- if the patch is in, it doesn't seem to make a > difference if it's enabled in settings or not, the error is always > there in syslog. Cc'ing patch author (@Udo: see below). Hmmm, thats weired. I don't have such errors on my system, and even more strange, minimizing risks was one of the design goals of the patch, thats why the nalu filter is right before the disk writer, thus without an ongoing recording, the patch does nothing. The filter itself also makes sure that no data can be accidentally dropped, by only dropping TS packets that only contain FF bytes and only within nalu fill packets. Is this the original patch from my website? ( http://www.udo-richter.de/vdr/naludump.html ) Are there any hints that this behavior started with a certain VDR version? Ok, some leaning out of the window: The patch adds an entry to config.h. The message origins from the config.h string DeviceBondings. Maybe not all parts of VDR (or plugins) were compiled against the patched config.h? This would cause an mis-aligned access to the string. Cheers, Udo PS: Unfortunately, I'm offline for two weeks, starting Friday. _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
