Skip to content
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

Incorrect VA / character mappings #1183

Open
revam opened this issue Oct 12, 2024 · 1 comment
Open

Incorrect VA / character mappings #1183

revam opened this issue Oct 12, 2024 · 1 comment

Comments

@revam
Copy link
Member

revam commented Oct 12, 2024

VERSION INFORMATION

Server Version: 4.2.2.190

Desktop Version: N/A

If you've compiled your own version, please use the last commit you compiled.

The Issue

AniDB currently stores VA/character mappings per anime. We on the other hand store it globally. So, when we have a character that appears in multiple anime, but with different VA for each, then we will currently store the last known VA/character mappings for a character from the last anime that was refreshed and contained the character.

Example

An example explaining it using the following character; Roronoa Zoro

If we refresh One Piece, then we will have two mappings for the character, one to Nakai Kazuya and one to Urawa Megumi. If we instead refresh One Piece (2000), then we will only have a mapping to Nakai Kazuya. And last, if we refresh One Piece: Taose! Kaizoku Ganzack, then we will only have a mapping to Takagi Wataru stored.

Proposed solution

Start storing VA/character mappings per anime, and also add a database/startup migration to regenerate all mappings from scratch again using the locally available xml files.

@bigretromike
Copy link
Contributor

storing those per series is the most sane way. I can imagine (as not so long ago) many original VA will pass away, and will be replace with new ones. then it would wipe mapping of are original VA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants