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

NoteRecorder only uses default input device #6

Open
cusmonaut opened this issue Oct 11, 2014 · 13 comments
Open

NoteRecorder only uses default input device #6

cusmonaut opened this issue Oct 11, 2014 · 13 comments
Assignees

Comments

@cusmonaut
Copy link
Collaborator

As a user
I want a menu option that allows me to select my input device
so that I am not forced to change what my default input device is to record.

Given a user with multiple input devices
When they select their desired input device from a menu
then that input device is used to record sound

@cusmonaut cusmonaut changed the title NoteRecorder oly uses default input device NoteRecorder only uses default input device Oct 11, 2014
@cusmonaut
Copy link
Collaborator Author

I would like to see this feature added as an enhancement at some point. Please feel free to asign it to me.

@jhaenchen
Copy link
Owner

I think that's a great idea we're using mcisendstring to do the recording. I would recommend checking out the following link http://mobile.experts-exchange.com/Programming/Languages/Visual_Basic/Q_20901375.html

@jhaenchen
Copy link
Owner

@cusmonaut Not sure why, but I can't assign it to you, your name doesn't come up.

@cusmonaut
Copy link
Collaborator Author

I belive I need to be added as a Collaborator.

@cusmonaut cusmonaut self-assigned this Oct 12, 2014
@jhaenchen
Copy link
Owner

Added you as a collaborator.

@cusmonaut
Copy link
Collaborator Author

@jhaenchen thanks, have you had a chance to take a look at some the links I posted in the wiki? I think the branching one is a pretty good idea.

@jhaenchen
Copy link
Owner

@cusmonaut I'm checking them out. The idea is that we each fork the repo to work inside. The repo should have a master branch and a dev branch, and we each create feature, hotfix, and issue branches on our own. If we want to work together, one of the team members clones the other's fork of the repo. Whenever something is finished at the dev branch, if it's ready for a release, it's merged up to master. Did I get that right?

@cusmonaut
Copy link
Collaborator Author

Yep, so we don't touch the master branch untill a release is ready. Our forks would be from the dev branch. It's up to you if you want to go this route but I think we should at least do the Master and Develop branches.

@jhaenchen
Copy link
Owner

I think it's a good idea. Would I make a fork off of develop? Can I even fork my own repo?

@jhaenchen
Copy link
Owner

Added the dev branch.

@cusmonaut
Copy link
Collaborator Author

Idealy you would, but that doc was focused around an organizational repo and not an individuals so I think you would be ok just making new branches off of develop. If you wanted to I think you can make an organization and give it controle of this repo, then I think you could fork that repo into your personal stuff.

@jhaenchen
Copy link
Owner

Gotcha. Okay, lets just start pushing to dev. I think you can make a branch for the audio input source thing for starters.

@cusmonaut
Copy link
Collaborator Author

will do, I'll be able to star work on that after the weekend is over.

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

No branches or pull requests

2 participants