† ponyo † (bleelblep)So modifying the #Nothing #GlyphComposer in any way breaks the glyph preview inside the app. I would assume it's detecting either signature verification or comparing against hash files.
Also exporting custom sound packs and importing them into the unmodified app or settings still plays the custom sounds and corresponding glyph lights.
My guess is that #Nothing is exporting the finished compositions and encoding the corresponding CSV Glyph patterns in the .OGG file which is why it still works. #Nothing don't care about the sound packs themselves per se but the instructions inside the .ogg file.
Final note the number of rows inside the CSV correspond to how long the glyph lights are active while the columns dictate which ones.
I still have no idea what the values mean but I am guessing they're controlling how bright it should be.
I think the maximum value is 4080 and the minimum being 0 which is off. I assume nothing is using a custom bit of software for writing the CSV which means I'd have to brute force it manually which sucks.
Also exporting custom sound packs and importing them into the unmodified app or settings still plays the custom sounds and corresponding glyph lights.
My guess is that #Nothing is exporting the finished compositions and encoding the corresponding CSV Glyph patterns in the .OGG file which is why it still works. #Nothing don't care about the sound packs themselves per se but the instructions inside the .ogg file.
Final note the number of rows inside the CSV correspond to how long the glyph lights are active while the columns dictate which ones.
I still have no idea what the values mean but I am guessing they're controlling how bright it should be.
I think the maximum value is 4080 and the minimum being 0 which is off. I assume nothing is using a custom bit of software for writing the CSV which means I'd have to brute force it manually which sucks.
ROOTBLOG
