• from me as well.
  Additionally, it'd be wonderful for me at least to export a specific sequence as a module (FE: 'Save Sequence As..'), as I use a 'MasterProject.mptm' file with all of my commonly-used samples, plugins, and instruments -- using the different sequences as songs/ideas. When I'm done with a track, I like to save it by itself and clean it up so that I end up with a much smaller module which contains only the required samples/data for the song.

Are you aware that when you change sequence, and you then export, it will render that sequence?

I can see how it would be handy to export all sequences to different wave/mp3's though.

I think I might remove the rather useless "limit file size" option (it never made a lot of sense - when normalizing, the file size limit affects the temporary WAV file, not the resulting encoded file) and use the freed-up space for some sequence controls.

Removing "limit file size" would be fine for me. It is indeed rather useless.

Agreed from me as well, although that probably doesn't have much weight. xD

I guess file limit was more of importance when hard drives had less space and also considering songs with endless loops.

@rakib, even for endless loops, I would still use time limit over filesize limit. The only reason why filesize limit could work, is when you export as mp3 and it calculates a different bitrate.

But even back then it was not a sensible metric - why would you say "I do not want this file to be larger than 1MB" rather than "I do not want this file to be longer than 30 seconds"? As already mentioned, this never worked when normalizing as it would measure the un-normalized temporary WAV file size, and especially when exporting to MP3 you would of course want to normalize the file before export, not afterwards. So it's a good candidate for replacement in the UI without having to make the dialog even larger for a new feature.

File size limit removed in r9066.

r9081 allows to export a range of sequences.

Merged to 1.27 in r9142.