Forum
Loading xrnis with phrases... a bit annoying
Forgive me if I’m blind - but I can’t seem to find an option anywhere which lets me turn off phrases/Prg as default, when loading instruments (xrni). When browsing through the instruments, it’s a annoying to hear all those phrases and manually have to set it off each time. But I have a feeling I’m missing something
1 post - 1 participant
It’s here, I can’t believe it’s here
God, I cannot begin to tell you how long I’ve waited for VST3 support, side-chaining, and some of you have probably seen some of my posts. The hours spent EQ’ing and compressing, weird partial workarounds with DDMF or other tools, trying desperately hours after hours after hours trying to rip the mud out of some deeply amazing piece.
And tonight, after an OS refresh and finally getting through installs, weeks after stumbling across news of this update and nearly having a heart-attack … spending an hour throwing a quick base together, drums side-chained into sub-base, side-chained into a grungy bassline, trailed by wandering chord strikes, and everything just so … bloody clear.
I want to say thank you, and thank you is deserved for this work, after years and years and years of begging pleading for this attention, I’m finding a stalemate of balance in this.
But it’s like … I can breathe. It’s all here. It’s all right here.
1 post - 1 participant
Reference MIXs for you?
Have you some reference MIXs?
mines are for example:
. Audio-Control freak
. Cossfire-Hydra
. Dom & Roland-Parallax
1 post - 1 participant
Renoise Use Counter
Hey there. When you download the demo version of Renoise, you are reminded every couple of hours to register your copy, and you are provided a count of how many hours you have used Renoise for. Does Renoise count your hourly usage, even after you’ve registered your copy? If so, how would one find out what the count is?
(Here is one of my screenshots from before I had purchased Renoise showing what I’m talking about.)
1 post - 1 participant
Time problem with renoise.tool():add_timer(func,time)
R3.3.1 Win10 x64
I am experiencing precision issues with the timer to run a function repeatedly. When using:
renoise.tool():add_timer(func,time)
I can’t get the timer to run below 60-62 ms. This could be used to create a repeat button, for example to shift the position of the line up or down.
The problem is that the timer seems to run very slow with a value in milliseconds below 60-70 ms.
For example, if you put 1000ms (1s), the timer will work practically perfect:
renoise.tool():add_timer(func,1000)
Up to about 70-80 ms it seems to work fine:
renoise.tool():add_timer(func,70)
But if you use a value lower than 60 ms, the timer will keep running something above 60 ms always. I get the feeling that in previous versions of Renoise (v3.0 …), the timer could run at 10 and even 5 ms with a small margin of error.
Is it possible that add_timer now has a minimum limitation above 50 ms? We need a timer to work ultra-fast, which can reach up to 1ms speed. For example:
renoise.tool():add_timer(func,20)
renoise.tool():add_timer(func,15)
renoise.tool():add_timer(func,10)
renoise.tool():add_timer(func,5)
I have been experimenting with this code that I have purposely written to test it:
local C=0 local T=0 local function bang() local NC=os.clock() T=T+1 --print("T:",T,"clock:",("%d"):format((NC-C)*1000),"ms") vws.TIME_TEXT.text=("T: %s | clock: %d ms"):format(T,(NC-C)*1000) C=os.clock() end local function bang_timer() if not renoise.tool():has_timer(bang) then renoise.tool():add_timer(bang,vws.TIME_VALUEBOX.value) else renoise.tool():remove_timer(bang) vws.TIME_TEXT.text="" C=0 T=0 end end --viewbuilder local function gwt_frame() local FRAME=vb:row{ vb:valuebox{ id="TIME_VALUEBOX", height=19, width=79, min=1, max=5000, value=1000, tostring=function(value) return ("%d ms"):format(value) end, tonumber=function(value) return tonumber(value) end, }, vb:button{ height=19, width=99, text="Timer Test On/Off", notifier=function() C=os.clock() bang_timer() end }, vb:text{ id="TIME_TEXT", width=140, text="" } } return FRAME endIt is even possible to notice that something is wrong simply by simply printing on the terminal.
Can anyone try this? If we cannot comfortably set a value between 10 and 100 ms, the timer is useless in many cases.
@taktik, can you review this matter in depth? Personally I use various tools with add_timer () remove_timer () and i’m experimenting serious slowness problems below 100 ms.
1 post - 1 participant
Renoise 3.3 uses the wrong full screen on macos
Renoise 3.3 still uses the wrong full screen mode on macos, where instead of being a new full screen “virtual destop” like everything else (respecting control+left/right etc), it does something custom, which it shouldn’t be doing.
2 posts - 2 participants
It be Swell Though
Had an experiment with swells, then I got side tracked and made this thing!
Enjoy!
Editing MIDI curves across two segments is a painful experience, or am I doing it wrong?
1 post - 1 participant
Help wanted: unreported missing VST (steam engine)
hi,
i loaded an old song, from before my reinstall to new win10.
when loading, renoise 3.1.1 dont just report what vst is missing, it asks me to point to steam.
i dont know which vst use the steam engine, and clearly its not installed.
instead of then just loading the song with missing plugins, it crashes.
i need to know what vst is missing, in order to get my song working… ?
4 posts - 2 participants
List "registered" VST,VSTi?
I look at the API reference,and it seem not possible to create a list from all registered Renoise instruments and effects…
I’am wrong?
1 post - 1 participant
The Reaper thread
I didn’t use it since a few years, tried it again yesterday.
Really impressed, I’m currently trying to make a jungle tune in it.
The audio editing is smooth and the interface is really reactive (compared to bitwig…)
makes chopping breaks in audio an almost pleasureful experience.
The things that are missing compared to other daws :
-
No “lfo tool” or modulators. I think this is not such of a loss, since there is the lfo automation generator thing. Automation is really well done, you can do automation clips and move them around under your media items. not bad
-
No straightforward midi drum machine thing. If you want to control samples by midi, you have to stack instances of the internal sampler and set manually the note for each instance … annoying.
-
No integrated slicing. We lose some of the renoise workflow here. No way to quickly try slicing something to see if it sounds good.
-
No cool way to do parallel processing. You really have to setup send busses for this kind of things… annoying. Bitwig is clearly the winner there (and Renoise in the sampler).
There is also a cool feature, you can apply effects to “clips”. This is similar to the sampler effect chains in renoise.
In a way those limitations are OK. This makes me more focus about making a track and less about endless sound design sessions like in Bitwig. Compared to Renoise it’s cool to see the waveforms of the breaks you are slicing. I will see what I will come up with it…
4 posts - 3 participants
Play from actual Pattern position?
Hi Renoise folks
Is there a function to play from actual editing position in pattern? Always when i press play Button he start Playing from position 0 of pattern not from actual editing position. thats broke my Workflow.
happy tracking
3 posts - 2 participants
Tools login broken?
Cant login anymore, password request dont work
Edit: Nevermind, email was in spam folder. But i’m not sure, why the password wasn’t working anymore…
Edit 2: I’ve set a new password and now my login is blocked. It seems login form is broken?!
1 post - 1 participant
Another lockdown 'song'
Hello all Renoise friends - I’ve been developing this new tune on-and-off over the last couple of months. I went back to it today and made some changes…this is the first time I’m posting it. Let me know your thoughts / suggestions. Cheers for your ears…
2 posts - 2 participants
Serum, PhasePland and Vital presets
Free pack of my own presets.
Description on YouTube.
Link: 288 FREE PRESETS - Serum, Phase Plant, Vital - YouTube
1 post - 1 participant
GUI Load Failure After Installing ASIO
Hello,
I was trying to get my guitar to input into Renoise using ASIO4ALL.
I did the following steps:
I set ASIO as my sound driver in the Renoise settings and it didn’t work.
I closed Renoise.
I installed ASIO4ALL.
I reopened Renoise.
I see these two dialog boxes:
CrashBackup here:
Untitled_3_14_2021__23_45_crash.xrns (3.5 KB)
I cannot open Renoise anymore without getting blocked by these dialog boxes. Please advise if I have to reinstall or if theres an easier way to revert the settings!
1 post - 1 participant
Linux: plugin ui broken (due to scaling) for some (most) plugins
On Linux (NixOS), KDE Plasma with scaling enabled, most VST plugins don’t render UI correctly when opened in Renoise.
For example TAL-NoiseMaker - free download but also many other plugins have problem rendering. It seems that UI is scaled but plugins which have fixed dimensions in UI won’t increase are cropped at their 1:1 scale size.
- on the left NoiseMaker opened via Renoise
- on the right NoiseMaker opened via Carla
Note that actual rendered area is of same size in both case but UI from renoise is cropped because it’s scaled:
Steps to Reproduce:- install plugin that doesn’t support UI resizing like NoiseMaker
- setup scaling in desktop (tested in KDE Plasma)
- open VST plugin via renoise
This is unclear frankly. Ideally the UI would be scaled but not cropped (it would fit the whole window). But I assume the dimensions are probably hard-coded on plugin side so it’s the plugin which cases the problem.
Realistically speaking I think the only feasible solution would be to force scaling in VST plugin windows to 100% as Carla does.
ActualUI is not fully usable because it’s cropped.
1 post - 1 participant
New Tool (3.3): Drawtomator
Wouldn’t it be nice to just draw something and that would drive some musical changes? The Drawtomator allows you to do this by assigning effect parameters to the X and Y axis of your drawing. However, this is more a proof of concept than a reliable automation device.
Time-wise, a recording won’t be an exact match for what you’ve drawn. Likewise, the timing of the replay can be variable as it’s playing back. This is because timers are used to record the drawing and replay it, but due to the nature of the API these are not accurate down at the level of milliseconds. They are at the mercy of what’s happening with the GUI – mouse movement in particular.
This variability is especially noticeable at lower interval settings. Raising the interval time helps a lot with this, but also makes the recording or playback more coarse, since there’s more time between updates. Although a low recording interval is less accurate it does record more information, which is beneficial when replaying at slower speeds.
When you’ve finished drawing and released the mouse button, this is detected by the snapback feature of the XY Pad. This means it’s possible to accidentally cancel the drawing by going to the Finish Corner. If you need to use the values of a corner in your drawing then you can change the snapback point to another with the Finish Corner option.
The Drawing Colour option lets you choose from three different colours available from the Theme that’s being used. Useful since some can be hard to see, or if you just like the change in colour.
2 posts - 2 participants
[Bug Api GUI] switch: midi_mapping marker only marks 2 items
Renoise 3.3.1, W10 x64
It seems I have a little GUI visual problem with the switch in a windowed tool.
To reproduce what happens:
- Create a window tool with a swith, for example include this swith:
- Select Renoise window and Press CTRL + M. The switch object must be fully marked. However, it will only mark the first 2 items:
I think this does not happen with the Renoise window. So it’s probably an API problem, with the window tools and the switch object.
1 post - 1 participant
Sun - Passage (the)
that’s the fastest BPM i did so far.
Nexus, Rmx, Omnisphere, Spire.
hope you’ll enjoy.
i think it’s one of my favorite but i might be biased.
1 post - 1 participant