So its my understanding that the runs in Black Eye (major and minor up and down) are NOT tempo synced, which I guess means they were recorded at one tempo. Anyone know what tempo they were recorded at? Also how does one adapt these to work in our compositions that are not written at the recorded tempo? Are these patches even usable in the real world where tempos are dictated by picture, feel of the music, etc?

Given how much of the Black Eye patches are phrase / tempo based I’m concerned at the lack of any sort of tempo syncing option in real world use. Thanks for any feedback you can provide!

I still use the VI Pro ipad app everyday and it makes using VI Pro SOOOOO much easier!! PLEASE consider making a Synchron player iPad Control app, as the lack of a premade and easy to use app actually keeps me using VI pro more often than synchron player!

With the full Synchron Concert D, there are presets / ways to make the piano sound different - 6 preconfigured presets: Concert, Intimate, Player, Pop, Ambience, and Mighty. For the special edition version, are these 6 presets included, just with less velocity layers? Thanks!

I see epic Orchestra 2 comes with a sort of "demo pack" of the current synchron libraries. If I already own some of the full libraries, is there any reason to install those parts of Epic Orchestra 2? 

Thats great to hear!! I ran my own tests between VEP6 & VEP7 and personally did not see noticable improvements in performance, but that was a couple of versions ago. Plus I'm running Cubase on a Mac. Maybe I'll have to run the tests again. 

Curious, are you using coupled or de-coupled instances? I know they made some pretty significant improvements for coupled instances which is great. 

 

True, but to make it clear, as long as you dont save over VEPro 6 projects in VEPro 7, you can always get back to VEP 6 by using the Ve Pro uninstaller and re-installing VEP6. I've done this multiple times during the beta period on both PC and Mac without issue. Just download the VEP6 installer from your user account while downloading VEP7 Demo so you have it ready, just incase. 

Thankfully Vienna let you demo VE pro 7 for 30 days so you can see how it performs for you in your studio. No need to be nervous. :)

Just double checking, but you right clicked on a single greyed out plugin and rescaned it individually? This actually worked for me and all my greyed out plugins are now working on my PC.

Just double checking, you are indeed running the server application and NOT the one simply named Vienna Ensemble Pro, but the one named Vienna Ensemble Pro Server, correct? 

Confused with what you mean by "uninstall leaves damage." I uninstalled VEP7 and went back to VEP6 many times during the beta period. As long as you dont save your VEP6 projects in VEP7, you can always roll back. Just use the uninstaller in your VE Pro application folder and reinstall as necessary. 

My name is Jon, and I'm a plugin junkie. In Cubase, this is fine as I can organize my plugins and even search for individual plugins by name. But unfortunately VE pro shows everything in one giant list organized by vendor, and this really hurts my productivity when I want to quickly add my favorite EQ, compressor, distortion, etc.

I really hope VSL will implement a user controlled organizational system, but in the mean time, are there any work arounds? I was thinking I could duplicate only my most used plugins into a new folder on my HD, and then direct VE pro to only scan that folder and not my normal components or VST folders, but on my Mac it seems I cannot direct a custom location for my plugins. 

Anyone else also have this frustration? Find any solutions? (even if the answer is no, if you feel frustrated as well please reply so VSL know this is an issue that should be addressed. Thanks!)

Watching the videos I see that for the string pad + solo patches, its a combination of low pad string chords plus a melody on top in a solo instrument. Is the opposite of this available where you have a high string pad + low solo instrument like cello, bassoon, trombone/horn, etc? 

Looking for clarification on this statement and what it means for users who own the original Chamber strings. At the bottom for the "registered user pricing" list it says the following

** Promotional Offer only available in July, 2018

Does this mean that this registered user pricing complete dissapears at the end of the month? Or does this mean that this specific promotional offer is gone, but there will still be an upgrade path for those who own the original chamber strings + Synchron strings I? I must admit I'm not sold on the new player yet, nor the concept of Chamber strings Synchronized and need more time to make an informed decision. I must admit I'm gunshy on VSL since preorder of Synchron Strings I, but I'm willing to give VSL some room to hopefully address the issues with Synchron Strings I, as this will dictate if I spend any more money on this new line, so I really need to know if this user pricing indeed completely dissapears at the end of the month, or the price will just be higher. 

