Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] All files to be on cache when capturing, and different parts for failed capture #395

Open
4syno4 opened this issue Dec 20, 2022 · 3 comments

Comments

@4syno4
Copy link

4syno4 commented Dec 20, 2022

Hi the program has been very helpful to me and I would like to say thanks first.

I have been using the program and there are two features that would be great addition so I am making request

  1. When using capture on cache option, all files should be written on cache first.
    I have ssd cache and hdd for array. I try to have my array off most of the time to save energy, so I usually really like cache options. I noticed that when I use cache only options, it saves .ts file to the cache, but still utilises /vods/ (on array) to write .json file. This keeps the array on while any capture was on. I really would appreciate if there is an option to have all files written on cache, and moved to /storage/vods/ after capture.

  2. Failed capture prevents more recordings
    Sometimes I need to stop capture to maintain my server. When I do so, and try to restart capture, it often fails because a file with stream date and name already exist from the first capture. I wish it was not like this. If I start second capture of the same stream, the program should just be able to rename the second capture as filename_part2.ts or something along the line. I shouldn't have to go into the server folders to change names or move the files elsewhere

I hope you could consider these points. Thank you!

@MrBrax
Copy link
Owner

MrBrax commented Dec 20, 2022

i'm really gonna have to think about these, both would require major rewrites to how files are loaded and handled, latter one is probably more probable

@luckiestone
Copy link

Agree with request 2. I've run two times into an error says

automator.captureVideo <WARNING> Chunk 404'd for **** (0/100)!
automator.captureVideo <ERROR> Failed to fetch segment for ***!
automator.captureVideo <ERROR> Read timeout, exiting for ***!

and then the capture ends while the stream is still on. It would be better if the app will backup the recorded and try to re-capture. Just an assumption, and I don't know if this is feasible.

@MrBrax
Copy link
Owner

MrBrax commented Dec 22, 2022

i'm gonna have to make it so more than one segment can be added to a vod, even though it's already an array.. but for now i'll just make it launch the fallback capture if enabled if it times out like that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants