Feed aggregator

MIDI Universal Controller Download “Demo Version” & “Image Capture Album”: Download the Demo Version here

• MIDI Universal Controller v1.0.245 Demo (May 2021, First Release).

How to start installing?

1. Download the ZIP file. Please always download & use the latest version published.
2. Inside is the tool in XRNX format. Install it like any other tool.
3. The access link is at “Renoise: Tools / ~ MIDI Universal Controller…”

Image Capture Album. A first look!

You can see much of the content of the tool by looking at the captured images. You will see that there is a lot of content there. Many things will be familiar to you! Download the album and take a look!

• MIDI Universal Controller - Image Capture Album

MIDI Universal Controller. Get the full version!

MUC is available as a Full Version, which requires a personalized user license, valued at € 20 (euros). If you are interested, please, contact the author «ulneiz» to get your personalized user license (send me a PM for more information).

Please, seriously consider supporting the development for this type of projects buying a license. Keep in mind that it takes a lot of time, effort and money to build!!!
…ulneiz

I also want to give a big thank you to all the users who are supporting the PRE tool and SMC tool. Thanks to this support, it is possible to continue developing complex tools such as MUC.

Enjoy it!

Concept of the MUC.

The MIDI Universal Controller or MUC allows you to control practically everything Renoise from the MIDI input, managing to unify the control magnificently.

Represented as a single dynamic floating window, the MUC works as a MIDI bridge between your physical MIDI devices & Renoise, controlling all operations. It offers access to a multitude of functions (navigation, transport, song characteristics, or instrument, sample, phrases, MIDI properties…), as well as unified control of all parameters (both for effects, modulation or VST/VSTi devices), editing features, automation, & other unique functions & controls not available from Renoise.

Use absolutely all of your MIDI routing for all your song projects without exception!

The MUC window. Controls distribution.

The main window is divided into 4 parts & will show a width & height determined according to the selected control area (List 1). To position it, use a strategic corner of your image monitor, or place it on a secondary image monitor. The window layout is as follows:

1. Top bar for internal navigation & selection of main elements.
2. Main device panel. Displays a multitude of sliders to control specific parameters or properties.
3. Bottom bar for load or remove different elements.
4. General button bar for transport & navigation.

How to start? Steps to MIDI Map.

As a general rule, you only need to do these steps once. The goal is to save the entire MIDI mapping somewhere. This way it will be possible to use it in a multitude of projects. Start a new project & immediately get to control the knobs, faders & buttons of your physical MIDI devices. The steps to map & save the mapping:

1. Go to “Renoise: Edit/Preferences…/MIDI” & make sure you have your up to 4 MIDI devices enabled.
2. Go to “Renoise: Tools/~MIDI Universal Controller…”. This operation will display the floating window of the MUC.
3. Go to “Renoise” & press “MIDI MAP” button (top right), the “MIDI Mapping” window will appear… Keep “Learn Mode” on.
4. Go back to the MUC window & go through each MIDI mapping by first clicking on each virtual control:
   ▸ Use the physical knobs, faders, or buttons on your MIDI controllers to map at least all of the most important controls of the tool window.
   ▸ In general, use the “absolute map mode” of the limited rotary knobs or faders for the drop-down lists.
   ▸ It is recommended to use the “relative map mode” of the 360° rotary knobs (if available) for all sliders.
   ▸ For most button or switch type controls, be sure to use physical buttons that output two MIDI push-&-release signals.
   ▸ Map all your physical controls strategically. Remember that you will need to do a short mental memorization exercise to associate the physical control with its corresponding virtual control.
5. Go to “Renoise: Song/Midi Mappings Info…”. Read & check that you have the correct mapping of all your controls.
6. Save all your MIDI mapping somewhere. You can do it in 3 ways:
   ▸ Save it inside an XRNM file. Go to “MUC: show options panel: MIDI Map & OSC/MIDI Mapping Files”.
   ▸ Save it in the general “Template Song”, valid to start any project. Go to “Renoise: File/Save As Template Song”.
   ▸ Save it in a existing “Song”, in the middle of the project. Go to “Renoise: File/Save Song As…”.

Once you have saved the MIDI mapping, you can work with all your song projects. MUC allows you to always use the same mapping universally, regardless of what items are added or removed in each song project.

