Why does Logic renumber my main source audio files in the bin?

When I'm working with a bunch of wav files added to the audio bin, Logic at some point (I'm not quite sure when) decided to recreate the files and renumber them. So now each wav file has a main name that is the new name+number Logic chose, and then the child of that is the original name+number. You can see what I mean below, with the original folder of files to the left and my Logic bin to the right. Also, the project's actual Audio Files folder on the hard drive has BOTH copies. The original wavs seem completely identical to the newly-created ones in every way except the file name.

User uploaded file


This is extremely inconvenient to work with, because these are chronologically-ordered audio files whose numbers have actual meaning. Why is Logic doing this? Is this standard behavior? What is the purpose of it? Can I override it somehow?

Logic Pro, Mac OS X (10.7.4)

Posted on Jun 29, 2013 3:22 PM

Reply
8 replies

Jun 29, 2013 4:54 PM in response to chrisremo

The top name refers to the entire file itself, the lower represents the regions within that file that are used in your song. If you drag the drag and drop te files directly into the arrangement, Logic gives you the opportunity NOT create new regions, but as soon as you cut or paste or punch into a region in the arrangement, the divided regions will appear with new numbers under the original file. You can "option/click on the little arrow to collapse all the drop downs and you'll just see the originals.

Jun 29, 2013 7:42 PM in response to Data Stream Studio

I understand that in principle, but that is not actually what is happening here. Please refer to my included screenshot. You can see that the original names of the files go from 01 to 17 (in the left in Finder, which are the files I added to the Bin), but Logic created NEW numbered versions that go up to 32, and inside THOSE newly-numbered ones are the ORIGINAL numbers.


To see the ORIGINAL filenames, I have to actually expand the newly-numbered one in the bin, and then inside that is the original numbered filename.


For example, there is an original file called SAMANTHA_02.wav. However, in Logic, that is now referred to as SAMANTHA_18.wav--Logic created that newly named file for some reason, and that is the name that takes precedence in the bin. I have to expand out SAMANTHA_18.wav to see the name SAMANTHA_02, which is the original file's actual name and the name that is useful to me.


The "Audio Files" folder on my hard drive includes TWO sets of these files now. It has the orignal set of wavs, then it also has what appears to be a direct duplicate of those wavs, with the new renumbered filenames for some reason. And those new filenames are the ones at the highest level of the heirarchy in the bin, even though I never added them myself or requested they be created.

Jun 29, 2013 9:55 PM in response to chrisremo

chrisremo wrote:


Logic created NEW numbered versions that go up to 32, and inside THOSE newly-numbered ones are the ORIGINAL numbers.


To see the ORIGINAL filenames, I have to actually expand the newly-numbered one in the bin, and then inside that is the original numbered filename.



The ones "inside" - that you can after you expand - are region names, not files. So in your screenshot, "Samantha_15.wav" is the filename. There is a region called "Samantha_01" that points to the file "Samantha_15.wav." This is easy to verify and see in action by dragging a file, or region, into the arrange and watch what happens in the bin. If you drag the "Sam_15.wav" into the arrange and let go, immediately the "Sam_01" will be selected in the bin. If you drag "Sam_01" into the arrange, it just stays selected in the bin. Now rename it in the arrange and see what changes in the bin.

Witness that in your original files you jump from 14 to 16 with one called "edited" in between. this is why there is a "15" corresponding to "01" and then "18" corresponding to "02."


Making more sense how that works now?


Witness that in your original files you jump from 14 to 16 with one called "edited" in between. this is why there is a "15" corresponding to "01" and then "18" corresponding to "02," adding to confusion.


Here's how to create a situation like the one you are in from scratch: I'll use an example of 6 files, numbered like yours (01 through 06). Drag them puppies into the bin. Select all. Go into Audio File>Copy/Convert. Just hit "save" at the bottom of the next window. Now it is going to ask you about something about already existing and if you want to save or replace. Hit save. Do that every time it comes up.


When it's done you have files called "whatever_07" through "whatever_12" and the regions (if you expand the arrows) are still called 01 through 06. Also, those will be the only files in the bin. Yet if you take a look in the folder in Finder you will see the original 6 files are still there.


