@d-healey @Oli-Ullmann haha yes that's why I will leave it up. I think I learned about this before (watching David's video) and just sort of forgot about what the boolean was for. 😆

@Christoph-Hart I gave this a shot but this wasn't the solution. It's my mistake.

@d-healey you are exactly right.

Basically for anyone who ends up here I recommend looking at and comparing the Info.plist that is part of the .component bundle. In my case I had changed the company code and this is why the plugin wasn't being recognized properly. Strange I couldn't find this in my Github commits but my issue had nothing to do with the version number.

Thanks both for your responses!

@Christoph-Hart Nice thanks! 👍

@Christoph-Hart can u share the example here would love to explore as well!

@HISEnberg Still can't seem to figure this out. I have an extra folder in my HISE project named External, which contains the bulk of my C++ code.

I've changed methods to adding this from FFTW3 directly into my project:

fftw3.h
libfftw3-3.lib
libfftw3-3.dll

And in my external C++ node I am doing something like this:

#define HAVE_FFTW 1 #define FFTW_DLL #pragma comment(lib, "../../External/libfftw3-3.lib")

But every time the compiler is failing to link:

!LINK : fatal error LNK1104: cannot open file '../../External/libfftw3-3.lib' [C:\Users\mikez\Desktop\HiseProjects\Personal\fftw-test\DspNetworks\Binaries\Builds\VisualStudio2022\fftw-test_DynamicLibrary.vcxproj]

@d-healey Nice thanks for clarifying, that does open up a bit more possibilities.

I'm trying some things to hack around it so I can get the best of both worlds. For instance, in CSS I am not seeing a way of distinguishing the list items by column. The items in bank > category > preset are all drawn the same in CSS.

@Christoph-Hart You move quick! Glad I mentioned it, my HISE-senses were tingling when I heard about this project. :)

Are you considering integrating the klang toolchain for rapid C++ deployment inside Scriptnode? I've been trying to find faster methods like this.

On another tangent which I don't think anyone else here cares about except for me, is the introduction of MIDI 2.0 to the JUCE Framework. Obviously this will take a bit of time, as there really aren't any major devices on the market that even support this yet, but it would be good to keep an eye on this development and possible integration into HISE in the future!!!!

Cool just to confirm for anyone else who ends up here, it does indeed work with the file_player in scriptnode

HiseSnippet 1448.3ocuX8zSabDEeVCiSvoIsopsms5IRUDxFLjf5gXL1t0sAvB6PiTOfF1cLdj2cls6NKXmnHkC8P+Vzy8qP+1zC8d9Fz9dyt16t0FJXQqQB44OuY9898dueuA5Fnr4ggp.hUo9S74DqOh1ahTOb+gLgjzoIw5SnsGuWjiPcTjtOOTSZLwmEFxcHVVq7M3trVaUh4yGdQClKSZySmhPNQIr4uT3Izoy1s92Kbcayb38EdY1cs5crUx8UtpH.QqPqP7Y1iXmyOjgaq.k7srvgDquht8laYWy4YNat416tiMaG9tCXCFTcKmZ01446VcqcY0d9N7JaSrJ1xQnUA8zLMODNzFJmI8FptTFeAmHBEm4xwAUI8faNdZx9CEtNcmROgDh0pcSIqUhIqOidfvQLa9rjFtP4TKxRZVEtNHU8V.IqLPZ0XH8XZO6.guNcEDOOf1Qp4ACXPrIKTh2Kw5Oo6qfMH0a3wFwaG.ClYv5aVoxSKC+5IecoRsjmKj7MbULGSRQagKOD1ppqR4tNtiRChj1ZgRVVIOTo4GIW+Ikdao0J8tRk+mKMXvBWCwRfx0kGrvkwblfqyv0kQdmwCdZ4KXtQ7YaD3n7DewaFwaGSMY1nR1QJzG4ySF2V45fDJ984CSjDtEBXERPHb2ZS35ySBWFx7GXWvGnB7HBGLEJ2bUIFmIakkCSyHVeI8scO9nuq098Os8QurYqie2IBkKWW9PkHjuwkrKHAL44bvoCfHM0BM0LSKoCN9298hwPzfqUhw0iRvUiHsVIM.ZMZ7fEfDxq5zDACjRk3qf+6yCzBjlsZxu.z.hyOWi1jGNRq7MjgmuRhLiE8VSGiyBfIYG3Ok663XzyLmX41uFiMo2XwafidE2w6+w5W8c3yB.wJn1AW4QzFZog46gtLY95UPoP4D4xz4kOPg0jEfT6b0rXgoLTnmjU38VnoT4Z0TtoP7wztBs8vEiwBK.iX1++AXLQI9gzVCFvs0o.bUZ6WurxtUt4xtz36uTRJ.bm3kmKiHKHNLxKU2Dq9vxwopv+BMULyOfCYR79pttrIqGx77c4GC.+okOyUYOpm3M74U.SxJaf6Xc6gLoj6FtLBkEui5PQNVEoExyOfoCDP0DE7+dPyca99InC4fBnFY73JSUn5wkNlA+E7IYwpyHLXwpSWLUdkbHWeoJXjIFk7ch08w.xWDKefjIO3zjX0XxdttpKQQAQRRLDhLy0U4NwenRJrwoh2wTLummJxnYY.dZEPioAlo9.7Xk9LgKVPzKJD5V3bjrGbNlWHYsxI7fPycdOZkMfefBjCUNvR2qMyFX+IcY5gXkF1.BRq4AaXOK89Jbnb4ZlGMcEaDuooOzJFsfS5YTFgmYgw5tSExPI7BVqjQROtD.GAE3EhS36DdBtpMykbRb+AfdvaINZXbrh3VeHc.vAm5a.DImq9ofqFv2H65y6P4s+58i7n1H+6xGOsWUlJwri.siNRG93oGXKnFwA5uaLKIo6.gLwKi2yArwyFaZnlg8vmNNcDjNlZZpzXp4ylqdOM2ONaJUlu2H9kwLV1YQV8QTLBeF7b4CPptOertuxblP4wE.Cf28CnuBbrAPpjCYNLzjOfE4pmadRFvu1MC7.PuUfuHzuSeGB5O7h8hzJO3LMciHWO8Wq9bdP8ecAzOn6bkdvGSOVozsC3+TDTdO4V6Ju+s0Wnq.yStCRdp+Gu4muF9+ATD4GipX29fvGdwUEDxWDXk0OhSYy83n69TqVigKSxby7HEnQcSQHCZd4jO2Y9TKyaYkbSKyv7CSTpwW3kWMpa1G+kjUSZnTi7Xl1RK0Ck+eoIpGyNPcpc76BP289lY.EToQ0cM5A33xK30+dvep6o114Op4Lbyk0vsVVCqsrFt8xZ3NKqgOaYM74+6Fh+mHRjCwTWnnpaq3VYVsjwUBPuUxeCPIPoOE

