Hello Falcowe,

thanks for your reply.

These are the characteristics of my computer:
• iMac 27" 2020
• Intel i9-10910 3.6 GHz 10-core
• 128 GB 2667 MHz DDR4 RAM (~35 GB free RAM during project running)
• Internal NVMe SSD with both OS, applications and libraries samples
• DAW tested: Cubase 11 Pro and Studio One 5.3 Pro
• Sample rate: 44100
• Bit depth: 32 float

These are VE Pro 7 settings:
• 7 running instances on
• 3 threads per instance
• 23 MIDI ports per instance
• 8 audio outputs per instance
• 4 audio inputs per instance
• MIR Pro latency: 1024
• MIR Pro IR cache: 2 GB

I tried using a different computer (laptop) with lower specs but the issue is still there.
I have installed a third-party CPU monitor application and the strange thing is that the usage indicator of each virtual thread is always incredibly low, but the fan keep spinning like crazy and macOS internal activity indicator application shows the posted numbers (~300% idle - ~600% playback).
Looking at my computer specs it should not have those kind of problems, and it should not have as much thermal throttling since the the CPU usage never reaches full cores 100%.
I noticed that the CPU frequency is always around ~4.4GHz, could be that the culprit?

Hello,

I'm always having weird crashes as soon as my DAW project connects to a VE Pro 7 server project.
Two times on three it crashes and the only thing to do is manually killing the Synsopos process from my computer activity monitor, because if I don't do that and try restarting VE Pro 7 it hangs indefinitely!
I really hope we no longer will have to deal with Synsopos anymore once VSL will transition to iLOK.

Hope you can help. 

Hello,

as soon as I start playback on my DAW (connected to a VE Pro 7 server project) I notice VE Pro 7 filling up CPU usage (626% on a 10 cores CPU!) and my computer fan spinning like crazy at maximum speed.
Buffer size is set to maximum and all of my VSL instruments preload are set to maximum too.
Stopping playback does not turn my computer back to normal: VE Pro usage remains at 276% and fan continues spinning at maximum speed.
The only thing to do to stop that is closing VE Pro/DAW project 

My computer is using an Intel 10 cores CPU, 128GB RAM and internal NVME drive to store instruments samples.
Hope you can help.

Hello Andreas,

any news on the VST3 issue?

Hi VSL,

I noticed from the contents page that the soft sustains from BBO Zodiac are missing in the 12 horns and 9 trombones instruments of Synchron Brass. Is that correct?

Hello Paul,

that's fantastic and very welcome news!
Could you please detail the amount of velocity layers available for the different instruments/articulations?

Thanks

Hello Paul,

could you please tell how many dynamic layers does Synchron Elite Strings come with?
Thanks.

Hello,

the problem is only related to Synchron Player and VE Pro,
because Vienna Instruments Pro shows up the correct MIDI CC names.
I kindly ask VSL to check what differs in their implementation between Synchron Player and Vienna Instruments Pro with Studio One MIDI CC binding.

Thanks

I have just tried using the Studio One special offer code from VSL but it doesn't work 

Is there anybody who has encountered the same problem?

UPDATE: solved

Originally Posted by: Macker

Just to give my fellow Logic users a little sneak preview of what can be done with the latest Logic. It's a very sweet articulation feature, which is playing nicely here with Syz Dimension Strings in VEP7 via AU3.

Seem to be something familiar to Cubase users about the articulation display in this pic? Have Apple nicked Steinberg's Expression Maps feature now?

Logic adepts will know the answer.

I'll explain later.

(The pic attached is a grab from my Retina screen, it won't display inline in this forum without spoiling the necessary resolution; sorry, it has to be downloaded.)

WOW, I can't believe it's finally possible to do that in Logic 

I'm looking forward to your explanation 

Originally Posted by: Paul

Hi everybody, 

I understand what you mean. 

Herb Tucmandl made these decisions in order to create stream-lined version of our products that allow a quick overview and high compatibility between sections. 

I can't make any promises at this point, but we will discuss how we can "bring those articulations back" and integrate them with the SYNCHRON-ized versions. 

Best,
Paul

Great, I'm looking forward to it!
Thanks

I also terribly miss a lot of other articulations from VI Appassionata Strings, such as the useful crescendos and diminuendos, staccato variations, harshes, legato slur, legato sfz and more.

Those are very great omissions and I wonder why VSL decided to remove them from Synchron-ized Appassionata Strings.

Please bring them back.

Originally Posted by: Paul

Hi, 

We just added new mixer presets to all SYNCHRON-ized products (including our SYNCHRON-ized Special Editions). which makes it more comfortable to integrate those instruments with MIR Pro. 

The whole Synchron Player mixer is reset for this purpose, so that you're ready to apply the MIR magic to dry samples. 

What is reset?

• EQ
• Impulse Response
• Algo Reverb
• Panorama
• Volume

Find all SYNCHRON-ized Library Updates in MyVSL and the changelogs here. 

Best, 
Paul

Hello Paul,

great news!
Are these for Synchron-ized strings only? I can't find any recent update for Synchron-ized Woodwinds with the MIR unprocessed mixer preset.
Thanks

Originally Posted by: bbelius

Hi,

I nevert encountered such problems, be it with my
- current AMD Ryzen 5950x, 64GB RAM, NVMe SSD (as many mics as I like @128 buffer size),
- last system Intel i5 8600k, 32GB RAM, NVMe SSD (presets work perfectly @128 buffer size), or
- current notebook i5 8250U @1.8GHz, 16 GB RAM, NVMe SSD (2-3 mics work fine @128 buffer size).

1) What exact version of Windows 10 are you running?
2) Are you running stock Windows, or did you already optimized any settings related to performance and energy consumption, data-collection...?
3) Are you using ASIO driver?
4) What audio interface are you using at what buffer size?

Best, Ben

Hi Ben,

thanks for your reply.
Both of the computer I tested was Mac systems (Catalina and BigSur) with integrated audio card, no external audio interface

Originally Posted by: migebo

Got my version yesterday evening...night...far too less sleep last night...anyway

There is a question with the CPU - Meter. The CPU will be max to 12% or 13 %, but the red Peak starts (do nothing on the fresh started computer) with 42 %. Just hit the pedal will rise up to 87% without playing a note. While playing it is about 100% fortunately without any drops...

Not a big deal,  the sound is perfect, but it looks a bit strange to me...others?

Win10pro / / 32GB RAM / GTX 1080 / SanDisk SDSSDH3 500GB / 10 Fingers / 1 Brain

I have never been able to play live ANY of the Synchron Pianos... I tried first on a 6-core i7 with 16GB RAM and internal NVMe and I was not even able to complete a piece execution with the Room-Mix mic only because of continuous CPU spikes. Then I tried a 6-core i9 with 32GB RAM and internal NVMe and guess what? Room-Mix mic was ok, but adding another mic produced the much hated CPU spikes again!
In both cases I set the buffer at 64 (since with higher it's impossible to play live) and the preload size to maximum (32768).
If one would play only pedal-less pieces than he MIGHT be able to use more mics, but... seriously?
I've read on another popular forum of people having CPU spikes even on a 2019 16-core Mac Pro!
To me and with my equipment, Synchron Pianos are currently unusable for live playing :(

I'd very like to know the exact setup that VSL and their demo contributors used to play and record their audio demos.

Hello,

that probably depends on the text editor they implemented, which create a new paragraph each time you press the ENTER key.
To avoid that extra empty line simply press SHIFT+ENTER instead of ENTER

I'd looove a VSL sampled Fazioli 308!!

Hello Paul,

will there be demo licenses of 280VC before the promotional price expires?
Thanks

Originally Posted by: Paul

Hi, 

Seems like the first note doesn' have enough time to get started. Did you try with the Legato Agile, which is designed for faster passages?

Best, 
Paul

Hi Paul,

many thanks, using Legato Agile on the first note and regular Legato on the following ones solved my problem!

Originally Posted by: Paul

Hello lupine, 

No reason. Can you please post an example and tell us which articulation you are playing?

Best, 
Paul

Hello Paul,

I have attached an audio excerpt (violins 1 only) from my current project and a screenshot of Cubase editor.
Here I am using the legato patch only, no xfade and max velocity on first note.

Hope you can help
Bests

Hello,

there's a reason why starting a phrase with legato patches causes the first note to be much lower in volume than the following one? That causes a very annoying bump in the music. Other VSL strings libraries don't have this issue.
Someone can help?

Hello,

you can try these:

• disabling unwanted MIDI chasing (unchecking "Preferences > MIDI > Chase events")
• disabling MIDI reset (unchecking "Preferences > MIDI > Reset on stop" and checking instead "Never reset chased controllers")
• simplifying your MIDI CC curves by thinning out MIDI data in your tracks (MIDI > Functions > Thin out data)

All you have to do is buy the Vienna Protection Plan, which has been available for years now https://www.vsl.co.at/en/Product_Overview/Vienna_Protection_Plan

I suppose Rasmus Faber refers to the GUI elements which in MIR standalone show up with the old VE 5 graphics, while within VE Pro 7 they come in the full renewed graphics of VE 6 

Hello,

I'd like to reopen this thread because I have the same issue and there is nothing I can do to solve it.
I am using Big Sur and pressing the space bar from within VE Pro 7 only lights up/down the little play icon in the toolbar and nothing else. It NEVER does play/stop my daw playback (both Cubase 10.5 and 11).

I tried everything: wiping out the macOS TCC database, removing and reinstalling VE Pro 7, upgrading from Catalina to Big Sur... nothing!

UPDATE: it turned out it is WaveShell v12.0 which causes the space bar "stealing". By updating to v12.6 the problem is resolved!