Forum

@Denim wrote:

Hi, a suggestion for a small but very useful workflow improvement - and I think this should be a native one:

Buttons for jumping to previous/next slice marker in the Sample Editor. Could be next to for example the “Slice” button. Also: view-wise, it should jump so that the slice marker is positioned in the center of the view you get to, and preserve the zoom level.

Most audio editor programs supporting markers of various sorts have this functionality, and is a big timesaver, at least for me.

Why: I do a lot of long audio recordings in renoise, and often I need to slice them up by hand (not automatically), and then I first usually slice everything roughly while zoomed all the way out, and then start to zoom in on each single slice marker to do fine adjustments. But it’s hard to navigate in a long waveform while zoomed in, so then I need to zoom all the way out again, and in again, and it’s very tedious. Prev/next buttons as described would be a huge timesaver in these cases.

Posts: 3

Participants: 3

Read full topic

@Dry_Eyes wrote:

Meddling with classic synth samples in the context of tribal peecussion.

Posts: 1

Participants: 1

Read full topic

@EggMcNuthin wrote:

I cut up the monowave and SQ80 full ROMs into individual waves and oneshot samples.
I also included ‘wavemaps’ showing the start and end points of the individual waveforms in the full ROMs for anyone who wants to try and scan a loop accross them them using the ‘loop control’ tool. There is also tuning information ( check the readme ). I tuned all the waves, saved them all as renoise instruments inside a renoise song file. They are great, please enjoy.

New Tool (3.0): Loop Control Renoise Tools Yo, Renoise crew, here’s a tool that lets you do sample loop point automation [image] 4939 [Screenshot 2014-04-21 20.27.59.png] It works by creating a doofer that is tied to the loop points of the selected sample. This can be done to multiple samples across multiple instruments. The loop control doofers are contained in a dedicated FX chain within each instrument and numbered according to the sample index. Usage: To create a loop control doofer, select ‘Add Loop Control’ from the sample list…

Get the wavs, tuned renoise instruments and wavemaps here,

After entering the ‘I am not a bot’ code, right click download. It will not download by hitting ‘enter’ on the keyboard.

Posts: 1

Participants: 1

Read full topic

@milkyheart wrote:

last weekend, i made the soundtrack for a quirky rhythm game.

check it in game context too if you feel like it: https://verysoftwares.itch.io/panic-percussion

Posts: 1

Participants: 1

Read full topic

@Lytz1 wrote:

Hey gang.

I work with a lot of groups (like a lot of you probably do as well)
and usually, I need to jump often to the groups (Ignoring the tracks in between,
which are often collapsed anyway at that stage)

So the idea is to have commands that jump just to the group-tracks.
(something like “jump to prev/next group track”)

Should be simple? Not sure. I have just recently started to look at LUA and this is still quite over my head.

Any ideas on this?

tL.

Posts: 2

Participants: 2

Read full topic

@fortina wrote:

Hi there! I come from Octamed Soundstudio on the Amiga and I’m importing some old tracks and have noticed something which I need some assistance with. Firstly a brief outline of my current setup:

I have an external synth, the Yamaha DX27 which only allows for 1 program to be played at any one time on a single midi channel. I have mine setup to receive on midi channel 16.

I have a few old Octamed tracks which I’m currently in the process of converting and importing into Renoise. In Octamed I have a couple of instruments set up with midi channel 16 and different programs each to play different sounds on the DX 27. If I select one of the instruments, it plays the correct program on the synth. If I then select another instrument it automatically sends the correct program and the synth plays the different preset.

This is also the case for the sequence. If I have “instrument 1” playing in track 5 in block 1 for example and then “instrument 2” playing in track 5 in block 2 then the correct sound / preset is played in each of them. i.e. the synth always plays the correct preset / program which is set for the instrument in the sequencer.

Now to Renoise:
If I select an instrument in Renoise which is set to midi channel 16 and whatever program number is set, the synth will only play the correct preset if I manually change the program in the instrument settings in the midi tab. Selecting another Renoise instrument which is set to midi channel 16 with a different program number does not update the synth / change the program and needs to be set manually again / refeshed.

