Renoise Forum

@Neuro_No_Neuro wrote:

OK, I drew a click sample, 10 samples long, into the sample editor. I then sliced the sample into two pieces. Sample and Sample Slice 1, shown here:

I have a pattern playing it as such (note change to slice 2 (S02)):

The sample plays back fine, the second slice is also working fine in a normal fashion.

What I do not know is how to make the second slice become time-stretched. Rather, enable the timestretch function AND get an audible difference.

What I did find out with a different sample is that the sampling portion that gets timestretched might need to be a certain sample length. 9 samples long is not long enough.

The only way I figured out how to do this was use a longer sample, such as a full-length hi-hat sample, and then duplicate it. Then set the two samples up as a drumset, and THEN apply the timestretch to the second sample only. It will stretch, and it will cut off when the non-stretched sample gets selected again in the pattern, kinda like a hi-hat cutoff.

I was hoping, initially, to be able to trigger the timestretch via the pattern itself, y’know, putting in a command in the sequencer to trigger “beat sync” on and off. No go. Unless I’m mistaken, this timestretch effect really is more for those making tracks with sample loops, versus single notes.

Is there some way to perhaps be able to do this via the sequencer, so I would be able to trigger a timestretch effect on a single sample (like a hi-hat or a bass drum or a note), or a short length of samples?

Posts: 1

Participants: 1

Read full topic

@EamonnMR wrote:

Reason 11 is out in late September and it’s going to be a VST. Would make my workflow a heck of a lot easier. Maybe I’m the only one who wants vst3 support. Just figured I’d put it out there.

Posts: 2

Participants: 2

Read full topic

@TURRICAN wrote:

When accessing the GUI Hi-DPI settings, Renoise 3.2 crashes to desktop when switching between settings…It’s very buggy…because the GUI will scale from 125% to 100% but changing that to a different setting just crashes Renoise.

Posts: 5

Participants: 2

Read full topic

@Tumulte wrote:

That’s a very simple improvement : just make redux versions follow renoises version (making it Redux 3.2, rather than 1.1)

(or at least 1.2)

From a strict programming point of view, redux is 1.1, but from a customer point of view it has renoise 3.2’s features.

“1.1”, kinda implies it’s less advanced (or that redux is unrelated to renoise), “3.2” clearly states it comes from the same batch

Posts: 1

Participants: 1

Read full topic

@Daed wrote:

When I try to render a timestretched selection to a sample, I get a sample of the original pitch/time.

Posts: 2

Participants: 2

Read full topic

@gentleclockdivider wrote:

Assign an intrument fileter to macro control , and automate it

When scrolling through the pattern with mouse wheel or arrow keys and playing the keyboard, the filter frequency is not updated

Posts: 7

Participants: 3

Read full topic

@mabersold wrote:

I only have Renoise installed on my home PC, but sometimes I get an idea for a tune when I’m on the go and only have access to my phone or maybe a laptop. Are there any simple tools for recording and saving a quick tune that I can access later? I’ve used an audio recorder in the past but I don’t really like humming into my phone in public.

Posts: 1

Participants: 1

Read full topic

@Neuro_No_Neuro wrote:

Neat update, got some time-stretching and nicer envelopes! New issue, though.

I have an 8-sample long “tick” sound. I was using the HP Clean filter in the Modulation section. It seems to not work on a one-shot sample. If I take it off the “One Shot”, the filter works. There’s no filter envelope involved, it’s just a short, drawn sample.

BUT

If I open a new track, the filter works fine on a regular hi-hat. If I open a new instrument, like my “tick” sound, it works fine there as well. Maybe I’ll just have to replace the sound?

Since I’m using that filter to timbrally control the sound, is there something I can to to make this work again?

Posts: 2

Participants: 1

Read full topic

@quadis wrote:

note off: why can’t i put a “note off” on the line that i’m currently on. whenever i press caps lock it jumps down a line and puts the note off there instead. is there some way to change this (other than changing the overall step length to 0)?

block loops: is it possible to have it play from the top of the block loop when i press enter like in 2.x? any time i press enter it starts playing from the line i’m currently on instead of from the beginning of the loop.

Posts: 1

Participants: 1

Read full topic

@Raul wrote:

With the current API 6, is there a way to detect that a window whose path is known is open, to avoid opening it again in another window and placing it in the foreground?

• For example, to open a window: renoise.app():open_path(file_path)
• But if the window is already open, how to place it in the foreground?

Posts: 1

Participants: 1

Read full topic

@NoiScale wrote:

Posts: 2

Participants: 2

Read full topic

@TheDamnChicken wrote:

I discovered some nice Timpani rolls, which played nicely with a synth piano. The track sort of happened like that…

I hope you like the spooks!

Posts: 1

Participants: 1

Read full topic

@unknown wrote:

Is it possible to chain phrases while working in the Redux plugin? For editing purposes it would be helpful to organize the playback of phrases from within the plugin without needing to rely on MIDI triggering since this can create a lot of awkward back and forth.

