Forum

Hello All, I want to know which PHP version quipped to spaceship operator between php5 and php7. As I am working on PHP 7, PHP7 is quipped with a new operator popularly referred to as spaceship operator which has a notation <=> Function can automatically return to null when the value is not accessible but I have not an idea about PHP 5. Can anyone suggest me?

1 post - 1 participant

Read full topic

I’m not sure if this is a commonly known trick, but i have just heard Renoise can’t do granular synthesis and i haven’t really thought about how a granular effect is being made.
The audio is chopped up into pieces of variable size with effects added to each ‘grain’, all in realtime and with parallell prosessing. I was almost lost at the chopping up part, but then i thought “why not use send tracks as ‘grains’?”
It sounded a bit far fetched, but when i tried it i was quite surprised how well this actually worked. In this example i use 6 ‘grains’, but you can make any number as long as your cpu is up for it.
Let me explain:

Add 6 send tracks for the grains and one as a bypass:

Add a gainer and set the output volume to -12 on all the grains tracks, but leave the bypass track as it is:
Grains:

Bypass:

Go to Track 01 (or any track for that matter) and add a Send device for all the grains like this:

Add a Send track for the Bypass in the front of the chain (turn it off and use it when you want to hear the dry signal):

Now for the actual splitting, let’s add an LFO that controls the grain sizes with it’s frequency slider. Let’s call it the master LFO:

Connect the LFO to a Hydra:

As you see, 6 LFO’s are controlled from this Hydra, so go ahead and make 6 LFO’s look like this:

Now, if you set everything exactly as i did here, then you should hear the exact same sound when you enable the bypass no matter which frequency you set the master LFO.
Now see what happens if you start adding different effects on the send tracks, then slide the frequency of the master LFO and you will hear the grains start changing size.
The higher the BPM and LPB the shorter you can make the grains.

GranularTest.xrns (578.9 KB)

1 post - 1 participant

Read full topic

I have to say my favourite is ‘Get At Them’ from 2016:

2 posts - 2 participants

Read full topic

The title says it all, is this possible with the current API? I couldn’t find it…

1 post - 1 participant

Read full topic

beat_select

Faster selection inside the pattern editor by beats and tracks. It snaps the selection to the start and end of beats automatically regardless of where you start it from.

Provides four key-bindings in Pattern Editor / Selection

• Select until previous beat
• Select until next beat
• Select until previous track
• Select until next track

And additionally two in Pattern Editor / Navigation

• Jump one beat down
• Jump one beat up

see the source on gitlab

download from direct link (this zip includes all my other tools as well)

1 post - 1 participant

Read full topic

Hello,

me is sorry for this beginners question, but how can i load / choose a soundfont for the fluidsynth-dssi plugin?

os: debian 11
renoise: 3.3.2
fluidsynth-dssi: latest compiled from source with gui / gtk support (note that the distro supplied is not working either, therefore the effort to compile).

In the past, after choosing the plugin, the gui opened automatically. Now nothing happens. There is a button “external editor” or so, but it is without function, i.e., nothing happens when clicked except on / off widget change.

I suspect that this started after recent upgrade from debian 10 to 11, but as i already upgraded all my machines, it is difficult for me to prove.

The plugin seems to work otherwise, as already saved songs are playing, resp. i can use one as a template, but it is really a workaround.

As far as i can see, when starting renoise in a terminal, there is nothing unusual.

Did not extensively used renoise for a while, so apologize, if me is missing something obvious.

Cheers,
mirsha

1 post - 1 participant

Read full topic

Hello,

I am not enjoying making music any more and I am therefore going to try to recoup some of my investment. Below are all for sale:

• Renoise registered until 4.2: £35.00
• Redux registered until 2.1: £30.00
• U-He Diva: £75.00
• Synthmaster 2.9.9: £45.00 (I need to pay a 15 Euro transfer fee to sell the licence, so not willing to negotiate on price)
• Softube Modular: £50.00 (I need to pay a 25 Euro transfer fee to sell the licence, so not willing to negotiate on price)
• Cockos Reaper - £15.00
• D16 Group Decimort - £20.00
• D16 Group Phoscyon - £25.00

Any questions please ask, happy to help. Payment via Paypal “Friends & Family” is ideal to save on seller fees and so on. Open to reasonable alternatives like bank transfer etc.

Thanks

1 post - 1 participant

