Running multiple videosnap sessions simultaneously about videosnap

[matthutchinson]

I've never tried that, it might work. It depends on how the capture sessions are handled. I've also thinking of changing the code in a new version to use AVFoundation, which may offer this natively. If I can find another camera to test this with, i'll let you know how it goes.

[miketissenbaum]

That would be great! The way I'm doing it now for sequential captures is
that I run it using a shell script that renames the files as it creates
them using a timestamp (so they don't overwrite each other). Ultimately I'm
trying to run 3 cameras with the same mac that are each creating
simultaneous videos every 30 minutes for 10 hours for a museum (works great
for one camera) - I might try it too and see. But if you do figure anything
out please let me know!

On Wed, Oct 29, 2014 at 6:04 PM, Matthew Hutchinson <
[email protected]> wrote:

I've never tried that, it might work. It depends on how the capture
sessions are handled. I've also thinking of changing the code in a new
version to use AVFoundation, which may offer this natively. If I can find
another camera to test this with, i'll let you know how it goes.

—
Reply to this email directly or view it on GitHub
#7 (comment)
.

[miketissenbaum]

Just worth mentioning that I got it to work no problem! just added an "&" after the first call in terminal to launch videosnap and then ran the additional versions as necessary

[matthutchinson]

After thinking this through, i'd rather not have this as a feature. I'd rather have the tool be closer to the unix philosophy of doing one thing well. If I added this I feel it would bloat the command code.

For capturing from multiple cam's you can use multiple processes of this command to do it (as you've explained).

[miketissenbaum]

I agree - it ended up working perfectly by doing it in the command line and
I actually like the simplicity

On Thu, Apr 16, 2015 at 2:21 PM, Matthew Hutchinson <
[email protected]> wrote:

Closed #7 #7.

—
Reply to this email directly or view it on GitHub
#7 (comment).