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

15Khz compatibility for all cores by default? #30

Closed
lroby74 opened this issue Sep 6, 2016 · 3 comments
Closed

15Khz compatibility for all cores by default? #30

lroby74 opened this issue Sep 6, 2016 · 3 comments

Comments

@lroby74
Copy link
Contributor

lroby74 commented Sep 6, 2016

Hello everybody,
just guessing why it's not possible to have 15Khz compatibility on default for all cores, in this way people may use any cores with own RGB Scart monitors like Philips CM8833 or Commodore 1084S or similar.

Thank you all
Roberto

PS
Mist is awesome!

@lroby74 lroby74 changed the title 15Khz for all cores by default? 15Khz compatibility for all cores by default? Sep 6, 2016
@harbaum
Copy link
Contributor

harbaum commented Sep 9, 2016

The cores that do support 15khz all support the same mist.ini setting. So this single setting affects all cores that support it.

But not all cores support 15khz if that's your question. This has to be implemented in each and every core.

@lroby74
Copy link
Contributor Author

lroby74 commented Sep 9, 2016

Infact i mean this, why 15 khz feature can't be programmed directly into
each single core in the moment that a new core get created

Il 09/set/2016 15:44, "Till Harbaum" notifications@github.com ha scritto:

The cores that do support 15khz all support the same mist.ini setting. So
this single setting affects all cores that support it.

But not all cores support 15khz if that's your question. This has to be
implemented in each and every core.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJPoepHc140-drKCweA33g2IYOgYRx3fks5qoWK-gaJpZM4J1p0g
.

@harbaum
Copy link
Contributor

harbaum commented Sep 9, 2016

Simply because it's some hours of extra work and not all developers have a matching screen and cable to test with. Plus they may simply not be interested in it.

@lroby74 lroby74 closed this as completed Mar 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants