KVR Audio

jdt · Post by **jdt** » Fri Sep 07, 2012 10:20 pm

Sweet Synth! GUI looks good here in FL Studio. The Arpeggiator in FL's Channel Settings opened up some interesting possibilities right away. Nice presets, Max!

Mac of BIOnighT · Post by **Mac of BIOnighT** » Fri Sep 07, 2012 10:39 pm

cymazic wrote: Keenly anticipating this download to finish , thanks again for the kind freebie
Maz

Very kind of you, thank you very much indeed

Hope you won't be disappointed

JDT, play around with the controls, it's a lot of fun!

Max - no hurry

MaxSynths · Post by **MaxSynths** » Sat Sep 08, 2012 12:02 am

@jdt: thank you, glad you like it

@Mac: si si pian pianino...

edison_carter · Post by **edison_carter** » Sat Dec 01, 2012 11:13 pm

hmm. Can't seem to get free version to detect in Reaper (x64). Haven't tried 32bit, tho, as I always use 64. Multiple detection attempts (forcing from the preferences, or restarting Reaper), no dice.

fyi!

MaxSynths · Post by **MaxSynths** » Sat Dec 01, 2012 11:30 pm

@edison_carter: Latte currently is a 32bit plugin, maybe is this the problem? Do you have problems with other 32 bit plugins?

edison_carter · Post by **edison_carter** » Sun Dec 02, 2012 12:37 am

MaxSynths wrote:@edison_carter: Latte currently is a 32bit plugin, maybe is this the problem? Do you have problems with other 32 bit plugins?

Not really. I mean, Reaper uses a 32-bit bridging scheme that works pretty well for me 95% of the time... you can generally easily use 32-bit plugs in 64-bit Reaper. There are some 32-bit plugs that just barely work or make the DAW crash, but very few that I own. What's weird about this one is, Reaper doesn't even detect it on the plugin scan. Usually, even plugs that end up not working for me when I instantiate them, are at least detected.

I also tried moving the lattefree.dll around to see if that mattered; that is, I had it originally in the LatteFree folder in my vstplugins directory, then I tried taking it out of the LatteFree folder and putting it in the root of the vstplugins directory. Nope.

MaxSynths · Post by **MaxSynths** » Sun Dec 02, 2012 12:38 am

This is weird

I try to figure out what's going on and I let you know...

edison_carter · Post by **edison_carter** » Thu Dec 06, 2012 3:42 am

MaxSynths wrote:This is weird I try to figure out what's going on and I let you know...

please do! I would love to try it out - and polyphonic AT! Woohoo!

thx!

MaxSynths · Post by **MaxSynths** » Thu Dec 06, 2012 10:50 pm

edison_carter wrote:
MaxSynths wrote:This is weird I try to figure out what's going on and I let you know...
please do! I would love to try it out - and polyphonic AT! Woohoo!

thx!

Didn't found a solution yet... I'll send a mail to Reaper's developer.
Can you send me a PM with your system specifications please (CPU, OS and RAM)?

Cheers,
Max

MaxSynths · Post by **MaxSynths** » Thu Dec 06, 2012 11:26 pm

Mail sent to Cockos

MaxSynths · Post by **MaxSynths** » Fri Dec 07, 2012 7:30 pm

@Edison: Justin from Cockos replied to my mail.
This is his reply, try to follow these suggestions and let me know if this solve the problem. Also it would be of some help if you can test with the 32 bit version of Reaper.

Do you know if the 32-bit version of REAPER works with that plug-in on that machine? It is possible that some other library (such as a particular version of the MSVC runtime) is not present on the machine, and if that was the case the 32-bit version of REAPER would also not load the plug-in.

The user should also clear the VST plug-in cache in REAPER (remove the relevant line in reaper-vstplugins.ini or reaper-vstplugins64.ini, or clear it within REAPER) when testing this.

edison_carter · Post by **edison_carter** » Sat Dec 08, 2012 1:12 am

MaxSynths wrote:@Edison: Justin from Cockos replied to my mail.
This is his reply, try to follow these suggestions and let me know if this solve the problem. Also it would be of some help if you can test with the 32 bit version of Reaper.

Do you know if the 32-bit version of REAPER works with that plug-in on that machine? It is possible that some other library (such as a particular version of the MSVC runtime) is not present on the machine, and if that was the case the 32-bit version of REAPER would also not load the plug-in.

The user should also clear the VST plug-in cache in REAPER (remove the relevant line in reaper-vstplugins.ini or reaper-vstplugins64.ini, or clear it within REAPER) when testing this.

Hm. I have not tried 32-bit Reaper, I just always use 64. I'll give 32 a whirl and see what happens, for testing purposes, but if it only worked in 32, it's unlikely I'd use it. : ) Also: I've cleared the plug-in cache a bunch of times, did multiple system and host reboots/restarts(even though you shouldn't need to do that - Reaper is designed so you can scan in new plugins that are deposited in your VST folder even without restarting the host, woo!)

thx again

e

edison_carter · Post by **edison_carter** » Sat Dec 08, 2012 6:48 pm

edison_carter wrote:
MaxSynths wrote:@Edison: Justin from Cockos replied to my mail.
This is his reply, try to follow these suggestions and let me know if this solve the problem. Also it would be of some help if you can test with the 32 bit version of Reaper.

Do you know if the 32-bit version of REAPER works with that plug-in on that machine? It is possible that some other library (such as a particular version of the MSVC runtime) is not present on the machine, and if that was the case the 32-bit version of REAPER would also not load the plug-in.

The user should also clear the VST plug-in cache in REAPER (remove the relevant line in reaper-vstplugins.ini or reaper-vstplugins64.ini, or clear it within REAPER) when testing this.

Ok - did some testing. I installed newest Reaper 32-bit (4.31), and I was able to get it to detect Latte, and it worked a-ok. However, in 64bit, there's still no reference to it anywhere in the reaper-vstplugins64.ini file, even after forcing a plugin redetection. Since I'm not an expert on how the 32-bit bridging host work in 64bit Reaper, you'd have to ask Justin again.

thx!

MaxSynths · Post by **MaxSynths** » Sat Dec 08, 2012 9:49 pm

Thank you very much Edison for testing with the 32 bit version! I think this is an important clue

Let's see what Justin have to say (stay tuned

)

Cheers,
Max

EDIT: if you have some spare time do you mind to try with my other synths (you can find the demos on my site) and see if they are detected? It would be very strange if this issue only happens with Latte, since my recent plugins (Crisalys, WTS-1 and some of the freebies) has been developed with the same version of SE.

BTW I strongly suspect the problem is on the Reaper side

MaxSynths · Post by **MaxSynths** » Sun Dec 09, 2012 2:29 am

Mmmmm I got this reply from Justin:

If their reaper-vstplugins64.ini file does not reference the DLL name, it is likely that the 64 bit version of REAPER is not configured to scan a folder which contains that DLL...

Now, I'm sure you are doing everything in the right way, BTW I have to ask you if you are sure that Reaper is scanning the right folder (Ok ok, don't shot me

).

Ok let's try something different. Can someone else with a 64bit system give a quick test with the latest version of Reaper, please?? (Scott are you there?

)

Latte VSTi (free version available)