Convert WaveTables to Window & Position-based loops (admittedly, a bit rough, but basically it means if you have xx amount of wavetable positions available, it creates xx amount of looping samples out of the original sample, and sets volume to 00-7F for the selected Wavetable position, and the rest are silent.
Mono & Stereo support
I’ve had that going for a couple of months (also .SF2 .REX .RX2 import, and .IFF import I recently put in for those interested in OctaMED / Soundtracker / Protracker), but today I put in, after receiving a bunch of requests, .PTI Export.
This should, in theory:
Save Stereo / Mono samples
Save the correct LoopMode & LoopStart&End
Save Max 48 Slices (so if there’s more, they’re not saved).
While I don’t have a Polyend Tracker device to test this on, at least the Export followed by Import works.
If you’re interested in this, please check out the newest build from here.
If you run into any issues, please let me know (and perhaps send me a screenshot or the .PTI file (original .WAV).
Am also on Gumroad.
Paketti is donationware/supportware/patreonware.
Good to see you here as well. If there is anything we can help you with or you got things to test, make sure to drop it in here as well. I‘m sure the community would love to help you in anyway we can
Hi @Sandroid !
And thanks for your previous help in testing out the .PTI Import.
So, I’ve been mostly using Stereo samples, with a simple forward loop, and cutting “more than 48 slices” down to 48 slices max. There was that GitHub Repo which helped me quite a bit, but it only targeted mono files, for the longest time i was loading stereo stuff as mono, until it was brought to my attention that some .pti files may have two channels, too.
I mean, it’d be helpful to know what the difference is between a “Beat Slice” and a “Sliced Sample”, and whether different Loop modes are exported correctly.
A thought occurs, though, it might be useful to be able to read the Transpose Pitch (Coarse) and Finetune pitch of an instrument saved as .PTI on Polyend Tracker - and to then be able to export those from Renoise to Polyend Tracker.
Basically I’m after some way of ascertaining that all the required/available features of the .PTI format are properly imported and exported, without any data loss, that’s the ultimate goal I think.
Btw here’s a little appetizer screenshot of how Import worked a while ago:
Stereo samples are usually interleaved :
riff header → left and right mixed
pti files are sequential
pti header → left → right
In other words, if you try to “patch” a pti file outside the tracker, you cannot simply exchange the riff header with the pti one (those reverse engineered one) on a wave file.
You have to rewrite the left and right channel sequentially.
Just my humble observation (i very possible could be wrong )
@jaap.roes is part of this forum as well, in case you have questions. Don‘t know if they are willing to respond to queries though. Just figured it‘s good to know.
There‘s a very small difference between a Beat Slice instrument and a Slice instrument.
Beat slice: the slices are assigned to notes. Useful - as the name implies - for beats. So C4 may play Slice 1 while C#4 will play Slice 2
Slice: plays a selected „slice“ chromatically and requires a FX command to target other slices within the instrument.
I think most of the defined attributes/parameters from the Github Repo are still exactly the same, the only difference being that with the Tracker+ they added Stereo sample capabilities which was not possible before.
If you need a video walkthrough of things or screenshots of things, just let me know and i’ll gladly provide them to you.
Thanks for chiming in!
And, yep, you’re 100% correct - i have the .PTI export set up so that it does it sequentially (much like how .pti stereo files are imported sequentially and then mixed together into left-right within the import script in Paketti).
Wait.. so.. in Slice mode, you pick a Slice, and the rest of the slices are silent and the Slice you picked is mapped C-0 to B-9? so then all I’d need to do was provide a slider / midimapping that lets you pick the Slice, right?
Are there Melodic .PTI Slice examples somewhere that demo this? Do the Slices tend to have different loopmodes + looplengths?
Well I’d definitely appreciate some examples of how the Melodic Slice (as opposed to Beat Slice) is done, so I could replicate that, and know that I’m doing the right thing. (Like, I’m just theorizing here, but let’s say there’s a melodic Slice sample with 30 slices inside it, and the 28th slice is selected → i would then write it so that the .pti import would mute the 29 other slices and just have 00-7F velocity on the 28th slice and keymapping mapped across the whole C-0 to B-9 limit).
that’d be a good feature to add into .PTI import, and then of course, .PTI export.
hi @Patrick ! yes, i’m currently trying to figure out if the zoom level can be set to “something sensible”, and if having a loop at the end of a sample will result , with the fixes, in such a situation that the loop End can be changed in Polyend Tracker, and the End-point is shown correctly.
ok looks like i can’t upload an attachment cos i’m a new user. but i’ve sent this file to @Sandroid over Discord, hopefully it’ll now 1) zoom properly 2) end amount + endLoop can be edited
p.s. i also added .RX2 to .PTI direct conversion within Renoise/Paketti - meaning, you can just load a .RX2 and convert it to .PTI and load it into Polyend Tracker.
)
