Prefer real releases over pseudo-releases

[throwaway-lmao]

Sometimes I try importing an album, and it gets matched to a pseudo-release, which romanises the original title. Since pseudo-releases aren't real releases, there's never an instance where I would actually want them in my library over the actual release it corresponds to. Existing dscussion related to on this topic seems more focused on the inverse of this.

Is there a way to force beets to use real releases over pseudo-releases? If not, would it be possible for such a feature to be implemented?

[RollingStar]

I'd start by looking at preferred or maybe even distance weights.

https://beets.readthedocs.io/en/latest/reference/config.html#preferred

https://beets.readthedocs.io/en/stable/reference/config.html#languages

match:
    #.1 = 90% similarity required. automatically matches above the threshold.
    #even at the chosen threshold, can be unintuitive and not automatically select the choice that meets the threshold.
    #There is a GitHub issue for this that I can't find.
    strong_rec_thresh: .1
    preferred:
        media: ['CD', 'Digital Media|File', 'Digital Media']
        countries: ['US', 'GB|UK']    
    distance_weights:
        #should help "quiet" matching. If beets is too eager to match incorrectly and ignore missing tracks,
        #then this creates more work for the user later when they manually correct the matches to a release
        #without the tracks, or find the missing tracks.
        missing_tracks: 10
        unmatched_tracks: 10
        #try to force away from vinyl
        #media: 20.0
        #mediums: 20.0

[throwaway-lmao]

I can definitely try that, but I don't think its the "correct" solution here. What I want is for Japanese releases to be in Japanese, Russian releases to be in Russian, and so on. Setting preferred languages, however, asks that ALL releases be in a specific language, whether or not they were ever released like that. I've yet to see any MB pseudo-release which translates/transliterates between two non-English languages, but nothing in the documentation suggests that it isn't allowed. I'd rather not shift the problem into Japanese or Russian instead of English, where I now have to make sure my English-original releases are actually in English.

Mind you, your solution probably works in practice so long as MB continues to be a predominantly English-centric community, but I prefer correctness over workarounds that work purely by happenstance. Something like an option in ignored for pseudo-releases, or an "original" language in the languages option would be the more "correct" solution in my eyes.