Both Mip and LMS are pointed to the same music folder. Mip shows a
library of 78,042 songs total (only 72, 084 with "ready" status). LMS
shows a library of 77,897 songs total. I am unsure how to reconcile
these differences and compare libraries. If I could determine the
missing tracks perhaps
mherger wrote:
> Wow... it seems as if you were the last user relying on MIP to manage
> your collection...
>
> I'd suggest you re-configure your LMS to scan your music folder, and
> only rely on MIP for the mixing (using that "only check mixable status"
>
> mode I mentioned earlier). This
mherger wrote:
> Wow... it seems as if you were the last user relying on MIP to manage
> your collection...
>
> I'd suggest you re-configure your LMS to scan your music folder, and
> only rely on MIP for the mixing (using that "only check mixable status"
> mode I mentioned earlier). This has
mherger wrote:
> Wow... it seems as if you were the last user relying on MIP to manage
> your collection...
>
> I'd suggest you re-configure your LMS to scan your music folder, and
> only rely on MIP for the mixing (using that "only check mixable status"
>
> mode I mentioned earlier). This
Wow... it seems as if you were the last user relying on MIP to manage
your collection...
I'd suggest you re-configure your LMS to scan your music folder, and
only rely on MIP for the mixing (using that "only check mixable status"
mode I mentioned earlier). This has been much more reliable in
mherger wrote:
> > The only difference in behavior is that I no longer get a scan
> > terminated message, so it appears to have completed successfully, but
> it
> > does not include any new music added. Maybe time to uninstall and
> > reinstall MIP, then LMS if no change. Other suggestions
The only difference in behavior is that I no longer get a scan
terminated message, so it appears to have completed successfully, but it
does not include any new music added. Maybe time to uninstall and
reinstall MIP, then LMS if no change. Other suggestions appreciated.
Please elaborate: no
mherger wrote:
> > Question though: Will this exclude all tracks I have selected as
> "not
> > enabled" in MIP from my LMS library?
>
> No, the big difference is that MIP would not be used to manage metadata
>
> other than the mixable status. In your current setup LMS reads all the
> track
]No, the big difference is that MIP would not be used to manage metadata
other than the mixable status. In your current setup LMS reads all the
track information from MIP and does import it into the library. This
theoretically would allow you to have your music collection without
defining a
Question though: Will this exclude all tracks I have selected as "not
enabled" in MIP from my LMS library?
No, the big difference is that MIP would not be used to manage metadata
other than the mixable status. In your current setup LMS reads all the
track information from MIP and does import
mherger wrote:
> > [18-03-28 20:54:40.9536]
> Slim::Plugin::MusicMagic::Importer::exportSongs
> > (200) MusicIP mixable status full scan
>
> I can't believe we still deal with MIP, ten years after their shutdown?
> :-)
>
> Here's my recommendation: set the scan mode to "Only read mixable
>
[18-03-28 20:54:40.9536] Slim::Plugin::MusicMagic::Importer::exportSongs
(200) MusicIP mixable status full scan
I can't believe we still deal with MIP, ten years after their shutdown? :-)
Here's my recommendation: set the scan mode to "Only read mixable
status". It's faster and causes less
Thank you for your help again. I am unsure I am getting the details you
wish but I have selected what seem like all the relevant logs and set
them to debug. I have run 4 attempted scans which show the same audio
file as the final entry:
[18-03-28 20:54:56.6631]
Change of plan ... I had not spotted that it is a plugin that is doing
the scanning.
So ... increase the logging level for that plugin (same place in LMS
interface).
Change to Warn or Debug and click Apply at the bottom.
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc)
Paul Webster wrote:
> Try increasing the logging level of the media scanner to see if it shows
> you which file it was last working on ... and then move that file out
> for a while to see if the next scan gets past it ... then the problem
> file(s) will need examining.
>
>
Try increasing the logging level of the media scanner to see if it shows
you which file it was last working on ... and then move that file out
for a while to see if the next scan gets past it ... then the problem
file(s) will need examining.
Settings/Advanced/Logging/Scan ... (might as well set
Logitech Media Server Version: 7.7.5 - 1416570306
rivrwing's Profile: http://forums.slimdevices.com/member.php?userid=31626
View this thread: http://forums.slimdevices.com/showthread.php?t=108871
"Media scan terminated unexpectedly" error for days now. Not sure what
the log is pointing to.
I use Music IP as my library. The configuration has been unchanged for
years and has been functioning better than ever for the past 18 months
on a new windows 10 machine.
Assistance appreciated!
atrocity wrote:
> My main server is a Pi and it works fine with my library:
>
> >
Code:
> >
> Total Tracks: 102,463
> Total Albums: 8,517
> Total Artists: 17,991
> Total Genres: 269
> Total Playing Time: 7567:14:11
>
> >
Nice.
eduardoo wrote:
> The pi is an interesting idea, but I wonder if the little ram and
> computer power it has can cope with the rather large library (almost 11k
> albums and over 110k tracks) of mine. I changed to this nas a few
> years back because the old one with ARM CPU and 1 GB RAM had
Man in a van wrote:
> Why continue to struggle?:rolleyes::confused:
>
> Get a Sunday paper round, save up and buy a Raspberry Pi 3B.
>
> Put LMS on the pi and point it at the Qnap for the music files.
>
> The world moves on, move on with it.:)
>
> Ronnie
The pi is an interesting idea, but I
mherger wrote:
> > /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins,
> >
> /share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins
> > seem to contain nothing.
>
> You'll have to delete them from Slim/Plugin. Or uninstall LMS before
> installing
/opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins,
/share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Plugins
seem to contain nothing.
You'll have to delete them from Slim/Plugin. Or uninstall LMS before
installing the old version.
--
Michael
Why continue to struggle?:rolleyes::confused:
Get a Sunday paper round, save up and buy a Raspberry Pi 3B.
Put LMS on the pi and point it at the Qnap for the music files.
The world moves on, move on with it.:)
Ronnie
eduardoo wrote:
> Thanks for your prompt reply.
>
> Excuse me for my silliness, for my QNAP running SSOTS, I should use
> logitechmediaserver-7.9.0.tgz?
>
> As for deleting plugins, I just use winscp to access the folders (
>
Just to get it straight, you mean I should untick fulltextsearch and
remote library and restart 7.9.1, before reinstalling 7.9.0?
No, manually delete the files from your disk.
Also, is there somewhere where I can get a more recent build of 7.9.0 to
try?
There's the released 7.9.0:
mherger wrote:
> > (squeezeboxserver-7.9.0-1408608555.tgz - a 121MB file). The
> refreshing
>
> Now that's three years old?!?
>
> > 0016: [17-06-05 13:40:34.0040] Slim::Utils::PluginManager::load (377)
> > Warning: Couldn't call
> Slim::Plugin::RemoteLibrary::Plugin->initPlugin:
> > Can't
(squeezeboxserver-7.9.0-1408608555.tgz - a 121MB file). The refreshing
Now that's three years old?!?
0016: [17-06-05 13:40:34.0040] Slim::Utils::PluginManager::load (377)
Warning: Couldn't call Slim::Plugin::RemoteLibrary::Plugin->initPlugin:
Can't locate object method
As I recently found that refreshing to next track's data on the
Squeezecontrol app seems slow after updating to 7.9.1
(http://forums.slimdevices.com/showthread.php?107392-Album-art-and-progress-on-next-track-slow-to-show-after-7-9-1),
I went back to my earlier copy of 7.9.0
29 matches
Mail list logo
