Debian is used as a basis for LibraZiK thanks to its social contract, its large community, its stability, its robustness, and its performance.

1. this is partly the case
2. the LibraZiK project packages some softwares :
   1. in newer version than the one provided by Debian
   2. not being in Debian
3. the LibraZiK project provides optimizations :
   1. being too specific to audio-production to be integrated in Debian
   2. being too biased to be integrated into Debian

Certainly because no one reported it to the packaging team. LibraZiK contains several hundreds of software dedicated to music. It is difficult, if not impossible, to keep track of everything. If you see a software in an “old” version on LibraZiK when there is a newer version and you think it should deserve to be in LibraZiK, come and participate in the LibraZiK project by reporting it.

This is certainly because:

• it does not respect one of the criteria to enter LZK
• no one reported it (see above)
• there are difficulties in providing it
• …etc.

In any case, if you have any questions about this, come talk.

This is a security principle and LibraZiK sticks to it. Indeed, LibraZiK does not know under which conditions you will use the system. Will it be a family computer shared between several people? A self-service machine in a music school? Your personal laptop? There is no way to know in advance. The choice is therefore made by default to make it as if it were going to be self-service in a music school for example and therefore with the potential to have several users.

If this behavior annoys you and you would prefer to be automatically identified as a user when the machine starts, you can modify the configuration by following this documentation.

If your machine is a 64-bit machine, then it is more interesting to use a 64-bit system on it to take advantage of the optimizations of this capacity, such as the ability to manage a large memory capacity. However, you should know that you can use a 32-bit system on a 64-bit machine.

If your machine is a 32-bit machine, then you must use a 32-bit system on it. Using a 64-bit system on this type of machine will not work (you won't even be able to install it).

There are several possibilities for this:

• in general : you can consult the manual of your machine.
• on GNU/Linux (1) : another possibility, very fast, is to use the following command in a terminal: lscpu | grep -i "mode(s)".
• on, GNU/Linux (2) : you can use, in a terminal, the command: grep flags /proc/cpuinfo. This will give you “flags” that reflect the capabilities of the machine's processor, and therefore, the machine itself:
  • the flag “lm” means “Long Mode CPU” → the processor is able to work in 64 bits
  • the flag “tm” means “Protected mode” → the processor is able to work in 32 bits
  • the flag “rm” means “Real Mode” → the processor is able to work in 16 bits
  • so, if you have the “lm” flag, this means that you can use a 64 bits system since your hardware has this capability
• on Windows © : go to the “General” tab of the “Start” menu and then go to: → Control Panel → System where you will be given information about your processor.

MATE is the default desktop environment of choice for LibraZiK. It was chosen because it is a good compromise between lightness, performance, stability, engineering intelligence and ergonomics. It is a good choice, and it is very strongly recommended to keep it.

If you wanted to use LibraZiK with another desktop environment, be aware that not everything may work, such as the menu layout. Since LibraZiK's documentation is based on this layout in MATE, you will need to mentally adapt LibraZiK's documentation accordingly. Finally, it is advisable not to remove anything related to MATE, as this could remove several features of LibraZiK that depend on it.

Before leaving you, don't forget that if you tinker with your LibraZiK, you must assume what you do, “you have been warned!”

PulseAudio may not launch at startup. Don't worry.

In such a case :

1. go to: LZK menu → System → Preferences → Personal → Startup applications
2. then, in the Programs at startup tab, select the PulseAudio sound system line,
3. then click on the Modify button,
4. in the line Command, replace start-pulseaudio-x11 by pulseaudio --start,
5. click on Save,
6. click on the Close button.

At the next startup, PulseAudio will be launched automatically.

It is commonly accepted that below 20ms, a musician can start playing “in real time” effectively without being bothered with an echo effect. However, it is only below 10ms that this does not really affect the musician's playing and therefore allows him to be comfortable. Some audio interfaces can allow you to go lower in latency, others not. For information about the capabilities of audio interfaces, please refer to the manuals of these interfaces and look on the internet.

Claudia and LADISH are dropped in favor of RaySession and NSM. If you have a need for a Claudia session, you would need to use the old LibraZiK-3, which was developed between 2020 and 2022. Please contact us.