About RT...
-
@d-healey said in About Rule Tec:
I'm assuming he is using images at 200% resolution so they will display well on everything from 4K down to 1K screens. But almost certainly the images could be optimized.
Yes @d-healey the size of the images is very big, and designed for 4K monitors. Also as Christoph said, even the images are compressed, on compiled plugins the images become very big bitmap files. so that's why if your image sizes are even under 50MB (this is the image size limit of HISE), your compiled plugin can be much more bigger.
-
@orange wow, did you just ask me to leave the forum ?
What a lovely attitude ?
You neither tell me to use the forum or use HISE or not, and I will post any opinions i have in this PUBLIC forum, if YOU dont want comments, do not post. -
@Win-Conway said in About Rule Tec:
@orange wow, did you just ask me to leave the forum ?
What a lovely attitude ?
You neither tell me to use the forum or use HISE or not, and I will post any opinions i have in this PUBLIC forum, if YOU dont want comments, do not post.No, I didn't say leave forum. It's none of my business. I just said if you don't like or don't want, then just don't, simple. In your vision, that's a comment too :D
-
Guys calm down, it‘s not the KVR forum here ;)
-
@Win-Conway said in About Rule Tec:
HISE should be treated the same as any other development platform, Christoph gets paid as he asks to get paid, or do you also ask that Jules is mentioned or JUCE or C++ or Javascript, no of course not, so asking for HISE to be mentioned actually denigrates it to Synthedit and Synthmaker level in the eyes of some.
I'm almost publishing some of my vsts and I have no problem no only mentioning HISE but even embedding a link to hise website within the plug-in itself. But is up to the developer to mention it or not, I will because I bother too much sometimes with questions, I bother @Christoph-Hart and @d-healey and now @orange too.
-
@Christoph-Hart
Well yeah, KVR has a lot of users, and i would suggest with attitudes like the above, not to post there, eaten alive springs to mind hahaha.
@Jay
All i did was ask if it was mandatory, its not, that's cool, also very cool that you will, personally I will not overtly mention HISE, I think it is disrespectful to HISE (My opinion, not trying to tell anybody else what to do) I intend to push HISE through promotion of HISE itself ;) -
-
...anyway.....back to Rule Tec.....
I'm intrigued how this "modeling" was done... - clearly the specifics of the model params are Orange's IP so I'm not asking for that, but I cant see where I would start to build a model-based audio processor in HISE, any clues?
HISE Development for hire.
www.channelrobot.com -
@Lindon There are many ways to do this.
One way is circuit modeling (Analog Obsession does it). But it is hard to do with Hise and requires extra C++ work.
The second way is non linear IR technology (Acoustica Audio does that) and Hise doesn't support that too.
The third way is measuring (vintage way). In order to do it, you need original machine. The Basically what I did is measuring and recording the original machine's parameter data step by step. (I recoreded a huge data and prepared a big data table for that.) And then I matematically modeled with equations (approx. 2000 interactive equations) to achieve this results. Then tell the Hise how to do that.
-
@orange yeah its that last bit "then tell Hise how to do that" - you did it in javascript? and changed what EQ? Gain?
HISE Development for hire.
www.channelrobot.com -
@Lindon Custom C++ module or script FX perhaps...
-
@d-healey nearly everything can be done by adjusting gain (EQ, Volume) and saturation, I have worked with a bunch of well respected developers whose models are just comparitive volume and distortion, but dont for one moment think that is easy, it takes a lot of intricate measurements.
-
@Lindon said in About Rule Tec:
@orange yeah its that last bit "then tell Hise how to do that" - you did it in javascript? and changed what EQ? Gain?
@d-healey said in About Rule Tec:
@Lindon Custom C++ module or script FX perhaps...
Yeah hybrid solution with Custom C++ module and Hise script fx.
The hardest thing about Pultec and bunch of other analog hardware is all of the parameters are interactive and non-linear. For example in Pultec, Low Atten knob doesn't react the same if the low boost is there, so that is a total pain for modeling. You can make only individual controls but the plugin won't sound like original machine. Or same with high boost and atten. You need to measure lot's of values, bring them together and make mathematically modeling.
Hise is capable of much more than what people think. Not only for vsti. Wait for hnode.... @Christoph-Hart
-
@orange What do I have to enable or add in my vst to add the (host automation)?
Like when you touch a knob in the plugin, the DAW knows what knob it is
-
@Jay
Adjust this settings in the knob/button that will be automated
"isPluginParameter": Enabled
"pluginParameterName": Your parameter name that will be displayed in the daw automation (Gain, freq, treshold....etc) -
@orange thanks again buddy
-
Bought it. Lovely EQ!
-
-
Just bumping this for two reasons, 1 it is pretty much the nost notable release from HISEin terms of industry coverage and adulation, 2 it shows that HISE is a real powerhouse for effects and we really need that VSTfx (an fx version of the vst to design in) build for developing too.
-
@Win-Conway Yeah definately.
I wish @Christoph-Hart could make improvements and remove the issues for fx plugins that was previously mentioned before.
