VSL Team,

I own and love every piano.  I am only now missing a felt piano from you to complete my setup.

Please add this to the wish list :).  I need that larger than life dreamy felt piano sound with the Synchron player.  As soon as vacations are over and the holiday kicks us into a new year, please setup your little VSL automated piano playing robot and have him/her record a felt piano.

For now, I will try to live with Una Corda Bosendorfer Upright with a filter.  Just don't keep me waiting forever :).

Thanks :),

Christopher

Hi all,

I wrote this song yesterday and finished it today.  2020 was long and rough year.  I needed to do something different to get myself to relax and release tension.  At first, I started to go down the road of just writing something inspirational and uplifting, but found myself wanted to release almost unsettling and unnerving energy.

This song probably fits in the category of Hybrid Epic Piano Meditation music.  You will find the glorious Steinway leading the way with the Power Drums adding body and additional rhythm.  I performed every part in live one at a time.  Starting with the piano.

Not my typical style of music, but it's growing on me and is very therapeutic.  I added some soundscapes you can hear like Rain and epic low pulses.

Hope you enjoy.

Despondence

Maestro2be

Of all the important things in that video, this was the most important to me that I picked up on as well :).  Can't wait to see how that works giving each instrument it's own personal relationship with a microphone!

Hi all,

I am getting terrible phasing issues when trying to use the High Strings XF preset and then choosing legato with vibrato xFade.  Anytime I play back my passages that xfade between light and strong vibrato the entire passage is filled with phasing issues.

Is this setting not good to use when you're bouncing in between the 2 cells at say 50%?  I am not hitting the slider and only going from 1 to 100, I am riding it like any other automation to give me a feel of slipping in and out of different levels of vibrato but it's completely unusable.

Is there something I am doing wrong?  I am simply playing a soaring single note melody above the orchestra and moving the xfade up and down to taste.

Thanks,

M

I have also made a video of this issue.  I am sending it to VSL Support as well but wanted you to see this Dietz.

Miracle Reverb Bug

Thanks!

Originally Posted by: Dietz

Huh! I have never run into that issue myself, but I'll give VSL's software engineer another hint to look into it.

Do you have any system details to share with us, in the meantime ...?

Kind regards,

I know right lol!  This is one of the strangest things that's ever happened to me on my DAWs. Here's my system setup:

1.  Windows 10 Pro version 1909

2.  AMD Threadripper 3970X 32-core process

3.  128GB RAM

4.  NVME SSD drives for all samples and OS

5.  Gigabyte TRX40 AORUS XTREME Motherboard

6.  Studio One v4.6 (does it in here)

7.  Studio One v5.1.1 (does it in here)

8.  Cubase 10.5 (does it in here)

9.  Radeon RX 5500 XT

10. Vienna MIR Pro 5.4.16751

11.  VE Pro 7.0.20

12.  Vienna Suite Pro 2.0.3424

13.  Vienna Suite 1.5.3329

14.  Synchron player 1.1.1949

15.  Synchron Pianos 1.1.1518

16.  Vienna Instruments Pro 2.5.18635

Hope that helps, this is one crazy annoying thing!  I love Miracle but it's getting impossible to use this way.  My bounces and playbacks are washed out in almost 9 seconds of reverb.  I even removed them all, saved the song and put them back in.

Thanks!

I have been doing that for many years.  The biggest thing is to let your ears tell you it's ok, not how it looks on the stage.  I have done some of the stupid shit you can imagine with this tool.  People would probably laugh and say I am an idiot but oh well!  As long as they don't see how it looks, and it sounds great I really gave up caring how it looked on the stage years ago!

Hi all,

I have been having an issue with Miracle in my songs where all Miracle instances will play the settings of another track.

As an example, I have a flute setup to play super long length of 7 seconds and 100% 0dB Wet.  When I start my song, the Solo cello that has it's own Miracle instance will play those exact same settings, even though it's setup to just do the standard "Synchron Stage Enhancement" of 2.10s.

