Hi, I'm sorry, I'm unable to find this... May be my memory failed.

 

I'm now just comparing the tiny differences in what you said above and what I did. (we reach same goals)

Your approach (in summary) is...
[1] Split large item in track into smaller items
[2] Convert smaller split items into regions
[3] Render regions (and let rendering handle smart naming)

My approach (in summary) was...
[1] Set markers in track
[2] Convert space between markers into regions (Used "SWS: Convert markers to regions")
[3] Render regions (and let rendering handle smart naming)

So - Pros and cons? Splits versus Markers
Both are easy to make happen in real time (real time was important for me)
(Key S to split while playing) or (Key M to add marker while playing)

But after that I remember finding it fiddly to quickly visually inspect all the splits in a long track
but really easy to inspect using markers.
So markers ended up being the more convenient approach for me; maybe because...
- it was always just one large stereo track at a time that I was working on (never a multitrack scenario)
- I had no intention of editing any of the regions (yet), (didn't care about fades or item processing of any kind)
I just wanted them dumped to disk with useful names (as fast as possible - because many many hours to work through).

 

Last edited: Oct 5, 2020

How about Reaperans, or Reaperees, or maybe Reaperista? Or Those Who Eagerly Enhance The Entire Roar, in short TWEETER?

 

Maybe Reapernauts or even Reapernuts!

 

But his stated goal "just the sample and nothing else - that I can then save to a mini library."
i.e., he does want the external files - for as many samples as he can usefully extract from his original file.
Building a library - presumably wants to re-use in other projects too.

Absolutely NOT wanting to start an argument here - but not clear to me.
Can you help with the details of a scenario where that happens - I haven't figured it out yet. I'm feeling slow today.

 

Yes. And I stated it because we don't know if op knows this already.
My example of "details of a scenario" are when I see that a newb has constantly imported the same drum audio file for the duration of a song, and thus has a huge amount of audio data for that project when, if they didn't edit the sample destructively, could have been just 2MB of audio data and copied regions. Which is repeating what I already said before.
daw 101.

 

I rather like Reaperistas. Reapersaurus? Maybe not.

 

I am now one of "the Reaped". Thank you Cockos - I liked it

 

Cheers, I've woken up now. So, now I understand why that baffled me. and maybe worth explaining.
It never occurred to me that any DAW would just duplicate wavs like that - and as far I can tell they don't.

I just explored it in Reaper.
Firstly, before saying what Reaper does... just clarifying how I'm using the word 'import' (traditional I think)
[1] Importing, as in bring an audio file into the project's folder on disk.
and
[2] Importing, as in importing an audio file into a track as an item/region (or whatever word you prefer)

For [1] I guess I'm used to just manually putting all the audio files I'm going to use where I explicitly want them to be,
rather than letting the DAW import on my behalf. But it's nice that the DAW can do that for me if I want to let it.

For [2] This is what I normally think of when someone says 'importing'.
It's just "creating a region that refers to an audio file that I have already manually located in my project"
And of course, importing the same audio file to multiple regions costs nothing;
the multiple regions just refer to the same audio file.

---

How does all this work in Reaper ? (traditionally and smart I hope)

Two of Reaper's settings are relevant
[1] Global preferences
[2] Project settings
In my Reaper, the default global preference is "Copy imported media to project media directory" set to OFF
and I don't remember ever turning it off (but maybe I did)
I would have turned it off if I had encountered it importing files.
and would have been stunned if I had encountered it importing and duplicating files.

In my Project settings (also mostly just default I think)
the Setting for "On import of media to project:" is by default set to "Use global preferences (do not copy media to project)"

So, Reaper looks like it 'can' do smart importing of media files into the project
but, by default, its settings favour my manual approach to organising those media files.

So, let's try to fool Reaper and force it to do dumb things like duplicating files.

I set my project settings to "On import of media to project:" set to "Copy media to project path"

I imported a wav file (from outside my project folder) and sure enough
Reaper obligingly made a copy of the wav file in my project folder.

Then I repeated the same action, i.e., import the same wav file onto a second track.
No way was Reaper going to be dumb enough to duplicate that file.
It just immediately recognised that the file was already in the project and made a new region with it

No surprises anywhere.
So now I still don't have a scenario where all this file duplication is happening.

Which DAW is guilty of doing this?
Not Reaper - nor any DAW that I've encountered (yet)

 

I think we have a winner

 

Mischen is definitely possible, especially when it comes to Reaper!

 

But Mischen vodka and Champaigne must be avoided at all costs. My stomach still hurts damn...

 

Just leave out the sparkle-water and all is good.

 

Newbs do this. Not the daw! I see it first hand every so often.
First time I saw it was with a Logic user, when Logic's default is to be able to copy regions!
And I've seen it with Audacity and Cubase.
I guess they wrongly think that one piece of audio can't be used multiple times, and don't know that a region just references the audio and can be edited non-destructively.
But I don't know what a newb thinks, do I?

Shame my explanation, which is true, wasn't good enough for you! And you felt to write a tldr comment and test a daw or something! haha.
And both u and Noa seem confused! hehe. 'Agreeing' over things when u both don't seem to know what I'm on about!

Hey, u both know that Steve has left AS, yeah?

 

Of course!
If you have 50x duplicates of the same 1MB drum audio file for 3+mins of a song in just one project, what happens if newb does this with every project No Avenger???
No storage space, or more storage space? hmmm.

 

Never happened to me, in no DAW. Maybe I was just lucky?

 

I know, right? Me neither, unless I chose to create a dupe audio file for destructive editing like pitch or something.
But you are not a newb! And probably didn't even start out as one!
In Logic, since the beginning, if you want to create a dupe region that refers to an audio file, it's one modifier key and a click.
But equally, I guess it's just as easy for a newb to action a Create New File from Region command and end up with 4mins of the same drum loop region as 40MB as opposed to 2MB! haha.
Saw that with students at a music college I visited!
And I saw it with Audacity with two people who "just" wanted a free simple audio tracker (I did try to warn them off of Audacity!), and they had mutiples of the same file amounting to 100's of MBs! hehe. Plus alll these weird tmp files that Audacity makes! Crazy.
And the same must be do-able with Cubase, because I saw the same affair in students project files.
Strange, but true say bruuuuh!