icemen wrote:
> I need some help with two players on server device,
>
> both devices are USB, ( USB dac and USB to coax converter, using
> different drivers)
> I can play them independently just fine ( in all modes; asio, KS,WDM) ,
> but having problems to leave booth output devices active at
Ouch! And Apple aren't exactly forthcoming with publishing their
protocol? Which is odd because the BluOS guys somehow got hold of it.
I guess I will have to wait until you find the strength to have another
go ;) All a quick google would reveal was this
I need some help with two players on server device,
both devices are USB, ( USB dac and USB to coax converter, using
different drivers)
I can play them independently just fine ( in all modes; asio, KS,WDM) ,
but having problems to leave booth output devices active at the same
time...
I've even
mherger wrote:
>
> I don't want to go there. It's just asking for either more problems, or
>
> more of these tweaks. Metadata problems should be fixed at the source.
Incidentally, Qobuz metada for classical music is the worst I have ever
seen. Just waiting for Spotify lossless to swtch ...
ucw wrote:
> It is probably me, but - and I did try to search the forum - suddenly
> I'm not able to play my DSD64-files through upnpbridge on my KEF LS50
> Wireless II directly. I'm rather certain it worked earlier. The KEFs
> support native DSD. Maybe I've did something in the settings but
Am running recently released UPnP Bridge (1.7.1.0) and am seeing a few
of these
Code:
[21-09-22 18:01:09.0078] Slim::Utils::Timers::__ANON__ (272) Error: Timer
Slim::Plugin::UPnP::Events::expire failed: Can't call method "pluginData" on an
undefined value at
It is probably me, but - and I did try to search the forum - suddenly
I'm not able to play my DSD64-files through upnpbridge on my KEF LS50
Wireless II directly. I'm rather certain it worked earlier. The KEFs
support native DSD. Maybe I've did something in the settings but I've
tried different
Budge74 wrote:
> 35788
Looks like the version of PowerShell thatÂ’s installed on your system is
from the 19th century [emoji102]
philchillbill's Profile: http://forums.slimdevices.com/member.php?userid=68920
View this
philchillbill wrote:
> When the setup.ps1 script failed, what error message(s) did it show (in
> red)?
>
> Regarding your YML, the region does not matter so much as it only
> affects latency to a small extent. Pick whatever is near you.
>
> It would be interesting to know what that pop up
Release 2.20.4 includes a couple of bugfixes/enhancements :
- The correct audio scrobbling type of 'Radio' is now exposed.
- Some improvements to the signalling of meta data changes to the
controllers.
Stuart McLean
EXPECTINGTOFLY PLUGINS :
- *BBC Sounds* :
kefkekeyser wrote:
> Lately, using the official Spotify app and then connecting my Touch as a
> connected player becomes unstable, the playback sometimes stops without
> a clear reason (don't know if it's caused by the Spotify app, my LMS on
> piCore or may network issue).
>
> I started to use
Lately, using the official Spotify app and then connecting my Touch as a
connected player becomes unstable, the playback sometimes stops without
a clear reason (don't know if it's caused by the Spotify app, my LMS on
piCore or may network issue).
I started to use the Spotty interface on the
Apesbrain wrote:
> Lots of changes to Radio wireless. Do we still need wlanpoke? Thanks.
I think, from reading old messages here, the changes are not expected to
have an effect on the WiFi6 interoperability problem.
So if that is why someone is running wlanpoke then they would still need
to
On my Touch I am seeing
"There was a problem installing this update. Please try again or contact
support"
It doesn't even download.
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile:
14 matches
Mail list logo
