13 ms·

Just out of curiosity, and without judgement, how much ai was involved in building this (ie was it vibed)? I'm trying to get a better idea of the kind of stuff

Just out of curiosity, and without judgement, how much ai was involved in building this (ie was it vibed)? I'm trying to get a better idea of the kind of stuff people are making.

oceanwaves 5mo ago
A -ton- No hesitation to enthusiastically share that it was actually a parallel goal to see just how deeply I could go while keeping it stable, performant, and extensible for the long term. I ended up building a lot of ancillary agent infrastructure to push the determinism in all the fanned out work slices, too. https://thinkwright.github.io/threadmark/ https://thinkwright.github.io/threadmark/ Also: https://brume.aftertone.co/develop.html#agents https://brume.aftertone.co/develop.html#agents
- rigonkulous 5mo ago
  Did you give any thought to using JUCE as a general framework? This way you could add more synths very easily .. (Apologies if you already do, haven't looked for sources yet..)
  - oceanwaves 5mo ago
    I do distribute VST/AU plugins that are built with JUCE, but this is an application that runs on the Raspberry Pi platform.
    - rigonkulous 5mo ago
      JUCE runs great on Raspberry Pi.
      - oceanwaves 5mo ago
        Even in my plugins, I don't actually use JUCE DSP primitives. It's mostly a product shell and distribution framework, two things I have no need for in this codebase.
        rigonkulous 5mo ago
        I understand .. but its not 'mostly a product shell' and distribution framework, there are a lot of things JUCE brings to the table that might've been useful in this context, such as being able to host plugins and adjudicate resources (shared memory primitives, extremely easy parameter setup and management across DSP and MIDI frames, easy integration of common codebases into both DAW and standalone versions, etc.) that are generally good for DSP .. you're not obliged to use JUCE's DSP incidentally, I have my own synth project based on JUCE with both ARM and x86 SIMD implemented side-by-side .. JUCE' primary value is as a runtime environment, which I guess you are more interested in setting up, yourself, and I get that, so yeah ..
  - deleted 5mo ago
    [deleted]
- deleted 5mo ago
  [deleted]

Just out of curiosity, and without judgement, how much ai was involved in building this (ie was it vibed)? I'm trying to get a better idea of the kind of stuff people are making.

oceanwaves 5mo ago

A -ton- No hesitation to enthusiastically share that it was actually a parallel goal to see just how deeply I could go while keeping it stable, performant, and extensible for the long term. I ended up building a lot of ancillary agent infrastructure to push the determinism in all the fanned out work slices, too. https://thinkwright.github.io/threadmark/ https://thinkwright.github.io/threadmark/ Also: https://brume.aftertone.co/develop.html#agents https://brume.aftertone.co/develop.html#agents

rigonkulous 5mo ago
Did you give any thought to using JUCE as a general framework? This way you could add more synths very easily .. (Apologies if you already do, haven't looked for sources yet..)
- oceanwaves 5mo ago
  I do distribute VST/AU plugins that are built with JUCE, but this is an application that runs on the Raspberry Pi platform.
  - rigonkulous 5mo ago
    JUCE runs great on Raspberry Pi.
    - oceanwaves 5mo ago
      Even in my plugins, I don't actually use JUCE DSP primitives. It's mostly a product shell and distribution framework, two things I have no need for in this codebase.
      - rigonkulous 5mo ago
        I understand .. but its not 'mostly a product shell' and distribution framework, there are a lot of things JUCE brings to the table that might've been useful in this context, such as being able to host plugins and adjudicate resources (shared memory primitives, extremely easy parameter setup and management across DSP and MIDI frames, easy integration of common codebases into both DAW and standalone versions, etc.) that are generally good for DSP .. you're not obliged to use JUCE's DSP incidentally, I have my own synth project based on JUCE with both ARM and x86 SIMD implemented side-by-side .. JUCE' primary value is as a runtime environment, which I guess you are more interested in setting up, yourself, and I get that, so yeah ..
- deleted 5mo ago
  [deleted]
deleted 5mo ago
[deleted]