On the other hand, MUC offers a bidirectional MIDI routing alternative. Access “MUC: Options Panel/MIDI & SysEx In ➜ Out”. This is especially useful for communicating with the MIDI Controller, allowing you to send raw MIDI messages or SysEx messages compatible with the MIDI controller in a custom way.

Peculiarities of the MUC.

This advanced control tool offers exclusive functions & some unique ways of handling. Thanks to its design, it is possible to control much more than Renoise via MIDI input, using far fewer physical controls. Some peculiarities:

1. With the window in “OFF” mode it is possible to change the Custom List 1, the Custom List 5, change MIDI mapping or access to Options Panel.
2. The List 1 (Area Control) and List 5 (Edit Operations) are customizable, with 3 presets (A-B-C) to choose from.
3. The automation switch (top bar) allows you to switch between the two automation modes with a simple click or toggle recording on/off, by press & hold.
4. MUC can display up to 1000 parameter sliders, useful for VST and VSTi plugins.
5. The “Slider Master” can be individually bridged with all parameter sliders (positive indexes) or all drop-down lists & transport valuebox for song operations (negative indexes).
6. Transport & Navigation button bar:
   ▸ [Stop] + [Play] buttons or [Stop + Collapse] button let you play the song from the current line or collapse only the selected track.
   ▸ [Stop] button will return a panic when the song is already stopped.
   ▸ The central switch (next to the transport valuebox), allows to switch between 6 different control song operations.
   ▸ The navigation buttons allow “press & hold” for repeat operations.
7. The “options panel” has several preferences & more information that can be turned on or off. This allows greater customization in the functions to be executed.
8. Inside “Pattern Editor” o “Pattern + Matrix” area the List 5 It allows to directly execute a multitude of editing functions, combining them with the 6-position switch.
9. Customizable device panel. It is possible to customize the distribution of the number of slide bars & number of columns, adapting to the physical MIDI controller.
10. The layout of the 4 main transport buttons is customizable -play, loop pattern, stop, edit mode- (1-2-3-4 Distribution), adapting to the physical MIDI controller.
11. It is possible to insert tracks with custom settings.
12. It is possible to control the Distribution Type (Sampler Keyzones) or the Keymap Distribution (Sampler Phrases), using a rotary knob or fader only.
13. MUC provides the ability to reproduce the sound of the instrument, sample, or phrase from a rotary knob or fader, via OSC.
    14 MUC includes envelopes for automation. Allows you to easily save, add or modify envelope points by text editing.
14. MUC is bi-directional. It also allows you to send MIDI output messages (SysEx Data) to enable/disable transport or navigation buttons (LEDs) or others.
15. The Section “MIDI & SysEx In ➜ Out” provides an alternative to custom bidirectional MIDI routing. Use it to gain more control of your compatible MIDI controller.

Also, MIDI Universal Controller offers some exclusive MIDI operations that are not available from Renoise, such as being able to change “presets” in the effects devices, or change “programs” in the plugins, & MIDI access to some specific parameters, such as the “Routing”, “Delay”, “Colors RGB”, “Color Blend” of the tracks, the “Track Headroom” parameter, or the main volume of different elements (song, tracks, instruments, plugins, samples, phrases…). This allows for faster & more direct control.

Use the MUC as a powerful interconnected network of controls for true MIDI control more easy, whether for any modest physical MIDI controller or a sophisticated mix of high-end MIDI controllers!

1 post - 1 participant

Read full topic

Renoise Classic(affordable as it is now)

Renoise X(With,for example,“Elastique Pro”…More costly)

1 post - 1 participant

Read full topic

It’s not my real genre, but I love those epic sounds.

Comments really appreciated.

2 posts - 2 participants

Read full topic

Does anyone know of an instrument that can be played comfortably whilst leaning back on the sofa, maybe even reclining?

I cant think of any super comfortable instruments except for maybe mbira or kalimba.
Only problem is you need fingernails to play those properly. Looking for something else. It can be electronic or accoustic. Tannerins looked kinda cool but they are not available to buy, ou have to make one yourself.

As for sequencers, all the handheld softwares which use gamepad for writing music are perfect for sofa time (LGPT, LSDJ, PSPSEQ), but what about actual instruments?
My searches so far have yielded things like autoharp but there must be something better out there.

guitar - left hand too uncomfortable

keyboard / piano - has to sit bolt upright

drumpad - sits bolt upright

mbira - perfectly comfortable but needs fingernails

tannerin - not available to buy

thummer - not available to buy (looked good in folded position)

