It was not as blame, but if it is indeed, as MwC_Trexx is saying, that’s potential Bug/Quirks. And it then is a part of the QTS then I can address them and see if there is anything know about this. But I’m not sure who is responsible for Plex to work on Qnap. Is it Qnap or Plex creating the source?
Regards,
Hans
By the way,
I am now doing as you’ve said and enter /share/Full-HD-01 and such, manual and seems to work. Also for the /share/Mix-01/DVD and such is working. At the beginning this didn’t work, but I used all capital and need to use the exact same letter so MIX-01 didn’t work, but Mix-01 does work.
To add to what Trexx and Dane22 have said so far, I am the principle contact within Plex to QNAP. I work primarily on the OS/Packaging team in addition to my support duties here. We three work together to implement corrections or changes. I usually am the one who ends up pushing the buttons in the end and getting it into a build.
If we have a real QTS issue here, I will gladly take it to QNAP and champion anything which needs to be done… They are very responsive and quick to implement corrections we find.
@HansThuis Just to add to what @ChuckPa and @dane22 are saying. I didn’t mean to imply that it is a QTS issue.
I was just stating that QTS 4.4.x adds a new dimension to the troubleshooting as there are only 1-2 models currently that have that version of QTS in the field.
Just as QTS 4.3.5 involved changes both on QNAP’s side and Plex’s, it is unknown if QTS 4.4.x will require/need changes from one or both parties as well.
No problem. In the interim, one potential workaround would be doing a symlink from the main folder on your USB drive to an existing folder such as /share/Public.
So you would end up with /share/Public/usbmedia and then add /share/Public/usbmedia into Plex Library. Not the prettiest option, but you could try something like that as a work around for now.
I have done as dane22 said and typed the path in directly in the field like /share/Full-HD-01 and such and this seems to work. If I will get problems with this, then I will check this SymLink more and to see how to do exactly. Never heard of this blush: and dane22’s solution is working good enough for me.
As I think, not sure, that with a SymLink when the name (like DEV3304_2 and them) will point to a differrent drive, the SymLink will then also point to the wrong one or …??
