I just tried with tape2wav and WinTZX and the results have very similar length and size on my computer ... (around 670 KB). Odd, indeed. In this instance, both are incorrect results. These are much shorter than they should be, which is about 724 KB. On a related note, I just tried the version of Lone Wolf III posted by Sergio in https://sourceforge.net/p/fuse-emulator/bugs/352/#d9df, and was finally able to load it on my +2A. Here's what I did: Converted the TZX to WAV in Tapir Boosted the level...
That would make sense. I wonder if it's worth having an option to do that or if Lone Wolf is the only case where this is important. Did some more experiments today with my turbo loader. I made several audio recording from my original TZX and compared them. Looks like aside from Tapir, few other methods can produce an audio file that is equivalent to it. I'm attaching my original TZX and a screenshot demonstrating how each audio file lines up at the end of the recording (all files are aligned from...
Basil I can load if I rewind and try again the failing blocks. Just tried Basil on my +2A today using the audio generated by Tapir. No go. I then opened the wave file in a wave editor and inverted the phase of the first custom block. It started loading (the border stripes changed color from green/black to green/cyan/black), but the black didn't load. The loader did, however, manage to fetch the flag byte and reject the wrong blocks. Really odd.
Okay, I did some tests with my loader. A table with Bit 3 Bit 4 Fuse 128K (Toastrack) +2A reset reset loads, quieter signal doesn’t load, same loudness loads, same loudness set set loads, louder signal doesn’t load, quieter signal loads, same loudness toggles reset loads, quieter signal detects pilot, doesn’t load, stuttering data signal loads, same loudness toggles set loads, louder signal doesn’t load, quieter signal loads, same loudness set toggles doesn’t load, crackling doesn’t load, crackling...
Okay, I did some tests with my loader. A table with Bit 3 Bit 4 Fuse 128K (Toastrack) +2A reset reset loads, quieter signal doesn’t load, same loudness loads, same loudness set set loads, louder signal doesn’t load, quieter signal loads, same loudness toggles reset loads, quieter signal detects pilot, doesn’t load, stuttering data signal loads, same loudness toggles set loads, louder signal doesn’t load, quieter signal loads, same loudness set toggles doesn’t load, crackling doesn’t load, crackling...
Okay, I did some tests with my loader. A table with Bit3 Bit4 Fuse 128K (Toastrack) +2A reset reset loads, quieter signal doesn’t load, same loudness loads, same loudness set set loads, louder signal doesn’t load, quieter signal loads, same loudness toggles reset loads, quieter signal detects pilot, doesn’t load, stuttering data signal loads, same loudness toggles set loads, louder signal doesn’t load, quieter signal loads, same loudness set toggles doesn’t load, crackling doesn’t load, crackling...
but the bits 3 and 4 are not used to produce any output But they are. When I was experimenting with my loader, I accidentally incorrectly left bits 3 and 4 in a "wrong" state while outputting to Port 254. This resulted in Fuse outputting a louder volume during a load, but the load proceeded as normal. I became curious and decided to do some test on real hardware. I couldn't get anything to load on the Toastrack (it just didn't see any valid signal and produced some crackling sounds), but the +2A...
All the TZX files that I can load after my patch work with the assumption that high means ear=1, but there's no guarantee that all other TZX files do the same. This could be related (even though indirectly), but at least on the 48K/128K, when outputting to port 254, a 1 in the MIC bit means low. So, to have the output low, MIC (Bit 3) must be 1 and EAR (Bit 4) 0. This may or may not be true for the +2 and later, since, as I mentioned earlier, manipulating these bits produces different results on...