slartibartfast wrote:
> Apparently Spotify streams to Chromecast at 256kbps AAC. This thread
> discusses it.
> https://community.spotify.com/t5/Live-Ideas/Chromecast-Stream-highest-possible-Quality-to-Chromecast/idi-p/4523194/page/2#comments
> Seems a little confusing to me.[emoji3]
>
> Sent
garym wrote:
> You're missing that the AAC is *only* for the webplayer. The "premium"
> column has TWO rows. The first row is for webplayers. The 2nd row is for
> everything else (like a desktop app running on your PC, your smart
> phone, or--importantly--your squeezebox player). Spotify
mherger wrote:
> > The table shows Premium account streams AAC to all Spotify Connect
> > devices. I think AAC is limited to the web interface for free
> accounts
> > only
>
> You must be looking at a different table than I do. I only see AAC on
> the "Web player" line.
>
> 32783
>
> --
>
mherger wrote:
> > Having played around with it a bit I personally find the AAC stream
> from
> > Spotty via Spotify Connect (which is supported natively by the
> Marantz)
>
> According to
> https://support.spotify.com/en/article/high-quality-streaming/ AAC is
> only available in the web UI.
Ron F. wrote:
> The Marantz N6006 looks like a nice streamer, but the published spec I
> found does not indicate support for Ogg Vorbis. I assume then when using
> Spotty, slimserver will transcode the Spotify Ogg Vorbis stream to 705
> kbps FLAC and stream that to the N6006 client. This is a
mherger wrote:
> > Thanks for a great plugin. Just one question, I notice you are using
> the
> > Spotty native Ogg Vorbis stream. It's my understanding that the AAC
> > stream is of a marginally higher quality.
>
> AFAIK only the web player uses AAC, none of the other players. So no, no
>
>
Hi Michael
Thanks for a great plugin. Just one question, I notice you are using the
Spotty native Ogg Vorbis stream. It's my understanding that the AAC
stream is of a marginally higher quality. I appreciate that Squeeze
hardware doesn't natively accept AAC but I am using a Marantz streamer
which
philippe_44 wrote:
> it's in "UPnP player audio capabilities", click advanced and you'll see
> "forced mimetypes" or something similar
Many thanks Philippe. All sorted and understood.
MikeatUpwey's Profile:
eggda wrote:
> Here it is:
> Thanks again - much appreciated!
>
> >
Code:
> >
> info
> info
> -1
>
> 0
> aac,ogg,ops,flc,alc,aif,pcm,mp3
> 1
> 120
> 1
> 1
> HASH(0x5e861a8)
> 1
> 4194304
> 1
>
> 1
> 1
> ?
> raw,wav,aif
> 100
mherger wrote:
> > Hi Michael, not sure whether I should be directing this to you or
> > Philippe but notwithstanding the above fix, I am still am
> experiencing
> > issues with the Radio Paradise FLAC stream when used in conjunction
> with
> > Philippe's CastBridge and a CCA device. Much the
mherger wrote:
> > Updated to v2.1.3. Anything we should know?
>
> A minor change to (hopefully) fix streaming to one of philippe's
> clients.
>
> --
>
> Michael
Hi Michael, not sure whether I should be directing this to you or
Philippe but notwithstanding the above fix, I am still am
philippe_44 wrote:
> Was a silly mistake - please udpdate to 1.6.3
Just a heads up for anyone struggling to perform a clean install of
Philippe's CastBridge and running Avast (free). After much frustration,
I discovered Avast (free) was causing the config file to become
corrupted. It also, on
Many thanks for a quick reply Phillipe.
I will have a closer look at my setup. Looks like it could be as you
suggest, something preventing forwarding of mDNS discover requests.
Thanks again.
MikeatUpwey's Profile:
13 matches
Mail list logo
