@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

The key switches are neither working when exporting to audio file, even if the plugin is open and in focus at time of export.. but this will likely fix itself when you patch it up.

Sounds nice, but stuck on Staccatissimo here

Groovi.wav

@David-Healey

Just having another tinker and FL Studio crashed..
Can't be sure it was Rhapsody.. but the project had been working fine for a good while before, then a few minutes after opening Rhapsody and playing some sequenced notes through it, FL Studio crashed.
I'll play some more to see if it happens again.

Oh, the key switches are not working when the plugin is minimized or closed.

Annnnndddddd-aaaaaaaahhhhhh, where's the filter bro!?
I've never been in to sampled sounds, but feeling a need for a filter.
Likely more so for bright brassy sounds, to both tame the high end and add more expression.
Maybe a single lowpass knob that can be automated in DAW.
Ignore this if already planned

Very nice David!

Really like the clean polished interface.

Briefly tested the VST with FL Studio on Windows, no issues.

A few tweaks maybe:
Was naturally trying to use the Dynamics | Speed | Amount knobs - not realizing they were disabled.. They could have more contrast between enabled / disabled states to be clearer.

The UI corner resize isn't nice when it jumps in big steps, and users may not be able to resize exactly as they want.. Fine step resize is superior imo, if no performance issues.

Great work

@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.

@David-Healey

I've completely uninstalled Rhapsody and the sample pack, then reinstalled new versions, also installed latest FL Studio beta.. unfortunately seeing the same crashes 10 seconds after unload.

The 10 second delay between unload and crash might be a clue, but sometimes it takes changing something in the plugin or DAW after unload to see the crash.

Key switches are working
They also working now when triggering sequenced key switch notes and melody notes @ same time.. before your fix the key switch notes had to be placed before the melody notes.

@David-Healey

Windows 11 25H2
Build 26200.8457
Intel i7-11800H 2.30GHz

FL beta from 2 months ago
I'll get the new beta and test it later today

It doesn't matter if new project or not, was consistently crashing with method stated.

@David-Healey said in Testers Needed for Rhapsody v3:

What are the steps to recreate the crash?

It was happening by simply unloading the pack / click unload button and accept.

Trying it now has inconsistent results..
Sometimes can't get the sample pack to reload at all after unload.

Try unload | reload.
Move some controls.
Toggle play stop.
Crashing randomly doing these now.

Unload seems like the culprit.
Haven't noticed crash without unloading first.
Doesn't necessarily have to be reloaded to get crashes.

@David-Healey said in Testers Needed for Rhapsody v3:

@Bart I've been down a little rabbit hole today with global cables, the articulation switching should work now

https://e.pcloud.link/publink/show?code=XZm4ycZWRIqN1pUCPmGxb4Vxktn7LJfhul7

Did you intend to link the sample pack again, or meant to be a patched app update?

Within 10 seconds of unloading the sample pack Rhapsody crashes FL Studio consistently.

Maybe place the library icon on the left side of the preset header, possibly with a gap.
That's where I'd expect to access it, yet I'm not familiar with sample based plugins.

@David-Healey

The key switches are neither working when exporting to audio file, even if the plugin is open and in focus at time of export.. but this will likely fix itself when you patch it up.

Sounds nice, but stuck on Staccatissimo here

Groovi.wav

@David-Healey said in Testers Needed for Rhapsody v3:

@Bart said in Testers Needed for Rhapsody v3:

Regarding the Dynamics knob, the Vibrato and Effects knobs - they're not working while in Performance state.

By not working do you mean the controls are disabled or that they are not having an effect on the sound?

Is this in the plugin/standalone or both?

Oh no wait, they are working.. they didn't seem to be sounding before, maybe it was related to the keyswitch issue somehow, or I just wasn't hearing them clearly.

Only testing with VST.

@David-Healey

Was assuming the other controls aren't meant to be working yet.. but then your first message here is stating the plugin is 'ready'.

Regarding the Dynamics knob, the Vibrato and Effects knobs - they're not working while in Performance state.

@David-Healey

Just having another tinker and FL Studio crashed..
Can't be sure it was Rhapsody.. but the project had been working fine for a good while before, then a few minutes after opening Rhapsody and playing some sequenced notes through it, FL Studio crashed.
I'll play some more to see if it happens again.

Oh, the key switches are not working when the plugin is minimized or closed.

Annnnndddddd-aaaaaaaahhhhhh, where's the filter bro!?
I've never been in to sampled sounds, but feeling a need for a filter.
Likely more so for bright brassy sounds, to both tame the high end and add more expression.
Maybe a single lowpass knob that can be automated in DAW.
Ignore this if already planned

Very nice David!

Really like the clean polished interface.

Briefly tested the VST with FL Studio on Windows, no issues.

A few tweaks maybe:
Was naturally trying to use the Dynamics | Speed | Amount knobs - not realizing they were disabled.. They could have more contrast between enabled / disabled states to be clearer.

The UI corner resize isn't nice when it jumps in big steps, and users may not be able to resize exactly as they want.. Fine step resize is superior imo, if no performance issues.

Great work

@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.