Menu
What's new
By:
Filters

About Update of Noteperformer 4 ?

@Wallander, do you plan to include Synchron Duality Strings?

Also, Synchron libraries are so full of options regarding the articulations that I wonder if you plan to include them somehow or if you plan to enable that CC option you enabled for portamentos?

Thank you!
 
I'm hoping @Wallander includes smaller libraries for NPPE support like collections of solo instruments with a smaller RAM footprint rather than full orchestras. The currently supported NPPE libs have very large RAM requirements and of course not everyone using NP is using it for Hollywood style scores with full blown orchestras. I'd love to be able to mix and match smaller ( and less pricey libs ) I have like LASS First Chairs, VSL Special Editions, and Chris Hein woodwinds for example which I use to write for smaller ensembles.

NPPE is such a great idea and am really looking forward to where it's headed with a variety of libs being supported. That will definitely determine my lib buying decisions!
 
Last edited:
Ivan Duch said:
@Wallander, do you plan to include Synchron Duality Strings?

Also, Synchron libraries are so full of options regarding the articulations that I wonder if you plan to include them somehow or if you plan to enable that CC option you enabled for portamentos?

Thank you!
Click to expand...
Duality Strings is an interesting library that we definitely don't rule out supporting at some point.

There are no guarantees that we will support additional articulations beyond those supported today. It's in the idea basket. That said, we already support most articulations that are practical to support, e.g., in Synchron Strings Pro. Articulations left out are mainly articulations with overlays, runs, swells, measured tremolos, and other tempo-aligned techniques that are only valid at a given tempo or context. For example, here's the upcoming articulation list for Synchron Violins 1:

long, long (non vib), long (molto vib), legato, legato (non vib), legato (molto vib), legato (portamento), staccato, staccatissimo, pizzicato, snap pizzicato, col legno, tremolo, trill (minor), trill (major), sul ponticello, sul ponticello (short), sul ponticello (tremolo), harmonics, harmonics (tremolo)
 
joebaggan said:
I'm hoping @Wallander includes smaller libraries for NPPE support like collections of solo instruments with a smaller RAM footprint rather than full orchestras. The currently supported NPPE libs have very large RAM requirements and of course not everyone using NP is using it for Hollywood style scores with full blown orchestras. I'd love to be able to mix and match smaller ( and less pricey libs ) I have like LASS First Chairs, VSL Special Editions, and Chris Hein woodwinds for example which I use to write for smaller ensembles.

NPPE is such a great idea and am really looking forward to where it's headed with a variety of libs being supported. That will definitely determine my lib buying decisions!
Click to expand...
NotePerformer 4.2 will support SYNCHRON-ized SE1. It's very lightweight, around 3 GB RAM for a full template.
 
Last edited:
Wallander said:
NotePerformer 4.2 will support SYNCHRON-ized SE1. It's very lightweight, around 3 GB for a full template.
Click to expand...
That's great. I'm so enjoying Noteperformer/NPPE that my next purchases are based on your support of the libraries. Is there anyway you can let us know what will be included (specifically) in the next update. The big EDU discounts will be ending soon and I'd like "stock up" if possible.
 
