Renoise Forum

Hi all, first timer here in the Renoise forums. I just dived back into Renoise after a hiatus and just realized something that always bugged me: the grey bar that follows the little orange cursor when moving up and down the pattern editor.

I’m not sure if others have felt the same, but it makes it a lot harder to create patterns. I use the static grey bars to identify quarter notes. Because of the moving grey bar (and that orange one that appears wherever I stopped my last play through), it’s hard to immediately glance and identify a particular given beat because those extra colors act as distractions.

I assume these were added to be helpful (in identifying what row your cursor is in and in identifying where you last stopped the playback). However, I would love to be able to remove them, as that would make Renoise a game changer for me.

I tried looking in the GUI preference section and couldn’t find anything of relevance. Is there a way to turn these colors off, or is this sadly a feature request that I would simply have to hope for?

1 post - 1 participant

Read full topic

Hello!

I’m trying to use instrument automation to recreate Elektron style parameter locks with vsts set up as drum synths.

Currently I’m experimenting with Zebra, I have a patch set up with the XY performance parameters mapped to the instrument automation meta device.

The problem I’m facing is that the switch between one parameter value and the next is not instant and has a “shwoopy” effect for lack of a better term. Currently I’m controlling a filter cutoff and if I have two notes that have the same cutoff value, the first one slides into it during the beginning of the note and the second one comes out the way I actually wanted.

I’ve tried putting the parameter value changes in a different column and setting the delay of each column so that the parameters should theoretically change a little bit ahead of the actual note but to no avail. If I put the parameter change a step early it changes the tail end of the preceding note.

Does anyone have any ideas on how to get around this? I’m not the biggest fan of using static samples for percussion and I’m trying to keep myself in the box. I could just use Logic’s Ultrabeat to get a similar effect but programming drums in Renoise feels a million times better.

Thanks!

1 post - 1 participant

Read full topic

Hello

Is there a way to record a sider / knob in automation without midi controller or forcing right mouse button?

Today I made some funny experiment - Line input that goes to singal follower, which controls instrument plugin on second channel and you can move knobs like filter etc. using your own voice.

Is nice, because whole channel with line input / signal follower is muted at the end and the only you can hear is how knobs are moving and changing sound in realtime (filters, eq, detune etc.).

But there is no option to save anywhere renoise sliders movements. It can be done if I’m using MIDI, but not when they move using singal follower or other internal effect. Or maybe there is some possibility to record knob/slider parameter without MIDI or right mouse button interaction?

2 posts - 2 participants

Read full topic

Hey Editors!

Is there an easy way to record internal macOS sounds?

Thank you in advance!

DS

1 post - 1 participant

Read full topic

Hi there… really love Renoise… bought a licence in 2011 and it’s the best money i’ve ever spent.

Can we expect some updates in the future besides to only bugfix updates?

Would really like to know what to expect.

Thanks, and keep up the good work Renoise dev team!

Greetz, Rob from the Netherlands

2 posts - 2 participants

Read full topic

Hello!
I normally just right click on a VST knob/slider and get a “Midi Learn” option… (for instance on a Reaktor VST)
But i cant seen to link to my M-32 Controller on any of the new Beatsurfing VSTs I purchased. Nor are they showing yup in the Instrument Properties… any suggestions??

1 post - 1 participant

Read full topic

Hello frens, I made this tool last year but hadn’t had time to release it. It’s basically a clip launcher that uses the phrases.

Making these tools takes a lot of time and effort, if you like the tool and it is within your possibilities consider donating some money, you can donate to my PayPal:

Vaya a paypal.me/Hossan212 e ingrese el importe. Como es PayPal, es fácil y seguro. ¿No tiene una cuenta de PayPal? No se preocupe.

That way you support me and support the development of this tool, in case features are required or in case there are bugs. Many thanks and enjoy
renoise.live.phrase.xrnx (28.4 KB)

1 post - 1 participant

Read full topic

This might go more towards tools but,
Extremely silly question, but would there be a possibility of making a tool that rewrites the note notation to Solfege notation (do-re-mi notation)
Would be pretty funny but kinda cool too imo
Solfège - Wikipedia.

Here’s a crappy mockup of what I mean hahaha

Realistically, it’s nonsensical, but for those in LatAm or outside of the West who have made music with Solfege notation, would this be interesting or tacky?
Feel free to delete if not allowed
Happy New year.

