Closed LukasJerabek closed 9 months ago
Also I have used this from tidal cycles documentation for startup.scd
/*
This is an example startup file. You can load it from your startup file
(to be found in Platform.userAppSupportDir +/+ "startup.scd")
*/
(
s.reboot { // server options are only updated on reboot
// configure the sound server: here you could add hardware specific options
// see http://doc.sccode.org/Classes/ServerOptions.html
s.options.numBuffers = 1024 * 256; // increase this if you need to load more samples
s.options.memSize = 8192 * 32; // increase this if you get "alloc failed" messages
s.options.numWireBufs = 64; // increase this if you get "exceeded number of interconnect buffers" messages
s.options.maxNodes = 1024 * 32; // increase this if you are getting drop outs and the message "too many nodes"
s.options.numOutputBusChannels = 2; // set this to your hardware output channel size, if necessary
s.options.numInputBusChannels = 2; // set this to your hardware output channel size, if necessary
// boot the server and start SuperDirt
s.waitForBoot {
~dirt = SuperDirt(2, s); // two output channels, increase if you want to pan across more channels
~dirt.loadSoundFiles; // load samples (path containing a wildcard can be passed in)
// for example: ~dirt.loadSoundFiles("/Users/myUserName/Dirt/samples/*");
// s.sync; // optionally: wait for samples to be read
~dirt.start(57120, 0 ! 12); // start listening on port 57120, create two busses each sending audio to channel 0
// optional, needed for convenient access from sclang:
(
~d1 = ~dirt.orbits[0]; ~d2 = ~dirt.orbits[1]; ~d3 = ~dirt.orbits[2];
~d4 = ~dirt.orbits[3]; ~d5 = ~dirt.orbits[4]; ~d6 = ~dirt.orbits[5];
~d7 = ~dirt.orbits[6]; ~d8 = ~dirt.orbits[7]; ~d9 = ~dirt.orbits[8];
~d10 = ~dirt.orbits[9]; ~d11 = ~dirt.orbits[10]; ~d12 = ~dirt.orbits[11];
);
};
s.latency = 0.3; // increase this if you get "late" messages
};
);
Hi @LukasJerabek - thanks for using the tool :)
Due to the possible software combinations/presets/options not to mention variation in hardware possibilities, this tool (by design) only looks after the installation of the software and not the configuration of audio pieces.
You will want to look at qjackctl
and use it to start JACK (if it's not already started, qjackctl
will tell you).
I'm going to close the issue (since this is out of scope of my tool) but feel free to ask for assistance on the https://club.tidalcycles.org forum, or Tidal discord
I think it is because of 23.10s pipewire. There may be some workarounds but seemed to complicated, so I made it work on windows.
I think it is because of 23.10s pipewire. There may be some workarounds but seemed to complicated, so I made it work on windows.
I use pipewire here on the 23.10 ubuntu studio release - it didn't add complication in terms of making supercollider work.
I will do some investigation on a vanilla ubuntu build though, and get back to you. This should be a relatively trivial solution
Well this is what I get when I run qjackctl, then I read somewhere it may be because of pipewire, found project that should solve that that I didnt understand at all and thats when I decided to just go with windows, because I didnt want to bother with sound libraries...
So I did a test with a vanilla 23.10 install onto hardware, installed git/ansible and ran my playbook - nothing else was required in terms of setup. I started supercollider and and editor, and tidal was fully functional.
I'm concerned that maybe by changing the supercollider startup there may be something wrong there that was the initial issue. Pipewire provides an API for all the jack supporting apps so they just work including qjackctl - although with pipewire there is not really any need to use qjackctl.
So provided no key changes are made to the audio beforehand, there is literally nothing to do except run the script, start supercollider and everything works for a vanilla 23.10 ubuntu
Interesting. Dunno what is the problem then because I did not make any changes to audio :/ but never mind I am ok with Windows instalation.
Hello I have run the ansible palybook with sudo ansible-playbook --connection=local -i localhost, tidal_vscode.play.yml
I can play samples in the list in vscode, but I cant run my code, there is just empty output, something like this:
My suspicion is on the
Waiting for SuperDirt (v.1.7.2 or higher)
Also because in supercollider everytime I run Superdirt.start I get:And here the suspicious part is
could not initialize audio.
Any idea what to do with that? I am using Ubuntu 23.10