I had a feeling you were going to create such a thing 
Nice job.
Just as well as I'm afraid that you are trying to fix the problem by implementing "automatic pause" ;-)
Nice test 
No any problem in blueMSX (direct support for CAS files with BIOS patching), but the final sentence is missing with openMSX ...
Yeah, but patching BIOS is not emulation, is it? 
Nice test
No any problem in blueMSX (direct support for CAS files with BIOS patching), but the final sentence is missing with openMSX ...
Yeah, but patching BIOS is not emulation, is it?
And forcing automatically RUN, CLOAD or BLOAD is not emulation
Besides, you play with the words, as you know perfectly that the BIOS rom is not altered, only its 'ghost' in the MSX memory.
Just as well as I'm afraid that you are trying to fix the problem by implementing "automatic pause" ;-)
Well, I don't have plans to fix this in openMSX. Not unless some useful, no offense(*), examples turns up that don't work correctly (and maybe not even then). So to load your example in openMSX you need a better file format than CAS. And since this topic is about replacing CAS with something else that's a good thing, right
(*) Your example is very useful to demonstrate the problem, but you know what I mean.
What about low Hz wav?
2400hz, 4 sample bytes per bit.
With only sample values -127 and 128, maybe zip makes it as good as a bitstream.
What is needed is just a bitstream, except freaky encodings with differing pulse length.
p.s. I just tried to google what is "TSX casette format" and end up in this thread
no idea whether it is just bitstream.
What is a "ZX block".
The MSX casette has a bitstream, and all the bload cload etc work on top of that, the bitstream format needs to know NOTHING about it.
New inventions like a block number and error check would work out of the box.
Because it is a different protocoll layer.
That is why I am suspicious about the ZX formats.
MSX bitstream file:
4 bytes amount of bits
rest is bitstream
done.
The only thing it doesnt cover is different PPI wiggeling patterns and pulse length.
The ZX formats that feel "universal",
can they cover for example "a 1 bit shall be PPI wiggle UP DOWN UP DOWN UP UP, each one in different timing".
I guess no.
Now that I think of it, instead MSX bits the bitstream could contain "PPI wiggeling pattern".
With an MSX casette, the file would contain only these 4 byte values:
11001100
11001010
10101100
10101010
The question is whether this does zip to similar size if the packer finds the repetitiveness.
with this format, any other pattern can be made, odd timings need to crank up the hz.
So now what I did is practicaly invent a "1 bit wav" format... how about taking just wav. A "low hz wav 9600Hz" would consist of only these sample sequences:
-127,-127,127,127 for the 0 bit
-127,127,-127,127 forthe 1 bit
again the question whether zip finds an aceptable packing.
then the solution goes with NO new format. that would be the greatest sucess in format invention
