As a workaround, you can use my FreeSound Quark in SC and set up a synth to play samples from there, I think. Sorry for the confusion!

I’m sorry that it crashed. Downloading stuff is asynchronous so always scary… A new version of dQ is on the way, you can save and load preset scenes etc, which helps a lot for live performances. Also dedicated DQSynthDef classes that is transparent like SynthDefs, you just memStore and go! But it will be around 1-2 months before I get to package it, too many troubles right now…

I actually have a SuperCollider backend for FreeSound, do you know about my FreeSound Quark? I’ve recently released a GUI frontend for it too, you may want to check these posts:

http://www.batuhanbozkurt.com/news/freesound-class-for-supercollider-released-as-a-quark
http://www.batuhanbozkurt.com/news/freesound-quark-update

You can adapt the class for any need, it can continuously download, and you can store them in buffers for sneaky listening etc… It’s not implemented directly inside the class but it is easy to make one that will fit your needs.

I’m gonna give a listen now. Best…

Unfortunately dq crashed when we created too many buffer synths. Searching through freesound randomly can be a slow process – time to release the python.

A super-collider back-end would be good. I’d list to listen to the samples before adding them to the mix (like a DJ’s headphones). Any suggestions on where to start? Hadron?

You obviously have to include sc_osc.h and sc_osc.cpp in your project. For now, objects for a Server, Synth and Buffer are included.

The classes were developed for dQ (but are kind of generic) so only server messages concerning dQ are included at this time, but it’s easy to expand by adding new methods by figuring out the appropriate messages from “Server Command Reference” help file distributed with SuperCollider.

—

You first need a representation of a server:

myServer = new scServer(“127.0.0.1″, 57110) //ip and port

To figure out how interaction with synths can be done, check out sAgent.cpp. Basically:

mySynth = new scSynth(synthName, myServer);

synthname is a string here and myServer is the server object we’ve created earlier. This creates a representation of a synth, but does not create it on scserver. When you want to create it:

mySynth->create();

When you want to get rid of it:

mySynth->free();

If you want to control a parameter:

mySynth->set(paramName, value);

paramName is a string and value is a float. You can find these methods defined in sc_osc.cpp. The usage is the same for other abstractions and their methods, you can just look them up from there. You can also add new commands easily (for example, according to Server Command Reference help in SuperCollider, to create a synth, you need to send “/s_new” osc message to server and it gets two arguments: synth name and node id. And the scSynth::create() definition in sc_osc.cpp does exactly that). If you want to add other commands, you can add them easily by changing the command and arguments. If you do so, please let me know so I can include it in a future release.

Feel free to ask if you have more questions.