last build (1.1.2) compilation errors
-
???
no problem for giving samples, but as i wrote before with and without samples it's the same thing. That's why i din't use samples for this simple example.are you just explain me that i must "remake" the samplemaps and hlac files ? not the same beetween 1.1.1 and 1.1.2 ?
for me the problem is not the samples. it's just the 1.1.1 vst compiled projects works in all DAWs, the same compiled project with 1.1.2 doesn't work; it crash DAWS
i miss something ?
-
No problem here to export with version 1.1.2! However, I still can not compile from GitHub....
-
ok, maybe my 1.1.2 version...
Is it possible to have a compiled 1.1.2 version (with standalone app for working) ?
will try with it my project -
Sorry guys, I am currently in over my head finalizing a huge project that is going to be released on Friday. I'll promise I'll clean up the codebase and make everything smooth again next week.
-
Good luck with your project Christoph!
-
Thanks, mate. BTW, you wanna beta-test? :)
-
apparently it was a problem of several circumstances.
1- bad compilation. recompilation done <- just repaired the sampler module problem.
2- the construction of the project with the settings and scripts of the 1.1.1, some of which have changed on 1.2.2: therefore incompatible.
3- presets made with 1.1.1 not compatible with 1.1.2 new settings. if used with new VST/project -> error/bug/crash/ shot down in flame.the samples are not in question because I just tested them in a new project created only with the version 1.1.2 recompiled and it works.
I think I'll have to start the project from the beginning (from scratch), not update it.
and again with that I'm not sure to solve the problem.seems that you changed the LFO speed steps, also same thing for arpeggiator, and few minor things in many modules. if using all of that in project, it must be redone, not updated.
I will try and keep you informed.
-
Yes, sounds fun
-
Wow, I'm looking forward to Friday!
P.S. Christoph Hart, I am sending you a message!
-
ok:
found problem with:-
background images (in OnInit because created with 1.1.1 and duplicated in UI JSON DATA with 1.1.2) -> so that create problem with vst.
-
presets problem (i already wrote this before) -> i must recreate it.
-
GUI size -> If i chosse height larger than 700+40 (708 or 710+40) -> vst crash/Daw freeze at vst analysis. So i kept 700+40.
-
last thing that everybody knows but me -> before compiling again = erase all folders in Binaries. i just erased the compiled folder. So made conflict.
for now, without new presets, it works (updated version from 1.1.1 with modified settings of new functions)
of course will test it again before saying "problem solved" until finished.
-
-
First off, I realize it's been a while since I've been using this software, and I'm starting to get myself back into it, now.
That being said, I'm also having issues with building HISE from the current source, even if hopefully because I currently have to use the minimum required Mac version (10.7). My errors, however, have to do with the linking of the universal binaries after compiling the source code. Something about the HISE binary data (i.e. icons) in all cases.
As it is, now, I've only changed three things within the source code for my own purposes:
-
disabled IPP, which is necessary if it's not installed, anyway.
-
changed the interpolation method for sample playback, which I confirmed in a build I have saved of 1.0.0 works.
-
edited "juce_AudioPluginInstance.h" by omitting one of its protected functions, which, for the 1.0.0 build, was somehow necessary to compile correctly on this particular OS version.
I even tried reverting the sample interpolation method to see if that was the problem, but, for better or for worse, it wasn't.
Any thoughts? I can provide an image showing the errors if necessary.
UPDATE: still haven’t figured out a fix, but I WAS able to diagnose a bit further: it appears that the problematic binary data is that which is referenced in the source code as binary data outside the modules in a simply-named BinaryData namespace. Unfortunately, attempts to merge the binary data with the modules also proved fruitless, leading me to believe it has something to do with either how that particular data is called, or the possibility that the data itself is corrupted somehow.
UPDATE #2: managed to temporarily fix it by adding the BinaryData namespace contents to the module namespaces. I would still advise it be looked into for the sake of those who are neither tech saavy nor resilient.
-
-
going to the news:
repared all that i wrote before. result:
-
studio one: OK
-
reaper: Ok
-
Ableton Live : ok BUT if you first launch (creating the folder in c/users/appdata/etc...) with Live. if you first launch in another daw and after opening Live : Bug !
-
Sonar & bitwig: NO ! do what you want boy, but we only accept the 1.1.1 version !
difference beetween 1.1.1 & 1.1.2 version , (instead of updated modules settings) = the script from "musicbox" with the settings, tooltips,presets and samples menus. In 1.1.1, in the VST versions the setting menu disapear. In 1.1.2 this menu is visible; but seems to create problems with some DAWs.
Some scripts in the SettingButton.js that 1.1.2/ VST version is not supported by this ones.
not tested other DAWS (reason, cubase, etc. ...)
-
