Sure.

It seems tha A(4?) in condenser mic, needs some treatment, too. It's ringing

Originally Posted by: andi

Hello V_ad_im, Lars and TFIS!

We can reproduce the ringing and will look what we can do.

Best regards,
Andi

Thanks.

Will there be a fix?

Almost all parameters can be controlled via midi cc.

Every fader able to send midi cc should work.

And please: DO NOT re-invent anything....

Yes

p. 47, Slot Editor - Edit.

Did you try polyphonic legato?

But don't make it so huge, like the controller curves in the SYPlayer. Otherwise people could accidentally read values or set proper x-over points... ;)

No problem to do a note shift here (->inspector 12 or even 24 semitones), because the position of the keyswitches won't be affected.

Originally Posted by: fahl5

Originally Posted by: TFIS

The new player has (imo) more dis- than advantages.

Which exactly?

Humanize gone

repetitions can't be edited

less control sources,

sequencer gone,

keyboard volume tracking gone,

mirx integration gone,

adjusting controller curves in sy-player is a pain in the ass,

scale editor gone,

remote app gone,

master release switch gone,

A/B switch gone,

"auto" voicing gone (which was never  "divisi"),

standalone mode gone...

just to name a few without looking too deep into the details.

They should have just built the mixing section to vipro.

The new player has (imo) more dis- than advantages.

Maybe someone using MIR can send some sweeps through the roompack to build IR by ourselves?

Would that work?

For some reasons I don't like the presets delivered by VSL ("wasting" the modwheel for articulations instead using it for dynamics, for instance).

So I build all presets from scratch (VIPro and SynchronPlayer).

I try to use allways the same keyswitches for the different libraries.

A is sustain, B is legato, doesn't matter if strings woodwinds or brass.

For synchron strings I use keyswitches inside the synchron player, which are remapped to my personal keyswitches / expression maps.

From 0s to 39s:

Distorted mess.

You could use the matrix list + program change.

Hi,

I tried it again with a factory preset: same result

ALL legato and ALL long articulations (even tremolo) lead to a cubase crash when setting the delay a little bit higher (0.2 for example, leaving the other knobs untouched) and play fast notes.

Different Instruments , reverb setting off, only one mic...

I'm pretty sure ribeye meant yout mockup, not "the people at VSL".

Hi Paul,

thanks for the reply.

I will try it with the factory presets this evening.

Is there a confirmation or am I the only one with that error?

Regards

T. Fischer

Sorry, I wrote it misleading:

It's thinks Windows, which shuts cubase:

Name der fehlerhaften Anwendung: Cubase8.5.exe, Version: 8.5.30.192, Zeitstempel: 0x58ad9164
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.16299.492, Zeitstempel: 0x5c04cfa2
Ausnahmecode: 0xe06d7363
Fehleroffset: 0x00000000000450d8
ID des fehlerhaften Prozesses: 0x84c
Startzeit der fehlerhaften Anwendung: 0x01d419e617761f15
Pfad der fehlerhaften Anwendung: C:\Program Files\Steinberg\Cubase 8.5\Cubase8.5.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: 710986a5-e1f5-4b13-888a-035d20b66f3f
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Thats what listened in the "Ereignisanzeige" (I'm too lazy to google the english word...now im curious...ah: Event Viewer!"

Edit: I ran sfc/ scannow without results

Problem: If you start from scratch, you won't have access to the mixer presets which are available if you use a factory preset.

So I resaved them

1.) Standard version

2.) Check the reverb setting. Sometimes I forgot to switch the reverb off.

Cubase 8.5, 64bit crashes ALWAYS, when setting up the player like shown and playing faster notes.

You should raise the max. voice count to 1024 and take a look at the x-fade settings on the edit page.

Originally Posted by: TFIS

Same problem here

Is there a fix now?

Self quoting sucks, but:

It seems that issue depends on odd soundcard latency settings.

I ran mine on 196 samples when the crash occurs, set it to 256 worked.