A nice feature some trackers have is to make a WAV export not to hard disk, but into a sample slot. so one could create a little sequence in a tune, open the WAV Export window and instead of specifying an output file, select a checkbox to render the chosen part of the song into a sample slot.
Edit: Moved to issue tracker http://bugs.openmpt.org/view.php?id=561
I can imagine this could be very useful in some situations.
I hope with all my heart, this gets implemented one day. :cry_fists:
No worries, I still know that I have this in my wishlist. Doesn't make it easier to implement it, though...
Render to clipboard would also be nice.
Oh, and while we're at it, render to printer of course! (SCNR)
:P I was being serious! imagine, just make a selection in the pattern editor and right click, select "copy as WAV" :D
Quote from: "Sam_Zen"I can imagine this could be very useful in some situations.
Ditto! Oldskool tracker songs often used chord samples to cope with channel limits. This would make it very easy to create them out of solo samples. If you want to do real HC oldskool and use just 4 channels, that is.
I think about it too.
But in my variant in the sample/instrument tab have an number of pattern. If it defined, tracker/player are rendering signed pattern to the this sample.
And in signed pattern do not use this sample as recursion!
So simple! ::)
I second, er, third, uh...tenth this request! :P
I was thinking more of building in the possibillity of using rendered channels...
So you can "bounce" your channels and they will show up like that in the pattern editor as a channel with the "rendered" attribute...
See my screenshot to get the picture...
If you add timestretch and basic sample editing that would be supercool for vocal tracks and remixing...
Please also see discussion I opened in:
http://forum.openmpt.org/index.php?topic=5127.0 (http://forum.openmpt.org/index.php?topic=5127.0)
I did an interesting find on how renoise copes with this..they use an open source lib called Rubberband.
http://www.renoise.com/tools/rubberband-timestretch-pitch-shift (http://www.renoise.com/tools/rubberband-timestretch-pitch-shift)
Source code and compiled commandline tool are available here:
http://www.breakfastquay.com/rubberband/ (http://www.breakfastquay.com/rubberband/)
That's quite a different beast from what my original idea is about, though.
Well... I suppose it is and at the same time it isnt..
Only difference is that you are talking about mixdown from Modplug to sample slot (in that case there are no issues with timing) but I was thinking about using a mixdown from some other daw or live recording and the things I have to do to make them become usefull in MPT.
That is why I started a new discussion in http://forum.openmpt.org/index.php?topic=5127.0 (http://forum.openmpt.org/index.php?topic=5127.0)
... mentioning Breakfastquay's Rubberband tool... would it be very difficult to replicate the way renoise uses this opensource lib in the sample editor screen?
What you are suggesting would be very usefull for me sometimes as well, when doing a mixdown in MPT to preserve channels or freeze vsti output to preserve cpu.
Saga has finally implemented this (http://bugs.openmpt.org/view.php?id=561) and it's a huge new feature. Let's test it, and if all goes well it will be in the next release. 8)
oh ... nice.
let's see.
Very nice. It works very well.
I'm a new (french speaking) user coming back to trackers I haven't used since since FT2 (in 91-92 ??) and this is amazing to come back to this.
What do you see as usage for this feature? It's a great way to add pitched delays.
Is this rendering function a first step to something else? I'm thinking of a base to something that could export each note of a pattern and create a multisample instrument.
This is a way to hear the right sound on format/platform that doesn't support the VST format but keeping anyway the small size of module (i.e not bounce to wav).
I'm listening to mod on my iphone using the modsize app. 8)
QuoteIs this rendering function a first step to something else?
No, it's a feature on its own that was not built with anything else in mind. A plugin grabber may happen in the future but that's completely independent of this feature.
Thanks for the reply.
Oh, if it'll lead to channel-plugin freezing someday in the future, it will be fantastic! No, doubly fantastic! :D
Is there a request or should I write one?