8 posts - 5 participants

Read full topic

The video starts off by demonstrating that everything works as expected in both the track effects section and the sampler fx chain when a phrase is not making use of the the sample number column.

0:32 - The phrase is switched to an identical version with the sample number column enabled. Now the Velocity Tracker in the sampler fx chain only responds to changes in the velocity column when they’re being used on the same line as an actual note. The exception to this is sample 0, which responds as it should.

1:13 - When the Velocity Tracker in the track effects section is set to respond to a specific instrument number, it instead responds to velocity changes from the numbered samples in the phrase.

1 post - 1 participant

Read full topic

That was an old previous post about this but seems that lots of links are outdated. Then better to create a new post.

So if you have a musical Twitter account, let’s be in touch!

Here is mine: https://twitter.com/Makeawishmusics

As that was said previously in the older post, this topic is not about the utility or not from Twitter, that’s another story ^^

2 posts - 2 participants

Read full topic

Hey all,

spent the past several days getting all my old tracks up and running with cover art on bandcamp. have a listen if you like! most of these tracks (13/22) were made in renoise. The earllier stuff, reason.

hope you find something you enjoy!

thanks for listening, and for being such a great community. renoise is

•••zensphere••• •••zensphere•••

•••H∑X is love••• •mind manifesting music for dark night deliriums•

1 post - 1 participant

Read full topic

Hello guys!

I’m trying to gather as much information as possible about the Akai MPD232 MIDI controller SysEx data. Does anyone have information to expand here?

At the moment, I have practically the control of the entire device, but I am missing everything related to the control of the RGB lighting of the 16 pads. Does anyone have information about it?

This is all I have collected:

USB MIDI Device: AKAI MPD232. SysEx Data

Device Modes:

• F0 47 00 36 30 00 04 01 00 00 01 F7 ➜ Device Mode 01: Lock all except the pads.
• F0 47 00 36 30 00 04 01 00 00 02 F7 ➜ Device Mode 02: Unlock all. It does not send SysEx data.
• F0 47 00 36 30 00 04 01 00 00 08 F7 ➜ Device Mode 08: Unlocks to send SysEx on MIDIIN4 for all buttons (no pads)
• F0 47 00 36 30 00 04 01 00 00 38 F7 ➜ Device Mode 38: Unlocks to send SysEx on MIDIIN4 for every button, pad, fader

Controls:

• F0 47 00 36 30 00 04 01 00 01 _ _ F7 ➜ Demo Mode: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 02 _ _ F7 ➜ Preset Change: _ _ = number of preset

• F0 47 00 36 30 00 04 01 00 07 _ _ F7 ➜ Tap Tempo: _ _ = (>=01 off, 00 on)

• F0 47 00 36 30 00 04 01 00 0E _ _ F7 ➜ Lock: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 11 _ _ F7 ➜ Full Level: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 12 _ _ F7 ➜ 16 Level: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 13 _ _ F7 ➜ Note Repeat: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 14 _ _ F7 ➜ Pad Banks: _ _ = (00 A, 01 B, 02 C, 03 D)

• F0 47 00 36 30 00 04 01 00 15 _ _ F7 ➜ Control Banks: _ _ = (00 A, 01 B, 02 C)

• F0 47 00 36 30 00 04 01 00 16 _ _ F7 ➜ Time Division: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 17 _ _ F7 ➜ Seq On/Off: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 19 _ _ F7 ➜ Seq Rec: _ _ = (00 off, 01 on)

• F0 47 00 36 30 00 04 01 00 1A _ _ F7 ➜ Step Bank: _ _ = (00 01-16, 01 17-32)

• F0 47 00 36 30 00 04 01 01 79 _ _ F7 to
  F0 47 00 36 30 00 04 01 02 00 _ _ F7 ➜ Sequence Lights

• F0 47 00 36 31 00 04 01 0B 0E _ _ F7 to
  F0 47 00 36 31 00 04 01 0B 2D _ _ F7 ➜ Sequence Button

• F0 47 00 36 31 00 04 01 00 _ x _ y F7 ➜ Display ASCII: _ x = Start number, _ y = Letter in ASCII

• RGB LEDS ???

What interests me the most are the SysEx messages that control the RGB lighting change of the pads. This is probably a string of more than 10 bytes, with 3 bytes destined for RGB color, probably 00 00 00 to 7F 7F 7F. I suspect it would go something like this:

