I spent a lot of time, learning curve included, building a multi on the Aria Player, intending to use it in Notion as a template for more than one project. I began work on a project and saved the file under another name, but the renamed file wiped out my channel assignments and all the "change instrument" tags I had renamed. So instead of reusing the same multi more than once, looks like I basically have to redo most of it whenever I create a new file.
This is clunky.
Creating an user-defined NOTION score to use as a template that has an Aria MULTI is not so difficult to do--provided you are software engineer and have made sense of busing and routing in the digital music production universe . . .
If I were guessing, then I think the problem you encountered is due to specifying different channel pairs in the Aria MULTI, although another possibility is the way you did channel reassignments in the NOTION score . . ,
I am writing a book about all this stuff, which is coming along nicely and is nearly 500 pages, with only another chapter or two to be finished; and one of the things I realized is that while some of this stuff can appear to be vastly complex, it becomes easy when you understand busing and routing . . .
Even though I have played electric bass and electric guitar for decades, usually with elaborate effects pedals--which requires understanding cables, guitar cords, busing, routing, and so forth--it took me a while to realize that it works the same way with digital music, except that instead of being physical guitar cords and so forth, they are virtual . . .
As a general rule, none of this is explained clearly anywhere, and it certainly was not immediately obvious to me; but it eventually started making sense, which for MIDI required taking some courses from Groove3 and macProVideo, which were very helpful and reasonably priced . . .
For the most part, none of this stuff is documented anywhere other than in this forum and soon to be in my book on digital music production, so it usually takes folks a while to make sense of stuff like this, which typically is very frustrating until you realize that it's all new information and overall doing digital music production is on par with flying a spaceship or running a Fortune 100 corporation in terms of complexity . . .
In other words, what you are doing maps to a recording session for Frank Sinatra, Elvis Presley, or the Beatles where you are doing everything, including managing the microphones and instrument cables, and everything else; so yeah, it's super complex, but it's not more super complex than when it's done at Capitol Records, Sun Records, or Abbey Road Studios . . .
You need to know everything everybody in the recording sessions did, and you probably need to compose the music, as well . . .
That's a lot of stuff . . .
HOW TO PROVIDE THE SOLUTION
There are two things that need to happen:
(1) Create the Aria MULTI and give it an unique name so you can reuse it easily,
(2) Do the channel assignments in the NOTION score and then save the NOTION score so you can use it as a user-defined template.
The word "channel" is used in a variety of ways, where the key bit of information is that what in the Aria player is called a "channel" is not the same as a channel within a bus for routing audio to NOTION is concerned . .
The simple version is that all the instruments in the first Aria MULTI need to be set to "1-2", since Aria sends them to NOTION on the "1'2" bus, virtual cable, or whatever one wants to call it . . .
In other words, all 16 instruments loaded in the Aria MULTI are sent to NOTION in what NOTION understands by default is "1-2", yet within NOTION the "1-2" bus, cable, or whatever will have 16 channels . . .
If you prefer, the "1-2" channel in Aria has 16 "channels" of instrument audio that it sends to NOTION . . .
Making this all the more circular, if you have several Aria MULTI instances, then they also send their instrument audio via the same, high-level "1-2", although it's probably possible to do this on the other high-level "big cable thingys", but I had not done experiments to discover this . . .
My general strategy is to avoid wandering into the MULTI world, but it's something I can do and perhaps makes a bit of sense . . .
Here in the sound isolation studio, I do everything in ReWire sessions with Studio One Professional and NOTION in ",song" layers with 10 to 20 instruments, each of which is a singleton, meaning that if I have 10 Aria instruments, I will have 10 instances of Aria, each with only one instrument, as I do with SampleTank (IK Multimedia), Kontakt (Native Instruments), MachFive 3 (MOTU), and Play (EWQL) . . ,
It's primitive; it works for me; and I think it's easier to understand and map, but so what . . .
The reason I do it this way is based on creating songs with the layer strategy, which there is a basic rhythm section layer for drums, bass, rhythm guitar, and keyboards usually playing chords . . .
When I am happy with the basic rhythm section, I record the audio and then do a submix to consolidate it to a smaller number of tracks--perhaps one for drums, one for bass, and so forth--except I do everything in pairs of tracks or triples of tracks for panning purposes (far-left, center; far-right), although these are the individual instrument tracks, which then as a layer are consolidated to one stereo track . . .
Everything does not need to be super-consolidated; and since I focus on what one might call "popular music", I like to have dual kick drums, dual snare drum rimshots, dual or triple rhythm guitars, and so forth, but usually only one electric bass, which is panned top-center . . .
You can see and hear this in my projects in this forum . . .
I created an Aria MULTI and used it in a NOTION score, which I saved as a template and then used the template to create more songs via opening the NOTION score and immediately doing a "Save As . . . ", which is what I think you want to do . . .
At first, I set each instrument in the Aria MULTI to a different channel pair, but it only worked for the instrument set to "1-2",; hence after thinking about it for a while, I set all of them to "1-2", and then it worked as expected and desired . . .
It's explained in the YouTube video (see above) . . .
Lots of FUN!
I read the original post a few more times, and this is a follow-up post with more information . . .
After thinking about it and reading the original post a few more times, I think there is another aspect to the problem, which is due to thinking that an Aria MULTI will provide meaningful names to the staves in a NOTION score, which as best as I can determine it will not do . . .
You can create an Aria Player MULTI and give it an unique user-defined name, but this is not going to map to each of the corresponding staves in the NOTION score having meaningful names . . .
The meaningful names in the NOTION score come from doing something in NOTION rather than in the Aria Player MULTI . . ,
After years of working with NOTION where NOTION was hosting the VSTi virtual instruments, I decided that it's easier to work in a ReWire session where Studio One Professional is the ReWire host controller and hosts the VSTi virtual instruments, while NOTION is a ReWire device running under control of Studio One Professional in its role as ReWire host controller, with the NOTION score comprising a set of ReWire MIDI staves , , ,
In this strategy, NOTION is focused on music notation and MIDI, which it creates and sends to Studio One Professional to be played by VSTi virtual instruments hosted in Studio One Professional . . .
It is similar to doing everything in NOTION, but if you are not using NOTION for real-time performances, then I think the ReWire MIDI Strategy is best, and it certainly is less complex than doing everything solely in NOTION . . .
It might be nice if an Aria MULTI could provide meaningful names for NOTION staves, but as best as I can determine this is not the way it works . . ,
One might suppose it's possible to create a single NOTION score with 100 to 200 staves of instruments, but when the VSTI virtual instrument engines are hosted in NOTION, this will be troublesome regardless of whether Aria Player MULTIs are used . . .
It is possible to have that number of ReWire MIDI staves in a NOTION score, since in the ReWire MIDI Strategy, NOTION is focused on music notation and MIDI, since NOTION is not hosting any VSTi virtual instruments and VST effects plug-ins . . ,
On the Studio One Professional side, I find that creating layers with 10 to 20 instruments works nicely and does not overload Studio One Professional, with this including some number of VST effects plug-ins, as well . . .
In other words, instead of trying to put everything in one NOTION score and one Studio One Professional ".song", it works better to work in layers, as explained in my previous post to this topic, although there actually will be one Studio One Professional ".song" that has more Audio Tracks as the layers are consolidated and submixed . . .
Create a layer and when happy with it, do some submixing and consolidation, followed by saving everything to a common folder for the song; zapping the first set of Instrument Tracks and replacing them with a new set of Instrument Tracks for the next layer, and so on--consolidating and submixing along the way, always keeping a logical named archive for the steps so you can backtrack when desired but otherwise go forward . . .
It takes a while to do all the configuration and setup work required for a reasonably complex song, and this can take a few hours overall, even when you have custom user-defined templates, user-defined presets, and so forth for VST effects plug-ins . . .
You might think it's a lot of time and a lot of work, but rollback the clock 50 or so years, and there were no personal computers, no digital music production applications, and everything was analog done with electromagnet tape machines in recording studios that cost millions of dollars, which restricted them to use by well-funded musical groups . . .
Configuring everything for a Beatles recording session probably require 10 to 15 people and a few hours, unless there was a symphony orchestra scheduled, in which case the number of people increased dramatically . . .
Most composers and musicians did not have access to that level of recording technology, because it cost too much . . .
Now, at the dawn of the 21st century, you can do everything with $10,000 to $25,000 on a computer in a walk-in closet or inside a Lincoln Towncar if you have a notebook computer and an AC converter to run the external digital audio and MIDI processor . . .
If it requires several hours over a few days to configure everything, perhaps one instrument at a time, this is fine with me, because I can do only one thing at a time no matter how it's done . . .
If it required one hour and 10 people to do the setup work for a Beatles recording session and I can do the same work in 5 hours, then great . . .
I am glad just to be able to do it without needing to be a hit recording artist or a millionaire . . .
And you can create your system in steps, getting virtual instruments and effects plug-ins a few at a time as your budget allows, and so forth for everything else . . .
It's at least the same quality and usually is higher quality than the multimillion dollar recording studios of half a century ago ()or longer) . . .
FACT: Doing elaborate and complex things requires a bit of work, some of which cannot be avoided.
Lots of FUN!
Thanks for the suggestions, and especially for reading my post again and following up.
I was writing from the perspective of being able to stay entirely in Notion, since the basic purpose of Notion, for me, is composition, and the template would be for being able to quickly begin working on a new idea. You're probably in the majority of people who now use Notion in tandem with Studio One, and your suggestions only work that way. You couldn't route everything to the 1-2 channel in the player and come out right working in Notion alone.
I do own Studio One and have used it some for the later stages of my process, but I haven't upgraded to the new version yet. I like the simplicity of Notion and if I want to continue that way it would be much easier just to load up several players, choose the instruments and save the file, and that way everything [would] read right on the score.
But if what read about the score editor in the new Studio One is true, it begs the question why you wouldn't start from scratch over there.
thomasbaxter wroteThanks for the suggestions, and especially for reading my post again and following up.
I did a few more experiments and encountered the same problem I think you encountered . . .
For reference, at present I am using Aria Player v1.620, and it definitely gets confused . . ,
It's not a problem caused by NOTION . . .
I did another set of experiments where I used SampleTank 3 (IK Multimedia) and created a MULTI for drums and a MULTI for bass and guitar--all with no problems loading, reloading, and so forth , , ,
Each SampleTank 3 MULTI remembers itself and does not become confused . . .
The NOTION score where I used the two SampleTank3 MULTIS does not become confused, and it remember the meaningful names . . .
If I can download a newer version of the Aria Player, I will do experiments to see if the bug has been fixed . . ,
For reference, the Aria Player I am using now came with Finale that I purchased in 2012, so it's a bit old . . .
UPDATE: I tried downloading and installing Aria Player 1.872 and 1.959, but the require a newer version of the Aria Engine, hence do not work here in the sound isolation studio , , ,
If I can find a new version of the Aria Engine, perhaps I can continue experimenting . . .
UPDATE: I found the Aria Engine update, but it doesn't work, so there's not much I can do other than suggest it's a problem with the Aria Player and Aria Engine--not NOTION, which I suggest because it works nicely with SampleTank (IK Multimedia) MULTIS saved in NOTION scores . , ,
I encountered the same or similar problem, so if you are using a newer version of the Aria Player and Aria Engine, then it's probably a problem that has been around for years and nobody used MULTIS enough to encounter it and report it . . .
If the problem has been fixed in a new version, then the steps in my previous posts to this topic should work--they work with SampleTank3 MULTIS . . .
Creating a NOTION score with several VSTi virtual engines, each with one or more MULTIS is a relatively normal thing to do, and when the VSTI virtual engines are working correctly there are not problems . . .
I generally avoid MULTIS, but I have a few user-defined MULTIS in SampleTank and MachFive 3 (MOTU) and use them for certain styles of songs . . .
ANOTHER CONSIDERATION ~ LIMITED OR CUMBERSOME SOLOING
If you do this in NOTION, then you only can solo the original Aria Player instances, not the staves redefined via Change Instrument (SHIFT+i) . . .
This also is the case in the ReWire MIDI Strategy, hence limited soloing in the mixer is a drawback . . .
You can solo instruments, but it has to be done in the Aria Player, which is cumbersome . .
For a variety of reasons, I stopped messing with stuff like this and decided to use one instance of a VSTi for one instrument, although sometimes I have cymbals and hi-hats on the same staff running off the same instance, but mostly when I am too lazy to create separate instances for hi-hats and cymbals. And I do this with cowbells on the snare drum staff, as well . . ,
Lots of FUN!
Users browsing this forum: No registered users and 4 guests