expectingtofly wrote:
> Indeed,. I stopped 2.26.2 being downloaded yesterday while we got to the
> bottom of those issues being reported. 2.26.6 is now available on the
> main 3rd party repository with the issue resolved.
Thanks, now downloaded just fine. I obviously chose just the wrong
moment
Is this temporary ?
Code:
Slim::Utils::PluginDownloader::_downloadError (266) unable to download
BBCSounds from http://plugins.expectingtofly.co.uk/BBCSoundsPlugin_2_26_2.zip -
404 Not Found
-
rbl wrote:
> Does anyone know about Triode's Network Test plugin? My SB3 is connected
> to LMS 8.3.0 on a Pi4 via WiFi. The Wifi is very good but the SB3 seems
> to think it is rubbish!
>
> 500kbps 100 100
> 1000kbs 68 75
> 2000kbs 33 60
>
> I hvave no idea what these numbers mean to be honest
ralphy wrote:
>
> Yes the radio actually pauses the stream, until the output buffer fills
> a bit then resumes. Occasionally, this pause/unpause happens several
> times before the stream stabilizes, which could sound similar to
> stuttering when you first start a stream. I've not had it happen
slartibartfast wrote:
> I remember that and I also disabled native aac at the time. Was that
> before or after the community firmware?
This post would suggest that it was before the Community Firmware:
https://forums.slimdevices.com/showthread.php?113479-Announce-Community-Firmware-for-Squeeze
ralphy wrote:
> What's happening is the aac decoder can't push enough decoded PCM data
> to the output buffer at the start of the high rate streams and jive_alsa
> throws an underrun error.
Right, I've just experienced this. Playback stops within a very short
time after the stream is started, a
expectingtofly wrote:
> I have had a couple of bugs raised on the BBC Sounds Plugin repository
> relating to audio stuttering :
> https://github.com/expectingtofly/LMS_BBC_Sounds_Plugin/issues/134
>
> Both reports are using Squeezebox radio's with the community firmware.
> The BBC Streams are
slartibartfast wrote:
> OK. One more thought. I have added a Cron job to reboot my Touch every 2
> weeks. Will I need to redo it?
I think not. The cron table is, I think, stored in the etc hierarchy,
which is left untouched by firmware updates. And I think it takes a
factory reset to wipe that
slartibartfast wrote:
> Do we need to take any notice of the items under Build failure
> mitigations?
No.
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.c
Ade_AV wrote:
> Had this working in the past but getting the following now
> >
Code:
> > 404 Not Found: settings/server/plugins/ShairTunes2W/settings/basic.html
> >
>
I have had this error on a Debian system if the Perl package
crypt::OpenSSL::RSA
Paytheprice wrote:
> As noticed before, just two of four radios seem to be affected. And it
> just happens if WiFi was turned off during the night. The third one did
> loose connection today and showed the blue WiFi icon while it was not
> connedted. Here a restart was necessary.
>
If you wer
P Nelson wrote:
> I have noticed unpredictable behavior trying to reconnect to the WiFi
> network. Not sure if I could recreate the problem. If there are logs
> that could help, let me know.
>
I have encountered something similar, but perhaps not identical.
See issue: https://github.com/ral
castalla wrote:
> So, why not use the brilliant picoreplayer Bluetooth feature to play
> Audible? Yes, with one big Snag ... All books have to be converetef to
> mp3 and critically lose the ability to bookmark and restart at last
> listening point.
>
I have never used Audible, but I believe t
Squeeza wrote:
>
> In that case i will have to type the Server-Adress manually, because the
> server may not be found automatically (different Subs).
> How can I type in - after already being connected to a (maybe foreign)
> WIFI - manually a Server-IP or - in other cases - where can i type in
te36 wrote:
>
> Does the community firmware claim to have better wifi driver to help
> protect against those wifi disconnects ?
> Or would i equally need wlanpoke as i need on stock firmware ?
>
No, it makes no such claim. The need for -wlanpoke- is likely to be the
same on both community fir
pd1acf wrote:
>
> Would this firmware, or another build, be applicable for the Classic
> devices? Would be nice to have all devices on the same revision.
>
No. The Classic devices do not use this firmware, at all.
pd1acf wrote:
>
> Would this firmware open up WPA3 support on these devices?
Apesbrain wrote:
>
> EDIT: Interestingly, it appears that "wlanpoke" remains installed after
> a firmware upgrade. I didn't expect that, but good I think.
A simple firmware upgrade basically leaves alone what in the etc
hierarchy, where I suspect wlanpoke is installed (I may be wrong).
A fac
bigcookie wrote:
> Hello,
>
> I installed the community firmware on 5 Radios and 1 Touch - running LMS
> (Logitech Media Server Version: 8.1.1 - 1610364019 @ Thu Jan 14 06:24:58
> CET 2021) in Docker on a QNAP system.
> During the last two days all my devices should a screen that the device
> h
hestbank wrote:
> Seeing the talk about Remote Login I thought, just for interest, I would
> have a look around inside. I can log in ok but the command "ls" doesn't
> show me anything. What language does the Touch use? Can anyone point me
> in the direction of a few basic commands.
You can enab
Rasputin_GY wrote:
>
> I'm glad the community firmware has CLI enabled by default, which made
> it easy to put that into wpa_supplicant.conf
Hmm, I wonder if that is really a good idea, given the well known login
details. Convenient for you on this occasion, of course.
--
Rasputin_GY wrote:
> Wasn't there an option after choosing a wireless network to connect to
> it using WPS instead of manually entering passphrase? I have to admit,
> it has been a while since the last setup :)
> Am I wrong? Could someone please let me know how to connect WiFi using
> WPS?
There
frankd wrote:
>
> maybe you could consider including the script provided by PomDev into
> the next radio firmware.
>
I have been taking a brief look at the script to see if its logic could
be embedded within Squeezeplay itself. It's not obvious to me, at
present, how that might be seamlessly
Thomas_S wrote:
> The reason that i wanted to update to firmware 8 is that I also use
> tidal. It is not longer possible to use the tidal app with the local
> lms. Since some weeks I had to change to mysqueezebox.com to use tidal.
>
> Under firmware 8 I found no possibility to start lms local o
ralphy wrote:
>
> Must be getting close already...just noticed that there are 'several
> threshold overrides in Playback.lua'
> (https://github.com/ralph-irving/squeezeplay/blob/master/src/squeezeplay/share/jive/audio/Playback.lua#L909).
> Something else to investigate.
And, if I recall correc
ralphy wrote:
> Sorry, Yes, I didn't think you had "POP" in the logs. I just meant that
> I've hadn't noticed it. I'll have another listen to the url stream from
> staresy more closely.
>
The original stream (last week or so) was
https://live.streamlojik.com:17070/20210210_2004.aac
ralphy w
ralphy wrote:
> Hence my comments about no real need for the downmix feature for the
> radio. I couldn't hear any difference between the bass driver and
> tweeter with it set to stereo or mono output channel mode. But if I add
> it to the community firmware I didn't want the change to be in on
ralphy wrote:
> I haven't seen/heard the "POP" issue with any of the 3 jive binaries.
> Very strange.
Bad choice of words. Seen in the log, not heard as a "POP", but heard as
an interruption in the stream coming at variable intervals. I associated
it with @staresy's description:
>
> It's an M
ralphy wrote:
> I'd be interested to know if the changes make a difference for others.
Thank you very much for this. It shows much promise.
I've been testing the revised binary against the same problematic stream
posted by @staresy. My results differ from yours, in that I have start
up problem
expectingtofly wrote:
> Apologies if it's obvious, can someone point me to the instructions on
> how to install this, and I'll test that it solves the issue for the BBC
> Sounds AAC streams
Download the tar file, untar it (-tar -x-f
/whereami/baby-jive-aac-stutterfix-8.0.1r16835.tar-). You will
P Nelson wrote:
> I am not sure if this belongs here, so it it belongs somewhere else, let
> me know.
>
> I have an SB Radio on firmware 8.0.1-r16835. When I returned to my
> office, one of my Red Radio's wifi had the red symbol so it was not
> connected. My other Back Radio four feet away wa
Peter Galbavy wrote:
> *and* there isn't a Settings link under the Plugins tab
I think that there one or two other Plugins that miss that link. Catches
me out every time.
mrw's Profile: http://forums.slimdevices.com/membe
KeBul wrote:
> Are the changes made for each community release documented and published
> anywhere
The first post of this thread has a link to the CHANGELOG. (In big blue
letters :) )
mrw's Profile: http://forums.slimdevi
Grumpy Bob wrote:
> I do have a question. One of the SBRs is used as a bedside radio, and
> started playing BBC Radio 4 (our usual alarm playlist, though not alarm
> was set for that day) at 4.35am GMT. Might that be a consequence of
> being notified of the availability of a firmware upgrade? Or
ralphy wrote:
> It might be related to increased memory usage, as the shared aac library
> is about 450K larger than the equivalent static jive binary.
>
> I'll build an aac static linked jive binary replacement for the radio,
> as a way to help determine if that is the cause.
Trying this. Som
staresy wrote:
> Hi,
> I updated my SB radios, controller and touch to Version 8.0.1 r16835 and
> settled down to my weekly Island Vibration stream:
>
> http://streamlojik.com/playlist/?ch=outreachradio&cd=Island%20Vibrations%20Midweek%20Musical%20M%C3%A9lange&dd=wednesday&hh=20&ll=2
>
> It's
staresy wrote:
> So, I think a buglet may have slipped into the latest version whilst
> working under the bonnet with the AAC decode engine.
Just an observation:
The stream is https. So LMS is fetching the stream, and effectively
proxying it. (Assuming AAC native is set).
Not that that should
SlimChances wrote:
> The notification on the player saying
Thank you for the confirmation of the notification that you are seeing.
That helps.
SlimChances wrote:
> I thought I had provided the necessary logs
I am chasing a bug. I had some reason to believe that the underlying
circumstances, in
SlimChances wrote:
> I am able to use my player the notification is just annoying. Eventually
> I will update again but not for some time. Thanks for looking at the
> logs
What notification ?
May I see a log ?
mrw's Prof
SlimChances wrote:
> I hope that is enough info.
Thank you very much for taking the time to do this. It helps.
Unfortunately, from my perspective, my buglet hypothesis does not seem
to be in point, at least in your circumstances.
Have you tried disabling the Community Firmware plugin ? My thin
SlimChances wrote:
> The log is attached. I am not quite sure how to set squeezebox server
> setting to info on the Touch but the log attached has "server updates"
> set to info and is for the server
It is the log from the Touch that I sought, not the log from the
server.
Log level settings are
SlimChances wrote:
> I have Firmware: 8.0.1-r16824 on my Touch and I keep getting a prompt to
> update software on the player. I set software updates off in server
> setting but that didn't seem to stop the update notification.
What is the update notification asking you to "update" to ?
Could
yeomanspc wrote:
> it will be nice not to have my SO occasionally ask why the radio sounds
> all 'tinny'.
I wish I could say that it is 100% tin-proof. But I can't - I've had one
incidence of tin in the 10 months or so with the modified firmware. Of
course, that will be the occasion when your SO
ralphy wrote:
> Because when I copied the classicfm.aac file to my test system ...
Ha ! An 'other factor'. I might not have owned up to that. :)
ralphy wrote:
>
> I've rerun the test and can confirm that I get 37 sync errors but the
> file plays...with a few "blips" in the audio.
>
There are
ralphy wrote:
> Now I need to find a file/stream that triggers the error.
I've conjured up a file that contains plenty of errors, and have
attached it. It is a plain '.aac' file, which I have constructed by
downloading 40 seconds or so from a remote stream, and specifying that
icy metadata shou
ralphy wrote:
> That's for the pointer. I'm going to revisit the aac decoder in the
> coming days as when I tried the test file in that ticket, the track
> position progressed through the entire track but no audio.
> At least the decoder doesn't crash with the out of bounds patch applied.
I'm
Paul Webster wrote:
> However, if that is checking a URL (which it appears to be based on the
> variable name) then I think it is quite possible for a genuine AAC to
> not have a dot.
> If correct then would it mean that real AAC content would not
> necessarily be detected properly?
Only if the
ralphy wrote:
> I trap on AAC_DEC_TRANSPORT_SYNC_ERROR as well but the newer fdk-aac
> decoder it's returning that error for this issue. Perhaps it's trying
> harder to decode the errant stream? but that's just a guess.
I came across this -ffmpeg- ticket which suggests what correct handling
sho
ralphy wrote:
> I found the problem with the FDK AAC decoder segfaulting in the
> community firmware.
>
> The aacDecoder_DecodeFrame API function multiplies the buffersize
> provided in the parameters by the data size causing it to try accessing
> beyond the allocated output buffer.
>
> https:
bpa wrote:
> I think we're both at the edges of our knowledge. I' m not going to
> worry about previous bugs/misconfiguration - I see the prime issue as
> two caches out of sync.
I don't doubt that you will be shown right, other than in using the term
'prime'. I think there may be two 'co-prime'
bpa wrote:
> The problem is same as before - two caches out of sync
>
> for same 1.fm URL
> $contentTypeCache has "aac" accessed in Schema.pm
> $urlToTypeCache has "mp3" access in Info.pm
An area that is well outside my knowledgebase ! I'll continue to study
and gain understanding.
Neverthel
bpa wrote:
> headercontent is audio frame data.
Thank you. That was the piece of understanding that I was missing.
bpa wrote:
>
> Problem was an AAC stream being identified as MP3 (as suffix was .mp3).
>
> Starts at ppst #43 but goes on and later MichaelH offers (and implement)
> a better s
slartibartfast wrote:
> I suppose the workaround is to disable native aac until it is fixed.
I won't be doing that, because it is important to be able to flush out
problems, which this episode has done.
It would be interesting to know what -faad- makes of the misidentified
stream, when LMS does
bpa wrote:
> First, in /Slim/Utils/Scanner/Remote.pm the ContetnType is set to "aac"
> based on URL.
>
But that is done _after_ looking at the remote headers.
bpa wrote:
>
> Later, after reading data from the stream, in
> Slim/Player/Protocols/HTTP.pm (after calling parseDirectHeaders to ge
slartibartfast wrote:
> Assuming we are both using the Community Firmware why is my Radio
> rebooting and yours is not?
Assumptions, assumptions... :)
You'll be pleased to know that my Community Firmware reboots itself
splendidly.
For undetermined reasons, the aac decoder in the official firmw
Paul Webster wrote:
> However, if that is checking a URL (which it appears to be based on the
> variable name) then I think it is quite possible for a genuine AAC to
> not have a dot.
> If correct then would it mean that real AAC content would not
> necessarily be detected properly?
Here is my
bpa wrote:
> The original bug was a shortcut to designate type from extension (IIRC
> not the last 3 letters) name rather than scanning the contents.
The code I have identified does not actually check for an extension, but
rather the last three characters. This just looks like a mistake.
And it
bpa wrote:
> >
Code:
> >
> [21-01-21 10:03:04.4177] Slim::Utils::Scanner::Remote::readRemoteHeaders
(376) This URL is an audio stream [aac]: http://strm112.1.fm/reggae_mobile_aac
>
> >
Well, a quick look at Slim:Utils:Scanner:Remote is very
bpa wrote:
> Found the problem.
>
> My LMS has determined it is AAC and tries to use faad - but it is an MP3
> stream.
I wonder why that should be. Headers indicate -audio/mpeg-, meaning, I
believe, MP3.
Code:
curl -I 'http://strm112.1.fm/reggae_mobile_aac'
HTTP/
jeroen2 wrote:
> Especially in urban environments Wifi is increasingly becoming an issue.
> There's some useful advice here:
> https://arstechnica.com/gadgets/2020/02/the-ars-technica-semi-scientific-guide-to-wi-fi-access-point-placement/
Very good article, thank you.
I can relate to the comme
P Nelson wrote:
> The biggest issue I have right now with several of my SB radios is it
> drops the Wifi connection. This is being caused by a new neighbors
> Wifi extender causing some type of interference. (The problem
> disappears if I move the SB Radio to my office.) The only way to get
slartibartfast wrote:
> I thought you could just long press on the "left" button to avoid an
> immediate upgrade.
Goodness me ! So you can.
So, there's another "unapparent way out".
mrw's Profile: http://forums.slimdevic
Heuer wrote:
> When I rebooted the devices they went straight into the upgrade menu
> with no apparent way out!
"No apparent way out" is, I suspect, because LMS considers this to be
"forced" upgrade. The revision on the new firmware is later than the
revision present on the device. See
-Slim::U
rfunk wrote:
>
> I'm not sure I wouldn't describe this as "a small click", but more
> like dropouts happening at a regular high frequency, happening every day
> but *only* when starting from the alarm function. (When I say "high
> frequency" that's to say many times per second as opposed to
rfunk wrote:
> Ever since upgrading my bedroom Squeezebox Radio to this firmware, my
> 6am alarm starting an internet radio stream has sounded really bad. It's
> hard to describe, but it's rough and quiet, almost like maybe it's only
> playing half of each sample.
I played out your station last
mrw wrote:
> Distinctly "healthier" than what I was seeing. If "health" correlates to
> >2% stream buffer fullness. You seem to vary from 0% to 6/7%.
> What stream is being played ? Presumably this is on a Radio.
I will add that when I play out BBC Radio
slartibartfast wrote:
> FWIW these are my figures]
Distinctly "healthier" than what I was seeing. If "health" correlates to
>2% stream buffer fullness. You seem to vary from 0% to 6/7%.
What stream is being played ? Presumably this is on a Radio.
---
slartibartfast wrote:
> How do I get to the messages file in the Radio? I am pretty sure I have
> done this before but it was long ago. I can SSH in using putty but what
> next? With WinSCP I get "Remote side unexpectedly closed network
> connection"
Code:
tail -F /var/
expectingtofly wrote:
> So it seems that there is something incompatible with the way BBC Sounds
> provides the data for the new AAC decoder, that was fine on the old
> decoder.
Or perhaps not.
What is easy to overlook is "how stressed" the Radio seems to be when
decoding aac streams. I've nev
slartibartfast wrote:
> I updated to the latest LMS 8.1.1 while my Radio was still playing my
> alarm radio station. Normally if I do this then the default alarm sound
> is triggered when LMS shuts down but not this time. This is probably the
> first time I have done this since updating the firm
expectingtofly wrote:
> I've upgraded the radios again and looked at the var/log/messages log.
>
> I get these 'Audio underun' and 'OUTPUT UNDERRUN'messages that seem to
> coincide with the juddering and micro stuttering when playing BBC Sounds
> AAC streams. Are they relevant? I don't get si
expectingtofly wrote:
> Interestingly, it happens repeatedly and reliably for me for all BBC
> Sounds streams (yes you are right LMS is fetching them, they are dash
> streams that are stitched together by the plugin.). There is a lot of
> stuttering at the start of the stream, and intermittent
nenu wrote:
> I don't see this mentioned in the changelog, but would the new firmware
> improve synchronization for Duet Controllers used as players? That
> wasn't working (or not implemented) with the official firmware, but
> maybe now it is?
I've done a little investigation over the last coup
slartibartfast wrote:
> Didn't you turn off native AAC at some point? I think you said it made
> the Radio menu more responsive.
Well remembered ! Fortunately I did remember to check the point before
commenting...
It does seem to make the menus more responsive, but for some reason, I
forget wha
sbp wrote:
> In my TIDAL log file (se download link above) I often see this. Do you
> think that is the cause of the problems
>
> >
Code:
> >
> [21-01-05 14:07:24.5057]
Slim::Player::StreamingController::playerOutputUnderrun (2239)
00:04:20:2a:d8:53: decoder: 155
expectingtofly wrote:
> The LMS that my radios are connecting to is on a very low powered
> raspberry pi model 1b, so I actually wondered if that is the problem.
I'm using a SheevaPlug, also quite low power...
mrw's Pro
expectingtofly wrote:
> I meant to raise this a few days ago also, I was going to do a bit of
> investigation. The new firmware has the same problems with the AAC
> streams on BBC Sounds. There is kind of a micro stutter and warble when
> playing AAC streams on the Squeezebox Radio, its as i
slartibartfast wrote:
> I just checked my Controller again and sure enough it is back to full
> brightness. I haven't even touched it since I last reduced the
> brightness.
Uptime ?
Meaning, might it have rebooted itself in the interim ? Just a wild
thought.
--
nenu wrote:
> To me it seems that the controller never tries to correct for any sync
> difference after it has been started.
Well, it certainly does try. Unless you've set the Controller player
synchronization setting to "Don't maintain synchronization".
But, of course, it is isn't entirely suc
nenu wrote:
> So yes, it does seem to work at first, but it gets out of sync very
> soon.
Are there any hints in those old 2008 threads as to where the problem
may lie ? Do have a reference to the WIKI page ?
I agree, my Controller does seem to play back noticeably faster than the
Radio, and w
nenu wrote:
> I don't see this mentioned in the changelog, but would the new firmware
> improve synchronization for Duet Controllers used as players? That
> wasn't working (or not implemented) with the official firmware, but
> maybe now it is?
Blimey, I've never thought to try that.
I have just
chill wrote:
> Every time I read through that paper I'm always taken by the care and
> attention to sound quality that went into the Boom's design.
Ditto. It must have been a fascinating and fun project to have worked
on.
chill wrote:
> Thanks mrw. I do remember your promising post about the DSP filter
> coefficients. If processing power in the Radio is the issue, then
> tweaking those filter coefficients in the hardware seems like a useful
> alternative. I'm sure the Radio has an admira
chill wrote:
> I'd really appreciate a basic tone control - maybe something like the
> 'treble/bass' settings in the Boom. Or better still, the ALSA 10 band
> Equalizer available under pCP. Are either of those possible? Have the
> various obsolete features that have been removed created enou
HeadBanger wrote:
> It was a bug with the automatic dimming setting. See old thread here:
>
> https://forums.slimdevices.com/showthread.php?73433-New-Dimming-Question-(Manual)-power-saving-dim&highlight=Controller+brightness
>
I have not been able to "relate" to any of that, I'm still not sen
HeadBanger wrote:
>
> Is the screen brightness bug on the Controller that Logitech never
> addressed something you could look to fix in a future update? If you set
> the brightness low it will eventually forget the setting and revert back
> to full brightness.
>
I have a Controller, but Ive ne
sota wrote:
> After the restart the wizard couldn't find any Wi-Fi networks and it
> looks like it's not seeing the Wi-Fi adapter. I tried another factory
> reset, but no change.
> Ethernet works fine. Any ideas or suggestions would be welcome!
On the Radio, take the "I don't see my network" op
TomAmes wrote:
> Just updated my seldom-used Controller without a blip. I discovered I
> was behind a previous Logitech update anyway. Not sure what this update
> did, but I do appreciate any and all efforts to keep this Squeezebox
> system alive and thriving!
Well, it will stop the "bouncing"
slartibartfast wrote:
> Since I followed your instruction to enable the blue icon every time
> there has been a short disconnection the icon has been red so it
> probably isn't critical to have. Did blue mean connected to WiFi/network
> but not connected to LMS?
Correct. I just had to turn off L
slartibartfast wrote:
> Does this enable the blue network icon that was removed many years ago?
I would guess not, I see no sign of a change in @ralphy's SqueezePlay
repository.
https://github.com/ralph-irving/squeezeplay/blob/master/src/squeezeplay/share/applets/QVGAbaseSkin/QVGAbaseSkinApplet
Bipox wrote:
> Also I can't find the plugin under 3rd party plugins. What is it called
> exactly?
You need to be running at least LMS *8.0.1*. Community Firmware for
Touch/Radio/Controller. Once the plugin is installed, enable it under
"Settings|Advanced" in LMS.
--
Here's the problem:
Code:
curl http://www.bbc.co.uk/radio/aod/availability/bbc_radio_four_extra.xml
410 Gone
410 Gone
This document is no longer available at this address.
Please contact mailto:carriage.enquir...@bbc.co.uk";>carriage.enquir.
Operajulian wrote:
> The BBC podcasts can take a while to load each list of options and some
> of them don't actually load the specific podcast.
Yes. The problem is that the BBC updates the opml listing dynamically,
with newest broadcast listed first. Unfortunately LMS cannot handle this
situati
bpa wrote:
> This is what BBCiPlayerExtra uses.
I hadn't noticed, before now. :(
@PasTim, if you are minded to make use of that first link that I posted,
-http://www.bbc.co.uk/podcasts.opml-, then I think you may find that the
BBCiPlayerExtra podcasts menu makes a rather better fist of it. It
PasTim wrote:
> I'm not really keen on keeping permanently signed in to the BBC for BBC
> Sounds. Am I being stupidly paranoid?
In my view, no. But I am relaxed about it... not that I've put it to the
test, yet.
mrw's P
PasTim wrote:
> I have never, ever, played a podcast from anywhere. I can see that I
> can download stuff from the BBC website, but what I thought I should be
> able to do was see a list of stuff in LMS and select and play from
> there.
>
> I have the podcast plugin and settings page, but no
bpa wrote:
> Quick response. If the issue is a LMS issue then LMS update is the fix.
> Many users will not update their LMS to fixed LMS 8.* or 7.9.3 Can't
> see any easy way out for proxy users.
Agree.
I'm pretty confident that a simple patch along the lines below would fix
it. But does requ
mrw wrote:
> I haven't tried using https. That might be a different code path. Would
> need to check how it works in the context of a proxy.
A proxy is not used when https is in use. Hence the issue doesn't
arise.
Refer -Slim::Networking::Async:
bpa wrote:
> Can't remove the "#extra" with current BBCiPlayer/BBCiPlayerExtra
> implementation.
> It was added to overcome removal of API by BBC.
> The "#extra" creates a unique response to the URL which LMS caches.
> Without "#extra" LMS would see Extra menu for station as the same as
> BBCiP
atters would proceed
smoothly.
My guess is that -HTTP::Request- handles this for us when it builds the
-path_query-. But the proxy request logic doesn't. Possibly the answer
is to have - _format_request- just strip any fragment suffix it may
find.
bpa wrote:
>
> @mrw Can you do a
@pshepherd, @bpa
I believe that it is the inclusion of the fragment suffix -#extra- in
the GET request to the BBC Server that is causing the trouble. I'll
guess that the BBC servers perhaps no longer tolerate it.
Modern versions of -wget-, -curl-, and browsers seem to routinely strip
this off b
1 - 100 of 300 matches
Mail list logo
