LennarDigital

kaverka · Post by **kaverka** » Wed Mar 14, 2007 7:46 pm

Not sure how I missed this in my testing, or even if Lennard considers this a bug. It may just be intended behavior, or it could be a strange combination of Live 6 and Sylenth 1.20.1. Please confirm:

1) Using Live 6.05 create a new project. Load Sylenth into a track.

2) Change patch to anything greater than 001

3) Record some MIDI

4) Save project, quit Live

5) Reload Live, reload project

6) Patch number in Sylenth interface is "001" when it should read something different, whatever you set it to in step 2

7) Play back project... the correct patch is playing, but Sylenth still shows Program Select < 001 >

Question: shouldn't the program select display the correct patch number? If you click the > button then it increments to < 002 > not to the correct next patch. It's clear that the patch number is not synced up when the project is loaded, even thought the sound seems to be.

This is minor (nothing like the issue in ACID 6.0d) but still annoying. Is this related to Synthedit again? Any possible fix on the horizon?

By the way, this does not happen with other plugins I use... their interfaces update with the proper patch name/number.

kaverka · Post by **kaverka** » Wed Mar 14, 2007 8:03 pm

Update: this same thing also happens in Sonar.

Lennard · Post by **Lennard** » Wed Mar 14, 2007 10:24 pm

Ah yes, this is too a shortcoming of SynthEdit. The new version will fix this problem too and will also allow displaying patch names.

kaverka · Post by **kaverka** » Wed Mar 14, 2007 11:25 pm

I think you've got a good case now for completely getting rid of SynthEdit asap...

I know you have your reasons, but let's face it, do you want to hold yourself hostage to the SynthEdit guy any more? I know you want to change things, and in the shorter term, he will *eventually* release an update, but I think it's pretty clear that a plugin of your quality and price should star far, far away from SynthEdit. Just my opinion as a paying customer.

Lennard · Post by **Lennard** » Thu Mar 15, 2007 12:10 am

I know, and that's exactly what I'm going to do. But you have to understand that one can not rebuild a big synth interface like this in just a few weeks, including full parameter/midi automation, a new voicemanagement system, new preset handling, compatibility with current presets and compatibility for Mac systems. This is a simply lot of work and thus needs time unfortunately.

So that's why I will update Sylenth1 when the new version of SE comes out, so the gapping and preset handling will be fixed. I will then continue to rebuild Sylenth1 without SE, which by the way might be called Sylenth2

kaverka · Post by **kaverka** » Thu Mar 15, 2007 12:55 am

I'm with you and I completely understand your reasoning. I'll happily buy the upgrade to Sylenth 2. I'll even PRE-pay, if that makes things go faster.

These SynthEdit drawbacks are annoying as you know... and the sooner we can get rid of them the better. Maybe you can knock on the SynthEdit guy's door to get him to finish up sooner. Hopefully, he won't cause new bugs to be introduced....

adl · Post by **adl** » Fri Mar 16, 2007 7:31 pm

To lazy to check

This problem still there?

Thanx!

Lennard · Post by **Lennard** » Sun Mar 18, 2007 3:09 am

There haven't been any updates this week, so yes..

But I think it would be best simply try the demo to see if it occurs on your DAW.

nrosko · Post by **nrosko** » Tue Mar 20, 2007 4:32 am

I have a problem with it saving presets in that the next time it loads it has the appregio selected. I'm using live6 as well.

Lennard · Post by **Lennard** » Tue Mar 20, 2007 6:37 am

nrosko wrote:I have a problem with it saving presets in that the next time it loads it has the appregio selected. I'm using live6 as well.

Sounds like you are loading presets (or tracks) that were saved with an older version of Sylenth1 (prior 1.20). In that case the arpeggiator and the chorus effect may be switched on at random. To fix this, simply save the preset(s) again with v1.20.

Let me know if that fixes the problem.

waveriderarts · Post by **waveriderarts** » Tue Mar 20, 2007 12:46 pm

Lennard wrote:I know, and that's exactly what I'm going to do. But you have to understand that one can not rebuild a big synth interface like this in just a few weeks, including full parameter/midi automation, a new voicemanagement system, new preset handling, compatibility with current presets and compatibility for Mac systems. This is a simply lot of work and thus needs time unfortunately.

So that's why I will update Sylenth1 when the new version of SE comes out, so the gapping and preset handling will be fixed. I will then continue to rebuild Sylenth1 without SE, which by the way might be called Sylenth2

hello,

there is a problem with the new update, it is that the parameters list is not the same than with the previous version. If I had a knob or a curve assigned then it may be than with the newer version it won't animate the same parameter. It is not 100% compatible so songs may load but play back differently. All that while having the same name for the plug makes it difficult to preserve compatibility of my repertoire. PLEASE TRY to avoid such situations in the future. Thanks.

... I would really love to be able to midi map some modulation but midi learn don't seem to work on those knobs.

...and as modulations destinations I would like to see other slots as possible choices

Lennard · Post by **Lennard** » Tue Mar 20, 2007 5:23 pm

Yes, I'm sorry for that, but it was necessary to break compatibility because there were new parameters added to the list (from the chorus and the arp). I've renamed most of them so that the most important parameters would all appear in the first 128 slots in the list. This was necessary for easy access in Live.

Midi learn for all knobs will be available in a future update.

waveriderarts · Post by **waveriderarts** » Thu Mar 22, 2007 3:45 pm

Lennard wrote:Yes, I'm sorry for that, but it was necessary to break compatibility because there were new parameters added to the list

well sir, I am swamped in such compatibility issues right now trying to render songs that were made in the earlier version. This is not to be taken lightly.

You breached my trust in you right there... you KNEW it, you should have warned us before install, or rename the dll with a version number or whatever! it is your job as a developper to keep things smooth for us users ok???? more so because you are trying to pretend to be your part of the major league as a developper... well most freeware devs avoid such issues why can't you!!!!!!

EDIT:
I know you said you are sorry, but you did not do anything prior the release to mitigate those problems, but maybe publishing a chart were param X in the new version means param Y of the previous version could help? or issuing a new dll with a different name?

Lennard · Post by **Lennard** » Thu Mar 22, 2007 4:00 pm

Like I said, it was simply unavoidable to change those names. The way they are listed now is way more accessible and way better for future compatibility.

You can still manually change the parameter links in your host though. Or if that is a problem or too much work, you can still run the previous version of Sylenth1 next to the new version. To do so, simply rename the new version to Sylenth12.dll and its accompanying directory to \Sylenth12\. Then install the previous version again (if you don't have the installer anymore, just let me know).

Lennard · Post by **Lennard** » Thu Mar 22, 2007 4:10 pm

waveriderarts wrote:but maybe publishing a chart were param X in the new version means param Y of the previous version could help?

Ok, I'll make such a chart soon.

LennarDigital

KVR Audio

Possible minor issue with Sylenth and Live 6? Please confirm