jellyfin-media-player
jellyfin-media-player copied to clipboard
jellyfin
support m1 macs
This is just a feature request to target the new mac m1(arm) build. It can run through the rosetta2 layer, but of course that has issues anytime your not running natively.
Yes same ! A M1 arm version would be awesome.
Ask for help if you need anything (test, build, etc...)
I would love to see this as well. I tried it through rosetta but the video freezes every second.
I think this is a duplicate of https://github.com/jellyfin/jellyfin-media-player/issues/19.
We still need to wait for QT 6.2 to come out with M1 support first (scheduled to release at the end of this September). Then we need to migrate the current codebase to QT 6, after that we need to fix the build config for arm64 platform.
So, I think it might still take a while before there is a native version of Jellyfin media player on M1 Macs....
For those of you watching this issue, you may be interested to know I recently acquired an M1 MacBook.
For those of you watching this issue, you may be interested to know I recently acquired an M1 MacBook.
Great news !!!!!
Yeah about that… I applied for a developer account and apparently they charged me the $100 and then decided to terminate it. I hadn’t even logged in.
No response from support of course. I’ll give it another day or two (I submitted another inquiry), but I think I am just going to have to leave this to someone else and leave the Apple ecosystem.
Really frustrating too. Just when I was really starting to get into Apple stuff.
It sucks. You can't develop without a developer account first?
I also bought a M1 for a cross-platform Electron app I develop for this target: https://champagnethomas.medium.com/elevate-desktop-app-2021-update-9155fd74bb85
I didn't applied to their program yet (when going stable only). Their program is required for code signing your app for shipping. But you and early adopters of your mac version can install a non-signed dmg before everything works fine. This is what I do for me and my users. See https://github.com/thomaschampagne/elevate/releases/tag/7.0.0-12.alpha
Hope you will get your refund !
You can't develop without a developer account first?
I am hesitant to invest my time in any platform I have been banned from… Speaking of they are apparently looking at my support case but haven’t made a decision yet.
The best outcome would be I am able to stick with Apple as other than this issue I have been a happy customer.
I got a response that they are looking into the issue, but I haven't gotten anything definitive yet. I will only pursue a refund if I run out of time or they give me a definitive response.
Needless to say I have been pretty happy with Apple and have bought a lot of their products, so I really would rather not drop Apple because of this.
They have banned me without providing any reason and said they will not process any appeals. As a result, I will not give them another dollar of my money, will switch away from all their products, and will not be providing any support or endorsement for them ever again.
Since the "wontfix" tag was added to this and other related issues, I assume it has become the "official" stance of Jellyfin rather than that of an individual contributor? While I sympathize with @iwalton3's situation, this comes off as a bit odd.
I assume it has become the "official" stance of Jellyfin rather than that of an individual contributor?
@iwalton3 is the official developer of this app, under the Jellyfin umbrella. If he can't or won't develop for a particular platform, then it's unlikely to be done unless someone else is willing to do it. Perhaps we can leverage the team's Apple account (if we have one, cc @anthonylavado) but failing that, it is what it is.
I'm a bit lost here, I sympathize with @iwalton3, but why are we discussing Apple developer accounts? No need so sign the app or put it on the app store.
The goal here is just to succesfully compile the app for Apple silicon. https://www.qt.io/blog/qt-on-apple-silicon
@joshuaboniface was only trying to say that @iwalton3 has decided not to implement this feature and he is the only one working on this client right now. If someone else decides to open a pull request that adds support in a way that doesn't impact the entire codebase it would likely be merged, but otherwise there are no official plans to implement M1 support.
I will not be working on it as I have sold the M1 mac I bought and am banned from the developer program.
It is particularly problematic because GitHub only has CI/CD for Intel.
Of course if anyone can find a solution to this then fine. But I can’t build, support, or release for this platform.
Hi all I was playing a bit with compilation settings to run it natively on Apple Silicon (M1). Now, it is basically running without HW acceleration. Still have a problem ffmpeg if I turn HW. I let you know about my progress.
Out of curiosity did you compile a universal binary? QT officially supports it since 6.2 but I’m curious how it works on QT 5.
On Sat, Nov 20, 2021 at 13:05 dominikscha @.***> wrote:
Hi all I was playing a bit with compilation settings to run it natively on Apple Silicon (M1). Now, it is basically running without HW acceleration. Still have a problem ffmpeg if I turn HW. I let you know about my progress.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jellyfin/jellyfin-media-player/issues/99#issuecomment-974688574, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACOYMPWRQTXMCPSGEBJAGQDUM7PPHANCNFSM45UZTMWQ .
If someone is interested in working on this feel free to re-open the issue
Hmm - seems like they don't want to support a competitor to apple tv/tv+ Very poor form
No that has nothing to do with this. Also Infuse is available on iOS and TV OS which supports Jellyfin.
@dominikscha Can you please share your compilation settings? I'm unable to build Jellyfin player for apple silicon:
...
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Thanks
@dominikscha Can you please share your compilation settings? I'm unable to build Jellyfin player for apple silicon:
... ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)Thanks
Hi Axell
I used the following in build.macos: dotnet publish Jellyfin.Server --configuration Release --self-contained --runtime osx-arm64 --output dist/jellyfin-server_${version}/ "-p:DebugSymbols=false;DebugType=none;UseAppHost=true"
As Jellyfin is using ffmpeg for transcoding, you could also experiment with getting a arm64 version of ffmpeg. I found one on Homebrew.
Is this build method still working? Considering purchasing apple silicon. Can this become an Apple Silicon thread and include the M2, or should M2 become a separate issue?
I didn't try it recently. My server is still running on an Intel Mac. I am waiting for Mac mini M2 before I migrate.
