Not yet, but I’ve been researching the wav chunk header that TE have used, once I’ve figured it out, exports in 44.1/16/stereo will have an option in the settings to enable embedding that slice info into the wav file header.
Edit: Current version can export for OP-1 Field/ OP-Z depending on the chosen aif audio context.
The other OP-1 Field specific feature is a slice from tape.json on the slice panel, which I have been working on this evening.
i can’t thank you enough for the “trim right” option! is it possible to apply “trim right” to all selected samples at once?
Not at the moment, but I have some “selected item” operations on my todo list, batch trim is one of those operations, and I think those features will make the 1.4 release over the weekend.
this will be a life saver! thanks a lot in advance!
quick question: for the sample trim function, can I in general change the sample start and end selector position? I‘m asking because on my iPad I tried this and it‘s not possible.
@brian3kb Loving the trim right 
-> +1 for batch trim right 
I did notice a little bug:
Thanks! And this is fixed on the next release as I’ve been moving around/rewriting a lot of the editor stuff the last few days.
I’ve been rewriting a lot of the editor, so selecting part of the waveform to affect with the editor options will be possible in the next release.
super cool ! 
I think the sorting by phrase comes from Loopcloud samples often having the key set into the file name - i.e. XZ_125_Cm_Dodgy_Bass_1.wav so was thinking there’s some useful data set into the file name.
Thinking further on this - how about some kind of API that allows ChatGPT to write a script that drives your app?
So one day we will able to do something like this ( blazing head on!):
Download best copy of Beethovens 9th as a wav, isolate the fourth movement incorporating Schiller’s Ode to Joy - run this through Lalala.ai to produce the isolated Choral Stems, work out tempo and key, and split into 32 parts and repitch each part from F Major to C minor.
Boom! 
btw another thing that blew my mind is the ability to import OT slice data. I was always feeling super lazy to “transfer” my OT samplechains (which are naturally not “spaced” perfectly) to DT but thanks to your tool, I was able to “port” many of them, and trim “right” (which is super crucial because of the limited space in DT) in a mere minutes!
you deserve a medal!
I‘d like to propose another feature as an iPad user who is not relying on the Transfer App:
Visual start and end points in the kits audio waveform (a short click)
Problem:
I would like to record a created kit into the DT and I need to make sure to crop the exact start and endpoints for the slices to align.
Solution: an option to prepend and append a short defined click that I could use as a reference to crop my sample.
Thoughts?
Would a very short audio pop, outside the audible range that shows up on a waveform (and ideally would trip the DT’s threshold record start) do what you need?
it would, preferably at the start and the end.
This could also be a selectable option.
As I’m making this mostly for myself to use, I’ve been adding things that I always spend ages on doing manually - OT slices being one of those things; so happy to hear others find those odd features useful too!
And when space is really limited on the DT, you can use the global pitch up export in the settings panel (or use it just for the effect). 
Are you building the chains then playing them out to the Digitakt over audio?
And if so, are you doing that from DigiChain or opening the exported file in another app to playback?
Trying to understand your workflow (and thus digichains capabilities) here. So you
I thought digichain went from multiple files to one combined file, not the other way around ?
(Sorry for newb question, haven’t tried to explore digichain as I’ve not personally found chains useful on my M:S)
If you drop a wav file along with its accompanying .ot file (generated by the Octatracks sample editor when creating slices on the hardware), when you click the slice icon on the list (it will have an OT icon), you will see an option to split the file into new samples with their start/end points taken from the .ot file.
And while DigiChain’s primary function is to build sample chains, it can also slice files into new samples. It can also be used to simply batch convert everything dropped in into the chosen sample rate, bit depth, mono/stereo.
Use the 120 slice grid, drop 120 of a drum sound (e.g. 120 kicks, 120 hats etc), build a spaced even chain pitched up an octave on export, do this for 6 files, then drop that as a folder on the MS, and you have a great drum machine with loads of variation using length value of 1 and then changing the sample start position to get to each “slice”.
I understand you can do that, I just don’t find it useful