Jump to content

appillar

Member
  • Posts

    35
  • Joined

  • Last visited

appillar's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the reply shivermetimbers. That thread was very interesting, informative, and not enjoyable! Whew! With the amount of time everybody puts into mastering Logic (and all the other programs out there), I think we all feel somewhat entitled to sharper tools than that. But I do accept having to weather some of the variation and delay discussed in that thread. I've been somewhat aware those issues exist, so it does feel like part of the animal to me. Still unanswered to me though is how a recording could be early. Some of ski's recordings were early (like mine), though they didn't discuss how that's possible. To me, that's breaking the laws of physics! Brainstorming: The sound is triggered when the MIDI note is played (or when the information gets to the external box, which is later not earlier), it comes back (even more late) and Logic intervenes, directed by some user-designated setting. It moves the audio to an earlier position than where it would naturally be without intervention, which in my case happens to be before the original MIDI note that triggered it. Ok, fine. In the end I'm just wondering if we can at least get Logic to not place the recording before the MIDI note that triggered it. I'll deal with all the variation and late stuff, at or after the original note! Oh, you asked a couple questions: 1) About my analog and digital comments... analog (1/4" TRS out) and digital out (spdif) on the synth (Roland Fantom XR). In Logic, on a channel strip, that comes up as 1-2 IN (analog) and 3-4 IN (digital). 2) Recording the initial MIDI note: I played it on my external keyboard controller onto the MIDI track in Logic, then quantized it to 1111.
  2. Hi Guys, Got a sync/latency question here. I opened a new project. I've got three tracks... MIDI, audio, and audio. I have a MIDI note exactly at 1111. This plays out my Mbox 2 to my external synth (set to a drum kit, the sound is a kick drum). I play the MIDI track while simultaneously recording the triggered kick from the synth back into Logic. I do this twice... one time analog from the synth to the first audio track, then one time digital from the synth to the other audio track. Here is the result, and the source of my question: On the first audio track the signal via the synth's analog outs appears eight milliseconds before 0:00:00:000. On the second audio track the signal via the synth's digital outs appears fifteen milliseconds before 0:00:00:000. Playing the project from 1111, both attacks are chopped by their respective distance from (before) 1111. My intuition tells me that if anything, the audio should appear later than 1111 (0:00:00:000). Why is it occurring before, and how can I adjust it? Thank you.
  3. Ah, interesting about what's written in the manual being affected by the author's preferences choice at the time. I never thought about that! Boy, as someone still learning Logic, I still find understanding some of it daunting, but at the same time I find the number of possible functionality-combinations very interesting. I'm looking forward to knowing them all! 8)
  4. Yeah I agree, not a bug... just wasn't sure which section to post it in. Yeah, mostly it's the unclear manual, but indeed, simply turning on the Cycle function doesn't cut it... you must have chosen regions for regions to be moved Thanks for expanding it! Uh, in your second section for the opposite behavior you mean "unchecked," right?
  5. Logic manual page 189 says: "If the Cycle function is switched on, all regions within the cycle are moved from the old track to the new track." This is not true. To verify, do this: 1. Make sure there is an inactive Cycle of some length above regions in your project. 2. Select a track. 3. Make sure no regions on that track are selected. 4. Switch on the Cycle function. 5. Option-click-drag in the header of that track to copy the track. No regions move. Regions move only because they are selected. Regions do not move because the Cycle function was switched on, and this is because switching on the Cycle function does not select regions.
  6. On page 301 the manual says this: "Using Solo Lock: On occasion, you may want to lock the solo status of several regions. As an example, this would be especially useful when you want to make changes to the playback parameters of a region, while listening to a specific group of soloed tracks." I translate that to this: "You can lock a group of regions as soloed, then move up or down your project soloing (and un-soloing) other regions while the original group stays soloed, to always hear the original group in context with the newly soloed region. It's not working like that for me, so I assume my interpretation is wrong, but I haven't figured out how to interpret that any other way. Anyone clear on Solo Lock Mode? Also, does the Track/Mute Solo Preference affect Solo Lock Mode in any way? Mucho thanks for any feedback!
  7. Regarding my initial scenario with the Solo Tool: Yeah... whatever the behavior, it should be consistent (play or don't play... and I would say don't), yet consistent it is not. Well hopefully that's on Apple's list of fixes. Clarifying your reply: 1 of 2: David, when you say Ultrabeat does always play along in Solo Mode, you mean without using the Solo Tool but just hitting Solo on the Transport, selecting any region on any track with the Pointer Tool, then pressing Play, right? Yeah, I see that. Ultrabeat, if it's sequencer is on, will always play with any selected region under those conditions, though like I said above... I would prefer it never play when regions on other tracks are soloed, since that negates the whole point of soloing. But anyway, so the problem seems to only be when you select regions with the Solo Tool. Ultrabeat will play along with audio regions soloed with the Solo Tool, and will not play along with MIDI regions soloed with the Solo Tool. 2 of 2: You said the fact I'm soloing regions with the Solo Tool is irrelevant in getting Ultrabeat to play: I see that Ultrabeat can't play along if the project isn't playing. But clicking specifically on regions with the Solo Tool does seem to be relevant since the project won't play if you click and hold the Solo Tool on anything else (like, say, the background). Am I missing your point? Maybe you're just pointing out that the act of soloing, or having a region sitting there "soloed," all by itself, doesn't trigger Ultrabeat, and that it's all about the clicking and holding component of the Solo Tool, which activates PLAY. I get that. Thanks for spending time on this!
  8. In the Arrange Window I've got two external MIDI tracks (#1-2) with regions recorded, one audio track (#3) with regions recorded, and an Ultrabeat track (#4) with no regions. With Ultrabeat's sequencer on, with the project stopped, if I click/hold on a MIDI region with the Solo Tool in the Arrange, the region will begin to play and Ultrabeat will not play along. If I do the same to an audio region, Ultrabeat does play along. Does anyone know if this is a correct function? Seems to me Ultrabeat shouldn't play at all if I'm soloing any regions on tracks not related to Ultrabeat, right?
  9. I had to read David's explanation a few times but I got it. Change the tempo (regardless that you're doing it with this specific command) and the MIDI data in the MIDI region will change speed. The goal of this command is to work against that. It wants to hold the MIDI data at the same speed while changing the project tempo. So something needs to hold the data in place (Lock SMPTE). For audio it doesn't matter because the "tempo" of the samples isn't going to be shifted by a tempo change, except in other circumstances where Logic can do that. Thanks for getting into this guys.
  10. Does anyone definitively know why the solution here is that MIDI regions and audio regions are not treated the same, for the same task? To match project tempo to region length w/locators: -Audio: choose region, drag cycle to # of bars, then command T -MIDI: choose region, Lock SMPTE, drag cycle to # of bars, then command T
  11. Thanks for the reply PaulSC. I guess their limited definition of "adjustments" needs to be discovered through trial and error... that sentence in the manual really sounds like something universal. Anyway, I tried out what you said with fades and was glad to get some clarification. Regarding dragging edges, I think you meant that by "adjustments" they don't mean trimming, since that specific adjustment to the source region does duplicate itself in clones, right? I tried to find more functions as examples, but there aren't many. I found the "repeat regions" command is one (only affects the source). It's amazing, even with all the documentation, sometimes this is still like finding the answer to a mystery. Thanks again!
  12. Hi Guys, Having trouble squaring up the manual and real world. Fourth line from the bottom of page 282 says, "Adjustments to the source regions do not affect clones." Earlier in the paragraph, they make it very clear that adjusting other clones will change other clones. This differentiation seemed clear to me, so I went into Logic to witness the difference. Editing one clone affects other clones, which is all good. What about source regions? Here's the problem: When I SHIFT+OPTION click and drag out a clone from an audio region, then, say, bring up that source audio region in the sample editor and silence part of it, the silence is duplicated in the clone, contrary to what the manual is telling me. Anyone know what's up with this? Is this a misprint? Thanks!
  13. Some controllers have a knob near each channel fader called an "encoder?" My Keystation doesn't have these.
  14. In the Logic Pro Control Surfaces Support pdf, on page 30 (anyone can access this via the HELP menu when Logic is open), in the "Multiple Controls Per Parameter" section, it talks about choosing the number of encoders used for each parameter. I'm using an M-Audio Keystation Pro 88 (just bought it) with Logic, and I'm in the middle of learning how to map this thing with Logic. In various documentation (and in some people's posts here on the forum) I keep running into this word encoder in relation to control surfaces and Logic, but I can't figure out what it is. What is being referred to when someone is using the word encoder in this context? Thanks!
×
×
  • Create New...