Re: Exporting Stems for Mastering

I'm all for exporting blue projects as wav files on a file-per-layer basis. This is pretty much what I do anyway right now, once I get to a point in the project that I feel is ready for mixing. And as far as figuring out which layers are affecting the sound, I wouldn't have a problem if you just ignored the issue and forced the user to mind those details, make them police their own sound-making layers. I like the file-naming scheme proposed.

Michael



----- Original Message ----
From: Steven Yi <stevenyi@...>
To: blue users mailing list <bluemusic-users@...>
Sent: Sunday, December 28, 2008 5:53:22 PM
Subject: [Bluemusic-users] Exporting Stems for Mastering

Hi All,

I was having a conversation over email with Clemens von Reusner about
implementing a feature for exporting audio from a project for
mastering in other programs.  I remember conversations with a few
people about this kind of thing and wanted to open up the discussion
to see about what would work best for everyone.  I myself do all my
work in blue so I'm probably not the best at figuring out what
everyone would want so am interested.  Clemens sent this idea:

[start quote]

Doing the final rendering to disc I found it useful to start with time
0 and to set the end with the yellow vertical marker - didn't care
about the silence between single objects. Working on details before, I
selected only the necessary tracks and variable start and end time
with the markers as well.

Maybe this would work?

1.    Vertical Selection
1.1   Unmute the tracks to be rendered

2.    Horizontal Selection
2.1   Rendering from time 0 to the last object
2.2   Set green and yellow vertical markers to set rendering start/end

3.    Files
3.1   Create single file
3.2   Create multiple files
3.2.1 Use soundlayers name, if there is no name given then goto 3.2.2
3.2.2 Add suffix to projectname incrementing automatically starting with
     the first soundlayer: 01...nn

     name-format: projectname_tracknumber.extension

     e.g.: 5 tracks, 3 and 4 are muted. Rendering to disc will generate

     project_01.wav
     project_02.wav
     project_05.wav

...and for systematically reasons somebody may need to...

3.2.3 Create multiple files II
     Create multiple soundfiles for each unmuted track and single
     soundobject

     name-format: projectname_tracknumber_objectnumber.extension

     e.g.: 3 tracks, track 2 muted, track 1 contains 3 soundobjects,
     track 3 contains 2 soundobjects:

     project_01_01.wav
     project_01_02.wav
     project_01_03.wav
     project_03_01.wav
     project_03_02.wav

[end quote]

There are some issues in regards to script-based objects process
correctly if objects depends on others, but I think it'll be easy to
take care of.

I also remember someone mentioning EDL (Edit Decision Lists).  I
haven't worked with them but I remember the last time I looked at the
format it seemed easy enough to generate.

So we have a number of possible ways to export the generated files.
I'd like to ask what possibilities you would like and I imagine we can
make an export dialog to support the different options.

Any thoughts appreciated!

Thanks!
steven

------------------------------------------------------------------------------
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users



     

------------------------------------------------------------------------------
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users