Feed aggregator

@Raul wrote:

I am detecting a certain alarmirsm in Apple users, because the new version of MacOS, Catalina, will not support 32 bits. So, many DAWs are not going to support 32 bit, probably migrating their most important software, all to 64bit.

The issue is that users have been living with 32 bits and 64 bits for many years. This is a huge problem for developers, who even have to launch 2 different software packages, with the enormous work that entails.

In addition, a 32bit operating system is limited to using only 3GB of RAM. It is reasonable to abandon 32bit software development, even if there are programs that do not need 64bit to function properly.

I understand that in Renoise this is also a drag. I think it is better to dedicate yourself fully to 64bit. If it is possible to continue supporting 32bit add-ons, ok. But it is very preferable to waste time in development in 64bit.

I think this situation is the direct fault of the developers, who are still developing in 32bit, and can do so in 64bit. Now many people are going to protest, but we will have to move forward in some way so that the entire time of software development is concentrated in a single package for each operating system. There are many fewer problems, and more advantages also for security and stability.

I believe that we are all going to lose many plugins along the way, which are made only in 32bit, but we will have to settle for that and move forward. In fact, Renoise 3.2.0 has graphic problems using 32bit add-ons. And you must support this 32bit software. Do you see the extra work that all this implies? If Renoise only supported 64bit, everything would work better and there would be more time to improve the 64bit package.

What bothers you personally about this whole matter?

Posts: 1

Participants: 1

Read full topic

@jonassantoso.com wrote:

Hello

Renoise has been my main music production tool for many years. After not having been active for a while, Renoise has called me again, and I have created an album of ten bitpop tracks.

