Feed aggregator

R3.3.0 Win10 x64

I would like to address a fairly common problem in the API: visual centralization of selection.

Using the API, when you add an element to a list or panel and select, such as a device, Renoise should visually centralize the selection of that element. The most common are device chains or lists.

I can check and list in this thread the known cases that work correctly and the ones that don’t:

Correct visual centralization:

1. Select tracks (in Pattern Editor), keep focus centralized horizontally. Ok!
2. Select track devices in Pattern Editor, bottom devices panel), keeps the focus centralized horizontally. Ok!
3. Select sample effect device (in “Effect” tab, DSP chain list) keeps the focus centralized horizontally. Ok!
4. Select samples (Samples box) keeps the focus centralized vertically. Ok!
5. Select instruments (Instruments box) keeps the focus centralized vertically. Ok!
6. Select sequence (Matrix) keeps the focus centralized vertically. Ok!
7. Select note column (in Pattern Editor) keeps the focus centralized horizontally. Ok!
8. Select effect column (in Pattern Editor) keeps the focus centralized horizontally. Ok!
9. Select line (in Pattern Editor) keeps the focus centralized vertically. Ok!

Incorrect visual centralization:

1. Select sample devices (in “Modulation” tab) does not centralize visually. It should centralize horizontally. Related issue
2. Select modulation set (in “Modulation” tab) does not centralize visually. It should centralize vertically.
3. Select sample effect device (in “Effect” tab, bottom devices panel) does not centralize visually. It should centralize horizontally.
4. Select effect chain (in “Effect” tab) does not centralize visually. It should centralize vertically.

Maybe there are some more. Fortunately there are not many.

In general, the properties of the selected_X_index song should be responsible for visually centralizing that selection, so that the user does not lose the visual focus of the element.
Related issue (renoise.song().selected_sample_modulation_set_device_index):
[Incomplete Doc] "selected sample modulation set device index"? Renoise Tools R3.2.4 Win10 x64 It seems that the API is missing the device selection within the sample_modulation_set (Reniose.Song.API.lua): – Access a single device by index. renoise.song().instruments[].sample_modulation_sets[]:device(index) This is to access the properties of the device. But there is no way to select the device (inside the sample_modulation_set). Something like this: renoise.song().selected_sample_modulation_set_device_index (this does not exist!) This should select the device and…

1 post - 1 participant

Read full topic

https://soundcloud.com/user-981941512/nesquafe
Hey everyone. Here’s a little 8bit style tune I’ve made. I hope you enjoy it if you check it out!

2 posts - 2 participants

Read full topic

Happy New Year Everybody! New Track Out! Let me know what you think.

1 post - 1 participant

Read full topic

Hello,

Renoise 3.3 does not find VST3 plugins if they are in another folder than C:\Program Files\Common Files\VST3
I am manually placing my VST3 plugins into another folder (which is specified in Renoise and also contains my VST2 plugins). Reaper has no problem with that and finds all the VST3 plugins in there just fine. But Renoise does not find them at all, only if they are in C:\Program Files\Common Files\VST3. I think that should be changed, so that Renoise recognizes VST3 plugins (*.vst3 files) in any VST directory path that is specified within the settings.

Cheers

1 post - 1 participant

Read full topic

Flashcore
Renoise for beats
Reaper in master rewire for melodies
Started messing with renoise more seriously a few months ago
this is one of the first track im decently happy with

1 post - 1 participant

Read full topic

I want to try translating this one into german:

files.renoise.com Renoise%20Quickstart_30.pdf

959.95 KB

i just want to translate most words as possible.

Then upload it in this forum.

Allowed?

1 post - 1 participant

Read full topic

In Renoise 3.3 I’ve noticed that for some reason Instrument names keep resetting quite often,

for example the default instrument name is VST: play_VST_x64 (), I rename it to VST: play_VST_x64 (Pipa),
and then after working a while I notice it’s VST: play_VST_x64 () again. A moment ago I had four instrument names reset to the default (three EastWest Play, one Best Service Engine 2 instrument) so it’s not just a single plugin.

