• ripcord@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 days ago

    Considering the lack of paity, error correction.imdo, it’s pretty amazing that worked at all, ever. Even at those low bit rates.

    • bstix@feddit.dk
      link
      fedilink
      English
      arrow-up
      13
      ·
      3 days ago

      The most common tape formats did use a parity bit, and the data was doubled, so that it could attempt to correct it if an error occurred.

      The signal was coded as pulse-width modulation, so the amplitude didn’t matter much as long as the zero crossings were timed within an acceptable threshold. I don’t know the exact width of these pulses, but it worked fine when copying a tape at double speed or more.

      • Light-DelaBlue@jlai.lu
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        and amstrad was smart enough its separated code into “blocks” if a block failed you can just rewind and try again. it was strangely quite robust honestly.

    • addie@feddit.uk
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 days ago

      ZX Spectrum tape file format had a ‘checksum’ at the end of each block, which was just an XOR of all the bytes in the block, basically parity. Lead to a whole pile of R Tape loading error messages when your tapes were going a bit dodgy. CPU probably wasn’t fast enough to read the tape and do error correction at the same time.

      Describing the data rate as ‘low’ kind of understates it. Averages 170 bytes per second. A ZX Spectrum 128K game that took up the entire memory could take nearly 13 minutes to load.

      https://sinclair.wiki.zxnet.co.uk/wiki/Spectrum_tape_interface#Blocks

    • Light-DelaBlue@jlai.lu
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      3 days ago

      i mean tehre was demo on flexidisc (a floppy vinyl record) and record love to pop even new.