@ossian1961 said in VST compiled romplers crash on old PC:

Pentium E6700

Pentium E6700 is 3.40 GHz VS Q6600 2.40 GHz. With DDR3 for you. DDR2 for me. huge difference.

anyway. the problem is elsewhere.
this old PC was mine before, and i composed music with sonar and studio one and a lot of vst (32bit) without problems.

this weekend we tried studio one, reaper. impossible to play just only 1 vst (every: waves - arturia - TOGU, etc. ...) without having 100% CPU hog and audio dropout.

Only cakewalk by bandlab (64bit) works well.

so i think this PC is very tired now ... ;)

that's not the problem that caused the crash with .ch1, but maybe a little guilty about ...

so i wont try to test with 2.0.0 and .ch1; Maybe with 1.6.0 and .wav. But if i have the same crash i think it's the PC sanity that cause problem first. Too old.

A little sad to have this kind of problem, but remembered a change for a brand new PC because starting to have some CPU/Ram limitations before. Now this computer is totally limited. :D

i think my son will start some project with this old PC and we will finish it with my brand new. better way ;)

@staiff it's not parametricEQ it is parametriq EQ with (q) instead of (c) as least in HISE. (that's how is written in Hise)

@dustbro Thank you, I will do it.

@christoph-hart thanks:)!

ceilf is still hanging around in the master branch, and it seems he brought a friend fabsf ;)

@christoph-hart you mean the audio driver issue?

Compiled the standalone .exe version for the rhodes you already have, but adding the audio settings panel.

By opening the .exe it says audio driver could not be initialized. (Looks like compilation saves the audio driver from mac or whatever, and looks for Core Audio instead of Windows Audio or whatever)

Fix attempt 1:
Turned audio driver to false. But doesn't work out
Turned all of them false but ui scale factor. Doesn't work out either

Fix:
Removed the audio settings call completely and worked.

Also, midi source on plug-in version also kills the plugin when you click it (obviously)

You might have to delete the moduleEnums.xml from your HISE appdata folder.

no.
Just i'm stupid.
i created before an LFO module. used sliderpack and table for custom LFOs.

After that erased the old LFO and replacing it by a global LFO (in global modulator).

And seems that the hip and the .xml kept the old LFO name and ID for the sliderpack and table.

I changed it when replacing the LFO. But the old settings stayed in the file.

So it crashed everytime i scrolldowned the listing, when arrived and showing the "wrong" pack and table.

i fixed it by hand in the both files.

No it's working fine.

No need to hack around on the scripting level, I provided a fix for this. Just ignore the value if it's zero, it won't cause any harm anymore.

okayyyyyy
took time to retreive the thread about crash in DAW (as i participated in, but i don't find it anymore)
remember that Alexaudio had the same issue in one of his project (confirm this Alex ?)

so i donwnloaded the project of this freeware and something strange happened when first opening in Hise:
a popup opened and said:
"the sample relocation folder does not exist. press ok to choose a new location or cancel to ignore this"

but this project contains no samples and no sampler module.

@Alex: it's a freeware; but it seems you added a timer (with gain volume controls) that shut down from 0dB to -100dB each 5 seconds ? like a demo ?
the .xml didn't work, the hip yes. All is on the script processor (like old HISE 1.0) what version did you use to create your project ?

vst 64 bit tested: working fine on all my daws (reaper, studio one, etc. ...). not tested the 32bit

EDIT:

the "color" section is a convolution. But as mentionned on other threads: the IRs are not embedded in the final vst. Maybe the cause for crash ? here no problem with that. but maybe a path to find the problem you have, David.

Okay...
i re-recorded my instruments in (min) 44100 kHz. redone the monolith and all is fine.

NOTE: i first create an .sfz encapsulation in ESC, just because i feel it more fun to import my samples inside HISE than direct .wav (.sfz has root note, start end sample, start end loop, etc. .. that is automaticly set up in HISE when importing)

when creating monolith a line is added in the samplemap.xml:

"MonolithOffset="value" MonolithLength="value" SampleRate="44100"/>"

maybe something wrong beetween the 27.8 kHz data infos inside the wav, the .sfz info and this line created in the samplemap file ?

BTW, with brand new 44100 kHZ or above samplerate: all is good ;)

So far nothing has been done with this and still cannot consistently do a Batch convert without crashing. I have to do things one by one, which is extremely tedious with thousands of samples.

@d-healey hahahahaha 😁

Any help?

@christoph-hart So is this SSE 4.1 requirment also system requirment of HISE exported plugins? Because of that should we give this information to the user before they buy the plugin?

@christoph-hart That worked! :)

Yup VS2017 it is plus the C++ extensions that will install themselves when you need them.

Could you make a video demonstrating the issue?

@d-healey I mentioned this before as well. I think Christoph is aware.