Feed aggregator

Hey folks,
having fun with formula’s, but i ran into a problem:
as i am playing with time… Sin() is my friend… NUMLINES, LINE, etc all help with this
however… What if I want to know the total amount of lines in a song… is there some
constant i could grab for that?

1 post - 1 participant

Read full topic

Hi all,
i’m thinking of getting Pi (model 4 - or other) soon - to be able to use it solely with Renoise. Can anyone, who owns any models, make a comparison of projects:

1. Open project on PC/laptop (mac/win/linux) - document resource usage
2. Open same project on Pi (the more models - the better) with same parameters(latency, sample rate, etc) document resource usage

video would be perfect - or screenshots of resource-intensive parts, and short summary in general. Since we got support for ARM in the latest update ► Renoise 3.4.0 & Redux 1.3.0 released it would be great to have general overview of how Renoise behaves.

any additional information is very welcome (which audio interfaces & midi instruments are working, any major flaws of this approach etc)
Thanks!

1 post - 1 participant

Read full topic

When in full screen, the notch obscures whatever goes in the middle of the upper part of the gui - in my case it’s octave setting. Would be great if Renoise could be notch-aware and move items to the sides, or even if a simple checkbox to avoid that area be available.

1 post - 1 participant

Read full topic

So because this whole world of M1 native problems, some plugins behaving better via au native bridge process some better via renoise sandbox, plus discontinuity of VST2 plugins, it would be nice to have migration tool between those plugins formats AU VST2 and VST3 [and any other for other systems].I’m aware that some formats raport different parameters sometimes, but still i think it would be usefull migration tool. Maybe there is ? but i didnt find one.
How i imagine it would work.
Well you would

• select source device from available in project
• you would select targeted format
• plugin compare all plugins parameters name by name and map one parameter to target parameter if same name
• if some parameters cant be mapped automatically, show list of those parameters in left column, and on right select with all parameters of targeted format, and “skip this” option

Click migrate and it converts, or create copy of this instrument/device, so you can test manually test if migration was done how it should.

1 post - 1 participant

Read full topic

As in title, when Output Thermal is bridged, gui doesn’t show up, its white/blank

• It was working in 3.3,
• it is working if starting Renoise as Rosetta2 mode in 3.4
• it is showing when using AU version

1 post - 1 participant

Read full topic

Hi,

I am a new user here, and need som help.

When I am copying a phrase to the main editor and play the loop, it does not play/trigger correctly. I have typed in the correct 00/instrument in the column. I have attached the xrns

https://app.box.com/s/u43oweyphh5yfr2cblprh19is3hbepkd

1 post - 1 participant

Read full topic

I’m on an Apple MacBook Pro M1 Max and after launching the latest 3.4 Renoise and opening one of my tracks I was greeted with an error: “The following plugins could not be found or failed to open: AU: Native Instruments: FM8”

I loaded the 3.3.2 version of Renoise to double check if the plugin was at fault and loading the same track was fine. Loading version 3.4 again and the same track had the error mentioned.

On a clean new song the following plugins are loading but with no audio:
Absynth 5, FM8, Super8

The following plugins DO work:
Battery 4, Kontakt, Massive X

Massive (standard not X) plays but changing any knobs in the plugin GUI while playing causes a massive audio pop.

Maybe this is a known set of incompatibilities at their end but seeing as the plugins all worked fine on the previous release before the official ARM version I’m also letting you know here.

1 post - 1 participant

Read full topic

https://www.youtube.com/embed/hYWRhJJpxYo

xrns: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free

1 post - 1 participant

Read full topic

When NI effects Flair / Choir / Phasis vst is bridged to m1, gui knobs are unresponsive, can’t move and change parameters smoothly. If you change values from within Renoise ui, changes are done corretly and ui is updated choppier but smoother vs updates from within plugin gui.

Other Ni plugins doesnt seem to have this problem.

I understand problems with bridging, And NI are the worst with migrating to m1 now, but i felt that its important to raport

1 post - 1 participant

Read full topic

