All Activity

https://github.com/edk2-porting/edk2-rk3588

About UEFI: it's a test suit from users, so it can be unstable. I haven't tested this so I can't say anything about it. About Android: I know there is official android images from orange pi website, but I don't tested it. If you will be using Ubuntu — I recommend Joshua Riek images.

Thanks, that's nice, because it matches the result of my own research which I had done two weeks ago: What I wasn't aware of, though is that you can use UEFI for booting, which is great news. Probably not for booting Android - did you ever run Android, is this even still a thing?

1. Orange Pi 5 Plus SoC: Rockchip RK3588. Storage Interface: Onboard M.2 M-Key slot (PCIe 3.0 x4, 2280 form factor). Multi-Boot Implementation: Equipped with a 16MB/32MB SPI NOR Flash. Supports UEFI (EDK2) deployment (need configuration) to enable a native boot menu directly from the NVMe drive. Alternatively, the MicroSD slot is positioned on the board's edge, allowing external media swapping via compatible enclosures without chassis disassembly. Enclosure Ergonomics: Compatible with standard metal cases that expose the MicroSD slot and all primary I/O ports. One-time assembly requirement is met by pre-installing the NVMe SSD and sealing the chassis. 2. Radxa Rock 5B SoC: Rockchip RK3588. Storage Interface: Bottom-mounted M.2 M-Key slot (PCIe 3.0 x4, 2280 form factor). Multi-Boot Implementation: Features a detachable eMMC module slot and an external-facing MicroSD slot. Multi-booting is achievable via customized U-Boot/GRUB configurations or UEFI images targeting the SPI Flash/SD card as the primary boot stage, while mounting core OS root filesystems from distinct NVMe partitions. Enclosure Ergonomics: Requires a dedicated aluminum heatsink-case. The NVMe drive is secured internally during the initial layout. System switching via MicroSD card swaps does not require opening the housing, as the card slot remains perimeter-accessible. I have first variant in use for almost 2 years, so I can help providing more information about this sbc. My config: Ubuntu 22.04 linux 5.10, NVMe 1TB with main OS, external HDDs for Data.

Thanks for the offer, through, the FFmpeg command building we do is pretty complex and working on this requires probably more iterations than we will have beta versions over the next few years... Acquisition of a device not a problem in itself, it's rather about which one. The requirements are: The device must use: RK3588 or RK3588S The device must have an internal M.2 M-key NVMe slot. Multi-Boot The device must be able to either boot multiple OS installations from NVMe (probably doesn't work) or boot with a boot loader with a menu on regular/flash storage while the core OS is installed on NVMe or boot from a non-fixed drive while the core OS is installed on NVMe and switch OS by changing the drive's medium In this case, the "drive'" must be externally accessible without opening the case The device must be useable in all possible ways without needing to disassemble and re-assemble it more than once - ever More generally: Everything that requires more time than it should/could, is a showstopper

When I try to play the following movie using Emby for Android (version 3.5.36 on an Nvidia Shield TV Pro), the movie doesn't start. It tries to start, but nothing happens on the client; it gets stuck at 0 seconds (fast-forwarding doesn't work either). On the server, you can also see that the client is stuck at 0 seconds (the server counts 0:00, 0:03, 0:07, 0:00 in an endless loop). Attached are the media details. In the Emby for Android TV app, the movie plays immediately and without any issues....

Okay, I understand. Thanks for your work and attempts! Maybe we can help you to test raw software in beta test? For example I have Orange Pi 5+ with RK3588S, it can transcode any format with ffmpeg included in Jellyfin without any bugs and much heating/cpu load. So I think it won't be difficult to test and feedback for such users as me.

