DSP compiling error on WIN, works fine on MAC

[d.healey]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

I am thoroughly confused.

What about the additional source code folder, anything in there?

[Morphoice]

@d-healey yes it has the same files as before, although I can't verify if they differ at this moment, i'd have to examine them, I understand they are created automatically?

[d.healey]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

I understand they are created automatically?

Yeah, but I think they need to be cleared when switching OS.

[Morphoice]

@d-healey

on a first look the old files have

wrap::mod<parameter::plain<project::Disintegrate, 0>, 

in the new ones it is

wrap::mod<parameter::plain<project::Disintegrate<NV>, 0>,

[Morphoice]

@d-healey i tried on another old project that stopped working, clearing them and even manually remove stuff didn't help, they were created the old way again... can't yet figure out why... it can only be something in the build directory, even removing "JuceLibraryCode" didnt solve it

[Christoph Hart]

@Morphoice the latter assumes that your project:: Disintegrate node has set the AllowPolyphonic flag set.

[Christoph Hart]

@Christoph-Hart What does the ThirdPartyNodes/node_properties.json look like?

[Morphoice]

@Christoph-Hart said in DSP compiling error on WIN, works fine on MAC:

node_properties.json

I can't find a file with that name, where should it reside?

[Morphoice]

@Christoph-Hart

AllowPolyphonic shows disabled. Wouldn't make sense in an effect plugin anways, would it?

[d.healey]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

Wouldn't make sense in an effect plugin anways, would it?

It's always better to compile if you can, a compiled network is generally going to be more efficient.

[Morphoice]

funny enough now that I added the ScriptFX1 to view the Network for the purpose of making this screenshot I hit compile DSP and this time it worked. Does viewing the network change anything internally? Does it need to be added as a ScriptFX1 to properly compile? Or is that just a coincidence?

[d.healey]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

Or is that just a coincidence?

I think this

[Morphoice]

@d-healey

lol. but I want to understand lol

[Morphoice]

@d-healey shall I now try on WIN or enough for today? ;)

[Lindon]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

@d-healey shall I now try on WIN or enough for today? ;)

well if you do - remember to clean out the Additional Source Code folder.

[d.healey]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

enough for today? ;)

Does not compute, there is never enough.

[Morphoice]

@d-healey computer says NO

[Morphoice]

@d-healey kidding aside, I need to figure out how to compile a current HISE version on PC first. I can't even remember how I did it back then. I share a dropbox with the pc so the source should be current, just hit projucer and then visual studio should do it, well once it has synced a couple thousand files

[Lindon]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

@d-healey kidding aside, I need to figure out how to compile a current HISE version on PC first. I can't even remember how I did it back then. I share a dropbox with the pc so the source should be current, just hit projucer and then visual studio should do it, well once it has synced a couple thousand files

I would caution against this approach for HISE building - use git/hub to get yourself a clean ready-to-build HISE project thats not potentially polluted with your post build Mac based stuff...

[d.healey]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

I share a dropbox with the pc so the source

Yup that's what git is for