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

Sound not right plus errors #108

Open
SerialDreams opened this issue Dec 19, 2024 · 4 comments
Open

Sound not right plus errors #108

SerialDreams opened this issue Dec 19, 2024 · 4 comments

Comments

@SerialDreams
Copy link

Unknown write e400 4
Unknown write e403 1
Unknown write e406 0
Unknown write e407 0
Unknown write e406 40
Unknown write e403 1

These get dumped in the console when I start it up, and the audio itself is kind of crusty.

@SerialDreams
Copy link
Author

Also for some reason it defaults to half a chord lower than normal. e.g. if a track is on E it will play on D# until/unless I initialize all instruments (Power+Part R, then Inst ALL)

@Kappa971
Copy link

Also for some reason it defaults to half a chord lower than normal. e.g. if a track is on E it will play on D# until/unless I initialize all instruments (Power+Part R, then Inst ALL)

Read the README file in the first page:

- Due to a bug in the SC-55mk2's firmware, some parameters don't reset properly on startup. Do GM, GS or MT-32 reset using buttons to fix this issue.

- SC-155 doesn't reset properly on startup (firmware bug?), use Init All option to workaround this issue.

More info: #99 (comment)

@SerialDreams
Copy link
Author

SerialDreams commented Dec 20, 2024

Well that answers most of this.
It's weird, though. I have had both an SC-55 and SC-55 Mk.II for a couple of years now and while the occasional weird pitch bending and wrong instruments happen, I've never once had to do a GS/GM reset because a MIDI was on the wrong key.

What of the errors being printed in the terminal? Is it anything I should be worried about?

Another question if you don't mind, are there any future plans to have the emulation catch and correct those issues automatically?
Moreover, will future version also (if not already done) remove the limits of the emulated devices? e.g. The SC-55 and Mk.II don't do well with dense chorus and polyphony.

PS: Suggestion, maybe future versions of Nuked could include some kind of simple, collapsible UI for the synthesizer buttons?

@Kappa971
Copy link

Well that answers most of this. It's weird, though. I have had both an SC-55 and SC-55 Mk.II for a couple of years now and while the occasional weird pitch bending and wrong instruments happen, I've never once had to do a GS/GM reset because a MIDI was on the wrong key.

This problem does not appear to affect the SC-55 (mk1), although I have not tested it.

What of the errors being printed in the terminal? Is it anything I should be worried about?

I don't know.

Another question if you don't mind, are there any future plans to have the emulation catch and correct those issues automatically? Moreover, will future version also (if not already done) remove the limits of the emulated devices? e.g. The SC-55 and Mk.II don't do well with dense chorus and polyphony.

Reading some past answers, I would say no. Apparently, these limitations are intrinsic to the ROMs and the extremely accurate emulation of Nuked SC-55. They are the original devices, emulated.

You can use Falcosoft MIDI Player to run two instances of Nuked SC-55 and double the polyphony.
I think there is also an unofficial fork of Nuked SC-55 that allows you to run two instances without third-party software, but I have never tried it.

A high-level Munt-style emulator is also in development (https://github.com/skjelten/emusc), which should not have the limitations of the original modules, but the sound accuracy might be worse.

For more technical questions you have to wait for a response from the emulator developer.

PS: Suggestion, maybe future versions of Nuked could include some kind of simple, collapsible UI for the synthesizer buttons?

Development is frozen for a while, I don't know. You have to wait for any clarification from the developer.

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