Audiobook workflow - best to master one big file or many?

[cello23]

I've recorded my first audiobook with around 30 separate clips. 

I'm wondering about workflow efficiency and sound consistency. Is it best to:

a) record/master a large file and then output to clips? 

b) record a large number of clips and batch process?

I've found it hard to judge consistency between clips, eg slightly different attack/energy, perceived volume. 

Sometimes shorter clips end up with latent differences exaggerated on mastering.

And they're a faff to process.

If I do them in a oner, will I get more consistent mastering? 

And if I join my raw clips into a single file, will it be easier to see/hear inconsistencies?

I've tried using Multitrack but keep losing files. I prefer working directly with the wavs. 

My DAW is Audition +RX standard. 

What do long form engineers do? Is there a 'best workable clip length'?

Advice appreciated!

Thanks, 

Jules

[SteveG_AudioMasters_]

It's always been the case that longer reads tend to be more consistent - within reason, of course. It's the same with voice-overs; if you need to re-record, then do large chunks, not small ones, as the small ones never match properly. There is no such thing as a best workable clip length - this depends entirely upon the reader and what they are comfortable with. You also have to note that people often sound different from one day to another (think congestion, colds etc), so ideally, do all of the read for a single project in a day if you can, and if you can't, then split the work into chapters, so there's at least a reasonable pause between sections. Also, only let readers drink clear non-alcoholic liquids during a read. Generally it's best to sip water, to keep your mouth hydrated.

Since in Multitrack, Audition records direct to wav files (and is remarkably good at it), if you are 'losing files' (?) then you must be doing something pretty strange, I'd say. Can you explain a bit more about that, please?

[cello23]

Thanks Steve.

'The small ones never match properly.' - yes, this is the issue. Will stick to bigger clips.

'Doing something pretty strange' Probably 🙂

I don't understood the relationship between files in the file folder and once they are dragged into Multitrack view. 

I'm used to recording/editing waveforms. I only used the MT to compare the clips.

When I changed something in the clips dragged into the MT, I thought the original wavs would still be intact. But it seems deleting them from the file area is deleting the originals, not an imported copy? 

I thought it worked like the Batch Process/Match Loudness windows, which seems to be a processing bay rather than the actual files. So I lost some files. 

I just haven't got to grips with the organising concept yet!

Thanks.  

[SteveG_AudioMasters_]

The files in the files window are the actual original files. But when you appear to have dragged one of these onto the track layout - well actually you haven't. All you've done is to put a virtual reference to the file in there. If you alter the length of it on the track, it doesn't touch the original file at all; it only affects the amount of it that is played back. If you add EQ, then this just EQ's the playback of the file, and doesn't touch the original at all either.

But if you double-click on the 'file' on the track layout, it will open the original file in Waveform view. Any changes you make to it there will be reflected in the Multitrack view, and if you make changes, you'll get a warning upon returning to Multitrack saying that you've altered the file (you get little ! marks as well, to remind you). Batch Processing works on the original files, as does Match Loudness - when you save the results, it alters the original files.

If you remove a file from the Files list in Multitrack, then a placeholder will remain on the track display, and if you save the session like that, then you'll get an invitation to 're-link' the files upon re-opening it. Obviously if you removed the placeholder from the track, any reference to it will have gone completely, so you won't get the invitation to relink.

You only get duplicate files created if the files you try to place in a multitrack session aren't at the session sample rate - or they are in a format that Multitrack doesn't recognise or work with - like MP3 files, for instance. These are decoded to wav files, and it's the wav file copy that's referenced in the session. And if you don't save that Wav file at the end of the session, you'll be back with the 'placeholders' situation again...

Does that make it any clearer?

[cello23]

Steve, 

This is great, thanks, because: 

I didn't realise there was such a difference between dragging and clicking - thought they did the same thing and didn't affect the original file. 

Also, I didn't realise Match Loudness and Batch altered the original files without asking for a save. I've been 'exporting as' with a tag - phew - but good to know. Because, for example, I could try it out to test-drive the changes, and not realise it's altering the original file without a sign. 

Really helpful!

Jules