Forum
Labeled Keyboard
I dunno if anyone already posted this but could there be an option to have the keyboard keys labeled; I’m sure at some point it’ll be second nature of what the keys are but at this time I’m stupid please help.
1 post - 1 participant
Low level Win10 tablet
Hi All
Briefly, I have a low-grade Win10 tablet and was wondering which old school version of Renoise would be best
It’s an Intel Atom Z3735g 1.3mHz with 1Gb ram
I only want to use samples and no VSTs for some on-the-bus ideas sketching
I’m sure that some Windows ‘tweaking’ would also be necessary too
Any ideas would be very much appreciated
Many thanks
1 post - 1 participant
Keybinds to move the edit position up/down by LPB
I have little experience with lua, and the documentation requires knowledge I don’t have atm… I got as far as adding keybindings. I had trouble getting the current edit position and adding/subtracting LPB from that, then setting the new edit position… basically everything that’s actually needed lol
Anyhow I’d like a tool that adds two keybindings that move the edit position up and down by lines per beat (to replace the default, rather inflexible “jump 16 lines up/down” keybindings). Any assistance with either learning resources or the actual code/tool would be appreciated.
1 post - 1 participant
New Album - Shitpost Futurist by _sink, made w/ Renoise 3.3 for Linux
Hi all. I’ve been a loyal renoise user for the past 3 years and have another album out. Everything I’ve publicly released (besides a few tracks on botb shhh) are in renoise. I love this DAW so much.
This record is different from my last few, it draws a lot in terms of tone and mood from early vaporwave and it’s sound palette is close to early 00s IDM, particularly ae this time around. I also commissioned a music video/performance to go along with it and it’s super cool and I hope you enjoy it. It’s a spooky, weird cynical thing.
1 post - 1 participant
Random Tools Appear on Startup
I’ve noticed whenever I open Renoise a random tool’s window always pops up over the default splash screen without me doing anything.
Seems to be random, now it’s Noodletrap sometimes it’s SliceMate. It’s not always the last tool I installed or anything like that.
1 post - 1 participant
Building tool to batch convert MIDI to XRNS
Hi,
I’m looking to convert a bunch of MIDI files to XRNS. Unfortunately, while this is possible by clicking on a MIDI file and explicitly opening it with renoise, the lua scripting doesn’t seem to include MIDI as a filetype that it can load. Any tips on using LUA to convert a MIDI file with multiple tracks to XRNS? I’m not worried about the lack of samples in the MIDI file, as I can add xrni’s post-hoc, but I just want the same output you get when you manually click on a MIDI and open it in Renoise.
1 post - 1 participant
Observable to detect tool window in foreground or background?
To build a window tool, it is sometimes necessary to know if the tool window is in the foreground or in the background, being able to toggle between the main Renoise window and the tool window with an observable or notifier.
Is there an observable that detects the change of state of the tool window, in the background or in the foreground?
In the following documentation there are “similar” observables, but not the foreground and background state of the tool. I’m missing something?
Renoise.ScriptingTool.API.lua -- Invoked when the tool finished loading/initializing and no errors happened. When -- the tool has preferences, they are loaded here as well when the notification fires, -- but 'renoise.song()' may not yet be available. -- See also 'renoise.tool().app_new_document_observable'. renoise.tool().tool_finished_loading_observable -> [renoise.Document.Observable object] -- Invoked right before a tool gets unloaded: either because it got disabled, reloaded -- or the application exists. You can cleanup resources or connections to other devices -- here if necessary. renoise.tool().tool_will_unload_observable -> [renoise.Document.Observable object] -- Invoked as soon as the application becomes the foreground window. -- For example, when you ATL-TAB to it, or activate it with the mouse -- from another app to Renoise. renoise.tool().app_became_active_observable -> [renoise.Document.Observable object] -- Invoked as soon as the application looses focus and another app -- becomes the foreground window. renoise.tool().app_resigned_active_observable -> [renoise.Document.Observable object] -- Invoked periodically in the background, more often when the work load -- is low, less often when Renoise's work load is high. -- The exact interval is undefined and can not be relied on, but will be -- around 10 times per sec. -- You can do stuff in the background without blocking the application here. -- Be gentle and don't do CPU heavy stuff please! renoise.tool().app_idle_observable -> [renoise.Document.Observable object] -- Invoked each time before a new document gets created or loaded: this is the -- last time renoise.song() still points to the old song before a new one arrives. -- You can explicitly release notifiers to the old document here, or do your own -- housekeeping. Also called right before the application exits. renoise.tool().app_release_document_observable -> [renoise.Document.Observable object] -- Invoked each time a new document (song) is created or loaded. In other words: -- each time the result of renoise.song() is changed. Also called when the script -- gets reloaded (only happens with the auto_reload debugging tools), in order -- to connect the new script instance to the already running document. renoise.tool().app_new_document_observable -> [renoise.Document.Observable object] -- invoked each time the app's document (song) is successfully saved. -- renoise.song().file_name will point to the filename that it was saved to. renoise.tool().app_saved_document_observable -> [renoise.Document.Observable object]This would be especially useful when using modifier key commands, so that the tool could change the state of these key commands depending on the state of the tool window, whether it is in the foreground or in the background.
Any trick to do this?
The specific scenario I am looking for is the following:
The window tool could detect when it is in the background. In this case you could deactivate certain features and reactivate them when the window is back in the foreground, especially useful for controlling the state of keyboard commands, preventing certain commands from remaining pressed when the window tool changes state to the background.
The point is to be able to switch between the Renoise window and the tool window and to be able to detect it to trigger a function.
1 post - 1 participant
Someone don't like your post
1 post - 1 participant
How do I fix this audio error?
For some reason I randomly started getting this error when using DirectSound. I need to use direct sound so I can hear youtube videos. Someone know a way to fix this? Couldn’t seem to find anything relevant online
1 post - 1 participant
MacOS Dock is Visible when Switching to Fullscreen Renoise
Renoise for MacOS is showing the Dock when in full screen and switched to from another app or space to varying degrees depending on circumstances.
This is an issue I’ve previously reported in lesser detail and subsequently closed, but it seems to still be present in the current release and appears to derive from the full screen mode having been implemented in a non-standard way.
Symptoms:
The Dock is either displayed permanently on top of Renoise, obstructing everything including controls underneath, or temporarily, sliding away immediately after switching to full screen Renoise.
Common for all circumstances is that showing the Dock violates the expected behavior of full screen MacOS apps which is to not display the Dock in full screen, except when summoned by pulling the cursor below the screen continuously for a period of time.
It’s been difficult to find a pattern determining whether the Dock is displayed permanently or temporarily, but CMD+TAB (the approximate MacOS equivalent of ALT+TAB in Windows) always leaves the Dock permanently displayed on top of Renoise.
Using the three-fingered slide gesture, CTRL+LEFT/RIGHT, Mission Control, or holding down CMD+TAB and selecting Renoise from the menu all seem to depend on circumstances in whether or not they display the Dock permanently or temporarily.
Additionally, accessing an open non-full screen app will draw the app and the Dock on top of Renoise, not on top of the Desktop and all other open (non-full screen) apps as expected.
Speculation:
Mission Control labels the Renoise space as Desktop. This, combined with the behavior surrounding non-fullscreen apps described above, seems to indicate that Renoise is not assigned its own space when put into full screen mode, but instead drawn in the default desktop space (Desktop) and ineffectively suppressing the Dock and other open apps.
Details:
The issue has been observed in Renoise 3.3.2, but has likely been present going back to version 3.3.0 or earlier. I’m running MacOS Catalina 10.15.7 on a MacBook Pro.
Also, the conventional keyboard shortcut to enter full screen mode in MacOS is CTRL+CMD+F, in case that’s of any value.
1 post - 1 participant
Electronic - Boom
Hello Renoisers,
This is my last track, a mix with hard sounds and 8bit melodic, in 80’s style.
VST : Spire and Synthmaster
VST Drums : Lethal and Battery4
and few samples…
Good listening !
1 post - 1 participant
New Tool (3.3): Keep Selected Pattern Looping
Simple menu entry that will keep the currently selected pattern in the sequencer looping. It updates automatically as you navigate patterns
ledger.scripts.KeepSelectedPatternLooping_V1.1.xrnx
Original Thread: Made as can be useful with some MIDI controller navigation.
1 post - 1 participant
Redux multiple phrase midi triggering
Last time I tried, it wasn’t possible to freely trigger multiple phrases in Redux simultaneously. Phrases are selected with CC, so if you want to play a chord with separate phrases from the sequencer you can’t (AFAIK).
If possible, I suggest making this possible by using MPE. Maybe that seems a bit hacky, but it seems better than not being able.
1 post - 1 participant
[Linux/Wine] Phoscyon + Carla + Instrument Automation = Distortion
Hello,
I am facing this weird issue on my laptop where if I try to automate values with Instrument Automation Device on Carla Rack + Phoscyon VST, the sound gets very distorted and glitchy. If I move the parameter knob on the Instrument Automation Device manually with a mouse, everything sounds fine. Only when Instrument Automation Device knobs get hooked to some other Renoise automation device such as LFO or Automation Edtior, the sound gets ugly instantly.
Any tips what might be causing this behavior?
1 post - 1 participant
Sample focus - free samples
Hey dudes, some of you will really like this.
samplefocus.com Sample Focus | The Easiest Way to Find Free Audio Samples1 post - 1 participant
Renoise is brilliant!
Over the years I’ve tried so many different digital audio workstations and for my experience is that what I like the most is Renoise and Reaper. They work together so well. Renoise and Reaper are best digital audio workstations (my opinion) to make music and noise.
1 post - 1 participant
Midi Script available?
I use behringer Cmd mm1 and it’s connected as well . But I want to know is there any midi Script driver for it or not?
1 post - 1 participant
Daisy (my new song)
Lofi hip hop beat, this time less sleepy/chill and more energetic/groovy. Features a neo-soul[ish] guitar as its main element (played by myself) Hope u guys like it!
On YT: Daisy - YouTube
On Spotify: Spotify
1 post - 1 participant
Discop Selection Loses Selected Song When Expanded + Resaved
-Have an XRNS expanded in the discop to browse internal samples
-Save that song with one of the samples still selected
This causes the XRNS to collapse which makes sense as sample data may change. However the selected song may now change: If you were browsing a sample 3 slots down, the selection becomes the song 3 slots down.
You would expect the selection to default to the song you were browsing (just as when you collapse the XRNS manually)
1 post - 1 participant