- Joined
- Apr 12, 2021
- Messages
- 1,846
- Reaction score
- 15,185
- Awards
- 19
Lmao, not a fan of this metaverse shit.
For almost every artwork I produce, I use both of the following: Photoshop + After Effects. Photoshop mostly because I'm used to it. After Effects because there is absolutely nothing like it out there if you include the plugin ecosystem.This is cool. What are you using, Gimp/Photoshop?
Yeah I used to be huge into C4D... until one day, I wanted X-Particles, and couldn't afford it... so got kinda mad with the whole C4D ecosystem and ditched my 3D work altogether.Nice. I used to do a lot in Photoshop, C4d, Vue and stuff like that, but it's been awhile. I miss C4d and Vue. I might have to get back into them.
What? I understand what you mean but I hadn't thought of altering images like that (not even sure if I could do it)open the image in Audacity
It was one of the first methods of glitch art that I learned!What? I understand what you mean but I hadn't thought of altering images like that (not even sure if I could do it)
I assume it will take a lot of saving and reopening / switching between programs to see if you liked what you changed.
Yup, but once you get used to the workflow it's not that bad reallyI assume it will take a lot of saving and reopening / switching between programs to see if you liked what you changed.
Yeah, but it's such a good way to sort of learn the art of glitching. I started off opening images in notepad and glitching them manually by editing the RGB values. Different formats give different results due to different compression methods. Next I moved to Audacity, and tried glitching using the filters. Obviously both of these methods are quite unpredictable and fiddly and time consuming, but it sort of gave me the base knowledge and understanding of the file formats and the math behind the filters for me to then go and code the specific things I liked to see in Processing, and when you're coding it yourself, it becomes very easy to streamline the saving and adjusting methods so it becomes much less fiddly!It's kinda neat. Very fiddly, tho. The original image was a fractal done in JWildfire. Then in Audacity, used a few filters.
That's seriously hard code, manually editing the image files. This does give some really interesting effects once you figure out what filters work and what sort of numbers you need to get the right effect. I wonder what else could be used here... hmm...Yeah, but it's such a good way to sort of learn the art of glitching. I started off opening images in notepad and glitching them manually by editing the RGB values. Different formats give different results due to different compression methods. Next I moved to Audacity, and tried glitching using the filters. Obviously both of these methods are quite unpredictable and fiddly and time consuming, but it sort of gave me the base knowledge and understanding of the file formats and the math behind the filters for me to then go and code the specific things I liked to see in Processing, and when you're coding it yourself, it becomes very easy to streamline the saving and adjusting methods so it becomes much less fiddly!
Ya, that should've said "hard core". Damn autocorrect. Damn autocorrect straight to the abyss.That's seriously hard code, manually editing the image files. This does give some really interesting effects once you figure out what filters work and what sort of numbers you need to get the right effect. I wonder what else could be used here... hmm...
So, the trick here is you have to select most of the file in Audacity, but leave a second (or few, depending on file size) in the beginning and end not selected so the header doesn't get corrupted. This is kind of a pain in the ass. What I ended up doing was importing an image, hitting control-a to select all and then at the bottom of the Audacity screen there's a counter for the "Start and End of Selection", which will start at 00h00m00.000s and end at however long the image is.I'm trying it at the moment but can't seem to open the file after saving it. Will have to take another look in the weekend.
This "converting" of an image to sound is actually pretty cool already though.
You could make a TIFF file of a seal / sigil, convert it to static noise and play that on repeat when meditating or preparing for a ritual
When working with uncompressed files it's extremely mundane. At the end of the day, uncompressed files are just a list of pixels, so editing them manually is basically just pixel art. But doing math on them definitely yields some interesting results. But that's basically easier to do using filters or code anyway... so manually text editing uncompressed images is basically just the first step of understanding the process.That's seriously hard code, manually editing the image files. This does give some really interesting effects once you figure out what filters work and what sort of numbers you need to get the right effect. I wonder what else could be used here... hmm...
Yeah, people actually do this. You can take it one step deeper by looking into spectrography.This "converting" of an image to sound is actually pretty cool already though.
You could make a TIFF file of a seal / sigil, convert it to static noise and play that on repeat when meditating or preparing for a ritual
I'm trying it at the moment but can't seem to open the file after saving it. Will have to take another look in the weekend.
Incogs answer should help you.So, the trick here is you have to select most of the file in Audacity, but leave a second (or few, depending on file size) in the beginning and end not selected so the header doesn't get corrupted. This is kind of a pain in the ass. What I ended up doing was importing an image, hitting control-a to select all and then at the bottom of the Audacity screen there's a counter for the "Start and End of Selection", which will start at 00h00m00.000s and end at however long the image is.
In select start section, add 1 second (so make it 00h00m01.000s) and in the end section subtract 1 second (if length was 00h02m21.062s, change it to 00h0220.062s, subtract 1 second). That usually does it. You can get more granular because depending on the file size, it may leave a bar of unchanged image at the top and bottom, which means you would need less than 1 second.
Also, you can import and export in either Ulaw or Alaw. Doesn't matter which you choose (at least with a bmp), but you need to save it as the same format.
Seems to be the 2 biggest issues leading to the exported image not working. Usually it's because the header got accidentally nuked (at least partially).
I just tried that with the seal for Paimon and it was seriously weird:I'm trying it at the moment but can't seem to open the file after saving it. Will have to take another look in the weekend.
This "converting" of an image to sound is actually pretty cool already though.
You could make a TIFF file of a seal / sigil, convert it to static noise and play that on repeat when meditating or preparing for a ritual
Yeah, image data transcoded into audio is almost always just noise.I just tried that with the seal for Paimon and it was seriously weird:
https://soundcloud.com/user-830161545%2Fpaimon%2Fs-uBrGhYGEMpw