A New Engine? Nearly.

Sounds legit, would be at home in a pre-1985 ZX game.

You don't really need to hand tune pitch values, just use any script engine to calculate them out. JS, Python, etc.

Then, if you go with composing by typing in the pitch values, you don't have to have a spreadsheet. Just make aliases, like C_2=100 (or C_2 equ 100 in some assemblers). Now you can just use note names in your db's.

Then, to save time, you can just generate both pitch values and aliases with the same script, and save a ton of time. You can do this with https://js.do/, for example. Just go there, copy/paste code below, click Run.

<script>

    //standart note table for a high octave

    NoteFreqTable=new Array( 2093.0,2217.4,2349.2,2489.0,2637.0,2793.8,2960.0,3136.0,3322.4,3520.0,3729.2,3951.0 );

    NoteNameTable=new Array("C_","Cs","D_","Ds","E_","F_","Fs","G_","Gs","A_","As","B_");
    
    //generate note to period table

    cpuClock=3500000.0;
    cpuToneLoop=200.0;    //cycles per engine loop
    div=32.0;

    for(octave=0;octave<8;++octave)
    {
        for(note=0;note<12;++note)
        {
            period=Math.floor((cpuClock/(cpuToneLoop/2.0))/(NoteFreqTable[note]/div));

            document.write(NoteNameTable[note]+octave+" equ "+period+"<br>");
        }

        div=div/2;
    }

</script>

Yay, congratulations on this achievement! And welcome to the rabbit hole of 1-bit engine making

Ehh, I wish I had Shiru's advice back in the day when I started to make my own engines. Could never wrap my head around it back in the day. Just like I couldn't figure out 16-bit dividers, lol. Speaking of which, I'd say try to figure those out next. Aside from having a greater note range, it actually makes things simpler

Of course, if you have any questions, ask away. More than happy to help.