search

tomcw / mb-audit

8 stars 1 forks source link

UI improvements #15

Open tomcw opened 9 months ago

tomcw commented 9 months ago
  1. For mba: at the "Tone" test stage:
    • state that keys 1,2,3... (and Q,W,E...) toggle the AY channels
    • visually show when a channel is on (INVERSE) or off (NORMAL)
  2. For "(C) SPEECH" test show a message if there are no speech chips + "Press any key"
    • currently it just returns immediately back to the main menu
  3. For "(E) 6522 T2C_H" test show a message if it doesn't run the test + "Press any key"
    • currently it just returns immediately back to the main menu
tomcw commented 9 months ago

Fix for (3) - https://github.com/tomcw/phasor-test/commit/a4bbf23a8100e00a3a494ede358c49790f44067a

tomcw commented 7 months ago

RE. (C) SPEECH At 1.50, this was using play-sc01-using-ssi263 v0.7, which detected MB & Phasor as "S" types. This was fixed at v0.8 (in May'22!), so I've added this to "mb-audit-v1.52.dsk".

tomcw commented 7 months ago

For (1): "Tone" test stage: 26a5f90a1572bf5eeae694120a371575ed068e93 Also improve showing Phasor mode: 7832eef243a294fd21baf616d242fb0ff6804dbb (Released in mb-audit-v1.52.dsk)

tomcw commented 7 months ago

To do: (2) EG. With Phasor in slot 4, then set Echo+ mode (C0CF), and run (2000G): it outputs an error(*) and exits immediately.

(*) Slot #4: Mockingboard failed test: 6522

tomcw commented 1 month ago

From @roughana:

Hi Tom, I am playing with mb audit 1.53 In my //e. I have installed my mega audio in slot 1 but it must be configured to provide MB on slot 2 as that is where it is detected. The quick test says to press 1-6 or Q-Y. Pressing Q-Y does nothing that I can discern. I have a bad output on left channel and 123 work briefly before the sound cuts out completely. I wasn’t sure how to exit the test but discovered ESC exits. Please add that prompt to screen for better usability.

To do: Add prompt to screen that ESC exits the "tone tests"

Also my response:

The "Press Q-Y" msg should only display for the Phasor card which has 2 more AY chips, so this sounds like a detection error (or bug).

I was wrong: it currently outputs this generic message whatever card it is:

(Where "USE KEYS" is FLASHing)

Re. Better UI instructions - I know it needs better wording to guide people through. Problem is lack of space in 40 cols! But I'll take a look (eg.could augment with better instructions on the GitHub page).