The Frequently Asked Questions of LibraZiK
This page is a compilation of frequently asked questions.
Debian is used as a basis for LibraZiK thanks to its social contract, its large community, its stability, its robustness, and its performance.
Certainly because no one reported it! 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 be in LibraZiK, come and tell.
This is certainly because:
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:
lscpu | grep -i "mode(s)"
.grep flags /proc/cpuinfo
. This will give you “flags” that reflect the capabilities of the machine's processor, and therefore, the machine itself:
ISO LZK-3 name | corresponding md5sum |
---|---|
librazik3-20201104-fr-amd64.iso | a691608b89f03c688a14f7698c6fa4a5 |
librazik3-20201104-en-amd64.iso | c21b8b0803f27afd71e7563daa729991 |
ISO LZK-2 name | corresponding md5sum |
---|---|
librazik2-32bits-20190702.iso | 1b0c84cd72cc115dc8755df4ba19152a |
librazik2-64bits-20190702.iso | 1b4b7a8eccbc0524f113dc729c7fe8fc |
librazik2-64bits-20181115.iso | 758459dc0deee34bc8668eb040b117a7 |
librazik2-32bits-20181115.iso | 928f87a729b1558a3369d17edef473d2 |
librazik2-64bits-20180120.iso | 89c625386a72e9695bb24e9834e5e5ba |
librazik2-32bits-20180120.iso | 9a433353109ae972888673f3c9c2089d |
librazik2-64bits-20171028.iso | d0e09935073b15476fcfa3aa5de2a00d |
librazik2-32bits-20171028.iso | 82fbec18d07408e50376ba06df8ca64b |
ISO LZK-1 name | corresponding md5sum |
---|---|
librazik-64bits-20160703.iso | e851a434236ba4453cf228cdc650116a |
librazik-32bits-20160703.iso | 255d5f0ed32b22117cf766598b760fcf |
librazik-64bits-20160429.iso | dfb5e27ab48c6e77aae00c12bd8f4350 |
librazik-32bits-20160429.iso | f3d3fe318e47fc127e6c8f5e6b89e7d4 |
librazik-20160208.iso | bdf5918cdb048999617104a73d9b04fc |
librazik-20160107.iso | 2ac4c4b15915e978f62e8190ab627edd |
librazik-20151231.iso | f431af761ce9defc1a2317b0f6858cdb |
librazik-20151207.iso | ecb7c0b70dd7670240963f7d0e6383db |
librazik-20151124.iso | 6f3ce36e017ecdf27098d1defe7dd217 |
librazik-20151104.iso | 3c90b626001f1cb6981993142673f00d |
librazik-20150912-0019-2.iso | 8829b140fcbe0d4893ee0396a2d3370c |
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 might work, like the menu layout. The LibraZiK documentation is based on this layout in MATE, so you will have to intellectually adapt the LibraZiK documentation. Finally, it is advised not to remove what concerns MATE because this could remove several functionalities of LibraZiK which 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 :
start-pulseaudio-x11
by pulseaudio --start
,
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, then using LibraZiK-3 (which exists as a live, or even in live persistent) should be of interest.