2 posts - 1 participant

Read full topic

I’m not one of those 432 khz people or whatever it is but is there a control somewhere in Renoise to pitch all the sound down??If not, what would be the best way to do this?No plugins or anything as i want all the transients and such relatively unaffected.

1 post - 1 participant

Read full topic

Hello and greetings,
I would like a tool that transposes all existing phrases in a project in real time, while a pattern plays/loops, according to keys pressed on an external midi keyboard.

So, a sort of global phrase transposer.

Thanks, I would be happy to pay for this.

1 post - 1 participant

Read full topic

I think, many of us feel like they are trapped in the technical aspect of music production. We know everything about EQ, Reverb, Mastering, Mixing and choosing the right plugins. But when writing music on a DAW you sometimes forget what music is all about: Creativity and emotions. That’s why I liked this conversation by successfull songwriters.

Full Songwriters Roundtable: Billie Eilish, Olivia Rodrigo, Dua Lipa, Jon Batiste & More

2 posts - 2 participants

Read full topic

is there a tool or process for transposing all instrument phrases at once?

my aim is to have a simple loop playing but to be able to transpose all the instruments in real time using a master midi keyboard so I can experiment with chord changes, etc.

is this a rtfm situation?
thanks

1 post - 1 participant

Read full topic

I do all my song mixing in the computer and have had the same cheap behringer 2 stereo, 4 mono channel mixer since the early 2000’s and am thinking about an upgrade. Basically looking for a similar 2 stereo channel mixer for hooking up my computer, monitor speakers & headphones, so I can use this old one somewhere else.

Any tips on brands with good price to quality ratio? Everyone shitting on behringer, this one still works, but perhaps there are beter options out there right now?

As my soundcard has been acting up lately, perhaps these digital mixers that also act as a soundcard are worth investigating? Anyone here have experience with the mixer/soundcard options?

Currently reading through; Best home studio mixers 2023: analogue and digital options | MusicRadar

This one has caught my eye (Allen & Heath ZEDi 10FX);

Anyone have experience with the zedi in Renoise, I wonder how recording the mixer inputs through usb works. I figure any of the channels on the mixers have digital equivalents which can be chosen in Renoise recording window, but you can only record 1 channel at a time?

1 post - 1 participant

Read full topic

Sorry to also bring this up…

when closing the Vital (Version 1.5.5) Renoise freezes completely. This happens with VST2 and VST3 version of the plugin.

Maybe there’s something in the log file that helps:

Vst3Plugs: Instantiating: /usr/lib/vst3/Vital.vst3…
Vst3Plugs: Failed to apply initial component state to controller (not critical)

Vst3Window: Creating a new main window…
Vst3Window: Setting window properties…
Vst3Window: Creating plugin parent window…
Vst3Window: Mapping the window…
Vst3Window: Attaching the plugin to the plugin parent window…
Vst3Window: Plugin window attached via _XEMBED_INFO

Vst3Window: Closing the Editor…
Vst3Window: Editor was closed

Vst3Window: Creating a new main window…
Vst3Window: Setting window properties…
Vst3Window: Creating plugin parent window…
Vst3Window: Mapping the window…
Vst3Window: Attaching the plugin to the plugin parent window…
Vst3Window: Plugin window attached via _XEMBED_INFO

Vst3Window: Closing the Editor…
Vst3Window: Editor was closed

Vst3Window: Creating a new main window…
Vst3Window: Setting window properties…
Vst3Window: Creating plugin parent window…
Vst3Window: Mapping the window…
Vst3Window: Attaching the plugin to the plugin parent window…
Vst3Window: Plugin window attached via _XEMBED_INFO

Vst3Window: Closing the Editor…
Vst3Window: Editor was closed

Vst3Window: Creating a new main window…
Vst3Window: Setting window properties…
Vst3Window: Creating plugin parent window…
Vst3Window: Mapping the window…
Vst3Window: Attaching the plugin to the plugin parent window…
Vst3Window: Plugin window attached via _XEMBED_INFO
Vst3Window: Closing the Editor…
Vst3Window: Editor was closed

Vst3Plugs: Releasing: Vital Audio: Vital…

CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: Caught signal: SIGSEGV (11) …
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Backtrace+0x4b) [0x7f809f0bb29b]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(backtrace+0x62) [0x7f809efdebf2]
CrashLog: ./renoise() [0xf808d0]
CrashLog: ./renoise() [0xc98ea3]
CrashLog: /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140) [0x7f809f426140]
CrashLog: /lib/x86_64-linux-gnu/libgcc_s.so.1(+0xf790) [0x7f809f0b9790]
CrashLog: [0xd858c63b7608f700]
CrashLog: [0x7f803b7f0540]

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

Application: Terminating…

Jack: Deactivate…
Jack: Releasing port ‘renoise:input_01_left’
Jack: Releasing port ‘renoise:input_01_right’
Jack: Releasing port ‘renoise:output_01_left’
Jack: Releasing port ‘renoise:output_01_right’
Jack: Close…
Jack: Jack was released

MIDI: Shut down: Closing all acquired MIDI devices…

MIDI-IO: Closing MIDI in device ‘Renoise MIDI In Sync’…
MIDI-IO: Closing MIDI in device ‘MPK Mini Mk II MIDI 1’…
MIDI-IO: Closing MIDI out device ‘Renoise MIDI Out Sync’…
MIDI-IO: Shutting down the MIDI sequencers…

Again this is on MX LInux Wildflower…

1 post - 1 participant

Read full topic

I just loaded HIVE VST3 in Renoise (in an empty project) and got this error

https://imgur.com/m4DLp38.png

I got the same error some days ago with CARLA.

The error log shows:

Application: Successfully loaded ‘Mutant_01.xrns’.

Vst3Plugs: Instantiating: /home/fox/.vst3/u-he/Hive.vst3…

Vst3Window: Creating a new main window…
Vst3Window: Setting window properties…
Vst3Window: Creating plugin parent window…
Vst3Window: Mapping the window…
Vst3Window: Attaching the plugin to the plugin parent window…
Vst3Window: Failed to fetch _XEMBED_INFO from plugin (not critical)
Vst3Window: Plugin requested new Windowsize 1260, 845

Vst3Window: Closing the Editor…

CrashLog: Caught signal: SIGSEGV (11) …

Vst3Plugs: Plugin ‘u-he: Hive’ crashed while calling one of its plugin view functions!

Vst3Window: Editor was closed

Warning Message: Ouch. The VST3 plugin ‘u-he: Hive (from u-he)’ crashed in event, function or class: ‘IPluginView’, Thread: ‘GUI’
Warning Message: IMPORTANT: This is a fatal error. Please save the current document under a !new! name to prevent losing important data. Renoise will silently ignore any following errors from this plug-in.
Warning Message: DO NOT IGNORE THIS ERROR; DO NOT CONTINUE USING THE PLUGIN. THIS CAN DESTROY YOUR SONG OR CAUSE OTHER RANDOM CRASHES AND PROBLEMS!
Warning Message: It’s most likely that this is a bug in the VST3 plugin, so please also report this problem to the authors of this plugin in order to get the problem fixed!

This is on MX Linux (MX-21.3_x64 Wildflower)

2 posts - 1 participant

Read full topic

This is a quick and dirty update to fix a crash (freezing UI) in Cubase 13 on Windows only.
If you are using MacOS or Linux or don’t use Cubase 13, there is no need to update.

Registered Redux users can download the update as usual from
Renoise Backstage

Demo versions are not yet available, but will follow soon.

• Windows, Cubase 13:
  when opening Redux with the expanded editor open in Redux, the Cubase 13 GUI would freeze.

1 post - 1 participant

Read full topic

Just had a crash using a vst3 version of shaperbox, last mention about it in the renoise log about it;

"Audio: Rescanning Audio devices…

WASAPI: Found input device: Analogue 1 + 2 (3- Focusrite USB Audio)
WASAPI: Found output device: Speakers (3- Focusrite USB Audio)

Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\ShaperBox 3.vst3…
Vst3Plugs: Failed to apply initial component state to controller (not critical)
Vst3Plugs: Disabled auto-suspending for plugin ‘Cableguys: ShaperBox 3’ (it reports an infinite tail)

Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\ShaperBox 3.vst3…
Vst3Plugs: Failed to apply initial component state to controller (not critical)
Vst3Plugs: Disabled auto-suspending for plugin ‘Cableguys: ShaperBox 3’ (it reports an infinite tail)
Vst3Plugs: Releasing: Cableguys: ShaperBox 3…

Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\ShaperBox 3.vst3…
Vst3Plugs: Failed to apply initial component state to controller (not critical)
Vst3Plugs: Disabled auto-suspending for plugin ‘Cableguys: ShaperBox 3’ (it reports an infinite tail)
Vst3Plugs: Releasing: Cableguys: ShaperBox 3…
"

