I made my own Image File Format

[@FlushDesert22]

"I'm tired of these stupid image file formats, so I'm contributing to the problem"

[@akaithecreator7448]

439 likes and 1 reply?

[@Ali_Jafari]

😂😂

[@BadmanYT-1254]

@@akaithecreator7448 why are you here

[@Sirbozo]

lol

[@nonexistentsquare2092]

@@BadmanYT-1254bro really said “Begone fool, for thou hath spoken too foul a word to remain” 💀

[@kousheralam]

wow, coverting a binary -> string -> do string manipulation -> show from the string. What's inside your head bro, it's pure genius

[@haraldbackfisch1981]

Going from int to string to almost always a terrible idea, just thinking of memory or lack of multiplication for data manipulation, have fun blurring in hex with strings. I love that he did it tho, sometimes u just gotta f around and find out, else we wouldn't have nice things in the first place :)

[@AOSP-is-still-Linux]

​@@haraldbackfisch1981 I think the OP was ironic, as the format of the message felt like that.

[@haraldbackfisch1981]

​@@AOSP-is-still-Linux youre right idk what i was thinking... wasnt thinking i guess 😅

[@Aloofmeepgamer]

Srsly

[@stgigamovement]

BWTC32Key B3K files are what happens after crossing compression with encryption with binary-to-text encoding. It actually works well in spite of me doing it because I don't like Base64.

[@lizkeres2593]

The major difference between jpeg and PNG is not only transparency but also the compression

[@borstenpinsel]

Both are compressed. Just with really different methods. Jpeg tries to emulate chunks of 8x8 px with parameters to a trig function (lossy to veeerry lossy depending on some parameter, but even the best quality (and thus worst compression factor) is very lossy). PNG however is basically a bitmap (lossless, no compression) which is then compressed with tar/gz algorithm. Basically cheating by making the 3rd party compression algorithm part of the file definition. It's like putting wave files into a zip folder and calling it a new audio format.

[@ursulmusic]

​@@borstenpinselSomething like audio FLAC, as it's lossless compression for PCM audio?

[@milesmartig5603]

jpeg and png both can store a lossless image

[@CryptoOfficial]

@@milesmartig5603 jpeg is per definition a lossy format even if you crank up the quality to 100% it’s still doing magic things with Fourier transformation and converting your image in a lot of lookalike patterns that they are close enough of the original pixels.

[@Henrix1998]

​​@@borstenpinselYou can't say PNG doesn't have compression, it just has lossless compression, even before tar/gz

[@y32code16]

2:27 "turns out its not 3.5 times more size" *shows a picture of 3.3x* "it can go up to 98 percent more size" *shows a picture of 98 times more size* on a 160.2 times more size image. yep thats face dev for ya

[@Kynatosh]

Yeah that was really weird, bro can't calculate

[@MrNosounder]

I fucking love how random these numbers are

[@dalhaan]

Tip: you can half the size of your files if you store the RGB values as raw bytes instead of characters. Each character is 1 byte long (assuming you are using a 1 byte character encoding like ASCII or UTF-8), but a hex character just represents half a byte in a human readable format. "9e", for instance, just represents the number 158 (uint8) which only takes up one byte, where storing "9e" as two characters you are using two bytes. Hex goes from 00 (0) -> FF (255), which is exactly how much a byte can hold. To do this you'll need to allocate a buffer of the number of pixels in the image times 3 (RGB per pixel = 3 bytes (1 byte for each colour) * number of pixels), then for each pixel: write a uint8 for the red value, write a uint8 for the green value, write a uint8 for the blue value. To read the file, loop over each pixel and read each byte (uint8) instead of writing.

[@dalhaan]

If you wanted you could also add an alpha channel by just adding an extra byte after blue, this would make each pixel 4 bytes instead of 3. And now you've created the bitmap image format 🙂

[@sollybunn]

Doesn't he do this 3m into the video

[@FaceDevStuff]

@@sollybunn I only stored the metadata (width & height) as bytes, the rest is full of hex values

[@rumisbadforyou9670]

he knew that, he's being rеtагded for no reason. he's just wants to jack up the yt algorithm, thinking "one day i will be making quadrillion dollars per nanosecond by pооping out: 'i pressed a key on my keyboard' / 'i copied seven lines of code from stack overflow' type of videos, yupeee!"

