HISE Meet Up
-
@DabDab It's 3PM Eastern Standard Time, USA. Given that different nations do daylight savings time differently (if at all), I'd suggest you'd get the most accurate result as someone native to your area. Hope to see you there!
-
@clevername27 Okay so what is the final date and time ?
-
@DabDab Monday 3PM EST USA
-
@clevername27 See you all then! For IRL, Las Vegas is always a worthwhile trip haha.
-
Very bad timing, I got sick and had the flu, so I couldn’t attend this time. I hope next time.
-
@orange hope you feel better soon
-
Just want to confirm this time, is the meet in 4.5 hours?
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey Yes I think so :-)
Berlin 8. London 7. -
-
I'll be late, don't wait for me. it'll bed time (new winter hour) for the kids... I didn't take it into account until David pointed it out
-
I missed the time . It is a late night time to me.
-
@DabDab said in HISE Meet Up:
I missed the time . It is a late night time to me.
you didnt miss anything - its about to start..I think.
HISE Development for hire.
www.channelrobot.com -
-
Here's the recording - https://youtu.be/WQHWM9I7W94
-
@d-healey
thanks for sharing this everyone -
Sorry for missing this, I'm fully engaged this week and couldn't find an excuse yesterday to hide in the loo for an hour.
I'd like to add my 2 cents to the docs discussion. Regarding with what's missing, I think there's a number of methods which are obscure and are missing examples. These are easily tackled as they come, someone can just post and then another person can chime in and provide an answer or an example. This ties in to the difficulty of adding to the documentation, because there should be a simpler way to just submit this to the docs. Right now I just make a post in the documentation subforum and hope @Christoph-Hart adds it to the docs while he's waiting for HISE to build or something.
Another point is the search. Here's Kontakt's docs https://www.native-instruments.com/ni-tech-manuals/ksp-manual/en/welcome-to-ksp
If you start typing, it'll immediately filter results and highlight first the matching methods, then methods or topics where the word is mentioned while showing a few lines of context as well. So I would suggest getting the search to this level.
Another option that compliments this further:
I'm playing Frosthaven (have been for a while and it'll take a bit whiler to finish it). It's basically an attempt to pack a tabletop campaign into a boardgame with hard rules that doesn't require a DM. Works great for two people. It's absolutely massive; the rulebook is 80 pages long. Practically a novella. At the end, there's an index with every possible keyword mentioned in the rulebook regarding the game mechanics, sorted alphabetically, and next to each is a list of pages in the rulebook where the keyword is touched on or explained (the pages explaining it are in bold). It works so well for navigating this huge rulebook on the fly. There's a version online and you can see the index here
https://pikdonker.github.io/frosthaven-rule-book/#page_80
The Kontakt docs I linked above do it with the search results; it shows all the places where the keyword was mentioned. But not everyone (especially someone new to a different part of HISE or HISE in general) knows what to search for. An index like this is easily skimmable and can provide leads very quickly, but can also solidify the lingo for HISE which will also make the forum talk more searchable.
It wouldn't have to link to pages or methods, but if a search like the one for KSP is implemented, clicking on a keyword should immediately pop up a search and the effect should be as if you just got pointed to a page in the rulebook.
This index of keywords is something the community can easily help create and solidify, and then a pass can be made through the docs to make sure it's consistent. This could be a lot less work than rewriting docs because of a paradigm shift or restructuring.
Regarding helping things get up and running more easily, I'll make a post on the weekend or next week to share some of the scripts I have that build different versions of HISE and plug in any preprocessor definitions that are written in a separate text file.
-
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.
-
@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.
