New files added but not shown in UMS until reboot of program

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
wazer
Posts: 35
Joined: Fri Feb 01, 2013 4:52 am

New files added but not shown in UMS until reboot of program

Post by wazer »

Hi so when adding files to the directory UMS its listening to and running, they wont show up until i have rebooted UMS, i have had this annoying little problem on my PS3,Sony TV, Samsung TV & WD TV, ever since i can remember, its been all version that i have tried 1.x 2.x 3.x.


Is there any fix or is it possible for you guys to add an options menu that you can press to actually restart/refresh the service/program from the TV Screen?
AngelShine
Posts: 12
Joined: Mon Feb 03, 2014 3:07 am

Re: New files added but not shown in UMS until reboot of pro

Post by AngelShine »

I have the same annoyance, there is a 'Scan all shared folders' button on the Navigation/Share Settings tab, but the button is always grayed out for me.
Sometimes I notice after starting UMS that I was missing a subtitle file, and after adding it I have to restart it for it to see it.

Is this intended? Anything we're missing?
ExSport
Posts: 595
Joined: Wed Oct 10, 2012 1:57 am

Re: New files added but not shown in UMS until reboot of pro

Post by ExSport »

If you will add new folder which is not configured in UMS, restart is needed. If any multimedia file is added to folder or subfolder of already shared folder in UMS, restart is not needed.
In this case new files are automatically added to the bottom of list.
About subs, what I remeber from past, it requires UMS restart so UMS can detect them.
If your mangnification glass is grayed, it is probably due to not enabled Media Cache in GUI.
Also in GUI you can find settings for showing "VIDEO SETTINGS" folder so you can browse it from renderer and use built-in options. I expect "restart server" will be there 8-)
wazer
Posts: 35
Joined: Fri Feb 01, 2013 4:52 am

Re: New files added but not shown in UMS until reboot of pro

Post by wazer »

ExSport wrote:If you will add new folder which is not configured in UMS, restart is needed. If any multimedia file is added to folder or subfolder of already shared folder in UMS, restart is not needed.
In this case new files are automatically added to the bottom of list.
About subs, what I remeber from past, it requires UMS restart so UMS can detect them.
If your mangnification glass is grayed, it is probably due to not enabled Media Cache in GUI.
Also in GUI you can find settings for showing "VIDEO SETTINGS" folder so you can browse it from renderer and use built-in options. I expect "restart server" will be there 8-)

I'm just adding files in the already predefined folder, and they are not shown at at all, will check that restart server options out right now ;)
tPW
Posts: 1
Joined: Sun Feb 09, 2014 5:22 pm

Re: New files added but not shown in UMS until reboot of pro

Post by tPW »

I have the same issue, I can't see any new files that I have added to a folder

Does UMS scan them every couple minutes or is it done on the fly? I waited about a half hour and the new file isnt there still, but a server reset fixed that.

Also renaming a folder causes it to disappear so I know something is being removed but its unable to add new data.

It would be nice if UMS had a scan folders every 5 min feature which would help with users who add data constantly
ExSport
Posts: 595
Joined: Wed Oct 10, 2012 1:57 am

Re: New files added but not shown in UMS until reboot of pro

Post by ExSport »

UMS shows new files immediately when UMS receives request for refresh/showing folder.
To force refresh, you need to go back outside folder and go inside again to see new files added to the end of list.
If you can't see new files, it can be bug but more probably problem of renderer itself. It is possible that renderer cached folder list and when browsed outside and back it doesn't send any request to UMS and show cached list without asking UMS.
Debug.log in TRACE mode can say more.
Post Reply