the big screen comes into its own for granular, and having it as a 'virtual modular' means I can modulate it really nicely.įunny enough last night, I was playing with the SSP granular using an LFO to scan a live input source. The SSP has a good granular module on it. Yeah, granular has been popular for a while now.īeads is kind of different, as its more focused on live granular. I already have too many players to justify another, but if I had the spare cash, and even harder to get, spare HP, I would get the ADDAC one. There is a great program on the Disting that I wish other players would adopt, it is a cross fade looper that automatically overlaps and fades the beginning/end of the loop to make them seamless - VERY useful for background beds and environmental stuff. I still have an unmounted Nebulae1 I try to sell ever so often, and a pair of Disting Mk4's which will loop waves too. I keep the VCO action in my NordG2 and computer where they stay in pitch and are easily polyphonic! I currently have two Nebulae2, two 4ms STS, a Tesseract Nutella, and a old ADDAC110 (my first wave player). My current modular setup is all WAV players/granular and no VCOs at all except LFOs. Yeah, for sure there is lots to choose from. all have their strengths, and plenty to explore with them all (imho) 'today, we are announcing the Nebulae 3'Īnyway lots of options in this space.
but Id think QuBit have enough Ideas for Daisy for that not be a priority. there is nothing stopping Qubit using rPI for another product, and they could use the newer CM3/4, which would be a pretty slick build. (but 'names' are marketing, so who knows if they'd keep the Nebulae name, or use something new?!) thats not to say better/worst, just different. similar to what is being done by NE Versio. I think it's more likely, if qubit were to build a 'Neb 3', it'll be a bit different, basically a granular built on Daisy.Īnd its 'openness' would be thru alternative firmwares. (this is a bit of over-generalisation, but I think the case in this instance)
#Beads new waveplayer full#
and that is exactly what Daisy is, albeit it, using a different approach.ĭifficult, its not a full 'computer' like the rPI within Neb2, so couldn't run csound (or similar) in the same way (needs pre-compiled code). or put another way, they developed Daisy to satisfy their DSP requirements, rather than use rPIs.Īlso, Neb 2 was touted (albeit, not very loudly) as an 'open platform'. So I think Qubit will use Daisy for all their future products (for at least foreseeable future) Well, Qubit and the Daisy Platform are 'connected' , Personally, I do NOT think there will ever be a neb 3. If ( myPort.Are we anywhere near a Nebulae V3? Was thinking about pulling the trigger but will hang off if an updated module is imminent. we use the Glide object because it smooths the input. MyPort = new Serial(this, portName, 9600)
#Beads new waveplayer serial#
Serial myPort // Create object from Serial class I think I need to adjust the multipliers of the values in order to perceive the differences of sound in a more clear way. To do that I use the serialRead example in Processing library, but I wouldn’t have been able put the pieces together to work without the help of Cagri. For my program I will need to change the input from the mouse to the serial port and obtain the value of the light sensor. This program changes the output sound depending on the position (x,y) of the mouse. I make all of the tutorial examples and I use Lesson 10 Interaction program as the base for mine.
#Beads new waveplayer download#
By looking at last year’s work I find Matt Keeter multi touch synth wich I find beautiful, so I decide to try and transform the light data into sound.įor that I visit The Beads Project site and download their library. But then I try processing and I start to think of different possible interfaces. My first idea is to start by animating the eyes of a face in scratch to open or close them depending on the amount of light. I want to make an interface for the light sensor board.
Links to the different platforms can be found in the class home. I also keep trying to understand C in a deeper way. I download and play around with Python, Arduino, Processing, Scratch. For this week assignment: write an application that interfaces with an input&/or outputdevice I start by taking a look at the different programming methods and tools that are available.
0 kommentar(er)
