-
Thanks for your answer! The project is saved correctly. It works if I only start an empty VE Pro server (i.e. don't open an mframe). When I then load any project with VE Pro in it, Logic makes VE Pro load the correct instruments and sets all volume levels right. When I then close this project, VE Pro of course stays open and has everything loaded. When I now load another project with identical tracks, but different volume levels, Logic correctly (re)connects to the VE Pro instances, but all volume levels stay the same and do not reflect the levels in the project. Had I closed all VE Pro instances and then opened the Logic project, VE Pro would have reloaded everything including the correct volume levels.
-
No, this does not work. I think Logic sends MIDI when loading a project. I tested it with my Technics Keyboard. Logic always sends CC7 when loading a project. Only if an instance in VE Pro is not newly loaded, but reactivated from a preserved instance, it seems to ignore this. Any way I can test this and provide further information?
-
But isn't this a bug? VE Pro correctly loads volume when there are no preserved instances there. But when there is a preserved instance, it totally ignores any volume information. Am I the only one affected by this issue? When I load a huge project of, say, 100 tracks (i.e. any project using my orchestral template), I have to move 100 faders by hand?
-
Unfortunately this does not work, either. How come noone so far has mentioned this issue. Either it is a bug in Logic, or a bug in VE Pro. I assume it is a bug in VE Pro since VE Pro correctly loads everything if the instance is loaded from within Logic, i.e. if it does not use preserved instances.
-
Ok, so it is not possible to keep VE Pro instances open? I thought this is what the preserve function is there for? That means when switching projects I have to close VE Pro and reopen it, correct? I mean, what use is it to have the samples loaded if VE Pro does not react to the track volume sent by Logic? Logic definitively sends the track volume because it works with other hosts, i.e. Bidule.
-
@Novatlan said:
Unfortunately this does not work, either. How come noone so far has mentioned this issue.That's strange - the 'send used instruments MIDI settings' function does the trick for me (although I am using CC107 not CC27 for the volume). I know this is an obvious thing to check but I will anyway (sorry); is the volume box ticked (in the track parameter box)?
-
Mosso, you _are_ my hero. If you were a beautiful young lady, I'd now propose to your dad for your hand :) That did the trick. I have never before worked with MIDI tracks and even an hour of searching in the Logic Manual (why don't they have a printed one?!?!) did not lead me to the right path. Just tried with my big orchestral template on a few tracks. When Volume is checked, VE Pro correctly loads the volume information. Many, many thanks! You don't by any chance use an Euphonix controller? This is the second big thing making problems on my mac...
-
One problem solved, here's the next one: If I move the fader in Logic with the Mouse, the value in the "Volume" checkbox is changed. If I move the fader with my Euphonix Controller or with any other controller, it stays the same. You can hear the effect, but since the value does not change and Logic always sends the value of the field to VE Pro, after reloading the project, VE Pro will get the wrong value. Any ideas?
Forum Statistics
194,022 users have contributed to 42,906 threads and 257,896 posts.
In the past 24 hours, we have 4 new thread(s), 16 new post(s) and 104 new user(s).