fratveno said:
Can you say how/what in Musio is supported? (I'm on cabled hi speed net this week only 😄 )
Click to expand...
The Cine series, similarly to the Kontakt engine:

NotePerformer 4

NotePerformer 4 is the Artificial Intelligence-based orchestral playback engine for Sibelius, Finale & Dorico.
noteperformer.com noteperformer.com

Still, it's much more convenient to let Musio automatically download the patches the first time you load Cine for Musio in NPPE.
 
Last edited:
Tilt & Flow said:
That's great. I'm so enjoying Noteperformer/NPPE that my next purchases are based on your support of the libraries. Is there anyway you can let us know what will be included (specifically) in the next update. The big EDU discounts will be ending soon and I'd like "stock up" if possible.
Click to expand...
Only the engines mentioned on this page. I don't want to say too much about it since engines can still be postponed, or instruments removed if they don't work properly. I'm fully confident about the Synchron Series, SE1, and Cine for Musio.
 
Wallander said:
Only the engines mentioned on this page. I don't want to say too much about it since engines can still be postponed, or instruments removed if they don't work properly. I'm fully confident about the Synchron Series, SE1, and Cine for Musio.
Click to expand...
Got it. Thanks. Looking forward to the Synchron Series!
 
wcreed51 said:
Will the full Elite Strings work with the SS Pro engine? The VSL Dorico template uses the same xmap for both...
Click to expand...
Not for the time being, sorry. I'm not yet sure how we'll arrange the additional Synchron collections, e.g., Duality, Elite.

We added the Elite expansion to Prime because it's included in the same VSL product. Still, that's only a subset of Elite with one microphone and fewer articulations.
 
Hello Arne,

Impatient for the release of the next NPPE update, do you have a release date to share with us?
Thank you again for your excellent work as it is a huge weight being lifted for creativity...
 
POTTIER said:
Hello Arne,

Impatient for the release of the next NPPE update, do you have a release date to share with us?
Thank you again for your excellent work as it is a huge weight being lifted for creativity...
Click to expand...
I don't have a date, sorry.

I must rework SSO to avoid the problematic patches. Since that was required, and the Studio Orchestra had to be postponed, I decided this update will also have the new model for balancing sounds against NotePerformer. The current model always had problems with boominess which are resolved by this. I don't want to rebuild SSO against the old model. Although straightforward, it requires manual work with all the engines.
 
wcreed51 said:
I don't suppose any of the Synchonized libraries will get engines (like solo strings)?
Click to expand...
Possibly, yes. The next update will support SE1, which has solo strings, although not as encompassing. Part of that process was creating a workflow for dry libraries, which we have now.

It’s done by an IR-based simulation of Close-Main-Ambient. It’s a triangular controller like the multi-microphone libraries, but it uses impulse responses.
 
Ivan Duch said:
Thank you for answering.

Yes, the way you're handling the portamentos is great, that way one can create the required articulations within Dorico (not sure if it's possible in Sibelius in such a way).

I guess these would be tools for users who are fine with tweaking and creating their own expression maps within the notation app (normally people used to DAWs). The benefit to having Noteperformer able to access these articulations is that the user doesn't need to have extra staves for the instrument to access the articulations nor have to load the Spitfire Player twice (or Kontakt, Synchron, or whatever), saving on resources.

So, if you feel like adding CCs + certain values is an easy thing for you to do, it'd be amazing.

I use the BBCSO tenutos and marcatos for certain phrases or repeated patterns like chords being played in quarter notes. On my end the tenutos seem to have a release, though. And the marcatos for the woodwinds, brass and solo strings have round robins and more than one dynamic layer.
Click to expand...
I gave this another attempt. The NPPE technologies are much better now than when I initially tried the marcato approach. I found a path to successfully employ longer shorts (e.g. marcato) for many instruments.

It will be in 4.2, but unfortunately, I don't have a timeline.
 
Last edited:
Wallander said:
I've given this another pass. The NPPE technologies are much better now than when I initially tried the marcato approach. I found a path to successfully employ longer shorts (e.g. marcato) for many instruments.

It will be in 4.2, but unfortunately, I don't have a timeline.
Click to expand...
Thanks a lot for looking into this! I think having those extra resources can help a lot. I'm really hyped about the upcoming release.
 
@Wallander, you mentioned you were integrating Musio. Two questions:

Will the purchase of the current cinesamples engine give access to the Musio engine?

And, how is Musio handling resources compared to Kontakt?
 
Ivan Duch said:
@Wallander, you mentioned you were integrating Musio. Two questions:

Will the purchase of the current cinesamples engine give access to the Musio engine?

And, how is Musio handling resources compared to Kontakt?
Click to expand...
We don't have anything like that in place since the engines were created separately and are two very different libraries from our point-of-view. Still, we're flexible. If you email support, we can transfer the Kontakt Cine NPPE engine into the Musio Cine engine, if you'd rather have the Musio engine.

For most people, the Musio engine supports a greater selection of sounds they have access to. On the other hand, the Kontakt engine has microphone positions and performance legato that are very difficult to support, which is also why the price is higher for some engines.

Musio is extraordinarily optimized. On my M1 machine, the full Musio Cine template loads in less than five seconds and uses around 10 GB of RAM in total. The Kontakt engine uses 50+ GB and takes a few minutes. Unfortunately, there’s a penalty to using multiple instances of a sound in Kontakt.
 
Last edited:
You must log in or register to reply here.
Top Bottom