Non Timeline: Export

[tweed]

Can't seem to make this work:
Project > Export > Project/Range. Does nothing. Checked Documention, no mention of Export function.
Just wondering if I'm missing something simple(entirely possible).

[male]

Can't seem to make this work:
Project > Export > Project/Range. Does nothing. Checked Documention, no mention of Export function.
Just wondering if I'm missing something simple(entirely possible).

Not implemented. Just create a track called Export (might want to set the recording file type to f32 if you think you might clip) and then route what normally goes to your system outputs back into that track and record. You'll find the .wav in the 'sources' subdirectory of the project (you can then use sox or whatever to resample, dither, encode etc.). This has been my workflow since forever... I find it works well enough that I've never felt the need to actually implement any kind of formal export dialog.

[tatch]

you can also use cadence/jack render, freewheeling mode would be pretty useful for that too.

[tweed]

thanks for the help guys. i was just wondering why that particular menu item was not responsive.

[Vixus]

Can't seem to make this work:
Project > Export > Project/Range. Does nothing. Checked Documention, no mention of Export function.
Just wondering if I'm missing something simple(entirely possible).

Not implemented. Just create a track called Export (might want to set the recording file type to f32 if you think you might clip) and then route what normally goes to your system outputs back into that track and record. You'll find the .wav in the 'sources' subdirectory of the project (you can then use sox or whatever to resample, dither, encode etc.). This has been my workflow since forever... I find it works well enough that I've never felt the need to actually implement any kind of formal export dialog.

Couldn't the menu option just automate this?

[male]

Couldn't the menu option just automate this?

Well, it could automate some of it... You'd still have to select which outputs to record and into what track. And even then, currently I can create four export tracks and connection their inputs to different outputs of Non Mixer and other things and export it all at once (for example, exporting an abisonics b-format mix and a stereo mix at the same time). That kind of flexibility is not practical in dialogs. Part of the philosophy of Non is allowing users with diverse workflows to do whatever they need, not attempting do codify lowest common denominator in dialogs and wizards like other projects do.

[Vixus]

True, but it could be handy for a quick stereo/mono mixdown, for emailing to someone or whatever.
It would just route all unmuted tracks to a new one and bounce.

Anyway, I would be fine with the manual routing, so it might be worth just getting rid of the menu option since it's not doing anything.

[male]

True, but it could be handy for a quick stereo/mono mixdown, for emailing to someone or whatever.
It would just route all unmuted tracks to a new one and bounce.

Anyway, I would be fine with the manual routing, so it might be worth just getting rid of the menu option since it's not doing anything.

Generally one wants to export through effects/mixing. What those external entpoints are is technically impossible to determine through JACK. (however, I'll grant that one could assume that whatever is connected to the system outputs should be recorded and be correct most of the time).

Anyway, what we're talking about here is a feature that would A) add code to Non in order to allow users to accomplish what is already both possible and trival and B) introduce the appearance of inflexibility. As I said, that goes against the philosophy of being light and flexible.

It should be noted that I have already removed the Export menu item since this thread was started.