-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ffmeg 0xfffffffa on all attempts to play a video. (Summary Post) #217
Comments
Sorry i don't understand much of the solution paragraph and I'm dealing with the same thing |
there is no solution we can enact we just have to wait for the devs to fix the issue |
Basiclly Were F'ed |
Also am experiencing this issue, NEW 3DS XL |
Honestly doesn’t sound too hard to do, I might try to do this myself when I have the time |
I have the same problem on a 3DS OLD, could it be that they already fixed it? |
Yes we are |
I also have had this issue for over a month |
windowsserver2003 get UUPPPPPP |
WHEN ARE THEY GOING TO FIX THIS!!!!!!! |
The error thrown, The only mentions of this error anywhere on Google (by searching Here is the website I found this on: https://programmersought.com/article/89887525290/ It is under the header "Encounter Problems" The I myself could not figure out how to get it to reconfigure and recompile, so maybe someone more experienced than measly me could crack the case. Just my two cents, but that's what I could find on the matter. |
If we know a fix(?), why not just fork ThirdTube? |
We don't, this is just my analysis. |
Added To Main |
For anyone who wants to attempt to fix this, you have to downgrade to 3ds-mbedtls 2.16 for the build to "work" properly. Newer versions cause the app to be even more broken to the point the app just crashes when you load a video. You still can't watch anything, but at least one can try and fix the real problem. As for this issue, my guess is the decryptor needs to be updated, not ffmpeg. The debug log backs this up, reporting some 403 errors from the networking stack. If anyone knows what they're doing, that's the first thing I'd try. |
Possibly Try FourthTube if you want an easier option: |
UPDATE: THREE WEEKS HAVE PASSED THE DEV HAS NOT PUSHED UPDATES YET I AM LOSING HOPE.
This is a detailed "summarization" of the already open issues.
Almost/All attempts on playing a video on version 5.4 result in the error code: ffmeg 0xfffffffa
And thus soft-locks your app, preventing any video or audio from playing.
this is a critical issue and until fixed, prevents the app from working.
Luma3DS: v13.0.2
ThirdTube: v0.5.4
Credit to @azgaresncf for a solution? "AV1 should be working on the 3DS, as the creator of the original Video player is saying here, because the AV1 decoder of the player (dav1d) is a SOFTWARE decoder, not an hardware one. [...] So the first thing that we can do is to bring the updated video player source code to ThirdTube." [referencing Video player for 3DS by: Core 2 Extreme]
Image from other user (credit to: @0529Cb1)
Info From @SeveringHams:
The error thrown, avformat_open_input() failed -1094995529 seems to be returned/thrown by the demuxer in FFmpeg, just looking at the documentation at https://ffmpeg.org/doxygen/trunk/group__libavf.html
The only mentions of this error anywhere on Google (by searching "avformat_open_input failed -1094995529" WITH the quotes) are on Chinese websites, and the one English translated one says to enable the demuxer library, or indicate in the configuration what demuxer library to use, or something to that effect.
Here is the website I found this on: https://programmersought.com/article/89887525290/ It is under the header "Encounter Problems"
The build.txt file in /library/FFmpeg/ tells us that many features of FFmpeg are configured to be disabled on the custom build of FFmpeg used in ThirdTube, and a handful of formats are selected to be enabled, so perhaps reconfiguring it to enable YouTube's current video file format (whatever it may be) would make it work.
I myself could not figure out how to get it to reconfigure and recompile, so maybe someone more experienced than measly me could crack the case.
The text was updated successfully, but these errors were encountered: