@MikeB

Beyhan, 38, Turkey.

Chemical engineer MSc, Mixing engineer, Graphic designer, Music Producer (Electronic Music & Trailer Soundtracks)

Feature request

It's actually compatibility request. Native Support for Apple ARM cpu computers.

Basically Done - it's not 100% stable, but I can compile a few example projects for M1.

Hi everyone

As you might know from the forum, in some plugins, there are multi-instance crash issues in all DAWs but mostly Cubase, Reaper, Studio One.

If the user inserts one plugin instance in the DAW project, it will be ok. But if the user inserts multi plugin instances (like 5 to 10), in some machines, the DAW project can not be opened again (no problem while inserting and using in the DAW project by the way, the only problem is about re-opening the DAW project again) and this is a nightmare for a user/customer also for you too as the plugin developer

These multi instance crashes can be inverse proportion. For example, DAW project may crash with only 3 instances of your plugin. But it may not crash with 50 instances Or vice versa. It's all about moodycamels queue issue with Hise.

Of course this issue is up to your code optimization. If the communication queue between audio thread and UI is full, that means your plugin is sending too many messages. These too many messages can cause a congestion / bottleneck and then the crash happens finally. The DAW project can’t be opened again!

I’ve been investigating this issue (also acording to the users’ feedbacks of course) for a while and I just wanted to share my observations with you. These are my experiments and observations. If you find out anything else please wellcome and share.

Please note that “Multi instance DAW Crash Issue” has no only one cause. This issue is the sum of various situations. If you will be careful about these causes, the crash issue can be reduced or even fixed. The main goal is making a very light cpu / ram user plugin. So, possible causes are described below:

---

Wrong If Statement usage

One cause is using too much sequential if statements in a wrong way. Just a quick example for wrong usage:

if (value == 1)
{
Do something
}

if (value == 2)
{
Do something
}

if (value == 3)
{
Do something
}

if (value == 4)
{
Do something
}

In above code, since each if statement will be checked and that will cause too much message during the initialization. Instead of the sequential if statements, this implementation should be done like that:

if (value == 1)
{
Do something
}

else if (value == 2)
{
Do something
}

else if (value == 3)
{
Do something
}

else
{
Do something
}

Now it is correct. With using else if, when the condition complies it will exit the statement and each if statement won't be checked. This will massively reduce the clog and the plugin will be much more tranquiled, relaxed Alternatively you can use switch / case statements for this purpose too.

---

setAttribute:
Another cause is the amount of used setAttribute APIs. More setAttribute you use, it means the plugin probably will crash more likely in multi-instances. (Remember sending too many messages). Of course you will need to use it in most cases. But if there is a case that you can live without using even one line, try not to use it. Do not over use setAttribute in your code and be careful while you use it especially in an array usage.

---

Shared Functions:
Shared functions have been used in various places in the same plugin. If these functions have lot's of setAttribute APIs, and if you used multiple shared functions in one GUI element (for example Link Button), the plugin tends to crash in multiple instances of course because of the bottleneck on the initialization.

---

Image size:
Total used image size is very important too. Please note that, even if you compressed images and the size is reduced; it doesn’t matters! On the exported plugins, the image will take it’s normal place inside the memory like it’s not compressed, as big sized bitmaps. So be careful about image dimensions and formats. For example if your background image doesn’t have transpency, there is no need to use it as.png file. Instead, use as jpg. Because .png files can be 3 or 4 times bigger than jpg files. Using jpg files will end up big bitmaps too but at least you will not get "Heap is Out of Space" error while compilng.

Also avoid using big pixel sizes. For example if your GUI canvas size is 1000 x 600 pixels, there is no need to use 5000x3000 pixels Try to sharp the pixel sizes too, as much as you can. For knobs, calculate the optimum frame size for your GUI mesaurements and then prepare the imagestrip acording to this size. Don’t use oversized image strips. We need to make a very light cpu and ram sucker plugin Acording to my observations, going above the 15MB total image size, the multi instance crash possibility will be much more higher

---

Deferring Callbacks:
It’s not the ultimate cure for the crash issue but it can be a big improvement for some situations. Search forum for the usage of deferred callbacks. Also if you can reproduce the crash issue in your system, try using and not using plugin exports individually. Observe the impact, if deferring callbacks makes the improvement, use it. Also multi instance DAW testing is a good idea, save multi plugin opened DAW sessions individually (like 5 instances, 10 instances or 30 instances) and try to reopen them

---

Timer Objects:
Over used Timer objects can cause problems too. Especially very short times like 10ms, 20ms….etc.

---

Simple Serial Copy Protection:
If you are using thousands of long serial number batches in your plugin, since these thousands of serial numbers will be checked in every initialization, it can cause crashes. Instead of using thousands of lines for the serial copy protection, use the formula technique for serial number usage. Or make the serial check once a day.

---

OpenGL

If your plugin uses lot's of live analysis, vector based animations...etc, using OpenGL will be a good improvement. But if your plugin doesn't use stuff like that, it will has no impact, in some conditions also negative impact like black screen, not loading the plugin, extra crashes.... etc.

Feature Request:

HQ Wavetable Synthesis with audio import function and similar (LAF adjustable) display below:

Hi everyone

We've been working on a WooCommerce linked licensing system for months. I can definately say that you can make an efficient online licening system with Hise. We've built even a License Manager application, and of course integrated the same system to the plugins too.

