You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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!
The text was updated successfully, but these errors were encountered:
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
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.
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
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
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.
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!
The text was updated successfully, but these errors were encountered: