No, not in my particular case. But you may well have better luck with your system than mine.

Thanks Paul. Sorry, I've only just had a chance to try this out. Unfortunately Cubase still froze when exporting audio after I installed the update. Perhaps there is something wrong with my particular system rather than the player itself. I plan to upgrade to an M1 Mac soon so perhaps a fresh system will cure it.

Thanks so much. I am incredibly impressed with the swiftness of you and your team's response!

I will keep an eye on this. It may have helped reduce the freezes but it's too early to tell at the moment.

Thanks Paul.

Hi Paul,

Thank you for your reply. I don’t know if I could bear to download all of that content again. It will take me weeks as I can’t leave it going 24 hours a day, only at nighttime and weekends (for family reasons).

Is there any way you could help me out with a cheap hard drive with it all on? My project uses almost all of my Synchron libraries plus some VIs from the Symphonic Cube.

I tried turning Cubase’s ASIO-Guard off and also exporting my mixdown to a different SSD drive but the feeezing still happens. I literally just tried and it froze at the very start of my project. It’s very frustrating.

Hello,

I'm on the latest version of Synchron player v 1.1.2046 running on macOS 10.15.7 in Cubase 10.5.30 as a VST3 plugin.

It seems to crash a lot for me. Sometimes it will crash when loading the project and Cubase will suddenly disappear. Sometimes it will crash when exporting an MP3 (in random places). If the crash happens when I'm exporting audio Cubase will become unresponsive — I can't even cancel out of the audio export. I have to force quit. Once I've done that I can no longer restart Cubase and, what's even worse, my Mac will not even shut down properly so I have to execute a hardware shut down but pressing and holding the power button for a few seconds.

All of my VSL library files are stored on a 6 month old OCW Thunderblade drive, but I'm exporting to a Seagate USB Hard Drive.

I know it is Synchron that is crashing because of the Cubase crash report.

I have the latest elicenser software. I'm not sure how to solve this issue.

Does anyone have any answers or suggestions for me?

Many thanks,

Darren

P.S. I tried to post the Crash Log info but the text size exceeds the limit for the forum software. Here is a link to the file in case it helps diagnose the problem:

https://www.dropbox.com/s/i15oheth4dd3t61/Cubase%2010.5_2021-10-10-092036_Mac-mini.crash?dl=0

In Cubase, there is a type of quantising called ‘Iterative’ which moves the notes towards the grid lines by a user-specified percentage. There are probably similar features in other DAWs. I usually set it to 50% and select just a few notes than sound a bit sloppy, carefully set the right grid quantise value (i.e. quarter notes, 8th notes) and quantise with Iterative Quantise. Then listen back to hear if it has improved things. Obviously be very careful if there are any triplets or duplets as these will need to be handled with a different grid setting. Also watch out for notes that get knocked in the wrong direction, which happens if they are closer to the next gridline to the right (or left) than intended.

Sometimes it may be worth just re-recording the problem section rather than try to massage a sloppy or slightly off recording.

I hope that helps.

I've just spent the last week trying to track down an issue I've been having when playing live in Synchron (VEP6 and VST3 single instance) in Cubase 10 on macOS 10.14.3. I was getting lots of red CPU overload warnings in Synchron and most notes being cut short or not sounding at all. Weirdly, this only happened with I played live, but not if I played back a pre-recorded MIDI track. It happened with all of the Synchron libraries including the pianos.

 

Initially I thought the problem was with my SSD. After buying new cables, and even using a Faraday bag and tinfoil, I found out the culprit was the high buffer setting in Cubase. I had it set to 2048; when I reduced it to 1024 the problem vanished. I'm glad I solved it because I was about to buy a new SSD I was that fed up and desperate.

 

I'm just posting this here in case any one else has this issue. I have no idea why this caused Synchron to throw a wobbly, but it seems it does not like the high buffer setting.

Cheers!

Hello,

Although I appreciate all the work that’s gone into upgrading Epic Orchestra, is there an option to not install it with VEP7? I own most of your libraries so don’t really need EO2 and would rather save space on my SSD.

Thank you.

Thanks for the quick reply. I guess I just need to take another look at the interface structure a bit more!

Hello,

I've just loaded up a few of the Cubase Expression Maps I downloaded from your website, and there seems to be an error with one of them:

The "VSL SY-DB-I - Trumpets.expressionmap" (SYNCHRON-ized Dimension Brass) had keyswitches intended to switch between the trumpet players, but had them on F3 to B3 (this is using Cubase's annoying C3=Middle C naming scheme - at least VSL got it right with C4!). This is within the trumpet's range and therefore deactivates any sample triggering in this section! According to the Synchron Player for the SYNCHRON-ized Trumpets it should be F5 to B5 (Cubase spelling, or F6 to B6 'Rest of World' spelling).

I have edited and saved a corrected version. How do I go about getting it to the right person to upload and replace the one you have on you servers (assuming I am correct)?

Cheers,

Darren

When I select the Trem marcato in any of the string sections, I can select Normal Attack, followed by "Long - vibrato" or "Tremolo" under Trem-Control and I can x-fade between them using the Dim. Ctrl/E slider. However, when I select Marcato Attack, the Trem-Control column is not visable, even though the slider still allows me to x-fade between the "Long - vibrato" or "Tremolo" sound. That seems odd to me. Surely the Trem-Attack column should be visable in both Attack versions, especially if you can still use the slider to x-fade between the trem and long-vibrato sound in both Normal and Marcato versions?

Is this as intended?

I have only just started using MIR Pro, and have also only just discovered MIRx and what it can do. I was excited to read that it would do automatically exactly what I have been struggling to do for the past few days. So I excitedly rushed to enable MIRx for my Vienna Instruments so they would fit and match with my Synchron libraries. I was left scratching my head as I could not find the Synchron Stage MIRx preset. I wondered if I not installed the presets correctly, so went looking for it in my downloads section. Nothing.

I'm disappointed to find out this is not available yet. But am glad to hear it is, at least, on your "to do" list.

I'd like to add my voice to those asking for this to be available sooner, rather than later.

Thank you.

 

I would like to know this too. Did you ever get an answer?

Hello,

I've created an A3 sized wall reference chart for the common instruments of the orchestra.

It includes written and sounding ranges; dynamic ranges; timbral characteristics; additional comments outlining the strengths and weaknesses of each group.

Instrument Reference Chart v6.1 (zipped file via Dropbox)

Both PDF and Sibelius formats are included. The included font is not required, but the chart will not look as intended without it. Of course, you are free to change anything to suit your own needs.

I would recommend that you get it laminated for longevity. Use good quality paper, possibly glossy, which will aid clarity.

The exact ranges of the instruments are always a bone of contention, as no 2 books agree completely. But all the ranges I have settled on represent the extremes of each instrument, which are obtainable with professional players. In some cases, the ranges can be extended beyond that shown, with a good player.

Most, if not all, instrumentation books always list the written ranges first. I have listed the sounding ranges (other than the octave transposing instruments) first, because I always write my scores at concert pitch. Therefore, I find it much easier to look down the list and see the actual sounding range whenever I'm writing a part. I'm sorry if this bothers you, but that's my preference.

Finally, not everyone may agree with all the remarks made in the 'Additional Comments' column. These comments have been collated from the bibliography cited on page 2, and they are the views of the respective authors. I have printed them here as a guide only; if you have a good reason to disregard these comments then by all means do so.

All the best,
Darren

[I could not edit my original thread from 2005 so created a new one. Original thread here: https://www.vsl.co.at/co...eference-Chart-version-4 ]

Hello,

I have only just seen this, sorry. I've uploaded it to my Dropbox account:

Instrument Reference Chart v6.1

 

Kind regards,

Darren

Hello,

I get an almost immediate crash on VEP 6 when trying to load the Pulsar Modular P900 AU plugin (demo version):

http://www.pulsarmodular.com/products/

This is on a fresh VEP 6 with absloutely nothing else loaded, and not connected to any DAW. Also, no DAW or audio app running. I noticed someone had a similar issue with VEP 5 last year:

https://www.vsl.co.at/community/posts/t41284-VEP-5-crashes-at-load-of-the-pulsar-modular-P900-Plugin#post247481

I have tried loading the plugin in VEP 5 and I am able to play and hear the plugin without any issues, but the GUI is invisible.

I am able to load the plugin in Logic Pro X without a problem.

Any ideas about how to solve this?

Many thanks,

Darren.

Specs:

macOS 10.12.6

Mac Mini Server 2011

2Ghz Intel Quad Core i7

16GB RAM

VEP Server (64-Bit) 6.0.16502

“Rage”? Really? Something’s definitely not right with your perspective if a product delay causes rage. Annoyance perhaps, but rage?

Sorry, but your post reads as either extreme over-reaction or sarcasm.

Hello,

I would like to echo what others have said. I am interested in this library, but am not prepared to pre-order unless I can hear some audio demos of the Synchron Strings alone - with no other instruments masking them. Only then will I be able to hear whether this is superior to what I already have (VSL and others).

I do hope the demos will appear before the Early Bird offer expires.

 

Thank you,

Darren

I hope I don't speak too soon, but I think I may have solved it.

 

Something weird happened in Cubase. I disconnected the VEP instance in Cubase, created a new VEP instance and selected the new MIDI outputs of that new instance.

 

Now it seems to be working OK...fingers crossed.

 

I still don't understand what happened though.

Hello,

 

I recently applied your latest version 5 update and now I can no longer hear anything coming from VE Pro.

I'm running Cubase 8.5 on Mac OS X El Capitan 10.11.6.

It says it's connected, but there is no sound. I'm also not sure any MIDI is getting through.

I tried to load a AU instrument with a virtual keyboard (Korg M1) so I could test it. When I play the keys on the Korg M1 virtual keyboard the interface lights up on the M1 (AU) to show that it's responding, but I can't hear anything.

I also tried to load a new empty Cubase project and load one VIP instrument in VEP. If I do that then it works ok and I can the intrument play when I feed MIDI into VEP. But my existing Cubase project is one that I've been working on for many years and to suddenly not be able to hear what I've programmed is very worrying. I don't understand what's going on. 

I have uninstalled and reinstalled all the latest VSL updates, but it still won't work. Please can you help me?

Thank you.

OK, thanks for letting me know Paul. I shall look forward to them.

This is a very nice demo. Thank you for that.

Hello,

Please could you point me in the direction of the audio demos for ONLY the Dimension Strings Cellos?

I have been searching the site and all I can find is the audio demos for the violins which were there before you announced the Dimension Cellos. I would like to be able to hear the cellos alone.

Thank you,

Darren

Thank you - version 5 does seem to work on XP...fingers crossed it behaves itself!

Hi,

I've just purchased VE Pro 5 and I'm having a hard time trying to figure out how to keep the VST plugins of version 4 side-by-side with version 5.

I need version 4 as well because I'm using the server version to connect to a Windows XP virtual machine (on Mac OS X Lion 10.7.3), and VE Pro 5 apparently is not compatible with Windows XP (although, I haven't tried).

Every time I install version 5, it replaces the VST plugins of version 4 - even if I copy them to my desktop. I even tried copying the version 4 plugs to a separate hard drive, and somehow it still replaced them with version 5 plugs (which is pretty freaky how it knew where I'd hid them!!!).

I'm starting to worry that it is not even possible - please help. If not I'll have to go back to using version 4, and would have wasted my money. :(