[@sollybunn]

@@FaceDevStuff that's a bruh moment (you didn't really expand on "were dealing with raw bytes now" so that's what I assumed)

[@dvidpi]

wowzers, im converting all images in my gallery to .bruh files! so efficient, fast and lightweight

[@m4rt_]

situation: there are 10 competing formats solution: lets create a new one to replace the old ones. new situation: there are 11 competing formats (Heavily based on an XKCD comic)

[@alastor--radiodemon7556]

bro made a .bmp

[@magicjinn]

was about to comment this

[@_kitaes_]

but worse

[@alastor--radiodemon7556]

@@_kitaes_ just a tiny bit worse but it balances out with the funnies :3

[@magicjinn]

@@_kitaes_ yeah, but it ends with .bruh, worth it

[@nomorebadmilo]

bro, why are you here, smily face demon.

[@Ceelbc]

By converting it into hex of 6 characters, you lost transparency. However, if you made it hex of 8 characters long, you could keept the transparency.

[@blissful4992]

very inneficient

[@Luna5829]

with 8 characters you'd only get 1 decimal point of transparency 9 characters is pretty good tho

[@Ceelbc]

@@Luna5829 RRGGBBTT, with T transparency. So 256 values. What do you mean with 9? Am I missing something? (I don't count the # you would write in code since it is not needed)

[@Luna5829]

i forgot the transparency could also be in hex and not in decimal but still, with T / 255 being the transparency, you'd miss quite a few numbers

[@LimoDieFlasche]

@@Luna5829 You wouldn't miss anything visible to the human eye ^^ There's a reason why no one uses amounts above one byte (2 hex digits) per color

[@henrispriet9812]

Instead of making an image compression format, bro made an image expansion format

[@realrunnow]

1:21 delusion on a next level

[@joseph_gerald]

Storing raw bytes is unheard of why not use a human readable 4bit representatipn instead (hex)?

[@urisinger3412]

If people are gonna read your image file they will do it in a hex editor​@@joseph_gerald

[@bits360wastaken]

@@joseph_gerald Not sure if stupid or trolling, your not going to give an image format the ability for someone to download it to their desktop, open up notepad, and read an images letters and reconstruct it in their mind at the cost of a 10-100x file size increase. And storing raw bytes is unheard of, look at the .png and .jpg format specifications for a clue on how deep it actually goes.

[@joseph_gerald]

@@bits360wastaken sorry was sarcasm 🥲

[@_kitaes_]

@@bits360wastaken png stores compressed raw bytes

[@thechillguy_mynewcharater]

web✅code editor✅programing lang✅text editor✅image file format✅operating system❌

[@stgigamovement]

What's next? A coding font? Don't know if it can have more characters than UnifontEX.

[@dr_s_e_x]

Now make a .huh file that is an audio format

[@smokedice]

this but its just a .wav stored as a string

[@HiloYT]

and then .bruhuh for videos

[@Koreley]

@@HiloYT you could make a conlang out of this

[@wouldyouskibidi]

.huh3 then .huh4

[@PJM257]

judging by how badly he struggled with an image format, i don't think he's ready to try an audio format lol

[@YoutubePizzer]

avif is actually conceptually really cool: if you guys follow video formats, there’s been a big push to add AV1 support to everything because of how much of a huge leap in quality it is over essentially everything else. So much so, that if you encoded an image as a single frame of an AV1 video, it would be better quality than the other image formats available. So that’s exactly what it is. It makes a tonne of sense to use the same compression algorithms for both video and image and could in theory mean you could make hardware-accelerated images too. Very resource efficient, it would be great if we could just magically convert absolutely everything to use exclusively AVIF from now on

[@neutronpcxt372]

It's not. JXL is better.

[@Yiss8]

JXL better

[@pachinger]

No it actually doesn't make a ton of sense to use the same compression for video and static images. Video codecs usually use the information of multiple frames to be more efficient. Just thinking about P/B/I-frames, chroma subsampling, etc.

[@chonchjohnch]

Hope alphabet sees this bro 🫶🏻

[@waralo191]

You should check out jpegxl, google is blocking it to maintain their monopoly. Since they own AVIF, and want it to become the standart

[@KryptonTR]

5:08 this song is a masterpiece

[@FaZekiller-qe3uf]

"Hex" is representing the color data in base sixteen whilst "RGB" (don't include the alpha channel, it's not a fair comparison) is representing it in base 10. It's the same exact data. There's no space "reduction" if you don't bloat it by storing it in ASCII, but you figured that out. Instead of bloating the file with line breaks you can just have a small header with the height and width.

[@o_q]

the interlacing on this video is making me crazy

[@Aeduo]

I think that might be part of the shitpost.

[@FaceDevStuff]

@@Aeduo nope, just plain stupidity on my part

[@RockRemastered]

I was thinking the exact same. Now the real question is, does it deinterlace ?

[@foco5657]

@@RockRemastered probably not because youtube's VP9 compression screws with interlacing

[@RockRemastered]

@@foco5657 that's pretty right. Resizing is the worst thing. But downloading the h264 video would maybe work.

[@per2632]

3:48 hex colors don't even have transparency and you used alpha type opaque for the png, so i'm surprised it showed anything other than complete white before you put a number there.

[@thefirstuwu8874]

1:22 I'm not an expert, but one byte should be able to give 256 unique combinations, as it has 8 bits and one bit has 2 states - 2 combinations ^ 8 bits = 256, we even have a place for zero. (an int value usually weights 2-4 bytes, but I don't think we need its extra functionality for storing a number from 0 to 255). HEX uses 6 characters - each character is 1 byte, so 1 * 6 = 6. I think you can do both methods equivalent in bytes, but RGB is more intuitive. Edit: Oh, everyone already commented about this :p

