seashell 35 Posted January 19 Share Posted January 19 (edited) I have files with a ":" in them. Like "Collection: Something." Emby converts this to some other character to the left and below the previous character. Hopefully this example pulled from the edit metadata screen will come through whatever encoding the forum uses. Filename: Collection: E18 Displayed name and name in metadata: Collection E18 I don't know what character that is, and haven't seen anything in the naming that says don't use colons, but maybe I missed it as ":" is kind of a hard search. So what is this character and how do I get emby to stop converting a colon into it? Edited January 19 by seashell Typos Link to comment Share on other sites More sharing options...
Luke 37110 Posted January 19 Share Posted January 19 HI there, can you please provide a specific example along with screenshots to demonstrate? Thanks. Link to comment Share on other sites More sharing options...
seashell 35 Posted January 19 Author Share Posted January 19 Do you not see the character in my previous post? I do. And it's specific example cut and paste. Link to comment Share on other sites More sharing options...
Luke 37110 Posted January 19 Share Posted January 19 I really need to see complete file paths, screenshots in the emby web app, as well as a server log either from when it was first imported or from refreshing metadata on it. Without that this is just guesswork. Thanks. Link to comment Share on other sites More sharing options...
seashell 35 Posted January 19 Author Share Posted January 19 It appears to be the way samba handles colons in file names. I'm not sure why sometimes it shows correctly in emby and othertimes not. Attached is a log showing the filename with the translated colon. Not sure why the colon gets through sometimes and not others. It seems to be a problem in the "extras" "featurettes" etc. type folders but not at the top level, but that's just from scanning my library and not an exhausting search/test. embyserver.txt Link to comment Share on other sites More sharing options...
Solution pwhodges 1532 Posted January 19 Solution Share Posted January 19 Some operating systems (odd ones like Windows...) don't allow colons in file names, because they are used for drive letters. One should not expect a smooth experience if trying to use them in file names as many programs are written to work with multiple OSs, and so combine their restrictions. Paul 1 Link to comment Share on other sites More sharing options...
seashell 35 Posted January 19 Author Share Posted January 19 So it seems. It looks like the colons that do work are not in the filenames but things emby has added when it pulled the metadata. Link to comment Share on other sites More sharing options...
seashell 35 Posted January 19 Author Share Posted January 19 I'll go fix my filenames. Consider this closed. Sorry for any hassle. Link to comment Share on other sites More sharing options...
Luke 37110 Posted January 20 Share Posted January 20 Quote many programs are written to work with multiple OSs, and so combine their restrictions. true statement. Link to comment Share on other sites More sharing options...
seashell 35 Posted January 20 Author Share Posted January 20 14 hours ago, Luke said: true statement. Now if only there was documentation listing all these combined restrictions. It could even be on a page about library preparation or naming... 1 Link to comment Share on other sites More sharing options...
Luke 37110 Posted January 20 Share Posted January 20 Hi, yes that makes sense. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now