I hear where you are coming from ZWaves, and I will for sure take your advice of saving individual projects (not just the metaframes) to heart going forward. I do already save multiple backups of my metraframes as I work, but when I first got VE pro I was told by VSL themselves that I should do as much mixing in VE pro as possible as it had better multi-threading than most DAWS (which I later confirmed by my own tests - I can load many more mix plugins in VE pro vs Cubase for example). This unfortunately means when I’m in the heat of writing & mixing, I often make little tweaks here and there as needed (less reverb on the flute in the Woodwind server project, a different distortion on this synth in the “lead synth” project, channel levels in another project, compression settings, etc)  and when making these tweaks, the last thing (for me at least) I'll remember to do is save each individual project, as having to stop and save slows down the creative flow!  In fact, I often rely on the “do you want to save changes” at the end of the day, and have on autosave in VE pro just incase I get a rare crash while working. But these are only saving the metaframe, and if VE pro has a bug where you can no longer click and open specific server projects for some reason, and these un-openable projects are saved with the metaframe, then obviously I will have to starting all individual projects so I can load them as a workaround to this bug going forward, no matter now much extra time it will take at the end of the day to re-save all my projects w/ proper version numbers that correspond to my DAW project files. What a pain, but its better than potentially loosing my ability to work! 

 

Whats odd is this isn’t even my largest VE pro project - I have much larger ones for songs I’m working on. (better knock on some wood, lol)

I really hope VSL chime in. I’ve sent them an official support request when I replied to this thread on the 25th, and as of today I have yet to get a reply. VSL support is usually fantastic and often get back to me the same day, so this has me a bit concerned! 

Made a video where you can see whats happening on my end. Is this the same that is happening to you? https://www.youtube.com/...f-c&feature=youtu.be

Just ran into the exact same issue here. I have my VSL synchron timpani in VE pro instance 1, and I use to be able to open it to make mix changes, turn on the "control me" button for the iOS app, etc, and now when I click on the name of the VE pro project to view it, nothing happens. Even if I try to "raise" from my DAW, that VE pro project will not open in VE pro. 

It use to open fine, so I dont know what has happened. Seems to be a bug to me. Hopefully VSL can chime in as I really need to get it working again and want to avoid having to rebuild from scrach as I'm unsure of the mix changes I made in that individual project! I'm running VE pro 6.0.17011

Did you ever find what works best for you? Curious to know myself. 

Then why is the old VSL Timpani able to have plenty of room on the keyboard for Left and Right hand mapping, but somehow the new Synchron does not? The range of the Timpani is the same!

See linked pictures here: https://www.dropbox.com/s/mssz3clumzy3h0q/VSLTimpaniMapping.png?dl=0
Top = VSL SE Timpani with two hand mapping. Fits great on a keyboard. No issue.
Bottom = Synchron Timpani with one hand mapping and a lot of empty (grey) keys!!

Again I humbly request an updated patch with the synchron timpani mapping matching the previous VSL timpani mapping as seen in my picture above. I'm not saying get rid of the current mapping, but PLEASE add an additional full keyboard / left hand right hand mapping for single hit articulations. Please forward this issue to tech support as I would really appreciate any help on this issue. Thanks.

Thank you for your reply and suggestions. I was hoping to simply be able to perform a 16th note part in a single pass without having to go back and change the programming. Your suggestions of recording octaves and then going back and changing the notes, though a work around, is not ideal as it cannot be done in a single pass. Also rolls will not work as I need the definition of the 16th notes.

