Jump to content

ski

Member
  • Posts

    15,802
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ski's Achievements

  1. Hey MS! Long time! 1) In your example you show a value of 50 for both the treble and bass staves in the grand staff. Those parameters adjust the distance between the staves, and my feeling is that they're redundant. If you need to increase or decrease distance between treble and bass staves, simply make a choice to adjust one of those values. There's no point in adjusting both. So, make a choice (flip a coin) to adjust the value of 50 for the bass staff. Leave the treble staff at 50. 2) Adjusting spacing above the treble (94) and below the bass (60). Scenario: I'm using the same Piano staff style for the entire first page of a piece. I'll start by adjusting the space above the treble so that the first system (the first line) of the piece looks good in relation to the title text. Now, any adjustment (-/+) you make to that value will consequently affect the spacing between systems. So if necessary, adjust the space below the bass (-/+) to get good spacing between systems. HTH!
  2. ski

    Hello Mr. Ski

    Thank you all for the praise and compliments. Much appreciated! 😇
  3. The influence of buffer size on MIDI timing is a completely separate topic from the recording delay setting. And latency compensation is a completely separate topic. I've been down this road a thousand of times. Troubleshooting your issue has to start from a fundamental place: recording delay. I'll try one more time... Do the loopback test as described earlier in the thread. You have to do the test exactly as described with no "improvisation." Once you've established that setting, 85% of your issues will go away. On a completely separate subject, you mentioned adjusting buffer size. (A) It has no bearing on recording delay compensation. (B) You should rarely need to adjust your buffer size once you've found the optimal setting for it. How to find that value is probably best discussed in a separate thread. MIDI timing via USB or 5 pin DIN MIDI... This is immaterial. If a synth is gonna play late, it's gonna play late. (I have one outboard synth that plays early, can you believe it?) Having to shift MIDI tracks using negative MIDI delay values on the MIDI tracks (read: not audio tracks) to get them to play in time is something every MIDI musician has to deal with. Buffer size influences MIDI recordings, but you have to do the work to figure out how much each synth is adversely affected and make notes. Let's come full circle... You said you have a track that plays back sounding perfectly. This means that nothing I've mentioned above need to be adjusted — except — your recording delay setting. The above is the best I can do: explain the cause of your issues, explain how they're separate problems, offer advice on accepting them and fixing them, etc. But if you don't do the one crucial loopback test, you'll never get to a happy place with any of this.
  4. samwhorocks, You said it all: Logic is shifting the whole audio file. That points fundamentally to an issue with your recording delay compensation setting. Nothing more. To really get to the bottom of this we need to rule a few things out with... A test! New track. Just a beat and a synth part where everything is playing back super tight. Now set your recording delay compensation to 2000. Record the synth part as audio and play it back against the drums. What's the result? Now mute that recording. Next, set recording delay compensation to -2000. Same test, record the synth part as audio. What's the result?
  5. samwhorocks, This points to a need to adjust your recording delay compensation value. There's a good chance that Logic isn't the culprit. (For the record, my first line of defense is to always blame Logic for everything, so that should say something.) 😇 It could be that your audio system doesn't report the necessary recording offset to Logic, thus the need to calibrate your recording delay offset. On my system (RME interface) set my recording delay to -75 samples. On my previous system (MOTU interface) it was -25 samples. Go figure. 🙄 It's probably no consolation to know that there are people who aren't experiencing the same issue. Then there are those who are experiencing it but can't tell the difference. Some people refuse to believe that this issue should be adjusted automatically by Logic, but here I would say "see the second sentence of this post." In your case, judging from a distance, I'd suggest doing the loopback test as a first step in troubleshooting the issue.
  6. Re MIDI timing, there are two things at play. One of them has already been mentioned: individual response time for each device. There has never been a standard for how quickly a sound (sharp attack) should emanate from a MIDI synth upon receipt of a Note On message. In the history of MIDI instrument development — to the present day — manufacturers have always striven for response times to be "as quickly as possible" as you might imagine. If any of you are old enough to remember the Roland D50, a hugely popular synth in its time, the MIDI response time was abominable (something like 50 ms). Other synths and drum machine response times were near instantaneous, and then there was everything in-between. Rampant MIDI response timing issues even gave rise to the development of a device called the "Russian Dragon" (i.e., Rushin' Draggin') 🤨 which allowed studio musicians to visualize timing differences (compared to a timing standard) as an aid towards making timing adjustments in their DAW's MIDI tracks. The second issue has to do with Logic's MIDI Delay Compensation. This is a complex subject in its own right which I wrote about some time ago (@David, maybe you could find that thread?) Basically, your buffer size will have an influence on MIDI timing. On one hand this is to be expected. On the other hand, it's... wonky... Bottom line: you should fully expect to experience differences in MIDI response time between your outboard/external/hardware MIDI devices.
  7. Hey David and Everyone, Got a notification for this thread just now, a bit more than 15 years to the day that I originally posted the procedure that David linked to. OMG! I just reviewed the procedure and it is still THE foolproof way to adjust Logic's delay compensation. To summarize, you're going to play audio out of Logic (just as you or another musician would hear it live) and record it back in using a physical connection (wires). This simulates exactly the scenario where you or another live musician performs against the track playing out of Logic. You may find that after doing the test that your recording delay is fine at zero, the default value. But you can't possibly know what the correct value is unless you perform this test. Cheers! Ski of Yore
  8. ski

    Hello Mr. Ski

    (just when I thought I was out, they drag me back in) 😵 Hello to airforceguitar, volo, Dan, and David! Dan, in looking through your Aries score, I wanted to point out something regarding symbol placement that's sort of in keeping with your comment about using/abusing the layout tool. Which I wholeheartedly recommend. But, OK, check this out: When adding dynamic markings such as mF, as shown in the attached example, the symbols should placed under the note associated with the marking, not before. So if a note starts on (say) 1.2.1.1, the symbol should have the same position. I think of it in terms of "physical position" even though, of course, we're not talking about real objects. There are two functions that help make placement easy: Guides and Help Tags. Normally I have Help Tags disabled because I find them really annoying, but not when it comes to doing markup in the score. The guide setting shown in the second pic is my default, though I'll change them on an as-needed basis. If, for whatever reason, positionable symbols like dynamic markings end up not being aligned with the notes, you can easily shift their position in the event list, or just by using the normal pointer tool (cursor). But don't use the layout tool for this. Start off on the right footing and have the symbols and notes positioned on the same beat. Then use the layout tool to fine-tune position up/down/left/right as needed. You'll find that by "getting it right the first time" using the above approach, the position of dynamic markings (etc.) will stay nicely in sync with the notes they're attached to regardless of how you might change the line layout later. For example, when you extract parts, or change the number of measures per line — whether in the score or in the part — the symbols will go along for the ride and maintain their alignment with the notes. An alternative to using the layout tool to fine-tune the position of symbols is to use the Nudge up/down/left right key commands. I find them indispensable.
  9. ski

    Hello Mr. Ski

    JamesF, thank you for taking the time to post with your kind comments about my course. I'm glad you and others have found it useful. 😇 @DanRad Yes, I'm out here, thanks for asking. Kinda under a rock for a minute, but working on coming out from under it.
  10. Hey Fuzzfilth! Try my setup, it doesn't multiple-trigger. That's because the Filter Duplicates box is checked in Processor 1. Also, FWIW, I chose the Quantize function to make this quick and easy to set up. If the OP wants to tailor the response so that the kick is triggered only when the pedal is fully down, then your modification of the map is perfect (of course).
  11. Try this environment fix. There are two Transformers which I've named "Process 1" and "Process 2." Program Process 1 as shown in the first screenshot, and set up Process 2 as shown in the second.
×
×
  • Create New...