Jump to content

Bruno de Souza Lino

  • Content Count

  • Joined

  • Last visited

Posts posted by Bruno de Souza Lino

  1. 6 minutes ago, David Baay said:

    If you want to share a copy of that audio somewhere, I can 'Set' it for you and summarize the process.

    While I do think both methods have too many loose ends and burden on the user, I managed to do the AudioSnap method after starting over three times. As much as that is prone to error, it has less steps than the set beat at now time method.

  2. On 2/1/2022 at 4:03 PM, David Baay said:

    As I said, Undo is your friend when this happens

    In some cases, the error happens not when the mistake is made, but several steps after it, so there's no way to pinpoint it. Couple that with the fact that you can't remove snapping once it's set and your only option is starting over.

  3. 6 minutes ago, David Baay said:

    You can set as many or as few points as needed. Each tempo change will persist until the next one. If a section is locked in for several measures with a fixed tempo, there is no need to have  superfluous tempo changes. This is what I prefer about SM/BAN vs. Melodyne that will interpolate tempo changes every 8th note even where there are no notes or Audiosnap/Fit Improv that  want exactly one tempo change at every beat, and nothing in between. Also Audiosnap has a long-standing regression bug where it doesn't place the tempo changes exactly on the grid, which is messy and complicates copy/cut/paste operations.

    There wasn't a single instance where Melodyne got the tempo right when I tried.

    7 minutes ago, David Baay said:

    If you get an "invalid" error with SM/BAN, the error is yours; you've tried to set a beat that is already set or would require a tempo outside the range of 8-1000 bpm to align with the current Now time

    Problem here is there's no way to know which is which, which makes the error message confusing at best. When I had issues with AudioSnap and your suggested method, I couldn't find what the error was and had to delete everything and start over. IMO those two should be more resilient than that. And of course, that was also when it didn't crash CbB altogether.

  4. 20 hours ago, David Baay said:

    I recommend using Set Measure/Beat At Now. It's faster,  more flexible and more reliable than editing the Clip Tempo Map, and yields a cleaner and more precise project tempo map than either Audionsnap  or Melodyne.

    Does it estimate the time if I leave some beats without  setting due to lack of transients like AudioSnap does?

    EDIT - It's also possible to run into the same AudioSnap error using this method.

  5. On 1/30/2022 at 1:28 PM, Glenn Stanton said:

    on my system with a Behringer UB-802 on USB 2, i'm getting a reading of 10ms @ 480 samples. have you run the wave profiler on driver settings tab?

    10ms @ 480 samples seems to be the minimum latency figure you can get and that's roughly a 32th note off. While I could try to adjust the compensation thing on the settings (which would be a nightmare, since I don't know how many samples I should offset it by to get specific amounts of ms removed or added), that wouldn't do anything for monitoring and I would be ahead in the recordings if I compensate the latency.

  6. Eventually, someone will do the "Inverted Mike Magini," which is all cymbals where the drums should be and you'd have all your other drums hanging on the rack. I remember seeing a picture of a rack setup where the bass drums were on racks.

  7. 1 minute ago, scook said:

    When the trial expires, the editor and polyphonic algorithms are disabled but monophonic MIDI-to-audio and tempo detection still work.

    Didn't Celemony change that to only opening projects after Melodyne 5?

    41 minutes ago, Lord Tim said:

    And yeah, as I said, tempo maps in AudioSnap are a bit more complex than just the double marker thing. I'd strongly suggest the time ruler method instead.

    At least on the first try, Melodyne didn't even get the average tempo right and most of the beats I know should be on 1 and 3 are on 2 and 4 instead. It insists on an average of 90 when the average should be 89 (88.70 to be more precise. AudioSnap rounds it to 89).

  8. 51 minutes ago, Lord Tim said:

    Rather than using AudioSnap for tempo detection, drag your original track up to the time ruler at the top of the window and let it detect that way. This uses Melodyne and usually gives you much more accurate results for this kind of thing.

    I don't have Melodyne.


    Getting this error usually means it's screwed the detection up. Zoom in really close to the part where it's complaining - there's likely a double transient marker detection on a beat in there. Find it and disable it. Either that or select around that area  in general and disable all of the transient markers and manually add them back where you like.

    Disabling the transient markers doesn't detach them from the measure they're snapped to.

  9. Hi.

    I've been trying to create a tempo map for a song by using AudioSnap to mark the transients. It's been working fine until I got  almost 3 minutes into doing it. Now AudioSnap is starting to complain about "Invalid measures and beats" and giving crap values on the average tempo as shown here:

    I figured maybe the audio clip is too long and split it at some point. Not only that didn't fix the problem, but this happens?

    And the same error continues.

    Since there's no other practical form of doing that ( tapping the tempo manually with midi then using fit to improvise would take three times longer because I can't have waveforms laid on the piano roll like you can in FL Studio), I must stop and wonder how much Audio Snap was tested for this purpose.

  • Create New...