Kingery

By the way, where is this in the manual?

Ahhhhhh. Most interesting. Ok. I think I can live on, HAHA. Thanks again.

Everything seems to be fine. Visually, there appears to be a difference between Absolute and Relative, but switching between them, both are +0.0. I've attached another screen shot. You can see the absolute volume line in yellow (rather faint) is a bit higher than the Relative line. But according to the fader and the "trim" both are 0.0. Any clue why the visual difference? I guess it doesn't matter, just one of those geeky things that bug me.

Ok, thanks. I'll check it tonight

Thank you for the response. I do find it interesting that when I switched to the volume inside the main, the resulting automation line that appeared was a few db lower than the original volume (from 0db down to -5db). I guess that is in reference to what you said about absolute volume and how it works. Thanks again.

I'm either just noticing this or it's something relatively new. In the screenshot, the automation menu has a Volume selection. If you open the MAIN selection there is a second choice of Volume with the two options of absolute and relative. So, what's the difference between the first Volume in the automation window and the second Volume inside the MAIN selection (excluding the two additional options). Is the first one for track only? The second for Region only? Why two choices of Volume? I looked at the online manual and couldn't locate an explanation. Thanks!

When you have the plug-in open in plug-in mode in the MCU/Extender, the flip does as I said. Everything flips to the faders of course, and yes, the fader will work the gain control. But, when you go back to track mode, the channel fader reverts back to it's original role. It ignores the plug-in automation and only reflects the "volume" automation level. What I what to do is reassign the plug-in automation to the fader in Track Mode. If that is even possible. I'm not sure how to explain it as clearly as I would like.

I think I did that, but it didn't seem to work as I recall. In addition to the gain control, the plug-in has all of the EQ, compressor and gate controls as well. I think what happened was — and I could be wrong — everything flipped. So fade one was the high pass filter, etc. I'll try it again later today and see.

This is one of those "I have too much time on my hands" questions, but humor me, please. I'm using the SSL Waves Plug-in in Logic Pro 10.4.4 on Sierra with my MCU Pro and Extender Pro. For the moment the units are working(!) and I can actually get some work done with them. I can automate and adjust the plug-in — specifically the gain — in plug-in mode. As you probably know, if one makes any adjustments to the gain through the plug-in mode, the change is not reflected on the LED read-out on the units. The read-out and the faders reflect the setting of the "volume" automation of the track or region, which are turned off (same if turned on). What I'd like to try to do is link the fader with the gain control in the plug-in so the LED does show the changes made in the plug-in. Is there a controller assignment I can modify/create that will accomplish this? Probably not, I suppose, but I thought I would ask. Like I said, I have too much time on my hands, but I'm curious if this is possible. Thanks!

Thanks!

Thanks. I'm probably going to switch to region for exactly the reasons you cited. I was using track only and that's what was surprising to me that Region Automation seemed to be in control even though I wasn't using it. What I failed to mention is the midi track was imported so I think it brought it's own automation information (volume) with it. Quite enlightening. Thanks for the feedback.

I ran into an "issue" that I haven't noticed before — noticed being the important word here — and it brought forth a question that so far from my reading I haven't answered. Does track automation cancel region automation (or vice versa)? I had a midi track using track automation that wasn't responding properly to automation commands. I happened to think to switch to Region Automation and there was the problem. It had a different setting and was overriding Track Automation. The region is the length of the whole project, so it's not an individual region among many on a track, if that makes sense. I tend to use Track Automation. This has made me wonder about the error of my ways. I guess to rephrase my question: do I have to make sure that the track automation is identical to the region automation or is region going to override track automation. It may be I simply don't understand any of this.

For what it is worth, reinstalled Finale 25 and problem solved. Also solved a number of other issues with the program.

It seems safe to say that tempo changes when Finale is rewired to Logic are pretty much impossible. I assume this is a Finale issue and will inform them of it.

I have looked at other threads about Rewire issues and none seem to be similar. I just updated to 10.4.3 in hopes it would solve the issues I had in 10.4.2 If I create the tempo changes in Logic to correspond to the changes in Finale, the audio of the rewire feed cuts off for four or five measures and then resumes. Also, in certain areas it will cause finale to repeat measures, which is really bizarre. I have taken all of the metronomic markets out of the finale document and tried again. Same problems. I have shut both programs down (not saving changes in Logic). Open Logic, re-do the tempo changes, reopen Finale in rewire. Finale has NO TEMPO changes. Same problems. Anybody have any clues? It doesn't matter if tempo changes are ramped or not. I'm trying to check some timing issues as the performer will be playing along with a track and I need to make sure some things line up. I can always create a midi file, open it in Logic and redo a lot of things, but I'd like to avoid that as my deadline is fast approaching. Thanks