• F0 47 00 36 31 00 04 01 ?? ?? _R _G _B F7 ➜ _R _G _B = (00 00 00 to 7F 7F 7F)

SysEx data may have things in common with similar Akai devices (MPD226, MPD218, or old models). Anyone have information on these topics?

1 post - 1 participant

Read full topic

Hi
I thought you renoisers might be interested to see Renoise in a sonicstate articel I wrote recently.

Sonicstate The DAWs - Choosing A Digital Audio Workstation

An overview of the most popular production software available today

Hope you enjoy it !

Chris

1 post - 1 participant

Read full topic

Is there a good way to make a live reverse effect because I don’t like rendering individual sounds and reversing them. I was trying to test to see if I could create this by using a delay and modulating the delay time backwards. It sounds as if it is playing in reverse but I am not getting a consistent playback. Let me know if you have any ideas !

1 post - 1 participant

Read full topic

New bossa nova can be found on my website.

EatMe - Nueva Bossa

Download and listen here: http://eatme.pro/music?search=nueva%20bossa

Bossa nova made with Band-in-a-Box and Renoise, using the LoungeLizard Session Electric Piano plugin for the electric piano bass lines and chords. Composition, production, mixing and mastering, Music by EatMe.

1 post - 1 participant

Read full topic

New house music:

EatMe - Shift (Mix and Master by Cypher)

I hired Cypher for a pizza to mix and master my tune “Shift”.
That turned out great.

The new mix can be downloaded on http://eatme.pro/music?search=shift

1 post - 1 participant

Read full topic

We are providing UK/USA/CA IPTV streams, with all local channels.

We have 10000+ IPTV Streams.

Quality is guaranteed.

Most wanted channels with stable streams world wide channels with good quality.

First test our stream if you are satisfied then buy.

Incredible offer for our valued clients.

ADDON PACKAGES UPDATE:

• EPL/EFL - 40 Additional connections

• Local UK Cinema, Sports - Direct Restreams
  We aso provide premium quality IPTV Subscriptions

For more info, pricing, channels, test line please contact us with your telegram id

Telegram Gray Stephen

You can contact @Stephen84 right away.

Thanks

1 post - 1 participant

Read full topic

Hello,

I put my question in Off-Topic Category but if there are Renoise answers (with working XRNS), it’s even better. So my question is about those small robot voices from the 80’s. I want to know how they were made with effects of that era. I know that it is not vocoders. But I’m not sure if it is octavers, pitch shifters, harmonizers, chorus, flangers…

Here are some examples. Can you help me? Thanks.

“Got it all together don’t 'cha baby”

"Ohhhh weee, you bugger. "

(here with a bit more effects but lyrics not found)

1 post - 1 participant

Read full topic

Clicked something by accident and now the window button is missing. It is supposed to be between the minimize and X button. Anyone know how to fix this??

3 posts - 2 participants

Read full topic

Here is a log. Running 3.3.2.