This seems to be happening quite often but I still haven’t yet caught what causes it.
Anyone else bumped into this? I don’t remember it ever happening in 3.2.4, or any previous Renoise version for that matter.

1 post - 1 participant

Read full topic

The current track delay seems to be only from -100ms to 100ms, however there are libraries that require more, for example Cinematic Studio Strings and Audiobro Genesis Children’s Choir both need around -350ms for their slowest legatos and look ahead to work correctly, so would be nice if you could set the track delay freely.

1 post - 1 participant

Read full topic

dropping here too will be easier to find it later , I’m quite a newbie in Renoise can’t see any drawback of it so sharing

seems the position of the reset of the LFOs can be controlled by Formula device using the following formula

function foo(A) return (A*100)*(LINEF%(NUMLINES/(A*100))/ NUMLINES); end

where A*100 is the number of the cycles per pattern which means the (custom)LFOs no needs triggering anymore to able to be in sync with the current pattern position (mainly can work as the automation editor)

device is here

<?xml version="1.0" encoding="UTF-8"?> <FilterDeviceClipboard doc_version="0"> <DeviceSlot type="DooferDevice"> <IsMaximized>true</IsMaximized> <IsSelected>true</IsSelected> <SelectedPresetName>mseg</SelectedPresetName> <SelectedPresetLibrary>User Library</SelectedPresetLibrary> <SelectedPresetIsModified>false</SelectedPresetIsModified> <IsActive> <Value>1.0</Value> <Visualization>Device only</Visualization> </IsActive> <Macro0> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 1</Name> </Macro0> <Macro1> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 2</Name> </Macro1> <Macro2> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 3</Name> </Macro2> <Macro3> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 4</Name> </Macro3> <Macro4> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 5</Name> </Macro4> <Macro5> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 6</Name> </Macro5> <Macro6> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 7</Name> </Macro6> <Macro7> <Value>50</Value> <Visualization>Device only</Visualization> <Name>Macro 8</Name> </Macro7> <NumActiveMacros>4</NumActiveMacros> <ShowDevices>true</ShowDevices> <DeviceChain> <SelectedPresetName>Init</SelectedPresetName> <SelectedPresetLibrary>Bundled Content</SelectedPresetLibrary> <SelectedPresetIsModified>true</SelectedPresetIsModified> <Devices> <FormulaMetaDevice type="FormulaMetaDevice"> <IsMaximized>true</IsMaximized> <IsSelected>true</IsSelected> <SelectedPresetName>Init</SelectedPresetName> <SelectedPresetLibrary>Bundled Content</SelectedPresetLibrary> <SelectedPresetIsModified>true</SelectedPresetIsModified> <IsActive> <Value>1.0</Value> <Visualization>Device only</Visualization> </IsActive> <FormulaParagraphs> <FormulaParagraph>foo(A)</FormulaParagraph> </FormulaParagraphs> <FunctionsParagraphs> <FunctionsParagraph/> <FunctionsParagraph>function foo(A)</FunctionsParagraph> <FunctionsParagraph> return (A*100)*(LINEF%(NUMLINES/(A*100))/ NUMLINES);</FunctionsParagraph> <FunctionsParagraph>end </FunctionsParagraph> </FunctionsParagraphs> <InputNameA>A</InputNameA> <InputNameB>B</InputNameB> <InputNameC>C</InputNameC> <EditorVisible>true</EditorVisible> <InputA> <Value>0.0400001779</Value> <Visualization>Device only</Visualization> </InputA> <InputB> <Value>0.0</Value> <Visualization>Device only</Visualization> </InputB> <InputC> <Value>0.0</Value> <Visualization>Device only</Visualization> </InputC> <DestTrack> <Value>-1</Value> <Visualization>Device only</Visualization> </DestTrack> <DestEffect> <Value>1.0</Value> <Visualization>Device only</Visualization> </DestEffect> <DestParameter> <Value>8</Value> <Visualization>Device only</Visualization> </DestParameter> </FormulaMetaDevice> <LfoDevice type="LfoDevice"> <IsMaximized>true</IsMaximized> <IsSelected>false</IsSelected> <SelectedPresetName>Init</SelectedPresetName> <SelectedPresetLibrary>Bundled Content</SelectedPresetLibrary> <SelectedPresetIsModified>true</SelectedPresetIsModified> <IsActive> <Value>1.0</Value> <Visualization>Device only</Visualization> </IsActive> <DestTrack> <Value>-1</Value> <Visualization>Device only</Visualization> </DestTrack> <DestEffect> <Value>-1</Value> <Visualization>Device only</Visualization> </DestEffect> <DestParameter> <Value>-1</Value> <Visualization>Device only</Visualization> </DestParameter> <Amplitude> <Value>0.5</Value> <Visualization>Device only</Visualization> </Amplitude> <Offset> <Value>0.0</Value> <Visualization>Device only</Visualization> </Offset> <Frequency> <Value>9.99999997e-07</Value> <Visualization>Device only</Visualization> </Frequency> <Type> <Value>4</Value> <Visualization>Device only</Visualization> </Type> <CustomEnvelope> <PlayMode>Lines</PlayMode> <Length>71</Length> <ValueQuantum>0.0</ValueQuantum> <Polarity>Unipolar</Polarity> <Points> <Point>0,0.0,0.0</Point> <Point>49,0.0918367356,0.0</Point> <Point>70,1.0,0.0</Point> </Points> </CustomEnvelope> <CustomEnvelopeOneShot>true</CustomEnvelopeOneShot> <UseAdjustedEnvelopeLength>false</UseAdjustedEnvelopeLength> </LfoDevice> </Devices> </DeviceChain> </DeviceSlot> </FilterDeviceClipboard>

