Feed aggregator

@LofiMat wrote:

short description:

• WOWzzr = Wow // AMTrzz = Depth
• FLUTTr = Flutter // AMTrtt = Depth
• Hidden Menue = HP // LP - Filters

hope someone is having fun with with simple but effectiv tool.

FLUTTrMANN.xrdp (5.2 KB)

FLUTTrMANN (means Wow&Flutter in german)

Posts: 1

Participants: 1

Read full topic

@saine wrote:

Perhaps I might interest you in a beat tape…

—> saine.bandcamp.com

(SoundCloud teaser)

All made in Renoise <3

Posts: 1

Participants: 1

Read full topic

@dspasic wrote:

Just a little practice with automating release via macro , and sample loop points (via macro as well)

i’ve used some airwindows plugins (example: on master ironoxide 5) and just for quick “glue” tdr kotelnikov GE on master

the main melody (pluck-alike) is drawn in the sampler

Posts: 1

Participants: 1

Read full topic

@Arcangled wrote:

I’ve had a productive month, by my standards. I’ve written a whole two tracks - twice as many as I’ve been doing per year, lately - and thought I’d share them here. So long as I can get these embed links to work.

Any comments/suggestions very much appreciated!

Posts: 1

Participants: 1

Read full topic

@trueschool wrote:

I just discovered the open source Surge VST/AU synth. Just opened it up and am already LOVING the wide variety of high-quality, useful presets. Check it out.

https://surge-synthesizer.github.io/

Posts: 1

Participants: 1

Read full topic

@Lincon wrote:

Hello everyone,
I’ve been thinking…

The renoise-zip-download in backstage contains the program BUT ALSO samples,instruments and demo songs…

Wouldn’t it be cool if the next update will contain some tools too?
Maybe some of the tool creators wouldn’t mind to have their tools in the zipfile…

Posts: 1

Participants: 1

Read full topic

@Raul wrote:

Given the complexity of Renoise, it is quite possible that there is no reasonable way to obtain the following:
The intention is to introduce very quickly in a table the BPM values ​​of each line along all the patterns of the whole song according to the sequence. Thus, said table will be used to consult it for a cumulative time calculation function.

This is an experiment that I have done:

local function sleep(ms) local sec=tonumber(os.clock()+ms) while (os.clock()<sec) do end end local function rec_bpm_lpb() local song=renoise.song() local trn=song.transport local tbl_bpm={} local tbl_lpb={} local ssq=song.sequencer for seq=1,#ssq.pattern_sequence do song.selected_sequence_index=seq tbl_bpm[seq]={} local nol=song:pattern(ssq:pattern(seq)).number_of_lines song.selected_line_index=1 for l=1,nol do tbl_bpm[seq][l]=trn.bpm sleep(0.050) if l<nol then song.selected_line_index=l+1 end end end rprint(tbl_bpm) end rec_bpm_lpb()

This function is excessively slow because it is not possible to extract the BPM value per line quickly (that’s why the function uses a sleep).

…

This implies 2 things:

1. Attend to the BPM values ​​of the automation editor (something extremely complicated, because they are not the value of the points, but the value of the ramps in each line)
2. And the ZTxx effects of all the lines (always take as priority the most right value of the line, in the track that is furthest to the right).

The objective is to create a tool that obtains down all the durations of all the patterns, individual and accumulated. But I’m afraid this is impossible to do.

As far as I have come, I have achieved a reasonably fast tool but only considers the changes for all the effects ZTxx (BPM value) throughout the song, (actually it also contains the changes of all the effects ZLxx (value LPB) ).

But at the moment of involving the BPM values ​​of the automation editor, there does not seem to be any reasonable way. The most unfavorable scenario is 1000 patterns of 512 lines. The tool should calculate everything in a reasonably short time, between 10 or 20 seconds I think it would be quite reasonable.

I think all this is impossible to do. If someone wants to think about it, leave your comments here.

The only way that could be calculated is for the API to offer the exact BPM value of each line, which is a data that depends on its ZTxx effect and its BPM ramps from the automation editor.

It would imply having a record of:

1. renoise.song (): pattern (p_idx): track (t_idx): line (l_idx) .bpm_value
2. renoise.song (): pattern (p_idx): track (t_idx): line (l_idx) .lpb_value
3. renoise.song (): pattern (p_idx): track (t_idx): line (l_idx) .tpl_value

Renoise does not have a vertical timeline in the sequence (left panel), where a cumulative time clock is detailed by pattern (let alone per line). And unfortunately there is no way to create a tool for this purpose, as far as I know.

Still other parameters exist that influence the duration of the song, and therefore in all the times accumulated by each line. This still complicates things more.

Has anyone ever tried something like this (create a tool that calculates the accumulated times of the song with all these factors)?

Posts: 4

Participants: 2

Read full topic

@Neuro_No_Neuro wrote:

Love the sound of tuned filterbanks! Ambient music from the inside! All Renoise with the help of Michael Norris’ Spectral Filter Audio Units.

Posts: 1

Participants: 1

Read full topic

@Neuro_No_Neuro wrote:

Love the sound of tuned filterbanks! Ambient music from the inside! All Renoise with the help of Michael Norris’ Spectral Filter Audio Units.

Posts: 2

Participants: 2

Read full topic

@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