It’s not quite as simple as that …
The nebulae has quite a few control messages being passed in, and some interaction with loading up samples that are all external to the csound patch.
Could be done but it’s not just a matter of running a csound patch :wink:

2 Likes

Has anyone been able to get Supercollider patches working on the Nebulae? The product description indicates this should be possible, but I can’t find the documentation for it anywhere.

True. could be a fun way to learn csound for sure. i recommend cabbage for hacking it up

Been experimenting a bunch and I have some questions if anyone has ideas…

  1. is it possible to record/overdub an external source onto a preloaded sample? That would be awesome…
  2. The granular is very choppy, like you can hear the loop. Is there a way to get a bit more of a smear sound effect for drones. By adding some modulation to density I have a work around but I wish the overlap would completely overlap the loop points.
    3.I’ve downloaded the Size05danish instrument, its awesome. Is there another spot to find user patches? I’ve read that the ones through Qu-Bits website are really spotty…and I can second that.

Thanks everyone

I’ve been fiddling trying to get this too. Trying to get something like the Morphagene Morph. I thought it was something in my sample.

OVERLAP should absolutely be able to get overlapping grains. In the standard firmware, it sets grain length as a percentage of the base grain generation period (i.e. % of duration set by DENSITY). The percentage ranges from very fast (e.g. 1% - so tons of dead time between the grain completing and the triggering of the next grain) to quite long (e.g. 600% - so 6 overlapping grains at a time).

If it still sounds “choppy” when overlap is set to a high amount of overlap, try adjusting the grain window to a softer window (BLEND control).

Also, typical granular synths normally generate grains from a fixed location, +/- some amount of variability, rather than constantly scrubbing through the file. To get this going, set Nebulae into FREEZE mode - use START to scrub through the file and choose your location to generate grains from. To add some variability to the location, use the secondary START control (e.g. press and hold SOURCE while turning START) to add some subtle random variation to the start position (release SOURCE to lock in the start position randomization amount). Use the same procedure to add some randomization to grain length via the secondary OVERLAP control. Now you should get a much more textural drone generated off of one location of your file. You will need to tune DENSITY and OVERLAP’s base values to taste depending on the variability/droney-ness of the source sample. Add some reverb to get it nice and smeary. Try scrubbing through your file with START to change the timbre of your drone.

15 Likes

this just made a lot of things click for ME, at least. thanks for the tips!

3 Likes

I just happened to notice @TheTechnobear has a new firmware out for Neb v2 which enables it to be used as a wi-fi access point. This allows for remote file management via a web file manager. Neat stuff.

6 Likes

Thank you for this tip. I have been bugging people with this questions since I got the device and everyone would always just come back and say, it does do that, but it never did it like I wanted it to. I appreciate the hints and workflow suggestions, this in combination with a little bit of Density randomization has gotten my smearing work to a new level :slight_smile:

3 Likes

My firmware (v2.2.1) now has support for supercollider :slight_smile:

using this you have access to both server and client side, and ive got a ‘live coding’ template (see desc on patchstorage)

I really do love Supercollider for live coding, generative stuff… so it great to have it on the Nebulae.

I hope to have a couple of SC patches running in next couple of days to give more in-depth examples of whats possible :slight_smile:

10 Likes

Really love my Nebulae, just got a new microphone for processing vocals through it in live performances.

Only just now I realised that it doesn’t process live input in realtime, you first have to save it to the buffer, before you can process the sound at all. Doh

Is there any way to modify the standard instrument to allow realtime processing? Or any other instruments for it, which can do realtime processing?

if you want to do live granular, you could load up the clouds instruments

you can create your own instruments for it - so opens the door for many different types of ‘processing’ for vocals and other instruments.

2 Likes

Ok cool. I’ll check out Clouds.

Not working now, so plenty of time to learn something new.

1 Like

Installed your new firmware, great work very easy to use.
I installed Clouds in the PD folder, and loaded it as per the manual, but it was unrepsonsive. Any suggestions why that might be?
Cheers

1 Like

its works here…

did you put the contents of the clds folder into pd? this is what you need to do…
nebulae does not support sub folders for patches. so all files need to go directly into the ~/pd

1 Like

I have put both the clds.pd and clds~.pd_linux directly in the pd folder.
Feel like I’m being a numpty and missing something obvious! :slight_smile:
Any suggestions for anything else to try?
Thanks

Does anyone know of any good tutorials showing how to install new instruments onto the Nebulae V2?

2 Likes

That looks right… @Comoving_Observer

If you have a signal into audio in, and blend fully ccw , do you not hear anything?
( don’t touch speed initially, you could accidentally put in an odd mode).

Note: as patches are alpha sorted - clds will be in slot1

Did you reboot? Is it showing 2 patches ( given you have a second one in there as well)

@photofractal if your using my firmware, just place pd patches into ~/Pd and csound patches into ~/instr … manual details how to ‘activate’ them.

Note: nebulae only reads what patches are available at startup, so you currently have to reboot it to see new patches.
( I’m going to change this so the browser allows a ‘refresh’)

Thanks for the advice! Figured it out, I think it was because I still 4 CV inputs patched from a previous mode, some might have had offsets on. Works totally great now!

1 Like

Cool - enjoy.
Yeah with clouds it’s quite easy to get into a state where it’s not making any sound… most common reason is density @ 12 o’clock , as you think it’s neutral - whereas it actually means don’t generate any grains (needs manual trig ! )

1 Like