Re:Quake 1 port for Apple Watch
by js4ever on Saturday November 19, 2022 @05:52AM
(#33669051)
Quake 1 was roughly 80mb once installed. Why this version is taking 1gb?
[ Parent
| on HN ]
What Moore giveth, Gates taketh away...
Bill Gates had a hand in Apple’s Watch OS?
Re:Quake 1 port for Apple Watch
by jamesgreenleaf on Saturday November 19, 2022 @06:56AM
(#33669352)
Let us consult the Book of Jobs.
So, Lord "Objective-C" Swift's binary blob size is harder to beat than Quake?
Re:Quake 1 port for Apple Watch
by andrekandre on Saturday November 19, 2022 @07:30AM
(#33669537)
looks like music (.wav) files...?
from the github:
> Extract game music from the gog game files:
bchunk -w “game.gog file location” “game.cue file location” track
(Music tracks will extract in to current working directory (track02 -track11.wav).)Original soundtrack was streamed from the CD. Seems like compressing to mp3 would be a big help
Decoding would probably be an issue. It’s already on the cusp with the current audio files, mP3s would probably throw it over the edge.
Assuming for the sake of argument that playing back mp3s during gameplay is beyond this device, resampling the wav files to halve the sampling rate when extracting them certainly isn't. You'd get half the storage back, the audio presumably wouldn't suck any worse than it already does on that little device, and it should all work since the 44.1Khz sampling rate isn't baked into the wav file standard (but who cares, you've got the Quake source code anyhow).
It'd be an interesting exercise to see how much you could lower the sample rate without it sucking. On second thought, you could convert stereo to mono first, without even worrying about the sampling rate, and get half the space back. But I'm sure you could do more.