Posts made by langermarc19

@d-healey There was a Debug one and a Release one

@Christoph-Hart To test this I just deleted all of the compiled DLLs, re-exported from HISE debug, compiled and built in XCode in the debug configuration, then loaded HISE Debug as an executable and got the double-free in the same location.

Not sure where the memory corruption could be happening here but still hunting

Should add that these are coming from the XCode output

the crux of the issue seems to be that the array of parameters is cleared here before any elements of that array are actually assigned. I think.

Update: this is happening for ANY compiled DLL that I load in HardcodedMasterFX while in DEBUG mode, seemingly when trying to initialize the parameter list

Hey @Christoph-Hart checking again to see if you have any thoughts here about where this might be coming from. Gonna go digging in a moment.

Hi There,

I am trying to debug a custom C++ node that I created. When I open the custom node in the Release build of HISE by using HardcodedMasterFX it opens, but when I try to debug by building from XCode with the HISE Debug as an executable, I get the following error when I try to open the custom effect:

Looks like a double-free, but I'm not sure why this would happen in Debug and not Release. Any thoughts @Christoph-Hart ?

@Casey-Kolb for reference

@Christoph-Hart for this one I don't have rubberband included no. But that's good to know I guess, it's not so far out of range if it's taking me ~5 minutes

Was just able to do a rebuild in a little over 5 minutes. Better but not great

PS I'm on a 2018 Mac Mini with a 6-core 3GHz Intel i5 and 16GB RAM

@d-healey @Christoph-Hart I set the scheme to the Debug build configuration and chose "Debug for Running" and it's still taking a long time.

The HISE version that I used to export the VST/AU initially was the release version. Is that potentially the problem?

Hi All,

I am somewhat new to HISE and just came across the first issue where I really need to be running my plugin in debug mode with a DAW as the debug executable. It seems that I can do this by building from the Auto Generated JUCER file and exporting to XCode, but actually building my HISE project takes a LONG time (like 20 minutes or more) because it needs to compile so much stuff.

Does anyone have advice on how to debug for quick changes when testing in a DAW? I want to be able to set breakpoints and write DBG output from the C++ code itself to investigate my custom scriptnode nodes and such.

Thanks!

@Casey-Kolb

@Christoph-Hart nevermind I found FXNodes_impl and I think that has what I need

@Christoph-Hart where in the codebase is polyphonic_base located? Want to look at how prepare is implemented to see if I can write breakpoints/debug output to find where this is getting reduced to mono. Thanks!

@Christoph-Hart this resulted in an error:

Reference to 'Point' is ambiguous

seemingly because there is a juce::Point<ValueType> class and also a macOS defined Point class. I'm going to dig deeper into what's actually happening when I'm building/linking these libraries. This is at the edge of my C++ experience.

@Christoph-Hart I attempted to do this by adding a path to the compiled rubberband.dylib in the "external libraries to link" section of the auto generated projucer file, and my node contains a #include to the header where the API methods are declared. Let's see what happens when I include the .cpp....

Hi everyone. I've been trying to get the rubberband time stretching library working within a HISE project to create a custom Scriptnode node which involves some time stretching.

I created a new node template using "Create C++ third party node template",
cloned the rubberband library (github link) into ProjectFolder/DspNetworks/ThirdParty/src. Then I built the rubberband libraries using meson, as instructed in the README included in the rubberband repository.

However when I try to either 1) Build the new node inside XCode (after exporting from the AutoGeneratedProjucerFile)
or
2) choose to "Compile DSP networks as dll" I get a bunch of "undefined symbol" linker errors from such as

 Undefined symbols for architecture x86_64
> Symbol: RubberBand::RubberBandStretcher::setTimeRatio(double)

I know that typically this happens when a function in a .cpp file isn't scoped correctly, but both the node file and the rubberband functionality are all header-only and so I don't think that's the problem here.

Any help appreciated! Spent a lot of time trying to solve this already.

Actually I think I may have found the answer in hi_dsp_library/snex_basics/snex_ProcessDataTypes

Yes I meant to write "template" twice....

I am trying to create a new scriptnode node. I created a new C++ file by selecting File>Create C++ third party node template in HISE, and have opened the template.

I looked at a few of the built-in nodes for reference, and watched this video, both of which helped my general understanding of what is going on.

I noticed however in both the built in code and the video there are calls to a function toChannelData(int channel) on input of templated type ProcessData&. Are we supposed to assume that the data being taken as a template argument is of a certain type with particular methods available? If so, what type is being assumed both in the video and the examples that we can call toChannelData(ch) on? Is there documentation somewhere that explains all of this.

Thanks in advance!