Ey @Raul am I right that Samrender doesn’t automatically detect the line range I set in the pattern editor through mouse dragging a selection and have to manually set the ’ Lines Range To Render’ in the tool gui? Or am I doing something wrong?
If not possible, could you please implement it? Would be much quicker workflow especially when using the keyboard shortcut for Samrender, have it work similar to Renoise native render to sample.
I’d like to use the tool for rendering pattern selections and use your ‘autocapture the track name to rename the sample’ as this is a feature I’m missing with Renoise native render to sample!
If you often render bits to sample from the pattern editor, everything is named “Rendered sample XX”, doesn’t give a hint to whats inside. A track name can be helpful *(also instrument names from the sounds that are inside the selection, perhaps an other option to take into consideration?). Here lies a possible problem though, what if the pattern selection spans multiple tracks inside a pattern, how would you name the newly created render?
Simply put each track name one after another until you reach the maximum amount of characters the instrument list accepts as a valid name?
I wouldn’t mind fetching only the first, most left, track name if selection is >1 track in a pattern.
This is such a great tool. I use it every day.
I found a small bug, that occurs whenever I try to call SamRender by its keyboard shortcut (I set it to alt+r) for the first time
After I open it once via menu entry it doesn’t happen again.
@weizenkeim Oh, wow! It must be some silly mistake of mine when updating the GUI. I will review it and release a new version with the fix as soon as possible. In fact I believed that this matter was resolved, because this error is familiar to me when programming this latest version.
Thank you very much for reporting the error! This helps a lot to make the tools stable.
Great. Thanks for working on this tool. It’s awesome. But I said that already. The bug was in the last versions too btw. I just didn’t care to report, because it seemed such a minor issue.
Yes, it is a minor (absurd) problem that has to do with updating a global variable in the first GUI load. Programming stuff. It doesn’t even have to do with the operation of the tool’s operations (which is much more serious). I’ll solve it …
Future feature suggestion for when rendering a song ;
some kind of high quality toggle that temporarily switches all samples oversampling options on in Renoise during render. You know, the anti aliasing toggle next to interpolation in the sample properties? Also turning on Sinc interpolation setting for every sample and when using the native filter devices, switch to the highest oversampling option. Curious how this would sound A/B’ing mixes
Forcing the change in all samples of all instruments of these two configurations previously and restoring them later is possible. Activate the switch “AA” and change interpolation to “Sinc”
What do you mean exactly? What configuration should I change?
For example check out the native analog or digital filter dsp device, there’s an oversampling option above the graph default at 2x, this can be set to 8x at maximum through the dropdown menu. Not sure if there are more native devices which have oversampling options?
no worries, it’s just an idea! Btw to be clear I don’t mean that these filter devices should be processed on all samples, just that the oversampling would be set highest for those devices actually used in a song.
I am pleased to announce the release of version 2.0.015 of the SamRender free tool. This new version is maintenance, improvement and include new features. It is a major version…
All new features are listed in the Update History (first comment on this thread).
This new version 1.2 of the SMR brings updated code for the latest version of Renoise (API v6.1). It brings some improvements and a new tool information panel.
Hi @Raul . Firstly, thank you for creating this great tool! The Accumulate option in particular is very handy for saving time in doing a lot of rendering. However, I noticed a few of the built-in keybindings are not working for me, at least on macOS 14.2.1 (Renoise 3.4.3, tool version 2.0.015).
Error when using shift + r to close the tool window:
smr/lua/keyhandler.lua:80: variable 'RND_MAIN_DIALOG' is not declared
stack traceback:
[C]: in function '_error'
[string "local mt = getmetatable(_G)..."]:29: in function <[string "local mt = getmetatable(_G)..."]:24>
smr/lua/keyhandler.lua:80: in function <smr/lua/keyhandler.lua:78>
Error when using left or right to select Track:
smr/lua/keyhandler.lua:24: variable 'rna' is not declared
stack traceback:
[C]: in function '_error'
[string "local mt = getmetatable(_G)..."]:29: in function <[string "local mt = getmetatable(_G)..."]:24>
smr/lua/keyhandler.lua:24: in function 'smr_kh_nav_tracks'
smr/lua/keyhandler.lua:87: in function <smr/lua/keyhandler.lua:78>
Error when using up or down to select Sequence:
smr/lua/keyhandler.lua:44: variable 'rna' is not declared
stack traceback:
[C]: in function '_error'
[string "local mt = getmetatable(_G)..."]:29: in function <[string "local mt = getmetatable(_G)..."]:24>
smr/lua/keyhandler.lua:44: in function 'smr_kh_nav_sequence'
smr/lua/keyhandler.lua:88: in function <smr/lua/keyhandler.lua:78>
+ or - also don’t seem to trigger any changes when attempting to select Instrument. The rest of the keybindings are working fine for me.
Of these, the binding to close the tool window is what would be most greatly appreciated to fix (if/when you have time). I would be happy to fix these myself, although I noticed the tool is using compiled Lua
Hi @tactilepro thanks you to report about these errors. In the next version all of them will be resolved! Actually, they all come from the same error, a specific reference that I overlooked.
I’m glad you like the tool. Have you also tried ModFXRender tool?
Thanks for the quick response and that’s great to hear! I look forward to the next release. For now at least I’ve found a pleasant workflow setting up my basic config on the first sample, then just use a combination of the Direct Rendering option then renaming my samples afterward using the command_palette tool.
I’ve played around with ModFXRender superficially but I very much want to dive into this more as time allows. I’m also quite interested in some of your other tools, particularly the Travel Through Phrases one. I will likely be in touch soon regarding getting a license for this one in the near future. Thanks for all your work on these!
I have a request Raul,could you please change the default position of ‘overwrite’ to ‘new instrument’ because it’s set to overwrite as default I have overwritten lots of files accidentally and I can’t undo the action to retrieve the overwritten file.That small change I feel would make a big difference,at least to me anyways
