-
Notifications
You must be signed in to change notification settings - Fork 92
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
Feature request - Control individual applications like in Volume mixer #18
Comments
@Suncatcher No, not at this point. |
@Suncatcher I have started the fork dev_v3.1_communicationDevice for this enhancement request. |
Spectacular, man! Will check it soon. |
@Suncatcher How about with the file as it is now? Is the result the same with |
@Suncatcher In fact, could you try the dll from the dev branch and tell me what you think? |
Well, it works not without glitches, but works and that's wonderful. About glitches: But all that doesn't matter for me. Could you please build a single cmdlet for this function? E.g.
|
Also, is it possible to install your module not manually but via NuGet or some automated manner? In order to be up to date when your DLL is updated. |
@Suncatcher We're working on getting the new version published to the PowerShell Gallery. Old version: https://www.powershellgallery.com/packages/AudioDeviceCmdlets/ |
You're right. Those things have now been corrected in the dev dll. As for being able to install the module not manually, I will get back to you once it is updated on the PowerShell Gallery. |
Thanks a ton! |
I can confirme the current v3.0 dll is now available from the PowerShell Gallery. When I merge in the finished volume mixer feature, I will update to v3.1 there.
|
It probably means that I don't know how to properly publish to PS Gallery. I will definitely look into that when I have the time. Thank you for bringing this to my attention. |
Well, I assume this is not the problem of publishing, but the problem of incorrect installation. As I said, module commands are not recognized:
What has gone wrong? I just done
|
Mmm, any suggestions? Tried to reinstall multiple times but module cmdlets are still not recognized. |
This link ain't working anymore: https://github.com/frgnca/AudioDeviceCmdlets/blob/dev_volume-mixer/AudioDeviceCmdlets.dll |
Correct. I still plan on adding this feature and merge it with future version v3.1 but I am currently in the process of moving places so I might not be able to code for this project for a bit. |
Do you still have that mentioned .dll for me to play around with until that
time? :)
…On Fri, Sep 21, 2018 at 3:31 PM frgnca ***@***.***> wrote:
Correct. I still plan on adding this feature and merge it with future
version v3.1 but I am currently in the process of moving places so I might
not be able to code for this project for a bit.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ApdNXHkIcCHZtZSDukgek4d4NtG57rVHks5udOoqgaJpZM4TMKJV>
.
|
Any update here? |
Bump, any update? This feature would be awesome |
Windows 10 (and presumably 11) has the ability to set what audio devices that individual apps listen to. For some reason, however, it resets often for me. If AudioDeviceCmdlets had the ability to set this, I could set up a script to run with Task Scheduler to make sure my apps are set correctly. |
I know this is over a year old, but I am very interested in having this added. Any update on this? |
Does your cmdlet support getting info about apps that are currently active (=playing) in Windows Volume Mixer like this?
I wanna list them and get info about their volume levels.
The text was updated successfully, but these errors were encountered: