set up complications...
-
so one of my products shows this message during set up - anyone any idea why? and how to get rid of it? (pressing ignore make sit work fine...)
-
@Lindon have you set these flags in prefs?:
HISE_SAMPLE_DIALOG_SHOW_INSTALL_BUTTON=1
HISE_SAMPLE_DIALOG_SHOW_LOCATE_BUTTON=0
-
@DanH nope if I do that will this go away/ - what are they doing exactly?
-
@Lindon they remove the sample install dialogue when you open a sample based instrument for the first time... It should solve your problem hopefully.
-
@DanH thanks I will give it a go.
-
@Lindon What have you done with the real Lindon? It was his thread that triggered Christoph to add those flags, and he did extensive testing...
https://forum.hise.audio/topic/1206/installing-samples-dialog
-
@d-healey said in set up complications...:
@Lindon What have you done with the real Lindon? It was his thread that triggered Christoph to add those flags, and he did extensive testing...
https://forum.hise.audio/topic/1206/installing-samples-dialog
the real Lindon? that guy had some sort of functioning memory - me now - I cant even remember who you are....
-
@d-healey -- hang on I just re-read that thread. I WANT to use the install process, but just not get this silly (false positive) error...
-
Yep this is definately NOT what I want ---
this completely circumvents the sampler install process....now no samples get installed at all... bad bad bad.
I'm just trying to get rid of this false positive response from HISE - see the image in the first post - If I press Ignore then it all works fine.
-
@Lindon what happens if you set both those flags to '1'?
In any case it seems your proj is messed up in some way!
Are you sure the Link file hasn't already been set in the app folder? (and it can't find the samples that it thinks are there?)
-
@DanH - so the link file has been set up in the sample install process, so its there- with the correct location - that is pointing at the correct folder - which is filled with all the correct samples, then it shows the message above, not every time and not to everyone... I wish I knew why or how to get rid of it.
-
@Lindon Probably because the check needs a bit more time before declaring the samples aren't installed...
-
@ustk said in set up complications...:
@Lindon Probably because the check needs a bit more time before declaring the samples aren't installed...
..er you mean a bit more time before it discovers the samples are installed?
so its a timing issue? Is there a way around this - some way to slow down this check?
-
@Lindon Hmmm... Yes, this is what I mean, but I'm not sure there is a "timing" involved. It might something else that makes the detection to occurs too late, only Christoph could answer, I am looking at the code but I'm pretty sure I won't be able to find anything...
-
@Lindon Can it be because users are placing the samples on a drive that takes too long to wake up?
-
@ustk said in set up complications...:
@Lindon Can it be because users are placing the samples on a drive that takes too long to wake up?
-- not for every case - I have users who have the samples installed do their desktop...
-
@ustk said in set up complications...:
@Lindon Hmmm... Yes, this is what I mean, but I'm not sure there is a "timing" involved. It might something else that makes the detection to occurs too late, only Christoph could answer, I am looking at the code but I'm pretty sure I won't be able to find anything...
@Christoph-Hart - can we have a loop that goes around this a couple of time - to account for different drive speeds - and thus reduce these false positives?
