Triode wrote:
> It needs the output device to be opened with a name of hw:* to do
> this.
>
> However - this is only valid for usb dacs or output devices where alsa
> knows the supported sample rates. For spdif then there's the
> possibility that alsa believes the sample rate is supported,
JackOfAll wrote:
> I have views, but I need to think some more before I start airing them.
> ;) The "several cans of worms in your near future" warning LED has
> already started to flash.
>
> But immediate thought.
>
> Needs to be a way of specifying the exception behaviour. ie. resamp
Triode wrote:
>
> squeezelite -r 192000,96000,48000,44100 -u E
>
> Where "E" = resample by exception if the output rate is not supported.
>
>
> This would mean that it would resample 88.4k material to say 192000 but
> not 96000 material. Is this the type of thing we want?
>
> [I am also wo
JackOfAll wrote:
> Triode,
>
> I'm thinking out loud, and probably missing something obvious, (as per
> usual), but why is any of this an issue? Squeezelite behaviour is to
> open the output device at the native sample rate. If that fails then
> it tries to open the device using plughw, whic
Hi
I cant test right now, but I think that I need to press CR to get a
prompt when using keyboard and HDMI.
Fiatelis's Profile: http://forums.slimdevices.com/member.php?userid=60087
View this thread: http://forums.slimdevi
I've accidentally deleted the email reporting the issue of the lms-CPAN
package no longer compiling on x86_64. If the person who reported it is
reading this, there are new packages in the testing repo (srpm and
x86_64) which resolve. (And no, the fix is not a joke. Adding '-v' to
the gcc CFLAGS re
dsdreamer wrote:
>
> The only issue I have is that, when there is not a "special event," I am
> forced to use the streams that use a lower audio sampling rate than
> 44.1kHz. I have the following rates available on my DAC: 44100, 48000,
> 88200, 96000, 176400, 192000, 352800, 384000. The result
Triode wrote:
> Has anyone seen the 100% cpu problem since this update? I can't
> reproduce myself, but wondered how stable the latest test branch was for
> people?
I haven't seen it again since the update. Too soon to say if whatever
you added/changed has fixed it or not, I think. I've not done
Triode wrote:
> Has anyone seen the 100% cpu problem since this update? I can't
> reproduce myself, but wondered how stable the latest test branch was for
> people?
I have not seen the 100% cpu problem so far. I'll give some thorough
testing (I saw some XRUNs).
Running jivelite in the HDGrid skin I'm seeing bad icons for the Radios.
Is this a known issue?
15383
Looks like the applet wasn't compatible with the grid mode, but using
grid size icons for the radio only or something?
+---+
|Fi
dsdreamer wrote:
> What is the best currently-available work-around I could use to overcome
> this issue?
>
Have you tried setting on demand pref to WMA only - the WMA streams are
48kbps / 44.1kHz. IIRC the AAC ones were 32kHz/56kbps.
---
Triode wrote:
> Has anyone seen the 100% cpu problem since this update? I can't
> reproduce myself, but wondered how stable the latest test branch was for
> people?
No, Squeezelite is behaving correctly; nor did I ever experience that
issue.
But I must admit that I'm doing nothing fancy; no up s
12 matches
Mail list logo
