'Sib. 2018.x: Managing vsti, routing, templates etc.'

Messages in this thread

Sib. 2018.x: Managing vsti, routing, templates ... - Geir Solerød, 18 Oct 08:14AM
     Re: Sib. 2018.x: Managing vsti, routing, templa... - Robin Walker, 18 Oct 09:09AM
         Re: Sib. 2018.x: Managing vsti, routing, templa... - Geir Solerød, 18 Oct 06:03PM
             Re: Sib. 2018.x: Managing vsti, routing, templa... - Robin Walker, 18 Oct 06:28PM

Sib. 2018.x: Managing vsti, routing, templates etc.
Posted by Geir Solerød - 18 Oct 08:14AM (edited 18 Oct 08:15AM)
Hi!

I make a series of scores, based around vocal soloists, SATB choir, and oboe, violin and piano.
What's in each score changes (as arie vs. ensemble)

I'm using vstis as follows

Solists: Kontakt (1) - Voices of Rapture
SATB choir: Kontakt (2) - Kontakt sounds
Piano (x2-3): Addictive keys

How is midi routing in Sibelius for multi-instruments in a vsti? When adding, changing order and deleting instruments?
First in score is routed as ch1, next as ch2?

How do I save correct midi sound setup for each song? Do I need to save a separate configuration for each song?
(FR: Save this config with project?)
Do you recommend using more native sounds for easier management of this? (Tried the piano, but went back to Addictive Keys as it sounded better)

When starting a new song, how do I best save time keeping staves, config and page-text, yet blanking it out for the new? Right now I delete all, keeping staves, but then page-text is gone as well. And there are a lot of times error in sound-setup.

Thanks!
Back to top | All threads
 
Re: Sib. 2018.x: Managing vsti, routing, templates etc.
Posted by Robin Walker - 18 Oct 09:09AM
> How is midi routing in Sibelius for multi-instruments in a vsti?
> First in score is routed as ch1, next as ch2?

No. See the Sibelius Reference concerning Manual Soundsets: routing is done by SoundID for connecting to channels within a single VST player device. Also see the Sibelius Reference concerning the "Preferred Sounds" part of playback configuration for routing requests between multiple player devices: again the SoundID is used.

> How do I save correct midi sound setup for each song?
> Do I need to save a separate configuration for each song?

You will need to save a separate custom Playback Configuration for each different such configuration, but it is possible that more than one score might be able to share a singe Playback Configuration.

> Do you recommend using more native sounds for easier management of this?

The Sibelius 7 Sounds sample library is easier to use because it has a full SoundSet to automate channel loading, etc. It also automates keyswitches and patch changes for articulations etc. With manual soundsets, you have to do a lot of this work yourself.

> When starting a new song, how do I best save time keeping staves, config and page-text, yet blanking it out for the new?

See the Sibelius Reference concerning Manuscript Papers.

--
Sibelius 2018.7/7.5.1/7.1.3/6.2/5.2.5, PhotoScore Ult 2018.7, Windows 10 64-bit 16GB. Desktop, and Microsoft Surface Book.
Back to top | All threads
 
Re: Sib. 2018.x: Managing vsti, routing, templates etc.
Posted by Geir Solerød - 18 Oct 06:03PM
Thanks a lot!

Does SoundID include midi ch routing for eg Kontakt multis?
Or is there something else?
Back to top | All threads
 
Re: Sib. 2018.x: Managing vsti, routing, templates etc.
Posted by Robin Walker - 18 Oct 06:28PM
SoundIDs are a concept unique to Sibelius, and their scope is limited to Sibelius. They are designed as an abstraction from underlying structures such as MIDI and VSTs, so that (a) a score can be playable in whatever playback environment it finds itself, and (b) a score can be composed and notated without any special content being necessary for specific player devices. The mapping between (a) SoundIDs and score notation, and (b) the underlying MIDI or VST framework, is automatically achieved by special text files called SoundSets. In the absence of these SoundSet files, usage of Sibelius with 3rd-party player devices is quite tedious and involves a lot of manual work by the user.

In the absence of a SoundSet file for the sample library in question, Sibelius knows nothing about the internals of player devices such as Kontakt, and would not know whether it was dealing with a multi or not. All it knows about when talking to Kontakt is channel numbers.

--
Sibelius 2018.7/7.5.1/7.1.3/6.2/5.2.5, PhotoScore Ult 2018.7, Windows 10 64-bit 16GB. Desktop, and Microsoft Surface Book.
Back to top | All threads
 

Quick reply

To add a reply to the end of this thread, type it below, then click Reply.

(.sib, .png and .jpg only)

Messages in this thread

Sib. 2018.x: Managing vsti, routing, templates ... - Geir Solerød, 18 Oct 08:14AM
     Re: Sib. 2018.x: Managing vsti, routing, templa... - Robin Walker, 18 Oct 09:09AM
         Re: Sib. 2018.x: Managing vsti, routing, templa... - Geir Solerød, 18 Oct 06:03PM
             Re: Sib. 2018.x: Managing vsti, routing, templa... - Robin Walker, 18 Oct 06:28PM