splunk Posted February 6, 2014 Share Posted February 6, 2014 I'm trying to replace some guitar rhythm chords that were played too softly with chords from the same take that were played louder. I've got the transient markers all in place and have selected the chord I want to use as the replacement using the marquee tool and the left/right arrows and copied it to the clipboard. But, when i use the right arrow to move to the transient where I want to paste and press command-V, the clipboard is pasted somewhere far to the right of the transient I've selected. It almost looks like the next transient is selected as the starting point - the playhead moves there - but the copied part of the audio is appearing even later than that. It's as if a bunch of silence has been added to the beginning of the original copied audio. I didn't use this feature a lot in LP9, but when I did, I don't remember having any problems with it. Have I forgotten some important step in the process or is this a bug in LPX? Link to comment Share on other sites More sharing options...
camillo jr Posted February 6, 2014 Share Posted February 6, 2014 Copy and Paste via Marquee working fine here in LP9. I'm curious, did you record to a click? If so, you might want to try a method that's a little less fussier way of doing this. Rather than grab the chord precisely and messing with transients and all that, I just copy the whole bar (or half bar or two bars) that has the chord in it and paste it into the new bar. Since I'm Marqueeing right on bar lines, this makes selection and pasting very easy. Then I drag the boundaries around in the pasted area till it all fits nicely. The other thing I do is turn off Flex while I'm doing this! Waaay less chance of messing up the selection by inadvertently changing it's length or adding Flex markers. Ditto for the surrounding areas where you copy from and paste to. Link to comment Share on other sites More sharing options...
splunk Posted February 6, 2014 Author Share Posted February 6, 2014 OK, not only was that great advice, it also allowed me to find the problem. It's either something weird with this particular session or a bug, but the problem was occurring because the start of the session was set to 0 1 001. When I tried your suggestion, I saw that the marquee selection was moving exactly one bar later than where I started the paste and the paste itself was happening one bar later than that. This happened whether I used a transient as the starting point or the cursor. As soon as I changed the start of the session to 1 1 001, pasting worked as expected. Further experimenting… It looks like the problem occurs during the copy, not the paste. If I copy something while the session start is 1, then change the session start to 0, pasting works as it should. It's only when I copy something while the session start is set to 0 that the offset during paste occurs, even if I change the start back to 1 before the paste. I'm not sure if this is just something that's happening with my machine or it's actually a bug in LPX. If someone can confirm this is a bug, I'll file a report with apple. Thanks for the help! Link to comment Share on other sites More sharing options...
camillo jr Posted February 6, 2014 Share Posted February 6, 2014 You're welcome although I'm not sure if it helped! And..... what do you mean by starting the session at 0 "1 001 or at 1 1 001"? Are these bar numbers? There's almost no reason to move the start of a session and in fact, having a session start before bar one is asking for trouble in various forms, including corrupting the session. Link to comment Share on other sites More sharing options...
David Nahmani Posted February 6, 2014 Share Posted February 6, 2014 I agree with camillo, you session start should always stay at 1 1 1 1. Logic can exhibit all sorts of unexpected behaviors (a.k.a. bugs) when the project start marker is at any other position (wether earlier or later). Link to comment Share on other sites More sharing options...
splunk Posted February 6, 2014 Author Share Posted February 6, 2014 Huh? Did I miss some simple way to align the measures so that I can do a pickup? What do you guys do when you have a pickup bar? Do you actually deal with offset measures? That is, what should be measure 1 is measure 2 in your session? That's a pretty unmusical way to deal with a song, so I'm guessing I've missed some way to change the measure display. The manual specifically states that I should drag the start of project marker to an earlier position if I want a pickup, so that's what I've always done. So, if that's the advertised feature in the manual and both of you are telling me that not only will it cause Logic to work unpredictably, it might even corrupt my entire project (and I believe both of you) and everyone but me knows this, then why does that situation continue? Shouldn't it be considered a major bug and be fixed? Thanks david and camillo. I had no idea this was a problem. I'm hoping you're going to have a method to make the bar numbers display correctly, though. It would be a total drag to be listening to bar 9 and see bar 10 in the display. This surely can't be the only solution. Link to comment Share on other sites More sharing options...
camillo jr Posted February 6, 2014 Share Posted February 6, 2014 Huh? Did I miss some simple way to align the measures so that I can do a pickup? What do you guys do when you have a pickup bar? I never start a song from bar one, usually more like bar 6 or 8, for a few reasons and pickup bars are just one of them. Do you actually deal with offset measures? Nope! The manual specifically states that I should drag the start of project marker to an earlier position if I want a pickup, Bad manual! BAD BAD manual!! (The manual is otherwise very useful, except on this point.) then why does that situation continue? Shouldn't it be considered a major bug and be fixed? There are many bugs in Logic that we wish would get fixed and occasionally, some do. But then a new version of Logic comes along and introduces new bugs. But rest assured, the Logic development team has been issuing bug fixes at a blistering pace lately. Unfortunately, the "move the start marker and yer song gets effed up" bug has been around for a looooong time and will likely remain unfixed for a while yet. Thanks david and camillo. I had no idea this was a problem. I'm hoping you're going to have a method to make the bar numbers display correctly, though. It would be a total drag to be listening to bar 9 and see bar 10 in the display. This surely can't be the only solution. I guess one man's "drag" is another's non-issue. I don't worry about the Logic bars equaling my song bars, (starting as I do at bar 6 or 8 ) simply because for me, this is OK. Link to comment Share on other sites More sharing options...
splunk Posted February 6, 2014 Author Share Posted February 6, 2014 OK, thanks camillo for all your advice on this. I do find it a little disconcerting, especially if I'm dealing with a chart, to have the bar numbers on the chart and the bar numbers in the session not match. OTOH, this annoyance is far preferable to the craziness I was trying to deal with when I had the session starting at bar 0, so for now, that's the poison I'm going to choose. I'll send a bug report to apple, but I'm getting the impression from you and david that this may be one of those things that I can never count on being permanently fixed. Thanks again! Link to comment Share on other sites More sharing options...
camillo jr Posted February 10, 2014 Share Posted February 10, 2014 You're very welcome, splunk! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.