Hi Mary,

I own the Bosendorfer 280 VC and the Steinway D-274 from VSL (both full library). I find them unbeatable for music production. I own the older VSL Vienna Imperial (recent iLok update). I didn’t try the Fasioli yet.

I also have a real seven feet Japanese grand piano which I play with great pleasure (but rarely record it). My MIDI keyboard is a mid-range one (Yamaha P515). I tested several velocity curves and made my own presets. I can't seem to get anything that comes close to my real piano.

Although the sound from the listener's point of view (for music production) is significantly less rich than my VSL instruments, I have to say that the playability of Pianoteq 8 seemed a little bit better to me. This is all very subjective, of course.

Have you tried Pianoteq? If so, I'd be curious to hear your thoughts.

C.B.

Hi,

It seems at first that unlike the Special Edition Solo strings, that there are no preset containing (or merge) both con sordino patches and senza sordino in the SYized Solo strings collection. Patches and presets are presented in different folders, as if they were different instruments.

But after looking more carefully, I found the presets. An example: "01c Violin Merged basic VelXF sus". They are in the folder "3b SYzd Solo Strings sordino".

C.

[quick translation below]

Bonjour Cyril,

De mon côté, je suis passé à iLok en avril-mai. J'ai eu quelques pépins au départ, mais ça s'est très bien passé en général. Un très gros projet Logic/VEP m'a donné du mal, mais je dois dire qu'il était déjà un peu instable avant le passage à iLok. Pour que tout rentre dans l'ordre, il a fallu notamment que je supprime des alternatives de projets et que je simplifie mon setup (j'avais plus de 200 instruments et autant d'instances de scripteur pour les changements d'articulation). Par ailleurs, j'ai dû élaguer un modèle VEP presque identique que j'utilisais avec Dorico 4.

Depuis avril, je pense que les programmeurs de VSL ont corrigé la plupart des bogues qui pouvaient gêner le passage à iLok. Cela étant dit, il faut vraiment suivre la procédure scrupuleusement. Il faut éviter que l'ancien système eLicence soit actif en même temps que iLok. N'oublie pas que tu devras télécharger à nouveau tous tes instruments (il te faudra prévoir la place en conséquence sur tes disques durs).

Enfin, j'expérimente en ce moment une approche sans VEP. Toutes les instances du lecteur Synchron sont directement dans Logic. Contrairement à ce que j'avais constaté par le passé, c'est plus performant sans VEP. De plus, cela a l'avantage de simplifier la programmation des scripts AG pour les changements d'articulations. J'imagine que VEP sera optimisé dans un avenir rapproché.

Bonne chance!

C.

==================

Hi Cyril,

For my part, I switched to iLok in April-May. I had a few glitches at the start, but it went very well in general. A really big Logic/VEP project gave me a hard time, but I have to say it was already a bit unstable before the switch to iLok. To get everything back in order, I had to delete project alternatives and simplify my setup (I had more than 200 instruments and as many writer instances for articulation changes). Also, I had to prune an almost identical VEP model that I was using with Dorico 4.

Since April, I think the VSL programmers have fixed most of the bugs that could hinder the switch to iLok. That being said, you really have to follow the procedure scrupulously. It should be avoided that the old eLicence system is active at the same time as iLok. Don't forget that you will have to download all your instruments again (you will have to plan the space accordingly on your hard disks).

Finally, I am currently experimenting with an approach without VEP. All instances of the Synchron player are directly in Logic. Contrary to what I had noticed in the past, it is more efficient without VEP. In addition, this has the advantage of simplifying the programming of AG scripts for articulation changes. I suppose VEP will be optimized in a near future.

Good luck!

C.

=======================

+1

C.

Same for me.

+1

Hi,

Any development here since last summer? This bug is very frustrating and insidious. I'm still losing a lot of work. As I wrote pressing the space bar is a real automatism (or a reflex).

Thanks,

Claude

Originally Posted by: Dietz

Hi Claude,

Thanks for your suggestion. I already made the issue known to VLS's software engineers.

Kind regards,

Thanks Andy.

Hope a fix will come soon from Dorico team.

Claude B.

Hi,

I was just about to prepare to ask the same question!

