am happy to say that CTRL-O - the age-old Schism Tracker hidden feature (PTN2SMP so pattern to sample) has been re-created into Paketti.
What it does it it does nothing to Mute / Solo states, and just renders the whole everything into a single sample, non-destructively (CTRL-O used to overwrite the sample-in-question in Schism Tracker so good luck with that).
this also means you can trigger it from a menu, or from a midi mapping.
I remember when Paketti was a collection of a few handy shortcuts and now this 
Paketti - or, Tracker Convergence Project ™ provides over 5000 shortcuts, 3000+ menu entries, 1000+ midi mappings and 70+ dialogs.
Some incredible work going into these long term tools on this forum!
So much to explore.
Is there anything like this? Tracker Commands - #8 by darnellisatwork
i’ve written a hacky SBx if you mean the “pattern effect loop”. it can be experimented with in paketti. give it a shot - needs to be enabled, though.
ok here’s a little demo of groovebox8120 use, a bunch of other features in paketti. and this time i use keycastr and talk too so dunno if the levels are alright but hey
EDIT: ok i got the info needed to, for next video, set up OBS so that the Renoise audio ducks when i talk. next stream.
This demonstration is like .02% of Paketti 
Great demo of the groovebox8120. At around 23:20 those sounds were wicked
+1 for Presets++
yep @elcasiino - that’s why i only said it was a little demo of the Paketti Groovebox 8120
which is a 8 part, 120 sample each “part” stepsequencer. but the hooks to automation, the 8 macro knobs that each Paketti-loaded instrument come in with, the “Selected Instrument Macro1-8” midi mappings (dynamic) etc allow for some fun possibilities.
in fact, the Akai MidiMIX setup for this (i got a few donations mid-2024 so was able to buy it) - has been built to do the Synthcamp demo, so that’s where the 8 knobs for pitch control for instance come from.
i just thought to also demo the repeaters, the shortcuts for loading a device quickly to any track dsp slot or sample fx chain, and a few other things. what i think i should do, is also add the Paketti Stepper controls to this gui, it could be a lot of fun.
anyway, then i got sidetracked to talking about preset++ which i still need to wrap up, but i’ve been busy doing a finished dialog + video for a specific company, and it’s summer vacation (daycare closed) so things aren’t going quite as fast as i’d like.
Improvement: Added CCizer feature to Load Plugins - therefore you can load a Plugin AND a CC Instr Device Control with one shortcut + midi mapping.
usecase:
So, here’s yet another “oh i applied ducking compressor but it still didn’t solve it, gotta find the sweetspot” audio recording video of demoing Paketti
this time i’m talking about
let’s hope 3rd time’s the charm and i get the audio ducking properly.
cool, trying out the wavetable transformer stuff as shown in the video, I get;
"‘C:\Users\pluge\AppData\Roaming\Renoise\V3.5.2\Scripts\Tools\org.lackluster.Paketti.xrnx\main.lua’ failed in one of its notifiers.
The notifier will be disabled to prevent further errors.
Please contact the author (lackluster | esaruoho@icloud.com) for assistance…
std::logic_error: ‘ViewBuilder: invalid value for rotary encoder: ‘1’. value must be [1 - 0].’
stack traceback:
[C]: at 0x0140ba5ce4
[C]: in function ‘__newindex’
.\PakettiWTImport.lua:876: in function ‘update_wavetable_dialog_simple’
.\PakettiWTImport.lua:815: in function <.\PakettiWTImport.lua:806>"
when having the ‘paketti wavetable’ control dial open and moving to a new, empty instrument in the renoise instrument selector list.
Also question, instead of the wavetable dial set up that is needed now to move between the generated wavetables, have you thought about using a stepper hooked up to a macro, so you can control which sample from the instrument is played though the macro instead?
Here’s an example .xrni to move between samples in an instrument in case you don’t know (move around the voice swapper macro to go through the 6 samples in the instrument);
diffy2.xrni (77.0 KB)
ohh what a rookie mistake. thanks for the paste and the description - i’ve fixed it.
thanks for the xrni, i’ll have a look at that too, hopefully tomorrow during naptime.
forget about that instrument, I don’t think you can move around >16 samples max?
Wow, so many interesting and useful features in one tool! Guess I was wrong about the slowdowns, seems to work nicely in Renoise. Very nice to explore your ideas, thanks for sharing.
hi @ffx Thanks for your nice words! I really appreciate them.
Yes, I’ve been doing a lot of thinking, dogfooding, rubberducking, live sets / jam sessions, video recording etc and a lot of the time this “use the tool” approach tends to result in even more integration and more “oh, but this should work like this… and when here, it should work like this” type workflow / usecase improvements.
which is why i do 1-on-1 calls with people, and now that i’ve taken to doing streams, it also helps to think out loud about what’s going on and explain things and see “oh, but this could be streamlined even further”.
as always, the newest version is on my github. if there’s eventually some way of ingesting the github post to the tool, i’ll then do that too (i.e. fast/automatic instead of slow/manual), but for now the tool version will always drag behind by a few days or a week…
anyway, plenty more incoming.
Hi @Jonas - i today found 3 ways to crash Renoise using Paketti. eventually figured out the issues (Single Cycle Waveform Writer, Unison Generator and Phrase Generator) - and fixed them. so in theory you should now be able to click around like a total madlad and still be able to not reach the crash state.
Hi @Ghost_Train - i’ve been meaning to get around to doing render-effects-to-sample including selected track trackdsp things, and samplefxchain things and macro things, for about 1,5 years now.
after describing how it should work to you over discord, i ended up writing it, finally.
here’s some results:
this is the original sample above, with massive cutoff + resonance + drive + parallel compression and LFO Amp + LFO Freq on the cutoff, and static pitchbend to make sure it plays at a low speed.
what results is this:
and if i chop the silence out:
i could make a version that always removes the silence out from the end of the sample, but for now i guess this demonstrates that this part of “long-form todo-list in Paketti” is finally done. it’s a singular shortcut that does it, pretty transparently. i won’t bore you with the details of what it does, but one thing that’s important is this:
it sets the track headroom to 0.0dB and then returns back to the original track headroom.
(related thread
)
p.s. i think the first request i received for “processed sample / effected sample to new sample, with tails” was from @tkna around april-may 2024 so glad to finally have been working at it and looking into it. - i think the original request was placed when i implemented the Paketti Default Instrument with cutoff + resonance - the idea was: "this sample, via these macro effects, to a new sample, and i thought, geez, this is gonna be hard. well, it took a lot of thinking about how to do it, and how to solve the situation with long samples, etc, but at least this is a minimum viable product / prototype now.
shout out to @slujr 's Wavetable tutorial video - i took one little part of it and wrote it into the Single Cycle Waveform Writer:
Improvement: Single Cycle Waveform Writer
You can now use Single Cycle Waveform Writer to create “a type of wavetable” - The newly added “Write A&B” button will create Wave A as Sample Slot 1, Wave B as Sample Slot 2. The Wave A will be in Sample FX Chain 1, the Wave B will be in Sample FX Chain 2. The FX Chain 1 will have a LFO connected to Gainer, and the FX Chain 2 will also have a LFO connected to a Gainer. After the Gainer, for both FX Chains, there will be a Send device to FX Chain 3 - which is the “regular” Paketti FX Chain (followed by FX Chain 4 for Parallel Compression). After this, the Live Pickup Mode is enabled in the Single Cycle Waveform Writer - but with additional tweaks: Now, after this change, the Wave A Waveform drawing will write to Sample Slot 1, and Wave B Waveform drawing will write to Sample Slot 2. The Instrument is configured like so: The Modwheel controls the Reset of both LFO devices in Sample Chain 1 & Sample Chain 2. Both LFOs are set to “Infinite” Frequency - meaning, only the Modwheel will change the location of the LFO step. The Selected Track also gets a LFO, connected to Instr. Macro device’s Modwheel. The Selected Track LFO Amplitude, Offset&Frequency, are exposed in the Mixer for easier availability, and the Dialog is automatically updated with three additional sliders - you guessed it, Amplitude, Offset and Frequency. This means that you can automate the LFO on the Selected Track - the device is helpfully renamed to Wavetable Mod *LFO , and thusly you can automate the crossfade / oscillation between the Wave A and Wave B waveforms. When dialog opens on an Instrument like this - the Live Pickup Mode is automatically set & the Three sliders on the Dialog are shown to the User. Additional bonus: Since you now have a FX Chain for Wave A, and a FX Chain for Wave B, the Wave A/Chain1 and Wave B/Chain2 can have effects loaded in&there will be automatable crossfading between the actual Chain output (such as effects) of the Waves.
here’s a Sectionizer.
yep. it lets you create sections. with number of pattern. and the pattern rows. and the counting naming.
Experimental EQ30 hack
Ok this is an interesting experiment and really needed to be made.
I’m a big fan of the age-old, 32-bit only, never-made-available for macOS, DiscoDSP EQ30. You can just draw with a mouse and get a bunch of sliders moved around.
Hold the left mouse button down and paint → a max of 30 EQ Bands are within your grasp with a single click + drag.
So here’s a Renoise v3.5 only hack for making it happen, using 4 EQ10’s.
If you have any ideas, do let me know. If you can think of other Renoise Native devices I could tweak and hack like this, do let me know, too.