The album was first released on Bump Foot (https://bumpfoot.net/foot281.html), a Japanese netlabel. I then additionally published it on YouTube with screen‑recordings of Renoise playing the tunes. Also, the XRNS files have been published. A list of the softsynths used―all of them free―can be found in the infotext inside the archive (and below).

The XRNS files and the YouTube playlist may be found here:

https://jonassantoso.com/even-further

Artist: The Hardliner (https://jonassantoso.com) Album: Further Beyond Serendipity Release date: 22 September 2019 Label: Bump Foot (https://bumpfoot.net) Original release URL: https://bumpfoot.net/foot281.html Catalog number: foot281 The eleven files listed below constitute the open-source release of above album and are released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). . ├── 00-the_hardliner_-_further_beyond_serendipity.txt ├── 01-the_hardliner_-_feline_population.xrns ├── 02-the_hardliner_-_all_things_equally_serene.xrns ├── 03-the_hardliner_-_beach_memories.xrns ├── 04-the_hardliner_-_chance_encounter_matrix.xrns ├── 05-the_hardliner_-_choco_azahara.xrns ├── 06-the_hardliner_-_devoid_of_harmony_pollution.xrns ├── 07-the_hardliner_-_first_exposure_to_a_new_colour.xrns ├── 08-the_hardliner_-_flexing_the_right_muscles_right.xrns ├── 09-the_hardliner_-_hidden_note_innuendo.xrns └── 10-the_hardliner_-_rainy_day,_tennis_court.xrns The album was created using Renoise V3.1 (https://renoise.com) and the following free softsynths: . ├── Charlatan (http://www.blaukraut.info) ├── Dexed (http://asb2m10.github.io/dexed) ├── helm64 (https://tytel.org/helm) ├── SQ8L (http://www.buchty.net/ensoniq) ├── Synth1 VST64 (https://daichilab.sakura.ne.jp/softsynth/index.html) └── Tunefish4 (https://www.tunefish-synth.com) The samples were mostly taken from the SoundTracker 'ST-XX' sampledisks and the set of waveforms that come with MusicLine Editor, all of which can be found on Aminet (http://aminet.net). --thl 20191007

–thl

Posts: 1

Participants: 1

Read full topic

@slujr wrote:

new beat up, all renoise dsp, lmk whatchu think

thanks for listening!

Posts: 1

Participants: 1

Read full topic

@Raul wrote:

Close All Plugin Windows. What is it?

This tool called “Close All Plugin Windows” provides two links & two key bindings to close all plugin windows:

• Menu access: “DSP Chain List: ~Close All Plugin Windows (VST)”
• Menu access: “Instrument Box: ~Close All Plugin Windows (VSTi)”
• Key binding: “Global:Tools: ~Close All Plugin Windows (VST)” …suggested: [CONTROL ALT P]
• Key binding: “Global:Tools: ~Close All Plugin Windows (VSTi)” …suggested: [SHIFT ALT P]

Remember to manually assign the commands for key binding in “Edit:Preferences:Keys: Global:Tools…”.

Download

com.ulneiz.CloseAllPluginWindows.v1.0.001.xrnx (1.4 KB)

Related thread Is there a Key binding to close all open plugin windows? Help, Support & Bugs Hello. I’ve searched around on the forums a bit but wasn’t able to find a solution to my problem. I have a bunch of VST plugin windows open, with no good way of closing them. They’re always-on-top so they’re disruptive to using the renoise interface I know that I can individually close each of those by clicking on the “editor” button, but that’s not very helpful when you’ve got a large number of instruments already open, and need to quickly close them. How can I quickly close all VST plugins …

Posts: 1

Participants: 1

Read full topic

@derfundig wrote:

Single pattern, phrase fun. Never repeats the exact same thing.

Posts: 3

Participants: 3

Read full topic

@jarzu3 wrote:

Is there a way to save your vst picking window as collapsed ?
So that when you start renoise up the vst folders are collapsed instead of expanded

Posts: 1

Participants: 1

Read full topic

@beatsgo wrote:

This topic builds off of concepts I presented in another thread that will be used to demonstrate a unique way of instrument/audio designing. A interesting concept that I’ve been toying around is how to randomize sample pitches. It’s fairly simple:

• Underneath pitch in the modulation chain, define 2 modulations: stepper and operand
• Stepper: configure it as shown below
  
• Operand: configure it as shown below
  

Now you have an instrument that randomly plays different pitches when hitting note.

This effect is great but comes with a downside: one modulation for a set of samples, not good for . Let say if 2 samples are assigned to that specific modulation chain we created, both of them are assigned the same pitch offset for every key press.

Instead of seeing a modulation chain as multiple outputs, think of it as a single channel/output. Treat each sample as an operator. If you put in that perspective, separate each sample to their own modulation chain as below. You can duplicate and modify the operand to suite your degree of detuning.

Let’s take this step one step further. What if you have 3 samples and only want to execute 2 per key press? The catch is the samples are executed at random at will. Right you can do that…

…but you can only trigger one key press at a time. That is unless you create a phrase that states 2 samples (no defined samples)…thus…

Posts: 1

Participants: 1

Read full topic

@beatsgo wrote:

One thing that may go a long ways is the capability of attaching the pattern matrix in the detached mixer view. Your thoughts?

Posts: 1

Participants: 1

Read full topic

@stoiximan wrote:

Hi all,i need some help about recording vocals.Should i put a compressor when recording vocals and if so what settings for the compressor.Any other tips would be helpful cause when i record vocals the are all over the place.

Posts: 1

Participants: 1

Read full topic

@minkepatt wrote:

What about the possibility to save a bunch of phrases to a library so that you can load this bunch thereafter, for example to use it for another .xrni-instrument?

Posts: 1

Participants: 1

Read full topic

@PrinzNika wrote:

the dropdown midi menu only Lists devices, that are in the Alsa midi realm.
I am trying to send midi to Ingen, which natively uses Jack. I could just wire it up myself if there was the possibility to open a midi out from renoise, but as I cant select Ingen, I cant send out midi.
Is there a workaround?

Posts: 1

Participants: 1

Read full topic

@linq wrote:

Is it possible to change the selected instrument via the Renoise API? Couldn’t find anything in the API docs but wanted to make sure.

Posts: 1

Participants: 1

Read full topic

@shimmer wrote:

I’m new to Renoise and DAWs. I have Blue Arp plugin setup to feed arpeggiated notes to a Dexed VST plugin instrument. The arpeggios sound great, but on initial key press there is a strong punch of a sound, almost like a kick sample. When the Dexed instrument itself is highlighted, the synth keyboard sounds fine on its own. Am I doing something wrong?

Posts: 1

Participants: 1

Read full topic

@savardm wrote:

Is there a way to manually type in the start and end point for a loop in Redux? Dragging the is a bit of a hit and miss approach. Especially when you have the right values but for some reason they didn’t import in.

Thanks.

Posts: 1

Participants: 1

Read full topic

@thebinarycollective wrote:

It would be cool to run on a Raspberry Pi or similar device.

Posts: 1

Participants: 1

Read full topic

@luisaguirre wrote:

I have a few DAWs I’ve been playing with. From these, Renoise by default sounds considerably more quiet when I load a VST or sample to play. I completed this track in Renoise:

https://soundcloud.com/luxatomic/into-the-microverse

And wasn’t satisfied with the way it turned out. The sounds seems to lackluster and dull. I’ve re-mixed and re-mastered several times with little improvement. I’m a beginner and am definitely learning the ropes, but the songs I create in other DAWs seem to have more punch to them even before any effects.

I did a little experiment and ran Renoise, Studio One and Reason with default launch settings. Loaded the Same VST synth on all three. Studio One and Renoise sounded pretty damn good, while Renoise sounded almost muffled very quiet comparatively.

I checked preferences and they all matched, and all are running through the same sound card.

Am I missing something? Out of all these DAWs I find Renoise the most creative to work with but when I export my stems they lack impact compared to Reason and Studio One.

Appreciate any feedback and help regarding this before I start another project that I’ll end up being unhappy with.

Posts: 2

Participants: 2

Read full topic

@omega1972 wrote:

Hi Everyone,

Wind e.p

Bandcamp : https://hymen-records.bandcamp.com/album/wind

Sea e.p

Bandcamp : https://hymen-records.bandcamp.com/album/sea

Have a nice day

Posts: 1

Participants: 1

Read full topic

@ffx wrote:

The audio latency could be switched to some kind of automated logic.

So if Renoise hits a cpu overload (already implemented), the latency could be increased to the next higher available latency, without stopping the song playback. Also there could be an option to start with 8ms always on song load then, so a maximal/minimum latency threshold setting.

Also there could be two shortcuts for increasing/decreasing latency on-the-fly, also without stopping playback.

I always like to use the most low latency possible in each song project, and always switching the latency manually in the prefs seems a bit of an annoying workflow.

Posts: 1

Participants: 1

Read full topic

@Land_of_Bits wrote:

Posts: 1

Participants: 1

Read full topic

@dep wrote:

Hello all. I am a heavy Renoise user, and utilize a lot of instrument and effect plugins in my tunes as well. I’m considering either a Macbook Air or a Macbook Pro for Renoise, and am curious if anyone here has experience with the lesser powerful Air for heavy usage. Thanks in advance!

Posts: 3

Participants: 2

Read full topic