Why does this happen?

[csiaudio]

Hi,

I've been experiencing this for a long time and thought I'd finally ask someone who might know why this happens.

I have a single stereo or mono 16 bit wav file that was sent to my from a client. When I import it into DP and this happens (see link)

http://www.creativesoundimages.com/mp3/Import.tiff

As you see the first 17 audio files listed labeled 'SLS Detroit Metro' are from one single audio file that was imported. Why is DP listing 17 audio files in my session that all have different times/lengths?

This makes me have to scan the list of now 17 files for that audio file that is the longest in length to import the complete audio file. On top of that, if I don't first click on a different audio file from within the list that is not associated with the import and then select the audio file from the new 17 imports DP will grab all of the 17 files at once as if I wanted to drag all of them into the session. Clearly another bug within DP.

This makes no sense and quite the PITA.

Any thoughts?

[NazRat]

Just speculation, but was the file from someone using Reason/Recycle or part of a loop library? I think that Detroit Metro is from one of the Logic/Apple loop packages. That's the way other programs see REX files - I think the other entries are basically loop markers. PT actually has an option when importing REX files to just include the original or create a clip group. Never imported a REX file in DP so may be way off base, but have seen the behavior you're describing in PT.

[magicd]

As you see the first 17 audio files listed labeled 'SLS Detroit Metro' are from one single audio file that was imported. Why is DP listing 17 audio files in my session that all have different times/lengths?

Not a correct statement. The first 17 items in the soundbites window are not audio files. They are "soundbites". In DP terminology, a soundbite is a set of region pointers within a sound file. All 17 soundbites belong to the same sound file. They are all different sets of pointers within the same file, each with a different length.

When you import a sound file to the Soundbites window in DP, DP looks into the sound file to see if there are region pointers. If there are, DP lists each set of region pointers as a separate soundbite.

I can not tell you how all those soundbite regions were created, but if the audio file came from somewhere other than DP, I can tell you that those regions (soundbites) were created in some other software. DP is just showing you what is in the imported file.

Clearly another bug within DP.

This makes no sense and quite the PITA.

Any thoughts?

It's not a bug. (sigh)

It does make sense if you know what you are looking at.

It might be a PITA, but if you want an imported sound file to only contain a single soundbite, you need to speak with whomever is sending you these files. When you import a sound file into the Soundbites window of DP, DP is going to import all soundbite regions listed in that sound file. If there are multiple soundbite regions in the sound file but you only want one region, how would DP know which region you wanted?

Here is a possible solution for you:

If you drag an audio file to the left side of the Tracks window, that imports the entire audio file into DP and places the imported soundfile into a newly created audio track (if there is any time stamp associated with the audio, the soundbite is placed at that location in the new track). When using this method of importing, DP only imports a single soundbite region - which represents the entire length of the sound file. If you import audio to the Tracks window instead of the Soundbites window, you'll only get a single soundbite per audio file showing up in the Soundbites window after the import.



Dave

[csiaudio]

Thanks for that info Dave I appreciate your help.

I have a question if you happen to read this again: If I have an audio file in DP, extend it to the length I need it at and then export it out - then reimport it for use later into DP via the Soundbites DP - I should only see it as one region correct? I ask this because I have a music library that I source daily for the marketing audio that I make a living at and the files that I did this with DP have the same issue it has multiple regions. Why would it do this if it were exported from DP?

Since I have your ear I'd also like to get your opinion regarding this issue as well if you don't mind:
At least 5 times a day when I grab an mp3 file into DP it will import it into a track but then DP doesn't allow me to do anything further. I literally cannot do anything except 'save' the session manually and then close DP and reopen and it's fine. Now, this doesn't happen all the time…not at all but it happens often enough that it gets frustrating…so, it's sporadic and not predicable.

Thanks for your help!

[Gravity Jim]

It's not a bug. (sigh)

If I had a nickel....

[Tim]

This happened to me just the other day: I dragged one sound file into another networked machine and there was like a dozen files in there. I know about the "pointers" and all that, but DP didn't do this before.
I must start reading those memos.

[csiaudio]

Yeah it would be nice if you could some how tell it to not look at all the pointers unless you want it that way.

I still don't understand if you export from DP and then later import that audio file why there are a ton of pointers on what should be a single audio file with no pointers.