• RT-Chris

    Thanks Mike, really great tutorial, very clear and easy to follow. Never knew about lop~ to help with clicking on line~ ramps starting at 1! I had been making elaborate asdr's trying very short attacks, but it was just never quite sharp enough for percussive hits... also seeding random - never had a clue what that really was...

    Hope there's more in the future!

    posted in tutorials read more
  • RT-Chris

    Just released some tracks that process some Ace of Base songs using Bonk and Fiddle https://ruintheory.bandcamp.com/album/the-sign

    posted in output~ read more
  • RT-Chris

    @ingox Yes! Took me a little while and some confusing cross talk but I realised after some debugging that in each abstraction I needed to prepend with an additional selector, and figured Symbols were better for debugging purposes too.

    And you're there ahead of me on the text too - I was going to mention the input accumulates rather than overwrites (which although maybe unintentional acts as a kind of save history), but did wonder if that was going to cause some erratic behaviour sending multiple sets of information. Thanks very much (again!) for your update, I would have been a while tying to figure out how to fix that :)

    posted in technical issues read more
  • RT-Chris

    @ingox Thanks, these are really really great! Bit busy over the weekend, but trying to unpack this now. Think I misunderstood the "save in main dir" file as a centralised form, so apologies for that. The second most recent file "save.zip" that actually does this is really great, thank you. It's very clear and so much easier to implement than what I was trying to make work.

    posted in technical issues read more
  • RT-Chris

    @ingox Thank you for building these (in the getdir format too!), it's honestly saved me so many frustrated hours clambering around and slowly debugging my way in the dark...

    Totally agree about the centralised saving. I had wanted abstractions to have multiple preset states, but that can be achieved by multiple centralised saves too, just don't change everything else in the patch ;)

    Sorry to ask as you've been more than helpful enough already, but just have a couple of questions about the centralised patch you've built as I'm still trying to understand it (I think I'm still on a steeper part of the PD learning curve than I had thought/hoped!)...

    To have a series of numbered saves, should I adapt the [append /array] to something with variables [append/array$2-name], or should that be in the concat function using [makefilename]? (I also was curious what the %g is in the makefilename, as I can't find any documentation of it).

    I'm amazed the array saves automatically as a text file without declaring .txt. Following form this, am I right in assuming to read the series of saves I set up the same function and just replace write with read?

    And finally (sorry!), as I understand the [const 0< [const 1< are examples of different arrays that are consolidated into the single $0-buffer. As there will be multiple arrays. is the order in which they are saved important? or is this where routing is a useful option (think you mentioned it before somewhere, maybe an earlier post)?

    Thank you so much again, you've been really extraordinarily helpful!

    posted in technical issues read more
  • RT-Chris

    @ingox wow, thank you for all of this. Never anticipated how complicated saving might get, but once I study this a while I'm sure I can get a handle as to how it works. Is a lot of this stuff just not in tutorials / guides out there? Seems like there's a big gap once you get past most of the basics and toward things like this, the forum is the only place I can get help. Anyway, many thanks again!

    posted in technical issues read more
  • RT-Chris

    Thanks, that's really helpful to see how that works I never would have figured that out. Looks like it's converting it to a string so PD can read the format. I remember reading spaces were an issue.

    posted in technical issues read more
  • RT-Chris

    @ingox For sure, think I've been slowly trying to get things working in small increments, and not looking at the bigger picture - that's good advice about centralising the saving in the parent patch.

    Still seem to be struggling to save in a absolute file format. Have managed to establish the absolute path as a symbol using [getdir], but when I pass it through [write $1< into [text define] it fails. I assumed it was to do with spacing, but I tried a spaceless directory/path and that doesn't seem to work either. Might have to go backto the drawing board with this one...:sweat:

    posted in technical issues read more
  • RT-Chris

    Just found [ggee/getdir], this does exactly what I want! :sparkles:

    posted in technical issues read more
  • RT-Chris

    Thanks as always @ingox , unfortunately it looks like the latest Purr Data release doesn't have the [pdcontrol] object yet for some reason...:disappointed:
    There's no other way of retrieving it via an external I guess, might just have to wait for this to make it's way into the next bigger lork/fork :pray:

    Thanks for the alternative suggestion also. I suspected it would make it a bit messier, and liked how with this way abstractions would be kind of self-contained and just work, but that might have to be the way this goes for now...

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!