Thanks go to @ustk for helping me about this system, he helped me to build a great solution for this I really appreciate that.

Here is a working example video with this system: https://noiseash.com/knowledge-base/activating-plugins/

I just wanted you to know that you can make the same thing including license activation/deactivation process with below requirments:

• Install the JWT Authentication for WP REST API to your Wordpress Woocommerce website. This is a secure authentication method (No need to embed Woocommerce API keys to your software anymore).

• You need to install Woocommerce License Manager plugin to your Wordpress Woocommerce website. That plugin is a go-to license plugin for Hise developers. It is a highly recommended, great and fast plugin that makes everything possible with lowest server requests. It's using JWT Auth system, that means no need to embed API keys to your exported plugin. This makes this plugin very secure and fast. With just one request, you can grab all of the user licenses which is a great feature! With Woocommerce REST API, you'd need to do it at least 2 requests, which isn't an economic way for the hosting server cpu. But with Woocommerce License Manager you can do it easily and much more securely.

If you install both on your Wordpress Woocommerce website, then you're ready to go with using Hise's server API and Woocommerce License Manager API in your plugins to authorize your products. You'll be able to get:

• Automatic license creation with the purchase
• Activate / Deactivate Licenses with Machine ID (max. activation number can be assigned)
• Get Purchased Products, Get License Meta Data,
• Register License that were sold by resellers
• Remove the license from the customer account
• You can combine this with subscription based selling via using a Woocommerce Subscription plugin
• And other ton's of features.

API documentation is here: https://firassaidi.com/docs/documentation-woocommerce-license-manager/api-version-3/authentication-jwt/

Bug Report

Latency Issue on FL Studio: When Delay Compensation is used, there is a big latency only in FL Studio. (Other DAWs are fine with delay compensation)

Bug Report

Write Automation Issue on AU Plugins: Write automation doesn't work in exported AU plugins. Read Automation works. (only AU plugins)

Hi everyone

I want to share some snippets that might be useful for you. I plan to share some stuff periodically. If you want to share yours, you can share here too, so all of the useful stuff will be in one place.

This is the first one, there are 57 vectorized icons (Bootstrap 3 Glyphicons) that I converted to the vectors in Hise, you can use them in your plugins

NOTE: Since the snippet has too many characters to write here, I am adding a text file below.

Cheers

1 - Vector Icon Set:

1_Vector_Icon Set.txt

@steve-mohican You've got several options:

• The first channel is social media marketing (Instagram, Facebook, and YouTube) as @dustbro mentioned.

• The second channel is email marketing. Still today it is very effective and all of the big brands do it continuously. But to do it, you need user emails, do not buy any bulk email addresses. The users should be subscribed to your newsletter email list themselves. For collecting emails, I suggest giving away a free plugin. This way you can collect audio industry-specific user emails.

• Another channel is forum websites. I highly suggest GearSpace, KvR, vi-control...etc. But be careful on this, forum websites (especially GearSpace) can be very dangerous for a new company because you can get lots of noise, arguments, attacks, even if your product is good But if the GearSpace audience accept your product, then you're ready to go everywhere

• You can contact Audio Industry Blogs such as Rekkerd, Bedroom Producers Blog...etc to publish your product release news. Also, you can publish one news per week in the KvR blog for free!

• I also suggest resellers (ADSR Sounds, APD, Producer Spot, Plugin Boutique...) Because they have thousands of existent customer database and the resellers can reach to them for you with a commission price.

Merry Christmas Hise family! I wish you a happy & safe holiday season

@d-healey I think this would be pretty good. "Opening files" has already been used by lots of plugin manufacturers. For executing the installers, it would be awesome though.

I am not sure this is already available in Hise but, also "Opning folders" would be great too.

https://www.gearnews.com/steinberg-discontinues-support-for-vst2-plug-ins/

@nesta99 Normally, of course you can name your plugins with spaces. For example: "Compressor LA2A Mk2"

And as I see, your Bundle Identifier looks ok too. Interesting.

@dabdab This video is from 2018. But 2 years after that video, in 2020 they released RetroVolt which is made with Hise. But I've just checked their website, it seems like the plugin is discontinued now.

@christoph-hart said in Creating dynamic fx's with Drag and Drop functionality in javascript?:

@lindon said in Creating dynamic fx's with Drag and Drop functionality in javascript?:

could be wrong...

I'm 99% sure the arpeggiator are the HISE slider packs connected to the 3 slider packs that the HISE arpeggiator offers - everything else would be a superweird coincidence.

That's why I thought so.

@natan said in Creating dynamic fx's with Drag and Drop functionality in javascript?:

A Combination Of The Center 3D and Every other Element Flat And Minimal Just Makes The UI Standout,

For the plugins, now I make the combination of the vector and 3D stuff but definitely need to go with fully vector in some projects

@natan It's so natural that you can find this ugly. Because you make great GUI stuff

Voxengo Deconvolver is a good way too

@casey-kolb It's been almost 3 years, needs to be fixed.

@lindon said in Trying to compile Develop.....again.:

@orange? Have you built develop branch with IPP enabled?

On Windows 10, I am using the scriptnode version from June 2021, but it works here with IPP enabled.

FYI, I had to update the VS 2017 to version 15.9.36 because it was giving errors.

If your VS2017 version is ok, I think you need to install the ipp into the correct file locations.