Device Details
Device Overview
| Name/Version: | Spacer 1.1 |  |
| Author: | iorobertob | |
| Description: | Spatialization ( Spatialisation ) supports 8 speakers. This Device creates spatial sound by calculating delays and gains for a multichannel system. This Device will take the sound from the INPUT and 'move' it across the room where it is used. "Locating it somewhere" in the space. It does so by changing the gain and delay of the signal sent to the channels.It uses an up to 8 speakers. The YELLOW circle indicates where the sound position in the room. For the sound to work, set the dimensions of the listening room and move the NUMBERED circles to match the position of the speakers in your room. The exponent 'q' is used to alter the effect of distance in the intensity decay of the sound, influencing the gain 'g' and time delay between speakers. It will work by sending a delayed signal to another track. This track should be enabled to receive the signal, by using a SpacerReceive maxforlive device (included in the zip file), and setting the output to the desired speaker on the DAW. i.e. to use 6 speakers, you would use 6 [return] tracks with a SpacerReceive object in each of them, specifying which channel it will receive, and set to output to any channel of a soundcard. In the Spacer device, you will enable the speakers you want and their position. The devices uses plusend~ and plugreceive~. Although it is supposed to not be supported and I read quite a few complaints about its behavior, it has been tested to work properly with up to 9 instances of Spacer and 8 channels setup. The reason to use this objects and not the LOM to modify the send's is that I wanted to have delay control, and the track delay in Live is not accessible with the LOM, so this is one solution that I implemented. Also, the device has OSC over WiFi capability to control Input Gain, Decay and the position of the Source with an XY pad. This has been tested with Android apps that handle OSC messages. It also includes the possibility to automate the movement of the sound source by using Lissajous curves or patterns. Please use and abuse to improve and get in touch with me! Update 1.1 - Fixed typo in send D1 https://iobridger.wordpress.com/ roberto@iopatterns.com |
Device Details
| Downloads: | 1691 |
| Tags | effect, utility, other, hardware, dj, beta |
| Live Version Used: | 9.1.1 |
| Max Version Used: | 7.2.4 |
| Date Added: | Sep 11 2016 08:03:36 |
| Date Last Updated: | Sep 11 2016 16:39:12 |
| Average Rating | -n/a- |
| Rate this device: | (must be logged in to rate devices login) |
| Device Type: | audio_device |
| URL (optional): | https://iobridger.wordpress.com/2016/09/11/spatialization-maxforlive/ |
| License (more info): | None |
Device Files
| Device File: | Spacer.zip |
Comments
| send~ and receive~ are supported but add an unpredicatable delay which, in the case of spatialisation, is really a problem. Did you test your device alongside a counterpart using max only for example ? |
Posted on September 12 2016 by madlab (report) |
| Seems great, looking forward to try it ! I've been struggling with the "circlepan" device because it doesn't work very well when there's something like more than 4 devices in the project, does this one works if I put it in, let's say, 12 tracks ? |
| @madlab Indeed, they are not recommended to use, but this was the one solution that could work, being that I am adding delay to each channel, and the LOM does not support modifying the delay in each channel. I did not do such test, but did try it live with 6 channels and around 12 instance of it, it worked just fine. @Hetan - As mentioned before, I created something like 12 instances of this device, and 6 channels output live with no problems ;) |
Posted on November 01 2016 by iorobertob (report) |
| Really useful, well designed plug-in thanks for the work on this! I'm using on a multichannel installation project and it's really helped. Would be great to have parameters labelled up so you can automate within Ableton though! Right now I'm using the Lissajous movement to see which parameters are the right ones to use but it's still total guesswork unless I'm missing something. They just appear as "live.numberbox[x]"which isn't massively useful if you're trying to do a specific type of movement. Would be a great addition to add this in for easier integration into pretty much any scenario. Otherwise a much needed patch! Thanks |
Login to comment on this device.
[ browse device library ]