Yeah as @d-healey says the audio pro industry is wide and DSP are everywhere from automotive the adaptive sound systems for venues and so on. I also think the plugin world will change in the future in the manner we are interacting with, and more AI/DSP research leads to the necessity of getting more and more specialised with tools that might not be simple to use for the "simple man". Of course the implementation of some tools is made easy sometimes, but then the top notch systems will always be ahead, broader, and more complex. And with complexity arises computation power and compatibility issues. I am happy to see many great tools arriving but afraid at the same time, not being able to catch up compared to specialised folks.
In fact if I agree the market will grow, it might be for more engineered DAWs and tools integrating tech that I can't compete with for myself (like DAWs doing almost everything in the box, very "intelligent" plugins, automatic mixing tools, and other funky sweeteners...) while I am still struggling with basic DSP theory like I'm stuck in the 90s...
But I might be off-topic lol

@Lindon Yes I recall debating this a few months ago in one of the HISE meetings. You're essentially right as it looks like the dynamic container is essentially doing this anyways on the backend, just dumping the data to JSON (and writeToStream which is a new one I am not familiar with).

Probably it boils down to preference, I like having as few UI components doing the heavy lifting with scripting.

What about this? https://techcommunity.microsoft.com/blog/microsoft-security-blog/trusted-signing-is-now-open-for-individual-developers-to-sign-up-in-public-previ/4273554

Some comments say it didn't work for them, but others say it did.

@d-healey you may wanna check this https://signpath.org/. I found it on a github comment, not sure if it works.

@Christoph-Hart Thank you for the nudge I was trying to find a good example to build from and this is giving me a better sense of the folder/file hierarchy relationship. I am still in the poke around the codebase and find out phase so will report back once I understand more.

Happy to make a pull request to add it to the official version of HISE as well if I get it working, but I know this is a pretty niche case so unless there is a demand for it I won't bother!

@HISEnberg Sure

Ah you found it first :)

@d-healey I imagine that works as well!

@HISEnberg yes I saved each one before compiling but still got the issues.

I only installed 4.1.0 the other day but have no issues building networks on my older version. I'll do a test nest time I'm at the laptop and see.

And yes I'm on windows, ah ok you're getting them on windows too...at least I'm not going mad then. Wonder what the issue is though?

@Lindon Ah that is an interesting suggestion. It seems to work exported to VST (as of now) so I will keep it that way. But if you have any suggestions for improvements let me know.

The reason I am approaching it this way is to make a minimal code version for others to use. It's sitll pretty intense for a novice developer but it's certainly much simpler than my last method. I am making a separate post for it which I will link here:

Link Preview Image Modular FX Template - changing Fx order with drag and drop panels

Modular FX Template Every now and again I see a user posting about how to rearrange FX networks and a new method crossed my mind on how to approach it. This ...

favicon

Forum (forum.hise.audio)

Looks like it is time to order myself a new shirt 🙃

2851749b-fa43-45b0-a491-86a7a999f353-image.png https://forum.hise.audio/assets/uploads/files/1729617949536-0d94aa62-654e-4c49-9983-0beb3117ff3e-image.png