bakker_be wrote:
> I just recently reinstalled my server with Ubuntu 20.04 and followed
> exactly the same guidelines I posted here previously. Don't forget to
> install the 32-bit libraries mentioned
> *_here
>
I have finally figured out the location of the recipes.xml file. Or
rather: I figured out that the mmm.ini also needs to be in the correct
place (apparently, MusicIP just runs with some hard coded default
settings if it doesn't find the mmm.ini.)
So here is what I did:
- Locate the file
I still haven't gotten those Music IP recipes to work. No I'm checking
if I can get them to work when running MusicIP in a docker container.
I'm using 'this image' (https://hub.docker.com/r/ptoulouse/musicip) and
the container seems to work fine (it started scanning the music files).
But adding
This article might help
https://www.howtogeek.com/687970/how-to-run-a-linux-program-at-startup-with-systemd/
Logitech Media Server Version: 8.0.0 - 1590897265 @ Sun May 31 06:47:52
CEST 2020
Operating system: Debian - EN - utf8
Platform Architecture: x86_64-linux
Perl Version: 5.26.1 -
I just recently reinstalled my server with Ubuntu 20.04 and followed
exactly the same guidelines I posted here previously. Don't forget to
install the 32-bit libraries mentioned
*_here
(\"https://forums.slimdevices.com/showthread.php?108991-MusicIP-on-Ubuntu-18-04=921667=1#post921667\;)_*
mikes wrote:
> Thanks, I tried your instructions first. I don't know about Mint 20,
> but best I can tell on Ubuntu 20.04, the whole init.d scripts thing has
> been replaced by systemd, but to be backwards compatible it auto
> generates systemd units to execute the scripts that you have in
mikes wrote:
> Thanks, I tried your instructions first. I don't know about Mint 20,
> but best I can tell on Ubuntu 20.04, the whole init.d scripts thing has
> been replaced by systemd, but to be backwards compatible it auto
> generates systemd units to execute the scripts that you have in
SlimChances wrote:
> I have MusicIP working on Mint 20 (which is based on Ubuntu 20.04). I
> followed the instructions I gave in this thread
Thanks, I tried your instructions first. I don't know about Mint 20,
but best I can tell on Ubuntu 20.04, the whole init.d scripts thing has
been
I have MusicIP working on Mint 20 (which is based on Ubuntu 20.04). I
followed the instructions I gave in this thread
Logitech Media Server Version: 8.0.0 - 1590897265 @ Sun May 31 06:47:52
CEST 2020
Operating system: Debian - EN - utf8
Platform Architecture: x86_64-linux
Perl Version:
bakker_be wrote:
> After a lot of searching, trying, cursing, searching and trying again
> I've managed to solve my issue :)
> Below what I've done, for future reference for myself, and to offer an
> alternative to what's detailed above. As with the above, my method is
> based on the info in
I'm still desperate to figure out why MusicIP is not finding any of the
recipes.xml files that I put in various directories.
I have one little hint where something might be going wrong but I don't
know how to proceed from this: I noticed that when I stop and start
MusicIP (by doing sudo
slartibartfast wrote:
>
> cache=/home/pi/.MusicMagic/default.m3lib
> (...)
> tivo=0
>
Just tried that, restarted musicIP and LMS but still no recipes in
sight. I'm not surprised though, since MusicIP somehow (magically?)
already knows where the default.m3lib file is, so I'm not really giving
chaug wrote:
> Well, perhaps not. I'm not sure. I did not touch it. It looks like this:
>
> [mix]
> mixsize=10 tracks
> restrict=3 tracks
> style=20
> variety=0
> seed=1
> [server]
> proxy=0
> host=
> proxyport=
> authentication=
> user=
> password=
> [services]
> key=
> cache=
> port=10002
>
slartibartfast wrote:
> Just noticed that your recipes file is in the correct place. Is your
> mmm.ini file correct?
>
Well, perhaps not. I'm not sure. I did not touch it. It looks like
this:
[mix]
mixsize=10 tracks
restrict=3 tracks
style=20
variety=0
seed=1
[server]
proxy=0
host=
chaug wrote:
> I can't get Sugarcube to see the recipes.xml file (for MusicIP recipes).
> I'm not sure if this has anything to do with the specifics of the setup
> discussed here, but I thought I'd start here.
>
> According to 'this'
>
chaug wrote:
> I can't get Sugarcube to see the recipes.xml file (for MusicIP recipes).
> I'm not sure if this has anything to do with the specifics of the setup
> discussed here, but I thought I'd start here.
>
> According to 'this'
>
I can't get Sugarcube to see the recipes.xml file (for MusicIP recipes).
I'm not sure if this has anything to do with the specifics of the setup
discussed here, but I thought I'd start here.
According to 'this'
chaug wrote:
> Thanks for explaining. I'm starting to make sense of the different ways
> of starting deamons. However, I believe `systemctl` (which was used in
> the previous instructions) 'is also part of systemd'
>
bakker_be wrote:
>
> The difference between the 2 approaches has to do with the difference
> between the way services are launched: 'systemd<->sys v<->upstart'
> (https://fossbytes.com/systemd-vs-sys-v-vs-upstart/). Systemd is the
> most recent of the three and the default in Ubuntu since
chaug wrote:
> Thanks mate, I know exactly what you're talking about.
>
> One little addendum for anyone using a 64bit system (amd64):
> magicmusicserver wont execute because it is a 32-bit executable. In
> order to be able to execute 32-bit on your system, you need to do
>
> >
Code:
bakker_be wrote:
> After a lot of searching, trying, cursing, searching and trying again
> I've managed to solve my issue :)
>
Thanks mate, I know exactly what you're talking about.
One little addendum for anyone using a 64bit system (amd64):
magicmusicserver wont execute because it is a
After a lot of searching, trying, cursing, searching and trying again
I've managed to solve my issue :)
Below what I've done, for future reference for myself, and to offer an
alternative to what's detailed above. As with the above, my method is
based on the info in 'HaveTheKnowhow'
Sorry I can not offer more help. However you could look over the Ubuntu
Forum thread where I got my directions for the Cli install ,perhaps I
missed a step in my description. Start at post #9 with @nlee2.
https://ubuntuforums.org/showthread.php?t=2391064
Logitech Media Server Version: 7.9.1
SlimChances wrote:
> Was it the wine install of graphical MusicIP or the MusicIP you
> installed by cli?
>
> Not sure if I can help you further than the instructions I gave as they
> were basically dictated by someone on the Ubuntu forums and another
> website. They worked for me with both
bakker_be wrote:
> Somehow this doesn't seem to work on my fresh 18.04 install. I get
> "Connection refused", and if I check the status of the service it tells
> me "Active (exited)" :(
Was it the wine install of graphical MusicIP or the MusicIP you
installed by cli?
Not sure if I can help
SlimChances wrote:
> I was able to get MusicIP working with Ubuntu 18.04 (Bionic ) with the
> help of the Ubuntu Forums and 'HavetheKnow'
> (http://www.havetheknowhow.com/Install-the-software/Install-MusicIP.html)
>
>
> How to install MusicIP on Ubuntu Server Bionic Once you have
> installed
chaug wrote:
> For me, the problem is that I am running MusicIP as a headless install
> on my NAS so I don't have access to the kind of GUI you are referring
> to. Is there any way to do this (archiving) via the CLI?
You can run GUI programs on headless servers using ssh's x11 forwarding
chaug wrote:
> Thank you both for those hints. For me, the problem is that I am running
> MusicIP as a headless install on my NAS so I don't have access to the
> kind of GUI you are referring to. Is there any way to do this
> (archiving) via the CLI?
sorry, i have no idea
Logitech Media
SlimChances wrote:
> I never had much luck using the m3lib file from another install. If all
> your music has been archived (fingerprinted) it only takes 5 minutes or
> so for MusicIp to do the scan (i had about 2 tracks under MusicIP).
> If the music isn't archived it will take quite a
Hi
You can find out more about archive analysis and how to check it, on
this page;
https://www.spicefly.com/article.php?page=musicip-offline
Cheers
www.spicefly.com - ** Spicefly SugarCube ** - A hassle free acoustic
journey through your music library using MusicIP. Plus the finest
chaug wrote:
> Could you explain that part? I was going to do just that, given that it
> will take days, if not weeks for doing a complete rescan. I'm not sure
> how to do the archiving.
>
> If the problem with using the default.m3lib from another install is
> merely that the file paths might
SlimChances wrote:
>
> Do not use default.m3lib from another install. Rebuild library from
> archived fingerprints
>
Could you explain that part? I was going to do just that, given that it
will take days, if not weeks for doing a complete rescan. I'm not sure
how to do the archiving.
If the
I was able to get MusicIP working with Ubuntu 18.04 (Bionic ) with the
help of the Ubuntu Forums and 'HavetheKnow'
(http://www.havetheknowhow.com/Install-the-software/Install-MusicIP.html)
How to install MusicIP on Ubuntu Server Bionic Once you have
'installed LogitechMediaServer'
SlimChances wrote:
> OK I got it to work, kind of
>
> If I issue the command in terminal >
Code:
> > systemctl start mmserver.service
> >
> and then restart LMS I can create MusicIP Playlists.
>
> This is inconvenient and awkward and I don't
OK I got it to work, kind of
If I issue the command in terminal
Code:
systemctl start mmserver.service
and then restart LMS I can create MusicIP Playlists.
This is inconvenient and awkward and I don't think of much value. I
think the issue is the
That's great, but I still can't get mmserver to enable as a service
Code:
$ systemctl enable mmserver.service
mmserver.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mmserver
update-rc.d:
SlimChances wrote:
> @slartibartfast
>
> Thanks for your help. I am afraid I am a bit lost at this point. Looking
> at your appended code to rc.local I see it refers to a file in
>
> >
Code:
> > /opt/max2play/options.conf
> >
>
> but I don't
@slartibartfast
Thanks for your help. I am afraid I am a bit lost at this point. Looking
at your appended code to rc.local I see it refers to a file in
Code:
/opt/max2play/options.conf
but I don't have either a directory under opt or
Getting erros when I try to start rc.local.service
I am wondering if I need to set permissions and or ownership
differently for those two files from https://www.netroby.com/view/3895
Code:
david@MainSqueeze:~$ systemctl start rc.local.service
Job for
slartibartfast wrote:
> Looks like you need to create it yourself.
> https://www.netroby.com/view/3895
>
> Sent from my SM-G900F using Tapatalk
Thanks
I will give it a try
Logitech Media Server Version: 7.9.1 - 1518987734 @ Sun Feb 18 22:55:43
CET 2018
Operating system: Debian - EN - utf8
SlimChances wrote:
> Thanks, I gave that a go but the second file rc.local doesn't exist on
> my installation. I did create
> rc-local.serviceLooks like you need to create it yourself.
https://www.netroby.com/view/3895
Sent from my SM-G900F using Tapatalk
slartibartfast wrote:
> If it is similar to Debian see this thread.
> https://forums.slimdevices.com/showthread.php?t=108884
>
> Sent from my SM-G900F using Tapatalk
Thanks, I gave that a go but the second file rc.local doesn't exist. I
did create
rc-local.service
Logitech Media Server
SlimChances wrote:
> To use MusicIP with LMS it is necessary to start MusicIP before LMS
> starts when the computer boots. Unfortunately with Ubuntu 18.04 this
> does not seem easy or possible to do. I used Boot-Up Manager previously
> with 16.04 to change the order so mmserver and thereby
To use MusicIP with LMS it is necessary to start MusicIP before LMS
starts when the computer boots. Unfortunately with Ubuntu 18.04 this
does not seem easy or possible to do. I used Boot-Up Manager previously
with 16.04 to change the order so mmserver and thereby MusicIP started
before LMS but
44 matches
Mail list logo
