Something like a 250.000 paquet queue should let you fill up a 24 GB buffer (leaving a bit of RAM for the other apps ). I just did a test again: with a 25 Mbps UHD mkv, you need a ~20.000 paquet queue for a 2 GB buffer (which already holds 10 minutes of material), and it takes just 30 seconds of playback for MPC-HC to fill it up (from local HDD). The settings are not opaque at all as they were described in detail the last time we discussed it:Įven just the tooltips in LAV config are pretty self-explanatory.īasically: set Maximum Queue Memory to the max RAM you want to use for buffering, then use the highest bitrate (and feature-length playtime) file you have to test while increasing Maximum Queue Packets until the player process uses up that amount of RAM. opaque about how they actually impact cache size (I'm not sure they are limitless and I'm not sure how the two values interact among each other in order to define cache size, if there's clear documentation I must have missed it).
Your reply was thorough and I surely don't want LAV to remove features. This is just "academic" curiosity, by the way. Maybe LAV needs to check for that and Kodi doesn't?
MEDIASHOUT TIME AND DATE ERROR MOVIE
how are the multiple versions of a movie inside a single file called). Could that have to do with (lack of) MKV branching support (editions. The only thing I don't understand is why, apparently, Kodi's internal VideoPlayer is generating less requests. I have already optimized LAV to avoid seeks during straight playback, so that after it was opened and probed, it will play it straight through from start to finish in one request - however seek requests during startup cannot really be avoided without removing features. Over HTTP, a seek is a new request, so depending on the exact file structure, this could be a few requests. When launching MediaShout 7, you will always come up to the Launch Screen. If you have a language you would prefer to see the program in, please let us know.
MEDIASHOUT TIME AND DATE ERROR MP4
Opening a file and reading its headers involves a number of seeks - in particular with MKV files (and also MP4 files), because they contain header information both in the beginning, and at the end of the file. Currently, only English is available with plans to include Spanish, French, German, Portuguese, and Chinese at a later date. Hoping that sooner or later an interested coder might look into it. Unfortunately I'm not a coder, I'm investigating this only to understand what would theoretically would be possible. If all of the above doesn't make sense, I'm sorry. In the second case, do you see that part of your work moving upstream to FFMPEG main codebase (as Kodi is based on that too)? Is this correct? Is this info coming from regular FFMPEG or is it your work. Which leads me to my question: if I understand things correctly, madVR "counts" on LAV Filters to pass on relevant info for proper HDR playback. While inquiring about the possibility of madVR as a binary add-on for Kodi, I got this answer from what used to be the main Kodi videoplayer coder.Īt least from a theoretical point of view, it appears that having madVR as an "external" video renderer could be doable. Hi nevcariel, I'm trying to understand what the best road to bring madVR to Kodi, now that the DSPlayer fork seems to be dead for the foreseeable future.