frequency problem

Page 3/3
1 | 2 |

By TomH

Champion (327)

TomH's picture

18-12-2017, 14:52

sd_snatcher wrote:

I really fear when solutions tend to become over engineered.

I'm more concerned about when appeals to common sense throw away the nuance of an issue.

Agree with the conclusion that 60Hz is a reasonable default, continue to disagree that a region should be hard-coded when the OS or browser can tell you what language the user has their computer set up in. If I'm a Japanese person, with my computer localised to Japanese, and I launch an MSX emulator to play my favourite Japanese game, showing me English because the emulator's authors and all their friends speak English isn't a great experience.

It'd also clearly be much better to make a good selection per title than just a guess overall — exactly the same way an emulator often has to make a MegaROM selection per title rather than just overall. Given the lack of traction in America, it might be interesting to see whether you can crack the problem in a similar manner: just as MegaROM type detection relies on sniffing likely bits of paging code, try to detect a decent quantity of Japanese text. If any is found, play at 60Hz. If not, 50Hz.

By Manuel

Ascended (18395)

Manuel's picture

18-12-2017, 23:53

I'm currently working on making an EU and INT version of C-BIOS, being 50 and 60Hz respectively. Making C-BIOS_MSX2+_INT the new default openMSX machine is in the pipeline.

This is a reasonable amount of work. I currently do not have spare time to start implementing elaborate machine-guessing strategies. As I said before, it's more something for a launcher to implement anyway, not for the openMSX core.

By hit9918

Prophet (2911)

hit9918's picture

19-12-2017, 00:34

"INT" sounds like integer. isnt "INTL" a usual spelling for "international".

By TomH

Champion (327)

TomH's picture

19-12-2017, 02:43

Manuel wrote:

I'm currently working on making an EU and INT version of C-BIOS, being 50 and 60Hz respectively. Making C-BIOS_MSX2+_INT the new default openMSX machine is in the pipeline.

This is a reasonable amount of work. I currently do not have spare time to start implementing elaborate machine-guessing strategies. As I said before, it's more something for a launcher to implement anyway, not for the openMSX core.

I think I'm not alone in being grateful for as much work as you're willing to do; conversation was more in the abstract of how much information could feasibly be guessed — not an attempt to build up some weird sense of entitlement. It might be an interesting idea just to play about with but, as you say, it's far from being something that an emulator needs.

Page 3/3
1 | 2 |