Posts: 1

Participants: 1

Read full topic

@Land_of_Bits wrote:

Posts: 1

Participants: 1

Read full topic

@taktik wrote:

Registered Renoise users can be download the update, as usual, from the Renoise backstage.

Demo versions are available at https://www.renoise.com/download

What’s new

• HiDPI (Retina) support and custom GUI scaling options. See below for more information.
• Rubberband based native time-stretching options in the sampler.
• Detachable mixer view. (Renoise only)
• Custom exponential, per point scaling in all automation editors and the AHDSR modulation device.
• Preview of sample editor selections with computer keyboard or MIDI.
• A whole bunch of bug fixes.
• Lua API changes: see here Most Renoise 3.1 tools will auto-upgrade and work just fine in Renoise 3.2.

System requirements Renoise

Renoise 3.2 is only available as a 64-bit application, but 32-bit plugins still can be loaded via the plugin bridge.

• Windows: Windows 7/8/10 64-bit or later. Windows 10 highly recommended when using a HiDPI monitor.
• Linux: x86_64 based Linux with glibc >= 2.19 (e.g. Ubuntu 14 or later).
• OSX: OSX 10.9 or later.

Redux

Redux is available as a 32 and 64-bit plugin.

• Any VST or AU (OSX) compatible 32 or 64-bit host.
• Windows: Windows 7/8/10 or later - 32 or 64-bit.
• Linux: x86 or x86_64 based Linux with glibc >= 2.19 (e.g. Ubuntu 14 or later).
• OSX: OSX 10.9 or later.

HiDPI & UI Scaling

HiDPI (High Dots Per Inch) or ‘Retina’ displays have a high resolution packed into a relatively small form factor, resulting in much greater pixel density than normal. Initially found on phones and tablets, they are becoming more commonly used in high-end laptops and monitors, especially those with a 4K resolution. Compared to regular displays, HiDPI renders pixels at twice the normal horizontal and vertical resolution, giving an overall density increase of 400%. To make use of this extra density without resorting to upscaling requires explicit support from the software application.

For more general and technical information about HiDPI:

• What is HiDPI and why does it matter?
• Pixel Density 4K

Renoise is now HiDPI-enabled

Starting from version 3.2, Renoise is a HiDPI-enabled application. If you don’t have a HiDPI display this changes nothing, though you can still make use of the new ‘User interface scaling’ option. If your display is HiDPI then the OS will now draw the Renoise UI in the higher native resolution instead of manually upscaling. That upscaling is typically performed by the OS so that non-HiDPI-enabled applications appear at the same size as they would when running on a non-HiDPI display. The downside of upscaling in this manner is that the UI can become blurry and sometimes lacking in responsiveness - issues which Renoise can now avoid completely.

Disabling HiDPI Support

If you need to disable HiDPI support, this is performed in the following way depending on your OS:

• Windows: Right-click the Renoise executable and select ‘Properties’. Go to the Compatibility tab and click on ‘Change high DPI settings’. In the DPI settings dialog, enable the ‘Override high DPI scaling behavior’ option, then in the ‘Scaling performed by’ drop-down menu select ‘System’.
• OSX: Toggle the ‘Enable Retina support’ option in the Renoise “Preferences > GUI” tab.

Requirements for HiDPI Support

• Windows: Windows 10 is required for full support. On Windows 8 the Renoise UI will be HiDPI, but Plugin GUIs will not be scaled. Versions of Windows prior to 8 do not support HiDPI.
• OSX: No special requirements.
• Linux: If your current Linux setup works with a HiDPI display, Renoise should work too.

User Interface Scaling Option

Found in the “Preferences > GUI” tab, the new ‘User interface scaling’ option can override the amount of scaling used by the default ‘Auto’ setting, which uses your main display’s DPI value*, and instead uses a percentage chosen from 100-350%. This option can still be used to enlarge the Renoise GUI even if your display isn’t HiDPI, making it more comfortable to use on higher resolution screens.

* On Linux: When present, the X resource ‘Xft.dpi’ setting is checked and followed, then the scaling is deduced from the default display’s ‘DisplayHeight / DisplayHeightMM’ ratio.

Limitations

Currently in version 3.2, the entire Renoise UI can only be displayed at one single level of scaling. When using multiple monitors with different DPI settings (or a non-HiDPI display using a HiDPI setting), the UI will always be rendered at the DPI of the main display and then up/down-scaled as needed on the other display(s) by the OS. So, if your main display is HiDPI, but you want to use Renoise primarily on another non-HiDPI display, you should disable the HiDPI support in Renoise to prevent blurring and potential lag.

Using VST/AU Plugins on HiDPI Displays

Since plugin instruments and effects are actually external applications, their interfaces are not controlled by Renoise. Most old (and even many new) plugins don’t support HiDPI displays, which may have implications depending on your OS.

