cudASCII

2 Replies, 500 Views

Making this thread for updates to cudASCII.

Currently it's able to read in a .bmp file and convert it to ASCII. I don't feel like doing whacky fractional scaling yet so I'm working on other file formats.

My question is, should I just use the file extension as the file type (and verify the file signature is in fact that file type), or should I try that, and if it fails try to deduce the file type from its signature.

The second approach is more robust, the only problem is it's also much more difficult.
Mew is under the truck
(This post was last modified: 07-24-2023, 04:40 PM by Amber.)
Lmao, I'd just assume the format and if it doesn't work seg fault, I imagine as a library it'll only ever be fed raw pixel data anyways. Unless you plan to have a standalone version
Yours truly,
Ayydan
(06-25-2023, 07:31 PM)Ayydan Wrote: Lmao, I'd just assume the format and if it doesn't work seg fault, I imagine as a library it'll only ever be fed raw pixel data anyways. Unless you plan to have a standalone version

I wanna support a wide variety of formats. Basically you can hook into this and give it a filepath, a file descriptor/pointer, or just raw data.
Mew is under the truck



Users browsing this thread: 3 Guest(s)