local rns_version = renoise.RENOISE_VERSION
KNG_CLR = { MARKER = {235,235,235} }
-------------------------------------------------------------------------------------------------
--capture the native color of marker (for Windows: C:\Users\USER_NAME\AppData\Roaming\Renoise\V3.1.1\Config.xml)
function kng_capture_clr_mrk()
--print ( os.currentdir() )
--Config.xml path:
--Windows: %appdata%\Renoise\V3.1.1\Config.xml
--MacOS: ~/Library/Logs/, ~/Library/Preferences/Renoise/V3.1.1/Config.xml
--Linux: ~/.renoise/V3.1.1/Config.xml
local filename = ""
if ( os.platform() == "WINDOWS" ) then
filename = ("%s\\Renoise\\V%s\\Config.xml"):format( os.getenv("APPDATA"), rns_version )
--print("Windows:", filename )
elseif ( os.platform() == "MACINTOSH" ) then
filename = ("%s/Library/Preferences/Renoise/V%s/Config.xml"):format( os.getenv("HOME"), rns_version )
--print("MacOS:", filename )
elseif ( os.platform() == "LINUX" ) then
filename = ( "%s/.renoise/V%s/Config.xml"):format( os.getenv("HOME"), rns_version )
--print("Linux:", filename )
end
--print( filename )
--RenoisePrefs
--SkinColors
--Selected_Button_Back
if ( io.exists( filename ) ) then
local pref_data = renoise.Document.create("RenoisePrefs") { SkinColors = { Selected_Button_Back = "" } }
pref_data:load_from( filename )
--print( pref_data.SkinColors.Selected_Button_Back )
local rgb = tostring(pref_data.SkinColors.Selected_Button_Back)
local one, two, thr = rgb:match( "([^,]+),([^,]+),([^,]+)" )
KNG_CLR.MARKER[1] = tonumber(one)
KNG_CLR.MARKER[2] = tonumber(two)
KNG_CLR.MARKER[3] = tonumber(thr)
end
end
kng_capture_clr_mrk()
My doubts have always been how to correctly define the complete path of the “filename”, so that it is compatible with the 3 operating systems and with all the possible Renoise versions. Do you think this code will always work?
Basically, a color is defined first (KNG_CLR.MARKER ={235,235,235}). After, the function takes the “Selected_Button_Back” color within the “Config.xml” file and, if the path exists, changes the color KNG_CLR.MARKER. If the route does not exist, it does nothing and preserves the previous KNG_CLR.MARKER color.This will only work when loading the tool for the first time.This type of tool is only loaded once in the memory, and remains there all the time, until Renoise closes. It would be necessary to restart Renoise or the tool in case of changing the Renoise color theme.
Edit:I am trying to get a reliable code to use it in all my tools.
couldn’t really see all interface elements on my 1366x768 screen.
The graphic design of the KangarooX120 is designed for HD screens (high of 1080 pixels) to see all the pads. However, its window design is cut in 2 parts. The first will show a mesh of 8x8 pads (64 pads, 966x648 pixels), and the second 7x8 pads (56 pads, 966x588 pixels), adding a total of 120 pads, designed for smaller resolutions. Use the 4 buttons on the left, above the piano, to change the graphic interface in its 3 viewing modes, or press F1, F2, F3 or F4.
I try to use this with addictive drums to make every drum instrument notes be written to separet tracks during midi recording with e-drums. Is this possible? Sorry for the spelling
Yes, it is possible. With the valuebox “PAD”, you can select each pad to configure it. Enable the swith of the left to change the selection of the pad automatically.
You can route each pad, being able to change 3 things:
The instrument. Use the instrument box of Renoise to change the instrument index, with the valuebox in “INS”.
The track. Change the track with the valuebox in “TRK”.
The note. Use the virtual piano to change it, with the valuebox in “NTE”, after completing points 1 and 2.
At the end of the process, you can save a bank, to retrieve it later in another session.
Edit: If you want to distribute groups of notes of one or several instruments in up to 10 separate tracks, you may be interested in using the Chord Builder of Piano Roll Editor v4. A very common case is to have a native instrument that is a complex drum kit. With the Chord Builder you can configure it very quickly, even trigger multiple notes from a single pad or a key. In this sense, the Chord Builder is more advanced than the KangarooX120. But if you only want to distribute single notes of different instruments on separate tracks, KangarooX120 will serve you. Remember to map the MIDI input to enjoy it.
I noticed that in the download section of the KangarooX120 tool at www.renoise.com the images are destroyed with the last migration. When I have time I will look to restore them with new images.
Look carefully at the values stored in each pad. Each pad has 3 lines of information:
Number or index of the pad.
Note value | instrument index.
Track index.
and…
…to the right of the pad: volume/velocity value (plug switch with “V” disabled)
A example (pad pressed):
Index of the pad: 43.
Note value: D-4 | Instrument index : 08.
Track index: 05.
…Volume/velocity value: 5F.
You must press the corresponding pad, not the piano. KangarooX120 are two virtual instruments for playing, the lower virtual piano and the upper 120 pads, which work separately.
The best thing is that you make a complete mapping of your MIDI pad with the pads that you want to use. Which MIDI pad are you using?
In this case I am saving a bank called “x16-Red Tr01-Tr06 C-4”, in which I have configured the red area of 4x4 pads, to always fire the note C-4 of the instruments 00 to 0F so that they record on tracks 01 to 16, with the same volume level 5F.
Each bank will always save all the configuration of all 120 pads. Go to the following path:
well this tool doesn’t work for me I tried like for a week now, like 20 times. I loaded that bank and I can’t change track number on the red pads like I used to, this tool have no effect. sorry.
Could this be just some typo bug or whatever that can be fixed? I would like to have this.
Also when I click on the knob(not the colored part) is it supposed to play the sound of the instrument connected to that pad?
@marbangens I’m sorry that you can not make it work. It seems that you have serious problems with the tool. Is it possible that you have not activated your OSC? I have taken for granted at all times that you had it activated.
I re-copy part of the instructions for use that are described in the comment #1:
2.- OSC & PREFERENCES . Enable OSC in “Renoise: Preferences/OSC/…”. Invoke the KangarooX120 tool. Then, show the preferences panel with the preferences button of the tool ((KangarooX120: press “RETURN”) and follow the instructions to set the configuration.
Make sure to use the same port 8000 with the protocol in Udp. Without the OSC, the tool “does not sound”, rather, Renoise “does not sound”. OSC is the communication protocool between the tool and Renoise.
KangarooX120 v1.1 build 030 works correctly. Make sure you use this version.
Yes, you can play the 120 pads with the mouse pointer or through the MIDI keyboard/pad controller, correctly MIDI mapped (the instrument, the note, the track and velocity configured). When you check the OSC settings, re-read the instructions above and try again. I assure you that this tool works correctly, very fine in addition.
What operating system are you using, and what version of Renoise are you using?
It would be nice if you copied a screenshot of your configuration…
You should be able to do this:
Edit: If any of your instruments “does not sound” after correctly configuring KangarooX120, maybe it is because the samples of the instrument are not properly configured. That is, if you play a routed pad with the instrument 03 for the F#5 note, this note must have an associated sample in the instrument. Otherwise, the note will not return a sound. That is, in addition to correctly configure KangarooX120 (which is only compatible with version 3.1.1 of Renoise), you also have to check that your instruments in Renoise are well configured (do not play a note that does not have a sample associated. The same for VSTi instruments).
If you do not want to make a video, you can use the program LICEcap v1.28 to capture the screen in an animated GIF.
I also use VSTi instruments (orchestral libraries). I have no problem with KangarooX120. Everything works correctly.
The KangarooX120 tool should work exactly the same in Windows 7 as in Windows 10.
Actually, the tool does not care if the instrument is a native one with samples (an XRNI) than a VSTi. The issue is that the instrument must be configured correctly to reproduce the corresponding notes, those reproduced from the tool. You can use the lower virtual piano to play an instrument while the other pads play the associated notes, as if you were playing two separate things. It is best to map a MIDI controller keyboard for the lower virtual piano and a MIDI pad for the pads, both sensitive to the velocity of the pulsation.
One more detail. Renoise has a problem currently with OSC and the undocked window of the instrument editor. If you have the Renoise instrument editor window separated, OSC can not send the messages from note_on, note_off to the pattern editor. Therefore, the tool will not work correctly. @Taktik already knows about this problem and will supposedly fix it. I mention it to you because this scenario can be the cause of not playing / recording the notes correctly, and this is a Renoise problem, not the tool. This problem affects all the tools that use OSC.
For the tool to work properly, you must have the instrument editor anchored, without a floating window.
I diddent have floating window. It behaves diffrent every time I use it, but on linux it had an effect. it made dubble notes. still on the same track… click on pad dont make sounds
I can not test in Linux, but it should work just like in Windows, since the API is the same. You must have correctly configured the OSC and the corresponding port open for the notes to sound.
Yes, you can record a multitude of notes at a time by playing several pads at the same time with MIDI Input.
To rule out problems, test with native XRNI instruments, instead of using VSTi instruments.
