Duplicate files on import

[Phil O]

Two more questions.
What file format are you exporting to?
How do you import? (drag, command-I, etc.)

Phil

[Sean Kenny]

Two more questions.
What file format are you exporting to?
How do you import? (drag, command-I, etc.)

Phil

I am recording in Broadcast Wav and exporting in Broadcast Wav. I use cmd F1 to import.

Just noticed something, if I just drag the file from the tracks overview to a "New" folder (or drag from the audio folder to the "New" folder, when I import or drag to the tracks overview/sequence editor I just get the single file.

It's only when use the proper export function for the soundbites window that I get the duplicate on import or drag to tracks overview/sequence editor.

So it would appear that the export process is the source of the problem

[bayswater]

Two more questions.
What file format are you exporting to?
How do you import? (drag, command-I, etc.)

Phil

I am recording in Broadcast Wav and exporting in Broadcast Wav. I use cmd F1 to import.

Just noticed something, if I just drag the file from the tracks overview to a "New" folder (or drag from the audio folder to the "New" folder, when I import or drag to the tracks overview/sequence editor I just get the single file.

It's only when use the proper export function for the soundbites window that I get the duplicate on import or drag to tracks overview/sequence editor.

So it would appear that the export process is the source of the problem

I can duplicate that. If I export a soundbite, when I pull the exported file back into DP, it shows one audio file with two regions. I tried it a few times with files of different names.

The first soundbite is named the same as the single region in the original audio file, and the second soundbite has the Finder name of the audio file, with ".2" appended to it. If you rinse and repeat, the next imported region will have a ".3" added.

So it might look like this is happening at export time. But if I open the exported files in DSP-Q, they only show the one region with the expected name. So it's more likely happening at import time. If that's so, perhaps this is a side effect of DP trying to make sure each soundbite has unique name?

[philbrown]

But if I open the exported files in DSP-Q, they only show the one region with the expected name. So it's more likely happening at import time. If that's so, perhaps this is a side effect of DP trying to make sure each soundbite has unique name?

The durations are different though (see the original screen shot).

[Sean Kenny]

I can duplicate that. If I export a soundbite, when I pull the exported file back into DP, it shows one audio file with two regions. I tried it a few times with files of different names.

The first soundbite is named the same as the single region in the original audio file, and the second soundbite has the Finder name of the audio file, with ".2" appended to it. If you rinse and repeat, the next imported region will have a ".3" added.

So it might look like this is happening at export time. But if I open the exported files in DSP-Q, they only show the one region with the expected name. So it's more likely happening at import time. If that's so, perhaps this is a side effect of DP trying to make sure each soundbite has unique name?

It's a relief to know that's not just me then. Thanks for this.

Another instance this happens is when I export a vocal from a project, I consolidate the vocal by highlighting all the soundbites comprising the vocal and merging, then export the 'mg' merged file. When I import the same to a fresh project I get the merged file and also all the individual soundbite/regions that were used to create it.

It's a really annoying feature, although if it were an option I can see it being useful sometimes, it's just most of the time I don't want it

[bayswater]

But if I open the exported files in DSP-Q, they only show the one region with the expected name. So it's more likely happening at import time. If that's so, perhaps this is a side effect of DP trying to make sure each soundbite has unique name?

The durations are different though (see the original screen shot).

In Sean's screenshot they are different. But in all my tests, they are the same. Weird.

[philbrown]

But if I open the exported files in DSP-Q, they only show the one region with the expected name. So it's more likely happening at import time. If that's so, perhaps this is a side effect of DP trying to make sure each soundbite has unique name?

The durations are different though (see the original screen shot).

In Sean's screenshot they are different. But in all my tests, they are the same. Weird.

Mine are different too, and it is weird!

[bayswater]

When I import the same to a fresh project I get the merged file and also all the individual soundbite/regions that were used to create it.

It's a really annoying feature, although if it were an option I can see it being useful sometimes, it's just most of the time I don't want it

The merge function is simply creating a new region within the original audio file that defines the merged piece, not creating a whole new audio file. Bounce to disk will create a new file with one region.

[bayswater]

Mine are different too, and it is weird!

Are you exporting from the TO or SE? Maybe the locators or sequence start and finish info, etc is being used in defining the regions. I exported from the SB window, and the soundbites are not being used anywhere in the project.

[philbrown]

Mine are different too, and it is weird!

Are you exporting from the TO or SE? Maybe the locators or sequence start and finish info, etc is being used in defining the regions. I exported from the SB window, and the soundbites are not being used anywhere in the project.

I have a procedure where I pull in the same biolerplate file into a job every week and the file I'm dragging in is 10+ years old so I can't really answer that in my case. It's only showing one region (the whole file) in DSP-Q though. I drag it into the SB window when I import it.

[Sean Kenny]

Here's another import I just did duplicates are exactly the same length. Files were created exported and then imported using the export/import feature in soundbites window

[bayswater]

I've tried a few different configurations and methods, and I can't get anything to show up with different lengths, start times, etc.

But as long as you are getting soundbites of different lengths, this does have consequences if you choose the wrong one to place in the project. If they are the same length, it just boils down to clutter and inconvenience.

Did you report this as a tech note?

[Phil O]

The first soundbite is named the same as the single region in the original audio file, and the second soundbite has the Finder name of the audio file, with ".2" appended to it. If you rinse and repeat, the next imported region will have a ".3" added.

That's what I'm seeing too, Sean. But the SB's are all the same length. I'm going to have to play with this a little more.

Phil

[Phil O]

This isn't happening on my system when I export to Core Audio Wave. I haven't tried other formats yet. It may be a broadcast wave issue. Dunno.

Phil

[Sean Kenny]

I've got a feeling it is the broadcast wav format that is the issue.

Bit busy in the studio at the moment but as soon as I get the chance I'll dig a little more

Thanks again guys

Cheers

Sean