As a studio muscian, sideman, touring musician for the last 50 years I've had numerous instances where I've needed to digitize, tweak, remaster, etc. audio files whether recorded by me or from media given to me from the venues I've played in. Other than that, I create audio/visual material for a number of university profs and lecturers who are doing online courses and require help.
All of this work is done (now and in the past) on my rigs that utilize a Linux OS and FOSS software included in the standard repos. Since 2017, I've been using MX Linux as my daily driver. The present iteration (MX-23) has everthing I need to perform my audio/visual tasks. Exceptions from what I can install from Synaptic (e.g., Ardour, Audacity, Ladspa Plugins, LMMS, LV2 Plugins, Qsynth, Qjackctl, Rosegarden) would be recent AppImages (Shotcut, CinelerraGG, Qtractor, Avidemux, Krita, Kdenlive, Musescore) along with Reaper on Wine-Staging with a few Vsts mostly Reverbs, Compression, and Mastering (all freeware .dlls). Absolutely no reason to use anything from MX's Test Repos unless you need better Firewire support, then install ALL the Pipewire, Wireplumber, and Qpwgraph upgrades from the MX Pkg. Manager Test Repos ... Long-story-short, it's easy-peasy rolling your own MX multimedia provisions. For me everything just works, the only caveat being Ardour not being able to use Jack (as GMaq points out, use ALSA as the back-end). Qtractor (latest AppImage), Qsynth, Rosegarden, function perfectly with Qjackctl.
Given that a user is already familiar with MX Linux, and that their hardware flawlessly supports it, there's no reason whatsoever for someone not to be able to roll their own multimedia workhorse.
Now to AVLinux ... GMaq has done an incredible job (actually, a herculean task!) in presenting the functionality of using Pipewire and also Qpwgraph as an alternative to Qjackctrl. This is an important and gargantuan step to take insofar as PW is the future Linux sound-server. His is the ONLY multimedia Distro to have come to grips with this innovation. With the dated version of PW in MX-23 that he had to work with, it is quite remarkable. For many seasoned music-creators with compatible rigs, the system works perfectly OOTB. For others, there seem to be many problems as witnessed here as well as in the LinuxMusicians Forum. Given the fact that MX-23 has an EOL of 2028, GMaq would have plenty of time to reckon with the most recent version of PW for better all-round support, including Jack. Maybe it just might cure Ardour-Jack woes insofar as some users need to stream audio/visual creations from Ardour.
On the other hand, I agree that there is simply too much bloat with GMaq's latest creation due to the inclusion/intrusion of commercial demo-ware. Unnecessary, except for the fact that he seems to want to demo his configuration prowess, e.g. using Yadbridge to implement Win-Vsts in a Linux-based environment. You don't need all those examples to make your point! Mixbus? Reaper Linux-Beta? Total overkill ... a huge ISO. Then there's his idiosyncratic, personal choice of the Enlightenment desktop (MX gives you Fluxbox as a lightweight alternative). OK, his is a Re-spin and he'll say "...if it doesn't suit you, don't use it...". I agree, but, apparently, it doesn't suit a lot of folks from all the posts (not just here) that I've looked at. Some just try it then scrap it, others perform a massive clean-up to get rid of stuff they don't want/need.
Finally, there's absolutely no need for "What about a regular MX Linux with AV Linux config?". Seasoned audiophiles should and could roll their own ... and to this end, I would be glad to help.
What about a regular MX Linux with AV Linux config?
Re: What about a regular MX Linux with AV Linux config?
Hi,
Perhaps @Zeke and @Karl Marx have missed the 1-click "Demoremove" menu option to remove all non-FOSS Recording Applications and Plugins, yes I included a lot of choices and still remained mindful of making it VERY easy to run a FOSS version if that's what the User prefers..
Zeke, I didn't really enjoy your passive aggressive pat-on-the-back-with-one-hand-and-slap-to-the-face-with-the-other routine at Linuxmusicians.com and I enjoy it less here..
If you're happy with Vanilla MX, that's wonderful but then there is no reason to post in this thread other than to again point out (somewhere new) that you don't like AV Linux. You say there is no need to make a Vanilla MX with Audio performance tweaks and then say people should "roll their own" and you will be "glad to help"...?
If this idea is so useless what is there to be rolling or helping with? The whole idea of the thread is basically to do exactly what you are talking about so I'm very confused about WTF your point is...?
Perhaps @Zeke and @Karl Marx have missed the 1-click "Demoremove" menu option to remove all non-FOSS Recording Applications and Plugins, yes I included a lot of choices and still remained mindful of making it VERY easy to run a FOSS version if that's what the User prefers..
Zeke, I didn't really enjoy your passive aggressive pat-on-the-back-with-one-hand-and-slap-to-the-face-with-the-other routine at Linuxmusicians.com and I enjoy it less here..
If you're happy with Vanilla MX, that's wonderful but then there is no reason to post in this thread other than to again point out (somewhere new) that you don't like AV Linux. You say there is no need to make a Vanilla MX with Audio performance tweaks and then say people should "roll their own" and you will be "glad to help"...?
If this idea is so useless what is there to be rolling or helping with? The whole idea of the thread is basically to do exactly what you are talking about so I'm very confused about WTF your point is...?
Re: What about a regular MX Linux with AV Linux config?
Obviously GMaq's frustration is apparent. Not only is my post misread as an attack, but the claim is made that "The whole idea of the thread is basically to do exactly what you are talking about so I'm very confused about WTF your point is...?". This is a very wrong assertion. My claim is that it is NOT necessary to implement any of the Extras he proposes if one decides to use a Vanilla MX-23. As I've said, the roll-your-own option doesn't require these additions ... everything just works without them. That's what I am talking about ... and it's quite different than what he wants to do. Is he still confused? If so, he should feel free to respond without abbreviated profanities please. It's not appreciated by me nor by anyone else in a public forum.
It would serve people better here if GMaq would specify, in detail, what he means by add-ons like:
(1) "Liquorix Kernel" --- one size doesn't fit all. On MX-23, In my specific hardware case, I found that Liquorix v.6.3.9 functions better than higher releases. I did have to experiment a bit to get the right match. Many users on this Forum have had to do the same depending on their hardware. BTW, antix-5.10.197 kernel performs just as well regarding latency. Again, I repeat, one size doesn't fit all! Right there is a big minus for this so-called tweak. Same goes for the latest AVLinux-MXE. I guess GMaq never thought about that!
(2) "AV Linux performance configurations" and to what extent, if any, would they be useful?
(3) "AV Linux utilities and helper scripts" (YADbridge, Wine-Audio-Utils, Sysedit) --- Why? Not necessary when rolling your own simple setup. Native Linux plugins (Ladspa, LV2, etc., are more than enough to get you covered.
Not all are familiar with aspects of these proposals and I think that they require elucidation so as to receive more enightened
feedback.
P.S.
I am not interested in a back-and-forth with GMaq. I only want to reiterate that he created his AVLinux-MXE 23 for himself and shares it with others. That's admirable. Yet the feedback, here and elsewhere, has proven that not all are happy with it for various reasons. He knows/admits that; therefore, he initiated this thread. Quite transparent, but doesn't seem to appreciate my critiques or suggestions. Too bad ...
Wishing GMaq a fruitful hiatus from all of this. Lots to do on the farm as well as his music performances. Be well!
It would serve people better here if GMaq would specify, in detail, what he means by add-ons like:
(1) "Liquorix Kernel" --- one size doesn't fit all. On MX-23, In my specific hardware case, I found that Liquorix v.6.3.9 functions better than higher releases. I did have to experiment a bit to get the right match. Many users on this Forum have had to do the same depending on their hardware. BTW, antix-5.10.197 kernel performs just as well regarding latency. Again, I repeat, one size doesn't fit all! Right there is a big minus for this so-called tweak. Same goes for the latest AVLinux-MXE. I guess GMaq never thought about that!
(2) "AV Linux performance configurations" and to what extent, if any, would they be useful?
(3) "AV Linux utilities and helper scripts" (YADbridge, Wine-Audio-Utils, Sysedit) --- Why? Not necessary when rolling your own simple setup. Native Linux plugins (Ladspa, LV2, etc., are more than enough to get you covered.
Not all are familiar with aspects of these proposals and I think that they require elucidation so as to receive more enightened
feedback.P.S.
I am not interested in a back-and-forth with GMaq. I only want to reiterate that he created his AVLinux-MXE 23 for himself and shares it with others. That's admirable. Yet the feedback, here and elsewhere, has proven that not all are happy with it for various reasons. He knows/admits that; therefore, he initiated this thread. Quite transparent, but doesn't seem to appreciate my critiques or suggestions. Too bad ...
Wishing GMaq a fruitful hiatus from all of this. Lots to do on the farm as well as his music performances. Be well!
Re: What about a regular MX Linux with AV Linux config?
AVLinux wrote: Wed May 08, 2024 9:53 pm Hi,
Perhaps @Zeke and @Karl Marx have missed the 1-click "Demoremove" menu option to remove all non-FOSS Recording Applications and Plugins, yes I included a lot of choices and still remained mindful of making it VERY easy to run a FOSS version if that's what the User prefers..
Zeke, I didn't really enjoy your passive aggressive pat-on-the-back-with-one-hand-and-slap-to-the-face-with-the-other routine at Linuxmusicians.com and I enjoy it less here..
If you're happy with Vanilla MX, that's wonderful but then there is no reason to post in this thread other than to again point out (somewhere new) that you don't like AV Linux. You say there is no need to make a Vanilla MX with Audio performance tweaks and then say people should "roll their own" and you will be "glad to help"...?
If this idea is so useless what is there to be rolling or helping with? The whole idea of the thread is basically to do exactly what you are talking about so I'm very confused about WTF your point is...?
Thanks for your replay.
1. First of all, I'm pretty sure that I made some points, that are somehow different from that, what Mr. Zeke wrote. No, I did not miss the 1-click "Demoremove"! That's precisely the reason why I mentioned the opt-in and the opt-out variants. The first one is just more the GNU/Linux-Way that respects your freedom, and the second one is not. You are long enough around to remember what happened, when Ubuntu came whit telemetry enabled per default, although the user could opt out of it? Well the GNU/Linux-Community did not like it, and for good reasons! Same whit Audacity after the akquisition. Well, some how the case of AVLinux is not that different and for sure even more problematic. In your replay you did not really address the issue.
2. You did not say anything about the contradiction between Enlightenment, witch relies heavy on systemd, and the fact, that MX-Linux is somehow a distro for people who don't really like it, or are even strongly opposed to it. Where is the above part from MX-Linux in AVLinux-MXE, that seams to be important for MX-Linux makers and users?
3. You must have overlooked my other remark, about all the software, that is FOSS in itself, but serves only one purpose: To allow users to use, proprietary, non-free software. This means that WINE, Wine-Audio-Utils and YADBridge, are also packages for the non-free user, that are pushed on every-user. Every unnecessary line of code, software package, or evil proprietary program is a potential problem, resources hog or security risk.
4. My last Point -> To use, or promote non-free software is, in my mind, somehow contra-productive and not really the FOSS-GNU/Linux-Way.
Why support, or use proprietary software, when the software makers, are not really interested to support you, the FOSS-user? They just don' care. And lets be honest, the philosophy behind GNU/Linux stands for free (as in freedom) licenses, and for good reasons. I don't get it. Why waste resources, time and money on products and corporations, that do not live up to the FOSS-standards? Isn't it better to support only software makers that respect your freedom?
Even native software like Reaper, Bitwig, Waveform etc. is not free. Every second spend on non-free solutions, is wasted and missed on the free side. Isn't it?
Just my 2 cents.
Greetings :-)
Re: What about a regular MX Linux with AV Linux config?
@Karl Marx
You make a lot of assumptions about my motivations and you also project a lot of your own ideas about an established "FOSS GNU Linux way" that I am somehow being antagonistic toward and "not respecting people's freedom"...
Of course you are entitled to your opinions and entitled to share them here, but they are in the end your opinions...
You could also argue I am being ultimately respectful of people's freedom by allowing them all possible choices to use a Production Studio based on Linux with all technologies that are available to make it as functional and comparable to other Production platforms. AV Linux has featured closed source Applications and Plugins almost since it began in 2008, I had Reaper (with Wine), energyXT and linuxDSP Plugins included for many years before now so it has always been obvious AV Linux has always embraced the excellence of FOSS and combined it with carefully selected closed-source software based on User requests and the real world needs of those intending to do unlimited world-class production on a Linux system. The notion that software is "evil" merely because it's source code is not publicly accessible is once again an opinion not reality, indeed the biggest recent threat to Linux was via malicious Linux code in the Open-Source XZ compression library... which demonstrates that code is code and it can be employed maliciously or beneficially regardless of it's source and secondly the malicious XZ code was right there in the open to the project developers and even that did not guarantee User safety.
As far as MX Linux and Enlightenment's requirement of systemd... I am not under the official umbrella of MX variants, I am a friend and supporter to the MX project using it's build toolchain, I as an arms-length entity do not have an official mission statement promising full functionality with all potential init systems, AV Linux simply uses what init systems are necessary to support the Operating system as presented and in the most recent version systemd is the best solution due to the requirements of the Enlightenment Desktop Environment..
I am completely non-partisan about FOSS vs. Proprietary, Linux vs. Windows or OSX, sysvinit vs. systemd and all related arguments, since AV Linux is a freely provided product with absolutely no implied guarantee I am not beholden to adhere to or embrace any political software ideology and I am not impinging on anyone's freedom since they have full freedom of choice to ignore or evaluate AV Linux at their discretion.
It is clearly not a FOSS-only product and there is no goal to make it so, it will use whatever init system makes the most operational sense and there is no goal to change that. If you want a completely FOSS system to create a production Studio and you insist on not using systemd then it really sounds like the antiX project is exactly the type of thing that will be to your liking in many ways!
You make a lot of assumptions about my motivations and you also project a lot of your own ideas about an established "FOSS GNU Linux way" that I am somehow being antagonistic toward and "not respecting people's freedom"...
Of course you are entitled to your opinions and entitled to share them here, but they are in the end your opinions...
You could also argue I am being ultimately respectful of people's freedom by allowing them all possible choices to use a Production Studio based on Linux with all technologies that are available to make it as functional and comparable to other Production platforms. AV Linux has featured closed source Applications and Plugins almost since it began in 2008, I had Reaper (with Wine), energyXT and linuxDSP Plugins included for many years before now so it has always been obvious AV Linux has always embraced the excellence of FOSS and combined it with carefully selected closed-source software based on User requests and the real world needs of those intending to do unlimited world-class production on a Linux system. The notion that software is "evil" merely because it's source code is not publicly accessible is once again an opinion not reality, indeed the biggest recent threat to Linux was via malicious Linux code in the Open-Source XZ compression library... which demonstrates that code is code and it can be employed maliciously or beneficially regardless of it's source and secondly the malicious XZ code was right there in the open to the project developers and even that did not guarantee User safety.
As far as MX Linux and Enlightenment's requirement of systemd... I am not under the official umbrella of MX variants, I am a friend and supporter to the MX project using it's build toolchain, I as an arms-length entity do not have an official mission statement promising full functionality with all potential init systems, AV Linux simply uses what init systems are necessary to support the Operating system as presented and in the most recent version systemd is the best solution due to the requirements of the Enlightenment Desktop Environment..
I am completely non-partisan about FOSS vs. Proprietary, Linux vs. Windows or OSX, sysvinit vs. systemd and all related arguments, since AV Linux is a freely provided product with absolutely no implied guarantee I am not beholden to adhere to or embrace any political software ideology and I am not impinging on anyone's freedom since they have full freedom of choice to ignore or evaluate AV Linux at their discretion.
It is clearly not a FOSS-only product and there is no goal to make it so, it will use whatever init system makes the most operational sense and there is no goal to change that. If you want a completely FOSS system to create a production Studio and you insist on not using systemd then it really sounds like the antiX project is exactly the type of thing that will be to your liking in many ways!
Re: What about a regular MX Linux with AV Linux config?
Hi. After two trials (January and April versions) and 2 weeks after installation on the hard drive, I have to agree with the criticism in the technical area. On a computer where it has been going for more than 2 years, the AV version of Linux with OpenBox (see below for details) is a highly unstable system. It's not even about the new desktop environment, because it's a matter of taste, you know. Probably to some extent it's a matter of getting used to it, and probably after a month of daily use most would have a different outlook. It's simply that it's a system that is, at the moment, a negation of a work-ready system. I had to spend an entire day fixing problems with certificates, with authorization, with strange behaviour of windows, and I was still left with many unexpected issues. Simply put, once something works, and other times without making any changes to the software it crashes. This is indicative of the instability and probably not completely successful fusion of MX Linux with the new environment as a universal system for any machine.
The system wants to log in, by the way, only from the version with Systemd, but still with problems. Sometimes it crashes after logging in, and almost always I have to log in twice to get to the desktop environment. The system with automatic login in me does not work completely. Making a live version from a snapshot doesn't work either. The system does not log in. Which is a serious drawback of losing the functionality of MX Linux and Antix.
From my point of view, you should answer Yourself whether you want to create a system for others or for yourself and share it with others. If for yourself then understand it perfectly and I have no complaints. I am very grateful. I have been using for more than two years for audio production. Mainly podcast.
However, if for others then in my opinion it would be better to simply stay on the environment supported by the entire MX Linux community and AV Linux would just be a regular respin. In such a situation it would be much faster to solve any problems, and also the system itself would be universal and stable. After all, in a system designed for specific music applications, it's not so much about the looks of the environment, but the functionality and, above all, the lack of reliability and quick troubleshooting after getting help.
If you would like to further develop the project in the direction of being universal for others then I would be happy to install it experimentally on a second disk and present you with all the problems I have found.
I personally use the Open Box version all the time. It is incredibly stable. If nothing happens by the end of MX 21 release support, I guess I'll have to switch to something else like Ubunto Studio.
-Computer- DELL OPTIPLEX 7020
Processor : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Memory : 16287MB (1811MB used)
Machine Type : Space-saving
Operating System : Debian GNU/Linux 11 (bullseye)
The system wants to log in, by the way, only from the version with Systemd, but still with problems. Sometimes it crashes after logging in, and almost always I have to log in twice to get to the desktop environment. The system with automatic login in me does not work completely. Making a live version from a snapshot doesn't work either. The system does not log in. Which is a serious drawback of losing the functionality of MX Linux and Antix.
From my point of view, you should answer Yourself whether you want to create a system for others or for yourself and share it with others. If for yourself then understand it perfectly and I have no complaints. I am very grateful. I have been using for more than two years for audio production. Mainly podcast.
However, if for others then in my opinion it would be better to simply stay on the environment supported by the entire MX Linux community and AV Linux would just be a regular respin. In such a situation it would be much faster to solve any problems, and also the system itself would be universal and stable. After all, in a system designed for specific music applications, it's not so much about the looks of the environment, but the functionality and, above all, the lack of reliability and quick troubleshooting after getting help.
If you would like to further develop the project in the direction of being universal for others then I would be happy to install it experimentally on a second disk and present you with all the problems I have found.
I personally use the Open Box version all the time. It is incredibly stable. If nothing happens by the end of MX 21 release support, I guess I'll have to switch to something else like Ubunto Studio.
-Computer- DELL OPTIPLEX 7020
Processor : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Memory : 16287MB (1811MB used)
Machine Type : Space-saving
Operating System : Debian GNU/Linux 11 (bullseye)
Re: What about a regular MX Linux with AV Linux config?
Apologies first: I am off topic
A simple question !
Is there "" somewhere "" an AVLinux edition with XFCE I can download.
I do not want the E edition ( not for technical , but private reasons )
Thanks
A simple question !
Is there "" somewhere "" an AVLinux edition with XFCE I can download.
I do not want the E edition ( not for technical , but private reasons )
Thanks
-
MelodyNaive
- Posts: 18
- Joined: Sat Jan 20, 2024 2:53 pm
Re: What about a regular MX Linux with AV Linux config?
@Tony45
I came here looking for same. But so far I have used MX23 with xfce. I have ardour7 from the repo & ardour 8 from AVLinux's index of packages. Both work. I installed pipewire from the repo & the pipewire-setup-mx (or something similar u'll know it when u see it). Removed Jack & pulseaudio. Installed the latest Liquorix kernel, then one came out since & I installed that. I used from his index of packages, the realtime quick scan. On all the places it said i needed improvement, I was easily able to figure out how to get a check mark for each one. I asked chatgpt3.5, the free one without login, to ask how to do some of the things. I had Xs on several but now I have 12/13 in good standing.
Right now my ardour with pipewire (actuallly select jack in ardour becuz ardour does not show pipewire, but I'm deff using pw as jack is uninstalled & there's a pipewire package that serves to pretend it's jack to applications) is set at 128 samples buffersize, & 48khz rate. I have 2.7ms latency with no xruns. That's only messing around with a mic thru an audio interface into ardour & listening to input & playback to see if it works.
Idk if I'll use vst plugins but I installed the wine audio utilities from his index of custom packages. It opens from the MX menu but selecting options like settings, configuration & Run WineASIO do nothing. I typed wine (tab completed wineasio64) in a terminal& it said it was running then to close the terminal. Idk what that means. I'm wondering if the repo packages wineasio-amd64 will serve teh purpose of making the plugins work, but I think I'll just forgo them for now. Tho come to think of it, the terminal command was wineasio64 so maybe that's what the utility is, plus it has a config & a settings option. So that package is wortha try.
I spent an hour on that avlinux desktop that starts with an E (I forgot the name). I couldn't stand it, trying to use the interfaces to customize. It was so buggy too. Like I selected a window theme, then the title bars of windows started sliding off the window frame lol.
MX23, MintDebian with Cinnamon, both work great on this laptop. I'd successfully recorded using the Mint I have installed on it with Audacity. Not for music so wasn't looking at quality issues, but it worked fine with no set up, just plugged my Behringer umc404 interface in & it worked. So I think the laptop is plenty good enuf. But I really tried to be patient even tho I instantly hated it, but that environment was killing me. I even logged out & logged back in with openbox that it comes with & was instantly relieved. U can use tasksel to install other desktops on it, but I only spent a brief time with mate & a couple others before I was tired, then woke up to decide I'd use MX23 with XFCE which is already great.
I came here looking for same. But so far I have used MX23 with xfce. I have ardour7 from the repo & ardour 8 from AVLinux's index of packages. Both work. I installed pipewire from the repo & the pipewire-setup-mx (or something similar u'll know it when u see it). Removed Jack & pulseaudio. Installed the latest Liquorix kernel, then one came out since & I installed that. I used from his index of packages, the realtime quick scan. On all the places it said i needed improvement, I was easily able to figure out how to get a check mark for each one. I asked chatgpt3.5, the free one without login, to ask how to do some of the things. I had Xs on several but now I have 12/13 in good standing.
Right now my ardour with pipewire (actuallly select jack in ardour becuz ardour does not show pipewire, but I'm deff using pw as jack is uninstalled & there's a pipewire package that serves to pretend it's jack to applications) is set at 128 samples buffersize, & 48khz rate. I have 2.7ms latency with no xruns. That's only messing around with a mic thru an audio interface into ardour & listening to input & playback to see if it works.
Idk if I'll use vst plugins but I installed the wine audio utilities from his index of custom packages. It opens from the MX menu but selecting options like settings, configuration & Run WineASIO do nothing. I typed wine (tab completed wineasio64) in a terminal& it said it was running then to close the terminal. Idk what that means. I'm wondering if the repo packages wineasio-amd64 will serve teh purpose of making the plugins work, but I think I'll just forgo them for now. Tho come to think of it, the terminal command was wineasio64 so maybe that's what the utility is, plus it has a config & a settings option. So that package is wortha try.
I spent an hour on that avlinux desktop that starts with an E (I forgot the name). I couldn't stand it, trying to use the interfaces to customize. It was so buggy too. Like I selected a window theme, then the title bars of windows started sliding off the window frame lol.
MX23, MintDebian with Cinnamon, both work great on this laptop. I'd successfully recorded using the Mint I have installed on it with Audacity. Not for music so wasn't looking at quality issues, but it worked fine with no set up, just plugged my Behringer umc404 interface in & it worked. So I think the laptop is plenty good enuf. But I really tried to be patient even tho I instantly hated it, but that environment was killing me. I even logged out & logged back in with openbox that it comes with & was instantly relieved. U can use tasksel to install other desktops on it, but I only spent a brief time with mate & a couple others before I was tired, then woke up to decide I'd use MX23 with XFCE which is already great.
-
MelodyNaive
- Posts: 18
- Joined: Sat Jan 20, 2024 2:53 pm
Re: What about a regular MX Linux with AV Linux config?
@AVLinux
is there any reason why using tasksel to install a different desktop won't work with avlinux? I spent an hour with Enlightenment while watching yr video. It seemed broken & the customization menus were so hard to use. I gave up after 10 minutes of wanting to set some keyboard shortcuts. The window themeing bugged out & at one point the window title bars were sliding off the frames instead of actually being able to click the window buttons.
When I lost patience I briefly tried Mate, Cinnamon, LXDE & another, just to see what would happen. Superficially it functions, but I was on a live usb which eventually I think the ram got tired of desktops being added, & the next day instead of installing avlinux I decided to tweak my MX23 with xfce.
With the liquorix kernel & using the realtime quick config until I got 12/13 issues checked off. I've got ardour working with 2.7ms latency just using pipewire with the mx setup package & all the associated packages that make it work in place of jack & pulse. Yr Wine utility installed, & even opened, but none of the 3 options do anything. I double click or select & Enter it does nothing. I even typed wineasio64 in a terminal wich said it was now running but Idk. I figure I'll try the repo's wineASIOamd64 package if I want a vst plugin.
I'm just curious what the drawbacks would be of using tasksel to install a different desktop? I know near nothing about how desktop's interact. I do know that I tried a Debian once, with several DEs installed. When I tried the KDE whcih was really cool, it caused my computer to freeze & lag. Then I read that Debian & KDE don't work well together (i was scared my newly refurbished laptop was actually sucking so that was a relief).
is there any reason why using tasksel to install a different desktop won't work with avlinux? I spent an hour with Enlightenment while watching yr video. It seemed broken & the customization menus were so hard to use. I gave up after 10 minutes of wanting to set some keyboard shortcuts. The window themeing bugged out & at one point the window title bars were sliding off the frames instead of actually being able to click the window buttons.
When I lost patience I briefly tried Mate, Cinnamon, LXDE & another, just to see what would happen. Superficially it functions, but I was on a live usb which eventually I think the ram got tired of desktops being added, & the next day instead of installing avlinux I decided to tweak my MX23 with xfce.
With the liquorix kernel & using the realtime quick config until I got 12/13 issues checked off. I've got ardour working with 2.7ms latency just using pipewire with the mx setup package & all the associated packages that make it work in place of jack & pulse. Yr Wine utility installed, & even opened, but none of the 3 options do anything. I double click or select & Enter it does nothing. I even typed wineasio64 in a terminal wich said it was now running but Idk. I figure I'll try the repo's wineASIOamd64 package if I want a vst plugin.
I'm just curious what the drawbacks would be of using tasksel to install a different desktop? I know near nothing about how desktop's interact. I do know that I tried a Debian once, with several DEs installed. When I tried the KDE whcih was really cool, it caused my computer to freeze & lag. Then I read that Debian & KDE don't work well together (i was scared my newly refurbished laptop was actually sucking so that was a relief).
Re: What about a regular MX Linux with AV Linux config?
Tony45 wrote: Wed May 29, 2024 4:05 am Apologies first: I am off topic
A simple question !
Is there "" somewhere "" an AVLinux edition with XFCE I can download.
I do not want the E edition ( not for technical , but private reasons )
Thanks
He still has the mirror up for the MX-21 version of AVL.
https://downloads.bandshed.net/AVL-MXE-21.3/
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.