As I go down the line of instruments they will ALL do this.  If I hit the power off button on the plugin and turn it back on, it comes alive with its own real settings and plays fine.  Problem is I have to do this every time I load the song on all instruments.

Anyone ever seen this or have suggestions?  I spoke to Support about this already but they were busy fixing a million other things for us all.  I suppose I could engage them again if no one here has any ideas.

Thanks!

Hi VSL Team,

So I have been trying to make some piano recordings and couldn't figure out why I couldn't achieve any sense of balance in my performances.  I just this moment accidentally realized that it's quite simple.

When I depress the sustain pedal and push a note, it's 4 times louder than the exact same note, same pressure, same velocity played with the sustain pedal released.  This is most noticeable in the very softest ppp playing, or essentially all the notes I play below 15-20 velocity.  Here's how to reproduce this result:

1.  Load up the Synchron Bosendorfer and change to "Intimate" position.

2.  Turn the Pedal Noise to -inf dB.

3.  Leave the pedal alone (in the up, non-depressed position) and play a note with velocity 1.

4.  Now depress the pedal and play the same note with velocity 1.

This note will be tremendously louder.  It happens for me on all notes of the keyboard.  I have also just tested all the pianos as I own them all and they all do it.  I also realize that it doesn't matter what player position I choose, they all do it.  Is this a bug or are these pianos not sampled at the same velocities for all scenarios of pedal depression techniques?

Is there a fix for this?  It's impossible to use these pianos this way and is playing mind games with my finger pressure during performances.

Thanks

I purchased the poster years ago, framed it and have it hanging on my wall next to my primary DAW station.  Always loved that poster :). 

The backgrounds are a great addition to this.  Very much appreciated!

So here is something while working with the VSL team that was suggested to me and at least seems to temporarily make them go away until it starts happening again.  At least I don't have to reboot or close my song and restart again.

When the problem arises, open one of your existing instances of the Synchron Player and go to the Gear icon in the top right corner.  Click on the Engine Tab.  For the setting of "Streaming Threads" change your number to something other than what it is now.  Mine was set to 4.  I changed it to 6.  I then closed it.  Open it again and change it back to your original setting.  I changed mine back to 4.

After doing that, the song worked again without having to reboot.  Took me like 10-15 seconds total.

I am still working with the VSL Team as needed and they were finally able to reproduce it on their end after doing a teamviewer with me.

Be curious if this helps others in this thread have to not reboot while VSL solves this issue.

Christopher

Originally Posted by: johnstaf

In Cubase, VST lists will have /// displayed to the right of VST3 plugins. Click on the output box in the inspector of an instrument track, and a list should open up with the current instrument selected. 

Thanks!  Exactly what I was looking for.

Christopher

Hi all,

I know how to identify which one is VST2 or VST3 before I install it into my song.  I am curious if it's possible to know after the fact when I have forgotten which I loaded if the current Synchron Player is VST2 or VST3 within the player itself?

Can it be done in Cubase or Studio One to identify the version?

Thanks!

Excellent.  Thank you Ben.

The plot thickens.

I performed the update yesterday and the results are still the same.  Dropped voices.  However, now it comes witha new issue.  All of my Miracle instances are randomly ignoring their proper decay times.  For instance, I have a 9 second length on my Flute, it now plays a length of about 1 second.  My Solo Cello is now playing for 9 seconds, with a length parameter of 2 seconds.

I hit the little "power off button" on the plugin, hit the "power on" the plugin again and it works as expected.

I reboot or simply restart the song.  It does it all over again.

Christopher

Hi Ben,

It's the latest as in, you all haven't gotten around to update it to show all the missing options?  Or it's the latest and somehow I am missing all the options I don't see in the manual?

Thanks,

Christopher

Hi All,

Where can I find the most up to date MIR Pro manual?  I see the tab at the top of the site that leads to "Manuals" but the MIR Pro looks many years old and many options are missing from it.

Thanks,

Christopher

