Re: [Bluemusic-users] Exporting Stems for Mastering
Brought to you by:
kunstmusik
Menu
▾
▴
Re: [Bluemusic-users] Exporting Stems for Mastering
|
From: Steven Y. <ste...@gm...> - 2008-12-30 17:38:50
|
Hi Michael, I think having option for render time start from zero or use render time start is good. I think maybe at this point I should mock up the UI for options and maybe graphically it'll be easier to understand what is going on. As for EDL, I'm not too familiar with it myself, but someone had brought it up here before and mentioned it's used in the video editing world. If I remember correctly, the file format is text. It's a secondary thing we can look at, and perhaps other formats as well. Thanks! steven On Mon, Dec 29, 2008 at 8:07 AM, Michael Bechard <got...@ya...> wrote: > Most of the time when I export the stems, if the objects are near time zero I'll just use time zero; it's easier to line them all up in the sequencer that way. But if the objects are deep into the timeline, I'll use some other time offset. > > For some layers it wouldn't be a good thing to export from the start of the first sound object. Most of the time my sound objects are aligned with the tempo, but on occasion they aren't, and trying to align those in the sequencer with the rest of the piece would involve some guess-work. > > I guess my preference would be to have it configurable? I would at least like to have the option of exporting from the start-time marker and not always time zero. Perhaps by default it would start at the time marker, but a global option would change it to use the first object start-time in each layer. You could also make it customizable on a per-layer basis, in addition to the global option. > > I'm not familiar with EDL. How compatible is that with other software sequencers? > > Michael > > > > ----- Original Message ---- > From: Steven Yi <ste...@gm...> > To: blue users mailing list <blu...@li...> > Sent: Sunday, December 28, 2008 6:05:06 PM > Subject: Re: [Bluemusic-users] Exporting Stems for Mastering > > Hi Michael, > > The dependency issue isn't really an issue I think, I've got it worked > out in my head how to get around it. > > One of the questions I had asked Clemens was the idea of generating > all material from time 0, or truncating and starting the export for > each layer at start of first object on layer. I imagine time 0 would > be easier to then import into another program, but if using something > like EDL's it could be nicer to have output starting at first-object > start, or even generate per-object versus per-layer. Any thoughts on > time 0? > > Thanks! > steven > > On Sun, Dec 28, 2008 at 7:00 PM, Michael Bechard <got...@ya...> wrote: >> 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 <ste...@gm...> >> To: blue users mailing list <blu...@li...> >> 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 >> Blu...@li... >> https://lists.sourceforge.net/lists/listinfo/bluemusic-users >> >> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Bluemusic-users mailing list >> Blu...@li... >> https://lists.sourceforge.net/lists/listinfo/bluemusic-users >> > > ------------------------------------------------------------------------------ > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |