One Synth Challenge #99: vst2413 by Keijiro Takahashi (J.Ruegg wins!)

[Frostline]

Ok, here's a quick fix for vst2413s (Win 64), allowing to copy instances while keeping parameters!

Oh I had such high hopes for this when I saw it.

Popped it into Reaper (after deleting the 3 previous versions of VST2413), and sadly it exhibits the same behavior when playing keyboard as the original. But did get the added bonus of piano roll not working and hung my soundcard to the point where system reboot was required to get the sound to stop (even after Reaper crashed).

I also tried this version in Lumit x64 (only other DAW I had on hand) and it exhibits the same behavior as Reaper when the note pressed and released does not stop and next pressed note just adds to the sound already playing. The piano roll there worked, though adjusting a few of the parameters to change the synth had little effects on the sound. But to be fair I don't have a firm grasp on how Lumit works so I could have been doing it incorrectly.

I may download the demo of MU-Lab and give that a go though I don't have high expectations of understanding how it works either But would be interesting to see if the VSTi will work in something on my PC.

I think there is just something about my particular system that is not VST2413 compatible. But I do appreciate Taron's effort and hopefully their 64-bit build of this will help others.

[Taron]

FASTEN YOUR SEAT BELTS, PLEASE!
I have managed to make my very first MAC compile!!! It was NOT easy by any freaking means and there are some fundamental unknowns for me about this machine, but- nonetheless- I have managed to make a working compile!

MAKE SURE YOU DELETE the original vst2413s from your vst folder and your DAW won't even try to find it anymore before you add or replace the attached one!

OMG...I can't believe it.

[Taron]

One thing I noticed with the original version as well as my current compile, is that holding too many notes will make the plugin fail. Beware of that, while I may go in there and try find the issue. There are a few things questionable in this code, while I'm kind of smiling about it, too, hehehe..."finally I can see what's wrong!!!". YAY!

[J.Ruegg]

Ok, here's a quick fix for vst2413s (Win 64), allowing to copy instances while keeping parameters!

Wonderful! - This also fixes the issue on reloading project. Thanks

Wow, I will try it later, I was having the same problems as richard in mulab.
Thank you Taron

[zerofox97]

https://soundcloud.com/zerothefox/vst24 ... pt/s-p19sm
This synth definitely can't do plucks, but hey, I tried.

[rghvdberg]

Ok, here's a quick fix for vst2413s (Win 64), allowing to copy instances while keeping parameters!

have you altered the source code ?
if so please do a pull request on github so others can profit from your code

how is this synth licensed btw ?

[Taron]

Good idea, I just have never done that, plus I might still modify stuff. I found part of the problem with the polyphony bug, but it gets a little convoluted after that and needs some more careful examination. However, I managed to avoid that potential crash "a little bit". There are factors that still get corrupted and those I have to track down. Not like it's my job, hahaha, but it's a fantastic exercise. Plus: I did my first mac compile!!!!!!

So, yeah, I will check into the pull request thing...thanks for the tip!
(On top of that, there are a few mistakes in the original code of the "p" version, which I'm not too keen on working out, so that's a potential issue... not sure. )

[doctorbob]

Hi Taron!!! Well done bug fixing/chasing ... any chance of making 32-bit winblows versions as well as 64-bit ones? I still run 32-bit Reaper on my 7 year old box - oh so many 32-bit plugins which I use all the time. The system is so stable I just don't want to mess at all.

[Yeah, I know I must go 64-bit all the way, but that will only happen when I get a new machine]

Cheers,

dB

PS I do appreciate you having a go - I know what bug hunting other peoples' code it like - used to hack around lots of raw X-Windows code (a nightmare!) working with the guys at Brown Uni - working on a X-Multiplexor - called XMX in those days.

[Taron]

Look up!
...I've posted the 32bit version already!

[doctorbob]

Look up!
...I've posted the 32bit version already!

ooooooooooopppps - missed that - serves me right for jumping to the end of the postings - sorry man!

Grabbing them now!

dB

[Taron]

I've updated the mac zip up there, locking it to program 0. I found out that without this lock it will crash under certain circumstances. My plan was to add banks as well, but I figure it's too much, really.

[Scrubbing Monkeys]

I've updated the mac zip up there, locking it to program 0. I found out that without this lock it will crash under certain circumstances. My plan was to add banks as well, but I figure it's too much, really.

What planet do you come from sir?....Seriously. It's like I am watching a grey matter Superman in real life.

[Taron]

Wehehell, you haven't seen my most outstanding physique, yet! And neither have I...in decades!

[generaldiomedes]

No idea, general, why it wouldn't show up. Make sure you have no other version interfering. I assume, Studio One will try to scan your vst folder?! So, yeah, make sure you're doing everything right first! And be sure it brings up a generic GUI, since this plugin has no own GUI!

Hmm, I made a copy of the .DLL in the same directory and called it vst2413_2.dll and that one showed up.

I think it is because I had the 32-bit version in another folder that Studio One had in the VST path, so it looks like another version was interfering.

thanks for doing the 64-bit version!

[zerofox97]

In all honesty, I don't know what I'm going to do with this synth, but I will persevere