Linux Blog

Remotely Changing Windows Volume

Filed under: Shell Script Sundays — TheLinuxBlog.com at 2:41 pm on Sunday, October 18, 2009

This is not really “shell scripting” but the end result is some more bash scripts in my bin directory so what the hell? It’s going in the shell script section because its Sunday. So what?

I like to listen to music on my Windows box while I work on my Linux box. Online radio and other sounds, just get in the way too much. One of the things I wanted to do for a while was remotely control my volume so I didn’t have to use my KVM to switch over to change the volume when ever anyone came in my office.

Its actually pretty easy to control your windows volume from Linux.

At first I thought, I’d create a dummy audio device, and some how map it over. Then I figured that was overkill and I’d try something a bit easier. I have SSH via Cygwin, so all I needed was a way to control the volume locally, and I could execute the command with SSH. Having no volume utilities jump at me when I looked through the Cygwin repositories I went to look for something else.

NirCmd is an awesome utility, giving me and other Windows users the ability to do things that Linux users may take for granted, you can read about it here: http://www.nirsoft.net/utils/nircmd.html after installing it, and making sure that my corporate AV didn’t throw a hissy, it was just a matter of dumping some scripts in my bin directory and chmodding them so they would run.

Here is what they look like:

Volume Down Script: ssh windowsbox -l owen -C “nir changesysvolume -2000″

Volume Up Script: ssh windowsbox -l owen -C “nir changesysvolume 2000″

Mute: ssh windowsbox -l owen -C “nir mutesysvolume 1″

Unmute: ssh windowsbox -l owen -c “nir mutesysvolume 0″

Real simple, and the mute/unmute really comes in handy for when some one walks into my office.

My Mind Stomps with OpenStomp.

Filed under: General Linux — TheLinuxBlog.com at 4:21 pm on Tuesday, August 26, 2008

I’m always looking for ways to integrate Linux into my life more, and harness technology. As a mediocre guitar player and Professional Linux Geek I’ve often thought about Linux and guitar effects. Sure, there is a ton of software and homebrew hardware out there, but I’d like something more than that.

I’m sure by now (since its all over the news) that you’ve probably heard about the OpenStomp. Awesome concept! Lets make something quite complex to build, lets not give out the actual details about the internals of the device and lets claim to be the “Worlds first Open Source Effects Pedal”.

I was considering purchasing one of these until I found out the price. Then I thought, oh. I’ll purchase a parts kit. NO kit available. Then I though, oh I’ll just build one from scratch. HOW, with no public schematics?

Sorry my friends, having a website, a hardware device and a forum that you publish your source code to will not get me to purchase your device. Charging $349 for the pedal that you don’t provide plans for doesn’t go down well. If my commercial “closed box” gets fried, I don’t couldn’t care because it was cheap. The Open Stomp is a different story, What kind of Warranty do you offer?
I know you offer schematics if I purchase it, but what happens if it breaks with no modification in the first day?

What happens if a software update blows my StompBox up? You only have one OS listed on your forums page, are you going to post each version there? Do you have a public subversion repository? Come on StompBox, get your act together and post it on source forge before some one else does. Also while your at it post your schematics so that people can look at them and justify spending the $349 instead of building it. Give them away to capable developers that are interested in your product, you know the ones that will make your product popular by enhancing it.

If you are wondering, this being The Linux Blog and all, if I’m throwing a hissy because there is no Linux version available I’m not.  I couldn’t care less. There are ways around that and if it gets popular enough, there will be a version available. What I’m sour about is the fact that there is nothing “Open Source” about the OpenStomp, other than the huge lack of good documentation, and some source code that is posted in the forum.

I think I’ll go look at the old schematics for some “stomp boxes” and see about building them. Apparently this isn’t open since there is no source code involved. Jeez