Feed aggregator

In Renoise

The Khou Xian. An ancient musical instrument from China. #khouxian #kouxian #jawharp #mouthharp

2 posts - 2 participants

Read full topic

https://www.youtube.com/@Dex_of_Ko-Ko/

1 post - 1 participant

Read full topic

Movie Recommendations – 5 Underappreciated Favourites

The holidays are coming up, you’ve already rewatched your favourites and nothing new looks any good. So here’s five lesser known movies all completely different from each other, covering a wide variety of genres, and hopefully you’ll find something that sparks your interest. If time investment is an issue don’t worry cos, unlike a lot of films these days, they’re all only 90 mins long.

1 post - 1 participant

Read full topic

I tried loading a new song and suddenly Renoise crashed and saved a back-up, from the log;

"Player: Constructing…
Player: Creating slave threads…
Player: 8 threads enabled. 8 CPUs are available.
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Vst3Plugs: Releasing: DOTEC-AUDIO: DeeDoubler…

VstPlugs: Releasing D:\PROGRAM FILES~SOFTWARE~FREEWARE VST(I)~FREEWARE64\GClip.dll…
VstPlugs: D:\PROGRAM FILES~SOFTWARE~FREEWARE VST(I)~FREEWARE64\GClip.dll was released

CrashLog: Handling Exception! Code : C0000005
CrashLog: 0000000140698EF6: l9_ippsLn_32f_A21 +2CB406
CrashLog: 0000000140622DEB: l9_ippsLn_32f_A21 +2552FB
CrashLog: 0000000140627FC4: l9_ippsLn_32f_A21 +25A4D4
CrashLog: 0000000140B9DD44: l9_ippsLn_32f_A21 +7D0254
CrashLog: 00000001403E9608: l9_ippsLn_32f_A21 +1BB18
CrashLog: 0000000140635BA8: l9_ippsLn_32f_A21 +2680B8
CrashLog: 0000000140634F92: l9_ippsLn_32f_A21 +2674A2
CrashLog: 0000000140635148: l9_ippsLn_32f_A21 +267658
CrashLog: 0000000140B774B4: l9_ippsLn_32f_A21 +7A99C4
CrashLog: 00000001408942B8: l9_ippsLn_32f_A21 +4C67C8
CrashLog: 0000000140C9E73B: l9_ippsLn_32f_A21 +8D0C4B
CrashLog: 00000001409D05B8: l9_ippsLn_32f_A21 +602AC8
CrashLog: 0000000140B67687: l9_ippsLn_32f_A21 +799B97
CrashLog: 0000000140B678E8: l9_ippsLn_32f_A21 +799DF8
CrashLog: 00000001403E9608: l9_ippsLn_32f_A21 +1BB18
CrashLog: 0000000140635BA8: l9_ippsLn_32f_A21 +2680B8
CrashLog: 0000000140634F92: l9_ippsLn_32f_A21 +2674A2
CrashLog: 0000000140635148: l9_ippsLn_32f_A21 +267658
CrashLog: 0000000140B774B4: l9_ippsLn_32f_A21 +7A99C4
CrashLog: 0000000140B2D618: l9_ippsLn_32f_A21 +75FB28
CrashLog: 0000000140B2DB61: l9_ippsLn_32f_A21 +760071
CrashLog: 00000001410B34E4: l9_ippsLn_32f_A21 +CE59F4
CrashLog: 0000000140C7757F: l9_ippsLn_32f_A21 +8A9A8F
CrashLog: 000000014056A2FB: l9_ippsLn_32f_A21 +19C80B
CrashLog: 00000001403F7809: l9_ippsLn_32f_A21 +29D19
CrashLog: 0000000140C02A49: l9_ippsLn_32f_A21 +834F59
CrashLog: 00000001403ECC40: l9_ippsLn_32f_A21 +1F150
CrashLog: 000000014071CF71: l9_ippsLn_32f_A21 +34F481
CrashLog: 000000014071ED08: l9_ippsLn_32f_A21 +351218
CrashLog: 00000001406C3000: l9_ippsLn_32f_A21 +2F5510
CrashLog: 00000001406A78FC: l9_ippsLn_32f_A21 +2D9E0C
CrashLog: 000000014072141A: l9_ippsLn_32f_A21 +35392A
CrashLog: 000000014071FF59: l9_ippsLn_32f_A21 +352469
CrashLog: 0000000140762C38: l9_ippsLn_32f_A21 +395148
CrashLog: 000000014071AB16: l9_ippsLn_32f_A21 +34D026
CrashLog: 000000014071FD76: l9_ippsLn_32f_A21 +352286
CrashLog: 00000001403FD7A3: l9_ippsLn_32f_A21 +2FCB3
CrashLog: 00000001403F88A0: l9_ippsLn_32f_A21 +2ADB0
CrashLog: 00000001403FE076: l9_ippsLn_32f_A21 +30586
CrashLog: 0000000140DE7893: l9_ippsLn_32f_A21 +A19DA3
CrashLog: 00007FFC83377344: BaseThreadInitThunk +00014

