Smart Audio Editor

[Josefa Palsgrove]

Notnecessarily. You can use Flex without using Smart Tempo, for example to quantize an audio performance, or to time correct a track, or to lengthen a sustained note or tighten another, etc. You can also use Smart Tempo without using Flex, for example to analyze the tempo of an audio recording or an audio file you import in order to apply it to the project's global tempo track.

I had a problem with this after doing a Free Tempo recording. I added some downbeat hints, when moved to audio track editor and added som flex markers. Used Quantize. And around this time I got a clash with tempo markers. I could delete a tempo marker but it pop up again.

I watched this video and it is a demonstration of how to make a rubato (free tempo?) recording conform to a fixed tempo. I thought it was a good clear explanation of something I have had trouble understanding.

Ah ok that makes sense yes. If you have tempo information in a file that is different from the project tempo and then you turn Flex on, the file will adapt its tempo to follow the project tempo, which is not what he wants in this case. So because beat mapping changes the project tempo in different positions throughout the project, before he turns on Flex, he needs to make sure the file no longer has its original tempo information embedded so that the audio file stays put.

@kidslow said:

I'm finding it difficult to generate empathy with anyone's umbrage here. I bought the Smart Effects Pack when it was just on sale for $.99 ... as a token of goodwill towards the dev ... and I was rewarded by being grandfathered into all the newly paywalled features.

I do get it @Simon , but if I got outraged at every app developer over the years who didn't tell me what was in an update, I'd be institutionalized by now. My take is similar to @Gavinski, that the developer didn't think things through. Didn't think through making AUv3 free, and changed course by paywalling it. Didn't think through the reaction to the silent change to paywall it. It is sloppy but independent developers sometimes have to make choices they don't fully understand, and I cut them a lot of slack.

I'm going to compare what I can do in Wavebox with ocenaudio and Amadeus on the desktop. Time for a change. Been using Fission for years for quick little trims of audio clips but it doesn't handle multitrack files, so that's out. Used older v1 Amadeus before that. I've never gotten along with Audacity, which I'm sure is capable.

Not necessary to load plugins for my needs, but desktop version loads some Audio Units. All the AUs installed on the system show in the pulldown, but only native M1 versions actually launch, not Rosetta ones. Among those that launched include Kushview Element and Metaplugin, plugin chainers. Tried loading a few Rosetta VSTs in via Metaplugin and the plugin windows opened, so that's a good sign. Not sure what happens when music passes through or a load is applied. Will find out.

I don't get the sense that the dev intentionally exposed the depths of these audio unit loading functions, just selected to allow it. Makes me happy to know there will be a lot more cross-over capability between ios and macos as new developers start and older ones update their toolchain. Seems to be made available through a few compilation switches and use of certain libraries and functions, is how I understand these features are being exposed. One pitfall, something about how the application must be sandboxed in the OS, because a few plugins were complaining about licenses. Metaplugin applied the license file just fine, but that's where I stopped. I wonder how iLOK behaves in this scenario? Or machine-locked licenses? Seems like a batch of future problems for plugin developers.

I'm assuming tempo aware means that it has some way of detecting/inputting BPM and ideally also setting the workspace up to use beat scale rather than time scale. Amadeus can do that but neither Wavebox nor Ocenaudio can. I have seen nowhere in Wavebox interface or docs to input, detect or otherwise work with tempo.

Hit & miss on the 6 loops I tested. Worked with 100bpm drum loop and 70 dobro, but failed on pad at 125 and cello at 130. Perhaps works through transient detection? Doesn't seem to be anyway to override with manual BPM.

In my comparisons of desktop editors I found Wavebox wanting. Ocenaudio is a real beast though. On ios, I can see using Wavebox for quick trims and edits of audio only and nothing more. I hope the developer keeps on improving it.

Does anyone know how to adjust the recording sample-rate in Wavebox on iPhone or iPad?