The same goes for the sequence. If at the beginning of the song the DX 27 is set to use program 8 for example by playing some notes in lets say track 5 for arguments sake, and then another different instrument is set to play / use program 10 in track 5 further down the sequence, the synth is stuck on program 8 and plays the wrong sound.

Is there a setting / method for making Renoise automatically update the sound being played on the synth when a different instrument is selected / played in the song?

Posts: 1

Participants: 1

Read full topic

@LofiMat wrote:

While working on my second doofer I noticed that the 3.1 Chorus device is changed and not the same as on my old mashine using 3.0. For the new Doofer (Stupid One in German) I would prefer the old chorus. I it still hidden somwere in Renoise 3.1 or accessable?

Dank

Posts: 1

Participants: 1

Read full topic

@ffx wrote:

If I was asked (I know I am not),I would consider the last, “doubled” point in the automation lane as conceptual flaw, since it leads into a lot of nonsense. Instead the automation lane should always look into next patterns next point. Ok there are pattern boundaries, who btw. actually needs to repeat a pattern using the same pattern number at all?! Still only have 64kb of RAM?

IMHO remove pattern repetition possibility at all (only keep numbering for comfort reasons, but not editable, auto increasing), remove vertical aliases (it is not that hard to use shift-f4 / shift f5), make automation drawing and handling boundary-less, make a linear representation of the song position in the api, not caring for patterns at all, then people can easily adapt their tools to make it work boundary-less and also Renoise internal tools easily can adapt, like adv. edit.

Since talking about removing not helpful complexity: Then remove instrument numbers, and the instrument list (or make it a track overview instead), put the instrument into the track chain at the left position as in Bitwig, then the instrument device also will be the automation device, no more cluttering or possible use of multiple autom. devices or on tracks not related to, etc.

Then remove all old versions Renoise backwards compatibility (people still can use Renoise 3.11), remove all “old mode - want to convert?” - behaviour (but no need to remove old dsp, doesn’t hurt), only one time write a 3.11->new version converter / song import so old songs adapt to the new structure, without any option. This to unclutter the amount of code. (Of course keep ft2 / protracker import).

API would break a bit, but also not that hard to fix for the tool devs, and in the end, it will be a lot more easy to use.

Super Renoise geeks gonna hate me now.

Posts: 23

Participants: 6

Read full topic

@bzakirasantjago wrote:

my new work :

http://bzakirasantjago.blogspot.com/2019/04/hackers-bz-akira-santjago.html

Posts: 1

Participants: 1

Read full topic

@stephaniesu wrote:

Hi All, I’ve written an intro guide on the musical notes for beginners learning piano. I am the main author on this article and feel free to check it out or let me know if you have any feedback. I hope it helps

Posts: 1

Participants: 1

Read full topic

@valankar wrote:

Spent my Saturday on this, enjoy!

Posts: 1

Participants: 1

Read full topic

@joule wrote:

I believe that patterns_observable sometimes can break, unless I made some rookie mistake.

My guess of possible cause, kind of: When using the duplicate sequence menu, while having “Keep sequence sorted” enabled, renoise will re-use any empty+non-used patterns that are found in between used patterns. This causes the patterns_observable not to reflect what really happened to the list. (?)

It can be reproduced by loading “DBlue - tension”, enable “keep sequence sorted” and duplicate sequence 15 with the code below (re)loaded.