As in topic, soundpaint vst [its free download with piano samples] after upgrade to 3.4 started crashing. It didnt happen in earlier version. New Crash preventing system prevent renoise from crashing, but its happening and show to not use this plugin. It happened two three times, but not always. I am playing notes with gui open and switching between presets, but for now i didnt find way to crash it every time.

M1 Big Sur.

1 post - 1 participant

Read full topic

Since updating to 3.4, Renoise loads in a tiny window on first loading it up, every single time; I have to manually click to expand to full size after every load…quite irritating. Anybody else? I’m on iMac Catalina.

note: even after expanding, resetting the size of each area, saving that to a snapshot and saving the session as the template, on next launch it ignores all of this and loads in a tiny window again, and with the sizes of everything I set ignored.

11 posts - 5 participants

Read full topic

Renoise 3.4
macOS 12.3 Monterey
Focusrite Scarlett 2i2 I/O

I’ve just installed Renoise 3.4 and am just working through the Building a Beat tutorial.

I’ve noticed that if I select a C4 on my MIDI keyboard, it inserts the note C4 correctly in the pattern editor, but also seems to capture extra info, presumable related to velocity, which I don’t want at this stage of the tutorial.

I figured that if I used the computer keyboard, this wouldn’t t be a problem. The only issue now is that pressing the Z key on my Mac Mini M1 keyboard is generating C3 rather than C4.

UPDATE: I’ve just sussed it thanks to this little gizmo…

UPDATE2: A couple of hours in and Renoise is pretty cool, isn’t it?

1 post - 1 participant

Read full topic

With the new 3.4 update, when I change the “voices” input on the U-He Report-5 synth, it doesn’t update in display. E.g. you can choose from 1 to 8 voices, default is 8. If I click the 8 and select 5, the selection menu closes, but it still says 8.

This does not happen in my other DAWs (Ableton, Reason) and did not happen with Renoise until installing 3.4 today… I wonder what’s up?

1 post - 1 participant

Read full topic

• MacOS M1 ARM Support
• Raspberry PI ARM Support
• MacOS Metal Rendering
• Windows WASAPI Audio
• Ableton Link Support

See full changelog and announcement at the Renoise Forum

You can grab a free demo version from the download page. If you are a registered user, download your personalized copy from the backstage server.

Hello Renoise! I hope you’re all doing well.

I’ve started working with GPU Audio - we just dropped an Early-Access plugin and Community (DISCORD) and would love for you to try it.

The plugin is a fun, simple convolution reverb that you can load your own IRs into. With GPU Audio, there is no added latency as a consequence of adding more instances so have fun and stress test your DAW if you’d like! I was able to run 128 stereo instances within 1ms latency on Reaper, last night.

Download it here for free! We will add new IR zips as we go: https://bit.ly/3KWRjS1

Please check the Read-Me as this is a test plugin, with purposeful limitations, and is currently only compatible on Windows PC with an NVIDIA discreet GPU. We are testing across most major DAWs Roadmap ahead includes, AU, Mac, AMD card support and much more.

GPU Audio is a full tech stack we designed to effectively parallelize audio processing across thousands of GPU cores, by offloading DSP from cpu to the gpu, and returning back within 1ms latency. If you’re interested in the novel innovation, we are speaking on March 24th at NVIDIA GTC

The plugin works is basically an open-benchmarking test for us as we prepare to launch an entire suite of products in 2 months We are also forming partnerships with great plugin makers to power up others’ future instruments and have lots of news coming.

Drop in and I look forward to meeting you! You can watch Sonic State dream about GPU Audio here: Sonic TALK 659 - Loop Monk, MPE, GPU + Ken Lewis - YouTube

Let me know if you have any questions!

Chris

1 post - 1 participant

Read full topic

Registered Renoise and Redux users can download the update, as usual, from:
Renoise Backstage.

Demo versions will be published later today or tomorrow.

ARM support for OSX (on Apple Silicon) and Linux (Raspberry Pi), MacOS Metal rendering, Windows WASAPI driver support, Ableton Link support (all platforms).

