Kethsar
--save-state - how to restart existing stream?
The README file includes reference to a --save-state flag you can include in a command line prompt that saves a portion of an already-started live stream download, but there is no reference made as to how to restart a download of a live stream after manually stopping it.
Is there a mechanism for doing so? I'm not very familiar with Go, but I couldn't find anything specifically supporting this in player_response.go.
If so, can you add it to the README file? If not, can we get support for this?
Use Case: A video editor is downloading a video from a live stream to cut into short-form clips for YT Shorts, TikTok, etc. They need to start cutting up the part they have downloaded to create YT Shorts or other short-form video from the longer video, but the live stream is still going. They need to manually cancel the stream download to mux the file, but they want to continue downloading the stream from where they started after muxing the existing files to avoid redundancy and overlap between two download files.
That is currently not supported. It was meant to work that way, but I forgot to test manually stopping a stream when it was caught up after implementing it. The current logic just automatically starts the muxing if your download is caught up. I do want to fix this at some point. You might be able to force it by killing the process, running the ffmpeg command manually, and re-running the yta command. On Windows you could use the task manager to kill the process, I think.
Well after testing it seems manually stopping the stream does not actually automatically start muxing if it's caught up, and does go through the set of questions if you don't have flags set specifically to bypass them. As long as the stream has not ended, that is. That means if you stop the stream and then answer "no" to the first two questions but "yes" to saving state, you should be able to follow the above steps without needing to hard kill the process.
Well after testing it seems manually stopping the stream does not actually automatically start muxing if it's caught up, and does go through the set of questions if you don't have flags set specifically to bypass them. As long as the stream has not ended, that is. That means if you stop the stream and then answer "no" to the first two questions but "yes" to saving state, you should be able to follow the above steps without needing to hard kill the process.
The second question is kind of ambiguous IMHO. It says "Would you like to save any created files" so one would assume if you choose No it would just delete all the partially finished files.
At least I personally won't expect there would be additional question after this which can save both state and files.
The actual difference between NY and NNY is that the first one would delete state but move temp files from subfolder to the CWD, while the latter would keep the state and not move the temp files. So I would think moving the 3rd question to the second (and revise the wording) makes more sense.
