Anki 26.05 Beta 2

Anki Beta Testing
23

Before posting about it in this thread, you need to determine if this issue is new to the beta or already existed in the prior release.

26

Senior Danika, I am perfectly a w a r e of that. What you failed to realize is that the previous beta has certainly affected a change addressing this issue, possibly referring to

“Making descending retrievability a pure R sort by @user1823 in #4400”.

If the change is global, then the results should have been consistent, as they were before. Now I don’t know whether the underlying issue was in this beta or is a persistent one from before.

With all due respect, I am only here to report an issue, not play Sherlock Holmes.

28

I can see similar sorting differences on 25.09.4 so I assume it’s not something new.

Docker is not officially supported yet. You might have luck using this Dockerfile (you can try downgrading PyQt6 if you see similar issues): anki/docs/docker/README.md at main ¡ ankitects/anki ¡ GitHub

29

Yes, I saw that dialog with “Close the applications and attempt to restart them” selected by default, and I kept that default and clicked on OK. I don’t recall if all the processes were listed, or just Anki.

I used Tools > Check for Updates from the menu within Anki 26.05b1 to upgrade to 26.05b2, as opposed to downloading the .msi installer program from within the browser and then running it separately, which is what I had done when installing Anki 26.05b1 itself earlier. I don’t know if that aspect made a difference.

And in case it’s relevant somehow, at the time I ran the upgrade, I was also running another process that was temporarily using most of the available physical memory (24 GB out of 32 GB), with some of the remainder obviously used by the browser, etc.

PS,
After the above dialog box with “Close the applications and attempt to restart them”, there was a series of other dialogs with errors and warnings. In fact, the original “close and restart” dialog box may have reappeared a second time, with a longer list of processes to close instead of just Anki. It was only at some later point in this series that I tried to close Anki manually by clicking on the big × in the top right corner, but could not because the bell rang instead and some alert or dialog kept the focus.

If there’s a Beta 3, I’ll try to document the exact update process behavior from the start.

30

Yes, this is what I tested too. Let me know how this goes in the next beta/stable, or you can install 26.05b1 again and try reproducing the issue if you’re interested in more testing.

31

I can see similar sorting differences on 25.09.4 so I assume it’s not something new

Hmm okay. Is this a bug or is this due to how filtered decks work :red_question_mark: Which is the “correct” sort?

32

I closed Anki 26.05b2 and reinstalled 26.05b1 from the .msi (using “Install just for you” scope), and then ran Tools > Check for Updates to reinstall 26.05b2. I also had the the 24GB memory hog process running just to try to reproduce the original circumstances.

This time the Anki window disappeared and there was no conflict with still-running processes. So the modal dialog issue never arose, and the installation process completed.

Oddly, when I ran Anki for the first time after the “update”, Help > About Anki… showed the version was still 26.05b1. I had to do Tools > Check for Updates a second time to actually get 26.05b2 installed.

33

The difference appears to be showing when filtered deck rescheduling is disabled. All cards are treated as review cards in this case, so learning cards become subject to the review order. If you have more comments about this, please create a new thread.

1 Like
34

UI Rendering Delay When Revealing Answer

Summary

When reviewing cards, the answer side does not always render immediately after pressing Show Answer. Instead, the answer content either:

  1. Appears only after a delay of several seconds, or
  2. Remains partially/unrendered until the user scrolls the review area.

This creates the impression that the answer failed to load and negatively impacts review speed.

Steps to Reproduce

  1. Open Anki and start reviewing cards.
  2. Review cards containing longer or more complex content (text, images, MathJax, HTML, etc.).
  3. Press Show Answer.

Expected Behavior

The entire answer side should render immediately and completely when Show Answer is pressed.

Actual Behavior

The answer content is sometimes not rendered right away. Instead:

  • The answer may take several seconds to appear.
  • In some cases, scrolling the review area causes the missing content to render instantly.
  • The issue appears related to the UI refresh/rendering process rather than card loading itself.

Additional Notes

  • Scrolling often forces the content to appear, suggesting that a repaint/reflow event may not be triggered correctly when switching from the question side to the answer side.
  • The issue is visible in the attached video recording.
  • This behavior slows down reviews and can make Anki appear temporarily unresponsive.

Environment

  • Anki version: 26.05b2
  • Operating system: win 11 25h2

This was an issue with previous releases as well but not to the extent as of now.

35

Interesting. There are cases where Windows fails to shut down Anki processes and require a restart to finish installation, but a warning should be normally shown in that case.

