gchip7groundie

Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • 13. Juli 2018 at 13:11 #36568

    Heiner,
    thanks for your suggestions, but
    -v does not help. i believe that applies only to audio spectrum and view meter.
    please tell me exactly where i can get Jivelite source in order to recompile.

    17. Juni 2018 at 23:23 #36228

    UPDATE:
    i may have inadvertently found a fix!
    for some kind of clue, i was looking through the boot log via „journalctl -b“ command
    and noticed that there were many error entries for lirc (every second).
    so since i do not have a remote control,
    i completely uninstalled the lirc.

    ever since, through several boots,
    there is only one max2play player as expected.
    and of course, no more error logs every second.
    for now, all’s well on the max2play land…

    22. Mai 2018 at 15:14 #35809

    as stated before, even though the Filesystem Mount worked and i could see
    the USERMOUNT entry (using cifs) in /etc/fstab, LMS could not access the NAS folder.

    however, the manual nfs command did work!
    so i manually added the mount command in /etc/fstab and now, all is well.

    i’d like to suggest that you update the Filesystem Mount page to say that
    beginning // is not needed; in fact, it would result in error.
    also, perhaps evaluate the comment about cifs being the preferred choice.
    in my case, nfs was definitely the simpler and only choice that worked…..

    18. Mai 2018 at 19:20 #35773

    all players playing the same song? simultaneously?

    18. Mai 2018 at 15:09 #35762

    thanks antonio for the forum link. i did find it.
    no, i am not using the SpotifyConnect plugin. instead, i installed the SqueezeboxServer with Spotty plugin which has its own Connect option.
    but as you already know, there are issues with Connect at present.
    like you said, i see „max2play“ device appear and disappear.

    at the moment, i have the best luck with my own android app and OrangeSqueeze.
    they see „max2play“ and i can stream Spotify just fine.
    strangely, at one point, i could play two separate sessions, one on max2play and another on my windows desktop!
    and i do not have a family plan…

    hope either Spotify, Spotty or both can straighten things out, ‚cause things are quite confusing for the user.

    18. Mai 2018 at 13:33 #35757

    hi,
    as far as the Filesystem mount, the web interface does not work!
    even if it states that it succeeded.
    i had to do the manual mount using the „sudo mount nfs“ command. afterwards, LMS had no trouble going to the NAS.

    only way i have found to fix the Spotify-Connect start problem is to re-flash.
    i am not absolutely certain but the problem started when i started SqueezeLite.
    so now i have opted to use the Connect option of SqueezeBox Server and it is working somewhat.
    strangely, Spotify (both on android and windows) does not itself see the „max2play“ device,
    but my own app (on adroid using the web api) does see „max2play“.

    antonio… where is the Spotty forum?
    i would like to keep up with the fix, which hopefully will be soon.

    18. Mai 2018 at 13:21 #35756

    hello Heiner,
    as i reported on another thread, i had to manually execute the mount command (i.e., „sudo mount“…)
    nothing to do rights.
    please check the web ui version of the Filesystem mount; even if it states a success,
    it did NOT work.

    17. Mai 2018 at 19:36 #35750

    for your info,
    i finally succeeded using Remote Control and directly using the following command:

    sudo mount -t nfs <IP Address>:/<DriveVolumeName>/<NameofShare> /mnt/<FolderyouCreated>

    after this, LMS is actually scanning the NAS files!
    so, please, Max2Play needs to correct the Filesystem-Mount function.
    you are making lot of people lot of headaches!

    17. Mai 2018 at 19:15 #35749

    hello,
    mount goes successfully with the following message:
    Directory created: /mnt/volume1/Music
    Mountpoint successfully added

    but yet, when LMS is set to scan /mnt/volume1/Music,
    it sees no files.
    yes, the /mnt/volume1/Music folder shows, but it’s not really Synology NAS.

    what is going on?

    17. Mai 2018 at 17:29 #35747

    hello, i wish to make an update.
    i have now installed the Squeezebox Server (SS) and it solved my Spotify Connect problem
    Squeezebox Server with the Spoty plugin does the Connect function nicely, so I do not need the separate plugin.

    only issue remaining is having the SS process the mount point to my NAS drive which contains all songs.
    also, for those trying to understand SqueezeLite, you do need a controller (i use Orange Squeeze on android)
    in order to have an UI and see your music library and of course, play music.

    hong

    17. Mai 2018 at 17:21 #35746

    hello,
    i was having similar problems with NAS mounting, but following Stefan’s instructions,
    was successful. but when i started the rescan process on Logitech Media Server on the mounted folder, /mnt/mpd,
    it finishes immediately having processed just 1/1 directories.

    of course, the /mnt/mpd should point to my NAS drive full of CD directories of some 7000 songs.
    so, why is the mount not really pointing to NAS?

    thank you for any pointers…
    hong

    17. Mai 2018 at 12:43 #35742

    hello,
    on initial boot and install of Spotify Connect worked just fine.
    however, auto-start on boot did NOT work. i had to manually start it each time.

    then, i was playing with squeezelite but without the auto-start.
    it always came back with the following error:
    [03:40:00.965570] test_open:310 playback open error: Device or resource busy
    [03:40:00.965912] output_init_common:382 unable to open output device

    then, i tried to start Spotify Connect manually and now,
    it fails with error:
    Trying to launch … NOT successful Click here to show detailed information
    error: Unrecognized option: ‚onstart‘

    so, now i am faced with two problems.
    please help with some advise…

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