jneen@cinnamon$ /Applications/Renoise.app/Contents/MacOS/Renoise Renoise LOG> ============================================================ Renoise LOG> Version : Renoise V3.3.2 (Mar 7 2021) Renoise LOG> Date : 2021-05-10 Renoise LOG> Time : 13:29:30 Renoise LOG> OS : Mac OS X 10.16 (x86_64) Renoise LOG> ============================================================ Renoise LOG> CPU: Found 4 enabled unit(s) with 1 core(s) and 2 logical processor(s) per unit. 4 cores, 8 logical processors are enabled in total. Renoise LOG> Application: Showing the splash window... Renoise LOG> Application: Initializing the API... Renoise LOG> IPP: Detected CPU type: 0x46 Renoise LOG> CoreAudio: Enumerating devices... Renoise LOG> CoreAudio: ======== device enumeration: 1 of 4 ======== Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Input information --- Renoise LOG> CoreAudio: Driver name: Apple Inc.: MacBook Pro Microphone Renoise LOG> CoreAudio: SampleRate: 48000.000000 Renoise LOG> CoreAudio: mFormatID: 'mcpl' Renoise LOG> CoreAudio: Flags: 0x 9 Renoise LOG> CoreAudio: Bytes per packet: 4 Renoise LOG> CoreAudio: Frames per packet: 1 Renoise LOG> CoreAudio: Bytes per frame: 4 Renoise LOG> CoreAudio: Channels per frame: 1 Renoise LOG> CoreAudio: Bits per channel: 32 Renoise LOG> CoreAudio: Device audio buffers: Renoise LOG> CoreAudio: Number of buffers: 1 Renoise LOG> CoreAudio: -- Buffer 0 -- Renoise LOG> CoreAudio: Number of channels: 1 Renoise LOG> CoreAudio: Size in bytes: 2048 Renoise LOG> CoreAudio: Total number of input channels: 1 Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Output information --- Renoise LOG> CoreAudio: Driver name: Apple Inc.: MacBook Pro Microphone Renoise LOG> CoreAudio: GetStreamFormat FAILED Renoise LOG> CoreAudio: ======== device enumeration: 2 of 4 ======== Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Input information --- Renoise LOG> CoreAudio: Driver name: Apple Inc.: MacBook Pro Speakers Renoise LOG> CoreAudio: GetStreamFormat FAILED Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Output information --- Renoise LOG> CoreAudio: Driver name: Apple Inc.: MacBook Pro Speakers Renoise LOG> CoreAudio: SampleRate: 48000.000000 Renoise LOG> CoreAudio: mFormatID: 'mcpl' Renoise LOG> CoreAudio: Flags: 0x 9 Renoise LOG> CoreAudio: Bytes per packet: 8 Renoise LOG> CoreAudio: Frames per packet: 1 Renoise LOG> CoreAudio: Bytes per frame: 8 Renoise LOG> CoreAudio: Channels per frame: 2 Renoise LOG> CoreAudio: Bits per channel: 32 Renoise LOG> CoreAudio: Device audio buffers: Renoise LOG> CoreAudio: Number of buffers: 1 Renoise LOG> CoreAudio: -- Buffer 0 -- Renoise LOG> CoreAudio: Number of channels: 2 Renoise LOG> CoreAudio: Size in bytes: 4096 Renoise LOG> CoreAudio: Total number of output channels: 2 Renoise LOG> CoreAudio: ======== device enumeration: 3 of 4 ======== Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Input information --- Renoise LOG> CoreAudio: Driver name: Rogue Amoeba Software, Inc.: Loopback Audio Renoise LOG> CoreAudio: SampleRate: 48000.000000 Renoise LOG> CoreAudio: mFormatID: 'mcpl' Renoise LOG> CoreAudio: Flags: 0x 9 Renoise LOG> CoreAudio: Bytes per packet: 16 Renoise LOG> CoreAudio: Frames per packet: 1 Renoise LOG> CoreAudio: Bytes per frame: 16 Renoise LOG> CoreAudio: Channels per frame: 4 Renoise LOG> CoreAudio: Bits per channel: 32 Renoise LOG> CoreAudio: Device audio buffers: Renoise LOG> CoreAudio: Number of buffers: 1 Renoise LOG> CoreAudio: -- Buffer 0 -- Renoise LOG> CoreAudio: Number of channels: 4 Renoise LOG> CoreAudio: Size in bytes: 8192 Renoise LOG> CoreAudio: Total number of input channels: 4 Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Output information --- Renoise LOG> CoreAudio: Driver name: Rogue Amoeba Software, Inc.: Loopback Audio Renoise LOG> CoreAudio: SampleRate: 48000.000000 Renoise LOG> CoreAudio: mFormatID: 'mcpl' Renoise LOG> CoreAudio: Flags: 0x 9 Renoise LOG> CoreAudio: Bytes per packet: 16 Renoise LOG> CoreAudio: Frames per packet: 1 Renoise LOG> CoreAudio: Bytes per frame: 16 Renoise LOG> CoreAudio: Channels per frame: 4 Renoise LOG> CoreAudio: Bits per channel: 32 Renoise LOG> CoreAudio: Device audio buffers: Renoise LOG> CoreAudio: Number of buffers: 1 Renoise LOG> CoreAudio: -- Buffer 0 -- Renoise LOG> CoreAudio: Number of channels: 4 Renoise LOG> CoreAudio: Size in bytes: 8192 Renoise LOG> CoreAudio: Total number of output channels: 4 Renoise LOG> CoreAudio: ======== device enumeration: 4 of 4 ======== Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Input information --- Renoise LOG> CoreAudio: Driver name: Apple Inc.: Aggregate Device Renoise LOG> CoreAudio: SampleRate: 48000.000000 Renoise LOG> CoreAudio: mFormatID: 'mcpl' Renoise LOG> CoreAudio: Flags: 0x 9 Renoise LOG> CoreAudio: Bytes per packet: 4 Renoise LOG> CoreAudio: Frames per packet: 1 Renoise LOG> CoreAudio: Bytes per frame: 4 Renoise LOG> CoreAudio: Channels per frame: 1 Renoise LOG> CoreAudio: Bits per channel: 32 Renoise LOG> CoreAudio: Device audio buffers: Renoise LOG> CoreAudio: Number of buffers: 1 Renoise LOG> CoreAudio: -- Buffer 0 -- Renoise LOG> CoreAudio: Number of channels: 1 Renoise LOG> CoreAudio: Size in bytes: 2048 Renoise LOG> CoreAudio: Total number of input channels: 1 Renoise LOG> CoreAudio: Renoise LOG> CoreAudio: --- Device Output information --- Renoise LOG> CoreAudio: Driver name: Apple Inc.: Aggregate Device Renoise LOG> CoreAudio: GetStreamFormat FAILED Renoise LOG> CoreMIDI: Creating client 'Renoise'... ..... hang ..... ..... hang ..... ..... hang ..... ..... hang ..... seriously this hangs for like forever i don't know why could it be a rewire issue? ..... hang .... ..... hang .... ..... hang .... Renoise LOG> CoreMIDI: Creating an input port... Renoise LOG> CoreMIDI: Creating an output port... Renoise LOG> CoreMIDI: Creating a virtual input port... Renoise LOG> Graphport: Initializing Freeimage... Renoise LOG> System: Using '/Applications/Renoise.app/Contents/Resources/' as resource base directory... Renoise LOG> GraphPort: Initializing the Font Engine... Renoise LOG> System: Executing '/Applications/Renoise.app/Contents/Resources/AudioPluginServer_i386.app/Contents/MacOS/RenoisePluginServer --enumerate /var/folders/lz/cczk834x4zs3522q5yzt79y80000gn/T/Renoise-0-2077/Renoise_TmpFile-0-0.tmp' Renoise LOG> Exception: Failed to open the file for reading Renoise LOG> AudioUnitHost: File IO error while reading the plugin bridge component list (Error: Failed to open the file for reading) [asks me for my password here] [i hit cancel]Renoise LOG> ReWire Slave: FAILED to install ReWire (Authorization was canceled)! Renoise LOG> ReWire Slave: ReWire Slave FAILED to open (Error: 100). ReWire might not be installed... Renoise LOG> ReWire Master: FAILED to open (Error: 100). ReWire might not be installed... Renoise LOG> Application: Start running... Renoise LOG> Application: Loading the preferences... Renoise LOG> Application: Init... Renoise LOG> ScriptingTools: Initializing Scripting Tool: '/Users/jneen/Library/Preferences/Renoise/V3.3.2/Scripts/Tools/com.afta8.scl_to_xrni.xrnx/'... Renoise LOG> ScriptingTools: Initializing Scripting Tool: '/Users/jneen/Library/Preferences/Renoise/V3.3.2/Scripts/Tools/com.renoisehackers.MidiConvertExtended.xrnx/'... Renoise LOG> ScriptingTools: Initializing Scripting Tool: '/Applications/Renoise.app/Contents/Resources/Scripts/Tools/com.renoise.ToolUpdater.xrnx/'... Renoise LOG> ScriptingTools: Initializing Scripting Tool: '/Applications/Renoise.app/Contents/Resources/Scripts/Tools/com.renoise.UpdateChecker.xrnx/'... Renoise LOG> DspDevices: Registering native DSP effects... Renoise LOG> CoreAudio: Using SampleRate 48000 (requested: 48000)... Renoise LOG> CoreAudio: Output device buffer size: 256 Renoise LOG> CoreAudio: Output device extra latency frames: 19 Renoise LOG> CoreAudio: Using Latency 5.333333 - MaxBufferFrameSize: 256 (requested latency 5.333333)... Renoise LOG> CoreAudio: Opening Playback Device 0 'Apple Inc.: MacBook Pro Speakers' (1 Stereo Channels)... Renoise LOG> CoreAudio: Enumerating Output Channel Names... Renoise LOG> CoreAudio: Output ChannelName 0 -> Left:'1' / Right:'' Renoise LOG> CoreAudio: Allocating Input Buffers... Renoise LOG> CoreAudio: Allocating Output Buffers... Renoise LOG> CoreAudio: Output IOProc was successfully installed... Renoise LOG> CoreAudio: Starting Device Apple Inc.: MacBook Pro Speakers... Renoise LOG> CoreAudio: Output Device is up and running... Renoise LOG> CoreAudio: Up and running Renoise LOG> CoreMIDI: Enumerating devices... Renoise LOG> Application: Creating a new document... Renoise LOG> MIDI: Loading MIDI actions from file '/Applications/Renoise.app/Contents/Resources/Scripts/GlobalMidiActions.lua'... Renoise LOG> Osc: Loading OSC actions from file '/Applications/Renoise.app/Contents/Resources/Scripts/GlobalOscActions.lua'... Renoise LOG> Player: Constructing... Renoise LOG> Player: Creating slave threads... Renoise LOG> Player: 6 threads enabled. 8 CPUs are available. Renoise LOG> Player: Start running... Renoise LOG> GUI: Creating the Document GUI... Renoise LOG> GUI: Successfully constructed Renoise LOG> Application: A new document was created. Starting graphics subsystems... Renoise LOG> GraphPort: Initializing in FullscreenMode Renoise LOG> Graphport: Running fullscreen at '0,0,1440,900'... Renoise LOG> GraphPort: Successfully initialized Renoise LOG> Application: Init OK Renoise LOG> Application: Enter MainLoop... Renoise LOG> Application: Exit... Renoise LOG> Shut down: Stopped the Player Renoise LOG> MIDI: Shut down: Closing all acquired MIDI devices... Renoise LOG> Shut down: Stopped and released all MIDI-Devices Renoise LOG> CoreAudio: Stopping Device 'Apple Inc.: MacBook Pro Speakers'... Renoise LOG> CoreAudio: Releasing Device 'Apple Inc.: MacBook Pro Speakers'... Renoise LOG> CoreAudio: Device is down Renoise LOG> Shut down: Stopped and released the active Audio-Device Renoise LOG> Shut down: Destroyed the Player Renoise LOG> Shut down: Destroyed the Document Renoise LOG> Shut down: Destroyed the GraphPort Renoise LOG> Shut down: Saving the Preferences Renoise LOG> Shut down: Destroyed the Preferences Renoise LOG> Shut down: App is down Renoise LOG> Application: Exit OK Renoise LOG> Application: Finalizing the API... Renoise LOG> Closing log file... jneen@cinnamon$

