Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Finale CC7 - Master Volume moves but why
Last post Thu, Mar 10 2016 by fratveno, 15 replies.
Options
Go to last post
Posted on Tue, Feb 02 2016 01:38
by SonicSonar
Joined on Mon, Sep 17 2012, Posts 62

Hello all,

I am able to get VSL work in Finale with the Keydump.  It seems sometimes when I use the CC1 to change the Y-axis, it also changes CC7 which is the master volume.  Why is that?

I am using VSL Dimension Brass.

 

Thanks

Windows 10
128 gig ram
i7 6850

Cubase 10
Finale 26
Posted on Tue, Feb 02 2016 02:24
by bogdan
Joined on Fri, Apr 18 2008, Canada/ Brockville, Posts 271

Hi SonicSonar,

I think you might want to look under the Preferences -Human Playback and check if the Dynamic Aproach for Sustaining Instruments are set to Automatic ( play around with those tab options to find your best setting). And also you could check under VI (pro or not) if your volume and Y axis are not asign to the same controller..I doubt that but check !

All best,

Bogdan

Posted on Sat, Feb 13 2016 17:35
by SonicSonar
Joined on Mon, Sep 17 2012, Posts 62

A way around this issue is set the Human Playback to none.  Somehow the "Standard" setting of the Human playback messed with CC7.  I still don't know the root cause.

Windows 10
128 gig ram
i7 6850

Cubase 10
Finale 26
Posted on Sat, Feb 13 2016 18:37
by Bill
Joined on Fri, Sep 23 2005, Berkshires, MA, Posts 970

Finale sends out a barrage of CCs when you start playback. Rather than tuen HP off, you can just use the MIDI to and put the beginning values you want at the start of the first measure.

Finale 25, Sibelius 2018, Notion 6, Overture 5, Cubase 10.5, StaffPad
Win10 x64, 32GB RAM; Focusrite Scarlett 18i20
Kontakt, Bunch of VSL, VIP, VEP, EWQL Orch, Choir and Pianos
August Forster 190
Posted on Sun, Feb 14 2016 13:08
by winknotes_282
Joined on Mon, Dec 23 2002, Posts 189

Make sure you download the Human Playback Preferences for Finale Special Edition file.  I realize you're not using a Special Edition library, but it changes things like which controller to use for sustaining instrument volume.  I'm not sure if it's the same for Finale 2014.5 but 2012 has 3 options I believe.  CC7+velocity, CC11+velocity and CC1+velocity.  Something like that anyway and you'd want to choose CC11+velocity since that's the default for VSL. 

Steve
Windows 7 Pro 64-bit
Finale 2011, 2012c
VSL SE
Posted on Wed, Feb 17 2016 13:33
by SonicSonar
Joined on Mon, Sep 17 2012, Posts 62

Yes, editing the HP playback pref seems to do the trick.  CC#11+ velocity  was probably the solution.

 

It works now.  And if it happens again, I know where to look.

Thanks

Windows 10
128 gig ram
i7 6850

Cubase 10
Finale 26
Posted on Thu, Mar 10 2016 08:41
by fratveno
Joined on Thu, Dec 01 2011, Posts 41

Originally Posted by: SonicSonar Go to Quoted Post
It seems sometimes when I use the CC1 to change the Y-axis, it also changes CC7 which is the master volume.  Why is that?

This is a bug in Finale (all versions since 2012 at least) with all dynamic alternatives. CC1 is ok when used within the HP techniques, but when sent as an expression (dump) use another CC, like 3...

Posted on Thu, Mar 10 2016 13:56
by winknotes_282
Joined on Mon, Dec 23 2002, Posts 189

Hmmm.  I wasn't aware of that bug.  That's interesting though because when I use the keyswitches the Vienna team provided Finale seems to confuse CC11 with CC1.  In other words when I use a keyswitch to do a keyswitch/CC1 patch change it also sends the same value to CC11.

Steve
Windows 7 Pro 64-bit
Finale 2011, 2012c
VSL SE
Posted on Thu, Mar 10 2016 14:34
by andi
Joined on Wed, Feb 18 2004, Vienna, Posts 3266

Hello fratveno and winknotes 282!

I can't reproduce the CC1/CC7/CC11 confusion here with Finale 2014.5. I remember that Finale mixed up CC7 and CC11 in an earlier version, but I'm not sure which version that was exactly. Anyway, this is fixed with Finale 2014.5 - at least on my computer.

Best regards,
Andi

Andreas Olszewski
Vienna Symphonic Library
Posted on Thu, Mar 10 2016 14:59
by winknotes_282
Joined on Mon, Dec 23 2002, Posts 189

I'll likely upgrade to 2014.5 in the next few weeks and hopefully that will take care of some of these issues.  Thanks for checking Andi.  I appreciate your diligence and patience with us. 

Steve
Windows 7 Pro 64-bit
Finale 2011, 2012c
VSL SE
Posted on Thu, Mar 10 2016 18:46
by fratveno
Joined on Thu, Dec 01 2011, Posts 41

Originally Posted by: andi Go to Quoted Post
Hello fratveno and winknotes 282!

I can't reproduce the CC1/CC7/CC11 confusion here with Finale 2014.5. I remember that Finale mixed up CC7 and CC11 in an earlier version, but I'm not sure which version that was exactly. Anyway, this is fixed with Finale 2014.5 - at least on my computer.

Best regards,
Andi

Oh, but that's not the bug I was referring to!  The CC7 and CC11 mixup is fixed in 2014.5, but not the bug I described, namely, CC1 data sent as expression dumps (in order to navigate the Y-axis) hijacking both CC11 and CC7 data...

Posted on Thu, Mar 10 2016 19:13
by andi
Joined on Wed, Feb 18 2004, Vienna, Posts 3266

Hello fratveno!

I can't reproduce such a behaviour here. If you want to, you can send your Finale file to and I'll look, if I can reproduce it then. Please include information about the exact Finale version your are using and the OS you are working under.

Best,
Andi

Andreas Olszewski
Vienna Symphonic Library
Posted on Thu, Mar 10 2016 19:31
by fratveno
Joined on Thu, Dec 01 2011, Posts 41
Hi Andi,

The bug has been documented, and has been acknowledged by Makemusic, as late as December 2015.

Best,
Posted on Thu, Mar 10 2016 19:46
by andi
Joined on Wed, Feb 18 2004, Vienna, Posts 3266

Ok, but the problem didn't occur here on my Windows 7 computer with Finale 2014.5. Anyway, good to know that Makemusic looks into it.

Best,
Andi

Andreas Olszewski
Vienna Symphonic Library
Posted on Thu, Mar 10 2016 22:37
by fratveno
Joined on Thu, Dec 01 2011, Posts 41

Frankly, I don't think there's anyone left at makemusic who understands the inner workings of human playback. The blunders around the release of GPO5 supports this theory. Anyway, the bug is easily reproducible, I'll send you the recipe when back in the studio.

ciao,

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.