Topics created by HISEnberg

@HISEnberg The fact is that I have the same questioning... I need better rendering and overall performances. I disregarded shaders, and honestly I don't really understand what settings I should use for which system.

@Christoph-Hart It works now, thanks!

@d-healey Great thank you so much. I think I need a refresher on the String API.

@HISEnberg Bruv…thank you.

@HISEnberg said in text Scaling differently across OS:

@orange @d-healey Thanks I see, I am using Latin-strict fonts but the issue persists. Luckily it is just a few labels that have this issue so I will just resize them for each OS but this is good information to have.

If I recall correctly there is the issue that mac pixels are square and Windows they are rectangles... so right down at the lowest possible level of display - they are different - so you need to compensate for the OS (or in this case hardware) in your code..

@Lindon @ulrik Thanks guys. I will try somethings in scriptnode though I don't expect such different results. Will post here if I find a solution.

Usually I wouldn't mind but my project is fairly dependent on having one global table envelope. I tried cheating by linking ScriptTables together but this was also causing crashes in HISE.

@HISEnberg haha I think the „under construction“ was just a passive aggressive hint from Dominik for me to take a look at it because he couldn‘t figure out how to use the method.

There‘s nothing „under construction“ there, it definitely worked at some point but I haven‘t used the method for quite some time. I‘ll take a look later.

@griffinboy Great I will post here if I come across anything.

@d-healey Okay thanks for checking, I'll open an issue for it on Github.

Thank you all for your quick responses! I have been on the move lately so not much opportunity to reply.

@Christoph-Hart thank you, I think this is the exact solution I am looking for. I haven't explored the macro control system to date so this looks like the proper time. Thank you for providing the snippet.

@d-healey I am not on my main system but here is 2 screen recordings of what I am talking about. It may be a DAW/Plugin dependent request, but the first recording is an Arturia plugin, the second is one made in HISE:

@Lindon you are correct, I think it is true with most DAWs. My hope was (and the macro control system seems to be the solution) is to set all parameters which exposed to the DAW, but only have visible/assignable the ones the user selects (so maximum 64 in the macro control scenario).

Screen Recording 2024-08-06 at 12.07.20 PM (1).gif

Screen Recording 2024-08-06 at 12.09.17 PM (1).gif

@HISEnberg yes, good idea, that also crossed my mind at some point.

@d-healey said in AudioLoopPlayer loading samples issues:

https://docs.hise.audio/working-with-hise/project-management/index.html

Thanks I am familiar with it, just been at the computer too long. Never hurts to brush up on it though.

@HISEnberg said in Audio Waveform Display Zoom Level:

Maybe a feature request

I'm sure it's been requested a few times

@Christoph-Hart Also I thought it would fix this other issue I am having but it seems to be related to something else.

I have a few FX networks that are modulation based (auto-panner, flanger, chorus, vibrato, etc.). These networks, compiled, work fine in other projects. However in this specific project, their modulation rates keep getting tossed to the maximum on every new note.

I really have no idea why (the ScriptFx works perfectly fine). Tracking their states in the Console shows them at the correct values. I removed any scripts I thought may be interefering with them. Are there any other modules (Midi, FX) or nodes in scriptnode that could cause this issue (maybe the converter, core.oscillator or temposync)?

@aaronventure Thanks I need to do some more study of the broadcaster first but I'll try the attachToModuleParameter and report back if it works!