All Activity

Hi. What happens if the stream really did go down permanently?

If the two servers are using the same key it should be one.

That can change at any time. I'm not saying this is impossible. I'm saying it isn't a straightforward as it might seem now that collections AND playlists can be sorted in different ways.

I just wanted to share my recent experiences related to some network changes I made in home network. I have had a 1Gig symmetrical fibre ISP connection for a few years now and have always struggled with remote clients selecting a very conservative "Auto" quality setting. Manually adjusting the quality setting to a higher level to force direct play almost never resulted in issues related to limited bandwidth. Last month I made the switch over to a Ubiquiti gateway and switch from a OpnSense router and Netgear switch. I never had issues with achieving my advertised line speed on my old setup so I figured all was good. Since switching over to my Ubiquiti setup, Emby's "Auto" setting has been much more reliable. I don't have tangible evidence to back it up but it just works better now. So either there was a change on the Emby backend around this same time or my new networking setup has much lower latency. I'm using the same DNS servers as before and nothing else in my setup has changed.

Yes, if the browser doesn't support FLAC, it should be transcoded. But I don't want FLAC to be transcoded for all browsers in general.

Happy to hear that. The next stable release will include the ARM64 package. Thanks a lot for testing.

Thanks, android log attached emby_android_1784137960830.txt

Hi, what makes you think this? How did you setup port forwarding in your router?

But that's not what you said in the expected behavior section of your original posting.

I can confirm that the problem is resolved when using the ARM64 build beta. The beta version opens as expected and both GUI and playback are stable and responsive. I'll keep using the beta until there's a public release. Thanks very much!!

Interessting, thanks.

Vid, Using Wifi could maybe be an issue. 2.4 Ghz can broadcast much farther thn 5 Ghz. Also maybe your neighbor is using the same Wifi Channel and causing your Wifi to get some interference. You can check this with Mobile apps that scan for Wifi. Maybe just changing te Wifi channel and or Ghz band on your router might help.

here are logs from 13-15 ... I think... Downloads.zip

Which browser supports flac https://caniuse.com/flac

Great - will do. Thanks!

The new beta has been published and it has an ARM64 package now. Please follow the instructions on the beta portal to get it installed.

I have a related question. If the same device connects to two different Emby servers, is it counted as one device or two? For example, if I have one server running the stable version and another running the beta version, and I connect to both from the same smartphone, how many device slots does that use?

That's more or less when I noticed it was happening to me too. I got to Kodi to watch something and it said the Emby server was offline... I checked Synology and it was. Had to start it manually a few times. Now I have to start it manually at least once a day, as sometimes when this crash happens Synology package manager doesn't bring Emby back up automatically. Sometimes it does. But i take this is a Synology thing and not an Emby thing. I thought about setting a job to restart emby once a day, but that's pointless. I rather work towards a real solution, that's when I started collecting logs. Now sa2000 has all my logs. Hopefully he (she?) can see something I'm not seeing and find out what's causing this.

@sa2000I have sent you my logs via DM, and I also sent you my script that's collecting the statistics. I have been scanning every 30 minutes since I installed emby years ago and never had any issues. That's mostly because the hardware is powerful and largely underutilized. I have 32G of ram and until this problem started emby had never used more than 1GB RAM even under heavy stress (serving simultaneous 4K videos to all four KODIs in the house while scanning at the same time). This points to something new, introduced by a plugin or one of the latest updates, as I keep my emby version up to date as much as I can. Thanks for looking at my logs! I hope they're useful and lead to a solution of this issue to us all!

But I want FLAC to be played by default. I don't want to have to convert the format every time just because of a browser.

See attachment, one folder automatically plugged in an image while the other did not.

What was the solution?

Hi that’s odd. The browser must be reporting that it supports it. The next release will have a section in settings to force transcoding of certain formats so you can use that.

The date issues for non-US users also bothered me. Air Date Fixer is created from the ground up. The Alpha plugin is about 97% done, just a few more tweaks.

Description: I found what appears to be an issue with codec detection or playback profile matching in Emby Server 4.9.5.0. Environment: Emby Server: 4.9.5.0 Platform: ReadyNAS (Linux) Client: Emby Web Browser: Sony Vewd Browser (OMI) User-Agent: Mozilla/5.0 (Linux; Android 12; BRAVIA 4K VH22) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.6533.120 Safari/537.36 OMI/4.25.1.92.StableAVB_Sony.1 Problem: The Sony Vewd browser is unable to play FLAC audio. However, Emby does not transcode FLAC to AAC (or another supported codec). Instead, it serves the original FLAC file directly, causing playback to fail. Audio transcoding is enabled for the user. Expected behavior: Since the browser does not support FLAC playback, Emby should automatically transcode the audio to AAC (or another supported format). Actual behavior: The playback request is made through the UniversalAudioService with: AudioCodec=aac but the server responds with: Content-Type: audio/flac The original FLAC stream is sent instead of a transcoded AAC stream. Relevant log excerpts: User policy: EnableAudioPlaybackTranscoding: True GET /emby/Audio/.../universal ... AudioCodec=aac Response: Content-Type: audio/flac Additional information: The issue only occurs with the Sony Vewd browser. Other clients (Android TV app, desktop browsers, etc.) work as expected. It appears that Emby incorrectly assumes that the Vewd browser supports FLAC playback, or the browser's playback profile incorrectly advertises FLAC support. Could this be a bug in the Vewd browser device profile or codec detection logic? embyserver_sanitized.txt