• OSX: ARM64 builds (shipped as Intel 64bit/ARM64 Universal binary) with the ability to load intel plugins via plugin bridge and Rosetta in Apple M1 based systems

• OSX: New macOS Metal based GUI rendering to improve UI speed, especially on Retina Displays and with some color profiles

• Linux: 32 & 64bit ARM builds (ARMhf & ARM64), optimized for Raspberry PI 3/4

• Windows: WASAPI Audio device support (with “exclusive mode” support like ASIO - and “shared mode” support like DirectSound)

• Ableton Link support

• Windows: Improved MIDI output timing, especially when using DirectSound
• Windows: Added an option to ignore ASIO reset requests (necessary workaround for some buggy drivers)
• Windows: Boost MIDI input thread’s priority to improve MIDI input playback/recording timing
• Linux: Added support for shared memory X11 images to improve GUI speed on some systems
• Linux: Allow using the “default” ALSA system device (e.g. to use pulse audio)
• Linux: Don’t limit possible ALSA audio buffers sizes to pow2 values
• OSX: Added “Audio Workgroup” support on OSX to minimize dropouts with very small audio buffer sizes
• OSX: Explicitly ask for user permission to use the microphone when using CoreAudio input devices
  OSX: In Device not picking up audio from microphone
• Fixed various timing issues with MIDI generator plugins
  Unstable timing (jitter) of VSTi MIDI routed events
• Compensate UI scaling when mouse-dragging controls with the GUI → “Mouse warping” option enabled
• Added new option to compensate MIDI input playback (not recording) jitter (at the cost of introducing a bit of latency) → See Preferences → MIDI → “Fix received MIDI event jitter”
• When recording MIDI events, always compensate/fix the time it took to receive MIDI events to improve timing, also when the “Adjust recording latency (record what you hear)” option is disabled
  Midi recording precision dependent on latency
• Allow specifying multiple “secondary” VST paths on Windows and OSX
• Try to avoid crashes when VST3 Plugin GUIs crash while opening/closing down their GUIs
• New Renoise Color Themes from spktkpkt and NPC1
• New DemoSong from keith303: Burst your Bubble

• OSX: fixed freeze when opening Redux VST GUI in Mixbus32C
• OSX: mark AU plugin as “sandboxSafe”
• Linux: Fixed keyboard focus issues when reopening the Redux GUI
• Linux: Fixed editor resizing issues in yabridge
• Fixed possible lags in hosts with many Redux instances
  Multiple Redux Instances Introduce Playback Lag (Logic X and Reaper)
• Don’t change the host’s mouse cursor when the plugin UI is closed
• Fixed a crash when shutting down Redux while a sample is previewed in the sample editor
  Redux crashes when deleting the Redux instance while an instrument is previewed

• Windows: Fixed possible wrong window size when maximizing Renoise on secondary monitors
• OSX: Fixed uncentered panels (open file/directory dialogs) on some version of OSX
• Linux: stop logging ALSA sequencer errors at some point to avoid flooding the log with errors
  Hard drive filled with log file
• Don’t remove unused tracks with the “Delete unused Tracks” command which have linked bypassed send tracks
  Delete Unused Tracks Bug with Muted Send Tracks
• Fixed wrong “Surround” maximum in track mixer devices
  Width & Surround Parameters Should Be Identical
• Fixed wrong default highlight color state in track mixer panels
  Loading a Renoise theme resets track colors
• Fixed crash when trying to render a plugin to instrument with routed MIDI outputs
• Fixed smoothed (fade-in) first transient in beatsynced samples with Rubberband timestretch
• Fixed that swapped plugin instruments in instrument box may temporarily silence them:
  Hard drive filled with log file
• Fixed possible wrong sample position labeling in sample editor with very large samples
  Loop/Slice Markers In Wrong Position When Zooming On Long Sample
• Some stereo VST2 plugins have been falsely treated as mono plugins with a mono side-chain input:
  Excalibur VST2 is mono in Renoise 3.3 & keyboard assignment issues
