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

How am I meant to know what to put with the --device option? #183

Closed
ghost opened this issue Dec 11, 2013 · 3 comments · Fixed by #198
Closed

How am I meant to know what to put with the --device option? #183

ghost opened this issue Dec 11, 2013 · 3 comments · Fixed by #198
Labels

Comments

@ghost
Copy link

ghost commented Dec 11, 2013

I want to change the camera lolcommits uses when it takes a shot, and am aware of the --device="DEVICE" option, but I'm not sure how to get a list of values I can pass?

@matthutchinson
Copy link
Member

Unfortunately we don't have (as yet) a --list-devices option in lolcommits. However lolcommits uses a couple of binary commands (vendored internally) to perform the capturing. They differ depending on what machine you are using (linux/osx/windows). Some of these commands DO have a list devices option. Here's the list;

  • OSX - VideoSnap (created by me) - e.g. download and run ./videosnap -l
  • Linux - mplayer - lolcommits uses the device= argument, so something like /dev/video0 or /dev/video1 would work
  • Windows/Cygwin - CommandCam - unfortunately lolcommits doesn't yet support choosing a camera device with CommandCam. It's totally possible, but just hasn't been implemented yet.

@matthutchinson
Copy link
Member

I'll tag this issue as a feature and leave it open.

FEATURE: Add a new command line arg for lolcommits (e.g. --list-devices) that allows you to list all capture devices (depending on the architecture you are on).

@ghost
Copy link
Author

ghost commented Dec 15, 2013

Thanks Matt.

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

Successfully merging a pull request may close this issue.

1 participant