Very pleased to report my first attempt at a plugin worked more or less as expected once I realized I had to route the midi from another track in Reaper. Now I am getting excited about what this thing can do.

So, thanks again for all your help @d-healey. And Thank you @Christoph-Hart for this software. Pretty cool. Pretty, pretty cool!

@d-healey Oh good! Phew! Thanks!

I’m trying to build an audio plugin whose parameters can be controlled via a midi controller- specifically noteON and noteOff. User hits any key on their MIDI keyboard and it sets a parameter to a certain value, they let go and it goes back again.

I’m exporting an AU component and testing in GarageBand. My first thought was maybe GarageBand does not support Midi Controlled Audio Effects plugins- this is what I gathered from a 3 year old thread somewhere online anyway.

But then I read somewhere that audio effects that accept midi input are AUv3 format. Is that correct? In that case, is it possible to export AUv3 in HISE or is this thread from last August still valid: https://forum.hise.audio//post/68619 ?

Thanks!

Thanks @d-healey . I might check out Proxmox in that case.

And now that you mention it, I think I did read somewhere that VMWare users were able to sign in to their Apple IDs as well after doing some tweaking of the VM’s serial number or something like that.

@d-healey said in Lessons Learned Developing in a macOS VM on Apple Silicon:

I do on my VMs (running with Proxmox).

Oh good to know! Are you able to use passthrough USB as well?

Here are some key takeaways from my experience trying to develop with HISE in a a macOS virtual machine running on Apple Silicon using Apple’s Virtualization Framework.

I did this because because I am paranoid about security, but there may be other reasons one would want to develop in a VM. Hopefully this will save you some time if you are thinking of attempting to do the same.

1. macOS VMs running on Apple Silicon machines using Apple’s Virtualization Framework cannot use external USB at this time as there is no passthrough from the host- so testing MIDI from an external controller isn’t possible as far as I can tell.

2. You cannot log into your Apple ID from within a VM at this time, so signing your binaries becomes nigh impossible.

3. Because you cannot sign into the App Store with your Apple ID, you will need to copy your preferred DAW into your VM for testing purposes. Since it is free and doesn’t require licensing, I just dragged GarageBand into my VM’s shared folder and that did the trick. This may not work with Logic, ProTools or Ableton LIVE.

For Xcode, I had to download that off Apple’s developer website since I had a version mismatch between my host environment (Ventura) and my dev VM (Sonoma).

4. Everything else ran swimmingly under Sonoma and the development branch of HISE from a few days ago.

So, if you aren’t trying to sign your code and aren’t trying to develop an instrument or plugin that you need to test with an external midi controller, then you shouldn’t have a problem.

Hope that helps!

Thanks @d-healey and @Christoph-Hart - good to know.

I should have clarified in the feature request that, of course, one would want to be able to edit the prefab modules in the interface designer, for those of us who just want to quickly prototype visually without doing a lot of coding. But, if that is impossible, then, yeah, not worth it.

Anyway, thanks again!

Oh I didn’t realize this was possible to do. Someone else told me in another thread I had to build them myself, one UI element at a time. Though, would still be cool if it could be done via the Interface designer and not via the script editor.

Anyway, thanks for the tip @Lindon !

It would save a lot of time if the pre-built GUIs from each of the modules could also be used as the basis for our own GUIs in the interface designer. Ideally they would come all hooked up with each of the UI elements already configured properly for each of their attributes so that we don’t have to hook up each knob and its values one by one.

thanks @clevername27 !

Ok, complete noob here so, please pardon the question if this is obvious, but I am trying to create a simple effects plugin and want to use the dynamics module’s gui from the backend in the frontend interface designer.

The module already seems to have a decent enough interface that pops up when I click on the module in my module tree. But I can’t figure out how to add it to the layout designer.

Do I need to add all my own UI elements one by one or is there a way to use the default layout from the module’s backend interface? Seems like I could save a lot of time if I don’t need to recreate the whole interface for each module.

Does that make sense?

Thanks!

@d-healey Good point! Of course, that doesn’t negate the fact that it has multiple known vulns already.

Ah, good to know @Christoph-Hart, Thanks..

In that case, I might give it a whirl like you suggest @d-healey.

This being said I don‘t care too much about those security warnings - if I was writing a software that does online banking I would make sure that there are no issues like this but a potential buffer overflow in a console text processor will not cause any harm and I can see no scenario where this could become even remotely concerning.

My concern is that while HISE is not an online banking app, it is still going to be run on the same machines that many people do their online banking on. And if there are known vulnerabilities that can be exploited, there are likely hackers out there trying to exploit them, no?

Of course, I may just be being paranoid out of ignorance. I only know enough to know that supply chain attacks like the one on xz utils are real, but not enough to know how they work. I suppose most attackers might tend to focus on web apps on servers because they aren’t sitting behind multiple layers of NAT, firewalls, etc like desktop clients. So, maybe you are right that a single vulnerability in a console text parser isn’t a big deal.

On the other hand, there may be scenarios one cannot foresee.
For example. multiple small vulnerabilities can be used to create bigger ones when exploited in combination. See:
https://arstechnica.com/information-technology/2021/03/expert-hackers-used-11-zerodays-to-infect-windows-ios-and-android-users/ That one relied on zero-days to break into fully patched end user devices. I imagine it would be even easier to exploit known vulnerabilities that have gone unpatched.

I guess in the end I am just trying to make the case for maybe not shrugging off warnings and using the GitHub tools to mitigate any potential security issues.

Food for thought anyway.

@clevername27 yeah, also looks abandoned more or less. See:
https://github.com/xcpretty/xcpretty/issues/360

Hi all,

How necessary is xcpretty for working with HISE on macOS?

The reason I ask is because the Dependabot and Code Scanning tools on Github list several security issues with it. (You can Fork the code and set them up under Security in Github to see them.)

These are the Dependabot issues:

Dependency Confusion in Bundler High Development
#1 opened 12 minutes ago • Detected in bundler (RubyGems) • xcpretty.gemspec

Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile. Moderate Development
#2 opened 12 minutes ago • Detected in bundler (RubyGems) • xcpretty.gemspec

RuboCop gem Insecure use of /tmp Low Development
#3 opened 12 minutes ago • Detected in rubocop (RubyGems) • xcpretty.gemspec

And these are the Code Scanning Issues:

Inefficient regular expression
High
#10 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:58
master

Inefficient regular expression
High
#9 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:58
master

Polynomial regular expression used on uncontrolled data
High
#8 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:481
master

Polynomial regular expression used on uncontrolled data
High
#7 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:462
master

Polynomial regular expression used on uncontrolled data
High
#6 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:459
master

Polynomial regular expression used on uncontrolled data
High
#5 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:433
master

Polynomial regular expression used on uncontrolled data
High
#4 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/parser.rb:316
master

Polynomial regular expression used on uncontrolled data
High
#3 opened 12 minutes ago • Detected by CodeQL in lib/.../reporters/json_compilation_databas...:37
master

Polynomial regular expression used on uncontrolled data
High
#2 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/ansi.rb:61
master

Polynomial regular expression used on uncontrolled data
High
#1 opened 12 minutes ago • Detected by CodeQL in lib/xcpretty/ansi.rb:51

TBH I don’t really know what those warnings mean but they have High severity warnings so they look scary.

So, can I get away without using xcpretty?

Thanks!