@d-healey For FX plugins, do we need to add or remove anything new in the build process?

Posts
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey Is there a way to completely reset all settings and make Projucer 100% clean?
I suspect something might be hidden in Projucer—are there any folders I should delete to ensure a truly clean build? -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey Also, have there been any recent changes to the HISE build process—like new flags or extra definitions—needed for using Global Modulators?
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey
The error is still there—no way to get rid of it.I created a new project, only imported the UI (no callbacks), and rebuilt the networks from scratch—same error.
I even tried using previous commits, but no luck.Could this possibly be coming from Projucer or the VS version?
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey Compiling A VST3 Right now
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey Strange, Which Commit?
And also what VS? for Windows? -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:
13 minutes ago
@ILIAM Are you compiling the network before compiling the pl
Just compiling the plugin, the network above has only 3 nodes, 1 timer, 1 MinMax, and 1 Bipolar.
I 100/100% sure the error is because of the Timer node ( set to Random ) -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey Okay, here are my results:
- Pluginval: Immediate crash, not scanned.
- Bitwig & Reaper: Plugin doesn’t show up.
- Cakewalk Sonar: Shows as 32-bit and flagged as risky. After inserting it, Sonar completely crashes.
Removing the Timer Control node fixes everything and brings it back to normal.
Could you please try compiling on your end and see if you get the same issue? -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@d-healey I also tested a LFO in a global modulator. It set to random, and same error shows up.
no, i didn't tested on pluginval or other daws.
It should compile and work normally on Ableton, I guess there isa bug in Random and hise.Do you have time to compile the snip and double check?
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@Christoph-Hart @d-healey I’ve tested every possible scenario, and they all lead to the same result.
The snippet below triggers the error:
HiseSnippet 1620.3oc2XszaaaDDdokW+PIoIAM.8pN5TDXPJqGVnGR7yTgV6HD4XzaAqHWEsvj6RPtxVtE8d+Y0eR4eP6LboDIkoskUaCZqLfk1YmYmWeyLKIehlK83deLVJBC4ZBwpRuHkKONVEQrpd10gbh0io8uVpGcvHlPR5dHw5qnmvh07nZFR6ecHKNl6Qrrp7Vjf0lqRR974WuOymIc4YjHjyUBW9OJBD5Lp8dyOH78Ol4wOSDji6FuoqqRdfxWMFrmJTaRHy8B1m3mxP1VgR9dV7Hh02Ra2g2dP6lM1s9NrNNNt06341nt8Nsa5UuQqVCrc1YmF6NnMwZsi7DZUTeMSyiIVqtux659iTWIMJ3bQrXfOGW3P5CZ1P9XkuG5hHUxAiD9dyBTwPXa0bgsJlv1KnmH7DynmE9dVxF0xjHe.zZkhlWkBlmSdyyNm4UhIYkyjV0XROm12MRDpy1AsmGQ6Jgr4PFjmxaJFdIV+N8.EvfTuc.6B9wQvhYBrUKa6WUC92K+tgiktZgRVSIOUo4uSt0Kq9KU2r5uVs17aMbXo6gpIR46yiJcaDZDcWBtkbbv.dzqpcIyeLeFif6WLlRu8XZ9TtqwqywnR1UJzuKjKuMf.IMTA+5CcOjoYXhHkFvWHORKPSv5P9kPYfIsrI8Pd7EZUHTHbibFfVTdi8Y5hPHrPKcCHFTHugIGYrPec9Bw+1vUKpI9bZOg1cT413JkXiPj5eBaLsZ7IziFNj6pyLvUoG+Se4J8plV5A5DUNkdX+dkVs8azLjcXDOjEwOS0ymc8VwrfPe96Ai6U0F3qbunu3m42rbHzn68QN1xcDSJ49wKSUyZKb3v4tyFuWMVKje5DlNRLA78SGGzGZn6xOH05.ZVqfEOl013ZDPzGlNkr3OfOoa5fqsR2zY5l4p6NkquREcQRdH82DqMvf9lziYBeLveNOJFgjVqSs2F9irmuu5pCTAghTvJjQRn0S4ec3HkT3hjLbL0t2KPMFTYpwmgz2eZxYpe.CoNCzLB76ONFZe38NYe3bRlLh.uSUdvuV+XlKDvutGSOBKfvFP.ZkGss6LTalOjAdvvtYfnAVgIodrHfBzkN1jfPMLcNpwn.eI.iX3TTqJ39lPVhorFpqmPiUC0ebPhhHELtuImwkmoxLpGSMTQC+dsibMIAJoqftDqfFzSo8CTJ8H.LkbOgyQDKVIW2NolOOuOl1M9b7jbY9SYDxSS8yJ47y0oZbzRQO7oIdHTersYyx7roBdON0p2oSsI8.e3j65M0JAQl2YVC6vNye2f9dlzSEjGycFK5Sbcb53FI20fhSPVvQCxDHjArIjY.Cj55TyQh1KzaYR5DK5YLnxFKc66K73Q8fKcgq1armPcrvrE7cB7hPNTDGBMn1eLzg0z9MC7g96zUfebhPl5DTrxibBaxr0Nv59ZdXZkSxZz42ftG3MWNy8M6bHeHarut.MxhopM.7hscAs8BfEGayGmFcrcbZ4jn7plKGcYFH5qo6zpw1Ib1rQ8F10q2dNiYcZyjimjCiMK9W.j8rYfrzcKCkMSz6q1YwQCUoCDgJeVjysfGJjAWKWXkdeYPSAkgzdi0p.X5Q58lKDkJjrVnScSjKQv3.RAVmGHXOGPXQOa1jjytLb0b9ws.yJECkor0nNIXtK3WYv.FIpuaG6Vviszn4tNNMZUmXp2Q1dX.9ExOgCFv7Or.3RUzVk1CwW3M7tSuvnrb8GyWzjClVxnQrrIc+RqaxI88N0IObux+Nf6qC2Xj4+.N04xSMKbp0KA50ZG6N06zt0t161rQ6NsSU6aYAArEA6kOqURumBMQH2ZHtZ5.NwDnZ4dhKoKxdjgxLrL3XFe4c8rGJ5L9D8YpDgg1jWBNCZPOh9AoGeHb2FORWC0janezDXaIyO2iz.XLX3GNrzqPq1koyqIaSJMxT+gFY97q+OWjo7anj0X9FQlMRuW4+qhMqTZro3MwKDfpRm06i7WQ1B2Q0ZwtL89J0EArjm0Z4dcGeIdxv.laj5ioCLPmaiDJPSHYxXBDgAqq4Ptb9tKABOwGccKdT2Pv5Kqf6rrB1XYEr4xJXqkUv1Kqf6d+BhuF0zoiHjGFB06nDPnk0QxokWUH7fAbOOtm4MrfX0YTj7IoONik0PA9xLVA+Zpkj7zcaOZ5aBz7nY+Y2s2z4
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
Things are getting worse here.
WTH!
I opened an empty project with just a Global Modulator, two LFOs, andEnable sound generator Fx
enabled, and guess what?
Same error again!Fx / Today commit
@Christoph-Hart Any thoughts on this? -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
I compiled a simple gain project, and everything worked fine.
After narrowing things down again, I discovered that the Scriptnode Node Timer
control.timer
(in Random Mode) is what’s causing the crash.
I ran several tests, and I can clearly confirm that the error comes from the Node Timercontrol.timer
@Christoph-Hart Any chance you could confirm this or take a look at it?
-
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
Nah, almost all compilation shows me the same error
anyone having a stable Commit?Not this one:
https://github.com/christophhart/HISE/commit/1d6a4d0e43ac6fbcf2bf7c0e53683657697f4370 -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@Christoph-Hart
I found out thatcontrol.timer
is causing crashes.
I compiled an empty project with just onecontrol.timer
set torandom
, and it triggered the same error.
Could you please take a look at that node? -
RE: Simple Gain buggy?
Use a stereo sample to test the Width knob.
Pan knob > modulation needs to be set either to the right or left—otherwise, it won’t have any effect. -
RE: Abeleton shows An error about a plugin I Compiled with the Latest Commit
@ILIAM This commit:
https://github.com/christophhart/HISE/commit/1d6a4d0e43ac6fbcf2bf7c0e53683657697f4370I erased all the Scriptnode networks and just kept the UI and a few HISE modules—still no luck.
I tried narrowing it down by removing and compiling step by step, but that didn’t help solve the issue.
Looks like I’ll have to rebuild the networks from scratch inside the new HISE. -
Abeleton shows An error about a plugin I Compiled with the Latest Commit
Hi,
I switched to the new commit yesterday, and now the project I made—which was working fine before—has started throwing an error and won’t even scan.
Were there any recent changes in the new HISE build that I should check or take care of? -
RE: FFT Analyser Path - Need help drawing the magnitude to height
@Chazrox Nah, just changing a number!
-
RE: FFT Analyser Path - Need help drawing the magnitude to height
@oskarsh Hey man, I tested the FFTVisual.
It works the first time (importing the snippet), but after just one change in the namespace and hitting compile, Hise freezes and crashes. Any ideas?