Feed aggregator

Sometimes when I open the instrument plugin menu in renoise (linux 64-bit, on the fluxbox DE if that matters) the menu instantly disappears again as soon as I click it. Restarting renoise fixes the problem but then it randomly seems to happen again. Here’s a video capture: bug

Steps to reproduce

1. Open the instrument plugin insert menu

Expected behavior

Menu stays open

Actual behavior

Menu closes quickly (see video)

1 post - 1 participant

Read full topic

Using Renoise to trigger my Akai S1000. My midi controller is connected to a MOTU midi express 128, then to the Akai.

The Akai is set up with drums on midi channel 1. Bassline is on midi channel 2.

Renoise has track 1 drums, track 2 bassline. I set up 2 midi instruments - both inputs are express 128 port 1, channel 1 (my controller). One output is express 128 port 1, channel 1, assigned track 1 (akai drums) and the other is express 128 port 1, channel 2, assigned track 2 (akai bassline)

I’m trying to “select” either midi instrument to JUST play the drums or the bassline. Tried a bunch of different stuff -

1. Setting up both instruments input to port 1 channel 1 plays both the drums + bassline at the same time
2. Setting one instrument input to channel 1 and the other input to channel 2 just plays channel 1 (akai drums)
3. If both midi instruments must play at once, it seems the only work around is turning off either track in the “track scopes” pane?

What are my options here? Is there an easier way I’m missing to JUST send either channel 1 or 2 into the akai, so it plays drums or bassline separately?

1 post - 1 participant

Read full topic

I’ve gotta say, I love this track! Sort of feels like the chemical brothers doing a more convetional house-style thing. Super simple but, for me, effective!

1 post - 1 participant

Read full topic

I would like to know if anyone is aware of any (if possible, free) software and plugins that can produce experimental textures and sounds. I am on a mac, by the way.

1 post - 1 participant

Read full topic

I’m new to Renoise and coming from Ableton Live. In Live it’s super easy to do parallel processing within a track with what Live calls racks. Is there any equivalent in Renoise or are sends the only way to do parallel processing? E.g. I want to process a sound though two parallel (not series) comb filters with different settings before going on to the next effect. Thanks for your help.

1 post - 1 participant

Read full topic

I know there is a groove tool for Renoise that can’t work right if the LPB isn’t set to 4. Is it the same with the master groove? If my LPB is 12 or 24 will it swing the right beats or will it swing by line?

1 post - 1 participant

Read full topic

If graphical automation is used to change BPM/LPB/TPL in the Master track (Points mode only obv.) then ZTxx/ZLxx/ZKxx effect commands will not function in the same pattern, even if the command and automation point are not on the same line. I assume this isn’t the intended behaviour since no other parameters behave like this?

1 post - 1 participant

Read full topic

I have an Analog Filter in a track and have automated several parameters on it. Various other effects with automation on the track. Automations on other effects are still working but the automation for the filter is not working. The automated parameters are just static when the track plays. The envelopes still appear in the automation screen and the little “this parameter has automation” check box appears next to the automated parameters. Total noob so I’m not sure what could be going on.

1 post - 1 participant

Read full topic

I’m trying to fade in a retriggered hi hat sound and I’ve run into a couple things I don’t understand about the retrigger function. First off, I want the sound to continue retriggering smoothly until the next note is played but the way I have it right now if I choose certain Y values for the Rxy command there’s an audible stutter between lines. E.g. if I use R07 instead of a smooth stream of 7-tick-long repeats, I get 7-tick-long repeats for one line, then a stutter, then 7-tick-long repeats for the next line and so on. I tried typing R07 for the first line and then R00 for the lines afterward because R00 is supposed to repeat the previous command but then it only retriggers for the first line and then there’s silence. I’m wondering if it has to do with the fact that I’m using a very short sound? If I use short enough retrigger values, e.g. R01, I get what sounds like a smooth stream of 1-tick-long repeats but I’m thinking that’s just because the stutters between lines are too small for me to hear them at that rate. In any case, I’m pretty sure I’m doing this wrong and you guys know how to do it right. I can understand that if the LPB is 12, seven doesn’t divide evenly into 12 so there would be inconsistencies between each retrigger beginning on each new line but is there another way to have retriggers of any length that just continue on until the next note regardless of retrigger-length/LPB?

Also, I want to smoothly volume fade in my smooth stream of x-tick-long retriggers. If I just interpolate between 00 and 7F in the volume column I get an audibly stepped fade in (as makes sense). I tried using the Ixx command on the same line as the note but whatever values I enter there’s no audible difference. I tried doing I01 followed by I00 thinking maybe it would repeat adding 1 to the volume each line but that didn’t do anything either. In fact, I can’t seem to get Ixx to work at all. I tried on a longer kick sound to put Ixx of various values on the same line as the note followed by I00 on subsequent lines and I can’t get it to fade in at all. Oxx works as I would expect so I’m not sure what I’m doing wrong / not understanding.

Thank you for your help

1 post - 1 participant

Read full topic

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

Read full topic

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

Read full topic

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

Read full topic

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

Read full topic

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

Read full topic

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

Read full topic

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

Read full topic

Renoise is brilliant! General Discussion Do you have any objective arguments to substantiate your claim? Or anything that actually is interesting for the reader? I don’t think the Renoise team needs such black/white views. In fact, nobody needs this. Also content and context are kings these days. Please stop filling the world with even more zero-content- derailed-pathless-texts. Do you mean that the Renoise team is brilliant? Nice that you want to give them some hugs then… I would agree, too. But I ask here, because this actually soun…

1 post - 1 participant

Read full topic

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

Read full topic

Is this done on purpose? Makes no sense to me?

2 posts - 2 participants

Read full topic

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

Read full topic