Example -- extend table class table.swap = function(t, index1, index2) t[index1], t[index2] = t[index2], t[index1] end class 'App' function App:__init(args) self.song = args.song self.pattern_list = table.create() -- add newly inserted pattern to the internal list self.pattern_init = function(pattern_idx, pattern) self.pattern_list:insert(pattern_idx, pattern) rprint(self.pattern_list) end -- update the internal list to reflect song.patterns self.update_pattern_list = function(event) if event.type == "insert" then local pattern = self.song:pattern(event.index) self.pattern_init(event.index, pattern) elseif event.type == "swap" then self.pattern_list:swap(event.index1, event.index2) elseif event.type == "remove" then self.pattern_list:remove(event.index) end end -- initialize the internal list for pattern_idx, pattern in ipairs(self.song.patterns) do self.pattern_init(pattern_idx, pattern) end -- add pattern list notifier self.song.patterns_observable:add_notifier(self.update_pattern_list) end local app = App { song = renoise.song() }

Posts: 1

Participants: 1

Read full topic

@lilith wrote:

When I cut a sample in several slices and play the slices the waveform automatically switches to the sliced sample, which I find annoying. Can this behavior be disabled?

Posts: 1

Participants: 1

Read full topic

@rainydayshirts wrote:

First thing I’ve done in Renoise. Still getting familiar with the software. Probably going to play with the mix some more. Everything in the track was created using built-in Renoise DSP FX and/or completely free VSTi’s and royalty-free/$-free samples.

Posts: 1

Participants: 1

Read full topic

@Neuro_No_Neuro wrote:

Not being a coder, I have no idea how to implement something like this into Renoise. Would it be possible to make something out of this code?

https://github.com/antonhornquist/gong

One can dream, no?

Posts: 1

Participants: 1

Read full topic

@Denn1593 wrote:

Here is a new song i have made. Enjoy!

Posts: 1

Participants: 1

Read full topic

@Same_Freaky_Sound wrote:

Just to help to spread info on their absolute clever controller.

Mine is designed for those DJs, producers, and musicians who are looking for a highly customizable, expandable and reconfigurable product. Mine is a modular midi controller consisting of a case suitable for accommodating modules made of single electronic interfaces in order to offer the maximum flexibility in the creation of its configuration. Solutions available on the market today don’t always fulfill the user’s needs.

http://queue.vip/Qr54OrH

DISCLAIMER:
I’m not related to this company at all, just proud that its an Italian company

Posts: 1

Participants: 1

Read full topic

@Raul wrote:

Renoise 3.1.1 x64 W10 x64:

I think there is a small problem with the following case of aplication:

– Opens a modal dialog to query an existing directory from the user.
renoise.app():prompt_for_path(dialog_title)
-> [valid path or empty string]

There is no way to return nil or a boolean, or string “Cancel” to identify if the user presses the “Cancel” button.

The specific problem is that, apparently the return of an empty string (""), returns the path C:/, a valid path. The issue is that some form of being able to continue with the function without resorting to the empty string is necessary. What happens is that if you use the empty string to continue with the function, the “Accept” button will do nothing, if you use the empty string as a condition to continue with the function (if path == “” then …)

The expected thing would be, to return

1. non-empty string or empty string (both)
2. nil …or “cancel” string.

That is, it is not possible to use the empty string for the Cancel button. If so, the OK button will not be able to take the empty string as a possible route. It forces the user to change the route in the pop-up window, when it should not be like that. C: / is also a valid path to save folders.

Posts: 1

Participants: 1

Read full topic

@Raul wrote:

I do not know if this matter is a forgetfulness or something that really works badly.

What happens:
The clock (top right) is always updated when changing lines in the pattern editor.
But if you enter a ZTxx or ZLxx effect, the clock is only updated when changing the pattern, but not when changing lines. Even if you clean all these parameters, it will not update per line.

This does not seem to affect the automation editor for BPM and LPB

The expected:
That the clock is always updated when changing lines, even if the parameters ZTxx or ZLxx exist.

Something related to this would be, if the API could have access to the clock data. It may be possible to build tools related to time, such as a time marker in the whole sequence, it would be very interesting.

Posts: 1

Participants: 1

Read full topic

@chrissp wrote:

Is there any chance of Renoise supporting MIDI Polyphonic Expression (MPE) in a future version? Or is it already possible to use the current version of Renoise with VST instruments that support MPE and an MPE compatible controller?

Posts: 1

Participants: 1

Read full topic