sw1

Hi there, I still am having issues with the following: I work in a large template with 500+ external midi tracks. All tracks have a small reset region at the start, which resets keyswitches and volume/modulation. Often I option drag regions on to other tracks to double instruments etc, and when I do that, the regions channel information (which we can see in the event list) will end up a different channel than the track that it's copied onto, and therefore the channel information will be different than the reset channel on the same track. One of the logic moderators cleverly found out that hyperdraw information will respond unexpectedly if there are different channels with midi information on one track. Does this pretty much mean I can't copy regions onto other tracks without having to change the channel? Is there a workaround? Am I the only one with this issue seeing I didn't find much to read about it? Thanks in advance

Hi there, I've been trying to find this on the forum, forgive me if it's already been posted once. I'm new to flex audio. I have a session with a bunch of midi, tempo 68, and want to add an audio file that has an original tempo of 60. So what I did is (this might be the stupid way, i don't know) is imported the audio file, changed the tempo of the session to 60 for a second, view flex audio polyphonic, change tempo to 68, and then my audio file plays along nicely with my sequence. Now I have 2 questions: - if I add several tempo changes, whether I add those in flex mode or not, the audio file seems to follow them in flex mode. I have to go out of flex mode at times to listen to the original file, because at some points the original loop might sounds better (sounds strange I know, but it's a very unusual loop). So I want to understand how Logic knows the original tempo of the audiofile. Because it seems to be that if I go in and out of flex mode and I make tempo changes while not in flex mode too, the audio file keeps following them. But then again I'm not quite sure if this is really the case, the thing I don't want, is when I go out of flex mode, Logic thinks the original tempo is something else and it will screw everything up. - also, this seems to work when I import and audio file in a project that has a single tempo. Now I have a sequence that already has several tempo changes in it (midi tracks), and I want to add the audio file and have it follow the tempo changes. The way I'm doing it doesn't work. Is there a way of doing this? I tried the follow tempo option, but that doesn't seem to work, the audio plays slower than the click and doesn't seem to pay attention to tempo changes. Hope this all makes sense, thanks LG 9.1.5

Just one more thing, re what David and camillo were saying; What does that channel in the even list mean exactly. I've been looking at different regions in a bunch of sequences, and most of them has notes, mod and volume on channel 1, in the event list. Though some regions have all that information on the channel that the external midi instrument is set to, like 3 or 15 or whatever. I guess I'm not quite sure if everything is supposed to be on 1, or is everything supposed to be like the instrument channel. I obviously have my external midi tracks assigned to 1-16 every time, to get midi from my other machine to the right track. Anyway, it's not that important I guess, I was just curious to find out on which channel it should come in and what it means. Thanks again guys

wow, you're right! that's interesting isn't it. Thanks a lot for that, I suppose I can change them all to channel 1 for now, and for the future figure out why it was coming in on channel 3 in the first place (controller, midi guitar, etc). Thanks everyone!

Well, I think somehow the volume hyperdraw is corrupted. Sounds a bit batty, but if I copy just the volume in the hyperdraw to another region, it acts the same way. If I select all that volume, delete it and draw it in again, its fine. Weird stuff innit

Hi there, thanks for the response again. So funny enough it doesn't work for me, what you're describing! If I mute the reset, it indeed doesn't go to 110 anymore, but it doesn't quite catch up how it should. For instance, I hit the dot (is that what you call node?) at bar 21, and then my volume hits 65, which is correct. If I stop it right away and jump to bar 23, in between nodes, it still reads 65 and not 62 which it should, until it hits the node at 25ish. See what I mean? And yes, you're right about the automation not going all the way to the edge, I think I was dealing with another project at the time. haha, well spotted

not sure if I know what you mean, in the setup we have we use external midi and bidule, I'm not actually loading anything in logic. Or did I misunderstand?

this is the stripped down sequence. The tba was already greyed out. What you will see is that the hyperdraw somehow jumps back to the volume that is set in the reset region hyperdraw, in this case 110 (you will see that if you type in 56 for instance in the reset region it will jump back to that). If I copy the region to a new track, same thing happens.

alright so I think it's a volume thing after all. If you look at this picture, you see that the volume is set to 62. If I hit play where the cursor is, the volume plays at 110, which I can see in the channel strip. Once it hits the dot at 62, it will carry on playing at 62 and whatever follows. When I hit stop like right after the dot 62 and go back to where the cursor is in the picture, the volume goes back to 110 until it hits the dot again. So it does appear to be a funny volume issue. I opened the session on two different machines, they have a different controller, and same thing happens both times. Any ideas?

so I just tried to copy lots of regions from a song to my template, in logic 9.1.5. All tracks end up at the bottom. Then I opened the exact same files in logic 8, and doing the same thing, it pasted them all on the right tracks! Seeing I used exactly the same projects, this really seems to be a logic 9 thing then, doesn't it?

yes the fader follows volume ramps. I think the problem might be modulation. It usually happens on instruments with modulating I think, for instance a vsl clarinet that will sounds really loud, as if the mod wheel is at the highest, until it hits a dot again and it corrects. I don't have track based automation going on at the time, I never use it, and I checked that to be sure. I don't have a screenshot at the moment, I'll see if I can make one when running in to it again (it seems a bit random). Thanks

same behaviour so far when I try that. I don't know if the following is of any importance; Logic doesn't paste the tracks at the bottom in the order they were in the copied project, but it pasts them starting with the region that's closest to the start of the song and ends with the regions that were last in the copied song. Does that make sense? So it kinda pasts them left to right. Doesn't seem very clear how I try to explain it, but I also don't know if it's even relevant. I did try merging all the tracks to the reset before copying them, but then it still stuck them all at the bottom so that didn't make a difference.

thanks for the response ski! 1. When you say that Logic is pasting the regions on tracks at the bottom, is Logic creating new tracks? yes 2. When the regions are pasted, are are all of the track assignments correct? In other words, are the instruments assigned to those tracks the right ones for the regions being pasted? Sometimes. Interestingly enough, I was just creating a couple of dummy projects, just to use for this test. I so I create a region, stick a few notes in there, and copy it to other tracks. Most of them actually go on the right tracks after copying to the new project, and the few that don't, go to the bottom but do have the correct port and channel. BUT, I just did the same test with an actual sequence from my previous project, lots of tracks and bits of regions, I did the same thing and it puts about 3 regions on the right tracks, and the other 50 or so at the bottom, most of them NOT having the correct port and channel. They are named the same, because before I copy the regions I do 'name regions by tracks'. 3. Are the names of the instruments between your source and destination songs EXACTLY the same? yes, they haven't been changed in 2 years 4. Based on what I read in your post, you've sometimes got two projects open at once. Can you confirm? indeed, I have them open at the same time, to copy from one and past into the other. 5. Are the songs you're pasting these regions into empty or do they already contain musical material being written for other cues? usually empty, apart from a 1 bar reset region at bar 1 of every track

I would really like to know if LG can still do this in 9, let me describe even more detailed what I am trying to do. I have a massive template in Logic 9.1.5, containing about 600 tracks, all midi tracks using external midi. Working on film music cues, I often have to copy midi regions from one project to another, for instance to reuse a theme or something. So the project I'm copying from is made in pretty much the same template as the project I'm copying to. In Logic 8, and I just checked this again, I just to open both projects, copy all the regions on one, paste them in the other, and they would automatically go to the right tracks. Now in LG9, when I hit paste, it sticks all tracks at the bottom and it takes very long to drag them all up to the right tracks. The 'import tracks' option in logic 9 is no good for this particular matter, seeing I have to select for instance 50 tracks out of 600, and I'd have to go back and forth to check which ones. And then it won't stick them in the correct spot. If anyone can tell me if this is still possible in logic 9, do I need to tick a box, or is there a new more clever way of doing this. Thanks a lot

thanks for the response. I know about the business of hyperdraw that isn't drawn all the way to the edge of the region won't work. All my hyperdraw does go to the edge. I meant Chase settings in project settings indeed. I don't have the modulation set to reset, as in the box is unticked. That's how it should be right? Thanks for the suggestions, any other ones up your sleeve?