Kevin, have you thought of optionally allowing the incoming msg to pass in the 'basepath'? It could be useful if someone wanted to put ffmpeg-spawn in a subflow.
I've got a case in mind of having multiple cameras that may or may not need to use mp4frag. Currently, since the 'basepath' is hardcoded, there needs to be multiple copies of the code processing it. With the ability to pass the value in a msg (msg.basepath) we could create one flow, and then make it a subflow cutting down maintenance.
For example: if you have 10 cameras, you could fix the issueonce in the subflow instead of having to fix it in 10 locations.
