196,166 users have contributed to 43,014 threads and 258,394 posts.
In the past 24 hours, we have 0 new thread(s), 6 new post(s) and 170 new user(s).
Hello Paul
Logic 8 has just been released, you can now select Midi 2 in Logic preferences
I am trying to import midi Logic files into Dorico, today it is a heavy work, is it going to simplify it ?
The best result I get is importing XML files but I loose all VI instrument names (do you know a solution to this)
Kind regards
Cyril
Hi Ben
I know that you are not a develloper of Dorico, my question is :
Are VSL Plug-ins going to support Midi 2 ?
If I have understand, MIDI 2 allows bi-directionnal conversation between the DAW and the plug-in as well as many other feature.
So if Logic, Dorico, VSL are all compatible MIDI 2 this should improve our workflow
Today when you import a Logic Midi file into Dorico you lose all the VSL instruments and there setting.
Did I understant the feature of MIDI 2 badly ?
Best
Cyril
@Ben said:
Hi @Cyril Blanc!
We are not the developers of Dorico, that's a question better asked in the Steinberg forum.
MIDI 2.0 has Orchestral Articulation Profiles which are sortof like Studio One Sound Variations, but have standard IDs for things like staccato, legato, pizzicato, etc., which should make it possible to use any library that supports the Orchestral Articulation Profiles without having to create expression maps. So, you could use pretty much all articulations in any string or woodwind or brass library in Dorico without any configuration needed.
These Orchestral Articulation Profiles are still under development, but I'm sure when the spec is finalized, VSL will probably implement it, like they have Sound Variations. It would mean less work for them, since they would no longer need to make "VSL for Dorico", and Cubase expression maps, and the same for other DAWs and notation programs.
I think you will find that MIDI 2.0 has been in Logic Pro since 10.7.7.
@Cyril-Blanc said:
Hello Paul
Logic 8 has just been released, you can now select Midi 2 in Logic preferences
I am trying to import midi Logic files into Dorico, today it is a heavy work, is it going to simplify it ?
The best result I get is importing XML files but I loose all VI instrument names (do you know a solution to this)
Kind regards
Cyril
it has been advertised only with 10.8, and you have it now in the pref
@rAC said:
I think you will find that MIDI 2.0 has been in Logic Pro since 10.7.7.
@Cyril-Blanc said:
Hello Paul
Logic 8 has just been released, you can now select Midi 2 in Logic preferences
I am trying to import midi Logic files into Dorico, today it is a heavy work, is it going to simplify it ?
The best result I get is importing XML files but I loose all VI instrument names (do you know a solution to this)
Kind regards
Cyril
The MIDI 2.0 that is included in these early DAWs is often only really partial or experimental support and not really complete support for MIDI 2.0. Cubase has said they have added support for MIDI 2.0 in the latest version, but it is really just initial support for high definition MIDI CC's (so that you can have up to three decimals after the controller value, ex. 103.267 instead of just 103).
@rAC said:
I think you will find that MIDI 2.0 has been in Logic Pro since 10.7.7.
Just curious, what's the advantage in this case? Even if the resolution is higher, the piano libraries would still have the same number of dynamic layers. And I suspect that 128 different options of velocity are enough that you won't hear the difference for a higher resolution.
i am personally excited about the future of midi 2.0 for a number of reasons. I think it's going to be a very slow and gradual transition and we have to see how it all gets utilized. The daws being able to record midi 2.0 tracks are just a first step, and macOS and windows are also incorporating 2.0 into usb drivers.
As it picks up steam I'm sure we will see plugins begin to provide 2.0 resolution. Obviously more layers of midi velocity are interesting but it's yet to be seen whether people will actually notice the additional resolution other then very few scenarios. I personally think more cc resolution will be noticeable.
all the stuff about articulation management may eventually be helpful but vst3, for example, has already abstracted that behavior a long time ago and there has been very little adoption by plugin devs or daws other then cubase. Steinberg's view is that midi 1.0 or 2.0 should be managed by the daw, not by plugins. Most of the cool 2.0 patch management is more likely to be used between daw and midi controllers rather then through the plugins. But we shall see how it all plays out over time.
i am also excited about time stamping added and looking forward to a future midi network in the studio all connected via 2.0 interfaces which reduce jitter. But so far there are no midi 2.0 interfaces, only a few midi controllers
One thing I have been wondering with regard to the piano libraries is how is it possible to actually take advantage of the resolution at which the instruments have been sampled without a midi 2.0 keyboard or a high resolution keyboard like the Casio PX-5S?
For example, the Bösendorfer Imperial has 4,000 samples per key but how can you make use of that with standard 7-bit velocity resolution?
We're nowhere near the point at which sample player velocity needs or could even benefit from MIDI 2 resolution. Unless of course you happen to have some exotic and very high-price machinery with several TeraBytes of RAM, several dozens of TB of storage, and a very large number of CPU cores that could qualify as an entry-level Supercomputer! And all that's assuming you'll be able to find sample libraries that target such machinery. In short, I'd suggest you don't hold your breath.
Also, using MIDI 2 to enhance the scope and scale of software instrument plugin preset selection and control - already absurdly overdone by developers in that merciless market - is unlikely to be enthusiastically received by seasoned (and jaded) users; more likely by the "more-is-better" and "latest-is-always-greatest" brigades of noobs, bluffers and con-artists.
Even at the specification level it's clear that MIDI 2 has its virtues and it's certainly not short of vices; but these won't be obvious to most folks in the user domain ahead of the few truly talented designers who'll take us all nicely into tomorrow in their own inimitable ways and in their own good time.
Oh but meanwhile, there's always Elon & co who like to pepper their products with what seem to be innovations (but mostly aren't), because hey - how else can they justify their churlishly high prices, keep their cult followers feverishly excited, and bask in all that public adulation? Lol.
+1 for MIDI 2.0
Was long torn between a Roland A-88 MKII and NI Kontrol S88 MK2 and decided for the latter in the (somewhat vain) hope to better use the VSL key switches with the help of jolly colourful LEDs. Now that the NI S88 MK3 is out which both supports MIDI 2.0 and has all three pedal inputs plus Polyphonic Aftertouch I plan to replace the MK2.
I am with dewdman42 and see much benefit from the new capabilities of MIDI 2.0, especially for the interoperation of plug-Ins and DAWs that do not require a transport layer.
The combination of abstraction and playability I am looking for was to some degree covered by the original NI Core product, which got updated to Core 2 to be abandoned later on and then resurrected as Komplete Kontrol. Original NI Traktor also supported OMS, which didn't become widely adapted, and I hope MIDI 2.0 fares better.
Supporting MIDI 2.0 might also help VSL to get out of the narrow corset that the Komplete Kontrol platform poses. Many of the VSL Libraries I have a license for still lack NKS support. How do I make my own?
