by schn4rk » Thu May 03, 2012 8:31 am
$this->bbcode_second_pass_quote('kmihelich', 'R')emember to consider dates and versions when you quote other information. The current version in the repositories is 1.0.24, not 1.0.21.
Indeed. I guess the question I was stuck on related more to the second patch I linked to, because I wasn't immediately sure whether it had been brought over into the mainline code. But it's something I could have (and still intend to) confirm by examining the current code more closely.
Sorry for getting so carried away with speculation!
$this->bbcode_second_pass_quote('kmihelich', 'N')ow for some real and anecdotal points before this thread gets too out of control on speculation. There doesn't appear to be any memory issues, otherwise the minidlna server that has been running on my PPv4 for over a month would be using more than 3.4% RAM. The DLNA client matters 100%, however. Most companies don't fully implement support, do a poor job of it, or have a limited selection of codecs which themselves may have issues. Samsung has been a well-noted offender, and Sony just does their own thing, they always have. Using DLNA, you're streaming the content as-is, so it is up to the client device to deal with the content on its own terms. If you've verified there are no networking issues either with physical connections or the capability of your equipment to handle sustained transfers among other network traffic, you really have only two places left to look. Either the client device can't handle it, or you're absolutely demolishing the plug with some other process(es). The latter is hard to accomplish though, as I can still compile and compress archives on the PPv4 while streaming 1080p material.
The PPv4 anecdotal info is really valuable, especially coming from you! So, thanks. Indeed, I can typically install a new package while streaming HD video (720p as I tend not to bother with 1080p much, personally). I guess that's why the possibility of a memory leak issue sparked my interest, because typically I don't experience issues until I have been streaming stuff for a little while in one session, so to speak.
Still, the point about how much the client matters does resonate with me. I know my Philips player can decode everything I've been trying to play, but I also know that it is not really an optimal DLNA client, insofaras it can't do things like subtitles over DLNA, even though it can handle them from an attached drive. I've poked around the Philips forums, and one of their devs has straight out said that this is because the DLNA standard doesn't support that at this stage. I know that's a half-truth at best, so it doesn't fill me with confidence about the quality of their client overall. For all I know, it could be a hardware issue with the player, too.
On the other hand, I still feel like it might be worth my time to investigate further the possibility of patching minidlna to cater to whatever quirks the Philips player has. I know this has happened with other brands of client, but obviously the Philips isn't very popular, so I might be on my own with this. That's fine though, it's part of the fun of rolling your own solution, isn't it?

I'll refrain from posting more speculation here, but if I find anything solid and relevant I will share it.
Finally - I am running my v4 from SATA also, so I'm pretty confident that's not the issue, but that's a really good point.