@Paul said:

Hello, 

FL1_perf_leg_sustain fades into sustained/looped samples after the transition between notes, whereas the "normal/natural"  FL1_perf_legato play the whole recorded original legato note, which is not looped and therefore shorter. 

Best, 

Paul

Thanks. I hear that now when I compare how the patches act after a transition.

What was confusing me, and still is, is that if I start with no notes playing, and then I play a single note in FL1_perf_legato (without transitioning to any subsequent note), that note loops forever. Is there any way to avoid the looping behavior on the first note?

@BachRules said:

What was confusing me, and still is, is that if I start with no notes playing, and then I play a single note in FL1_perf_legato (without transitioning to any subsequent note), that note loops forever. Is there any way to avoid the looping behavior on the first note?

In contrast, if I start with no notes playing, and then I play a single note in OB2_perf_legato (without transitioning to any subsequent note), that note does not loop forever. So there's inconsistent behavior between FL1_perf_legato and OB2_perf_legato. This appears to be a bug in the functioning of FL1_perf_legato.

• first note in FL1_perf_legato: loops forever;
• first note in OB2_perf_legato: fades out.

Paul

Dietz

Hello

Will VSL be acknowledging and fixing this bug?

Hi, 

Some instruments are MUCH harder to loop, so sometimes we had to decide against using the looped version of the sustains. That´s just how it is. 

Best, 

Paul

I'm sorry if I was wrong to call this a bug. Since the behavior is important but unpredictable, I think it would be great if the documentation informed users what to expect.

First-note behavior in various perf_legato patches:

• FL1: loops
• OB2: doesn't loop
• KLB: loops
• BA: loops
• FL-3: doesn't loop
• OB-3: loops
• KL-3: doesn't loop
• BA-3: doesn't loop

 If this non-intuitive behavior is what you decided to give us the best sound, I'm all for it, and I'm happy to accomodate it for the sake of sound quality. Just thinking it would be great if it was documented and I'd not had to run experiements to understand how it works and why I was getting erratic performance before.

The issue of loops vs. non-loops came up some time ago.  Originally, there were no loops at all in VSL because unlike other sample libraries up till then, they were creating a pristine, totally realistic orchestral sound.  If you look at the sample libraries before VSL, you will understand what I am talking about.   I was one of the people using those sample libraries before VSL and know the difference.   [:'(]

So later they did a huge job of creating looped versions. These are not entirely complete, because the company has been concentrating on getting new software out, new instruments sampled, new paradigms of how to create reverb with MIR, etc.  So the loops have a bit of inconsistency.  It has not caused me any trouble since almost every instrument you need loops on are looped - including ones that are in "Resources" in the solo instruments, as well as all the strings except solo which was decided against as an artistic issue. 

One thing on this list of non-looped Bach rules posted - that is correct, but if you audition the fl3 sustain for example, it IS looped.  So when that same sustain sample occurs with the legato start note, it is not looped.  But it is no real problem as you will usually be alternating between sustain and legato anyway. 

My point is there are a few inconsistencies, but they are not really of significance for actual performance.  Also, most of these things are addressed in instrument updates, whih VSL has been doing regularly. 

@Another User said:

..., as well as all the strings except solo which was decided against as an artistic issue. 

One thing on this list of non-looped Bach rules posted - that is correct, but if you audition the fl3 sustain for example, it IS looped.  So when that same sustain sample occurs with the legato start note, it is not looped.  But it is no real problem as you will usually be alternating between sustain and legato anyway. 

My point is there are a few inconsistencies, but they are not really of significance for actual performance.  Also, most of these things are addressed in instrument updates, whih VSL has been doing regularly. 

I understand looping can cause artificial sound. I like VSL for providing pristine sound, leaving me more options and control. I don't mind an incomplete collection of loops here. I was only confused by the undocumented inconsistency I discovered. Thanks for the background info.

I wonder how to get a non-looping first note for FL1, KLB, BA, and OB-3? 

"Resources" occurs with most instruments' patch list and has some extra versions of legato, sustaining legato instruments like the solo woodwinds and brass, as well as single layer long notes.   

On that situation of a non-looping note you can't get a non-looped version.  However, it doesn't make any audible difference on those instruments due to the ensemble sound, and because of the release samples that are available.  Probably the only place where having unlooped instruments matters is solo strings.

@William said:

"Resources" occurs with most instruments' patch list and has some extra versions of legato, sustaining legato instruments like the solo woodwinds and brass, as well as single layer long notes.   

On that situation of a non-looping note you can't get a non-looped version.  However, it doesn't make any audible difference on those instruments due to the ensemble sound, and because of the release samples that are available.  Probably the only place where having unlooped instruments matters is solo strings.

Thanks again, William.