have fun

1 post - 1 participant

Read full topic

Probably been posted before but I couldn’t find anything with a quick search, anyway pretty wicked demo of his workflow with Octamed and Akai S950 / 1100 plus some other old school kit:

https://www.youtube.com/watch?v=IDn7ZDcx9w0

https://www.soundonsound.com/techniques/retro-jungle-production-pete-cannon

1 post - 1 participant

Read full topic

Hello all, I’m new in town here.

I’m watching this video from Bizzy B about setting up an amen break in Renoise, and around 4:20 he slices the break and right clicks > slices > slice to phrase. Immediately after, he shows the phrase menu, plays it (by pressing enter, and not space… why is that?) and then changes the bpm. He shows that pressing other keys on the keyboard will play the sample at the same tempo (170 bpm) but the pitch changes.

My issue is that when doing these same steps, my break is playing at the same root pitch on all key presses up and down octaves. It’s definitely moving at 170 bpm, but never changing pitch. I followed his directions very closely, is there an option that may be selected that I am missing here? Or is it because of something else like, my sample has too few slices?

Thanks

1 post - 1 participant

Read full topic

Hello!

I’m having syncing issues with Generate VST3 (did not try VST2 as I stopped installing those altogether)

The LFOs and the SEQ when in ‘Play Sync’ mode do not sync properly. It is weird. They start out of sync and then get synced seconds later.

Generate is paid but Pendulate is not, and I guess they share some code. I did not try with this plugin but I bet that the issue is there too.

I’m pretty sure the problem is within the plugin and not Renoise, but wanted to post a bug report before submitting one to Dan at Newfangled Audio.

Cheers!

1 post - 1 participant

Read full topic

@taktik I searched for this and found the only way to get the desired result is to place a Gainer set to -INF to do this; shut down an entire channel’s volume.

Is there a possibility that this may be accessible via the pattern sequencer in the future - very handy to just type in a channel “mute” command that fully silences the channel like the Gainer can.

@Raul - is this something accessible via Lua?

1 post - 1 participant

Read full topic