[@maxamillanman9050]

Low-key you explained better than my Prof tho

[@sumlittleguy]

You can make the image of color layers. For example: if it's just the background you determine the color of single pixel and then paste this pixel into different location instead of finding out the color of each pixel. Repeat that multiple times with doffirent colors and you get and image! It will be VERY light no matter how many pixels are there on X and Y coordinates while the image contains only 1 color.

[@marcels.7074]

i wanted to make a JSON image format { "meta": { "size": "69x420" }, {"pos":[1,1], "color":"696969"} .... }

[@FaceDevStuff]

sounds hella inefficient, love it!

[@SIMULATAN]

Should call it "jif" for maximum confusion

[@thefirstuwu8874]

@@SIMULATAN can call it "Jim" - Json IMage

[@bambi186]

Absolute madman

[@mgord9518]

This isn't too far off from plaintext images from the days of old like PPM. Sure, it's absurdly inefficient as far as size goes, but you can edit it with nothing but a text editor, easily understand the format just by looking at it and they're very rarely used for large images anyway

[@devaraanimation]

So this is what it feels like to be the guy who made the .webp file format

[@sagnikkundu89]

Webp is good actually pls research

[@devaraanimation]

@@sagnikkundu89 so the joke went over your head. I was talking how it got the same degree of support as .webp.

[@sagnikkundu89]

@@devaraanimation xDd. It wasn't obvious to me

[@hedgehogsch.7270]

congrats! You just invented the netpbm file format 😊

[@JamesR624]

The who-what now?

[@nathanpgratner2501]

I will be using .bruh images as the primary image type on my pc

[@black360d]

Same

[@LambOfDemyelination]

why store the hex as a literal string, a byte can be represented in one character (byte), instead you use two bytes to represent one byte??

[@Fifasher2K]

E in bruh is for efficiency.

[@rka3477]

congrats you invented .bmp

[@urisinger3412]

But 2x bigge

[@kevenrodriguesmeirelles2241]

you're in my top 10 Dev KZbinrs, I love your projects!!

[@Potencyfunction]

I dont understand anything from it, I belive I am not for that. My skills and preferences are other, but is always good to have an eye on what is real and in trend with others.

[@remboldt03]

You just made a worse bitmap. But I really like it. I love those indi projects

[@ToxicMothBoi]

Finaly a good file format, the .bruh format🙏 Like god intended

[@chickenspaceprogram]

my man reinvented bitmap images, incredibly based

[@Pcexperiments]

you can use regedit ti automatically set how it opens, what icon it has and add it to `right click>new` menu

[@KyriproShorts]

What in the.bruh is this. Like what the.bruh

[@Mats_Games]

1:15 1080i detected

[@TheBriti-Critic]

I was waiting for the "This video is in the .bruh format" 🥵🤧🥵

[@alword]

.bruh4 video with .bruh3 sounds

