Neural node bug on HardocdedFX as embedded
-
There's currently a bug in Neural Node.
The model I embedded attached below was working on the HardcodedFX in previous commits. Now the Hise screen freezes when the project starts.
Since the model is long, I wasn't able to paste the snippet.
-
@Christoph-Hart will the neural node bugs be fixed with the Hise 5 release? Please, at least this one, you can try the above model and see the issue.
-
@resonant fixed now. The problem was that it tried to load the network in the hardcoded FX before the first script compilation so it couldn't find it and there was an uncatched exception.
Now it prints this order of events to the console, so when you load your project you'll see something like:
Main Interface: Can't find network with hash 1234 Main Interface: Initialised network with hash 1234 (NetworkId)So if you read that everything's fine.
-
@Christoph-Hart said in Neural node bug on HardocdedFX as embedded:
@resonant fixed now. The problem was that it tried to load the network in the hardcoded FX before the first script compilation so it couldn't find it and there was an uncatched exception.
Unfortunately, the same problem persists. Hise still freezes while loading the project.
I've just compiled the latest commit with the latest Juce 6 submodule. -
@Christoph-Hart Have you had a chance to look at this? The last fix doesn't seem to have worked. Maybe it's something simple?
-
@Christoph-Hart said in Neural node bug on HardocdedFX as embedded:
@resonant fixed now. The problem was that it tried to load the network in the hardcoded FX before the first script compilation so it couldn't find it and there was an uncatched exception.
Now it prints this order of events to the console, so when you load your project you'll see something like:
Main Interface: Can't find network with hash 1234 Main Interface: Initialised network with hash 1234 (NetworkId)So if you read that everything's fine.
A friendly bump. Same issue persists.
I believe same thing happens on the Global Cables node too. -
@resonant I had this come up regarding the global cables. I forget exactly how I got around this, but I recall that just loading a new xml within the project, opening a scriptnode network with the node/global cable in it (maybe recompile the script interface and/or .dll network), then trying to relaunch the actual XML I am working from, seemed to clear up the issue.
-
@HISEnberg I recompiled the dll so many times. Also deleted the HardcodedFX and loaded again. No luck.
