Ahoi!
Lately more and more plugin companies catch my eye claiming to use "machine learning" to capture analog technology (alias free) plus some other buzzwords...

Can someone elaborate on what we are looking at here? What are those machines? How is this done and can this be done in HISE? The only ever thing in this ballpark I heard of is the Kemper profiler... But now they are doing it to Distressors, 1176s etc... And usually compressor plugins all do pretty much the same with just different values and sensitivity curves for attack/release. At least if AP Mastering can be believed ;)))

@Lindon really depends on what sound and modulation possibilities you want to go for. Whipping up comething custom in faust should be straight forward. Habe a look at the boss or moog clusterlis schematics, they are usually among the most recommended flangers. Probably airwindows is another good source to start and easy to turn into a node. I had a thread how to do it now long ago you should find all you need in there

@clevername27 I just started heavily using spectra layers 9 yesterday to edit vocals. And funny enough I just recommended it to a colleague in the movie business who switched from protools to cubase

@d-healey brilliant! thanks

when a plugin is bypassed by the DAW, does or can it still do something? Is it just not receiving audio or completely dead? I was thinking of graying out some things in the GUI when it is bypassed, would that be possible?

This is just a stupid thought I'm having but has anyone ever considered seperate loop points on stereo samples? I came across this when sampling some chorused stuff on the Juno 60, where you could never find a perfect loop, but it should be possible if the left and right sample are treated seperately and have a nice effect not making the sound appear looped at all... worth giving a shot? how would it be done in HISE? two samplers panned right and left? seperate mic positions?

@Christoph-Hart see video. right on the node

@Morphoice I just found out about the tab, it worked either way, but the nodes still crash when I right click them, so that might be a completely different problemo

Ahoi,

I've just installed a new windows 11 and compiled the latest HISE
if I now pull and open my project (e.g. UNSTABLE) and try to compile the DSP network
there is this new message @Christoph-Hart added

I assume I have to add a ScriptFX node and go through all the networks and tick/untick all the nodes, but however if I do that and just rightclick a node to access its properties
HISE just does a little crashie on me.

I've recorded a short video here:
https://www.dropbox.com/scl/fi/ymwnk517pfhfk0iurcmie/IMG_9324.MOV?rlkey=od8drpdds7uc5ugahuwi93606&dl=0

basically all I wanted to do is recompile my project for PC because it still said MyCompany in the plugin info. Please tell me I'm not in for another 3 day adventure to get everything working again. I'm attempting to manually create the node_properties.json maybe that solves it already ;))

@griffinboy

Awesome thanks! I've already consumed some of those, ChowDSP was my read when designing the tape wow thing. Essential! Also did some experiments with WDF in faust so I seem to be on the right track there.

I'll take a deep dive and see what I can come up with!

@griffinboy hit me!

@jenö said in HISE 4.1 release vs compiling from dev branch:

I don't really understand how to keep the self-compiled version up to date and it just seems tideous to check for updates.

He has a point though ;)))
I've gone through that and still am agitated regularly if I have to over and over again, but that's just because I'm an old senile lazy bastard ;) In fact it's quite rewarding once you get a hang of it, gives you a great sense of achievement and I guess it's just what you have to deal with if you want to develop software. No pain no gain. And If I could do it, you can too @jenö - this forum has a superb community helping you on your way to becoming a pro plugin developer! No better place to start than here with HISE! I have spoken. ;o)

I'm looking into summing plugins, you know those claiming to emulate consoles, adding harmonic content.. I've been using Waves NLS in the past and liked it, though I can't really tell what it does and getting away from Waves altogether I'm trying to make my own...
Has anyone had a look into those magical things before and would like to share their insight?

I've checked out airwindows console and I can't really make heads or tales of it, some other companies model channel strips that don't even do anything nonlinear to the signal apart form being normal eq's... AP Mastering's rants come to mind ;) I don't want to create something that can be done in Pro Q3, otherwise where would be the point.

I do have access to some consoles, but from what I can test-record and measure the differences in sound (unless you crank them to extremes) are so subtle, they are not even worth the CPU to algorithmically rebuild them, or am I on the wrong track here?

If, say, channels interact because components are close to each other and there is some "bleed" that somehow is sonically pleasing, then that wouldn't be possible in a plugin anyways as DAW channels can't influence others or "bleed" apart from send and just adding some tanh saturation for "warmth" seems morally wrong ;))

@Christoph-Hart it did, I was using the plugin for over a week in my own album production before I decided to try and compile a pc version

@Lindon there's a menu item to create a third party node c++ template, which also creates a node_properties.json

in my case it contains

{
  "Disintegrate": [
    "IsPolyphonic",
    "AllowPolyphonic"
  ]
}

which apparently is the information HISE needs to create the DspNetworks.h file correctly. Otherwise it would have missing some parameters causing them nasty compiler errors I couldn't make heads or tales of...

I created the third party node files manually, so the json wasn't there. Had never heard of that before and on MAC it never made a difference, but the PC seemed to take offence ;)

@Christoph-Hart Good idea! Had I known I probably wouldn't have caused the fuzz. It worked fine on MAC, that was the confusing part. Also thanks for the github idea, it's cumbersome. but seems to keep the build files clean. Another crucial takeaway was compiling the third party nodes WITHOUT (disable AllowCompilation) the network first, then restart and compile the DspNetwork, it wouldn't work otherwise.... maybe that would be worth another warning somewhere ;))

Thanks to everyone who helped me find the solutions to the various issues and overcome my frustration to pull through. It was only three days of work and we got there in the end, I learned another bunch of things that will sure make things easier for me in the future. Also started a C++ course lol

@d-healey deleting shit multiple times and fetching it all over, compiling it all over in the end resolved the hash mismatch error.... though I wish I could exactly pinpoint what went wrong the first time, I guess it just is what it is sometimes, just fidding about

@d-healey so the c++ error could be fixed thanks to christoph, there was actually a json file missing to hold some info about the third party node hence the DspNetworks.h was created wrongly...

as suggested by christoph to work with github rather than dropbox i managed to compile the the network on the pc, now attempting to compile the final plugin. fingers crossed, third day's the charm ;) (hopefully)

@d-healey yes directly from the build directory.... I did it all over again, now github complains there is a filename too long when I try to clone my project onto the new pc.
I have to give up for the day, I need to go to work now. barkeeping. drinking. and vice versa.

@Christoph-Hart C:\HISE which is where github put the source... I'm just doing it again from scratch