• catkisser666

    Hey everybody,

    I'd like to get pure data working on my raspberry pi to run headless, open a patch, accept audio input, and send it on out to the worth.

    I have a sabrent usb audio device, It works fine if I open a gui and load pd within it. Upon loading the gui Pd takes the sound card, is happy, and a very simple patch of adc->dac puts the audio out.

    I can't get it working headless. I've followed every internet advice. I know this isn't the fault of pure data but of Linus Torvalds/the Linux community, but I'd like to plug in the raspberry pi, get it going headless on say, ring mod into some delay, and just go from there. But will this ever be possible? Please help.

    I wiped the microsd card today, installed raspberry stretch, and that's what it runs on now.

    Thank you.
    A dying soul.

    posted in technical issues read more
  • catkisser666

    Does Camomile have this kind of functionality? I haven't played around with it yet but I've been thinking about getting some of my patches working in it to integrate into Reaper. I assume that if you render a project in a DAW with camomile that it can calculate the output in non realtime. Otherwise it would be quite limited. But again, I haven't tried this yet; I'm just hoping to in the near future.

    posted in technical issues read more
  • catkisser666

    All of these fft based solutions are closely related to what a vocoder is, though. They'll likely sound artificial and robotic without careful tuning. There's no real general purpose solution to these kinds of questions, as far as I can tell.

    You might look at the I06.timbre.stamp.pd help file but try replacing the example sounds with piano and guitar samples and see what you get and go from there.

    posted in technical issues read more
  • catkisser666

    There's an object in the fftease library called dentist~ that lets you specify which partials to let through or block, which will let you do more radical editing of the spectrum of the guitar tone than an EQ. It won't get you to a piano sound but it might get you to something that's more plinky plonky out of the guitar.

    posted in technical issues read more
  • catkisser666

    There's a moog~ in ggee that sounds pretty nice to me

    posted in technical issues read more
  • catkisser666

    Okay here's another conundrum: the help file for threshold~ says that it triggers when it EXCEEDS the target value, which is why I have the .9999 nonsense in the adsr patch. Further testing suggests that it actually triggers when it HITS the target value. I'm attaching a small patch to demonstrate. Is this just an infelicity in the help file, or am I overlooking something?thresholdTester.pd

    It's much nicer to have it bang on the target value, as I can use it like a signal-based select, rather than having to specify a target value that is vanishingly close to the actual end value of the attack segment.

    posted in technical issues read more
  • catkisser666

    Thanks for all the suggestions about this. I'm going to keep plugging away and report back when I find the fix, though I'll probably ultimately take th8a's suggestion of using tables for the envelope segments so I can eliminate the hacky way I'm using threshold~.

    I've been building in lots of print and env~ objects to try to figure out where the exact problem is. I believe I've successfully determined that it's NOT the voice stealing or the threshold~ object. All the midi info seems to be getting routed to the right voices, and the decay segment seems to be playing correctly even in notes that get stuck on, which it's the purpose of the threshold~ object to trigger.

    For some reason the midi off control seems to be sent to the envelope, but it isn't registering it. I can fake another off event with messages and the envelope releases normally at that point. I've been playing around with a slightly more complex synth patch that uses the same envelope abstraction, which is actually a little more helpful because it has multiple oscillators for each voice, and they do NOT all seem to get stuck on at once. In fact, the base oscillator seems to be the only one that gets stuck on, whereas the 2 suboscillators do not, which suggest to me that I might have screwed up the construction of how the oscillator patch interacts with the envelope. But I'm still only closer to figuring it out; I haven't had much time to mess around with it lately.

    posted in technical issues read more
  • catkisser666

    What do you want to do with it? That'll probably affect how you end up designing it.

    You can get the audio either in through adc~ if it's external to your computer or readfs~ to play a file on the hard drive. Hook those up to env~ and you'll get the dB of the input. Do whatever kind of math you need to do on it to convert it into the range you want and then feed that into some kind of oscillator.. You could also just feed it into a mtof since the dB values will already overlap with a good chunk of possible midi note values.

    posted in technical issues read more
  • catkisser666

    Playin around, still pretty baffled. This behavior happens fairly infrequently, and is hard to reproduce on demand, but happens certainly enough that I'll encounter it a handful of times in any session of messing around with the synth. I wonder if maybe something external to Pure Data could be making it miss the midi note off event? The only thing I can see from looking at the adsr patch that would account for the behavior is not receiving the note off message to trigger the release, but I could be wrong. Sometimes it seems like it might happen more when the computer is under more strain, so maybe something with the midi to usb interface I use is responsible? Hard to quantify.

    Also willing to take advice on replacing the slightly hacky way I'm using threshold~ with something more correct. Though I don't think the threshold~ object is contributing to the problem itself.

    posted in technical issues read more
  • catkisser666

    Hi guys. I put together an adsr envelope abstraction a while ago to get the functionality I wanted where each segment of the envelope could have its own specified exponential curve. It generally works great, except that when I play glissandi in the synth patch I'm building one note appears to get stuck on every time if I play up to amount of polyphony. I assume there's something going on with the voice stealing, but I can't exactly see what or how I could fix it. Y'all have any advice? I'm attaching the whole synth patch in case it helps to look at it in context. The abstraction is adsr.pd which references expLine.pd to make the curves.

    Thanks for any help you can give with this!
    Little Ringy.zip

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!