I haven't seen that behavior specifically on my system.  for me it happens to my entire song and all instruments in the song.  Once it happens to one, the entire song is rendered useless and a complete reboot and reload is required.  No amount of unmuting, unsoloing or any other measure resets it and makes them start working again for me.  This is true within VE Pro 7, Cubase 10.5, Nuendo 10 and Studio One v4.6.1 and v4.6.2 on Windows 10 Pro.

The search continues.  Hopefully we get to a resolution on this as I am weeks behind and losing motivation and steam on my current projects.

Christopher

Ben,

I was able to reproduce it in Cubase pretty quickly.  I took a minidump while it was playing the song and crackling, popping and dropping the notes.  I also then stopped the song, let the computer catch up for about 30 seconds to calm down and took another minidump while it was sitting idle.  I was able to reproduce that as always, even when idle like that, the second I hit a note it drops it with the red disk.

Here's my case number as I emailed a link to my OneDrive with the minidumps:

Case 351129

Thanks,

Christopher

Originally Posted by: bbelius

Please create a process mini-dump of the host after the issue appears (host the Synchron Player in Cubase and create the dump from the Cubase.exe process), please see the following image on how to create a minidump with process explorer:
http://cloud.addictivetips.com/wp-content/uploads/2012/02/create-dump-1.png

https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Send us the dump to
Hopefully this will help in the investigation.

Many Thanks!

I am trying to capture this tonight.  Does it only work in Cubase or will the one from Studio One also work?

Christopher

Originally Posted by: holywilly

Originally Posted by: bbelius

We use our own plugin-format inside VEP for our players.

The drop off behavior happens on Synchron Player tracks in VEP 7, all softwares are the latest. And no note drops when using as instrument track in Cubase Pro (both VST 3 and 2). I’m on Mac OS Mojave.

I can tell you with absolutely certainty that it happens in VE Pro 7 because it does it for me on Windows 10.  It's the first place the issue arose and I put in a help ticket for it.

For myself and Dave who have done all this testing above as well as many others who are simply not voicing it yet, it's not DAW or host specific and so far proven to do it in VE Pro 7, Studio One, Cubase, and Nuendo.

With Ben just bringing to light that VE Pro 7 uses it's own proprietary version of Synchron Player, it just further shows it's specific to the Sychron Player and most likely nothing else.  We were able to quickly get to the fact that it's VST3 inside a DAW and VE Pro 7's version specifically.

I would be cautious about making any adjustments to your systems, especially since I have risked and almost lost everything doing the tests I did above.  All to which amounted to absolutely no improvement.

Christopher

Today I tested using VST2 instruments in several situations and every time they worked fine the entire day while the VST3 had issues all day.

At this point I guess I hope the VSL team will get this resolved.  I don't have the energy in me to replace all my instruments as my template is 1500 tracks of VST3 and my current song is 491 of those.

Christopher

Hi Ben,

I have 10 NVMe drives with every section on it's own.  Synchron Player shows over 600MBs on the speed for all drives.

It automatically set it to 3072 for preload buffer for all drives.  That used to work perfectly up until this issue started on that update.  I have since tried every setting up to the maximum of 32768 which is where I am right now and it happens no matter what setting I use.

Thanks,

Christopher

I was not able to make the VST2 Synchron Player do this tonight in my testing.  I ran it for several hours and all the VST3 instances were doing it, but the VST2 instances were running just fine.

Christopher

Same thing for me Dave.  I still have the issue and it's not resolved.

This time I loaded up the project and ran absolutely nothing but Studio One.  No VE Pro, no internet browser, nothing.  Just opened the project and left it looping and it started doing it shortly after.

While the project was now misbehaving, I added a brand new VST3 instance and added a simple woodwinds flute 1 and it does the same thing.  I then added a VST2 instance and added the same flute and setup and it doesn't do it.

I then loaded up VE Pro and all of my VE Pro instances are VST3 and they do it as well.  I added a VST2 64bit instance with a Synchron player inside of it and it didn't do it.

Perhaps it's a VST3 thing?  I am going to copy all the parts to these new VST2 instruments and let them loop for a few hours and see what happens.

Christopher