If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Thanks a lot! New builds should be out shortly. Please give it a try.
It looks to me like you didn't put the new scan.so file in the
auto/Audio/Scan folder
If I replace scan.so (from 2009 according to WinSCP) with the version from the zip file it works.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
> That happens when you have multiple versions of Scan.pm and/or Scan.so.
> Depending on the search path (which is determined by system path for the
> .so and by LMS path for the .pm) if the files found report a different
> version it will exit with a load failure.
Starting LMS with --d_startup might report a potential version conflict.
Can you check whether you find a Scan.pm in the arch folder hierarchy
for your platform?
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
> It looks to me like you didn't put the new scan.so file in the
> auto/Audio/Scan folder
> If I replace scan.so (from 2009 according to WinSCP) with the version
> from the zip file it works.
I did replace the existing binary file, not put it in a new place. See
> It looks to me like you didn't put the new scan.so file in the
> auto/Audio/Scan folder
> If I replace scan.so (from 2009 according to WinSCP) with the version
> from the zip file it works.
I did replace the existing binary file, not put it in a new place. See
But would there be multiple copies of Scan.pm below CPAN/arch/5.32? If
so, where, and what versions (it can be found on line 5)?
On my system I have a scan.pm (1.06) in
5.32/arm-linux-gnueabihf-thread-multi-64int/Audio
That does not seem to exist on GitHub. On GitHub it is in
5.32/Audio
Would the update leave the scan.pm I added manually if it was in a different place to yours?
Do I need to manually delete the Audio/scan.pm that I added?
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
> Would the update leave the scan.pm I added manually if it was in a
> different place to yours?
> Do I need to manually delete the Audio/scan.pm that I added?
I don't know... might even depend on the package management system.
Would LMS start if you removed that additional Scan.pm file? Did you try
to start with --d_startup?
I figured it out. I reinstalled the update from the update folder on my SD card and removed the Audio/scan.pm I added. I then noticed that Audio scan was back to 1.05. So I had done my usual trick of thinking I had the latest version but I was one version behind. So I had a scan.pm (1.06) with a scan.so (1.05) [emoji1787]
After another update everything is fine.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
> Would the update leave the scan.pm I added manually if it was in a
> different place to yours?
> Do I need to manually delete the Audio/scan.pm that I added?
I don't know... might even depend on the package management system.
Would LMS start if you removed that additional Scan.pm file? Did you try
to start with --d_startup?
Search path mechanism would not trip over multiple instances present - it is first match served.
Should note that pre 8.x had a Audio/Scan.pm directly below CPAN (so not in arch). Depending on how users install LMS this may still be present if they upgraded from a lower version.
I figured it out. I reinstalled the update from the update folder on my SD card and removed the Audio/scan.pm I added. I then noticed that Audio scan was back to 1.05. So I had done my usual trick of thinking I had the latest version but I was one version behind. So I had a scan.pm (1.06) with a scan.so (1.05) [emoji1787]
After another update everything is fine.
Haha. Different reason, same result. Good job finding the cause.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment