This post is a rant on how infuriating it can be when developers don't work together with other companies as well as they should.
So basically I have a few things. A PC with 7.1 audio ports. Speakers that can accept different inputs. An AudioEngine D1 DAC (Digital Audio Converter) which outputs to 3.5mm if wanted, and takes in USB or Optical. A google home. A chromecast audio.
My request was so simple. I want to control Spotify with my voice, and have it play, on request, to my speakers or when I want, directly to my DAC which sends to my headphones.
Hell no it wasn't simple. To get that exact scenario to work, I had to plug the chromecast audio into my line in port on my PC. Run a 3.5mm male to male from my line out on the PC to the speakers, and run an optical cable to my DAC. Using VAC (Virtual Audio Cable) I could route the audio from the chromecast audio to both my optical output and the 3.5mm line out.
Luckily the godsend Spotify connect usability saved my ass because I can open Spotify on my PC and control it from there (More on this later). So now I've got voice control via the google home, which can control the music.
But I'm a power user and I don't want to have to say "Hey Google" just to pause and play my music. So I download VoiceAttack and another program that scripts directly into Spotify via launch parameters. Now I can say "Pause music" and it does so.
So back to why it was important to control Spotify on my desktop. I use Rainmeter and I like the fancy little visualizer I found. It can also pull the artist and track info directly from Spotify and display it. Which I love and I can't do without so I had to go through all this ^ trouble.
If only the Google Home could control Spotify connect natively. Then I could do all this nonsense directly, without running 4 different cables (2 more virtual).
tl;dr Google home doesn't let me control spotify connect so I had to jerry-rig it.
Submitted December 24, 2017 at 07:22AM by Tigerman456 http://ift.tt/2BGg6um via TikTokTikk
No comments:
Post a Comment