Application: Caught an unhandled fatal exception (Thread: GUI)!
Application: Saving a backup…

Error Message: A fatal error or crash occurred (unhandled exception in thread: GUI).
Error Message: A backup of the current document was saved at
Error Message: ‘C:\Users\pluge\AppData\Roaming\Renoise\V3.4.3\CrashBackups\Untitled_12_21_2023__9_46_crash.xrns’…
Error Message: This either happened because of a bug in Renoise, or because of a bug in one of its loaded components (plugins). Please contact bug@renoise.com and report this problem, so that it can be fixed.
Error Message: Note: It’s very important that we know exactly what has happened (what you were doing before this message popped up), or the problem cannot be replicated/analyzed. Please include a description of what you were doing and which components were being used…

Application: Terminating…

MIDI: Shut down: Closing all acquired MIDI devices…
MIDI: Shutting down MIDI server…
MIDI: Shutting down DirectMusic…

"

Windows 10, latest Renoise running the wasabi driver.

2 posts - 1 participant

Read full topic

Currently, when a pattern that is right after a pattern section row is duplicated, Renoise not only creates a duplicate of the pattern but also the pattern section row above it.

Duplicating a block of patterns also does this but only if the top pattern in the block is right under a pattern section row.

On the other hand, duplicating a pattern that is under a pattern section row, but it’s not right after it, duplicates the pattern without duplicating the pattern section row.

The duplication of sections like this is really confusing. If I duplicate a block of patterns and see a bunch of sections duplicated as well, it makes me have to review what I did because seeing all those new sections makes it look like nothing happened. It’s hard to explain.

That said, the ideal situation is to allow sections to be selectable rows. If a user wants copy/paste or duplicate a section row, they should be allowed to do so by selecting it and performing the function, instead of Renoise deciding when to do so.

1 post - 1 participant

Read full topic

Hi, longtime Renoise user here, looking for help with a pretty simple question.

I’m looking to build a small Raspberry Pi machine, solely to run Renoise as an external sequencer to send program changes to my Keystep Pro. This would be much cheaper and easier for me than purchasing and learning how to use another external sequencer. It needs to be small enough to fit on my synth board, so my laptop won’t work for this, and I’m planning to purchase a very small touchscreen monitor for the Raspberry Pi.

My (latest) concern is screen resolution. The devices that seem to best fit my needs have pretty low resolution, 800x480. Elsewhere on the Renoise website, the screen resolution requirements are listed for Linux as: “min 1024x768 pixels”.

Am I correct in understanding that Renoise will not even boot on a Linux device with resolution lower than 1024x768?

Or, will it boot up and run, but I will be unable to see the full GUI at any given time? Just being able to boot and run would meet my needs as I will have no need to see the entire GUI on the Raspberry Pi.

Thanks for taking the time to read this, I appreciate any help with this or with other issues I could run into with this project. Pete

1 post - 1 participant

Read full topic

Hitori Tori - Live Set Dec 2023

1 post - 1 participant

Read full topic

Is it possible to use an effect like Yxx to trigger a note, but instead of it being probabilistic it definitely triggers the note every x number of pattern repeats?

For example, say I have a pattern that’s 10 steps in length and I put a crash cymbal sample at the top of the pattern. How can I get it to trigger the sample on the first iteration, and then wait 3 more loops before it triggers that note again?

Thanks in advance!

1 post - 1 participant

Read full topic

Has anybody tried to make music interactively / live with a MIDI controller that supports the matrix and macro knobs (not just a MIDI keyboard)? The Oxi One Sequencer looks very promissing. Any ideas or experiences?

1 post - 1 participant

Read full topic

very specific, very strange issue, that i’ve experienced across two different computers now, on two or more different versions of renoise.

i have two displays, one computer monitor (144hz) and then a hdmi going to a TV (120hz).

every single time i turn my monitor off and on again (like at night > in the morning), if i have renoise open, the renoise window will be frozen when the monitor is turned back on.

i can still use it though. if i press space, the loaded song will start playing, if i click ctrl+s, the song will save, if i click the X in the corner, it’ll close. it’s just that it’s frozen in place. when the song is playing, nothing is moving. when i click ctrl+s to save, i have to follow it by pressing “Y” or “N” because i know there’s a prompt asking me if i want to overwrite, i just can’t see the actual prompt, because the window is frozen.

i know it has something to do with the displays, because if i unplug the TV completely, this doesn’t happen.

