In theory, yes. In practice, no. ffmpeg has a flag
+discardcorrupt
set by default to remove corrupt packets from the stream. If you're getting a lot of corrupt packets that might signify an issue with your connection to the stream.Nope, that's fine - this is due to ffmpeg trying to maintain a 1:1 with the ongoing stream. Sometimes it'll already have the information it needs if it's recording faster than it's receiving info so it can just skip chunks.
Short answer is no. If you lose connection to the downstream suddenly or you experience a hardware fault/close the terminal you run the risk of the container getting fucked and it not being able to process properly. You can try reencoding it, but that often doesn't work.
Nope. You can close the browser entirely. The only thing that matters is that the terminal is still open.
So for that specific method of recording a stream, no. Generally speaking, Fansly defaults the "auto" quality to highest first, so if you take the first GET header in the Network tab you should get 1080p (or whatever the highest is etc).
I've got it, I'll upload it later today
I see, that's good to know
Damn, that sucks. I hate my internet, man.
Ok, this is also good to know, meaning I can dedicate all my pc to this. I wish I can say the same for my internet connection. I live with a other people, so it's hard to just get a dedicated internet service just for my self.
I did copy the first header everytime, but I notice that some of the output I got have reduced quality. Is there a reason for that? Tbf, I also did have to rerun ffmpeg multiple times due to a lot of other error like server timeout error, or couldn't find http error, and stream discontinuity error.
Yes
Thank you McKenzie. Truly 🙏
Yeah I do the majority of my recordings on a dedicated Raspberry Pi I have running so theres no real performance bottleneck - though obviously theres a limit on concurrent streams. In regards to the internet connectivity, it is a pretty resource intensive so you might struggle with it on lower end connections. Also YFU in particular runs her streams at a very high bitrate so thats gonna strain things further. Moreover, depending on your ISP, you might get your speeds throttled for high DL traffic (and UL traffic if you choose to share your recordings), which obviously isnt great if you live with others.
Your connection is choppy so Fansly is defaulting the auto to a lower quality woul be my guess
This is also likely due to your connection - but just make sure you're using
-c copy
and -protocol_whitelist http, https
in your ffmpeg command, as you'll see those errors more frequently if you've not included them.If you are the streamer yourself the app has a built in way to record. Otherwise, not really? You're kinda stuck with screen recorders until somebody develops an extension or mod for the app.
Yeah, I might need to content with sharing 720p quality. Or contribute some other ways. But if by some miracle I can get an upgrade soon, I woud love to share high quality stuff.
Ah that would make sense. I guess I should use the second or third header so it wouldn't fall into the auto category and got switched by Fansly
I did use the command prompt you share that include protocol whitelist, I guess it just shows how bad my internet connection is.
That's unfortunate, BlueHaze sometimes did her nsfw stream in the spooky D word, that's why I wanted to know if there is a way. Oh well, it can't be help at this point.