Read full topic

Windows 10

Getting Crashes Version 5.6.0 of T-Racks 5 – Also happens in renoise 3.3.

Start loading some T-racks 5 plugs in renoise and open their GUIs. After about the third plug and GUI opening it will take renoise down with the “Ouch” crash dialog.

Seems to replicate easily when searching and loading with ‘VSTi from menu’ tool with auto-open gui enabled (Ed. checkbox) .

but can be done via loading and opening normally in renoise too.

Tool if needed:

https://forum.renoise.com/uploads/short-url/jOvuQlwBPcG67Olvl1cM6iW6X61.xrnx

Shortcut:

`VFM` Search and Load FX

Latest IK product manager:

https://www.ikmultimedia.com/demodownload/

1 post - 1 participant

Read full topic

Perhaps it’s just taking a very long time since I just did a clean reinstall but the waves shell is scanning fine in Bitwig Studio & Metaplugin.

This is a very common problem with Waves plugins. Any renoise specific tips?

1 post - 1 participant

Read full topic

As I’m developing more tools I’m faced with the annoyance of having to duplicate the same helper functions inside the scripts of different tools. Has anyone tackled this problem before?

Thought about having a “base tool” that would contain common scripts my other tools could include in their source. Of course this could lead to issues across different versions and such but nevertheless here is a function that does the inclusion. It also makes it possible to rely on any other tool in general but that is even dirtier

function include(dir, module) local path = dir .. "/" .. module .. ".lua" local file = io.open(path, "rb") if(file ~= nil) then package.path = package.path .. ";".. dir .. "/?.lua" require(module) package.path = package.path .. ";./?.lua" else local message = path .. " not found!\n make sure you have " .. dir .. " installed!" renoise.app():show_prompt("missing dependecy!", message, {"OK"}) end end

And one would use similar to require like:

include("../com.exampler.base_tool.xrnx", "util")

to include a script named util.lua from another installed tool.

To be clear, not saying this is a good solution or that anyone should use this, just sharing for fun.

I guess another way might be to pack all my tools into a single tool as they don’t take up much space anyways and they only offer keybindings so there is little drawback to having all of them installed.

Alternatively one could “build” tools by including the necessary files but I like the fact that my source is the same thing as the distributed tool.

2 posts - 1 participant

Read full topic

Not sure if this is a bug: The scream filter seems to distort even with distortion at 0%. Is this an expected behaviour?

1 post - 1 participant

Read full topic

Hi,

do you think there might be a workaround for the common selectbox problem with U-He plugins?

Currently all selectbox popups in any U-He plugins are not clickable as long as the “enable keyboard” option is checked. So then you will have to click that checkbox many times. I alrady asked U-He, they say it’s a Renoise problem. I think they use a normal system’s select box.

3 posts - 2 participants

Read full topic

Hello there,
i’m having problems recording automation via MIDI.
It seems that Commands that are not mapped go into the Effects Column of the active Pattern, overwriting possibly existing commands and flooding the song with unneeded information.

Now the MIDI-Controller i’m using is a DIY one, so im not quite sure if the problems on sloppy programming or Renoise or me being dumb (Channels used are 6 and 7, CC Numbers don’t seems to make a difference), but if someone has some idea whats wrong/how to fix this please let me know.

Thanks and greetings,
Jochen

3 posts - 2 participants

Read full topic

Anyone know some good ones? I already have the Datafile and X-Static Goldmine stuff, and that’s the kind of thing I’m looking for - old school house/dance vocal samples, like the stuff you hear in Haddaway or similar. Having a hard time finding samples like that, these days it’s mostly “vocal chops” and mediocre accapellas etc. Thanks!

1 post - 1 participant

Read full topic

Hi @taktik, I was wondering if you could share how the .automation[].points[].scaling variable (-1.0 - 1.0) works to create the interpolation curve. I’m developing a tool and have been trying to figure out how to calculate what values will be between two automation points, but reverse engineering complex math equations is not really my strong suit.

1 post - 1 participant

Read full topic

‘Try remove CachedFailedVSTs_x64.db and CachedFailedVST3s_x64.db in your preference folders and do a rescan.’ This is not a solution before anybody suggests it.
I was onto waves support,I uninstalled everything including renoise,worked the first time,failed after.Anybody else having problems?

1 post - 1 participant

Read full topic

