# Question on next Firmware for Play+ **URL:** \ **Category:** Play\ **Created:** [July 18, 2024, 11:06am UTC](https://backstage.polyend.com/t/question-on-next-firmware-for-play/13009 "2024-07-18T11:06:01Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![troxx](https://backstage.polyend.com/user_avatar/backstage.polyend.com/troxx/32/6444_2.png) [@troxx](https://backstage.polyend.com/u/troxx)\ **Post date:** [July 18, 2024, 6:13pm UTC](https://backstage.polyend.com/t/question-on-next-firmware-for-play/13009/8 "2024-07-18T18:13:52Z")
I’m not sure where folk are coming from that they cannot see how useful sample slicing is regardless if a device does not natively sample? A device does not need to sample to slice loops, there are millions of loops available to you already, christ most folk will already have a ton on their laptop, theres even a number of sample libraries like Splice to grab loops from. You would just compile loop samples or samples you wish to slice exactly the same way as you currently compile your oneshot samples into a folder? Whats the difference? If folk can’t see the creative benefit of this, then it’s probably just something that doesn’t excite you and thats fine, we all create things differently man 👍 I’ll link to another post I made already about it… > [@Sample slicing mode](https://backstage.polyend.com/t/sample-slicing-mode/1057/26): > > Yeah I imagine it could be done Digitakt style like, either to a slice grid, or auto slice at transients. The way the Play users folders for it’s algorithms is also important here, so I imagine when slicing a sample it is sliced to it’s own folder, the user is able to select which slice to play by holding the pad and selecting the slice number for that sample, obviously slice would also be an option under chance/action for Random Slice and Random Slice under the randomiser function. The slice … --- _[View the full topic](https://backstage.polyend.com/t/question-on-next-firmware-for-play/13009)._