Linux FAQ - Revision history

Achenar at 19:30, 9 July 2025

2025-07-09T19:30:14Z

← Older revision		Revision as of 19:30, 9 July 2025
Line 341:		Line 341:
	: YOURUSERNAME - nice −10		: YOURUSERNAME - nice −10

	Alternatively, you could create a group 'Audio', add your user to that group and then use '@Audio' instead of “YOURUSERNAME”. After this, you should save, log out and then log back in. To make sure this has worked, launch Renoise, select ALSA and ensure that the 'Realtime threads' option is enabled. You will get a friendly warning if RT creation failed. See [https://wiki.linuxaudio.org/wiki/system_configuration ~~https://wiki.linuxaudio.org/wiki/system_configuration~~] for more information and tips on how to build and tweak a real-time audio Linux workstation.		Alternatively, you could create a group 'Audio', add your user to that group and then use '@Audio' instead of “YOURUSERNAME”. After this, you should save, log out and then log back in. To make sure this has worked, launch Renoise, select ALSA and ensure that the 'Realtime threads' option is enabled. You will get a friendly warning if RT creation failed. See [https://wiki.linuxaudio.org/wiki/system_configuration the Linux Audio system configuration] for more information and tips on how to build and tweak a real-time audio Linux workstation.

	=== Jack ===		=== Jack ===

Achenar at 21:03, 8 July 2025

2025-07-08T21:03:00Z

← Older revision		Revision as of 21:03, 8 July 2025
Line 112:		Line 112:
	=== Performance Problems ===		=== Performance Problems ===

	Audio performance problems can occur in Linux for a variety of reasons. Some of the symptoms include: crackling/stuttering audio, audio with noise, excessive Xruns etc. Luxury window managers such as Compiz and Beryl consume a lot of priority time from your CPU resources. ~~[http://www.renoise.com/board/index.php?showtopic=27618~~ Some users have reported] drastically improved performance when shutting these options down, so if you're encountering performance issues it is recommended to use a lighter window manager such as Openbox instead. For further information on audio performance, please consult the documentation (and community) of your particular Linux distribution.		Audio performance problems can occur in Linux for a variety of reasons. Some of the symptoms include: crackling/stuttering audio, audio with noise, excessive Xruns etc. Luxury window managers such as Compiz and Beryl consume a lot of priority time from your CPU resources. Some users have reported drastically improved performance when shutting these options down, so if you're encountering performance issues it is recommended to use a lighter window manager such as Openbox instead. For further information on audio performance, please consult the documentation (and community) of your particular Linux distribution.

	=== Performance Problems With HDA/Intel Soundcards ===		=== Performance Problems With HDA/Intel Soundcards ===
Line 341:		Line 341:
	: YOURUSERNAME - nice −10		: YOURUSERNAME - nice −10

	Alternatively, you could create a group 'Audio', add your user to that group and then use '@Audio' instead of “YOURUSERNAME”. After this, you should save, log out and then log back in. To make sure this has worked, launch Renoise, select ALSA and ensure that the 'Realtime threads' option is enabled. You will get a friendly warning if RT creation failed. You can find a more detailed explanation about PAM and low latencies in Linux here: [https://web.archive.org/web/20081220103232/tapas.affenbande.org/wordpress/?page_id=73 http://tapas.affenbande.org/wordpress/?page_id=73].		Alternatively, you could create a group 'Audio', add your user to that group and then use '@Audio' instead of “YOURUSERNAME”. After this, you should save, log out and then log back in. To make sure this has worked, launch Renoise, select ALSA and ensure that the 'Realtime threads' option is enabled. You will get a friendly warning if RT creation failed. See [https://wiki.linuxaudio.org/wiki/system_configuration https://wiki.linuxaudio.org/wiki/system_configuration] for more information and tips on how to build and tweak a real-time audio Linux workstation.

	~~Also, see~~ [https://wiki.linuxaudio.org/wiki/system_configuration https://wiki.linuxaudio.org/wiki/system_configuration] for more information and tips on how to build and tweak a real-time audio Linux workstation.

	=== Jack ===		=== Jack ===
Line 373:		Line 371:
	'''My question or problem is not addressed by anything in this FAQ. What I can do?'''		'''My question or problem is not addressed by anything in this FAQ. What I can do?'''

	Renoise features an active forum where you can ask your questions, so don’t hesitate to join in with [https://forum.renoise.com the community].		Renoise features an active forum where you can ask your questions, so don’t hesitate to join in with [https://forum.renoise.com the community.]

Achenar at 14:15, 10 October 2019

2019-10-10T14:15:05Z

← Older revision		Revision as of 14:15, 10 October 2019
Line 36:		Line 36:
	This lists the available recording audio ports. If there is no list then you should consult the ALSA documentation with regards to MIDI I/O.		This lists the available recording audio ports. If there is no list then you should consult the ALSA documentation with regards to MIDI I/O.

	=== Checking the ~~JACK~~ Audio Capabilities ===		=== Checking the Jack Audio Capabilities ===

	Renoise can connect to a [[Jack Transport]] server through different backends. At the time of writing, those supported are: ALSA, Core Audio, Port Audio, Free Bob, OSS and a 'dummy' backend. Please ensure that your chosen backend is correctly installed before continuing. To check if ~~JACK~~ is installed and working with your backend, open a terminal and type the following:		Renoise can connect to a [[Jack Transport]] server through different backends. At the time of writing, those supported are: ALSA, Core Audio, Port Audio, Free Bob, OSS and a 'dummy' backend. Please ensure that your chosen backend is correctly installed before continuing. To check if Jack is installed and working with your backend, open a terminal and type the following:

	: $ jackd -d your_backend —help		: $ jackd -d your_backend —help
	: <nowiki>[enter] </nowiki>		: <nowiki>[enter] </nowiki>

	This will list all available ~~JACK~~ server options provided by the audio backend. If there is no list, but you get a ''"jackd: unknown driver [your_backend]"'' error message, then ~~JACK~~ does not support that particular backend. If you get a "Command not found" error, it's possible ~~JACK~~ isn’t installed or the ~~JACK~~ installation is broken. If ~~JACK~~ was installed from a distribution package then check exactly how was packaged. If you compiled ~~JACK~~ by yourself then check if you have correctly configured everything.		This will list all available Jack server options provided by the audio backend. If there is no list, but you get a ''"jackd: unknown driver [your_backend]"'' error message, then Jack does not support that particular backend. If you get a "Command not found" error, it's possible Jack isn’t installed or the Jack installation is broken. If Jack was installed from a distribution package then check exactly how was packaged. If you compiled Jack by yourself then check if you have correctly configured everything.

	=== A More Technical Checkup ===		=== A More Technical Checkup ===
Line 334:		Line 334:
	=== Realtime Threads ===		=== Realtime Threads ===

	'''How do I configure Linux to enable Realtime Threads for ALSA or ~~JACK~~?'''		'''How do I configure Linux to enable Realtime Threads for ALSA or Jack?'''

	~~To allow Renoise to create realtime~~ threads~~, which~~ are required for low latencies with ALSA ~~or JACK~~, you have to edit the /etc/security/limits.conf file. A realtime kernel does ~~NOT~~ help here, ~~does not~~ set the required options ~~automatically!~~ To enable RT thread creation via PAM open the /etc/security/limits.conf file as root (or via sudo)~~. Then somewhere at~~ the end of the file ~~add~~:		Realtime threads are required for low latencies with ALSA and Jack, and to enable them you have to edit the /etc/security/limits.conf file. Simply running a realtime kernel does ''not'' help here, since it doesn't automatically set the required options. To enable RT thread creation via PAM, open the /etc/security/limits.conf file as root (or via sudo) and add the following lines to the end of the file:

	: YOURUSERNAME - rtprio 99		: YOURUSERNAME - rtprio 99
	: YOURUSERNAME - nice −10		: YOURUSERNAME - nice −10

	Alternatively you could ~~also~~ create a group ~~“Audio”~~, add your user to that group, and use “@~~Audio”~~ instead of “YOURUSERNAME”.~~Save. Log Out. Login. Then it~~ should ~~work~~. To make sure ~~that it works~~, launch Renoise, select ALSA and ~~make sure~~ the ~~“Realtime threads”~~ option is on. You will get a friendly warning if RT creation failed. You can find a more detailed explanation about PAM and low latencies in Linux here [https://web.archive.org/web/20081220103232/tapas.affenbande.org/wordpress/?page_id=73 http://tapas.affenbande.org/wordpress/?page_id=73].		Alternatively, you could create a group 'Audio', add your user to that group and then use '@Audio' instead of “YOURUSERNAME”. After this, you should save, log out and then log back in. To make sure this has worked, launch Renoise, select ALSA and ensure that the 'Realtime threads' option is enabled. You will get a friendly warning if RT creation failed. You can find a more detailed explanation about PAM and low latencies in Linux here: [https://web.archive.org/web/20081220103232/tapas.affenbande.org/wordpress/?page_id=73 http://tapas.affenbande.org/wordpress/?page_id=73].

	~~See~~ [https://wiki.linuxaudio.org/wiki/system_configuration https://wiki.linuxaudio.org/wiki/system_configuration] for more information and tips on how to build and tweak a real-time audio Linux workstation.		Also, see [https://wiki.linuxaudio.org/wiki/system_configuration https://wiki.linuxaudio.org/wiki/system_configuration] for more information and tips on how to build and tweak a real-time audio Linux workstation.

	=== ~~JACK~~ ===		=== Jack ===

	'''I have playback problems (crackles, drops, high latencies, etc.) when Renoise plays through ~~JACK~~. What I can do?'''		'''I have playback problems (crackles, drops, high latencies, etc.) when Renoise plays through Jack. What I can do?'''

	We have ~~seen~~ that many playback problems ~~while Renoise is using JACK~~ are ~~often~~ related to ~~JACK~~ server settings. First ~~of all~~ try running the ~~JACK~~ server in non-realtime mode~~: to do this remove~~ the -R option, if you run it on command-line, or - if you run qjackctl - uncheck the ~~“Realtime”~~ checkbox in ~~“Setup”~~ → ~~“Settings”~~.~~'' ''~~The ~~JACK~~ realtime option should be enabled ~~only~~ if you have a kernel with the realtime patch.		We have found that many of these playback problems are related to the Jack server settings. First, try running the Jack server in non-realtime mode by removing the -R option if you run it from the command-line, or if you run qjackctl then uncheck the 'Realtime' checkbox in "Setup → Settings". The Jack realtime option should only be enabled if you have a kernel with the realtime patch.

	=== LADSPA ===		=== LADSPA ===
Line 355:		Line 355:
	'''Renoise doesn’t list my plugin. Why?'''		'''Renoise doesn’t list my plugin. Why?'''

	Renoise ~~never~~ list a LADSPA plugin in the following cases:		Renoise will not list a LADSPA plugin in the following cases:

	* The plugin has zero input and zero output (~~so it has~~ control ports only);		* The plugin has zero input and zero output (control ports only).
	* The plugin isn’t real-time capable;		* The plugin isn’t real-time capable.
	* The plugin is real-time capable but ~~Renoise~~ detected ~~that it’s~~ unstable (it ~~crash~~ Renoise if it tries to load ~~it);~~		* The plugin is real-time capable but has been detected as unstable, since it crashes Renoise when it tries to load the plugin.

	'''Why is Renoise using the wrong in-/out- ports of my plugin?'''		'''Why is Renoise using the wrong in-/out- ports of my plugin?'''

	~~While~~ connecting to a LADSPA plugin Renoise ~~can’t~~ detect which audio ports are ~~REAL~~ audio (left-/right-) ~~inputs~~ and which are ~~REAL~~ audio (left-/right-) ~~outputs~~. So Renoise assumes the first two input ~~audio~~ ports are left-input and right-input and the first two output ports are left-output and right-output. LADSPA plugins are designed to be something like basic blocks for synthesizer modelling environments~~. That means~~ a single plugin can do ~~just only~~ logic operations (ring modulation between two audio ~~signal~~, ~~produce~~ an ADSR envelope when an input audio signal is over defined threshold~~, and so on~~) or the plugin expects more than two audio in to produce its output (~~think about~~ surround processors)~~. That’s why Renoise can list a LADSPA plugin which output has no sense at all~~.		When connecting to a LADSPA plugin, Renoise cannot detect which audio ports are ''real'' audio inputs (left-/right-) and which are ''real'' audio outputs (left-/right-). So Renoise assumes the first two input ports are left-input and right-input, and the first two output ports are left-output and right-output. LADSPA plugins are designed to be something like basic blocks for synthesizer modelling environments, meaning that a single plugin can only do logic operations (e.g. ring modulation between two audio signals, create an ADSR envelope when an input audio signal is over a defined threshold) or the plugin expects more than two audio inputs to produce its output (e.g. surround processors).

	'''Why Renoise lists audio generators (oscillators, noise sources, etc.) in the effect list?'''		'''Why Renoise lists audio generators (oscillators, noise sources, etc.) in the effect list?'''

	~~The answer to this question~~ is similar to the above ~~(“Why Renoise uses the wrong in-/out- ports of my plugin?”)~~: Renoise ~~can’t~~ list generators as ~~instrument~~ because it can’t detect ~~what’s the use of~~ the plugin input control ports.~~'' ''~~Guessing the correct control port for setting the frequency by ~~it’s~~ label ~~isn’t~~ a solution: due to the nature of LADSPA ~~plugs~~ a frequency input can be control data as well as audio data. ~~Also~~ Renoise ~~can’t~~ know ~~which~~ kind of control data the plugin expects~~: can~~ be a signal that ~~raise~~ the ~~freq~~ by 3dB/octave, the MIDI note number or even pure frequency as a floating point number. ~~This is a part of the~~ problem with LADSPA generators~~: another one~~ is that note-on and note-off events are unsupported (in ~~better~~ cases you can have a control handling them) because LADSPA never describes instruments (unlike VSTi or DSSI).		This is similar to the question above: Renoise cannot list generators as instruments because it can’t detect how the plugin input control ports are set up. Guessing the correct control port for setting the frequency by its label is not a solution, since, due to the nature of LADSPA plugins, a frequency input can be control data as well as audio data. Additionally, Renoise cannot know what kind of control data the plugin expects; it could be a signal that raises the frequency by 3dB/octave, the MIDI note number, or even pure frequency as a floating point number. Another problem with LADSPA generators is that note-on and note-off events are unsupported (though in certain cases you can have a control handling them) because LADSPA never describes instruments (unlike VSTi or DSSI).

	=== Others ===		=== Others ===

Achenar at 13:30, 10 October 2019

2019-10-10T13:30:14Z

Show changes

Achenar at 15:28, 9 October 2019

2019-10-09T15:28:19Z

← Older revision		Revision as of 15:28, 9 October 2019
Line 228:		Line 228:
	=== Renoise ===		=== Renoise ===

	'''Why Renoise ~~isn’t~~ able to play when other applications are playing (or after other ~~application~~ have used the audio resource)?'''		'''Why isn't Renoise able to play when other applications are playing (or after other applications have used the audio resource)?'''

	As far as we know, in many desktop manager an audio manager is provided (ex. aRts on KDE or ESD in GNOME). The audio manager often locks the audio resource for it’s own use (this may happen while and after an application used it for playback). So, to solve the problem try disabling the audio manager and set all your audio application to use ALSA directly: ALSA is capable of sharing the audio resource out-of-the-box.		As far as we know, in many desktop manager an audio manager is provided (ex. aRts on KDE or ESD in GNOME). The audio manager often locks the audio resource for it’s own use (this may happen while and after an application used it for playback). So, to solve the problem try disabling the audio manager and set all your audio application to use ALSA directly: ALSA is capable of sharing the audio resource out-of-the-box.

	'''Renoise gives ~~out~~ of memory errors when loading particular songs / samples ~~while i have enough memory~~'''		'''Renoise gives incorrect 'Out of memory' errors when loading particular songs/samples'''

	Be sure that you have not restricted your virtual memory settings on any global level in Linux or that no virtual memory restrictions are set. You can check out your virtual memory settings by entering ''ulimit -a'' in a console. If you want to raise virtual memory just specifically for Renoise you could set this by entering the following command:		Be sure that you have not restricted your virtual memory settings on any global level in Linux or that no virtual memory restrictions are set. You can check out your virtual memory settings by entering ''ulimit -a'' in a console. If you want to raise virtual memory just specifically for Renoise you could set this by entering the following command:
Line 332:		Line 332:
	=== Realtime Threads ===		=== Realtime Threads ===

	'''Ho do I configure Linux to enable Realtime Threads for ALSA or JACK?'''		'''How do I configure Linux to enable Realtime Threads for ALSA or JACK?'''

	To allow Renoise to create realtime threads, which are required for low latencies with ALSA or JACK, you have to edit the /etc/security/limits.conf file. A realtime kernel does NOT help here, does not set the required options automatically! To enable RT thread creation via PAM open the /etc/security/limits.conf file as root (or via sudo). Then somewhere at the end of the file add:		To allow Renoise to create realtime threads, which are required for low latencies with ALSA or JACK, you have to edit the /etc/security/limits.conf file. A realtime kernel does NOT help here, does not set the required options automatically! To enable RT thread creation via PAM open the /etc/security/limits.conf file as root (or via sudo). Then somewhere at the end of the file add:
Line 345:		Line 345:
	=== JACK ===		=== JACK ===

	'''~~Got~~ playback problems (crackles, drops, high latencies, etc.) when Renoise plays ~~thru~~ JACK. What I can do?'''		'''I have playback problems (crackles, drops, high latencies, etc.) when Renoise plays through JACK. What I can do?'''

	We have seen that many playback problems while Renoise is using JACK are often related to JACK server settings. First of all try running the JACK server in non-realtime mode: to do this remove the -R option, if you run it on command-line, or - if you run qjackctl - uncheck the “Realtime” checkbox in “Setup” → “Settings”.'' ''The JACK realtime option should be enabled only if you have a kernel with the realtime patch.		We have seen that many playback problems while Renoise is using JACK are often related to JACK server settings. First of all try running the JACK server in non-realtime mode: to do this remove the -R option, if you run it on command-line, or - if you run qjackctl - uncheck the “Realtime” checkbox in “Setup” → “Settings”.'' ''The JACK realtime option should be enabled only if you have a kernel with the realtime patch.
Line 359:		Line 359:
	* The plugin is real-time capable but Renoise detected that it’s unstable (it crash Renoise if it tries to load it);		* The plugin is real-time capable but Renoise detected that it’s unstable (it crash Renoise if it tries to load it);

	'''Why Renoise ~~uses~~ the wrong in-/out- ports of my plugin?'''		'''Why is Renoise using the wrong in-/out- ports of my plugin?'''

	While connecting to a LADSPA plugin Renoise can’t detect which audio ports are REAL audio (left-/right-) inputs and which are REAL audio (left-/right-) outputs. So Renoise assumes the first two input audio ports are left-input and right-input and the first two output ports are left-output and right-output. LADSPA plugins are designed to be something like basic blocks for synthesizer modelling environments. That means a single plugin can do just only logic operations (ring modulation between two audio signal, produce an ADSR envelope when an input audio signal is over defined threshold, and so on) or the plugin expects more than two audio in to produce its output (think about surround processors). That’s why Renoise can list a LADSPA plugin which output has no sense at all.		While connecting to a LADSPA plugin Renoise can’t detect which audio ports are REAL audio (left-/right-) inputs and which are REAL audio (left-/right-) outputs. So Renoise assumes the first two input audio ports are left-input and right-input and the first two output ports are left-output and right-output. LADSPA plugins are designed to be something like basic blocks for synthesizer modelling environments. That means a single plugin can do just only logic operations (ring modulation between two audio signal, produce an ADSR envelope when an input audio signal is over defined threshold, and so on) or the plugin expects more than two audio in to produce its output (think about surround processors). That’s why Renoise can list a LADSPA plugin which output has no sense at all.
Line 369:		Line 369:
	=== Others ===		=== Others ===

	'''~~No-one of the above~~ FAQ ~~cover my problem/doubt~~. What I can do?'''		'''My question or problem is not addressed by anything in this FAQ. What I can do?'''

	Renoise features an active forum where you can ask your questions, so don’t hesitate to join in with [https://forum.renoise.com the community].		Renoise features an active forum where you can ask your questions, so don’t hesitate to join in with [https://forum.renoise.com the community].

Achenar at 15:06, 9 October 2019

2019-10-09T15:06:06Z

← Older revision		Revision as of 15:06, 9 October 2019
Line 166:		Line 166:
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	Since the VST specifications license isn’t compatible with GPL, it's possible to find VST plugins for Linux in a binary form. So, '''''always''''' check that the VST plugins you have installed [[#Renoise:_Checking_What.E2.80.99s_Wrong\|~~meets~~ all of their dependencies]].		Since the VST specifications license isn’t compatible with GPL, it's possible to find VST plugins for Linux in a binary form. So, '''''always''''' check that the VST plugins you have installed [[#Renoise:_Checking_What.E2.80.99s_Wrong\|meet all of their dependencies]].

	=== Plugins: Why Does Renoise Not List My Plugin? ===		=== Plugins: Why Does Renoise Not List My Plugin? ===

	Renoise cannot list your ~~plugins~~ for three reasons:		Renoise cannot list your plugin for three possible reasons:

	# ~~Your plugins aren’t~~ stored in any of the search ~~path~~ specified by the environment variables ~~(see the “Setting up third parties plugins” section about this)~~.		# The plugin [[#Setting_Up_Third_Party_Plugins\|isn’t stored in any of the search paths]] specified by the environment variables.
	# ~~Your~~ plugin ~~are~~ buggy ~~so they crashed~~ (possible causes can be unmet dependencies or real ~~buggy plugin~~)and Renoise ~~black-listed them~~.		# The plugin is buggy, causing it to crash (possible causes can be unmet dependencies or real errors in the code) and Renoise to blacklist it.
	# While ~~your~~ plugin is made on a Renoise ~~supported technology~~ and works with other hosts, Renoise never ~~list~~ it because ~~its~~ structure isn’t supported. This could happen, for example, with LADSPA plugins that have no audio ~~outputs~~ port or ~~which~~ are ~~not capable~~ of ~~Realtime~~ processing~~. Renoise never support them at the moment~~.		# While the plugin is made with a technology usually supported by Renoise and it otherwise works with other audio hosts, Renoise never lists it because the structure isn’t supported. This could happen, for example, with LADSPA plugins that have no audio output(s) port or are incapable of realtime processing.

	=== Plugins: My LADSPA Plugin is in the Wrong List ===		=== Plugins: My LADSPA Plugin is in the Wrong List ===

	Renoise always treats a LADSPA plugin as it ~~was~~ an effect, even when the plugin is a generator (e.g.: an oscillator). ~~Cause of~~ the LADSPA specification, Renoise cannot identify the mean of a plugin control port, so ~~it can’t say -~~ for example - which is the frequency control port or the trigger port. Also note that Renoise cannot ~~try~~ to guess the mean by matching a word in the port description.		Renoise always treats a LADSPA plugin as if it is an effect, even when the plugin is a generator (e.g. an oscillator). Due to the LADSPA specification, Renoise cannot identify the mean of a plugin's control port, and so is unable to, for example, tell which is the frequency control port or the trigger port. Also note that Renoise cannot attempt to guess the mean by matching a word in the port description.

	=== Renoise: Checking What’s Wrong ===		=== Renoise: Checking What’s Wrong ===

	~~You~~ have decompressed the archive~~, you~~ run the Renoise executable but nothing works~~. The~~ following instructions ~~can help you solving your problems~~. Open a terminal and ~~go into~~ the directory where you have decompressed Renoise ~~by typing the following~~:		If you have decompressed the downloaded archive and tried to run the Renoise executable, but nothing works, try the following instructions. Open a terminal and enter the directory where you have decompressed Renoise:

	: $ cd		: $ cd
Line 189:		Line 189:
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	~~Let’s look~~ if the Renoise executable links to all the required libraries~~. Type this command~~:		Now find out if the Renoise executable links to all of the required libraries:

	: $ ldd renoise		: $ ldd renoise
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	~~The~~ ldd command should ~~get~~ an output ~~like~~ this (~~if Renoise correctly finds all~~ the ~~required libraries~~):		If Renoise finds all the required libraries then the ldd command should respond with an output such as this (note that the numbers in brackets and the library paths are only examples; they will be different for you):

	* linux-gate.so.1 => (0xffffe000)		* linux-gate.so.1 => (0xffffe000)
Line 209:		Line 209:
	* libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7af9000)		* libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7af9000)

	With the exception of the libraries linux-gate.so.1 and /lib/ld-linux.so.2, all the other libraries ~~points~~ to a physical file located in the path on the right of the “=>” separator. If any of those libraries ~~has~~ no counterpart to a physical file ~~here’s a~~ problem ~~(NOTE: never care if your numbers between parenthesis or~~ the ~~library paths are different from mine). If some library has no counterpart to a physical file you can fix it in two ways~~:		With the exception of the libraries linux-gate.so.1 and /lib/ld-linux.so.2, all of the other libraries point to a physical file located in the path to the right of the => separator. If any of those libraries have no counterpart to a physical file, then this is the source of the problem, which may have one of the following solutions:
	# if you are ~~sure you have those~~ libraries correctly installed you must ~~be sure~~ that they ~~are on~~ the path;		# If you are certain that the libraries are correctly installed, you must check that they have actually been installed to the correct path.
	# ~~the~~ required libraries ~~aren’t~~ installed so you ~~have to~~ install them. ~~If you are in case 2 the following table~~ shows you in which package you can find the required libraries (package names are quite distro-specific, we will create documentation for all the ~~distro where~~ we have knowledge of):		# The required libraries are not installed, so you must now install them. The list below shows you in which package you can find the required libraries (package names are quite distro-specific; we will create documentation for all the distros that we have knowledge of):

	* Libraries librt.so.1, libdl.so.2, libpthread.so.0, libc.so.6 and libm.so.6 are available in the libc6 package		:* Libraries librt.so.1, libdl.so.2, libpthread.so.0, libc.so.6 and libm.so.6 are available in the libc6 package.
	* Library libasound.so.2 are available in the libasound2 package		:* Library libasound.so.2 are available in the libasound2 package.
	* Library libstdc++.so.6 are available in the libstdc++6 package		:* Library libstdc++.so.6 are available in the libstdc++6 package.
	* Library libgcc_s.so.1 are available in the libgcc1 package		:* Library libgcc_s.so.1 are available in the libgcc1 package.
	* Library libXau.so.6 are available in the libxau6 package		:* Library libXau.so.6 are available in the libxau6 package.
	* Library libXdmcp.so.6 are available in the libxdmcp6 package		:* Library libXdmcp.so.6 are available in the libxdmcp6 package.
	* Library libX11.so.6 are available in the libX11–6 package		:* Library libX11.so.6 are available in the libX11–6 package.
	* Packages libc6, libgcc1, libxau6 and libxdmcp6 are dependencies of the package xserver-xorg which is required to have the X.org graphical environment.		:* Packages libc6, libgcc1, libxau6 and libxdmcp6 are dependencies of the package xserver-xorg which is required to have the X.org graphical environment.
	* Package libasound2 is a dependency of the package alsa-utils which is installed to have the ALSA sound capabilities.		:* Package libasound2 is a dependency of the package alsa-utils which is installed to have the ALSA sound capabilities.

Achenar: /* Linux FAQ */

2019-10-09T14:34:41Z

Linux FAQ

← Older revision		Revision as of 14:34, 9 October 2019
Line 38:		Line 38:
	=== Checking the JACK Audio Capabilities ===		=== Checking the JACK Audio Capabilities ===

	Renoise can connect to a [[~~JACK~~ Transport]] server through different backends. At the time of writing, those supported are: ALSA, Core Audio, Port Audio, Free Bob, OSS and a 'dummy' backend. Please ensure that your chosen backend is correctly installed before continuing. To check if JACK is installed and working with your backend, open a terminal and type the following:		Renoise can connect to a [[Jack Transport]] server through different backends. At the time of writing, those supported are: ALSA, Core Audio, Port Audio, Free Bob, OSS and a 'dummy' backend. Please ensure that your chosen backend is correctly installed before continuing. To check if JACK is installed and working with your backend, open a terminal and type the following:

	: $ jackd -d your_backend —help		: $ jackd -d your_backend —help

Achenar at 14:32, 9 October 2019

2019-10-09T14:32:35Z

← Older revision		Revision as of 14:32, 9 October 2019
Line 132:		Line 132:
	If the result is a series of paths separated by ':', then the plugins were searched for within those directories. Check if your LADSPA plugins are stored in any of those directories. If the result is an empty line, this means the LADSPA_PATH variable hasn’t been set. In this case Renoise will look for plugins in the default paths, so you have to check if your LADSPA plugins are stored in any of those directories. If you have found that your LADSPA plugins aren’t stored in any of the search paths, you can proceed in three ways:		If the result is a series of paths separated by ':', then the plugins were searched for within those directories. Check if your LADSPA plugins are stored in any of those directories. If the result is an empty line, this means the LADSPA_PATH variable hasn’t been set. In this case Renoise will look for plugins in the default paths, so you have to check if your LADSPA plugins are stored in any of those directories. If you have found that your LADSPA plugins aren’t stored in any of the search paths, you can proceed in three ways:

	# Move your LADSPA plugins into any of the search paths.		* Move your LADSPA plugins into any of the search paths.

	# Add the path where you've stored your LADSPA plugins to the LADSPA_PATH environment variable. To do this, open a terminal and type the following:		* Add the path where you've stored your LADSPA plugins to the LADSPA_PATH environment variable. To do this, open a terminal and type the following:

	: $ echo LADSPA_PATH=/path/to/my/ladspa:\$LADSPA_PATH >> ~/.bash_profile		: $ echo LADSPA_PATH=/path/to/my/ladspa:\$LADSPA_PATH >> ~/.bash_profile
Line 141:		Line 141:
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	# Start Renoise with a custom LADSPA_PATH environment variable available only for that Renoise ~~run~~. To do this, open a terminal and type the following (this assumes that you have Renoise in the path):		* Start Renoise with a custom LADSPA_PATH environment variable available only for that Renoise session. To do this, open a terminal and type the following (this assumes that you have Renoise in the path):

	: $ LADSPA_PATH=/path/to/my/ladspa renoise		: $ LADSPA_PATH=/path/to/my/ladspa renoise
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	Setting up ~~the~~ VST plugins follows a procedure similar to LADSPA~~. There is~~ no real VST specifications for Linux so ~~we have chosen~~ an environment variable based solution. Renoise will look for VST plugins by searching in the paths stored in the VST_PATH environment variable. If the VST_PATH variable isn’t set, Renoise will default to the paths /usr/lib/vst, /usr/local/lib/vst and ~/.vst. To check the value of the VST_PATH open a terminal and type the following:		Setting up VST plugins follows a procedure similar to LADSPA, but there are no real VST specifications for Linux, so Renoise employs an environment variable based solution. Renoise will look for VST plugins by searching in the paths stored in the VST_PATH environment variable. If the VST_PATH variable isn’t set, Renoise will default to the paths /usr/lib/vst, /usr/local/lib/vst and ~/.vst. To check the value of the VST_PATH, open a terminal and type the following:

	: $ echo $VST_PATH<nowiki>[enter]</nowiki>		: $ echo $VST_PATH<nowiki>[enter]</nowiki>

	If the result is a series of paths separated by “:”, so the plugins were searched ~~into~~ those directories. Check if your VST ~~plugin~~ are stored in any of those directories. If the result is a empty line means VST_PATH variable ~~isn’t~~ set. In this case Renoise will look for ~~plugin~~ in the default paths, so you have to check if your VST plugins are stored in any of those directories. If you have found that your VST plugins aren’t stored in any of the search paths, you can proceed in three ways:		If the result is a series of paths separated by ':', then the plugins were searched for within those directories. Check if your VST plugins are stored in any of those directories. If the result is a empty line, this means the VST_PATH variable hasn’t been set. In this case Renoise will look for plugins in the default paths, so you have to check if your VST plugins are stored in any of those directories. If you have found that your VST plugins aren’t stored in any of the search paths, you can proceed in three ways:

	Move your VST plugins in any of the search paths.		* Move your VST plugins into any of the search paths.
	Add the path where you have stored your VST plugins to the VST_PATH environment variable. To do this open a terminal and type the following:
			* Add the path where you have stored your VST plugins to the VST_PATH environment variable. To do this, open a terminal and type the following:

	: $ echo VST_PATH=/path/to/my/vst:\$VST_PATH >> ~/.bash_profile		: $ echo VST_PATH=/path/to/my/vst:\$VST_PATH >> ~/.bash_profile
Line 160:		Line 161:
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	Start Renoise with a custom VST_PATH environment variable available only for that Renoise ~~run~~. To do this open a terminal and type the following:		* Start Renoise with a custom VST_PATH environment variable available only for that Renoise session. To do this, open a terminal and type the following (this assumes that you have Renoise in the path):

	: $ VST_PATH=/path/to/my/vst renoise		: $ VST_PATH=/path/to/my/vst renoise
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	(the ~~command above assumes that you have Renoise in the path)~~		Since the VST specifications license isn’t compatible with GPL, it's possible to find VST plugins for Linux in a binary form. So, '''''always''''' check that the VST plugins you have installed [[#Renoise:_Checking_What.E2.80.99s_Wrong\|meets all of their dependencies]].

	~~Because~~ VST specifications license isn’t compatible with GPL, is possible ~~you can~~ find VST plugins for Linux ~~only~~ in binary form. ~~ALWAYS~~ check if the VST ~~plugin~~ you have installed meets all ~~its~~ dependencies~~! (to make this check see the “Checking what’s wrong” section below)~~

	=== Plugins: Why Does Renoise Not List My Plugin? ===		=== Plugins: Why Does Renoise Not List My Plugin? ===

Achenar at 13:41, 9 October 2019

2019-10-09T13:41:35Z

← Older revision		Revision as of 13:41, 9 October 2019
Line 122:		Line 122:
	=== Jack Timeout Problems When Starting Renoise ===		=== Jack Timeout Problems When Starting Renoise ===

	When ~~starting up~~ Renoise~~, before starting Jack there are situations~~ where Jack shuts down immediately. ~~The source of~~ the ~~problem: When~~ Ubuntu software audio mixing (~~E Sound~~, ESD ~~Enlightment~~ Sound Daemon) is enabled, ALSA is always reported as being busy under Renoise. To fix this, disable the Esound mixing:system > preferences > sound ~~selecting~~ ALSA as device for everything, then ~~have disabled E Sound~~ mixing in the ~~“Devices”~~ tab. This ~~way~~ Pulse Audio ~~is totally bypassed~~ and can even be uninstalled. ~~Not~~ the cleanest solution, but works.		When launching Renoise you may encounter a situation where Jack shuts down immediately. This is caused by the fact that when Ubuntu software audio mixing (Esound, ESD Enlightenment Sound Daemon) is enabled, ALSA is always reported as being busy under Renoise. To fix this, disable the Esound mixing: "system > preferences > sound", select ALSA as the device for everything, then disable Esound mixing in the 'Devices' tab. This bypasses Pulse Audio (and can even be uninstalled). This is not exactly the cleanest solution, but it works.

	=== Setting Up Third Party Plugins ===		=== Setting Up Third Party Plugins ===

	Renoise supports LADSPA plugins and VST plugins compiled for Linux. ~~According~~ to the LADSPA specifications, Renoise will look for LADSPA plugins by searching in the paths stored in the LADSPA_PATH environment variable. If the LADSPA_PATH variable isn’t set, Renoise will default to the paths /usr/lib/ladspa, /usr/local/lib/ladspa and ~/.ladspa. To check the value of the LADSPA_PATH open a terminal and type the following:		Renoise supports both LADSPA plugins and VST plugins that have been compiled for Linux. Conforming to the LADSPA specifications, Renoise will look for LADSPA plugins by searching in the paths stored in the LADSPA_PATH environment variable. If the LADSPA_PATH variable isn’t set, Renoise will default to the paths /usr/lib/ladspa, /usr/local/lib/ladspa and ~/.ladspa. To check the value of the LADSPA_PATH, open a terminal and type the following:

	: $ echo $LADSPA_PATH [enter]		: $ echo $LADSPA_PATH [enter]

	If the result is a series of paths separated by “:”, so the plugins were searched ~~into~~ those directories. Check if your LADSPA ~~plugin~~ are stored in any of those directories. If the result is a empty line means LADSPA_PATH variable ~~isn’t~~ set. In this case Renoise will look for ~~plugin~~ in the default paths, so you have to check if your LADSPA plugins are stored in any of those directories. If you have found that your LADSPA plugins aren’t stored in any of the search paths, you can proceed in three ways: Move your LADSPA plugins in any of the search paths. Add the path where you ~~have~~ stored your LADSPA plugins to the LADSPA_PATH environment variable. To do this open a terminal and type the following:		If the result is a series of paths separated by ':', then the plugins were searched for within those directories. Check if your LADSPA plugins are stored in any of those directories. If the result is an empty line, this means the LADSPA_PATH variable hasn’t been set. In this case Renoise will look for plugins in the default paths, so you have to check if your LADSPA plugins are stored in any of those directories. If you have found that your LADSPA plugins aren’t stored in any of the search paths, you can proceed in three ways:

			# Move your LADSPA plugins into any of the search paths.

			# Add the path where you've stored your LADSPA plugins to the LADSPA_PATH environment variable. To do this, open a terminal and type the following:

	: $ echo LADSPA_PATH=/path/to/my/ladspa:\$LADSPA_PATH >> ~/.bash_profile		: $ echo LADSPA_PATH=/path/to/my/ladspa:\$LADSPA_PATH >> ~/.bash_profile
Line 137:		Line 141:
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	Start Renoise with a custom LADSPA_PATH environment variable available only for that Renoise run. To do this open a terminal and type the following:		# Start Renoise with a custom LADSPA_PATH environment variable available only for that Renoise run. To do this, open a terminal and type the following (this assumes that you have Renoise in the path):

	: $ LADSPA_PATH=/path/to/my/ladspa renoise		: $ LADSPA_PATH=/path/to/my/ladspa renoise
	: <nowiki>[enter]</nowiki>		: <nowiki>[enter]</nowiki>

	~~''(the command above assumes that you have Renoise in the path)''~~

	Setting up the VST plugins follows a procedure similar to LADSPA. There is no real VST specifications for Linux so we have chosen an environment variable based solution. Renoise will look for VST plugins by searching in the paths stored in the VST_PATH environment variable. If the VST_PATH variable isn’t set, Renoise will default to the paths /usr/lib/vst, /usr/local/lib/vst and ~/.vst. To check the value of the VST_PATH open a terminal and type the following:		Setting up the VST plugins follows a procedure similar to LADSPA. There is no real VST specifications for Linux so we have chosen an environment variable based solution. Renoise will look for VST plugins by searching in the paths stored in the VST_PATH environment variable. If the VST_PATH variable isn’t set, Renoise will default to the paths /usr/lib/vst, /usr/local/lib/vst and ~/.vst. To check the value of the VST_PATH open a terminal and type the following:

Achenar at 13:22, 9 October 2019

2019-10-09T13:22:31Z

← Older revision		Revision as of 13:22, 9 October 2019
Line 112:		Line 112:
	=== Performance Problems ===		=== Performance Problems ===

	Audio performance problems can occur in Linux for a variety of reasons. Some of the symptoms include: crackling/stuttering audio, audio with noise, or excessive Xruns. ~~There is a class of luxury~~ window managers ~~like~~ Compiz and Beryl ~~that~~ consume ~~a hell of~~ a lot of priority time from your CPU resources. Some users have reported drastically improved performance when shutting these options down~~. If~~ you ~~want the best audio~~ performance it is recommended ~~not~~ to ~~use these type of compositing window managers, instead~~ use a lighter window manager ~~like~~ Openbox. ~~Consult~~ the documentation of your Linux distribution ~~and the Linux community on how to modify your distribution for best-audio performance. [http://www.renoise.com/board/index.php?showtopic=27618 More information and ongoing discussion]~~.		Audio performance problems can occur in Linux for a variety of reasons. Some of the symptoms include: crackling/stuttering audio, audio with noise, excessive Xruns etc. Luxury window managers such as Compiz and Beryl consume a lot of priority time from your CPU resources. [http://www.renoise.com/board/index.php?showtopic=27618 Some users have reported] drastically improved performance when shutting these options down, so if you're encountering performance issues it is recommended to use a lighter window manager such as Openbox instead. For further information on audio performance, please consult the documentation (and community) of your particular Linux distribution.

	=== Performance Problems With HDA/Intel Soundcards ===		=== Performance Problems With HDA/Intel Soundcards ===

	~~A lot of various~~ laptops ~~are geared with~~ an HDA/Intel soundcard ~~and~~ their buffering capabilities ~~seem to be less~~ than ~~the average soundcard~~. If you have such a soundcard, ~~then you will have~~ to set the period amount for the ALSA driver in the Renoise preferences to 3 periods. ~~If your~~ Renoise version ~~is lower than version~~ 2.0, ~~you are~~ recommended to upgrade~~. In Renoise <= 1.9.1, you~~ can only ~~use Renoise decently~~ with ~~such a soundcard~~ by ~~setting up~~ the Jack deamon ~~and setting~~ the periods/buffer to 3 ~~in the Jack configuration~~.		Many laptops feature an HDA/Intel soundcard, but their buffering capabilities are lower than those of other cards. If you have such a soundcard, it is recommended to set the period amount for the ALSA driver in the Renoise preferences to 3 periods.

			For users of [[Jack Transport]] who are also still using Renoise at a version below 2.0, it is recommended to upgrade since older versions can only achieve decent performance with these soundcards by using the Jack deamon to set the periods/buffer to 3.

	=== Jack Timeout Problems When Starting Renoise ===		=== Jack Timeout Problems When Starting Renoise ===

	When starting up Renoise, before starting Jack there are situations where Jack shuts down immediately. The source of the problem:When Ubuntu software audio mixing (E Sound, ESD Enlightment Sound Daemon) is enabled, ALSA is always reported as being busy under Renoise. To fix this, disable the Esound mixing:system > preferences > sound selecting ALSA as device for everything, then have disabled E Sound mixing in the “Devices” tab. This way Pulse Audio is totally bypassed and can even be uninstalled. Not the cleanest solution, but works.		When starting up Renoise, before starting Jack there are situations where Jack shuts down immediately. The source of the problem: When Ubuntu software audio mixing (E Sound, ESD Enlightment Sound Daemon) is enabled, ALSA is always reported as being busy under Renoise. To fix this, disable the Esound mixing:system > preferences > sound selecting ALSA as device for everything, then have disabled E Sound mixing in the “Devices” tab. This way Pulse Audio is totally bypassed and can even be uninstalled. Not the cleanest solution, but works.

	=== Setting Up Third Party Plugins ===		=== Setting Up Third Party Plugins ===