I looked at the expression map for Special Edition. The right key switches are ordered for the right cells in Synchron Player. The problem: this brings us to legato (with a chromatic run) and not the portamento articulation (the cell just below). The result is the same whether we use the line or zig-zag line symbol (Glissando / Portamento) in the Dorico's score. Everything seems to indicate a bug in the expression maps.

Has anyone encountered the same problem? A solution?

Thank you very much,

Claude B.

Thank you for your answer Dietz.

While waiting to find a real solution, maybe VSL programmers could add a button or a preference to activate and deactivate the "Play" shortcut with the space bar? Because pressing the space bar is a real automatism (or a reflex). It is very difficult not to forget to abstain from it when making adjustments directly in MIR.

Thanks,

Claude

Same for me. Waiting…

Thanks.

C.B.

+1

+1

Hi Paul,

I Have the same problem. Elicenser is updated. The new licence is active. I use the last SYnchron Player and the Special keyboards files are listed in the Volume Scan Path. 

C.

P. S. OK now. I'll download the new files (your last email).

Me too!

Fine!

Great!

C.B.

Hi Rangi,

I have a big set up at home (iMac Pro, etc.). When I go out and I want to work with VSL I use my 2016 MacBookPro (with internal and external SSDs and 16 Gb of Ram). It could be a little bit short occasionally, but it works pretty well most of the time, but only if I use a 512 ms or 1024 ms buffer (audio preferences). What is your buffer setting ?

I think the new MacBook generation (with i9 and 32 Gb of Ram) could be a working solution.

Good luck!

Claude B.

(English translation below)

J'ai bien peur que non Cyril. Et c'est bien frustrant. 

Il semble que l'intégration des AU3 (dans Logic en particulier) soit encore inachevée. Si on peut utiliser des ports désormais, ils sont limités à 8 par instance et chaque port ne donne accès qu'à 16 canaux. Ça ne serait pas si mal si l'intégration était complétée, mais plusieurs briques de Logic ne gèrent toujours pas les ports. Le Scripter par exemple, qui est important pour moi en raison de l'utilisation d’ART Pro de Audio Grocery. Je pourrais sans doute me rabattre le système d'articulation de Logic, mais je préfère voir les changements en texte sur les régions midi.

Après plusieurs essais infructueux avec les AU3, j'ai donc décidé de conserver mon approche actuelle (pour un temps du moins). J'utilise les outils de AG avec des instruments multitimbraux de Logic VEP et les VEP Event Input (une instance par port). Ça me donne un maximum de 48 ports avec 16 canaux chacun. Donc, en pratique, 48 instruments multi-timbraux (pour un total de 768 instruments). Je dois, évidemment, prendre bien soin d'insérer un plug-in I/O de Logic sur chaqe instrument multitimbral sinon ça dérape complètement! Par ailleurs, j'ai eu souvent des soucis (latence, problème de synchronisation) lorsque j'utilisais des pistes audio en même temps que mes instruments VIP avec VEP/MIR. Mais Logic accepte mieux depuis l'année dernière cette dernière astuce imaginée par Vienna (à l'époque de VEP4, si ma mémoire est exacte).

Il faudra être à nouveau patient…

C.

=======

I'm afraid not Cyril. And it's very frustrating.

It seems that the integration of UA3 (in Logic in particular) is still incomplete. If we can use ports now, they are limited to 8 per instance and each port only gives access to 16 channels. It would not be so bad if the integration was completed, but several bricks of the software still do not handle the ports. The Scripter for example, which is important to me because of the use of ART Pro from Audio Grocery. I could rely on Logic's articulation system, but I prefer to see the text changes over the midi regions.

After several unsuccessful attempts with the AU3, I decided to keep my current approach (for a time at least). I use AG tools with Logic VEP multitimbral instruments and VEP Event Input (one instance per port). It gives me a maximum of 48 ports with 16 channels each. So, in practice, 48 multi-timbral instruments (for a total of 768 instruments). I must, of course, take care to insert a plug-in I / O of Logic on each multi-instrument or else it completely derails! In addition, I often had problems (latency, synchronization problems) when I used audio tracks at the same time as my VIP instruments with VEP / MIR. But Logic agrees better since last year this trick conceived by Vienna (at the time of VEP4, if my memory is correct).

It will be necessary to be patient again ...

C.

Show icon smaller or one icon for a group. These are great ideas!