Forum
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
Sun - Screamtronic
Phrase editor controls to pattern editor
Hi. New guy here, with the first post and feature request: please add the phrase editor Vol/Pan/Dly/FX toggles with accompanying hexadecimal sliders to the pattern editor. As a new guy I’ll be coming to grips for some time with both the various commands and the hexadecimal system. It’s nice that each toggle has its own specific list of commands, and sliders help a LOT with the process of inputting values. And the whole time I can learn and get good enough to just know what to enter. Sound good or am I missing something? Thanks-
1 post - 1 participant
Iterating over selected note columns on multiple tracks
here’s what I have, but I can only get it to modify note columns in Track 1… feel like I’m missing something incredibly obvious. (changing delay value is just a placeholder for now)
edit - … I’ve been sitting there with only Track 1’s delay column visible, lol. classic tunnel vision and then figure out the problem right after you ask for help
edit 2 - oops, meant to post this in Beginners LUA API Sandbox. my bad
local sel_pattern_index = renoise.song().selected_pattern_index local start_track_index = renoise.song().selection_in_pattern['start_track'] local end_track_index = renoise.song().selection_in_pattern['end_track'] for track_index = start_track_index, end_track_index do for pos, note_column in renoise.song().pattern_iterator:note_columns_in_pattern_track(sel_pattern_index, track_index) do if note_column.is_selected then -- do stuff note_column.delay_value = 42 end end endedit - better, I think:
local sel_pattern_index = renoise.song().selected_pattern_index local start_track_index = renoise.song().selection_in_pattern['start_track'] local end_track_index = renoise.song().selection_in_pattern['end_track'] for track_index = start_track_index, end_track_index do local curr_track = renoise.song():track(track_index) if not curr_track.delay_column_visible then curr_track.delay_column_visible = true end for pos, note_column in renoise.song().pattern_iterator:note_columns_in_pattern_track(sel_pattern_index, track_index) do if note_column.is_selected then note_column.delay_value = 42 end end end1 post - 1 participant
[Linux] Understanding the relationship between Carla Windows bridges and Renoise
Hello,
I am having an issue where I can’t get the Windows plugins to work through Carla and Wine on Renoise Linux. I had this thing working alright just a week ago, but I recently updated my system and Wine started crashing when Carla tried to load the Windows plugins. It turned out that I had to downgrade Wine to version 6.2 from 6.3 to somewhat fix things.
However, after the update I can load Windows plugins on the Carla standalone application, but when I load the Carla rack on Renoise, the “Available tools” in the refresh dialog for plugins does not have support for the carla-discovery-win32, carla-discovery-win64, etc. So there’s no way to use the Windows plugins on Renoise. It just feels weird that now the standalone application works properly but the Renoise plugins are missing certain components, I guess.
I am not really understanding from which directory Renoise pulls the Carla plugins, since the only active environment variables are VST_PATH and VST_PATH3 which both point to ~/.vst, and that location only have my native Linux plugins.
Running Manjaro Linux with these packages installed:
carla-bridges-win 2.2.0-1
carla-git 1:2.3.0.RC1.r11.ga08ed288b-1
wine 6.2-1
I have tried other combinations of the available packages for Carla but this seems to be the only one working at all.
1 post - 1 participant
176.4 Khz rendering? ... 44.1 x 4 = 176.4
Midi Control A Single Reason 11 VST Using Separate Renoise Tracks
Hi guys,
Now that 3.3 is out, the Reason 11 vst works just fine inside Renoise.
My question: Is it possible to only use one instance of Reason 11 vst inside Renoise all while using multiple Renoise/midi tracks to control each instrument back inside Reason?
For example, I want to use Europa, Malstrom, and Redrum, which are all inside Reason, but I want to use separate Renoise midi tracks to control each of these instruments. (Think Bass, Lead, and Drums).
Yes, I could open up three instances of Reason inside Renoise each as their own tracks, but it hurts the cpu on my budget laptop. This would be the easiest way to solve the issue, but Reason is a vst that has a bunch of mini vsts inside of it.
…If I could use Reason as a single vst, all while using Renoise to control each instrument inside of it, that would be great!
My issue right now is that I have the vst on one track, I layer a Europa and Kong, and both the synth and drum hit play together. I am trying to figure out where the Midi Out device (on Europa and Kong) routes inside Renoise and how I can use a Renoise track to play only drum hits and the other track the Europa.
Again, It would be so cool to have up to 10 tracks all while there is only one vst present.
2 posts - 2 participants
Pattern Sequencer: Support for Multiple Loop Sections
It would be fun if you could have multiple looping sections defined in the Pattern Sequencer.
Especially for situations where you are jamming with renoise, it would be nice to define several looping pattern sections that you can jump between.
1 post - 1 participant
Hit By A Train By PanosK
Selling Renoise 3.3.1 (updates until 4.3)
Purchased less than a month ago (feb 16th) for 82,28 Euro including VAT. Asking 55 Euro (Paypal).
License is valid until 4.3. I like Renoise as a tracker, however it’s not for me as a DAW. So I’m hoping to sell this and go the VST route with Redux.
1 post - 1 participant
Noir Sad Orchestral theme
Hello ! I have composed a small theme inspired by various chord progressions in a dark and jazzy key. The problem we have when we compose something is that hearing them hardens our ears and we end up getting used to them and we find no faults in them. And that is something painful. I would like you to comment on everything that you find bad or good on this simple topic. I have used as few instruments as possible, I know you can decorate with more horns and add percussion effects, but the strings eat up almost all the space! Comment thanks !!
Ear it using headphones due bass notes.!
1 post - 1 participant
Guitar Rig 5 VST makes scrolling lag
I noticed that whenever i use the Guitar Rig 5 VST i experience that when i scroll down the pattern with the mouse wheel on the track it becomes very laggy. This is even when Guitar Rig says it only uses 3% CPU.
I haven’t noticed this problem with any other plugin, so i assume the problem is with the plugin itself, but i thought i’d mention it just in case.
Has anyone else noticed this issue?
1 post - 1 participant
GUI of Surge VST3 is not updating when I turn the knobs on my midi controller
I want to use Surge Synthesizer (VST3) with a midi controller, but if i turn the knobs of my midi controller the VST GUI does not get updated. However, if I hover my mouse over the controls in the GUI of the VST, it gets re-rendered and the sliders are updated.
I thought this was an issue with the VST, since other VST plugins do not show this behaviour in Renoise, but the folks at Surge Synthesize could not reproduce the issue in other DAW’s, so they thought it could be Renoise-related. GitHub issue: GUI is not updating when I turn the knobs on my midi controller · Issue #4050 · surge-synthesizer/surge · GitHub
Does anyone else have this problem or know what might be causing this? I’m using Renoise Renoise 3.3.1 on Windows 10
1 post - 1 participant