SWAP - Dj/audio patch with cool features for contributions &/or advice
Apr 06 2016 | 11:10 am
The DJ/audio patch that I have created represents months of work (I'm still learning Max!) and contains a lot of features; these are listed below. The patch has been created for my uni dissertation project - which is looking at open-source materials/community vs high-price products. The patch is fully functioning though I still have to iron out some of the finer details now I am able to play with it properly. I will post a video link shortly showing how to use the patch and what it can do :) I want to give this to the community as an open-source patch but I would like to ask the following so that I can show that this project is truly open-source;
* - There are sub-patches created for send and return audio effects and would like to ask for some simple effects that can be used,
* - If you make any changes, please post the patch on this page, highlighting what you have done.
Before I talk about the features I would like to say that I am also working on creating a hardware interface using an Arduino Uno, 2 MuxShields and a completely hacked version of Firmata to achieve the task of getting all 92 pins to work!! The layout of this patch is to make hardware routing a simpler and tidier task.
Functions Of The Patch
Two stereo channels each with pre-gain, 3 EQ's and Cuts, pan and volume
A display showing the movement of the waveform as the track plays, drag files onto displays to load them and select areas of tracks
Loop player that allows for cropping samples.
Copy audio from the audio channels to and between loops,
Loop player with option to split an audio file in up to 16 segments that can be re-arranged, muted or reversed (Left & Right channels are independent!)
Assign Loops and Channels to either side of the cross-fader
Save audio files
Stream audio files (yet to fully implant this feature though it is in the patch)
I would appreciate anything that anyone wants to contribute to this patch including any advice. If any one has any questions about this then please post them on this page and I will happily answer anything.
Many thanks
- Apr 06 2016 | 12:08 pmI'm getting the following errors when trying to open from clipboard.newobj: oggtx~: No such object "$" variable out of range (1) "$" variable out of range (1) "$" variable out of range (1) "$" variable out of range (1) +: doesn't understand "signal" +: doesn't understand "signal"using max 7.2 WIN7 (64bit)I would be interested in testing out the patch, and seeing how you managed it.
- Apr 06 2016 | 1:33 pmI created this patch on Max 7.2 in OS X, El Crapitan!. It should work on Win as there aren't any system specific objects in the patch (I think).I get the same messages in the console that you've pointed out but the patch works fine. I'm not sure where the error is coming from but finding it is something on the 'to-do list'.The 'newobj: oggtx~: No such object' message relates to an object, written by Tom Zicarelli, for streaming audio from Max. The object is available at: http://reactivemusic.net/?p=17504Are you having problems opening the patch?
- May 02 2016 | 9:40 amBROKEN OBJECT ERROR-- FIXED! The original patch failed to perform properly because some of the objects became broken. This was either because they were in a sub-patch or due to creating the patch using Max versions from 7.0 to 7.2? I spent a lot of time trying to work this out as the broken objects didn't produce a console message and the objects used to replace them were IDENTICAL!!Anyway, here is the patch again and I'll post the link to the blog I'm making to document the development of the patch, underneath. It starts of with introductions and some stuff about the hardware but I soon realised that I should dedicate it purely to this patch to make life simpler.@ Hamildad, the '$ out of range (1)' error was because I had created a [peek~ $1] object so that I could assign any [buffer~] name to it. The [peek~] object would still work fine but the "$1' was wrong syntax. To fix this, I used [peek~ $s] instead. To find the source of these errors, I discovered that clicking on certain error messages in the console would cause the erroneous object to turn yellow, momentarily (depending on what the error message was) Don't know if this is useful for you?If anyone has any comments or questions about the patch/project then please ask, only too happy to help :)Link to the blog about the patch development: https://wordpress.com/read/feeds/43669072/posts/928203661