R3.3.2 W10/W11
Go to: Renoise: Edit/Preferences/GUI/Global: "User interface scaling"

If you change the scaling, some elements do not finish positioning themselves in place.
For example:

1. You will see inconsistencies in the “Preferences” panel, which is a floating window. Some GUI objects do not fit properly.
2. You will see that the Renoise top menu (File, Edit, View …) does not correctly adjust the horizontal spacing between the texts.
3. You will see strange mismatches between objects in somewhat more complex GUI window tools.

Interestingly, if you have the option Reload All Tools enabled in the tools menu, you can partially solve the problem. That is to say:

1. You change the scaling of the GUI (some graphic objects do not fit well).
2. You click on “Reload All Tools” and some problems are solved, like the horizontal spacing in the Renoise menu or the correct distribution of the objects in the complex window tools.

This makes me think that changing Renoise’s GUI scaling doesn’t end the whole process. One step is missing to correctly resolve the exact location of all graphic elements.

3 posts - 2 participants

Read full topic

R3.3.2 W10/W11
In general, the entire folder of mouse pointer cursors needs an update. The problem is that some cursors are pixelated, due to their inappropriate size (width x height).

I guess this was not finished due to lack of time?

How to see it?

Go to the usual Renoise installation folder.
C:\Program Files\Renoise 3.3.2\Resources\Skin\Cursors

Examine all the cursors to check their format and size.

For example, if you take the cursor Default.cur (31 KB, static cursor, multiple formats) as a reference, you will see that it is different from the rest, with much higher resolution.

For example, take the cursor “ValueChooser.cur” (1 KB, static cursor, 32x32 pixels) and you will see that it has a much lower resolution than Default.cur.

Here is a capture (with RealWorld Cursor Editor program):

Other…

You can check all the icons …

This causes a poor experience when using Renoise (it looks like a “beta”), even more so if you use a scaling greater than 100% in the GUI.

Solution

Replace all icons with small resolution (all of 1KB) to match with Default.cur reference icon (of 32 KB), in “multiple formats”.

1 post - 1 participant

Read full topic

If you recording midi notes into a looping pattern, and the last note which started at the end of the pattern still was not lifted on pattern-restart, the note-off will be placed AFTER the next note. So two note-offs then will be messed up. I think here the last note-off simply could be left out, if a new note passed the playhead… Not sure which logic would make the most sense, how do other DAWs handle this case?
Maybe the whole note at the end then should be moved to the right, but this could make no sense for the sequence. I think in any case then, leaving out the note-off would be the better approach…?

2 posts - 2 participants

Read full topic

Good morning,

I would like to suggest to you to add the (currently missing) basics to midi recording:

a) Renoise lacks of “erase on/off” / “overwrite/overdub” modes. I’ve seen a bunch of scripts which try to compensate this lack of features, but all those scripts never do the job accurately like a native implementation. This might be due the fact that playback events in lua always fire sloppy, so you will always need some pi*daumen lookahead.

Concept
I think there should be an “erase on/off” button next to metronome button or so, also shortcuts. In “erase on” mode, Renoise simply deletes all notes which are in the way, in the same row of the track used while recording. It acts like there was no notes in the track yet. After stopping, it also will fix maybe obsolete note-offs. In “erase off” mode, it should respect all existing notes, even after pattern repeat.

b) Renoise is not very intelligent when it comes to recording into a loop. Once the loop range passed, it usually messes up the note data on the beginning of the pattern. Humans are not machines, so it will be very likely that you leave the note a bit too late for example.

c) If you record something, you fail and undo it and then record again, Renoise now might have placed the cursor to a more right column, without obvious reason. Or Renoise thinks that there is note data on the left, but there isn’t any. I don’t remember the exact scenario, but this happens pretty often.

d) Lack of minimal comfort stuff: A metronome volume would help a lot, if you have a pretty quiet base mix, the metronome simply will destroy your ears (I also think a shorter more percussive “tick” sound would also improve the experience). Also it would be nice to a have a mode “pre-count, but later disabled”. So the metronome precounts, and then stops! The current precount switch could have three states instead only 2. Precount also could get an extra icon. Or precount was not an extra property anymore, but metronome on/off would get more states instead. Such thing also is pretty difficult to implement using lua.

I don’t think this would be lot of effort, but heavily improve the midi recording experience.

Thanks for consideration!

1 post - 1 participant

Read full topic