@JulesV I haven't heard back from Christoph so I assume not...

@Christoph-Hart that's superb news! I'm so looking forward to bringing my AMS RMX16 clone to dolby atmos to have that gated reverb in my next album. It was a stupid idea to start making an album in atmos anyways but hey... why not

@David-Healey Oh good spotting, this might come from the fact that there's some internal path normalization but the wildcards do not use this.

BTW, I've added another feature to the asset manager last week: you can define a SharedWildcard which allows you to define files that might be shared across multiple of your assets - the asset installer will then skip them at installation / deinstallation (and verifies that they don't conflict when installing two assets that share files).

@David-Healey Yep, we talked about it here https://forum.hise.audio/topic/12926/question-about-ms-encode-decode-order-in-stereo-widener-example/3?_=1779473723375

@emmanuelbuccheri Loading a sample map always stops the audio engine.

To cross fade load the sample maps into two samplers at the start and crossfade between them. Or load the samples into multiple groups in the same sampler and use the group xfade feature.

I have an old video that shows some techniques here: https://youtu.be/0cn1l8231n4

@ScreamingWaves said in Module tree navigation tips:

does that mean that one can have multiple master chains?

There can be only one. But you can use containers to separate different flows. There's also send effects which occupy a separate chain.

@voxuer1 Yes, I have only tried as FX plugins, both on Mac and Windows, au & vst3.
It's working as it should

@voxuer1 nice glad it worked!

@David-Healey Hah that's that then :D. By a hair.

Yes it would have been a bespoke little thing just for my needs.

I'm not very hopeful about finding plugins. The Mac market in the 2000s was infamously sparse, especially in the sampler realm.

Still, it's a thought that didn't occur to me, thanks. I'll try and do a bit of research.

Cheers :-)

@MicheleBonventre What's different between the test plugin and the original project?

Also you might try with PluginVal to see if it gives any hints about the issue.

@Lindon well there was a problem in one of my includes, that neither HISE player nor HISE expansion projects was prepared to report.... so moving on for a bit...

It was caused by having different sample rates in 2 different samplers. I had to convert all to 41.1khz which is what I started my project at.

@David-Healey Hi,

I will simplify, make the chord analyzer separately

@ScreamingWaves https://docs.hise.audio/scripting/scripting-api/transporthandler/index.html

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

@Yannrog You need to script your own radio buttons for this. I posted a video on Patreon recently about it.

@David-Healey Thanks for the courses

@Christoph-Hart
Hi Christoph,

How can we create an official account (without the evaluation) ?

@ustk They're much better handled in JUCE 8 in my experience, I've built two shader based elements that work well in JUCE 8 when compiled as panels into a HISE build, I have had a lot of issues with GPU rendering though currently doing the work on CPU until I work that out. Annoyingly these depend on JUCE 8 functionality so neither works now I've had to downgrade to JUCE 6. Fingers crossed this is sorted soon!