I'll fix that up when I have some time. Thanks for pointing it out. Most panics come from when something went wrong with the ffmpeg subprocess. I didn't know that there is a way for the user to handle errors coming from this subprocess.
I originally wanted to use json for parsing, however the unmarshalling would have required a large struct with fields for all the metadata ffprobe outputs. I thought that using "-print_format compact" resulted in a simpler parsing approach. Correct me if I'm wrong there, I'm still relatively new to Go.
Thanks for sharing the link to your project. I'll try to implement the stdout buffering with "bytes" rather than doing it manually.
Made a push adding getters for relevant fields and making field names uppercase in the Options struct. Don't know how long it takes for pkg.dev to update, but the issue should be resolved now.
That's correct. I like to use go for image processing and wanted to apply some of the algorithms I made to video but did not find a simple way to do so. I set out to make a video I/O module.
I'm currently fixing all the non-idiomatic problems as well as adding some getters for each struct. Thanks for the feedback!