• Windows: By default all plugins are treated as non-HiDPI-compatible (because most plugins are not). So any plugin will be upscaled by the OS unless you tell Renoise that it supports HiDPI by unchecking “Plugin > Compatibility Options > Auto scale external editor”. This only applies to Windows 10. On versions prior to Windows 10, plugins that don’t support HiDPI will always appear small on HiDPI screens.
• OSX: When a plugin supports HiDPI and is running on such a display, it will just work in most cases.
• Linux: As far as we’re aware, there’s no way to automatically upscale non-HiDPI-compatible plugins. So if a plugin doesn’t support UI scaling it will appear small on HiDPI screens (the Renoise GUI will still scale properly).

Posts: 16

Participants: 15

Read full topic

@dspasic wrote:

from propellerheads to reason studios,
nothing new from my perspective worth of major version (except 1 thing > automation curves tbh)

• and you can use rack inside another daw.
  ~ so what is changed actually? possibility to load it in another daw with same old mixer emulation comp/buscomp (but now as rack apart from mixer itself) - and phaser and chorus? really? 10>11??
  https://www.propellerheads.com/

What’s your opinion guys?

Posts: 3

Participants: 2

Read full topic

@taktik wrote:

Apart from the PLAYMODE_LINEAR -> PLAYMODE_LINES change, only new functions or optional parameters got added, so most tools which worked in Renoise 3.1 should auto-upgrade and work just fine in Renoise 3.2.

Changes renoise.Application

• changed: renoise.API_VERSION = 6
• new: renoise.app():show_custom_prompt and show_custom_dialog got a new optional key_handler_options parameter to enable tracking of key release events and to suppress repeat events.

{ "send_key_repeat": true|false, -- by default true "send_key_release": true|false -- by default false }

• new: renoise.app().key_modifier_states -> [read-only, table with all modifier names and their states]
• new: renoise.app().window.mixer_view_is_detached

renoise.Song

• new: renoise.song().instruments[].phrases[]:has_line_edited_notifier/add_line_edited_notifier/remove_line_edited_notifier(func [, obj])
  
  Same as line_notifier, but the notifier only fires when the user added, changed or deleted a line with the computer keyboard.
• renamed: renoise.SampleEnvelopeModulationDevice.PLAYMODE_LINEAR to PLAYMODE_LINES
• renamed: renoise.SampleEnvelopeModulationDevice.PLAYMODE_CUBIC to PLAYMODE_CURVES
• new: renoise.song().instruments[].sample_modulation_sets[].devices[].external_editor_visible
• new: renoise.song().instruments[].sample_modulation_sets[].devices[].points[].scaling -> [number, -1.0 - 1.0]
• new: renoise.Sample.BEAT_SYNC_REPITCH, renoise.Sample.BEAT_SYNC_PERCUSSION, renoise.Sample.BEAT_SYNC_TEXTURE
• new: renoise.song().instruments[].samples[].beat_sync_mode, _observable -> [enum = BEAT_SYNC]
• new: renoise.song().patterns[]:has_line_edited_notifier/add_line_edited_notifier/remove_line_edited_notifier(func [, obj])
  
  Same as line_notifier, but the notifier only fires when the user added, changed or deleted a line with the computer or MIDI keyboard.
• renamed: renoise.PatternTrackAutomation.PLAYMODE_LINEAR to PLAYMODE_LINES
• renamed: renoise.PatternTrackAutomation.PLAYMODE_CUBIC to PLAYMODE_CURVES
• new: renoise.song().patterns[].tracks[].automation[].points[].scaling -> [number, -1.0 - 1.0]

renoise.ViewBuilder

• new: text.style ("normal" | "strong" | "disabled")

Posts: 2

Participants: 1

Read full topic

@stoiximan wrote:

Thsi song is about when you feel like life is passing you by.Lyrics are in Greek and of course everything is done in Renoise.

Posts: 1

Participants: 1

Read full topic

@Fabrice wrote:

Simply a slow-beat short track I’ve made late last night. Based on some classic chinese instruments samples.
The tittle is more about that I wanted to eat sesame peanuts candies during making this track.

Posts: 1

Participants: 1

Read full topic

@sokoban wrote:

By default under Renoise v3.1.1 there are only 5 textures for themes. And imho, only the “Jeans” one is a bit more cool but not really amazing. So I searched this forum and found somes really nice textures, for example here:

Color Themes For Renoise General Discussion Here are some color themes with new textures (to be put in the renoise/skins/textures folder): “Hippie” texture in white (keith303’s color scheme) [image] Hippie texture in my last color scheme [image] Satin finish texture (a mod of my last color scheme) [image] Leopard print texture (keith303’s color scheme) [image] Stupid pink flowers & wicker [image] hippie texture with 60’s psychadelic color scheme (Mindbeat’s XP blue color scheme) [image] There’s all in: get it here

The issue is that these textures don’t work under Renoise v3.1.1. Do you know if there are technics (or even better a tool) to convert old textures to new textures? Thanks…

Posts: 1

Participants: 1

Read full topic