i’ve had SOME luck with setting both the monitor and TV to 60hz. that worked on my old computer, but it wouldn’t work with 120hz or anything above.

i’m thinking i can’t possibly be the only one who’ve experienced this?

1 post - 1 participant

Read full topic

Doesn’t seem that hard and what better song to have forcefully played everywhere if it’s good enough. I’m giving myself 5 days.

1 post - 1 participant

Read full topic

Backrooms: The Complex - A Sense Of (No) Place

The Backrooms taps into a definite, though hard to describe intuition about liminal spaces, creating an unnerving feeling. The Complex: Found Footage is a short free game that puts you into those spaces and also reminds me of something specific in real life.

2 posts - 2 participants

Read full topic

Edit page hesitates while scrolling? Any fixes

1 post - 1 participant

Read full topic

I use Renoise for live performances. Would love a way to set the amount of each pattern to loop before progressing to the next. Even better would be to have a matrix of patterns loops with a set amount and be able to bounce around based on a probability.

Any way to do this currently?

1 post - 1 participant

Read full topic

Pretty self-explanatory: in Renoise’s “About…” window, add a simple line right below “Renoise 64-bit - V…”, something like “Renoise Tools API V6.1…”, to give a user quick information about what the current API version is.

It would make it easier for people who need that information quickly, and would help avoid the need to do a search online, or to open up a bunch manifest.xml files. At the very least, it would make the “About…” window look more complete.

1 post - 1 participant

Read full topic

The timing of MIDI input in Renoise is not stable in the following situation.
It is stable on REAPER.

What should I do?

Renoise preferences MIDI:

Renoise preferences AUDIO:

REAPER preferences Device:

REAPER preferences MIDI Device:

Environment:

• OS: Arch Linux x86_64
• Kernel: 6.6.3-arch1-1
• WM: sway
• pipewire 1:1.0.0-1
• pipewire-jack 1:1.0.0-1

config:

$ grep -v \# ~/.config/pipewire/jack.conf.d/override.conf jack.properties = { node.force-quantum = 144 } $ $ cpupower frequency-info analyzing CPU 5: driver: intel_pstate CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 4.30 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 4.30 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 2.97 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes $

Screencast with audio:

https://0x0.st/HYKy.mp4

2 posts - 1 participant

Read full topic

Hi, i recently started to use midi in Renoise.
Perviously i only did that for live played tracks, using Studio One…

Now, i created 4 tracks “live” in Renoise with a Virus TI as midi.
When i had 6 instruments, midi, my cpu meter is at constant 25% just for one instrument.
and then when i use some vst in cooperation with the midi, it goes overburn to 90% cpu

this was previously not an issue.

I use a Behringer 404 UMC HD ASIO soundcard, in ASIO mode

The issue is that 25% cpu for midi only is fine, but when VST are introduced, the audio engine is completely wiped out. so it must have something to do with the midi coding.

?

1 post - 1 participant

Read full topic

Operating system: Macos 13.5
Renoise Version: 3.4.3

Problem: In the pattern sequencer you can play or schedule the currently focused pattern with shift+space or cmd+space. These commands are listed in the keyboard shortcut preferences but rebinding them does not work - the default binds persist. This is inconvenient in macos since cmd+space brings up spotlight.

Steps to reproduce:

1. Open renoise
2. Press cmd+, to open preferences
3. Select “keys”
4. Rebind the keyboard shortcut for Pattern Sequencer → Transport → Play from edited sequence to cmd+return
5. Close preferences
6. Open the pattern sequence matrix
7. Press cmd+return

Expected result: The track should start playing
Actual result: Nothing happens

You can work around this issue by disabling the global macos shortcut for spotlight and using the default cmd+space key bind.

Thank you for reading, and for building renoise.

1 post - 1 participant

Read full topic

I am starting to reuse Renoise after a long time and have several plugins to use, instruments and effects, many of which can be installed as VST2 or as VST3.

I understand from quickly browsing the forum that VST3s are more prone to causing problems with Renoise. Is this true?
Do you recommend that I use the VST2s? Or is it really indifferent for Renoise?
Thank you.

2 posts - 2 participants

Read full topic

I found a very old thread asking for something similar but maybe some new feature has been added in the meantime that I can’t find.

I have this need: I have several of my old musics in mod and xrns format written long ago and I would like to re-arrange them, and I have a need to search instrument by instrument for the points where they are used within the song (sometimes there are instruments that are only used at one point).

I haven’t found a quick way to do this kind of search; I have to scroll through pattern by pattaern and track by track of the whole song to find a particular instrument.

I had assumed that in Renoise there was some sort of search within the song but it seems not.

Do you have any suggestions?

1 post - 1 participant

Read full topic