The old mapping of right hand and left hands across the keyboard was a great solution to this issue. May I ask why this changed with synchron percussion? Is there a way to make a feature request to have an additional preset patch that has seperate left and right hand mapping, or at least the same mapping but spread across for right and left hand playing? I must admit the current mapping is pretty frustrating and is like taking a step backwards in playability. In fact, I cant think of any other recently released Timpani sample instrument that doesn't have right and left hand mapping. Given the range restrictions of the actual instrument, its not like there arn't enough keys on the keyboard. So I'm a bit confused as to why this change was made. 

Thanks again for your reply. I truly appreciate the help. 

Hopefully this is possible. I'm running the VE pro Synchron Timpani preset with the VI pro instances and routing already set. However the main issue I'm running into is doing fast parts with the timpani spread across only half of the keyboard is very difficult. I'm use to Left and Right hand spread across the keyboard so I can play left and right hand parts with my left and right hand. VSL even did this in the past with older SE timpani, so I'm very use to programming this way. 

Why was this changed with the Synchron Timpani? Is it possible to get seperated Left & Right hands back for Synchron Timpani?

Also while I'm here, is it also possible to mute the open timpani as needed.  For example I want a note to ring out for 2 bars and then muted. Searched the manual but it doesn't say if this is possible. 

Try opening Kontakt as stand alone and make sure its registered. If it is, rescan the plugins in VE pro (choose rescan all) and see if it then shows up. I remember having problems with Kontakt and doing the above and restarting the machine made it work. 

I just updated my VE pro today (for the ability to turn off "Enable midi for muted events" preference among other things) and an unfortunate side effect of this update is a lag/delay when trying to connect to the server from my DAW Cubase 8.5 on Mac OS 10.11.6. When I create a new VE pro instrument in my DAW (Cubase) and hit the "connect" button to connect to the VE Pro 64-bit server, the takes a good 5-7 seconds before I can see my localhost and create a new instance. Once I see <new> and/or unconnected VE pro servers in the list, creating or connecting is instantaneous, its getting to this list where the delay occurs. This happens on blank cubase projects with empty VE pro servers, as well as opening old projects that didn't exhibit this behavior before updating. 

My pervious VE pro version 6.0.16068(64-bit) was instant when connecting to servers, so I dont understand why there is now a 5-7 second delay. The only thing that has changed are my VSL plugins (updated VE pro, VI Pro and Vienna Suite today to the latest versions). 

Any help would be greatly appreciated. Thanks!

I agree to a point, but I must admit I found the virharmonic demo in which he didn't use a single CC or keyswitch to be very impressive. Perhaps its different as a listener as I do not know the composers intent, therefore do not know if it was realized properlly. Perhaps as a compositon tool it would be too frustrating, though its my understanding you can override any automatically chosen performance element, so in a way its like VI-pro and its matrixes, except it will hopefully get you 80% of the way there on the first pass without any setup time. But again, maybe I'm not understanding the instrument fully and would love to hear from you more specifics since you own both. 

Appreciate the discussion BTW. :)

p.s. feel free to PM me if you would rather share your thoughts in private. Again I really appreciate any specifics you can provide as you own both of these tools. Thanks again. 

Wow - so you dont think virtual instruments should behave more like musicians? You think they are mutally exclusive? Isn't that what we are using sampled instruments for in the firstplace, to realize our original music as if it was played by real musicians? I'm confused as to your point I guess. 

Thank you! I would love for you to elaborate a bit more on why you feel this way, as I do feel I'm having a bit of "new car envy," lol. 

Again I respectfully disagree with your stance. If what you said was true, VSL would have never invented the best VI player in the world - they would have never allowed "huminazation functionality" in VI pro, they would have never allow for speed to control playback of different samples and for the many differnet ways to trigger matrixes, not to mention their sequencer in VI pro, etc. They would have left it as one track per sample and thats it, and you would have to play multiple takes on these different tracks, edit these so they are balanced, etc in order to realize a single musical line. ALL these innovations are to make their sample libraries easier to perform, not program. This is the big difference, and again IMO is where the future of sample libraries are going. In fact, VSL already saw this comming to a degree, which is why they added such functionality to VI pro in the first place, no?