@ulrik said in Optimal Midi Architecture:

So I set the TransportHandler to trigger the clock every 1/64T note (the lowest value available)
and based on that, I can make calculations for each note value for position and length etc.. using this function

Nice plugin ulrik

I'm likely aiming for a higher PPQ of 960, so not sure it's possible that way..

Chatbot stating: Running a JS loop 960 times per quarter note per sequencer lane will cause hell. And I think you're stating that 96 PPQ is the highest that can go?.

Supposedly the Hise MIDI Player has an internal PPQ resolution of 960 PPQ, handled by sample accurate C++ timing. That's what I need

The MIDI Player could work, but I don't see a way to use it without initially clogging up the plugin with 50 - 100+ MIDI Players, nor finding a way to set them to other MIDI Channels.

Info pointing toward a lot of work to get higher resolution timing without using the MIDI Player..

Stuck, but there must be a way in Hise.

@David-Healey said in Agentic coding workflows:

I can see cost being a massive restriction for using agents regularly.

Try Google's Antigravity with the Gemini 3 Flash model set to Fast.
It's near the quality of their Pro models but with significantly more free limits.

Claude Sonnet models have typically been the best I've experienced, but the gap is small now, even for Google's Gemini 3 Flash model, which people are actually preferring; just be prepared for it to once in a while randomly write 100 lines for a 5 line piece of code.

Claude's pricing is ridiculous.
I would be very hesitant to pay a subscription for any AI model when my input is training it, unless it happens to ultimately demonstrate consistent error free value.

I played with Hise for a month last year and quickly learned that my brain doesn't have the interest and time to learn everything about scripting and development needed to create the semi complex plugins I'd like to; so I tried using LLMs with moderate success..

The most immediate issue I found has already been described here - the LLMs would continue to make the same basic scripting mistakes, assuming more standard Javascript. It can be reduced to some degree by providing the agents with strict rules and contexts, but they still revert to making an unacceptable number of the same basic mistakes that you've clearly instructed them not to, even when stating specific instructions directly within the prompts.

That's where it's been most obviously unusable for me; if I'm spending half the time reiterating the same basic Hise scripting errors back to the LLM, that's too much time and tokens wasted to achieve anything substantial. It's mostly the frustration of it that kills the motivation to continue, otherwise it has great potential!

I really hope this can be overcome to make plugin development viable for people like myself, who have the interest, but not necessarily the time and programming experience to achieve what we'd like to without the help of LLM agents.

It would be great to see Hise not only survive, but to potential thrive with AI. Hise has more going for it, that if updated with effective LLM scripting capacity would likely be worth the Hise and Juce license fees for me, over other free options.

Whoever implements AI plugin development the most efficient and appealing way will pocket our money at the end of the day.

BTW you can use the 'Recompile On File Change' Hise option along with an external editors Auto Save option to seamlessly auto compile plugins/scripts at the time you change window focus from external editor to Hise.

@David-Healey

Rule #1

Dont trust anything AI

@Christoph-Hart said in Optimal Midi Architecture:

I'm living under a rock here. How wide is the DAW industry adoption of this? All of the hosts I'm using don't care at all about MIDI 2.0.

It's only just being rolled out across operating systems and will indeed take some time for DAW's to catch up, although predicting Bitwig will be all over it soon enough.

I guess for me it's always been a fantasy to have more control and resolution, particularly regarding per note automation, next level music... MPE has always been a limited workaround.

Internal synths could could make use of the upgrade

Oh look Bitwig are already in the game.... yas

Damn, the original issue isn't solved in project, I can't do another day on this lol.

@dannytaurus

@Bart Oof, I don't think the design-nerd side of my brain could accept that!

Thought that might be the case lol.. I'm a visual perfectionist too, but learning that asymmetry and contrasting elements are usually more interesting.

Your plugin looks great!.. because it has contrasting elements vertically, plus the ADSR and shape options break up the knobs.. Don't be afraid to make components different sizes and shapes :)

A GUI that i've always found appealing because of it's numerous contrasting components - Harmor - it's a visual treasure chest that's consistently fun to play with.

@dannytaurus

Thanks Danny. I'm wanting the docs as an added folder to the workspace in VS Code, so I don't have to jump out of the IDE every time to look something up. Also for searching keywords throughout the documentation. The Hise Docs search bar appears to only show functions containing the keyword.

@David-Healey

Awesome! Thanks for your input David!

Really appreciate your video tutorials also.. I would have likely never attempted plugin dev scripting otherwise, great work ;)

Hise for the WIN