Sorry to be a drag but I'm bumping. Thx.

They are all wav files to start with?

I thought that was what export stems did...

You had a thread about export stems didn't you?

Pg 171 in the reference manual I have

Tacman7 wroteThey are all wav files to start with?

I thought that was what export stems did...

You had a thread about export stems didn't you?

Pg 171 in the reference manual I have

All the tracks were recorded in studio one. No imports.
Track 1 always did the recording and when finished I moved the newly recorded event to a new track. I would then record again on track one and move the next event to another new track. Etc.

So I don't know why it's giving a different file format when I drag out to browser and export them. Bug?

What do you get when you export stems?

Tacman7 wroteWhat do you get when you export stems?

Sorry for the late response.

Doing it from the menu produces wavs all the time, however doing it this way means though that all the wavs will start and finish at exactly the same place for each track (i.e. all tracks will be 15 mins or something). That doesn't happen when I drag and drop specific events. If you look at the screenshot you will notice each event contains a song (which I transferred from vinyl).

So rock and hard place.

1) Export stems produces wavs but I have no control over the duration (end point). I was attempting over on this thread:
viewtopic.php?f=151&t=28623

2) Export via drag and drop gives me exactly what I want but the file format seems to a toss up (what this thread is about).

So topic is...

Why would drag and drop give me different file formats?? Each event was created exactly the same way (recorded from the same audio source which was my turntable).

When I drag a midi clip to the browser the default is midi loop or something.

If I want a .mid file I toggle the choice with the alt key while I'm dragging.

Maybe something similar for audio files?

Tacman7 wroteWhen I drag a midi clip to the browser the default is midi loop or something.

If I want a .mid file I toggle the choice with the alt key while I'm dragging.

Maybe something similar for audio files?

I'm selecting a bunch of events and dragging them all at once in one sweep though. The file format still varies. I'll see if this works for one at a time though...

PreAl wroteWhy would drag and drop give me different file formats?? Each event was created exactly the same way (recorded from the same audio source which was my turntable).

Merged audio events (audio parts with the chain symbol in the left corner) will always be dropped as .audioloop* files. So first bounce your merged audio events prior to dragging them to the browser as .wav.

* these .audioloop files are basically .zip files with a .flac file in it and a .xml with audioloop slice info, which corresponds with the event regions within the part.

PreAl wroteWhy would drag and drop give me different file formats?? Each event was created exactly the same way (recorded from the same audio source which was my turntable).

niles wroteMerged audio events (audio parts with the chain symbol in the left corner) will always be dropped as .audioloop* files. So first bounce your merged audio events prior to dragging them to the browser as .wav.

* these .audioloop files are basically .zip files with a .flac file in it and a .xml with audioloop slice info, which corresponds with the event regions within the part.

That is exactly it - great - that sorts it out - thanks!

So another question, I'm not sure if anybody would know the answer, but why is this the expected behaviour? I don't ever want to use audio parts (I'm sure people using it will be fine). Is this behaviour logical?

Thanks...

Happy that this was finally solved. I was thinking of suggesting bouncing them before exporting, but I didn't have a proper explanation to why that would be needed. Niles to the rescue.

Re: merged audio events. I guess the behavior with export as .audioloop could be logical. I like to think of them as pages in a book. If the slices are pages, the merged events are folders for storing such pages temporarily and an exported wav file is a printed book, then it could make sense to let pages in a folder stay pages in a folder when you store them. If you have lots of little edits, the undoable merging function can be useful when trying to keep track of things. I guess the .audioloop is the closest native equivalent for exported files, so, yeah. Personally, I've yet to use .audioloops.