[@Ahnaf_Shariar]

WOW, we are getting .bruh image file format before GTA 6.

[@Sartfla]

This is actually almost exactly what I wanted.

[@GalaxinTM]

avif still superior - transparency - better compression than jpeg - can be animated like gifs (comparable to video format quality)

[@official-obama]

according to wikipedia, it is open and royalty free too

[@urisinger3412]

​@@official-obamaPNG and jpeg both are

[@nbvehbectw5640]

When you talked about storing RGBA in characters and not bytes, I was like.... bruh.

[@kibbewater]

Every channel in RGBA are only a byte long. You could fit an entire pixel in the space required for an int. Using string for for the color will double the size for each pixel

[@xFifaEuro271]

man i love this video.Bruh

[@katamari_]

thank you for defeating the monstrosity that is webp files

[@deventerprises2640]

I think the issue with the tremendously high file sizes maybe because you are storing the ascii representation of the hex codes where in fact you can store hex codes as raw binary in the .Brun file

[@poka26ev2]

This reminds me of the .stalin image I created 3 months ago to send sus photos in case the group chat gets leaked

[@poonamshah3930]

At this rate bros about to make his own programming language to make these in....... oh no wait he already did it

[@MaxCE]

i always had an idea to detect text and store the characters used like as a font. then it would only store the position of the text. this would be useful for text over detailed backgrounds.

[@BruhDOTcam]

Interesting image file format.

[@RealUniCat]

that's EXACTLY what i wanted to do, except in javascript but i gave up because it's too hard and i wanted to do this in the current year 2024

[@stgigamovement]

BWTC32Key is a homemade file compression program with custom format written in Javascript.

[@RealUniCat]

@polonezzz stalker go away

[@RealUniCat]

@polonezzz I know

[@kevinchandra280]

Bro spent much hours, energies, and computer memories just for this "meme".

[@ygypt]

rgba and hex are not mutually exlusive. rgba means ur storing red green blue alpha, and hex just means ur encoding as base 16 instead of base 10. what you did was turn rgba into rgb, because you remove the 7th and 8th hex characters that represent the alpha

[@snowbelldog]

In addition, its format will be significantly larger, since rgba only requires 4 bytes (32 bits)... hex requires 2 bytes per color, which for rgb results in 6 bytes instead of 4 bytes, even without a alpha channel. With the hashtag it's even 7 bytes. I haven't looked any further, but he has no idea what he's doing 😅

[@slavatar1337]

blazingly fast file format

[@angelocore]

Yo you can try to convert the hex back to binary instead writing it as text, it will make the file size less for sure

[@okunamayanad]

2:28 98% more means like around 1.8~1.9x 98x the size means 9700% more so there is a huge difference in what you say and what it says on the screen.

[@MePeterNicholls]

“I’m not an expert…” but does this

[@glengal6490]

Though most of your videos are completely useless. It teaches me more than my college. My favorite youtuber so far. Love you brooooo

[@KosinsStuff]

It is pretty easy to make your own file format, you really just lack support for it since no one knows it exists or how it works

[@HighFidelityFox]

this is literally the XKCD comic about standards 😂

[@randospawn7495]

You can say probably update the file format by telling it that if multiple pixels in a row are the same color that they could be simplified to the amount and then the pixel data, otherwise just the pixel data.

[@insane.braindamage]

i think the worst time of image file formats when you try to save them is "webm" or "webp"

[@glintcoretheprotogen]

i want you to make this more efficient than pngs so we can take over internet

[@Stepanchicko]

bro just made bmp with hex

[@notkeehan]

Beautifully chaotic

[@2Deep.]

We should make it more better.

[@SKIENCE-X9PAT]

the disguised file formats are relatable

[@supercrazy50000]

your conversion algo can be useful to show images on oled displays

[@THEAXOLOTT]

Make this for your browser

[@SirMato]

3:21 interesting background song choice

[@SSQMinky]

18

[@stgigamovement]

BWTC32Key is a homemade compression format.

[@JDoawp]

Sooo, a ppm file but with hex instead of RGB? :p

[@Wilsons-World]

Interlaced! This looks great on my HD Trinitron.

[@superlavahair1536]

they make hd crt tvs?

[@Wilsons-World]

@@superlavahair1536 Yes! They're also 16:9. My set has HDMI.