Same story as in
OSX Mojave: Addictive Drums 2 VST2 GUI randomly crashes Help, Support & Bugs Did update from 3.1 (it worked flawlessly) to 3.3 Loaded Addictive Drums 3 VST (2), open gui, load some preset, hit [let say a lot/crazy drum solo;)] notes for few moments (minute/two), repeat crash. Keep on happening every time, once faster one slower. Update: 3.2 seems to do it too, less often Update2: second crash was when clicked addictive drums logo on ui, it worked for some time and crashed. G Log: VstPlugs: Opening custom cocoa editor window for plug ‘XLN Audio: Addictive Drums 2’… V…
and it worked and works good in 3.1. Same story, playing notes via midi controller for period of times, but this time Ample Sound bass j. i would add to same topic but i did see that was edited so i didn’t know what i should do.

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

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: Successfully loaded template document.

GraphPort: Initializing in WindowedMode
GraphPort: Successfully initialized

Application: Init OK
Application: Enter MainLoop…

VstPlugs: Trying to instantiate ‘/Library/Audio/Plug-Ins/VST/ABJF.vst/Contents/MacOS/ABJF’…
VstPlugs: Plugin is a Mach-O executable…
VstPlugs: Loading bundle: ‘/Library/Audio/Plug-Ins/VST/ABJF.vst’
VstPlugs: Analyzing VST plugin ‘Ample Sound: ABJF’, Unique ID:1096968806, Version:2400
VstPlugs: Instantiate OK
VstPlugs: CreateInstance succeeded
VstPlugs: Opening custom cocoa editor window for plug ‘Ample Sound: ABJF’…

CrashLog: 0 libsystem_platform.dylib 0x00007fff5c31bb5d _sigtramp + 29
CrashLog: 1 ??? 0xbff0000000000000 0x0 + 13830554455654793216
CrashLog: 2 AppKit 0x00007fff2e08df48 -[_NSDisplayOperation queueDrawOperationForView:rect:rectSet:windowRegion:options:] + 236
CrashLog: 3 AppKit 0x00007fff2e08e7f9 -[_NSDisplayOperationStack queueDrawOperationForView:rect:rectSet:windowRegion:options:] + 142
CrashLog: 4 AppKit 0x00007fff2d7e4f10 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4956
CrashLog: 5 AppKit 0x00007fff2d7e4798 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3044
CrashLog: 6 AppKit 0x00007fff2d7e4798 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3044
CrashLog: 7 AppKit 0x00007fff2d7e3b8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65
CrashLog: 8 AppKit 0x00007fff2d7e1490 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893
CrashLog: 9 AppKit 0x00007fff2d7e0ac9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253
CrashLog: 10 AppKit 0x00007fff2d7dd6be -[NSView displayIfNeeded] + 1302
CrashLog: 11 AppKit 0x00007fff2d7da3ff -[NSWindow displayIfNeeded] + 280
CrashLog: 12 AppKit 0x00007fff2d7da240 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684
CrashLog: 13 AppKit 0x00007fff2d7d5334 NSDisplayCycleObserverInvoke + 162
CrashLog: 14 AppKit 0x00007fff2d7d4eb4 NSDisplayCycleFlush + 1030
CrashLog: 15 QuartzCore 0x00007fff3ab9954d _ZN2CA11Transaction19run_commit_handlersE18CATransactionPhase + 49
CrashLog: 16 QuartzCore 0x00007fff3ab98d26 _ZN2CA11Transaction6commitEv + 212
CrashLog: 17 AppKit 0x00007fff2d7d484d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274
CrashLog: 18 CoreFoundation 0x00007fff30149374 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
CrashLog: 19 CoreFoundation 0x00007fff301492a9 __CFRunLoopDoObservers + 451
CrashLog: 20 CoreFoundation 0x00007fff300ebe42 __CFRunLoopRun + 1143
CrashLog: 21 CoreFoundation 0x00007fff300eb779 CFRunLoopRunSpecific + 459
CrashLog: 22 HIToolbox 0x00007fff2f33c1ab RunCurrentEventLoopInMode + 292
CrashLog: 23 HIToolbox 0x00007fff2f33bee5 ReceiveNextEventCommon + 603
CrashLog: 24 HIToolbox 0x00007fff2f33bc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
CrashLog: 25 AppKit 0x00007fff2d6d377d _DPSNextEvent + 1135
CrashLog: 26 AppKit 0x00007fff2d6d246b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
CrashLog: 27 AppKit 0x00007fff2d6cc588 -[NSApplication run] + 699
CrashLog: 28 Renoise 0x000000010312ba06 Renoise + 8542726
CrashLog: 29 Renoise 0x0000000102917d92 Renoise + 73106
CrashLog: 30 Renoise 0x0000000102917c61 Renoise + 72801
CrashLog: 31 libdyld.dylib 0x00007fff5c1303d5 start + 1
CrashLog: 32 ??? 0x0000000000000001 0x0 + 1

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: ‘/Users/admin/Library/Preferences/Renoise/V3.3.0/CrashBackups/Untitled_1_10_2021__2_28_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…

