NKS library image for 32bit Vst

67maxx

Hi all,

I make NKS libraries for myself, especially for having a better browser of the presets.

I am trying to do this with 32bit Vst and the presets are working well (even with some glitch sometimes).

The only problem is that I cannot manage the images. I can make them work with the 64bit Vsts, but they don't show up with the 32bit Vsts.

What I am doing wrong please?

TIA

I own a Mk2 keyboard and I use Windows 10

I forgot to say that I use JBridge for the 32bit Vsts

Max

PoorFellow

https://community.native-instruments.com/discussion/28033/nks-library-image-for-32bit-vst

Someone else used JBridge over here and the output is uploaded here , I don't know if any of that is of any actual help but apart from standard information such as here and here then it is all that I could come up with !

PoorFellow

https://community.native-instruments.com/discussion/28033/nks-library-image-for-32bit-vst

Someone else used JBridge over here and the output is uploaded here , I don't know if any of that is of any actual help but apart from standard information such as here and here then it is all that I could come up with !

Vocalpoint

https://community.native-instruments.com/discussion/28033/nks-library-image-for-32bit-vst

Why are you bothering with 32bit VSTs when that format is not even supported by NI any longer

Would also love to know what 32bit VSTs you are working with?

I guess I am not understanding the end game here?

VP

67maxx

https://community.native-instruments.com/discussion/comment/142646#Comment_142646

There are still beautiful 32bit Vst. HG Fortune made lots of free synths with amazing sounds.

About the supporting, there are some synths no more supported, but still usable. One is from NI, AbSynth5 which I was lucky enough to buy just before it disappear. Should I stop using it because is no more supported?

So, the end game is, in my opinion, that everyone has different tastes, some people like the new stuff, other the old one and others both of them :)

67maxx

https://community.native-instruments.com/discussion/comment/142642#Comment_142642

Thank you very much PoorFellow, I'll check it out (especially the SQ8L) and I'll let you know if I succeed :)

Vocalpoint

https://community.native-instruments.com/discussion/comment/142651#Comment_142651

Not disagreeing with you at all.

It's more about the fact that none of today's modern DAWs support 32bit VST anymore so what exactly is the point?

And Absynth is poor example. Not only is it not 32 bit - it will only be usable as long as NI says it is. Once it can no longer be activated - that will be the end of Absynth.

Continued success.

VP

PoorFellow

https://community.native-instruments.com/discussion/comment/142652#Comment_142652

Best of luck ! 🙂

And incidentally then while I do think that Vocalpoint got a very valid point with respect to the 32 bit versus 64 bit then I also think that you should do what you like to do and learn all that you can from that and then if you want then move on from there.

And while I will probably never return to this then I myself still 'dream' about doing stuff with 8 bit and 16 bit computers that I got stashed away and to continue assembly language programming of same (I abandoned some of that because of living in the wrong country so that I couldn't get sufficient documentation at the time). You can acquire quite a lot of knowledge from working with 'outdated' stuff , however a lot of what you learn will not be valid for the new things. On the other hand then 'development' is going so fast that no matter what you learn soon will require serious updating... Programming language wise then it's best to lean some dialect of something that looks as if it will be of use in the future !

In the end , if you learn something that you can use elsewhere and you have a good time or if you just have a good time with something like that then : Have fun ! 😀

67maxx

https://community.native-instruments.com/discussion/comment/142683#Comment_142683

Thank you PoorFellow :D

and you know what?

Thanks to you I finally got the solution after more than a year of tests and research.

I am not a programmer, but I really like to learn and problem solving.

BTW, the solution was in the "read me" in the SQL8 NKS library:

"In addition, you must also edit EVERY preset in Maschine browser to reflect [jbridge]SQ8L as the VENDOR."

Ok, it is not Maschine, but MK2 :P

Now everything is working! :D

You cannot believe how happy I am now lol, thank you very much :D

Kymeia

"In addition, you must also edit EVERY preset in Maschine browser to reflect [jbridge]SQ8L as the VENDOR."

It really should make it clear you can do that all at once, I can imagine some poor soul trying to do it one by one

67maxx

https://community.native-instruments.com/discussion/comment/142710#Comment_142710

The read me actually says that. I forgot to add it, sorry

BIF

I have been wanting to leave 32 bit since about 15+ years ago when mainframe computers were doing it. But the weird thing there is that mainframes had 31 bit code (yes, 31 bit), and then went to 64 bit, along with another thing called "unicode". Unicode was the magic potion that allowed mainframes to take on any real or imagined language characters, even those that would require double-byte character sets such as Kanji. Unicode would work natively with any mainframe database, so if you wanted to manage a relational database of drug names in Romulan, you probably could. Just find the code page number for Romulan, plug it in, and you're on your way.

For example: Code page 775 (CCSID 775) is a code page used to write the Estonian, Lithuanian and Latvian languages.

Yeah, I've been a geek for a long time. Still trying to recover. Meetings every Tuesday, lol!

Oh, and as far as I can tell, Romulan, Klingon, and Vulcan are not available in Unicode. Imagine my disappointment!