This repository was archived by the owner on May 8, 2022. It is now read-only.
forked from winguru/xTeVe
-
Notifications
You must be signed in to change notification settings - Fork 8
Store buffer in memory (instead of writing to disk) #30
Labels
enhancement
New feature or request
Comments
It would be better to determine the root cause, but until we figure it out ... yet another checkbox will never hurt 😉 |
@SCP002, dude! do you not have a day job? I hadn't even had time to look at how this should be implemented, and you already did it. |
@joshjryan Kind of 😅 Will make a new release in, <= 2 hours from now, just need a small break 🙂 |
I just pulled your changes down and built it...I'll keep an eye on memory usage to see if anything is leaking. |
@joshjryan Here is the "official" 🙃 build ready already. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
My clients buffer more often than I'd expect, when using the xTeVe (and ffmpeg and VLC) buffer. I'm not exactly sure what's causing it, but looking at how much is written and read from disk is interesting.
Describe the solution you'd like
Might it be better to store the buffer in memory, instead of all the writes/reads to the temp directory?
Describe alternatives you've considered
N/A
Additional context
I just want to get some input on this thought. Feel free to let me know what you think.
The text was updated successfully, but these errors were encountered: