Jump to content

Recommended Posts

Posted

I have an issue regarding a H264 encoded 1080 file that is over 5GB big under Music Video category. It is simply not recognised by Emby, while I can access the file if it is shared from my NAS (and play it - i.e. it is not corrupted), and I have comparable files in the usual Movies folder which play fine.

 

I can access the folder from Emby, but the file is simply missing. This made me wonder, whether there are any limitations given the various categories (Movie, Series, Music, Music Video) in Emby?

Posted

Hi.  No, the size is irrelevant.

 

Why do you feel it is not recognized by Emby?  How is it named?  What is the file type?

 

Music Video Naming

Posted

It is named Author - Music - Part 1.mp4

 

I do not "feel" it is not recognized, it is not recognized. The folder when I go into it in Emby is _empty_.

Posted

What happens if you remove or change the " - Part 1" part of the name of the file?

Posted

Changed, no change. It is still not recognised. 

Posted

Exactly what did you change it to?

 

Can you please show us some screen shots of both your file system and the Emby UI showing the problem?

 

Have you tried searching for the item in Emby?

Posted

Ok, I think I know what is the problem. Basically, I noticed that none of my music video files are identified in Emby. The problem might be the following:

 

Emby category Music is defined with the following path:

/volume1/Music

Emby category Music Video is defined as:

/volume1/Music/Music Videos

It seems that if you define one category with a path and another category as a sub-folder, the two do not like each other. IMHO it would be good to provide a possibility to define exceptions, if required.

Posted

Ah, yes, that's correct.  You cannot have one library be a sub-set of another.

  • 2 months later...
Posted

try to re upload the file or maybe change the format

  • 1 month later...
doffactory
Posted

@@doffactory are you still having an issue?

 

Hi, not, as I moved the folder somewhere else. That solved the issue, however, it can be mentioned in any of your documentation that the practice noted in my initial message should be avoided.

Posted

Thanks for the feedback.

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...