Hey @cyberik it seems like there is a problem with using the tidal looper in combination with ~dirt.doNotReadYet_(true). When you disable this (set it to false), then the looper works like expected.
@julian could you please help us out here? This is how I basically add a newly written buffer (after it is initially allocated)
I got the same Primitive '_SFOpenRead' failed error. I would really appreciate to get a hint how I can make this works with SuperDirt running with the doNotReadYet flag. Many thanks in advance!
Thomas, when you write "You can change the default looper mode by changing the variable pLevel", what are the different values and meaning of pLevel. And I think that rLevel is the recording level.
recLevel: Value to multiply by input before mixing with existing data.
preLevel: Value to multiply to existing data in buffer before mixing with input.
So the preLevel is just useful in overdub mode because it affects the gain of the existing audio in a buffer and is useful for mixing the new audio to this existing buffer.
hey @mrreason , just recently installed the tidal-looper quark in sc and when running the basic tidal code in the readme, i don't hear any sound when playing the "loop" sample after recording with the "looper" sample.
What I've done in SC to init tidal-looper is simply the line
// Initialize the TidalLooper
~looper = TidalLooper(~dirt);
I also set my input device to the default mic on my macbook ( any way to confirm that sc is actually using that as input? )
The output i see in the sc console when running the init is
---- initialize TidalLooper ----
loading synthdefs in /Users/.../tidal-looper/classes/../synths/standard.scd
function olooper was successfully loaded.
function looper was successfully loaded.
function rlooper was successfully loaded.
function freeLoops was successfully loaded.
have not seen any errors when executing the code in my ide. Wondering if I can get some help in debugging this? Thanks!!
Hey @bbquan and thanks for trying out the tidal-looper quark. It looks like that the tidal-looper is installed correctly. It would be helpful to see how your Tidal code looks like. When you have problems with the usage you should look at this thread:
But to your question how to debug the audio input:
Sure - there is a good chance that his thread will help you too:
If some of these answers helped you, I would be happy if you let me know what was missing in the README of the tidal-looper repository.
Haven't checked out the tidal looper, but is it possible to save slices from splice/slice operations? What i would like to have would be the ability to save out the slices into a directory. Then i could use these as source for patterns like n" 0 3 4 1 2" #s"folder1 folder2" etc. And further, it would be fun to be able to do this in a kind of feedback loop, so i could chop up samples, replay them back and rechop them back into the same directory.
[...] but is it possible to save slices from splice/slice operations?
TL;DR your use case is one of the many motivations (or reasons) why I created this looper
Kinda. There is no direct connection to these TidalCycles functions. If you route your output signals to some virtual input busses, then you can loop everything which comes from TidalCycles. You can slice your audio result with the looper, record it, play it back, slice it again and so on. You can specify different input busses and you can save different results under different names. But you could replace the buffers on the same names too.
ahhh... that was exactly the problem. when i executed s.options.inDevice i got nil. putting in those two lines into sc finally did the trick. also looper works how I would expect now. thanks a bunch!
Yes but it's the way the slice function cuts up the samples make it a lot easier to generate single hits. If it's done at the looper level, the looper has to figure out where to trim the samples. Haven't looked at superdirt to see if it can do that.
Thank you for the looper! I'm finding it wonderful for building up layers of sound with olooper, but I'm having trouble figuring out how to get rlooper working with qtrigger, did the essential functionality of that change since the posts in this thread were made? You say to use it "to start the recording when the next loop starts", but when I use it, e.g.
once $ qtrigger $ s "rlooper"
d1 $ s "loop"
it starts recording immediately after I run the code, records for a full cycle, then starts playback of the recording at the beginning of the next cycle. So if I trigger the code halfway through the cycle and wait until the beginning of the next cycle to start playing a one-cycle melody, my melody ends up starting the next cycle half a cycle late, and gets cut off half a cycle short.
Obviously qtrigger has changed at some point, since I can tell it no longer accepts arguments, but I can't seem to find any documentation or discussions about the change.
(P.S. any chance you know a good way to increase input gain to supercollider? my guitar is coming into my interface pretty hot but I need to really pump the gain in Tidal to hear anything)