I think I tried deleting the plugin while Renoise was in playback mode and Renoise suddenly vanished.

(Build
Hash: *redacted
Architecture: Windows Intel x86_64
Timestamp: Dec 14 2023, 15:48:34

Plugin
Name: ShaperBox
Version: 3.5
Licensed to: *redacted
Your Shapers: Time Drive Noise Filter Liquid Crush Volume Pan Width Compressor Oscilloscope
Channels: Stereo In, Stereo Out
Type: VST3
Path: C:\Program Files\Common Files\VST3\ShaperBox 3.vst3

Host
Name: Renoise
BPM: 160
Sample rate: 48000
Path: D:\PROGRAM FILES~SOFTWARE\Renoise 3.4.3\Renoise.exe

System
OS name: Windows 10
Region: US
Memory: 23.934 GB (total)
Up Time: 0.156 days
Time: 2024-01-03T03:19:48.031+01:00

CPU
Model: Intel(R) Core™ i7-4790 CPU @ 3.60GHz
Vendor: GenuineIntel
Cores: 4
Threads: 8
Speed: 3.591 GHz (current)

UI
Scale: 125%
Host scale: 100%
OpenGL: Disabled
Screen 1: 3840*1080 (current)
Screen 1 user area: 0 0 3840 1080
Editor area: 1270 145 1300 793
)

1 post - 1 participant

Read full topic

Hi! I’ve been writing a video game soundtrack and doing its sound design for a few years. Initially I was writing rock music in Cubase for it, but at some fateful point I revisited my tracker roots by taking a serious dive into Renoise. A friend remarked how much he preferred the direction things were going with a tracker and it’s been no looking back since! I loved the days of Scream Tracker and Impulse Tracker, but really hadn’t enjoyed anything since until Renoise! Totally worth the money and a joy…most of the time!

I’m using a few VST synths, a few samples, and BFD3 for most drums in the music. The sound effects have been all over the board. I went on quite a few sampling trips to have original material to mangle… birds, farm animals, tractors, and tractors, and tractors, tools, metal shops, old house sounds like door latches, and so on! With the sound effects, I’ve far preferred the approach in Renoise versus traditional DAWs. High-tempo tracker sequencing to all the sampler modulation options have made it a grand ole time!

The game itself, Blister Blight, is a 2D action-platformer, with a retro vibe and nods to Megaman and Metroidvania genres. …plenty of its own unique game-play, some RPG elements, and humor as well! It’s been a load of fun seeing all aspects morph and develop over time.

We’re at the point in the game’s development where we are starting a Kickstarter campaign to fund its completion. Our main goal is to provide the art team and lead developer the ability to work on it full-time. We aim to deliver it onto the Steam and Nintendo Switch platforms. I’m very excited about what we already have to show and am very confident in the team continuing to crank out amazing stuff. I would love for you to take a look at how far we’ve come and be on the look-out for the upcoming Kickstarter! Come discover plenty of story, art, game-play clips, and maybe even my music at: https://blisterblight.com/kickstarter/

• viking camel / jermookie / jeremy simon
  www.vikingcamel.com

1 post - 1 participant

Read full topic

Here you go. Now, just perfect it. I did all the work for you. Not quite perfect, though, but close. Thanks for sending your Doofer; it really turned my morning around. I thought everyone was my enemy. I also didn’t sleep; I kept working on a song all night. I removed all the needless Gainer values, fixed a stupid mistake I made in messing with the sync to lines per beat, added two more Stereo Expanders, and added an extra Gainer to level off the volume.
Fly Around (YardTosho Final v3).xrnt (26.8 KB)

3 posts - 2 participants

Read full topic

Seems basic but I can’t for the life of me work out how to set this up.

I’m after the behaviour as found on the Roland classics eg Juno 60 or SH-101 (or pretty much any analogue/virtual analog tbh) in that there’s a control for the filter cutoff point and a separate parameter that controls the amount of envelope added without changing the base cutoff point.

Obviously we have the Input paramater on our filter modulation lane but separating out the two is eluding me.

Any ideas?

2 posts - 2 participants

Read full topic