Difference between Kodi on M2P andf OpenElec?

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Difference between Kodi on M2P andf OpenElec?

This topic contains 2 replies, has 2 voices, and was last updated by  Hammerhead 3 months, 2 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • 7. July 2016 at 2:00 #21278

    I’ve been having a great deal of difficulty trying to get M2P working on my Pi. There always seems to be a problem with losing the WiFi connection, expanding the SD card doesn’t seem to work properly, and other issues… like… wouldn’t it be a good idea to give us a URL for where to download .deb Kodi packages instead of having us guess at which one to use?

    So, I’m wondering if there is any real advantage to using M2P over the HiFiBerry OpenELEC/Kodi installation. Can someone explain what the advantage of M2P might be that I would want to continue getting frustrated?

    8. July 2016 at 15:24 #21341

    Hi Hammerhead,

    well, that doesn’t sound too good… we updated the latest prebuild-sd-card-images to version 2.32. Maybe you start again with a fresh image. SD-Card expansion and wifi should work without any problems (as long as you start the expansion before the card is full). If you have a Pi 2 and not a Pi 3 with buil- in wifi, it might depend on your wifi-stick if anything is not working correct (e.g. disconnects). The kodi package is part of the image – no need to install anything.

    So what are the major benefits of Max2Play: if you are only using you player for Kodi via HDMI and nothing else, you can take OpenELEC or some other distribution. If you want a flexible system with support of different players (Audioplayer, Multi-room Setup) and a lot of other things (see our features / plugins page) you won’t find a system that is this easy to configure. In other words, Kodi is just one little part of Max2Play.

    8. July 2016 at 18:04 #21391

    I bought the Pi3 and HiFiBerry DACpro with intent to task it exclusively as a ‘smart’ client running Media Monkey on the Pi and pulling FLAC from my NAS which is running Emby server for my modestly high-end audio only system.

    My plan was to install Media Monkey on the Pi, and leave the DB also on the NAS, so that there would be consistency of tags, play lists and whatnot. Unfortunately, I found out that’s not possible because MM does not run on Pi, it only runs on Windows or WINE, so I’m screwed. Musicbee would be a strong 2nd choice, but again – not on Pi – Windows only. Even if I could get some flavor of Windows (even Windows IOT) running on the Pi, the problem would then be driver support for the HiFiBerry DAC, so again… screwed.

    As a secondary plan, I tried to use M2P and gmediarenderer as a DLNA client, and control it MediaMonkey on my laptop and/or android phone, but multiple attempts at installation failed miserably; in other words, screwed. After banging my head against the wall with M2P, I finally just went with the HiFiBerry OpenELEC/Kodi image. It just works. But I would like to keep my options open and consider another player – or hopefully one day get MediaMonkey or MusicBee running on the Pi, but I’ve had no end of troubles with M2P. And yes, I am using version 2.32.

    If I could at least get M2P and gmediarenderer or preferably upmpdcli working on the Pi, then I could install MediaMonkey on my PC, move the DB to the NAS, and send the audio to the Pi using my laptop or phone as the control point. But again, I’m having no manner of luck at all.

    It’s terribly frustrating. Any help is appreciated.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Register here