I mean as of now all I've done are a few experiments with PCM. I made this by rigging up a google colab to turn audio files into P8 strings. Then bikibird came up with Defy, which is a much better solution than my janky uncompressed one. The most recent thing I made is a terrible "game" I made as a joke.
Luchak made a FANTASTIC ReBirth-ish groovebox program though! I'm planning on like...making a whole album using it alone lol
Have you released/are you planning to release this as a p8 cart? or do you have the source code on github? Because I'd kinda like to fool around with it, since I'm teaching myself DSP with P8. (And I may or may not be way into the idea of developing modules for this platform :P)
Yeah, I'm running into rendering issues too. None of the walls on the base floor are rendering, though I do see some walls on the cellar floor. I'll try making my own maps to see if I can figure out what's going on, but I'm not promising I'll be able to figure anything out.
Not at the moment, I sort of hard-coded all the variables when I made this, since I was more considering Vaporgene as a "conceptual piece" itself than a "legit" plunderphonics generator.
I'm considering remaking this in Python or JUCE or some other actual programming language eventually though, since all the stuff it does is pretty simple stuff for most audio libraries. And looking back, I think it probably would have been a good idea to give the user some amount of control over the chaos.
I'm gonna have to look into some way to let the user change audio drivers without making them have to get a full copy of Max. I'll keep everyone posted.
Hm. I'm actually at a loss. This is one of the problems of using somebody else's engine to make a program, sometimes the problem is on THEIR end. What I'd do is make a post on the forums of cycling74.com with screenshots attached explaining that you're trying to use an executable made with Max 8, and give them the info about your OS and sound card as well. If you do, link me to the post in case there ends up being anything I can do about it. Here's hoping we can figure this out.
Thanks for informing me about this issue. I might just need to recompile it with the latest version of Max/MSP for Windows. I'll try to get this done as soon as I get access to a Windows computer.
Okay, a lot of people are saying that the Max console is giving them a specific error. The Cycling 74 website says that the issue should be fixed if you update your sound card drivers, so please let me know if that fixes it!
According to the Cycling 74 website, "ad_mme: stopping due to error" is an audio device driver issue, and they say the fix is to update the drivers for your sound card. Do let me know how that goes though, if there's anything that I can do on my end I'll try to fix it up, but this seems like it's an issue with Max/MSP in general.
According to the Cycling 74 website, "ad_mme: stopping due to error" is an audio device driver issue, and they say the fix is to update the drivers for your sound card?
I'm sorry, I hope that this works. Unfortunately it seems to be less of an error in the program I made and more of an error in the software that I used to make it. I feel your pain, I'm trying to work on creating another Max/MSP device right now and keep running into a crash issue that seems to be on the part of Max/MSP itself. :/
I'm...not entirely sure. I only have access to a MacBook right now, so the menus tend to pop up in the toolbar at the top of the screen. I'm SURE there's a way to access the options on Windows but I don't know off the top of my head HOW. I'm guessing maybe right click in the program or its icon in the Start menu bar?
The MIDI settings are totally irrelevant, they're just there because Max/MSP takes MIDI input, and exporting a Max patch as an executable really just means wrapping the Max/MSP engine itself. That's why if you explore the files of the executable, you'll find a bunch of assets that aren't used (these come stock with Max). That said, I probably should have done some "optimization" involving deleting any unneeded assets from the executable, that would quite likely cut down the file size significantly. As for the MIDI...well...we'll see if I can think of any ideas for that. ;)
Hey! Sorry that I haven't been so active with this project lately, been super busy with my grocery day job. Really appreciate the input, though.
I like your ideas. My original intent for this program was to make something that sort of blurred the line between music creation software and a musical composition in and of itself (in the same sort of spirit as John Cage's radio pieces) so I didn't put in a LOT of granular control, but the "change" button wouldn't be too hard to implement at all. Same with the crossfade, I'm not sure why I didn't add that in at the start. I GUESS you could make the argument that the glitchy loop clicks are part of the ＡＥＳＴＨＥＴＩＣ, but at the same time it wouldn't hurt to have that as a parameter that can be dialed in to taste.
I wasn't even aware that the program was accessing the mic. That's probably a quirk of the Max/MSP engine it runs in, I'll see if there's any way to disable it within the patch.
I'll have to do some thinking about the "normalize each loop" part. Normalizing the input audio itself shouldn't be too hard, but every loop in the program is just a randomly selected chunk of that single audio buffer. It might be worth putting a compressor at the end of the signal chain?
I totally agree that the buttons SHOULD be lit up when active, I just didn't know how to really do that in Max? I'll have to see if there's a way to make a button object behave like a "toggle" (i.e. an on/off switch) instead of a "bang" (a triggered pulse).
As for the higher sample rate, if the input audio's sample rate is higher Max SHOULD be able to just automatically deal with it. I think the output is 44.1kHz by default, so a lot of the "crunchy" artifacts you hear are just the result of playing a 44.1kHz input file at a slower sample rate. If the input audio has a higher sample rate than that, you SHOULD hear less artifacts when slowing it down. Then again, I know that a lot of audio people work at 48kHz, but again, if the input audio is still at 44.1kHz, making the output sample rate 48kHz isn't going to do anything but make the output file bigger than it needs to be.
It could be related to having multiple audio outputs/drivers? Vaporgene uses the Max runtime and maybe it's pointed itself at a different audio driver, like ASIO or something. I don't currently have much of a way to check right now as my Windows machine is currently out of commission, but see if going into system audio settings and making sure that the computer speakers are the default helps at all.
Oh man, I hadn't even considered making stuff for Renoise and Reaper. I should probably look into that, especially considering from what I've heard it's more "serious code" instead of a DSP sandbox. That might give me a leg up on what I want to ultimately do, making cross-DAW VST plugins...
Oof. Thanks for the heads up on that. I'm not sure whether there's much I can do myself except wait for Cycling to release a version of Max that's been debugged and then recompile. I did write this on 64-bit OSX, for whatever that's worth.
I've had the thought of a v2 in my head for a while, actually. Thanks for reminding me of that! Probably gonna throw in Max's crappy built-in reverb as well :)
EDIT: On that note, I've also thought about making a Max for Live version with automatable parameters...think people would go for that? I'm planning on throwing some other M4L devices up here eventually, so far I've got a modal synth/effect and a Eurorack-esque pitch and CC randomizer in the pipeline. Think people would go for those?
Sure, if you want to! The only caveats are I'd appreciate being credited for the app, and if you use existing copyrighted music in Vaporgene you MIGHT have to deal with some copyright law BS. Other than that, go crazy!
VAPORGENE software is a virtual composer of music. Every decision of the output is done by VAPORGENE. However, there is the possibility of adding user-defined constraints in the future. Thank you for your opinion.
