Richard's suggestion is exactly what I myself do when the need arises. There is no technical reason that I can think of why it shouldn't have worked for you, assuming the copy was done correctly. One reason there's not a built-in function for this is that you may want to do the copying in various different ways. You may want to move, hardlink, or softlink etc. If we're talking a client with waveform data attached (e.g. a non-timeline session), the copy could involve many gigabytes of data and take a long time, run out of free space, etc. Also, I'm just philosophically opposed to duplicating OS-level features (such as file management) in myriad different applications.
On Wed, May 15, 2019 at 6:06 AM Peter Lutek <[email protected]> wrote: > On Tuesday, May 14, 2019 6:29:00 P.M. EDT, Richard wrote: > > > All I did was to find the equivalent files in my prepared mixer > > with the strip called "Stereo" and copy them over the ones in > > ~/NSM Sessions/nsm-test-session/Non-Mixer.nOOYI. > > > > Now when I open the modified session in NSM I get my Stero > > Mixer mixer instead of the empty shell I started with. > > thanks for that, richard! > > unfortunately, for my project it didn't work completely. non-mixer didn't > load all of the strips i had set up, and then it ended up frozen -- i > couldn't even close it without shutting down the computer. > > so, i guess the most secure usage would be to always let NSM start, save, > and manage non-mixer sessions -- that ensures non-mixer projects exist > within an NSM "ecology" right from the start, so that we can integrate > other JACK clients as becomes necessary later. > > ...i'd be curious to hear from jon liles about the design methodology > around these sorts of questions, if he's listening in... :) > > cheers! > .pltk. > > > -- > peter lutek | improvising musician in toronto > peterlutek.com > > >