CoreAudio: Stopping Device ‘Native Instruments: Traktor Kontrol Z2’…
CoreAudio: Releasing Device ‘Native Instruments: Traktor Kontrol Z2’…
CoreAudio: Device is down

MIDI: Shut down: Closing all acquired MIDI devices…

1 post - 1 participant

Read full topic

I’ve noticed a midi related issue lately, whenever Renoise is, for example, exiting, and is trying to close midi subsystems, Renoise will hang (pretty much in not responding mode) until I pull the usb plug of my midi keyboard, after which it proceeds to do what it was going to. The exiting is not the only place where this happens though, but I can’t tell what Renoise is trying to do that particular moment, but whenever it hangs, I see some midi related text at the bottom left info area. Anyone bumped into anything like this? I’ve never had anything like this with Reaper and the controller (Akai MPK49) seems to work fine with it. I’ve had this happening with Renoise 3.2.4 and 3.3 at least.

1 post - 1 participant

Read full topic

Hello, im experiencing weird problem with Aural Verb # on linux (vst2). If I put it on for example snare the fx drops immediately after snare sample ends, even if reverb should have longer tail it is momentary cut off.

I tried same plugin with same sample in bitwig and it is working fine.
Cannot tell if on windows/mac plugin will behave correctly.

1 post - 1 participant

Read full topic

Did update from 3.1 (it worked flawlessly) to 3.3
Loaded Addictive Drums 3 VST (2) load some preset, hit [let say a lot/crazy drum solo;)] notes for few moments (minute/two), repeat crash. Keep on happening every time

Log:

VstPlugs: Opening custom cocoa editor window for plug ‘XLN Audio: Addictive Drums 2’…

VstPlugs: Cocoa Editor window for plug ‘XLN Audio: Addictive Drums 2’ was closed

VstPlugs: Opening custom cocoa editor window for plug ‘XLN Audio: Addictive Drums 2’…
VstPlugs: Cocoa Editor window for plug ‘XLN Audio: Addictive Drums 2’ was closed

VstPlugs: Opening custom cocoa editor window for plug ‘XLN Audio: Addictive Drums 2’…

CrashLog: 0 libsystem_platform.dylib 0x00007fff5c31bb5d _sigtramp + 29
CrashLog: 1 ??? 0x0000000000000000 0x0 + 0
CrashLog: 2 CoreFoundation 0x00007fff300f9604 -[NSArray initWithArray:range:copyItems:] + 401
CrashLog: 3 Foundation 0x00007fff3241109c -[__NSOperationInternal _waitUntilFinished:] + 199
CrashLog: 4 Foundation 0x00007fff32445e56 -[NSOperationQueue waitUntilAllOperationsAreFinished] + 282
CrashLog: 5 AppKit 0x00007fff2d7e4f39 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4997
CrashLog: 6 AppKit 0x00007fff2d7e4798 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3044
CrashLog: 7 AppKit 0x00007fff2d7e4798 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3044
CrashLog: 8 AppKit 0x00007fff2d7e4798 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3044
CrashLog: 9 AppKit 0x00007fff2d7e3b8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65
CrashLog: 10 AppKit 0x00007fff2d7e1490 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893
CrashLog: 11 AppKit 0x00007fff2d7e0ac9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253
CrashLog: 12 AppKit 0x00007fff2d7dd6be -[NSView displayIfNeeded] + 1302
CrashLog: 13 AppKit 0x00007fff2d7da3ff -[NSWindow displayIfNeeded] + 280
CrashLog: 14 AppKit 0x00007fff2d7da240 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684
CrashLog: 15 AppKit 0x00007fff2d7d5334 NSDisplayCycleObserverInvoke + 162
CrashLog: 16 AppKit 0x00007fff2d7d4eb4 NSDisplayCycleFlush + 1030
CrashLog: 17 QuartzCore 0x00007fff3ab9954d _ZN2CA11Transaction19run_commit_handlersE18CATransactionPhase + 49
CrashLog: 18 QuartzCore 0x00007fff3ab98d26 _ZN2CA11Transaction6commitEv + 212
CrashLog: 19 AppKit 0x00007fff2d7d484d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274
CrashLog: 20 CoreFoundation 0x00007fff30149374 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
CrashLog: 21 CoreFoundation 0x00007fff301492a9 __CFRunLoopDoObservers + 451
CrashLog: 22 CoreFoundation 0x00007fff300ebe42 __CFRunLoopRun + 1143
CrashLog: 23 CoreFoundation 0x00007fff300eb779 CFRunLoopRunSpecific + 459
CrashLog: 24 HIToolbox 0x00007fff2f33c1ab RunCurrentEventLoopInMode + 292
CrashLog: 25 HIToolbox 0x00007fff2f33bee5 ReceiveNextEventCommon + 603
CrashLog: 26 HIToolbox 0x00007fff2f33bc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
CrashLog: 27 AppKit 0x00007fff2d6d377d _DPSNextEvent + 1135
CrashLog: 28 AppKit 0x00007fff2d6d246b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
CrashLog: 29 AppKit 0x00007fff2d6cc588 -[NSApplication run] + 699
CrashLog: 30 Renoise 0x000000010cf3da06 Renoise + 8542726
CrashLog: 31 Renoise 0x000000010c729d92 Renoise + 73106
CrashLog: 32 Renoise 0x000000010c729c61 Renoise + 72801
CrashLog: 33 libdyld.dylib 0x00007fff5c1303d5 start + 1
CrashLog: 34 ??? 0x0000000000000001 0x0 + 1

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: ‘/Users/admin/Library/Preferences/Renoise/V3.3.0/CrashBackups/Untitled_1_9_2021__16_15_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…

CoreAudio: Stopping Device ‘Native Instruments: Traktor Kontrol Z2’…
CoreAudio: Releasing Device ‘Native Instruments: Traktor Kontrol Z2’…
CoreAudio: Device is down

MIDI: Shut down: Closing all acquired MIDI devices…

1 post - 1 participant

Read full topic

Hi guys, is there any way to record volume for notes played via plugins? I am using Serum with a controller keyboard and whilst Renoise adds the initial volume/velocity to the volume column when i press notes it doesn’t actually have any affect. I can change the initial volume to 00 or 7F etc and no effect at all. Also altering the volume in the column during the note being played does nothing.

Is this by design, is there no way to record velocity or volume for a plugin? All i want to do is something simple like play a note then fade out using Renoise. I know most effect commands only work on samples, but is this the same for something simple like volume?

Thanks

2 posts - 2 participants

Read full topic

https://woqinzi.com/kometbomb/prototracker-modular

2 posts - 1 participant

Read full topic

I notice that other DAWs like Ableton and Logic have dedicated “Glue Compressors” for adding cohesion to parts in a mix. Do either of Renoise’s built in compressors work well as glue comps, or do you guys have favorite 3rd party plugins for accomplishing this effect? I don’t really get it TBH, but with our new #Sidechain superpowers, it sounds like this is one of the main uses of sidechain in other DAWs.

1 post - 1 participant

Read full topic