pepper

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: issue with OWL patch #2917

    pepper
    Participant

    Just checking in on this. Thoughts?

    in reply to: issue with OWL patch #2883

    pepper
    Participant

    Just tried out [slide 16 16] – doesn’t resolve the issue actually. In fact, what I’m hearing is that the glitches are more pronounced in gen~ itself, which is what I was trying to avoid. I’d like to do this without any glissando if possible.

    in reply to: issue with OWL patch #2882

    pepper
    Participant

    I should also mention that I’ve seen some other example code whereby the [mix] object was used instead of [+], but not sure that this would matter. Maybe it’s an idiosyncrasy with [history] that I need to take account for?

    in reply to: issue with OWL patch #2881

    pepper
    Participant

    OK, thanks guys!
    Martin, I uploaded the file for you to peruse. It seems like you’re both in agreement that a [slide] will help to alleviate those issues. I guess I’m still curious why the glitches don’t occur in the Max/MSP domain, but maybe it’s because the processing can happen quicker. I’ll try out the slide trick for sure.

    Let me know if you have any more thoughts!
    best,
    pepper

    in reply to: some questions #2877

    pepper
    Participant

    @Martin Klang – I uploaded a file that exemplifies the issue and linked to it in a separate thread. Thanks for any help!

    in reply to: some questions #2868

    pepper
    Participant

    Thanks Martin. Very helpful, and I have in fact read most of that.

    default:
    I did in fact see that post, but I suppose there’s a feature request in there: It would be nice to get some sort of visual feedback that this is in fact the default patch that is going to load when you turn the pedal on without any UI. Is this possible?

    push:
    From what I’m reading (or maybe not reading), the push button is not intended to be held in terms of using a loaded “owl patch” (which is less of a patch and more of a compiled executable DSP program). I feel like this is a bit of a design quagmire, since it’s simply a button. Is there a way to override the default behavior of the 3-second measurement that allows you to scan through patches? Buttons are useful and could be really interesting for the user of the code running on the owl! I wish there was more than one! 🙂

    • This reply was modified 6 months, 3 weeks ago by  pepper.
    • This reply was modified 6 months, 3 weeks ago by  pepper.
    in reply to: some questions #2865

    pepper
    Participant

    I should mention that I think I also have a patch that seems to either crash the owl, or that the owl doesn’t like. Somehow, it always ends up rejecting the patch from loading, and either refuses to load it, or loads it for a while, then it seems to crash and default to another patch. Let me know if you need more info on this; I could submit it as a bug report or maybe there’s something silly I’m doing. Thanks!

    • This reply was modified 6 months, 3 weeks ago by  pepper.
Viewing 7 posts - 1 through 7 (of 7 total)

Latest News

Links

Follow us on Twitter