VOGONS


Reply 560 of 563, by Apple IIGS

User metadata
Rank Newbie
Rank
Newbie

Update: I tested Nuke-55sc on a more modern computer (Core i7 Pro, versus the Core 2 Duo previously used) and much of the latency while playing a real-time MIDI keyboard has vanished! It's not as responsive as my hardware SC-55mkII, obviously, but the average person likely wouldn't notice. No surprise that all the crackling and garbled sound has disappeared too. It's still quite remarkable to hear an emulated Sound Canvas with about 99% accuracy coming out of an ordinary desktop PC with just a plain old DAC!

I also finally figured out how to use the JV-800 side playing one of my MIDI keyboard in real-time using a USB->MIDI cable adapter! (a nice treat, since I had a JV-880 stolen from me before I had a chance to try it). I'm wondering though, how accurate is the JV-880 side of Nuke-SC55. Is it still a work in progress or is it considered complete? I noticed one patch (RevCymBend) wasn't working properly, and a few others seem to have some minor clipping or distortion. I don't have a real JV-880 to compare with, unfortunately.

Reply 561 of 563, by EmperorGrieferus

User metadata
Rank Newbie
Rank
Newbie

Listening to Descent OST through Yamaha MU80, I realized that it shares a fair amount of samples with SC-55. I wonder why.

Reply 562 of 563, by zaphod77

User metadata
Rank Member
Rank
Member

because the mu-80 has a tg300B mapping that it uses when it does a GS reset.

Reply 563 of 563, by syche

User metadata
Rank Newbie
Rank
Newbie

Hi!
I just recently started using Nuked SC-55 (before I've been using SC-VA for years) and I have some (perhaps dumb) questions.
1. Which is a better (or less problematic) emulated device for DOS gaming: SC-55 MK1 v 1.21 or SC-55 MK2? I guess, what I mean is which one is considered to render music in most DOS games more correctly and without quirks, or if the difference is negligible enough and can be ignored?
2. There is a warning in the readme file that due to a bug in the SC-55mk2's firmware, some parameters don't reset properly on startup and need additional actions to properly initialize. I presume then, that means SC-55 MK1's firmware doesn't have this bug and no additional actions are required? Am I right?
3. When Nuked SC-55 starts up it produces 6 "Unknown Write" errors on MK2 firmware and 14 "Unknown Write" errors on MK1 v 1.21 firmware. Is it expected behavior and does it mean anything bad in practice? Does it actually mean that it's preferable to use MK2 firmware with Nuked SC-55 (since there are much less errors during MK2's initialization)?

Sorry if these questions have already been asked and answered. Thanks!