@thrice801 said in issues and questions about css styling:

but still illustrates the on screen keyboard issue within panel

Yep, no idea why that happens

np figured out a workaround with setPlaybackPosition instead

@ulrik that did it thanks! swore I tried it yesterday but think I did something wrong

I'm seeing this in the latest version of HISE as well on multiple MacOS:

batchCompileOSX: line 7: /HISE/tools/Projucer/xcbeautify: Bad CPU type in executable

macOS 15.4.1 + Xcode 16.3
macOS 13.7.5 + Xcode 15.4

building from the autogenerated projucer file works as expected.

@d-healey success! (sort of, exporting still not working but will post separately). Thanks for the help

@d-healey so I read through that, but I don't think that's the issue, because I don't even have a libfaust.so file in that directory, only the .a file?
(I'm on the most recent version on the github releases page, as of like 2 months ago; not the develop branch btw)

I did see a readme in the file, and saw this contained within, which sounds like the issue; well sort of, different filename though. Screen Shot 2025-04-13 at 7.20.20 PM.png

However, when I attempt to follow the steps, I don't see a valid architectures section at all. I see Screen Shot 2025-04-13 at 7.21.07 PM.png

So I changed OSX Architecture from default to Native Build Machine and tried that, but still didn't work.

I also tried following the instructions of the readme to download and install faust into the faust directory, also didn't work.

@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 All included files should be available from the little drop down at the top of the script editor in which they are included.

b8625da2-eefd-4895-b95c-73dce3b334df-image.png

ahh ok I see thank you! been meaning to subscribe to your patreon gonna do that now

@d-healey makes more sense now thanks!

@thrice801 said in Issue with simply playing a file, and question about introspection:

@d-healey when I tried the trace function, it broke off execution and opened xcode (not familiar with xcode debugging), I can't tell if that is the expected behavior from that, or if it was trying to log some data as json unsuccessfully, and it is blowing up, and xcode is catching the error (the line it breaks on is something about json serialization) - is that the expected behavior of trace, or is it supposed to be putting info in my console? - also the variable watch table gave me slightly more info which is helpful, could see arrays of strings and what not, but still don't see any class names or object types and what not.

Thanks all I eventually got it figured out, and was able to get the file loaded in the AudioLoopPlayer. However I am now realizing, there is no play method on this thing. How do I actually go about triggering playback of the file, or what am I missing here?

I'm basically just trying to trigger playback of the sample now, when the daw transport play button is clicked, except I have no daw here. So I'm wondering, how do I actually play it back, and also: is there a way to simulate daw transport playback/controls directly within hise (and or setting tempo and things)?

just running it in the code editor, just using Console.print(trace(myObj));

-- any idea on the triggering playback of AudioLoopPlayer also, programatically? is that not possible, do I need to use a sampler and attach midi for playback or something?

@thrice801 You should use the develop branch if you want the latest features and fixes.