You can usually work around this by changing the Video Driver option from Tools > Preferences. I’m actually seeing it less often with this release on Windows with the default Direct3D driver (#4686), but this is probably not the case on all systems.

1 Like
36

Tried them but it didn’t make much of a difference

37

Can you try this build and let me know if you see a difference? Release "26.05b2" (sign=false, draft=false, testpypi=false, pypi=false) ¡ ankitects/anki@95f91b6 ¡ GitHub

(Scroll down to the Artifacts section and download installer-windows or installer-windows-arm)

38

I had the same problem where any Anki card with audio spit out this error: Sound and video on cards will not function until mpv or mplayer is installed.

Your fixed worked! For those who are curious (on Mac):

  1. Ensure Anki is closed
  2. Open Finder
  3. From the menu bar, press Go > Go to Folder... or press Cmd+Shift+G
  4. Paste /Applications/Anki.app/Contents/Resources/app_packages/anki_audio/
  5. Hit Enter
  6. Rename lib to libs
  7. Open Anki :slight_smile:
1 Like
39

I tried the build, and it seems to have alleviated the issue by about 90–95%. I still notice it occasionally, but it’s much less frequent than before.

1 Like
40

Sometimes, on both versions b1 and b2, I have a missing part of the interface.

image
image931×232 4.38 KB

Version 25.09 works stably.

I didn’t want to write here; maybe there’s something wrong with my system again. And the most important thing is that when I was advised to write, everything was perfect that day :slight_smile:
It’s been the same since this morning. But after repeatedly launching and restarting Anki without add-ons, I finally got it to start glitching just like I saw.
Changing the video driver didn’t help, nor did disabling add-ons.
Rarely, but sometimes even the “Browse” window doesn’t display the list of fields. But that’s okay, let’s say everything looks fine and everything loads. I need someone to try adding this code to the note type:

<div class="hide2s">{{Front}}</div>
{{Back}}

css:

.card {
 font-family: arial;
 font-size: 18px;
 text-align: left;
 color: black;
 background-color: white;
}

.hide2s {
    opacity: 0;
    animation: showField 0.3s ease forwards;
    animation-delay: 2s;
}

@keyframes showField {
    to {
        opacity: 1;
    }
}

This code will display the field after 2-3 seconds.

Since this code works and sometimes doesn’t work, it can’t be said that such functions are not fully supported by QtWebEngine.

So, if we see the field right away, something isn’t working. So I check, and sometimes everything works, and sometimes it doesn’t work on the main screen but works in the preview, and sometimes after 10 tries it might not work even in the preview.
It’s hard to pinpoint and understand, but at least someone might try it and tell me how it works for them. I ran this on Windows 10.

41

That’s weird. Will keep an eye on reports.

42

It appears that the betas introduced a change in the minimum supported macOS version (because of the updated Qt version). The new minimum supported version is macOS 13 (Ventura). This information will need to be added to the release notes.

2 Likes
43

And to the main site:

image
image767×184 14.5 KB

And to the manual, which already needed some clarification on this.

2 Likes
44

Environment:

Detailed Reproduction Steps:

  1. Install Anki 26.05b2 beta on Linux.
  2. Create a new flashcard using ames to record an audio clip.
  3. Observe that ames generates a filename with mixed case, e.g., ffmpeg-recording.6jSlvq.opus.
  4. Check the Anki media folder (collection.media): Anki has silently saved the file as all lowercase: ffmpeg-recording.6jslvq.opus.
  5. Inspect the actual flashcard note/database: The note still references the original mixed-case name: ffmpeg-recording.6jSlvq.opus.
  6. Run Tools > Check Media.
  7. Check Media says that ffmpeg-recording.6jSlvq.opus was referenced by card but not used, and that ffmpeg-recording.6jslvq.opus is present in the media folder but not used

The Bug:

  • Disk State: The file exists physically as ffmpeg-recording.6jslvq.opus (lowercase).
  • Database State: The card reference expects ffmpeg-recording.6jSlvq.opus (mixed case).
  • Result: Because Linux is case-sensitive, Anki fails to find the file matching the database reference. It reports: “The following files are referenced by cards, but were not found in the media folder: ffmpeg-recording.6jSlvq.opus”.
  • Verification: The file does exist and plays perfectly on Android/iOS after sync (which ignores case), proving the data is intact but the local lookup is broken.

Evidence of Regression:

  • Pre-beta files: The audio files recorded by the external tool were mixed case, and saved as mixed case by Anki in the media folder.
  • Other tools: Audio added via Anki’s built-in recorder or HyperTTS does not trigger this issue; only files added via ames (and potentially other external scripts saving to the media folder that use mixed case file names) are affected.
  • Scope: This affects any audio file added post-upgrade where the source tool uses mixed-case characters.

Suspected Cause: A regression in the Linux media handler in Anki 26.x that normalizes/sanitizes filenames to lowercase upon writing to disk but fails to propagate this change back to the database/note fields. This creates a permanent mismatch on case-sensitive filesystems. (ok this part was stated by ai)

45

This is done to prevent issues when moving to case-insensitive filesystems: Importer overwrites existing media files with different letter cases ¡ Issue #4433 ¡ ankitects/anki ¡ GitHub

The quickest fix would be to modify ames to convert the filename to lowercase before saving, but more generally, the tool is using AnkiConnect’s storeMediaFile method to save the media file but failing to check the response to get back the normalized filename (Anki also normalizes the name to remove problematic characters).

3 Likes