@d-healey Thanks! It's the modulation wheel. It makes sense because I just realized that the mod wheel on a normal midi keyboard does the same thing.

Also I read the K-Board manual and it says that the pressure is sent to the mod wheel (CC1) but it can be changed to Channel Pressure massage with the software editor.

@Noahdeetz

Hey @Christoph-Hart is this what you would recommend?

Best,
Noah Deetz

@Lindon Ah I think it was the Company ID. That seems to have fixed it! Thanks.

@d-healey thank you for pointing me in the right direction.

@Christoph-Hart Makes sense and thanks for everything, legend

@DanH Thank you, Dan!!!! I have a "great success!!" (-Borat voice) on my hands thanks to you!

I had some initial trouble, but ChatGPT helped me correct it.

I'm posting here incase it's useful to anyone at allScreen Shot 2023-11-14 at 10.36.57 AM.png
Screen Shot 2023-11-14 at 10.37.11 AM.png

@HISEnberg Sounds great! I'll send a message your now.

@d-healey Great, I'll use Git in that case. Thanks!

@Lindon

oh my god, i get it! Now thats embarassing. Thank you so much!!

@d-healey said in Server.downloadFile() - any extra error data?:

@Lindon

FileSystem.Downloads

-- and Im going to assume this is user writable...

Yes this should always be writable, otherwise it's a user issue :)

😉

@Christoph-Hart Ok, now it works. Thank you!

const appData = FileSystem.getFolder(FileSystem.AppData); const settingsFile = appData.getChildFile("GeneralSettings.xml"); if(settingsFile.isFile()) Console.print("General Settings vorhanen"); else Settings.setZoomLevel(0.75);

@maxtownsley

Hey @Christoph-Hart has there been any fix to this yet or should I downgrade to 14.3?

Figured it was worth it to check before downgrading.

Best,
Noah

@Evan-Splash @d-healey @Christoph-Hart Alright I've made a minimal pull-request (assuming no one needs it as Dave raised)

@d-healey Looking at the matrix output, it moves at the rate set by the floating tile.
So, I guess the setting I was looking for was hidden in a weird place 😁

Thank you for the tip!

I didn't know HISE made any modifications to JUCE.

Mostly small getter / setter functions or other trivial things, but the most important change (which has no chance of getting pulled into the main JUCE codebase) is the addition of a custom Buffer for floating point values to be stored in the var class.

The process of updating JUCE is rather annoying (and each time it introduces some weird glitches), so I only do it when there's a real reason for it (also my cheap ass doesn't have a JUCE 7 license yet)...

Normally I'm doing these steps:

Fork the master branch of JUCE exactly from the commit that I forked it into HISE Copy over the JUCE directory from the HISE repo. This mark all my changes in the git. Review them again, do some cleanup and discard the changes that are useless (sometimes I just remove an assertion that annoys me too much) Create a patch from my changes Copy the current JUCE version into HISE Apply the previously generated patch file to reapply the custom HISE changes (sometimes I need to resolve merge conflicts).