SOLVED: Umlaut

[Ice]

The Log shows several entries like this one:

2023-08-06 02:31:14 filemnt/media4/D/Die Toten Hosen/Im Auftrag des Herrn/9 - W�nsch DIR was.mp3: No such file or directory
error from daemon in stream: Error grabbing logs: invalid character '\x00' looking for beginning of value

why can't the umlauts of existing files be interpreted correctly?

[Venson]

Hey @Ice

What is your OS?
I would be surprised if that is actually related to the umlaut, do other titles without umlauts in the same folder be detected?

[Ice]

As far as i can see are all files dedected except the one's with umlaut.
The files with umlaut are listed in the Playlist but cannot played (pls see attachment), instead it shows an error message Like: 
Playback error
This client is not compatible with the media and the server is not sending a compatible media format.    

Jellyfin runs in a Docker-Desktop (windows 10) Container (linuxserver/jellyfin) Vesion 10.8.10.

[Ice]

There are some other errors in Log:

2023-08-06 02:29:58 [flac @ 0x55ca4267cb00] Discarding ID3 tags because more suitable tags were found.
2023-08-06 02:30:08 [00:30:08] [ERR] [47] MediaBrowser.Providers.Music.AudioMetadataService: Error in ffprobe
2023-08-06 02:30:08 MediaBrowser.Common.FfmpegException: ffprobe failed - streams and format are both null.
2023-08-06 02:30:08    at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.GetMediaInfoInternal(String inputPath, String primaryPath, MediaProtocol protocol, Boolean extractChapters, String probeSizeArgument, Boolean isAudio, Nullable1 videoType, Boolean forceEnableLogging, CancellationToken cancellationToken)
2023-08-06 02:30:08    at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.GetMediaInfoInternal(String inputPath, String primaryPath, MediaProtocol protocol, Boolean extractChapters, String probeSizeArgument, Boolean isAudio, Nullable1 videoType, Boolean forceEnableLogging, CancellationToken cancellationToken)
2023-08-06 02:30:08    at MediaBrowser.Providers.MediaInfo.FFProbeAudioInfo.Probe[T](T item, MetadataRefreshOptions options, CancellationToken cancellationToken)
2023-08-06 02:30:08    at MediaBrowser.Providers.Manager.MetadataService2.RunCustomProvider(ICustomMetadataProvider1 provider, TItemType item, String logName, MetadataRefreshOptions options, RefreshResult refreshResult, CancellationToken cancellationToken)
2023-08-06 02:29:58 [mp3 @ 0x55a4fea19b00] Estimating duration from bitrate, this may be inaccurate

Such entries [ERR] are repeated every few hours. Unfortunately, no file name is given to remove or correct the file. Therefore i cannot say if this is also related to the problem with "umlaut".

[Ice]

The log shows other strange entries:

2023-08-06 02:28:51 jellyfin | [mp3 @ 0x560fee8d6b00] Estimating duration from bitrate, this may be inaccurate
2023-08-06 02:28:51 jellyfin | [mp3 @ 0x559c182d8b00] Estimating duration from bitrate, this may be inaccurate
1970-01-01 01:00:00 error from daemon in stream: Error grabbing logs: invalid character '\x00' looking for beginning of value

the last entry has a wrong date. An invalid character appears to result in an error.
The previous entries only go up to 06 August but no further. Today is 13 September, where are the log entries between 6 August and 13 September?

[Ice]

More Errors:
[2023-09-27 09:22:51.309 +00:00] [ERR] [62] Emby.Server.Implementations.IO.LibraryMonitor: Error in Directory watcher for: "/mnt/media4"
System.IO.FileNotFoundException: Could not find file '/mnt/media4/D/Dire Straits Discography/Dire Straits - Communique/Dire Straits - Communiqu�'.
File name: '/mnt/media4/D/Dire Straits Discography/Dire Straits - Communique/Dire Straits - Communiqu�'
[2023-09-27 09:22:51.309 +00:00] [INF] [62] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/mnt/media4"
[2023-09-27 09:22:52.923 +00:00] [INF] [62] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "/mnt/media4"

I did change the name of the folder Communiqué to Communique but now the filename has also the kind of "Umlaut" 'é' ...

[skribe]

I saw a user with a similar issue the other day related to special characters, but it did not seem related to Jellyfin in the end. The very same file names he was using were working on my server, but his could not find the files. We ultimately decided that it was either the OS or Docker that was having an odd interaction. He suspected it might have been related to WSL.

[Ice]

This is possible because in Docker i can see the Files like that as an example:
 
"Der Dritte Raum - Klubraum - 03 - H�r mich.mp3"

This way it look also in Jellyfin... So I have to look with Docker-Desktop runing under win10. Do you have a hint on where to look?

[skribe]

Unfortunately not. I don't use it myself, and the other user didn't really provide any other information. They just went off to research the issue.

[Ice]

I have found a solution, after long research and many tests.
Docker-compose.yaml looks now like that:

version: '3.5'
services:
  jellyfin:
    image: linuxserver/jellyfin
    container_name: ICE-JELLYFIN
    hostname: ICE
    network_mode: 'bridge'
    ports:
      - 8095:8095
    volumes:
      - D:\Applications\Jellyfin\config:/config
      - D:\Applications\Jellyfin\cache:/cache
      - D:\Daten/Video:/mnt/media
      - media2:/mnt/media2
      - media3:/mnt/media3
    restart: 'unless-stopped'
volumes:
  media2:
    driver_opts:
      type: nfs
      o: "addr=192.168.1.54,ro"
      device: ":/data/Videos"
  media3:
    driver_opts:
      type: cifs
      o: "username=<username>,password=<password>,iocharset=utf8"
      device: "//192.168.1.55/video"

The solution is the added ",iiocharset=utf8" BUT to take this effect you have to recreate the volumes in docker-desktop.
Important: In Docker desktop, you need to delete the container AND any associated volumes. Running the docker-compose up -d command will recreate everything.

media is an example to include a host local folder with media.
media2 is an example to include a shared folder on a nas configured with nfs-access.
media3 imcludes a cifs share on annother nas (on this share/volume the problem occured).