It seems to default to 44.1k (on a 48k only device like the iPhone 8) and no way to select which microphone or input to use?

@Samu said:

Does anyone know how to adjust the recording sample-rate in Wavebox on iPhone or iPad?

It seems to default to 44.1k (on a 48k only device like the iPhone 8) and no way to select which microphone or input to use?

I'm mostly using TwistedWave for my 'field recordings' as It allows me to monitor using a lightning headset (or headphones connected to the Lightning -> 3.mm dongle) and select any of the devices built-in microphones (Back, Front or Bottom) for recording using a long-tap on the record button which is super handy (It does NOT allow input selection when using an USB-Interface with multiple inputs, for that I need to use either Auditor or a 'DAW').

I'm actually quite impressed by the free Dolby On app for field recording. The editor only allows trimming but the built-in processing is top notch! (it defaults to using the bottom microphone for recording).

Well maybe I should give TW another chance, I have a tense relationship with its UI, unlike the orange & teal in WB that makes me feel focused on the recording. Sure I will have a look at the Dolby app, many thanks Samu!

These bugs happen in new sessions created in Logic (I previously thought these were happening only on old sessions created in Logic 10.5.0 but now realise it is also happening in sessions newly created in 10.7.8).

1) I drag a splice loop into Logic, then when in smart tempo I click on analyse and it immediately crashes. This happens about 8 times out of 10. Is this happening to anyone else? It's such a simple function in Logic that I can't understand how it would be a bug?

2) Also something similar happens when I drag an audio file into Quick Sampler 'optimized', especially if I drag it straight from splice and drag it to the 'drag audio files here to create instrument tracks'.

There is also the issue with Logic crashing when I select flex pitch and also analysing the tempo within smart tempo...neither of these issues would have anything to do with a 3rd party audio as it happens with audio I recorded myself.

Can confirm every point. LPX Rosetta, M2 Pro. I've contacted Logic support, they asked me for a problematic project, I made one with a broken flex pitch and another one with broken quick sampler, recorded a video of both crashes. Let's wait and make more reports for support. The problem began with 10.7.7 and fresh MacBook, Intel version of 10.7.7 was fine.

Re: Crashes- I am experiencing the same issues as both themadpad and root_sashok. Except I am running a clean install, not using Roseta, and pulling my sound library from an external. I dragged my library to my main drive and took the external out of the equation, so ruled any issues there. If I turn the smart tempo setting >set imported files to: >Off, the problem goes away. I am able to then drag a sample in as audio, and analyze through the smart tempo tab of the editor window. Its annoying but at least a workaround for now.

I recorded a super-rubato improv session in 3/4 with a bandmate on MIDI keys. I bounced the MIDI part to audio, and am using Smart Tempo and the Tempo Editor to manually input barlines (and therefore tempo changes) throughout the piece. It changes tempo rapidly enough that Smart Tempo doesn't detect it, so I have to do this manually.

Here's the issue. When I select "Adapt Project Tempo and All Regions to Region Tempo and Downbeat" with "Maintain Time Position of All Regions" toggled on, while I expect the tempo track to adjust itself to be in accordance with the manually adjusted tracks in the tempo editor... nothing happens. The project reverts itself to 4/4, and stays at 120bpm. What am I doing wrong?

Matthew, as I understand Smart Tempo functionality, it uses the tempo and time signature information saved with the audio file. If you haven't saved the project (and thus, the new tempo and time signature information to the region you just edited) before using the function, it applies the existing tempo / time signature information of the audio file associated with the region. Which would be 120 bpm and 4/4 time signature, in this case.

So, for Smart Tempo to work, save the project first in order to save the tempo and time signature with the audio file you created and edited in File Tempo Editor. After that choose the Adapt Project Tempo mode (your project's mode is set to Auto) in the LCD display (see screenshot). Then right-click on the region in Tracks area and select Tempo > Adapt Project Tempo and All Regions to Region Tempo and Downbeat. Hope it helps.

3a8082e126