HISE Meet Up

[d.healey]

I think the docs search is something that might benefit from an AI system. Where you could tell the AI I want to do X and it would point you to the relevant documentation pages - and definitely not attempt to write any code for you.

[aaronventure]

@d-healey that, too. there are plenty of tools available for implementing this into your own website as well. It could get expensive: I don't know the exact pricing for similar services from AWS and the like.

You already can use the NVIDIA ChatRTX on Windows where you download an open source LLM your computer can handle, upload the documents that you want to talk about (HISE docs repo) and then just chat to it.

There's also https://anythingllm.com/ but I haven't tried it.

[d.healey]

Should we arrange a meet up for the end of this month? Christoph will be back then too. :)

[HISEnberg]

@d-healey Yes would love too!

[griffinboy]

@d-healey

Would like that!

[Lindon]

@d-healey yep all in.

[Christoph Hart]

I‘m back on Friday so let‘s doodle that stuff.

[Morphoice]

@d-healey I'm all in!

[Oli Ullmann]

@d-healey
Great idea! :-)

[VirtualVirgin]

@d-healey
May I join?

[d.healey]

@VirtualVirgin Of course, everyone is welcome.

[d.healey]

Think I've done this correctly....

Doodle

(doodle.com)

[d.healey]

If anyone wants to propose discussion topics for the meeting please do. A couple of suggestions: Onnx, Christoph's HISE goals for 2025.

[griffinboy]

@d-healey

Did we do one on broadcasters already?

[Matt_SF]

@griffinboy said in HISE Meet Up:

@d-healey

Did we do one on broadcasters already?

+1 for broadcasters.
I'm in!

[d.healey]

@griffinboy I've got some broadcaster feature requests :) I have more tutorials planned too.

[Lindon]

@d-healey said in HISE Meet Up:

If anyone wants to propose discussion topics for the meeting please do. A couple of suggestions: Onnx, Christoph's HISE goals for 2025.

I'd like us to discuss the priority of bug fixes...what we think needs to be fixed first, second etc. NOT specific bugs but the category of bug. Here's my suggestion:

1. Bugs that cause existing functionality to no longer work - so it worked in a previous version - now it doesn't.
2. Bugs that cause proposed functionality to not work - so its never worked - but we'd all really like to see it fixed
3. New Stuff.

..and can we (if say we agreed to these categories) get bugs annotated in GitHub with their category.

[d.healey]

@Lindon That sounds like it will be very beneficial, so the first category are regressions and the second is failed implementation.

[DanH]

@d-healey Perhaps areas where Hise can be brought up-to-date / in line with current plugins.

For example the ADHSR envelope and the Table editors could really use updating.

Perhaps the Wavetable Synth / Waveform Generator?

[d.healey]

@DanH I'm not sure we should turn it into a feature request meeting, we can do that on the forum (same goes for Lindon's bugs actually). I think we should take the opportunity of having realtime interaction to see things in action.

@DanH said in HISE Meet Up:

Perhaps the Wavetable Synth / Waveform Generator?

What's your suggestion for these?