2011-12-13, 17:34
291M if that goes over 300M, oomkiller will reach out and cause the dreaded Level 3 Out of Memory
davilla Wrote:It's not a bit-rate issue. It's a memory usage issue.
Memphiz Wrote:The magic 300M limit somehow remembers me on Apollo 13, where they need to figure out in which order they activate the devices for not hitting the magic 20A current
davilla Wrote:It's not a bit-rate issue. It's a memory usage issue.
davilla Wrote:291M if that goes over 300M, oomkiller will reach out and cause the dreaded Level 3 Out of Memory
Jester Wrote:I'm no dev, but have a linux background, isn't oomadj -> OOM_DISABLE an option ?
canadave Wrote:For the ignorant among us (such as myself), what aspects of a video file affect memory usage during playback, such as in this case? Pure file size? Capital letters in the title?
Is there any way to take a video file that is a mem usage hog and turn it into a mem usage harmless piglet without a drastic reduction in quality?
davilla Wrote:H264 level/profile will effect mem usage, indirectly that's the number of reference frames. This particular video has 2. The other things are audio. This particular video is a 7 channel DTS-xxx.
Jester Wrote:To answer to my own question (I think), I'm not a apple dev person, no clue about iOS
so, normally in linux you can "bypass" our dear friend oomkiller by doing
echo -17 > /proc/$PID/oom_adj
where $PID is the PID of the AppleTV process
or using sysctl
vm.overcommit_memory = 2
vm.overcommit_ratio = 50
both don't seem to be an option.
canadave Wrote:Oh, okay, thanks. Good to know. And yeah, I can see how a 7-channel DTS audio stream might be problematic
Sarlic Wrote:So is dumbing down my files the only thing I can really do here? Or staying put with the Cydia version (which currently has scraping issues and I don't think works with MySQL.)