@MIDIculous said in .hr1 and .hr3 Files Opening:
I'm finding that Keka is no longer compatible with the Winrar format and yields tons of errors.
yes.
zip is better.
for example with wordpress sometimes we have problems with rar files. Never with .zip files.
pretty sure we ABSOLUTLY don't understand each other.
When finished compiling your soft (standalone .exe, component, app, etc....) and samples (HR1) you can:
1- put all in one folder and compress it (rar and/or zip).
2- create an app + a samples folders and compress then (2x zip or 2xrar).
I absolutly not telling about compressing the raw samples and samplemaps. But final product.
as i said before some formats are not supported by web browser and/or wordpress. I forgot to mention .exe files.
Wordpress hate .exe file. So we must compress in .zip and/or .rar to upload them.
the best way to avoid conflit beetween browser, platform and product is to compress it.
Don't forget to talk about the conflict beetween PC, mac and linux format and the way that browser "read" them.
And most of time if you put to download an .exe file the security software will warning. Not with compressed files. Sames for other formats (as hr1)
@Christoph-Hart
compress in rar is just for download purpose After that they decompress to have the hr file.
mainly of system (wordpress for example) hate direct .wav and other formats. But when compressed in .zip/.rar all is fine for customers 
compress (zip or rar) your hr-x files and you won't have weird issue with firefox
i confirm
the name used to save the .xml file depend/change the master container name and project. Vice versa.
But not change the project name in the properties/settings.
My old projects had sometimes different names beetween settings/description, master container, project and saved .xml. Now: All must have the same name (except description).
always told on old thread. Take a look at the samplerate.
when i use "old" vintage samples (from emulator, fairlight, linndrum, etc. ...) set to 30/33 khz you ear pitched sound when converted to monolith. 22/44/48/96 khz it's ok.
@remarkablex
Yes.
for rendering engines it is a matter of taste. None is better. they will all photorealistic rendering if you set them well.
for DAWs it's the same. Here in France FL studio is considered a DAW for children, Studio One a DAW for amateurs (who do not compose the "good" music because on Studio One). It makes me laugh to read all this on the internet.
We even go (in France) to criticize Win10 - claimed as shit - against Win 7.
I had a grandmother who cooked with old, old-fashioned pans. But she was making food as never before I had my meal (my madeleine de Proust).
Then yes. everything is a matter of taste. As for this FX Noiseash, which looks like many other plugin recreating the Puigtec already. Yes, it's true. But there are some we like to use, others not.
So I will test it, and it's not impossible that I prefer this one to others.
Basically, I create my own VST to feel more comfortable with a device, which already exists, created by other companies; But my version I know, so I master it better.
So to finish this very long text: HDRI studio rig is just an example, you're right Remarkablex, if you prefer Octane and you master it better, then continue with. In any case the rendering you made on this plugin is just ... Woaow! 
same soft: C4D, but after trying Arnold and Octane, i use now HDRI studio Rig:
https://greyscalegorilla.com/downloads/hdri-studio-rig/
powerful photorealistic render more faster tha Arnold and Octane (and you have not to "convert" materials and textures as with A & O).
Really nice GUI. didn't tried yet the FX.
Synthedit is not the only one to do that.
Arturia too (their images and settings files are outside the plugin - in appdata or other), but they use JUCE.
U-HE too, but I do not know how they code their plugins.
I do not know if it's a security issue, but I notice that often these plugins are more "heavy" and CPU hog.
May be unrelated to this, but I notice it here ...
Personally I'm not for unless you want to allow your users to create custom skins for your plugins. Your GUI is yours. Leaving it outside allows everyone to recover and do what they want.
Strange answer, but:
Your errors are maybe not the REAL error.
i explain:
did you use the "old" filter in global FX ?
i had something like that before.
for now Christoph had re-added filter in global FX, but called "polyphonic" filter. The old one was "monophonic".
So you must rename your FX inside the .xml preset, changing "mono" by "poly", save, and reopen your old 1.6 project in 2.0 and ...voilà ... All "strange" errors are gone 
yes i know this error is about filter; but in my old 1.6 files the errors was all other, but never written : "your filter cause error", a lot of another errors (in fact, all FX and codes after the "filter" section in fact.)
you can compile...