DSP compiling error on WIN, works fine on MAC

[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

[DanH]

@Morphoice are you still having issues compiling the dsp networks on Windows? If so did you try loading the VS project and running it from there?

[Morphoice]

@Lindon I used github to install it onto the dropbox folder, the WIN is just a virtual machine accessing the external dropbox, I don't see the need to install github inside the virtual machine again

[d.healey]

@Morphoice If you install git, then you just call git pull to get the latest version directly from Christoph's repo

[Morphoice]

@d-healey yes that's how it works on my mac but do I necessarily have to do it again on PC if both machines access the same files on disk? I'm considering switching from a virtual machine to PC hardware... just for the sake of it, a friend is about to bring over an old notebook

[d.healey]

@Morphoice Oh I see, a shared disk makes sense.

[Morphoice]

@d-healey still wont compile HISE ;/(