|
| |
|
Bitfire V1.0-Alpha [2021] |
Website :
https://github.com/bboxy/bitfire/
Credits :
| Code | .... | Bitbreaker of Arsenic, Nuance, Oxyron, Performers |
| Test | .... | The Human Code Machine of Arsenic, Masters' Design Group, MultiStyle Labs, Oxyron, Performers |
| Help | .... | Krill of Plush |
| | | The Human Code Machine of Arsenic, Masters' Design Group, MultiStyle Labs, Oxyron, Performers |
Download :
Look for downloads on external sites:
Pokefinder.org
User Comment
Submitted by soci on 24 March 2021
| Managed to improve the zx0 compression time to a more reasonable 9,624s and 0,595s (-q) since last time. I'm not sure it's going to be a net win overall as it's unlikely any future savings will compensate for the time spent on this. But that was not the point anyway ;) |
User Comment
Submitted by Sparta on 20 March 2021
| Nice speed improvement and impressive compression ratio with ZX0! It's good to see that there are now two loaders using every byte in every sector on the disk. :) |
User Comment
Submitted by Krill on 12 March 2021
Joe: Sort of, Loader Benchmarks - but then this isn't really about "best", because no silver bullet and all, but rather best for your purposes.
That said, still need to patch a few things to catch up in that benchmark. =) |
User Comment
Submitted by Joe on 12 March 2021
| Cool work! Is someone still doing those "scientific studies" on which loaders are the best/benchmarks? |
User Comment
Submitted by Digger on 12 March 2021
| Time to try it on my half legged 1541-II. |
User Comment
Submitted by Bitbreaker on 12 March 2021
| Yes, it does inplace decompression by default, as long as it can rely on the load-address given by the file. If you relocate the packed data, an end-marker is added to have other means to detect the end of decompression. Then overlap-restrictions apply and the file grows by 18 bits. |
User Comment
Submitted by soci on 12 March 2021
| Interesting. So zx0 was modified to do in-place decompression? A quick test shows compression time became insane. 43Kb in 1m53,557s now vs. 0m0,069s with bitnax. For a 700 byte gain. With -q it's a more reasonable 0m3,789s for 400 bytes. Will check it in detail later. |
User Comment
Submitted by Frantic on 11 March 2021
Thanks!.
Somehow I now feel like I should code yet another loader and name it Sprinkle |
User Comment
Submitted by Krill on 11 March 2021
User Comment
Submitted by Frantic on 11 March 2021
Which are the four ones? Krill's loader, Bitfire, and...? Spindle? ...and?
I haven't followed this topic for a while. |
User Comment
Submitted by Krill on 11 March 2021
| Now the current 4 popular demo IRQ loaders are all playing in the same on-the-fly decoding ballpark! \=D/ |
User Comment
Submitted by Pantaloon on 11 March 2021
| oh oh oh :) time to make a new demo to test this. |
|
|
|
 | Search CSDb |
|
| Navigate | |
|
| Detailed Info | |
|
| Fun Stuff | |
· Goofs
· Hidden Parts
· Trivia
|
|
| Forum | |
|
| Support CSDb | |
|
 |  |
|
