Anyone using Spitfire UACC KS?

tack

Damned Dirty Ape
I'm wondering if anyone here has successfully incorporated UACC KS into your templates? I'm pretty sure that some libraries (definitely Horns and Low Brass) are pretty hopelessly broken with UACC KS as there seems to be some improper interaction with CC1 that causes a UACC KS note to sporadically select the wrong articulation.

Before I send a bug report to Spitfire I wanted to know if anyone here using a BML heavy template was using UACC KS without issue.

UACC (non-KS) works ok, but this has a number of disadvantages to UACC KS, so I hate to give up so easily.

Thanks!
 

kunst91

Senior Member
I'm wondering if anyone here has successfully incorporated UACC KS into your templates? I'm pretty sure that some libraries (definitely Horns and Low Brass) are pretty hopelessly broken with UACC KS as there seems to be some improper interaction with CC1 that causes a UACC KS note to sporadically select the wrong articulation.

Before I send a bug report to Spitfire I wanted to know if anyone here using a BML heavy template was using UACC KS without issue.

UACC (non-KS) works ok, but this has a number of disadvantages to UACC KS, so I hate to give up so easily.

Thanks!
I'm curious, what are the disadvantages to regular UACC? I have a full BML template and change articulations quite easily.

I have never tried UACC KS, but I think the problem lies in the fact that UACC was designed to be used in its "pure" form, and this is what I would recommend.

I know that doesn't answer your question (sorry!), but I would recommend looking into the standard UACC--I imagine that is where spitfire will devote the preponderance of their attention.
 

Svakenakis

New Member
I'm wondering if anyone here has successfully incorporated UACC KS into your templates?
I'm having similar issues with Locked to UACC as well. I have created a set of hardware switchers mapped to Mural Vol.1 Violins with Locked to UACC enabled. After that I hopped that I can use my UACC preset with the Violas when I select the Violas MIDI Track. However I noted that the Pizzicato switching #61 does not work with Violas. I tweaked another CC32 fader to find out the Pizz UACC #, so I found out #56.
Same issues with "Sul Pont" which are recalled via #4 for the Cellos & Basses according to the official UACC online document but for the 1st Violins "Sul Pont" is recalled via #81. All Instruments are Locked to UACC in my case. It seems that UACC is not such universal as should be or I'm missing something?
 

kunst91

Senior Member
I'm having similar issues with Locked to UACC as well. I have created a set of hardware switchers mapped to Mural Vol.1 Violins with Locked to UACC enabled. After that I hopped that I can use my UACC preset with the Violas when I select the Violas MIDI Track. However I noted that the Pizzicato switching #61 does not work with Violas. I tweaked another CC32 fader to find out the Pizz UACC #, so I found out #56.
Same issues with "Sul Pont" which are recalled via #4 for the Cellos & Basses according to the official UACC online document but for the 1st Violins "Sul Pont" is recalled via #81. All Instruments are Locked to UACC in my case. It seems that UACC is not such universal as should be or I'm missing something?
I would file a support ticket with spitfire. There have been similar problems with UACC in the past, and they are typically good about dealing with them quickly (although with Albion one coming soon I'm not sure if they'll have the time).

I'll also ask, do you have the latest update for mural? Because I have found spitfire strings to be the most stable with regard to UACC.
 

Ryan

Senior Member
I use a BIG template with Spitfire Audio stuff only. The UACC are still not corresponding correctly I have also done some test-drives with the UACC-KS, and so far I think they both need some more work under the hood. I have on the other hand, decided to use both UACC and the old-school way of switching articulations.

Right now I'm doing a new install of Windows 10 on my DAW. if you are interested, then I could make a video of my template with the expression setup inside of Cubase.
Check out my youtube:
https://www.youtube.com/user/Ryanfilmscores/videos

Best
Ryan
 
OP
tack

tack

Damned Dirty Ape
I'm curious, what are the disadvantages to regular UACC? I have a full BML template and change articulations quite easily.
Sometimes it's nice to be able to layer articulations. With keyswitches, you can do this by pressing and holding multiple keyswitches at the same time, and UACC KS supports this too. UACC doesn't support this. (It could in theory, using CC value 0 to act as a "note up" which would be compatible with Touch OSC, but it doesn't work like this today.)

Also, at least in my DAW (Reaper), I haven't been able to find a clean way of managing UACC events. CC events don't register while step recording, so I can't easily insert a UACC event via my usual way (Touch OSC). Instead I seem to have to dial it in manually which is quite cumbersome (at least in Reaper). Also the way Repear shows CC events, the lower value UACCs are barely visible.

On the whole, UACC is quite unpleasant to use in Reaper. If anyone has any tips in this regard I'd be very interested.

UACC KS is much nicer to use, except for the small problem that it is terribly broken in multiple libraries. I'll file a bug report with Spitfire, but this doesn't do me much good in the medium term.

I suspect I'll end up using a custom solution, one or both of Kontakt multiscript and Reaper scripts.
 
Last edited:
OP
tack

tack

Damned Dirty Ape
I tweaked another CC32 fader to find out the Pizz UACC #, so I found out #56.
Same issues with "Sul Pont" which are recalled via #4 for the Cellos & Basses according to the official UACC online document but for the 1st Violins "Sul Pont" is recalled via #81. All Instruments are Locked to UACC in my case. It seems that UACC is not such universal as should be or I'm missing something?
What you're missing is that the link you referenced (and indeed the top hit on Google) is out of date. Spitfire does us all a disservice by keeping that page active.

This document is the v2 spec which supersedes the page on Spitfire's website:

https://spitfire-webassets.s3.amazonaws.com/pdfs/UACCv2spec.pdf
 
OP
tack

tack

Damned Dirty Ape
Did up a quick screencast showing the UACC KS bug. I'll fire this off to Spitfire.

 

gbar

Active Member
Sometimes it's nice to be able to layer articulations. With keyswitches, you can do this by pressing and holding multiple keyswitches at the same time, and UACC KS supports this too. UACC doesn't support this. (It could in theory, using CC value 0 to act as a "note up" which would be compatible with Touch OSC, but it doesn't work like this today.)

Also, at least in my DAW (Reaper), I haven't been able to find a clean way of managing UACC events. CC events don't register while step recording, so I can't easily insert a UACC event via my usual way (Touch OSC). Instead I seem to have to dial it in manually which is quite cumbersome (at least in Reaper). Also the way Repear shows CC events, the lower value UACCs are barely visible.

On the whole, UACC is quite unpleasant to use in Reaper. If anyone has any tips in this regard I'd be very interested.
.
IMHO, it's geared toward Cubase users. Expression maps are the key, I expect. Not that I have that experience because I use Sonar, and Cakewalk ignores everybody asking for expression maps.
 
OP
tack

tack

Damned Dirty Ape
tack -- thanks for video but you nearly destroyed my speakers! Cheers
Yeah, sorry about that. I'll pay more attention to mic placement next time. I usually try to find a way to avoid speaking during these things. :)