ba_hill

Hi, Make sure you've unzipped the python script. What are you typing in the terminal? It should be "python3 /Users/Shared/aulist.py" (without the quotes). Brian

My pleasure!

Hi, I've written a short python program that will print out a list of all installed audio units and their version numbers. It doesn't list the manufacturers. This is offered completely free but with no warranty whatsoever. If you're familiar with python it will be easy to modify this script to list any plugins you like. If you're not familiar with python but you're reasonably comfortable with the command line terminal the script should be easy to use. Chances are you will have to install one python library, though. Unzip the file attached to this post, aulist.py.zip, and put it somewhere you can get to it easily. First, install the Objective C library which python needs in order to use some Mac specific functions. This should take a couple of minutes or less depending on the speed of your internet connection. You'll see a bunch of text scrolling by in the terminal. It will stop when it's done. You only have to do this once. After the library is installed you won't need to do step 1 again. If you're running MacOS Big Sur or Monterey: 1. Open the Terminal app and type (without the quotes) "pip3 install pyobjc" . Wait until the text stops scrolling in the terminal. 2. Next, type (without the quotes but with the space at the end) "python3 " If you're running an earlier OS: 1. Open the Terminal app and type (without the quotes) "pip install pyobjc" . Wait until the text stops scrolling in the terminal. 2. Type (without the quotes but with the space at the end) "python " After step two everything is the same for any version of MacOS. 3. Drag and drop the script, aulist.py, to the terminal. You should see the full directory path to the file show up on the command line. 4. Press return. If all goes well you should see a list of all your installed AUs. You can copy the text from the terminal and paste it into a text or spreadsheet document. aulist.py.zip

Conversion to lossy formats can increase the peaks of audio files. See https://www.izotope.com/en/learn/mastering-for-compressed-audio-formats.html "What do MP3 and AAC do to your audio? Lossy compression refers to a class of data encoding methods that uses inexact approximations (or partial data discarding) for representing the content that has been encoded. (Read the Wiki article for more.) In simple terms, lossy compression formats utilize psychoacoustic models in an attempt to remove the audio information our ears won’t detect as missing. This often means removing audio information from both the high end and the wider elements of the stereo image. Any lossy encoder introduces an approximation error, a noise which can increase peak levels and cause clipping in an audio signal, even if the uncompressed source audio file appears to peak under 0 dB. It can be hard for the average ear to isolate and detect the artifacts, so consider the following audio examples."

No, I'm sorry I don't.

No, I'm sorry I don't.

It sounds like the issue is with Neutron. I don't have any idea how to work around that but you might contact Izotope and see if they have a solution.

I did try the X-Touch with another EQ plugin, Apple's AUPararmatricEQ, using Smart Controls and it worked the same as with Neutron. Are you using Smart Controls when you get the X-Touch to work as it should with other parametric EQs? Which other EQs did you try? If they work with Smart Controls (as opposed to directly mapping to the EQ's controls) then my theory is probably wrong and there's something else going on.

I've had a chance to look into this and I don't think there's a solution. As far as I can tell everything is working as designed but the limitation is in a combination of the Mackie Control protocol and the way Smart Controls work. The spec for the rotary pots on the Mackie Control devices is to output values between 1 and 65. Smart Controls, from what I can tell, map whatever range the controller puts out to the range of the plugin that is being controlled. In this case Smart Controls maps 1-65 to a range of 20-20,000 (Hz). That comes out to about 314 Hz per step on the X-Touch. If you look closely as move the X-Touch pot slowly you can see that the Neutron's frequency changes by that increment. If you map a controller that puts out values from 0-127 you'll get increments of about 157 Hz per step - still not much use at low frequencies. Only if you map a 14 bit controller (which I don't believe you can do with a Mackie Control device but you may be able to if you program the X-Touch Mini yourself) will you get increments that are small enough to be useful in lower frequency ranges.

I'm sorry. I don't know. Out of interest, where would I check for and edit these bit value settings for the controller?

It sounds like Neutron may be expecting a 14 bit value from the controller but the controller is only sending a 7 bit value. Is it possible to set the X-Touch Mini to send 14 bit values?

Hi, I had a somewhat similar problem. My audio moved when I changed the tempo. Locking the SMPTE position of the audio before changing the tempo worked for me. Maybe that will do the same if you lock the audio before creating the tempo map. Select your audio tracks then click Functions>Lock SMPTE Position.

Thanks man! Maybe I should clarify a bit as I'm not sure Apple understood the function when they added it. When transposing/quantizing to scale, it only really makes sense to do all (non-percussion anyway) parts on all tracks across the same range of bars. This is why it seems so weird they added it to the piano roll editor. It's one level up from where you'd instinctively do it. It's essential for jazz (and probably other genres as well) that scale quantize can be applied to a single track without affecting other tracks in the same range of bars. One of the cornerstones of jazz melodies and solos is the tension between the scale the soloist/melodist is using and the scale(s) from which the accompaniment comes. Playing diminished scale lines over unaltered dominant chords is a very common example.

It looks like Create MIDI Track from FlexPitch Data is missing one feature that Audio to Score had - the ability to determine the MIDI velocity of each note. Create MIDI Track from FlexPitch Data gives the same velocity value, 80, for every note regardless of the note's amplitude. Audio to Score would give velocity value proportional to the note's amplitude. That was really useful when doubling or harmonizing an audio track with a software instrument.

I recently made a groove template from an audio file of a song. What I did was find a short section where the tempo didn't vary too much and that had the groove I wanted, clipped that out and cropped the beginning and end until it looped cleanly. From that I could determine the tempo. I set logic to that tempo and selected exactly one bar within that short section. I edited the transient markers in that selection and made a groove template of that. If you need more bars to for your groove template you can start with a larger section so that you have several bars worth after you've cropped it to loop. Brian Can you post a screenshot of what you mean? I will post a pic later, but for now, you can just import any song from the 70's.. and try to use the feature. It's easy when you're making a GT from say... a drum recording that was recorded into your session... to a grid/tempo, but I run into problems otherwise.