Well, on the FFmpeg side, everything is prepared, but not at the side of Emby Server. We do not even have a device other than the underperforming hand-warmer (which I won't ever touch again ).

I got few minutes, so let me explain our - let's say - "limited excitement" for RockChip devices. Few years ago, users convinced us to look into those types of devices (earlier gen of course) for transcoding and it looked very promising - at least on paper - so we bought a Pine64 with an RK3399 and looked into it. Step-by-step it became clear that the specs were blatant lies and none of the promises kept true, like ffmpeg support, which had been mentioned and confirmed at various places, and then it turned out that there had been an earlier attempt, abandoned 1.5 years ago, completely unusable, requiring some kernel of firmware that wasn't even available - a total failure. Playback at FullHD - stuttering like crazy - far away from all the specs they published - and it was clear that this device will never be able to transcode anything (when it cannot even de-code, how should it at the same time? Several OS images were provided and the only question was: which bug will the next one have what the others don't have? OS had to be copied on an eMMC card - ancient technology, super-slow, took endlessly long and the result worked only in one of 3 cases - at best. The device became super-hot, even for little effort, cooling was insufficient, and it became even slower when hot and it was hot most of the time. Also, it was hardly possible to keep it closed. Each time I reassembled, it took only minutes until another reason came up for disassembling again, yet it needed its case for cooling, so it was an endless chain of open close open close open close - you couldn't put it into a corner and be good. It might be a nice gadget for doing simple things, but the way how it was advertised - by RockChip, not by Pine - is not acceptable, just a collection of lies. It's been an incredible waste of time, disappointing all along the line with a manufacturer who is lying about capabilities - from this background it should be understandable that since then, our excitement for anything about RockChip has been - as said - rather limited. The conclusion was that we won't do any pioneering work and won't make any move in this area until there's proven evidence that this can work in a reasonable way and other will have done the required work on ffmpeg integration and suitable OS images, drivers and convincing device models are available. The condition of the last sentence seems to be fulfilled, that why we're going for another attempt, but not as a top priority.

Thank you hatharry it's working now! When you ask Alexa to stop, it says "I encounter a glitch. Can you say that again?" It stops the music though. Edited: Stop music doesn't say the error anymore but playing next song doesn't work now. Tried Alexa next track, next song, and next. Thanks for the quick support.

Hi, checking in to see if there are any updates on this. TY

I think you mean automatically adding all the items in the deletion queue to a single collection. If that's what you mean, I like the idea and I'll try to include it in the next update.

New Emby server Beta release, v4.10.0.19.

@FourCornersthere are plenty of more appropriate places to discuss this topic out on the interwebs. This forum is not one of them, thanks.

Wow, this is awesome! Can we somehow understand the status of progress? Is there much more work left to be done?

Thanks @howllor for pointing that out. I'd like to add a couple of thoughts as well. First, I tested the plugin and it's well made. I don't have anything against it at all. That said, I have two things to say I can confidently say 99% of people use Sonarr/Radarr primarily to manage and organize torrent downloads, not just for their calendar. If someone is using this plugin, it's likely because it shows downloading content as upcoming items in Emby. If the goal is only to display upcoming releases based on release dates, Emby already supports that, atleast for TV shows. That's why I was confused, especially since @ebr previously said, "We do not integrate with any of the content acquisition features of those apps." The plugin also uses yt-dlp, while the development policy specifically mentions that downloading videos directly from YouTube is not allowed and recommends using YouTube's public API instead. I'm not trying to argue or ask for special treatment. Whether my plugin is posted on the forum or not doesn't really change anything for me. I just wanted to share something I thought others might find useful and was trying to understand where the line is drawn so the policy is applied consistently.

Just to let you guys know - this is not on the never-gonna-happen list. We're working towards it, and progress is made...

Any updates on this? Because I don't use it at all and have no intention of ever using it. And it's a shame, it takes up a lot of unnecessary space on the interface, in my opinion. Would it be possible to simply make this feature disableable and hide it, and adjust the interface accordingly?

Does anyone have tips and tricks to share for the cleanest/most automated way to get Emby to pull correct metadata for live recordings of sports? I have TheSportsDB plugin installed; it correctly scrapes info for individual games but only when the filename exactly matches TheSportsDB's suggested naming exactly, which requires renaming a recording after the fact. On top of that, I haven't found a way to get Emby to match the "show" name to the relevant league in TheSportsDB (e.g. NBA, NFL), even when I rename the folder with the show to the exact name and try to hard code the correct TheSportsDB id for that league in the metadata. Has anyone found a way to better automate the renaming that has to happen? And what is the best-case scenario for the leagues/show names -- just manually pull stuff and lock the item (and then I guess manually move episodes over to the right folder)?

@Lukechecking where we are fixing the search TY

Hi, checking in on this option if it's being implemented any time soon? TY

I use Telegram and Whatsapp Bots.

OK the 3.8.4 plugin update has added support for their new paging requirements. Thanks.

Still not working. (all updated) For me it looks now like this: When opening emby on dex in minimized mode and i hit play on a video, the video starts in full screen. But there are no controls (play / pause) when moving mouse. The black borders on top and bootom are visible now. But the task bar of dex is still visible. So not real full screen. When hitting the "back" on the keyboard (WIN + arrow left) emby returns into window mode and the screen is just black. But i can hear the sound of the video still playing. And when moving mouse on the now minimized window, controls appear (and controls work). Hitting the "back" on the keyboard (WIN + arrow left) then, i can return to the movie overview and start/continue the movie again. then all the same behavior like described before. Tried starting emby on my phone (when connected to the dex screen) then, the movie starts in full screen on dex screen (taskbar visible, black border on top/bottom visible, but no controls) and on the phone there is black screen with the controls that are working. When hitting the "back" on the keyboard (WIN + arrow left) on the phone, the fullscreen on dex still displays the last shown stopped video. When moving the move to the dex and hitting the "back" on the keyboard (WIN + arrow left) the image disappears. Note. dex is starting all apps again, and closing on the other screen. for example starting a browser on mobile and then on dex it closes the window on dex and vice versa. Same with emby. But somehow the fullscreen when starting a video always start on the dex screen. Tried in chrome for example to open emby. there the fullscreen is not switching to the dex screen.

It's a Galaxy S21 Ultra with Android 15 and a Marantz SR7015.