Sound not being produced

oof. i'm sorry. this kind of goes beyond my level of experience to be honest. maybe someone else can be more helpful.

No problem, I really appreciate the effort.

Hi @sachin_lyer,
Well this is a new one on me..

Thanks for detailing all the steps you've taken. So supercollider sound works, tidal->superdirt communication is fine.. I'm not yet sure what else to suggest..

So everything works, except there is latency of around an hour?? Do you think it could be exactly an hour?

In tidal (in atom), what does say if you run tidal_version ?

Hello @yaxu,

I am currently running 1.4.4
t>"1.4.4"

I will try my best to time it a couple times tonight, but I'm not sure how accurate I will be (the last time I timed it, it was 35 min, and I'm pretty sure this most recent time, it was over an hour).

If nothing else works, I might try to figure out how to reset the audio drivers on my computer. Also, I think the missing link might be between Supercollider and the sample libraries. Is there any way to test playing dirt samples from Supercollider?

Also must add, at risk of being a little bit cringy, you're super duper awesome and I really love your work. You're the definition of a cool person. Live coding is one of the big reasons I got into CS.

Hm, have you changed your BootTidal.hs at all? Adding a large value for oLatency could cause this, for example..

Otherwise, 1.4.4 is a little old, you could try updating with cabal v1-update tidal or cabal update tidal --lib

(and thanks!)

OMG, we got sound, yay. I reset all my cabal packages and this time specifically install 1.6.1. For some reason when I display the version in atom it is still 1.4.4, but for the moment I'm not going to question it.

I think when I was updating tidal earlier, I had unknowingly entered a smaller version of cabal hell, where it was defaulting to tidal 1.4.4 because that's what the packages supported (or I'm not understanding anything), so I was not updating it correctly.

Either way, thanks so much for all the help.

That's really good news!

But if it displays 1.4.4, then it very probably still is. Cabal in general is not working well at the moment. A reliable fix is to remove all the packages by hand - on Mac OS and Linux you can do this by removing the hidden .cabal and .ghc folders from your home folder. Then install again using the 'old style' cabal commands which work much better than the new ones. You can do this with cabal v1-update then cabal v1-install tidal

So in brief I'm not sure why it's working now but wasn't before !

So....the problem is back.

The thing that I had done before was clear the .cabal and .ghc folders, but I did
cabal install tidal --lib, and that for some reason gave me 1.4.4. Then, when I updated it to 1.6.1 using the v1-install tidal method (verification through atom and tidal_version), I think it is having the same one hour(ish) latency.

I also tried playing the Dirt Sample audio files through Supercollider itself
b = Buffer.read(s, "Users/sachiniyer/Library/Application Support/Supercollider/downloaded-quarks/Dirt-Samples/808/CB.WAV"); a = { (PlayBuf.ar(1, b, rate: 440 * 1024/44100, loop: 1) * 0.1).dup }.play; a.free();
(mostly from the supercollider docs), and that worked well.

The tidal messages are still being set (verification again through trying to send a sound it does not understand). I also am not sure whether sound is being sent after an hour or so. I assume that it is the case (the one time I tried it, it was not playing after an hour and a half).

Supercollider/scsynth is using about 1 gig of memory. I have not changed anything in my BootTidal.hs. Messages are still able to be sent through both emacs and atom. Sample rates are still synced (verification through the booting of Supercollider and also Audio/Midi Setup). Supercollider audio works as expected I think (testing with some basic synths and modulation). Quarks are all updated. I tried SuperDirt.resetEverything, but for some reason it was not understood by SuperDirt (here is that output). Other routing of audio in my computer is working, not that it should matter too much I think (verification through soundflower).

