if you render a selection you can bounce/render anything within a pattern regardless of it’s position within a pattern and regardless of the pattern length. For example: you could bounce step 4 - 8 within a 16 step step pattern.
This would just give you a more precise export, that doesn’t require any triming and extra fiddling and would just be a huge timesaver all in all.
A yes.
And how would this work on longer samples?
I could imagine it would cut them off?
That way it could be used as a slicer perhaps?
With trackspeed and the chosen steps being the resolution.
Although im afraid it cant render beyond the first step.
But dont know that technicality.
Edit. O no duh. You can only select the starting step ofcourse 
I really think that this functionality would benefit my workflow.
Maybe to do it with a shortcut key combination, as it is a thing that could be an integral part of the way I like to write music with!
I’m finally getting Play Plus and this feature is crucial. Users should be able to bounce the synths and the drum engine to a sample.
you can already. Just solo the tracks you want & render pattern (maybe it’s called export pattern, not sure). the new sample will be in your renders folder.
Yeah I know. But all those exported files will have irrelevant names like master.wav or whatever.
I think a key thing to consider here is that if I render a “pattern”, just to get a note at the beginning of that pattern, then the re-imported sample will have a ton of blank space at the end, taking up extra sample memory time. If I do this even a few times, I’ll have quite a bit of “dead space” being wasted in my sample pool memory which is limited… Render and re-import only a selection would be most welcome to me. 
true true
What if you make a shorter pattern for export? I mean, track length is adjustable.
If you mute all the tracks except one and render the pattern, will just the one pattern be audible in the render? Or does it ignore the mute state? If it ignores the mute state, that’s kind of a bummer.
Export respects track mute states.
To be honest, I’m quite happy with the workaround. It’s slow but allows me to achieve everything I need. The only thing I miss though is the ability to rename samples in the sample pool. When using this technique, I end up with numerous samples called ‘master.wav’ in my projects.
I recently thought “wouldn’t it be cool if the Play could load exported waves” so I tried it. I expected to be blocked loading the exported samples and was amazed to find this works. Kudos to Polyend for not limiting file access when loading samples!
This amazing capability opens up Play not only to layering sounds and creating chords but also layering effects like differing delay lengths, and getting 100% wet sounds which the Play normally does not allow for.
This capability of the Play and Play+ only makes it all that much more obvious that these machines desperately need a DELETE capability and for that matter the ability to rename samples in the Pool.
I have a project called Sampler where I can load in any samples I want, trim them, trim the pattern length and export. That rapidly ends up creating a total MESS of exported folders.
As noted by many of us, being able to delete files and folders is low hanging fruit that would make the Play’s so much easier to work with.
On top of that, the ability to rename is already in the Play, but renaming samples in the pool is not currently allowed. That would make this “resampling” capability all that much more useful if we could sample layers and not have a pool filled with files named “master” or “reverb”.
There is no reason we should have to constantly pull our SD cards just to delete and rename things. The Play is fully capable of this.
PLEASE OPEN UP FILE OPERATIONS!!! It’s not even hard to implement as you have all the pieces already in place.
Actually playing with this on tracker+and it leads to amazing results yes please