AJV20 71 Posted Friday at 05:52 PM Posted Friday at 05:52 PM Please add support for the new iPhone Duo. It would be a bigger plus if you guys use the Apple native buttons as well
Luke 43443 Posted Friday at 05:58 PM Posted Friday at 05:58 PM HI, the app should already run. What features would you like to see?
Neminem 1972 Posted Friday at 05:59 PM Posted Friday at 05:59 PM Curious what's wrong with it. Is it not displaying the right way?
AJV20 71 Posted Friday at 06:02 PM Author Posted Friday at 06:02 PM (edited) The entire screen space is not being used. Also for the outer screen the buttons are usually on the ride side now there’s also more positions the duo can open to that usually affect video apps differently Edited Friday at 06:03 PM by AJV20 1
OSBuckeyes4Life 14 Posted Saturday at 11:24 AM Posted Saturday at 11:24 AM (edited) Hi, another iPhone Duo user here. Emby looks fantastic on it, but I’m having trouble getting the app and player to use the whole display. I’m on Emby for iOS 2.2.59, with Emby Server 4.10.2.0 running in Docker on Arch Linux (rolling release), kernel 7.2.11-arch1-1. Home changes after playing a video I noticed something interesting that might help narrow this down. When I first open Emby, there’s a separate area for the clock and battery at the top or on the right, depending on how I’m holding the phone. Home doesn’t use that part of the screen. Open Emby and look at Home. The separate status area is visible. Open a video and let it go into fullscreen playback. Go back to Home. Now Home uses the full display and that separate top/right area is gone. I haven’t restarted the app in between. It looks much better at that point, so I’d like it to open that way from the beginning instead of having to play something first. The screenshots show the before and after. Could you look at what changes when the player enters fullscreen, and why Home only picks up that layout afterward? I wonder if the status-bar or safe-area settings aren’t being updated until the player changes them. Fullscreen playback and zoom Zooming is another frustration. It makes the picture bigger and crops it, but it doesn’t seem to make the playback area itself use the available screen properly. I understand that a widescreen movie can have black bars on a differently shaped display. I’m not asking for the picture to be stretched. I’d like the player to use the full available area, with Fit preserving the picture and Fill being a separate choice if I want cropping. The normal movie black bars in the playback screenshot aren’t the issue I’m reporting with Home. Could this be checked on both the inner and outer displays, including rotation and opening/closing the phone? Would the native Apple fullscreen controls help, or does this need a change to Emby’s layout? Navigation dock disappears in portrait The bottom navigation dock with Home, Search, Downloads and Movies only shows when I hold the phone in landscape. When I turn it to portrait, the dock disappears. Could you check that too? I would expect those navigation options to stay available in either orientation. Logs I’ve attached the identifiable playback activity from the previous 12 hours, plus a shorter log covering the more recent test. They include HLS requests and successful HTTP 200/206 responses. There’s also a separate download/sync log in case it helps, but that isn’t live-streaming activity. The playback-info requests reference 4K files at 3840×2160, 3840×2076 and 3840×1608. Some of those requests are prefetch calls, so they don’t all represent active playback. I haven’t found anything in the server logs that explains the fullscreen change; the before/after screenshots are probably more useful for that. Personal details and credentials have been removed from the logs. Screenshots duo-01-initial-home-landscape.png duo-02-initial-home-portrait.png duo-03-playback-view.png duo-04-home-after-playback.png Log files duo-playback-layout-followup-sanitized.txt duo-playback-12h-sanitized.txt duo-download-sync-12h-sanitized.txt Could you please take a look and let me know if there’s anything else that would help reproduce it? I’m really enjoying how Emby looks on the Duo. Getting these fullscreen and layout issues sorted would make it even better. Thanks! Edited Saturday at 11:52 AM by OSBuckeyes4Life
OSBuckeyes4Life 14 Posted yesterday at 12:18 AM Posted yesterday at 12:18 AM Update: the outer/front screen has the dock/viewport problem too. On the outer screen, Emby opens with the dock down the left. If I start a movie and rotate into portrait, the black dock area stays across the top. The video is no longer centered and gets pushed down. The home-screen screenshot also shows the app leaving part of the display to a black system/status area instead of using the full available viewport. On the outer screen, I want the app to open full-screen and remain full-screen through playback and rotation, without retaining a sidebar-sized black strip or offset from the previous orientation. The movie should fit and stay centered in the available viewport with its original aspect ratio; I am not asking to stretch or crop it to eliminate normal cinematic letterboxing. I reproduced this with The Super Mario Galaxy Movie and Jurassic World Rebirth. Setup and playback stats - Emby Server 4.10.2.0, Linux x64; Emby for iOS 2.2.59. The request user-agent reports iPhone OS 18_7. - Remote access through Proton during these two tests. The server applied a 12,000,000 bps streaming limit, despite PlaybackInfo requests advertising MaxStreamingBitrate=200,000,000. - The Super Mario Galaxy Movie: MKV, 3840x1608 HEVC Main 10, BT.2020/PQ, 23.976 fps; E-AC-3 5.1 at 1,024 kbps/48 kHz. Library runtime 1:38:14.889, file size 11,130,095,130 bytes, reported total bitrate 15,104,739 bps. Server reports the source exceeding the 12 Mbps DirectStream limit. Playback start was reported at 0 ms, stop at 3,007,296 ms (50:07.296), 35.789 seconds apart in the server log; that position jump is not 50 minutes of continuous playback. I did not find a matching FFmpeg log establishing the actual output path for this movie test. - Jurassic World Rebirth: MKV, 3840x2160 HEVC Main 10, BT.2020/PQ, 23.976 fps; TrueHD 7.1/48 kHz. Library runtime 2:13:40.012, file size 20,903,992,246 bytes, reported total bitrate 20,851,831 bps. HLS transcode reason: ContainerBitrateExceedsLimit. Output: 1920x1080 H.264 Main/BT.709 at 11,616 kbps, AC-3 5.1 at 384 kbps, MPEG-TS segments, 3-second segment target. Two FFmpeg launches occurred for the same playback session. Playback resumed at 25:45.335 and stopped at 26:15.787 (30.452 seconds of position advancement across 40.013 seconds of server-log time). The server confirms the playback sessions and transcoding details, but it does not capture the client viewport or dock state. The screenshots show that part of the problem. Server/FFmpeg excerpts Server-log excerpts (relative timestamps; selected records for the two movie tests). Emby Server 4.10.2.0; Emby for iOS 2.2.59. T+000.148s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+000.150s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+000.150s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+001.834s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+001.836s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+001.836s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+001.925s Info SessionManager: Playback start reported by app Emby for iOS 2.2.59 on iPhone Duo playing The Super Mario Galaxy Movie. Position: 0 ms. PlaySessionId: [SESSION] IsPaused: False T+037.714s Info SessionManager: Playback stopped reported by app Emby for iOS 2.2.59 on iPhone Duo playing The Super Mario Galaxy Movie. Position: 3007296 ms. PlaySessionId: [SESSION] IsPaused: False T+037.922s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+037.923s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+037.923s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+038.258s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+038.261s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+038.261s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 15104739, max bitrate: 12000000 T+095.544s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+099.850s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+099.852s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+099.852s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+100.409s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+100.412s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+100.412s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+103.916s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+103.916s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+103.916s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+103.917s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+103.917s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+103.917s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+103.917s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+103.917s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+103.917s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+108.345s Info SessionManager: Playback start reported by app Emby for iOS 2.2.59 on iPhone Duo playing Jurassic World Rebirth. Position: 1545335 ms. PlaySessionId: [SESSION] IsPaused: False T+148.358s Info SessionManager: Playback stopped reported by app Emby for iOS 2.2.59 on iPhone Duo playing Jurassic World Rebirth. Position: 1575787 ms. PlaySessionId: [SESSION] IsPaused: False T+148.503s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+148.505s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+148.505s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+148.938s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+148.939s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+148.939s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+149.383s Info MediaInfoService: UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 T+149.416s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 T+149.416s Info MediaInfoService-[REQUEST]: Bitrate exceeds DirectStream limit: media bitrate: 20851831, max bitrate: 12000000 Jurassic World Rebirth — FFmpeg log excerpts: [transcode attempt] Duration: 02:13:40.01, start: 0.000000, bitrate: 20851 kb/s Stream #0:0(eng): Audio: truehd, 48000 Hz, 7.1, s32 (24 bit) (default) (original) Stream #0:1: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], Level 150, 23.98 fps, 23.98 tbr, 1k tbn (default) Stream mapping: Stream #0:0: Video: h264 (Main), cuda(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 11616 kb/s, 23.98 fps, 90k tbn Stream #0:1(eng): Audio: ac3, 48000 Hz, 5.1, fltp, 384 kb/s (default) [transcode attempt] Duration: 02:13:40.01, start: 0.000000, bitrate: 20851 kb/s Stream #0:0(eng): Audio: truehd, 48000 Hz, 7.1, s32 (24 bit) (default) (original) Stream #0:1: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], Level 150, 23.98 fps, 23.98 tbr, 1k tbn (default) Stream mapping: Stream #0:0: Video: h264 (Main), cuda(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 11616 kb/s, 23.98 fps, 90k tbn Stream #0:1(eng): Audio: ac3, 48000 Hz, 5.1, fltp, 384 kb/s (default)
Luke 43443 Posted yesterday at 03:48 AM Posted yesterday at 03:48 AM Hi guys, this topic is starting to have a bit too many things all in one place, which will make individual items harder to track. Let's use this topic for fullscreen support on iPhone Duo, which we are looking into. Please open new topics for other issues that you encounter with it. Thanks !
OSBuckeyes4Life 14 Posted yesterday at 11:56 AM Posted yesterday at 11:56 AM @LukeEverything I have posted is internal external logs related to the front full screen and the internal full screen mode? All of this is the same. I’m just trying to give logs for the experience and what’s it’s doing. 1
Luke 43443 Posted 19 hours ago Posted 19 hours ago OK we are looking into the full screen issue. Thanks. 1
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