Some things I think I could also do:

  1. Maybe delete and reinstall all quarks (I don't have much installed, just FoxDot, Jack, ddwChucklib stuff, and I think a couple other small things, but here is the full output from Supercollider)
  2. Leave my computer running tomorrow from morning to night and see if sound is produced (I have to do weekends, because school).
  3. Maybe update Supercollider (I'm running a fairly recent version - 3.10.2)
  4. Figure out how Mac audio drivers work, and see if there is anything that I can do there
  5. Downgrade to 1.4.4 and maybe the Live Coding fairies decide to be nice to me
  6. Figure out how to wine Ableton and it's vsts, throw my Mac of a bridge, head the preachings of Richard Stallman, and finally make the switch to free non-proprietary software

Other than that I am thoroughly, truly thoroughly, confused. If there is anything else you would like to have me test or try, I would be more than happy to.

Hm, your superdirt version is a couple of versions behind, but still, should work fine.

Tidal 1.6.1 is good, that shouldn't be the source of the problem

Messages are getting from tidal to superdirt straight away, verified by sending a sample that doesn't exist and getting an error message, so that's fine.

SuperCollider is making sound fine..

It did work, now it doesn't, so it's somehow intermittent. I don't think upgrading tidal would have broken it.

You could try the examples here to test superdirt from within sclang:

Eg running this should make sound (straight away):

SuperDirt.default = ~dirt;

(
(type:\dirt, orbit:0, s: \cr).play;
(type:\dirt, orbit:1, s: \cr, speed:2/5).play;
)

Otherwise, it's a really strange one.. SuperDirt and Tidal should be referencing the same clock, so I don't see how it could be out by an hour. If you have something on the supercollider that does changes the default tempoclock or something, that might cause it..

Yay, the SuperDirt stuff does not play. So that was most likely the source of the issue.

But as life is, good things don't last. So when I tried to update Supercollider, it no longer responds (and neither does 10.1.4, or the other versions I tried).

I'm going to factory reset my computer (I've had some other problems with sound cards being unstable and vsts not working correctly), and I'm fairly sure this should solve the problem. If not, I'll be back.

Ok all I can suggest is play soothing music and light some candles while it reinstalls

Yup,

Just finished setting up everything today (and it all seems to work - fingers crossed). I'm pretty sure the Chet Baker and imaginary candles put me in the right headspace.

I'm running the latest version of supercollider (3.11.1), and tidal 1.4.4. It's working now, and updating tidal shouldn't change anything, but I'll cross that bridge when I come to it.

Thanks for all the help. Maybe one day I'll figure out exactly what was wrong.

That's great! I'm just confused about why you're ending up with version 1.4.4 of tidal. The Mac install process should leave you with the latest version 1.6.1.

The cabal install tidal --lib gives me 1.4.4. I am not sure why this is the case. I have had success getting 1.6.1 by doing v1-install tidal. Updating has also not given me 1.6.1. The only reliable way I have found to get 1.6.1 is to do a v1-install tidal (with clearing the .cabal and .ghc folders).

Thanks. I think I'll update all the install docs to use v1-install. v2 just isn't working.

Hi!
Idk if this might be something related but had some of the same errors out of sc

FAILURE IN SERVER /n_run Node 1006 not found
FAILURE IN SERVER /n_set Node 1006 not found
FAILURE IN SERVER /n_set Node 1006 not found
FAILURE IN SERVER /n_run Node 1005 not found
FAILURE IN SERVER /n_set Node 1005 not found
FAILURE IN SERVER /n_run Node 1003 not found
FAILURE IN SERVER /n_set Node 1003 not found
FAILURE IN SERVER /n_run Node 1002 not found
FAILURE IN SERVER /n_set Node 1002 not found
no synth or sample named 'tmp' could be found.
module 'sound': instrument not found: tmp

(Repeats ad infinitum)
Tidal is working, finally on my raspberry running patchbox and tidal 1.6.1
so sound is coming but these errors seem to add some latency, here and there. The mentioned 'tmp' sound folder has loaded successfully and is the only thing playing... Any ideas?

Do you get some errors/warnings on startup?

Only

WARNING: SynthDef superfm too big for sending. Retrying via synthdef file

Using emacs btw

Hello!

Have not been using Tidal in a while (sadly) but was trying to use it again but somehow somthing somewhere seems to go wrong constantly.

My issue is, that I am not able to generate sound.
So in my SuperCollider startup file everythong seems to be running as it should since it is able to detect all Dirt-Samples and tells me: SuperDirt: listening to Tidal on port 57120

In Atom following lines appear:

Choose ghc base path

no custom path configured
*** use ghcup default path**

Ghci command: /Users/michaelstark/.ghcup/bin/ghci Ghc-pkg command: /Users/michaelstark/.ghcup/bin/ghc-pkg

Start atom-tidalcycles plugin

Choose BootTidal.hs path

no custom path configured
not found in current directory
*** found in the tidal installation folder**

  • load BootTidal.hs from /Users/michaelstark/.cabal/share/x86_64-osx-ghc-8.10.7/tidal-1.7.10/BootTidal.hs

t> Loaded package environment from /Users/michaelstark/.ghc/x86_64-darwin-8.10.7/environments/default

t>

t> [TidalCycles version 1.7.10] Installed in /Users/michaelstark/.cabal/store/ghc-8.10.7/tdl-1.7.10-d78e273c/share Listening for external controls on 127.0.0.1:6010 Connected to SuperDirt.

t>

If i try to validate a line of code NOTHING happens...
If I try to validate a supposedly non - functioning line of code still nothing happens...

I'm on MacOs Monterey.

Does anybody have any thoughts on it?
Would really appreciate any help.

Thanks a million in advance.
Hope you r well!