Can't play after update v3.066

[mm103]

I updated sylenth1 to v3.066, but there are just short attack sounds when I play it. I changed decay, sustain and release, but doesn't work. How can I solve the problem? or Can I download the previous version of sylenth1?

[surreal]

Following. ..

[Lennard]

What OS and DAW software are you using exactly? Does this also happen when you create a new empty project and add an instance of Sylenth1? Or only when you load a certain project? Does it happen with all presets or just some in particular? What if you turn off all effects in Sylenth1?

[mm103]

OS: macOS 10.14.6
DAW: Ableton Live 10.1.7

>Does this also happen when you create a new empty project and add an instance of Sylenth1? Or only when you load a certain project?
Yes, It happens with both situations.

>Does it happen with all presets or just some in particular?
All presets.

>What if you turn off all effects in Sylenth1?
I turned off all effects but nothing changed.


I tried VST and AU, but some consequence.

[Lennard]

Strange, it does the same for both VST and AU versions?
Can you maybe create a new empty project, add 1 instance of Sylenth1, put a few notes in a midi clip and export the output to wav, then send both the project and wav file to support(at)lennardigital.com ?

[mm103]

OK! I'll send you those files.

Thanks.

[Lennard]

Update on this issue: We found that the problem was not in Sylenth1. One of his midi inputs was messing things up, possibly continuously sending AllSoundOff messages that would turn off the sound. When changing his midi input from 'All Ins' to a single midi device the problem was gone.

I'm still interested to find out which midi input was causing this and what exactly it was sending. So if you can use a midi monitor to log the midi data sent, that would be useful!

[e-crooner]

Good to hear it was not S1's fault

(I like the new copy options. I think when selecting the Link amp env A and B option, that should automatically execute the copy to the other amp env option before linking them, else the other amp env might retain the wrong values when the A, D, S or R slider is not moved.)

[HansR83]

I have the exact same issues in Ableton and Logic Pro X. Studio One 4.6 is working fine.
I made a quick video about it, hopefully it's helpfull:

[Lennard]

I have the exact same issues in Ableton and Logic Pro X. Studio One 4.6 is working fine.
I made a quick video about it, hopefully it's helpfull:

I moved your post to the correct topic to avoid confusion. So please try changing your "Midi From" input for that channel from "All Ins" to your preferred midi input. That should fix it.

I'm quite curious though what exactly is causing this, so if either of you can find out which midi input is causing this and what it is sending exactly, please let me know.

[HansR83]

I have the exact same issues in Ableton and Logic Pro X. Studio One 4.6 is working fine.
I made a quick video about it, hopefully it's helpfull:

I moved your post to the correct topic to avoid confusion. So please try changing your "Midi From" input for that channel from "All Ins" to your preferred midi input. That should fix it.

I'm quite curious though what exactly is causing this, so if either of you can find out which midi input is causing this and what it is sending exactly, please let me know.

Thanks, I will try it tonight and let you know.

[HansR83]

I have the exact same issues in Ableton and Logic Pro X. Studio One 4.6 is working fine.
I made a quick video about it, hopefully it's helpfull:

I moved your post to the correct topic to avoid confusion. So please try changing your "Midi From" input for that channel from "All Ins" to your preferred midi input. That should fix it.

I'm quite curious though what exactly is causing this, so if either of you can find out which midi input is causing this and what it is sending exactly, please let me know.

You are right, changing the midi input to a single controller 'solved' the problem.

[e-crooner]

So, if it's not a S1 problem, nor a DAW problem, is it an Apple OS problem?