Have you selected a preset? Concert, Player, Ambient, ...

Hi, 

Thanks for the update. We'll look into it!

Best, 
Paul

To refine the pattern of misbehavior I am observing - it appears that the GUI freeze is precipitated by clicking on anything in the top row of icons - GUI size, CPU, Settings - either before or after loading samples in a fresh instance of Synchron Pianos. Leave them alone, and you can load samples, and subsequently modify other (sound) parameters. Touch any of the three and I am stuck - I can play the preset as currently configured, but cannot modify any parameter or load a new preset. Have to start again with a new instance. Hope this helps!

Cheers, Craig

Hi Paul -

Yes, it is the 1.0.464 version. I will contact you via with more particulars, later today when I am in front of my home studio workstation. Thanks for your reply!

I think it may be a clue that the path under Settings was ... empty ... after initial install. Seems like adding the folder to Directory Manager would be irrelevant, even though samples did load after that step, and a re-install of Synchron Pianos (player). I only tried going through Directory Manager after trying to populate the path within Synchron Pianos ... The Synchron Pianos Yamaha folder lives on the same SSD as Synchron Strings, so the path is quite short and simple ... but nothing would appear in the path dropdown. Then I went to Directory Manager, re-installed Synchron Pianos, and now cannot even get the paths dropdown to open.  

And let me say again that the sound is gorgeous - to me, especially so in the upper registers, which are crystalline and pure, and ring out so cleanly with the Synchron stage ambience. Lower registers have power yet retain clarity. Never has my Kawai MP11 controller felt more like a real piano. Not only will my music sound better, my playing skills will improve (okay, that's a low bar, ha-ha). 

But unfortunately I must start to work (day job) now so will be in touch with the support center later today.

Cheers, Craig  

Hi Paul -

Good question! Yes, in fact I had just applied the latest Windows 10 updates (2018-03) just BEFORE downloading and installing updates to all things VSL, and the Synchron Pianos Yamaha library. The PC reported its Windows update status to be "up to date" before installing Synchron Pianos, and again late yesterday afternoon just before my first reply to this thread, and again this afternoon. HOWEVER, I just now clicked "check for updates" again and ... PC is downloading another 2018-03 update (KB4088891). I think you may be onto something here, so let me get this update installed and see what happens (it's a slooooow download ...)  Was that part of the update set that you had on board in your shop before releasing Synchron Pianos?

Thanks again,

Craig

Hi Craig, 

Let's see if we can find out more with the *.ini file for Synchron Instruments, you find it in [your_user_name] / Appdata/Roaming/VSL => Vienna_Synchron.ini

Please send that file to , with a quick link to this thread. 

I'd say Porter. 

Best, 
Paul

Just to give both of you some extra info here:-

1. No, this definitely does not require the April update.  I have not installed that because I'm not part of the early adoption scheme, and given the reported problems with it I wouldn't install it anyway.  I can run the VSL CFX fine, so that update is not required.

2. This may or may not be relevant to your problem Craig, but is something that you should be aware of, Paul.  On Windows filesystems, hard/junction links, which were pointers to other filesystem locations but which are treated by the OS as extensions of the existing filesystem, cause the VSL CFX to crash.  They work fine with literally every other piece of software I've ever tried, including other VSTs, so there is something amiss here.  It only occurs when there is an attempt to load the actual samples.  That is, if the hardlink points from C: to E:, and the software the files in C: and they are actually in E:, which should be treated as C: because of the hardlink, in practice they' are not treated the same.  don't know if it's in the VSL loading mechanism, or related to elicencer which is probably quite strict about locations, but it's worth keeping in mind.  Certainly a crash should never be the intended behaviour, so this amounts to a bug, and is useful to know in case anyone wants to move the software and was hoping to use junction links.

You're very welcome, and just for extra info, I have since downloaded and installed the latest version, and although the samples still don't load with junction links used, it no longer causes a crash (the samples simply remain unloaded), so I think you've somewhat fixed that one already. 

Thanks, Paul, for your help via VSL support ... I am all "fixed."

Thanks for your input karvala ... I didn't move nuthin', promise ... (ha-ha)

A round for everybody 

Off to play piano 

Cheers,  Craig

Hi, 

Did you check in Logic Preferences => Plug-in Manager?

Maybe you need to validate the plug-in manually.

Best,
Paul