#128

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
#129

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
#130

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?

#131

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
#132

Ok cool. I’ll check out Clouds.

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

1 Like
#133

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
#134

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
#135

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

pd
pd1739×940 74.1 KB

#136

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

2 Likes
#137

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’)

#138

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
#139

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
#140

Just one other question, the Speed knob is “mode”, how does that relate to Clouds parameters?
Cheers

#141

It gradually steps thru them fully ccw = granular ,
The leds don’t really mean anything as I spread the available modes over entire range - I probably should just associate them with octaves , and so led colours - but don’t think of it at the time, so it’s not :wink:

( given the wide range - you’ll be able to see which octave = which mode after a while)

1 Like
#142

Yes, I’m also a little confused about this so some simple advice would be valuable! :slight_smile:

#143

So do I just drag the clds.pd file directly onto the USB drive or do I first need to create a folder titled “~/Pd” and drag it into there. Haven’t found too much in the manual or on the internet explaining this initial step.

#144

Yes also the clds~.pd_linux

I think ~/pd is already on there.
also in my browser you can just click on the ‘pure data’ button this will take you to the same folder.

In fairness to qubit, I think most confusion arises from the fact there is no display, they just did it by ‘syncing’ the usb drive - but it’s really easy to get confused because you cannot see what’s going on.
I think the browser makes this much easier.

I’ve another idea, that when i get around to it, will help the mental model associated with patch selection via the ‘slots’

1 Like
#145

here’s a sampler/looper sound on sound looper svanya orginally shared with the fourm
adjusted for Qbit Nebule 2
press “freeze” twiddle knows
audioflow.pd (41.4 KB)

1 Like
#146

OK I put both files on the root directory of the USB stick along with 2 other .pd instruments and some .inst files too. All of the alternate instruments work accept the clouds. I put it in the first slot and I can see it is there but when I click it I get no sound at all.

I’m still a bit confused about why the instructions are to make a folder for pd files on the usb drive when all other instruments are working from the root level. Not sure what I’m missing here.

#147

have you installed my firmware?

the ‘factory’ firmware does not support pure data externals (e.g. ~clds.pd_linux) and so will not work.
so you’ll need to use my firmware if you want to use clds.

(also id recommend once you move to my firmware, you use the ‘browser’ functionality, as its much easier to see whats going on)

more details : https://www.muffwiggler.com/forum/viewtopic.php?f=16&t=226841&start=25