I would rather not go and manually set/unset quarantine bits - is there a way to tell renoise to like. Not do this?

Thanks!
jneen

EDIT: To clarify, I don’t use ReWire and I am not interested in using ReWire. I’ve removed everything ReWire-related I can find in /Library/Application Support/Propellerhead Software and in ~/Library/Application Support/Propellerhead Software and rebooted, and this still happens.

1 post - 1 participant

Read full topic

Backstage offers a good selection of past builds, but they only appear to distribute .exes, and the directory structure of 3.3 is not compatible for example with the binary of 1.2.8 (the oldest available release).

I thought to try to download from the demo archive, but every build listed here Archived Releases | Renoise is a dead link.

Is there an official method for this I’m not aware of?

1 post - 1 participant

Read full topic

Heya. I have a song that crashes renoise 3.3.2 on linux alsa and jack. Just load it, hit play and let it loop, and after a while it crashes renoise. Maximum 2-3 minutes play time, but for me until now it has always crashed after an unknown time, sometimes right after loading, sometimes later…

Please do not shoot me, I know it is the most stupid way to do sound synthesis in renoise. But I have many other projects, where I use the formula device normally, and they once in a while also crash the same way. Just this experimentation triggers the crashes reliably, so I thought it would be a good opportunity to report it as a bug. Also maybe someone likes and go lul. Is eeezy, n4tive fM sYNtH3s1z, bR0…

Song1.xrns (35.4 KB)

1 post - 1 participant

Read full topic

1 post - 1 participant

Read full topic

Applied acoustics has released a modular which sounds pretty good , problem is when using the pc keyboard while interacting with the gui (even moving the mouse cursor across the gui ) there is a enormous amount of lag and sometimes note event’s are delayed becasue of this lag
Problem only exists in renoise , tried it in the free vst host cantabile ( with pc keyboard ) and everything runs smooth .
Already contacted the developer , but like I said …it’s a renoise issue
https://www.applied-acoustics.com/multiphonics-cv-1/

1 post - 1 participant

Read full topic