I'll quote this, since it regroups what I wanted to address:
- starting on reboot: yeah, I suspected the .rc, but fact is, it works on DSM 3.2 beta, probably because they thought of escaping spaces.
Since 3.2 will get more and more accepted, I'll just recommend you to upgrade the DSM. And it's Lion-compatible also. :D
- inteferring with metrics display: believe it or not, Elan asked the super Synology software support, and the response was "we don't support spaces". Again.
They plan to fix it in a next DSM release, so the step for "starting on reboot" will just be repeated. :)
- Icon doesn't work anymore: I made the "if...else..." because someone in the first Synology thread used a different network configuration, and my old one didn't work.
My bad, I hoped it would work from the code I was given. I'll fix it for the next release.
can anyone confirm the folder issue in the films section?
my paths are like this
volume1/media/series
volume1/media/films
in the films folder are subfolders for film bundles like terminator or rambo
volume1/media/films/terminator
and within there are the mkvs
i have figured pms films section to watch the volume1/media/films folder
so far so good
all film bundles like terminator or rambo are scanned successfully
but pms scans ONLY the subfolders like terminator or rambo and the mkvs within
NOT the mkvs stored in the volume1/media/films folder
any ideas guys?
regards
sonic
sonic, you’re not the first person on this thread to have this issue.
Last time, it wasn’t a user rights issue, so this is probably something to ask Elan about.
Try to create another thread in Bugs -> Plex Media Server for Linux, explaining your issue; Elan may check it out or see something obvious.
oh, ok
haven’t seen anyone else posting this issue
i´ll do so
It was a little tricky, it's in the old thread: http://forums.plexapp.com/index.php/topic/26663-dont-forget-synology/page__view__findpost__p__188634
Since you're the second one, I wanted to make a different thread.
Just to be sure it's not the known issue: is there a special character (other than space, dash, numbers and normal letters, accents are no good) in one of the movie names in volume1/media/films ?
Those make the Scanner crash right now (Unicode encoding, thou art a harsh mistress) and often explains the "nothing is showing up when I scan" cases.
there are too many films for that issue 
Is anyone having a problem with scanning only one folder? i.e. it’s auto scanning me Movies folder, but not my TV shows folder. i have to remember to do that manually all the time.
I would refer to Nudgenudge's post above about the special characters. I don't know of a way to disable auto scanning on 1 section and not the other. Sounds like a filename or folder name issue to me.
It's not a special character issue, as none of the TV shows have any special characters in them. Plus, when I go into the Plex web admin and scan manually, it will correctly scan the added episode.
One other thing, where is the Plex folder now? It’s not showing up in my file manager. Has it moved?
Ignore me - found it via terminal. Is it supposed to be hidden from view in the File Browser?
If you are referring to the “Update my library when changes to my folders are detected” option. I have not had that working on Synology yet. I have set “Update my library hourly” option instead and it seems to be working correctly.
I recall someone saying that the monitor portion is not working yet.
While streaming with Plex App on iPad and iPhone (4) the stream stops after 10 minutes. Seems to be pretty exactly 10 mins all the time. First I had my HDD sleep on 10 minutes so I thought that was too suspicious. After changing to sleep never still the same.
Streaming Series like White Collar 720p mkv files for example.
Local Wi-Fi 8Mbps (but since it’s 720p that should make no difference)
I had it as low as 2Mbps and same 10 mins.
Direct Streaming is switched on.
Anyone more having this symptoms?
Regular Plex clients on MacBook and iMac are just fine.
I wanted to do a few tests, but real work got in the way each day.
I think this could be that the transcoding file gets too big for /tmp.
What you could do to test is to create a folder /volume1/Plex/TempTranscoding via SSH (or File Manager), do:
chown plex:users /volume1/Plex/TempTranscoding
and then edit the file we mentioned earlier:
vi /var/packages/Plex\ Media\ Server/scripts/start-stop-status
to change this line:
su plex -s /bin/sh -c "export LD_LIBRARY_PATH=/usr/local/plex/;ulimit -s 3000;/usr/local/plex/Plex\ Media\ Server &"
to this line:
su plex -s /bin/sh -c "export LD_LIBRARY_PATH=/usr/local/plex/;export TMP_DIR=/volume1/Plex/TempTranscoding/;ulimit -s 3000;/usr/local/plex/Plex\ Media\ Server &"
Then, stop/restart the Media Server.
This allows the transcoding file to be located in the main filesystem.
I don't know how it works for performance or just plain stability, but if it does work, I'll edit it for future packages.
I installed the latest package on my DS1511+ but my movies wont show in Plex on my Mac Mini.
Other servers show correctly.
Any ideas on how to fix or troubleshoot this?
Check and double-check to make sure you don't have any foreign symbols and/or illegal characters in your file names.
I removed all library sections and created a new named 123 with one movie called robots.avi and the library still does not show in the player or my iPad. It works if I ad it manually in my iPad.
Any other suggestions?
Does the user 'plex' have read permission to the said folder(s)?
Ok, doesn't seem to be the scan that's failing, and that you can se it if you add the IP on your iPad, it's probably Bonjour/Avahi discovery.
However, I don't really have a workaround for this, except for "disconnect/reconnect/if it doesn't work, reboot". Bonjour can be a prissy ■■■■■ sometimes.
What do you mean by disconnect/reconnect?
Is it possible to check if avahi is running somehow?
Edit: I checked with a Bonjour browser and the NAS does not publish itself. My windows and OSX servers shows in the list.
Ok, so that's stranger.
if you do a "ps w", do you see the avahi-daemon process?
And in any case, try to do "avahi-daemon restart", and check again afterwards.