[@foco5657]

i don't think so cuz youtube's compression fucks with interlacing artifacts

[@Wilsons-World]

@@foco5657 Good point. If s are blocking together 2 or more lines, that could totally ruin it.

[@peterweston6588]

If you are storing the hex in ascii, you can zip it like any text file.

[@fahrulrputra2589]

Ah yes, smartest rust programmer

[@HGStyleOfficiel]

you didnt even bothered trying to compress it using lzma... i love that file format xddd

[@Trayfellow]

Close enough, welcome back carykh

[@DJruslan4ic]

Making a file format is easy (i guess). Engeneering how it actually stores, how to parse it, and other stuff is the hard part

[@infiteri6030]

When i did this, i turned an png from 250kb to 10mb, the png took 1.2 s to load, the custom imagr took bout 0.02s. Nice

[@MasonAlex-f9p]

JFIF is a bitmap graphic that uses JPEG compression.

[@Internat-doener-federation]

0:25 that's wrong, jpg cam be transparent, but that's pretty uncommon.

[@maddsua]

bro reinvented bmp but with extra steps

[@ebselectronics]

Definitely using .bruh from now on

[@Gardener-AI]

This is somehow so captivating

[@AlbySilly]

3:47 My guess is that the rendering engine uses floating point numbers between 0-1 to display the graphics while the way the file is saved gives an integer of 0-255, try dividing the color value by 255

[@manshenriksson]

Yeah 1/256 ~= 0.004 lol

[@Elitsa_27]

this is genius , evil , but genius , you can troll your friends to think the got a virus with one image☠

[@guppy13]

this certainly is a bruh moment

[@candybluebird]

this dealt psychic damage :

[@grady631]

I did this once, but it had a really low color amount, probably around 8 colors, a locked really low resolution, and would have to be decoded by hand (it was binary numbers in .txt. REALLY inflexible format)

[@STG24]

0:11 JFIF stands for JPEG File Interchange Format It is apparently better than JPG/JPEG and some windows 10 updates cna cause browsers to save in .jfif instead of .jpg or .jpeg

[@YariCodes]

the data of a .jfif file is the same as a .jpeg. it's just an alternate file extension, like .jpg to .jpeg.

[@bukdays]

brother 255 255 255 and #FFFFF take the same amount of bits. Both are three values of 2^8. A HEX 'digit' represent 16 possible values. 2 HEX values represent 16^2 possible values, that is 256 possible values. Just like the each of the RGB values. HEX is just numbers represented in base16

[@ErCapoAlex]

It’s also compression (ok both are compressed but differently)

[@Tuntor689]

hey i’ll take it over .webp

[@codeman99-dev]

2:32 That's not a percentage buddy. "100% more" means to double. Starting at 3mb and then adding 100% more would be 3mb + 3mb.

[@fiddleabout]

"buddy 🤓☝️"

[@MaurOwO]

imagine hiding images in the bruh format is s very goood idea

[@AlanBurr25]

bro reinvented the bitmap image lmao

[@lancemarchetti8673]

Nice work!

[@TurquoiseFan23]

Oh, how I understand you, saying twelve instead of twenty...

[@Akhulud]

avif is actually the best file format

[@m4rt_]

jpeg is losy (you loose details) png is lossless (you keep all the details)

[@gold4668]

3:24 OH MAN NOT RAM RANCH 💀

[@nooneinpart]

EIGHTEEN NAKED COWBOYS IN THE SHOWERS AT RAM RANCH

[@Monkeymario.]

0:33 avif if i remember right is a image format made by netflix i tihkn its made by netflix and avif is actualy really good at small file size while keapinb detail and its a lot better than jpeg abd has TRANSPARENCY :D also the video equivalant is webm which is made by google but it pretty much is the video equivalant of avif infact i think avif stole from webm right?

[@nooneinpart]

WebM came way before AVIF, but it is indeed also based on a video format like AVIF. WebM is based on VP8, the precursor to VP9 that KZbin currently uses. AVIF is based on AV1, the successor to VP9, and KZbin also uses that but only for popular videos because it's harder to encode and not that many devices currently support it compared to VP9. WebM and AVIF are basically just single-frame videos with no audio.

[@ChrisGT4G]

as a unity developer .jfif is my 1# opp when importing textures

[@spooksoh]

this vid deserves a ✪