• Some stereo VST2 plugin’s MIDI output routing didn’t work:
  MicroTonic MIDI Routing not working
• Fixed a crash when receiving aftertouch events from a MIDI generator VST/AU plugin
• Fixed possible crackles when automating bypass parameter of send devices
• Skip processing bypassed side chain devices, when no delayed samples are present
  Bypassed sidechain send won't disable sidechain input
• Apply BPM/LPB/TPL pattern automation also when an envelope in “Point” mode is present:
  BPM/LPB/TPL Automation Overwrites Effect Commands In Pattern
• Treat envelope automation in point modes like pattern effects and fixed pattern follow for them
• Fixed missing updates of “parameter is automated” highlights in the automation list
  Parameter automation status isn't updated when changing pattern
• Ensure idle for tools is called frequently on Windows and Linux even on high GUI loads
• Fixed a few small envelope device GUI issues
  Envelope Device GUI Issues
• Bring existing song comments/options dialog to front when opening them via the menu/keyboard shortcuts
• Fixed broken playback of real-time played MIDI poly-aftertouch events
  Poly-Aftertouch implementation is flawed
• Fixed missing applied initial program changes when importing MIDI files
• Fixed possible crash in MIDI importer with very long MIDI files
• Fixed a crash when entering a “0” value in filter HZ parameters
• Fixed wrong reported velocity values in Velocity Tracker for notes in phrases
  Velocity Tracker Responds Incorrectly To Phrase Velocity Changes
• Log why exactly a plugin can’t be opened when it was created for a different architecture which the plugin bridge doesn’t support
• Fixed possible missing update of track popup in instrument FX chains:
  Sampler Effects FX Chain: Routing tracks not update!
• Fixed a crash when releasing a dragged slice marker after/while a sample gets deleted

5 posts - 4 participants

Read full topic

On Windows there’s now a new WASAPI audio driver mode in Renoise’s audio prefs, which allows, compared to DirectSound, lower latencies and more stable audio processing. It’s basically a great alternative for those who don’t have proper ASIO drivers for their inbuilt soundcard or when the provided “pro” ASIO drivers suck.

• If you’ve got a proper ASIO driver for your soundcard, always use this one.

• Then, try WASAPI in non-exclusive mode first. This basically works similar to DirectSound but offers better performance and latency as DirectSound.

• If you don’t need to use your soundcard for other apps while running Renoise, try WASAPI in exclusive mode. It will allow to use even lower latencies, but obviously will block sounds output from all other apps.

• If WASAPI doesn’t work for you, use DirectSound. It’s the most compatible and last option, which should simply work everywhere. This also should be the default in Renoise on Windows.

WASAPI tends to have problems synchronizing capture and playback devices - this is not only a problem in Renoise, but a general one. With a line-in or microphone device enabled, the required latency very likely is higher than when using a playback device only. This unfortunately is also true in exclusive modes and especially when the devices are from different drivers.

So if you don’t need your line-in or microphone device, don’t enable it with WASAPI.

2 posts - 1 participant

Read full topic

As some of you did not like my last lo-fi-release I just sat down again and deeply concentrated on creating a lofi-tune with much better sound than the disastrous last one.

I’ve always wanted to create this “concentration-music” everyone is deeply learning too. Maybe this is good enough?

1 post - 1 participant

Read full topic

Last night I had a dream about putting a piece of video into one of the instrument slots and cutting it up with the tracker interface the same way I would glitch and mangle a sample. The resulting video was like a music video or the visuals they show in clubs and concerts. This got me thinking what a “Renoise for Video” could look like. Video synthesizers could generate interesting color patterns to modulate. We could string out video filters the way we build signal chains, with LFOs and automation creating rhythmic effects. All of this creative power with a tracker workflow! Wouldn’t that be amazing? What a dream…

5 posts - 4 participants

Read full topic

Check it!

https://www.youtube.com/embed/bcRHNduz7xo

Stay safe!

1 post - 1 participant

Read full topic