The other way to get to where you are is to have all the files in the arrange and to "create new audio files" from the regions, but then you would have to rename all the regions (they'll just be 07 through 12). Also, the originals would still be in the bin. Finally, because some of your regions are dark grey in the bin, that points to them having not been in the arrange yet.

Jun 29, 2013 11:13 PM in response to seeren

I know I haven't placed any regions in the arrange for any of these files except for the first three.


To take one example: Why is the SAMANTHA_17 region--which corresponds to the original SAMANTHA_17.wav--inside of the newly-created and newly-numbered SAMANTHA_32.wav in the bin? I haven't even placed that file/region in the arrange window yet, so I don't know why it would be doing any renumbering at all at this point. Logic simply created an ADDITIONAL wav called SAMANTHA_32.wav, and then for some reason placed a region called SAMANTHA_17 inside of THAT in the bin. This is what I'm trying to figure out. It seems very counter-intuitive.


I understand the difference between files and regions. What I don't understand is why Logic has doubled the number of source files I have (there are litererally two copies of every single one of these wavs in the Source Audio folder for this project, with increasingly high serialized number filenames) and used these newly-created files as the canonical names for the files in the bin.

Jun 30, 2013 12:02 AM in response to chrisremo

chrisremo wrote:


I know I haven't placed any regions in the arrange for any of these files except for the first three.


I haven't even placed that file/region in the arrange window yet...


Which is why I said this:

"because some of your regions are dark grey in the bin, that points to them having not been in the arrange yet."


Why is the SAMANTHA_17 region--which corresponds to the original SAMANTHA_17.wav--inside of the newly-created and newly-numbered SAMANTHA_32.wav in the bin? I haven't even placed that file/region in the arrange window yet, so I don't know why it would be doing any renumbering at all at this point. Logic simply created an ADDITIONAL wav called SAMANTHA_32.wav, and then for some reason placed a region called SAMANTHA_17 inside of THAT in the bin. This is what I'm trying to figure out. It seems very counter-intuitive.


I understand the difference between files and regions. What I don't understand is why Logic has doubled the number of source files I have (there are litererally two copies of every single one of these wavs in the Source Audio folder for this project, with increasingly high serialized number filenames) and used these newly-created files as the canonical names for the files in the bin.

In my last paragraph I outlined one way this could happen, and 2 reasons why I don't think that this is what you did.


The two paragraphs before that detail what I think is about the only way to arrive at your exact scenario. Every little quirk that you are experiencing comes about in this way. I can find no other method to arrive at every single hitpoint than this, which includes:


1) inconsistent region/file names

2) numerically congruent (it's late - I mean you have files 1-6, and then duplicates that are 7-12) numbering system of duplicates

3) the numbers of "2nd generation" duplicate files have region names that correspond to the 1st generation

4) some of these have not been added to arrange, some have, but some haven't.

5) bin shows just 1 version of each file, yet 2 versions exist in folder


Here it is again. Maybe at one point you wanted to copy the files for destructive editing, or convert them for some other reason. Regardless, I strongly believe you, at some point, did the following:


Here's how to create a situation like the one you are in from scratch: I'll use an example of 6 files, numbered like yours (01 through 06). Drag them puppies into the bin. Select all. Go into Audio File>Copy/Convert. Just hit "save" at the bottom of the next window. Now it is going to ask you about something about already existing and if you want to save or replace. Hit save. Do that every time it comes up.


When it's done you have files called "whatever_07" through "whatever_12" and the regions (if you expand the arrows) are still called 01 through 06. Also, those will be the only files in the bin. Yet if you take a look in the folder in Finder you will see the original 6 files are still there.


One other point, just FYI. The regions in the bin are not "inside" the other ones. Think of it instead as you see the "file.wav" in the bin. If you click the down arrow, you are not looking inside of it, you are looking at a list of all its occurances and how they are divided up. In your case, each region is used once, and it is the entire lenght of the audio file. But if you take one of those and chop it up, duplicate it (in the arrange), and whatnot - you'll see how it is one 'master file.wav' and you'll see the list below it.

Jun 30, 2013 12:13 AM in response to seeren

Sorry; I do understand that the regions aren't "inside" the files. When I say "inside" I'm only referring to the heirarchical representation in the bin; I recognize that a region is only a particular logical representation of a subset of a source file. However it still seems very odd to me that, despite never having actually placed a given region in the arrange yet, the full-length region and the the audio file are named the way they are in my bin currently, with the REGION retaining the ORIGINAL name of the source file, but the overarching FILE having gained a new name corresponding to the newly-created and newly-renamed file.


What this means is that if all the files in my bin are unexpanded, the filenames bear no obvious relationship to the original source files that I actually dragged in, other than sharing the same prefix. But the actual USEFUL part of the filenames are the number suffixes that I named myself, which are no longer correctly shown in the bin (or rather, they are only correctly shown in the regions once the files have been expanded).


I definitely never went through any of the processes you describe; I simply dragged the files into the bin, and that was it. I was never presented any dialogue box with an option to save or replace. The reason I'm confident I'm not forgetting that I did any of this is that I had made so little progress on the project before posting this question that I hadn't even had time to place more than the first couple files into the arrange (as you point out).


At this point I'm just guessing that I have some kind of option set somewhere that is prompting Logic to resave or duplicate all added files automatically; I don't know why else this would happen in this way.

Aug 17, 2013 10:41 AM in response to chrisremo

Hey chrisremo.


I have to admit that I haven't read the full dialogue of this thread but I think I could help you out some. I just clicked on the screenshot you provided & I know what's going on:


1. Audio File Folder (labeled here as "Pt2 Audio Diaries") shows the name of the audio files in your folder


2. Audio Bin: e.g. "SAMANTHA_21.wav" shows the name of the actual file as it is right now but you'd have to drag that to the track you'd want it to be placed in. Once you do, you'll see a small waveform in it's place where the "blank waveform" currently is.


3. Next, double click below where it says "SAMANTHA_05", Command + A (to select all), Command + C (to copy) then double click "SAMANTHA_21.wav" & Command + V (to paste).


4. Now your .wav file will show up as SAMANTHA_05 in your audio folder if that's what you want.


The ONLY problem is, in Logic Pro X, Apple, Inc. has taken out ability to delete files from audio folder via the audio bin by using Command + Delete which *****!!!


I hope this helps. If not... Hey, I tried.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Why does Logic renumber my main source audio files in the bin?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.