Home of the Squeezebox™ & Transporter® network music players.
Page 5 of 46 FirstFirst ... 3456715 ... LastLast
Results 41 to 50 of 457

Thread: Thecus N5200Pro

  1. #41
    Senior Member
    Join Date
    Apr 2007
    Posts
    378
    THanks iletunic for the great work. Thanks to Andreas as well for his past work.

  2. #42
    Junior Member
    Join Date
    Jul 2008
    Posts
    11

    problem with the artwork

    The module works ok, Squeezecenter is up and running, except for an issue with Albumart:

    [08-09-16 17:16:05.3022] Slim::Networking::IO::Select::select (250) Error: Select task failed: mkdir /raid/data/module/SQUEEZECENTER/system/SlimCache/Artwork/5/c/7: Permission denied at /raid0/data/module/SQUEEZECENTER/squeezecenter/lib/Cache/FileBackend.pm line 222
    [08-09-16 17:16:05.3513] Slim::Networking::IO::Select::select (250) Error: Select task failed: Error in tempfile() using /raid/data/module/SQUEEZECENTER/system/SlimCache/Artwork/d/c/9/XXXXXXXXXX: Parent directory (/raid/data/module/SQUEEZECENTER/system/SlimCache/Artwork/d/c/9/) is not writable
    at /raid0/data/module/SQUEEZECENTER/squeezecenter/lib/Cache/FileBackend.pm line 569

    Does the module sets the rights on those dir's? In that case i found a bug ;-)

    I removed the previous version of the module, didn't backup the cache dir, installed the new module, did a full rescan. All ok, except these errors.
    The user that owns the Arwork dir is Root, where the user on the other dirs (e.q. FileCache) is nobody.
    So i did a chown -R nobody Artwork from the /raid/data/module/SQUEEZECENTER/system/SlimCache/ dir, and that solved my artwork problem

  3. #43
    Quote Originally Posted by BramWithaar View Post
    The module works ok, Squeezecenter is up and running, except for an issue with Albumart:

    Does the module sets the rights on those dir's? In that case i found a bug ;-)

    I removed the previous version of the module, didn't backup the cache dir, installed the new module, did a full rescan. All ok, except these errors.
    The user that owns the Arwork dir is Root, where the user on the other dirs (e.q. FileCache) is nobody.
    So i did a chown -R nobody Artwork from the /raid/data/module/SQUEEZECENTER/system/SlimCache/ dir, and that solved my artwork problem
    Not sure why that happens, but simply restarting the server should fix it (ie. disable it, then enable again). That directory seems to be created by the scanner, so it's not present when the server first starts, and is changing the permissions.

    I'll make a new version which will explicitely make the Artwork dir before the server starts.

  4. #44
    Banned egd's Avatar
    Join Date
    Jan 2006
    Location
    Johannesburg, South Africa
    Posts
    1,692
    Quote Originally Posted by iletunic View Post
    Sounds like a good idea. Could you create the page at its appropriate location and send me the link? I'll try to fill the info as I find free time...

    Just to ensure everyone again, I will be building new modules for myself anyway, now that I set everything up, so I will also post them to onbeat.dk.
    Ok, I've created a Wiki entry located at http://wiki.slimdevices.com/index.ph...hecus_N5200PRO

    You will need to create a logon to the Wiki to be able to edit the page. Don't worry about formatting, just dump your text there and I'll pick it up and format it when you're done

  5. #45
    Just loaded the new module - seems OK except that the old problem of not playing m4as has resurfaced - white light on but silence.

    ISTR last time this was down to problems in one of the config files - there are a few old threads on this - the fix should be in there somewhere.
    One point I do recall is that the receiver is more fussy than softsqueeze as regards the -endian option for faad.

  6. #46
    Member
    Join Date
    May 2005
    Location
    Edmonton, AB
    Posts
    76
    This is great news. I'm finally getting back to upgrading to a new NAS and last winter the Thecus was on the short list. I have one quick and hopefully obvious question: The thread was titled N5200Pro but a few people are posting about their N5200s. Now AFAIK the main (only?) difference is the CPU speed and memory. Does the module work equally on both of them?

  7. #47
    Quote Originally Posted by BramWithaar View Post
    The module works ok, Squeezecenter is up and running, except for an issue with Albumart:

    [08-09-16 17:16:05.3022] Slim::Networking::IO::Select::select (250) Error: Select task failed: mkdir /raid/data/module/SQUEEZECENTER/system/SlimCache/Artwork/5/c/7: Permission denied at /raid0/data/module/SQUEEZECENTER/squeezecenter/lib/Cache/FileBackend.pm line 222
    [08-09-16 17:16:05.3513] Slim::Networking::IO::Select::select (250) Error: Select task failed: Error in tempfile() using /raid/data/module/SQUEEZECENTER/system/SlimCache/Artwork/d/c/9/XXXXXXXXXX: Parent directory (/raid/data/module/SQUEEZECENTER/system/SlimCache/Artwork/d/c/9/) is not writable
    at /raid0/data/module/SQUEEZECENTER/squeezecenter/lib/Cache/FileBackend.pm line 569

    Does the module sets the rights on those dir's? In that case i found a bug ;-)

    I removed the previous version of the module, didn't backup the cache dir, installed the new module, did a full rescan. All ok, except these errors.
    The user that owns the Arwork dir is Root, where the user on the other dirs (e.q. FileCache) is nobody.
    So i did a chown -R nobody Artwork from the /raid/data/module/SQUEEZECENTER/system/SlimCache/ dir, and that solved my artwork problem
    To followup on this, my proposed solution will not work, and restarting the server won't fix it. Every time a full rescan is done, the Artwork directory is removed and created again. Looks like the scanner.pl is not ran using the user and group of the running server. I didn't do extensive testing yet...

    Can someone from Slim devices or someone who knows the code comment? Where and how is the scanner.pl launched?

    BTW, I have a new module for 7.3 ready, just have to fix the Artwork issue. It is significantly redesigned, uses the new Custom.pm module, and you no modifications were done to the SC tarball (ie. you'll be able to just untar a new version into it to upgrade, and put Custom.pm into proper location, plus edit convert.conf if needed).

  8. #48
    Quote Originally Posted by Daryle Tilroe View Post
    This is great news. I'm finally getting back to upgrading to a new NAS and last winter the Thecus was on the short list. I have one quick and hopefully obvious question: The thread was titled N5200Pro but a few people are posting about their N5200s. Now AFAIK the main (only?) difference is the CPU speed and memory. Does the module work equally on both of them?
    Yes, it works on both.

  9. #49
    Junior Member
    Join Date
    Jul 2008
    Posts
    11

    Great !

    Quote Originally Posted by iletunic View Post
    BTW, I have a new module for 7.3 ready, just have to fix the Artwork issue. It is significantly redesigned, uses the new Custom.pm module, and you no modifications were done to the SC tarball (ie. you'll be able to just untar a new version into it to upgrade, and put Custom.pm into proper location, plus edit convert.conf if needed).
    That's great news!
    I'm quite happy with the 7.2 version, web ui is much faster than before, and the 5200pro seems a bit overpowered now ;-).

  10. #50
    Quote Originally Posted by iletunic View Post
    To followup on this, my proposed solution will not work, and restarting the server won't fix it. Every time a full rescan is done, the Artwork directory is removed and created again. Looks like the scanner.pl is not ran using the user and group of the running server. I didn't do extensive testing yet...

    Can someone from Slim devices or someone who knows the code comment? Where and how is the scanner.pl launched?

    BTW, I have a new module for 7.3 ready, just have to fix the Artwork issue. It is significantly redesigned, uses the new Custom.pm module, and you no modifications were done to the SC tarball (ie. you'll be able to just untar a new version into it to upgrade, and put Custom.pm into proper location, plus edit convert.conf if needed).
    Any chance you could fix the M4A issue while you're at it..?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •