Jump to content

Hide files with name beginning with a period "."


Recommended Posts

robertpolson
Posted

Because I use Macs in my house, OS X creates files starting with a period before the name. These files are used for thumbnails or whatever else OS X Finder needs them for. However, unlike Plex and Kodi, Ember indexes files that are names as "._Movie Name" and they show up as duplicated media files in the library. 

 

How can I tell Emby to not index files with "." in front of the name?

  • Like 1
kjp4756
Posted

As far as I can see there isn't a way to tell emby server to ignore the ._ files.  I think some code changes would be required for that to happen.

 

For the time being I simply delete the ._* files from my media directories.  I also try not to use finder to browse my media.  I try to do everything from terminal or on my server via ssh.

FrostByte
Posted

The only thing close that I'm aware of is the .ignore file in any folder will tell Emby to ignore all files in the folder

  • 4 months later...
raphaeldavid
Posted

Same problem, I looking for a solution.

Posted

Same problem, I looking for a solution.

 

what's an example of what you're trying to do?

raphaeldavid
Posted

I think the problem arises from the use of a MAC with a NAS.

 

Hidden files are created (.file, see attached file)

 

I can erase the file directly on my NAS, but it would be more practical to exclude this type of file.

post-43857-0-06614200-1445201866_thumb.jpg

Posted

can you show a screenshot of the directories so i can see what the files look like? thanks.

Posted

ok we are already supposed to be ignoring files that start with ._ , and this is out of the box with no configuration required. so i will have to retest that.

Posted

Can you click to the edit screen for some of the duplicates and see what the paths are? Thanks.

  • 3 weeks later...
Posted

Can you click to the edit screen for some of the duplicates and see what the paths are? Thanks.

 

Got the same issue, screenshot attached

 

563a0044e43ba_Bildschirmfoto20151104um13

Scott84Z28
Posted

If you had your movies in their own sub-folders, you wouldn't have this problem.

  • Like 1
Posted

are you on the latest version of the server? we have an ignore clause for this very thing.

Posted

I'm still on 3.0.5724.6, because it's the lastest edition available via FreeBSD Ports, i was too lazy to setup Emby by myself :P

 

Was the fix implemented after that version, so an update should fix it?

Posted

it has been there for a long time actually but it is best to try on the latest version before additional dev time is spent looking for a problem.

Posted

Alright, i will try to update sometime soon and will report if the problem still exists

raphaeldavid
Posted

I just installed the new version ... same problem.

post-43857-0-46685000-1446668828_thumb.jpg

post-43857-0-26188200-1446668829_thumb.jpg

Posted

Ok, i found it. it's resolved for the next release. thanks.

  • Like 1
  • 2 weeks later...
Posted

Ok, i found it. it's resolved for the next release. thanks.

 

I just installed build 3.0.5781.1 and still see the same issue.

Posted

Sorry, I should have clarified. I meant next major release. 5781.1 is just a path release with a couple fixes. I wasn't comfortable sending this fix straight to release, so it is going through the full dev, beta, stable cycle. By the same token, we will probably have another patch release next week and this will not be included in that either.

Posted

No worries. Happy to see it in the iOS app store. :)

 

Looking forward to an Apple TV version.

Posted

Thanks for the hard work guys!

 

Any idea when that next major release might come out?  Not having this feature is absolutely killing the usability of the product.  

raphaeldavid
Posted

The problem appear in the Movies section but not in my series...

  • 2 weeks later...
andreluizrangel
Posted

Same problem with me. Any idea when that next major release might come out? I was considering using the embed instead of plex but this functionality for Mac users is indispensable.

  • 1 month later...
Posted

Sorry, I should have clarified. I meant next major release. 5781.1 is just a path release with a couple fixes. I wasn't comfortable sending this fix straight to release, so it is going through the full dev, beta, stable cycle. By the same token, we will probably have another patch release next week and this will not be included in that either.

Has this bug been fixed? It was still present in 5786.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...