MX Linux Forum

Posted: **Sun Jan 14, 2024 4:18 pm**

Hi!

Just sharing my Blog post of the release of AV Linux MX Edition 23.1!

http://www.bandshed.net/2024/01/14/av-l ... -released/

***NOTE** - An updated and revised ISO "20240120" has been uploaded addressing 2 issues: Enlightenment packagekit updater replaced with MX's 'apt-notifier'. PulseAudio Volume Control (pavucontrol) added to expose PipeWire's Pro Audio profiles. Also Muse Sound Manager was added for MuseScore.. If you've already downloaded and installed the initial ISO then you can fix the Package updating issue with the info in this forum post:

viewtopic.php?t=78951

You can install 'pavucontrol' through the Package Manager and the Muse Sound Manager is available here: https://muse-cdn.com/Muse_Sounds_Manager_Beta.deb

Posted: **Sun Jan 14, 2024 4:24 pm**

Great job @AVLinux

I'll give it a look in a vm.

Posted: **Sun Jan 14, 2024 11:28 pm**

Thanks!

Posted: **Mon Jan 15, 2024 1:24 pm**

hi glenn, i watched your presentation of the new gem on yt.
i would like to ask you if there is any way to upgrade from avlmx 21 or is it to be installed fresh?

Posted: **Mon Jan 15, 2024 2:15 pm**

nudiecrudi wrote: Mon Jan 15, 2024 1:24 pm hi glenn, i watched your presentation of the new gem on yt.
i would like to ask you if there is any way to upgrade from avlmx 21 or is it to be installed fresh?

It says in the release announcement that unfortunately there is no upgrade path from AVL-MXE 21.3, we've moved to a whole new Debian platform, a new Desktop Environment and there are too many custom Package changes for an upgrade to work so install is the only option:

http://www.bandshed.net/2024/01/14/av-l ... -released/

Posted: **Mon Jan 15, 2024 3:11 pm**

how to update this in normal use? In the previous version, a green square appeared in the lower right corner and it succeeded that way. There is now a corresponding icon in the lower right corner, but it says that "failed to obtain authentication" if i try to install updates.

Posted: **Mon Jan 15, 2024 4:26 pm**

When I installed it in virtualbox (7.0.10), I found it to be really sluggish to taking a couple of minutes to open programs.

My guest machine specs I set up were

6 cores
8192 MB RAM
128 MB video
50GB disc

So I installed MX-23.1 XFCE using the same machine specs and upgraded it's kernel to the same as AVL-MXe (6.6.9-liquorix from the repo). XFCE booted up and ran fine.

Then I installed MX-23.1 KDE using the same machine specs and kernel and it barfed on boot up. After searching around for quite a while, I found this tip. Now all three OS's boot fine.

Open the settings for the machine and go to System > Acceleration. Change the Paravirtualization Interface from Default to Hyper-V.

virtualbox.jpg

Posted: **Mon Jan 15, 2024 5:20 pm**

SjzstudioMK wrote: Mon Jan 15, 2024 3:11 pm There is now a corresponding icon in the lower right corner, but it says that "failed to obtain authentication" if i try to install updates.

I get the same thing. In the settings for the icon there is no package manager selected. What should be there?

quickshot_240115_141629.jpg

Posted: **Mon Jan 15, 2024 10:03 pm**

Hi,

Damn, I can reproduce this issue on a new install on my Studio box... the Package Manager selection box thing is normal but that's not the problem..

Enlightenment uses 'packagekit' to track updates and the package icon in the lower right corner is it's frontend for packagekit... My MXDE-EFL spins based on MX-21 worked seamlessly with packagekit but I have a sinking feeling that something in Debian Bookworm has broken packagekit or an update to apt or dpkg has broken compatibility. A possible fix is to swap out packagekit for MX's 'apt-notifier' but I need to test this and make sure it works properly with Enlightenment..

In the meantime if you're concerned about updates then simply manually update with either MX Package Installer or Synaptic Package Manager until I figure it out..

Posted: **Mon Jan 15, 2024 10:37 pm**

OK...

Here's what I did to switch to apt-notfier which seems to work..

1. Open MXPI and install 'apt-notifier'
2. On the Enlightenment shelf (panel) right click on the packagekit icon in the lower right corner and select 'Remove' to remove it from the shelf..
3. From the Enlightenment menu go to Settings-->Modules and 'unload' the Package Manager Integration module
4. Go to Enlightenment Menu--> Settings-->Settings Panel-->Apps-->Startup Applications and 'add' MX-Updater
5. Reboot and MX-Updater (aka apt-notifier) will now handle system updates

Posted: **Mon Jan 15, 2024 11:15 pm**

AVLinux wrote: Mon Jan 15, 2024 10:37 pm OK...

Here's what I did to switch to apt-notfier which seems to work..

1. Open MXPI and install 'apt-notifier'
2. On the Enlightenment shelf (panel) right click on the packagekit icon in the lower right corner and select 'Remove' to remove it from the shelf..
3. From the Enlightenment menu go to Settings-->Modules and 'unload' the Package Manager Integration module
4. Go to Enlightenment Menu--> Settings-->Settings Panel-->Apps-->Startup Applications and 'add' MX-Updater
5. Reboot and MX-Updater (aka apt-notifier) will now handle system updates

@AVLinux I found out that you can fill in the field with the app you want to use.

I've added mx-packageinstaller to the command line.

package1.jpg

Now I have a second selection at the bottom (Manage packages). It opens MXPI. I'll test it when I know we have updates.

package2.jpg

Posted: **Tue Jan 16, 2024 4:09 am**

With this new AV Linux MX 23.1, Audio Damage EOS installer now works correctly. But For example, Dubstation2 doesn't work, I have to use earlier versions of this plugin, which do work. Why is this so? I'll probably have to contact Audio Damage again.

Or, Glen, do you have any ideas on what to try.

Might be the best AvLinux yet. However, if I use Mixbus 32C in full screen mode, it behaves a bit strangely. The menus do not respond as in normal mode

Posted: **Tue Jan 16, 2024 5:08 am**

AVLinux wrote: Mon Jan 15, 2024 2:15 pm
nudiecrudi wrote: Mon Jan 15, 2024 1:24 pm hi glenn, i watched your presentation of the new gem on yt.
i would like to ask you if there is any way to upgrade from avlmx 21 or is it to be installed fresh?
It says in the release announcement that unfortunately there is no upgrade path from AVL-MXE 21.3, we've moved to a whole new Debian platform, a new Desktop Environment and there are too many custom Package changes for an upgrade to work so install is the only option:

http://www.bandshed.net/2024/01/14/av-l ... -released/

ok thanks. i had no time to read the blog post. i will start saving my stuff so..
may be is the right occasion to tidy up a few things

Posted: **Tue Jan 16, 2024 10:04 am**

Hi,
maybe a stupid question but where is the proaudio setting for Pipewire?
i still use Envy24 multichannel PCI cards for multitracking and without the proaudio setting i can't use all channels with pipewire.
see : https://gitlab.freedesktop.org/pipewire ... xplanation

The new version looks great and is very snappy!!

Posted: **Tue Jan 16, 2024 10:18 am**

troathscream wrote: Tue Jan 16, 2024 10:04 am Hi,
maybe a stupid question but where is the proaudio setting for Pipewire?
i still use Envy24 multichannel PCI cards for multitracking and without the proaudio setting i can't use all channels with pipewire.
see : https://gitlab.freedesktop.org/pipewire ... xplanation

The new version looks great and is very snappy!!

Yep, I don't fully understand the whole Pro Audio thing either and it doesn't recognize my multichannel USB interfaces properly, I simply use the ALSA backends with Ardour/Mixbus or Reaper then the DAW is using the hardware directly but if you need pipewire-jack then there is a document included in ~/.config/wireplumber/main.lua.d/lua_example that looks like this:

Code: Select all

#Setting up a device not recognized correctly for the PipeWire "Pro Audio" profile.

1. Get your Device ID from 'wpctl status' (Focusrite Clarett used as example).

$ wpctl status
Audio
 ├─ Devices:
 │     107. Clarett+ 2Pre                       [alsa]

2. Get your ALSA Device name.

$ wpctl inspect 107 | grep device.name
  * device.name = "alsa_card.usb-Focusrite_Clarett__2Pre_00004281-00"

3. In this folder create a text file called "51-my-alsa-config.lua" with this content and place your ALSA Device name where indicated.

table.insert(alsa_monitor.rules, {
	matches = {
		-- ORed
		{
			{ "device.name", "matches", "< Place ALSA Device name here between quotes>" },
		},
	},
	apply_properties = {
		["device.profile"] = "pro-audio",
	},
})

That will allow you to set up a multichannel device with a Pro Audio profile..

Posted: **Tue Jan 16, 2024 10:32 am**

Tnx for the quick reply Glen.
I have tried an arch distro a few months ago and it just had the proaudio setting in the pipewire mixer...
I will see if i can get it running, luckily i still have the previous version of Avlinux MX on my main studio PC

Posted: **Tue Jan 16, 2024 11:06 am**

troathscream wrote: Tue Jan 16, 2024 10:32 am Tnx for the quick reply Glen.
I have tried an arch distro a few months ago and it just had the proaudio setting in the pipewire mixer...
I will see if i can get it running, luckily i still have the previous version of Avlinux MX on my main studio PC

Please try this, it will be very helpful to know for other Users.

Please install 'pavucontrol' either with MX Package Installer or Synaptic Package Manager, then tell me if the 'Pro Audio' profile is appearing for you in it's profile list

Posted: **Tue Jan 16, 2024 11:19 am**

SjzstudioMK wrote: Tue Jan 16, 2024 4:09 am With this new AV Linux MX 23.1, Audio Damage EOS installer now works correctly. But For example, Dubstation2 doesn't work, I have to use earlier versions of this plugin, which do work. Why is this so? I'll probably have to contact Audio Damage again.

Or, Glen, do you have any ideas on what to try.

Might be the best AvLinux yet. However, if I use Mixbus 32C in full screen mode, it behaves a bit strangely. The menus do not respond as in normal mode

Commercial Plugins are really up to their developers to fix, I know Audio Damage are still fine tuning their Linux builds but they need to know about the issues you are having to fix them. When you do a bug report to them make sure to indicate that you are on a base of Debian Bookworm, Plugins are interacting with the core system libraries and the Desktop Environment etc.. is of little importance, what matters are things like X11, libc6 the exact DAW you are using and deep system stuff..

As far as Mixbus, I'll have to look when I get a minute, I've never used or tested it in fullscreen mode..

Posted: **Tue Jan 16, 2024 1:13 pm**

And the first challenge (for me) on the new build.

There's a couple of modest apps I use regularly, being jack-mixer, and jack-keyboard. They're in the standard repos, and have been for some time.

When I go to install them, they're insisting, as part of their dep requirements, that jackd be installed too. I've done a cruise in the interlink, but nothing jumps out as a solution, without displacing pipewire, in favour of "olde" jack.

Has anyone smarter in linux ways than I am, come across this, and how did you solve it?

Or (for the time being) do I have to build from source, and hack the makefile somehow.

Aside from that, the upgrade to 23.1 has been a pleasurable and relatively trouble free experience.

A big thanks to Glen and the MX/AntiX team, for your efforts.

Posted: **Tue Jan 16, 2024 2:14 pm**

AVLinux wrote: Tue Jan 16, 2024 11:06 am
troathscream wrote: Tue Jan 16, 2024 10:32 am Tnx for the quick reply Glen.
I have tried an arch distro a few months ago and it just had the proaudio setting in the pipewire mixer...
I will see if i can get it running, luckily i still have the previous version of Avlinux MX on my main studio PC
Please try this, it will be very helpful to know for other Users.

Please install 'pavucontrol' either with MX Package Installer or Synaptic Package Manager, then tell me if the 'Pro Audio' profile is appearing for you in it's profile list

Nope, sadly that does not work.
I'm gonna try the other method you described

Edit :
Whoops

had to open Pavucontrol and from there in Configuration i can select Pro Audio to both Envy24 cards. At least now i can set both cards to Pro Audio.
Gonna do some testing, tnx for the tip

Posted: **Tue Jan 16, 2024 2:56 pm**

alextone wrote: Tue Jan 16, 2024 1:13 pm And the first challenge (for me) on the new build.

There's a couple of modest apps I use regularly, being jack-mixer, and jack-keyboard. They're in the standard repos, and have been for some time.

When I go to install them, they're insisting, as part of their dep requirements, that jackd be installed too. I've done a cruise in the interlink, but nothing jumps out as a solution, without displacing pipewire, in favour of "olde" jack.

Has anyone smarter in linux ways than I am, come across this, and how did you solve it?

Or (for the time being) do I have to build from source, and hack the makefile somehow.

Aside from that, the upgrade to 23.1 has been a pleasurable and relatively trouble free experience.

A big thanks to Glen and the MX/AntiX team, for your efforts.

Hi,

I don't think installing jackd (the daemon part of JACK) is the kiss of death, in fact if you install Qtractor for instance it's going to pull in jackd and libjack2 (the library part of jack) is already installed to help 'old JACK' apps to continue running..

The system is set up to link calls for 'libjack' to pipewire-jack so if you install jack-mixer when it runs it will theoretically work as it always has except it's mixing pipewire-jack... jackd is kind of sitting there as an unused dependency but shouldn't harm or prevent things from working (or at least that is my educated guess)

Posted: **Tue Jan 16, 2024 3:15 pm**

Ok, thanks. An educated guess is an opportunity.

Posted: **Tue Jan 16, 2024 3:23 pm**

alextone wrote: Tue Jan 16, 2024 3:15 pm Ok, thanks. An educated guess is an opportunity.

Please confirm or deny this very precarious guess..

Posted: **Tue Jan 16, 2024 3:29 pm**

troathscream wrote: Tue Jan 16, 2024 2:14 pm had to open Pavucontrol and from there in Configuration i can select Pro Audio to both Envy24 cards. At least now i can set both cards to Pro Audio.
Gonna do some testing, tnx for the tip

That's very valuable info, I need to add pavucontrol to future releases as it appears that it shows profiles that the Enlightenment Mixer doesn't..

Posted: **Tue Jan 16, 2024 4:03 pm**

During booting, a text line appears in red.
An error log is printed in the home directory.

There you can find the lines:
CF: fallback to system config config file for [e_comp]
CF: system config load for /usr/share/enlightenment/data/config/AVL-MXe/e_comp.cfg failed

Is it serious?

OK...

Here's what I did to switch to apt-notfier which seems to work..

1. Open MXPI and install 'apt-notifier'
2. On the Enlightenment shelf (panel) right click on the packagekit icon in the lower right corner and select 'Remove' to remove it from the shelf..
3. From the Enlightenment menu go to Settings-->Modules and 'unload' the Package Manager Integration module
4. Go to Enlightenment Menu--> Settings-->Settings Panel-->Apps-->Startup Applications and 'add' MX-Updater
5. Reboot and MX-Updater (aka apt-notifier) will now handle system updates

That caused problems with the usb sound card. It got stuck in some kind of startup loop.
The loop could be stopped by executing pipewire-start
I removed that starting program MX-Updater from the list and the operation returned to normal.

Posted: **Tue Jan 16, 2024 4:27 pm**

That is very odd, one should not have anything to do with the other... Is your system BIOS set to boot from USB?

Are you booting with sysvinit or systemd?

I've never seen that error but I don't think it's important right now..

Posted: **Tue Jan 16, 2024 4:43 pm**

Are you booting with sysvinit or systemd?

sysvinit

Is your system BIOS set to boot from USB?

What do you mean. I already installed this on the hard drive

In any case, this still works normally.

That error message might be because that file /usr/share/enlightenment/data/config/AVL-MXe/e_comp.cfg does not exist.
In fact, the whole folder /usr/share/enlightenment/data/config/AVL-MXe does not exist.

What have I messed up again?

Posted: **Tue Jan 16, 2024 4:48 pm**

Hmmm did you uninstall anything?

Is 'mxde-enlightenment-assets' still installed? That file should exist and is part of that package..

Some systems even if installed act weird at boot when things are plugged into USB ports and the system is set to boot from USB

Posted: **Tue Jan 16, 2024 4:48 pm**

@AVLinux Glen, congratulations.

Btw. the appearance is so nice, wallpaper, logo even the font type of "mx edition" :)

Posted: **Tue Jan 16, 2024 4:54 pm**

Charlie Brown wrote: Tue Jan 16, 2024 4:48 pm @AVLinux Glen, congratulations.

Btw. the appearance is so nice, wallpaper, logo even the font type of "mx edition" :)

Thanks! The font is this: https://online-fonts.com/fonts/abeatbykai

Such fonts are normally not my taste but it matched very well with the Enlightenment 'e' Logo

Posted: **Tue Jan 16, 2024 5:02 pm**

AVLinux wrote: Tue Jan 16, 2024 4:48 pm Hmmm did you uninstall anything?

Is 'mxde-enlightenment-assets' still installed? That file should exist and is part of that package..

Some systems even if installed act weird at boot when things are plugged into USB ports and the system is set to boot from USB

/usr/share/enlightenment/data/config# dir
default profile.cfg standard tiling

As far as I know, I haven't uninstalled anything

Posted: **Tue Jan 16, 2024 5:07 pm**

OK,

What does this command show:

Code: Select all

apt-cache show mxde-efl-enlightenment-assets

Posted: **Tue Jan 16, 2024 5:12 pm**

$ apt-cache show mxde-efl-enlightenment-assets
Package: mxde-efl-enlightenment-assets
Status: install ok installed
Priority: optional
Installed-Size: 262876
Maintainer: Glen MacArthur
Architecture: all
Version: 20240106-bookworm1-1
Depends: gtk2-engines-murrine, gtk2-engines-pixbuf, lightdm, enlightenment, enlightenment-data, terminology, terminology-data, yad, zenity, bash, mousepad, imagemagick, sox, samplerate-programs, cpufrequtils, ffmpeg, pacpl, jmtpfs, mediainfo
Conflicts: mxde-efl-enlightenment-assets
Description: GTK, GRUB, lightDM and Icon Themes as well as helper scripts and various assets for the Enlightenment Desktop Environment - Custom AVL-MXe Package.
Description-md5: 661a2c6c2ab11715b99356778d5a9c2b

Posted: **Tue Jan 16, 2024 5:18 pm**

OK, actually I'm wrong, nothing is missing in that folder

That looks good, I don't know what that error means, it's looking the AVL-MXe 'profile' in /usr/share but it is present in ~/.e/e/config where it should be so I don't think that error is important..

So since you removed MX-Updater from Enlightenment's startup does it still appear in the systray when you boot?

Also if you don't mind can you edit out the email address from the "Maintainer" line post above, I forgot it would print like that..

Posted: **Tue Jan 16, 2024 5:29 pm**

So since you removed MX-Updater from Enlightenment's startup does it still appear in the systray when you boot?

In fact, I completely reinstalled tonight.
So this should now be in its original state. Except I have installed more plugins.
How can I print the boot list that appears on the screen during booting?
I'll continue tomorrow, it's already past midnight here in Finland

Posted: **Wed Jan 17, 2024 1:28 am**

AVLinux wrote: Tue Jan 16, 2024 3:29 pm
troathscream wrote: Tue Jan 16, 2024 2:14 pm had to open Pavucontrol and from there in Configuration i can select Pro Audio to both Envy24 cards. At least now i can set both cards to Pro Audio.
Gonna do some testing, tnx for the tip
That's very valuable info, I need to add pavucontrol to future releases as it appears that it shows profiles that the Enlightenment Mixer doesn't..

Yes indeed.
The Enlightenment mixer does not show the Pro Audio profile.
Yesterday tried to wrap my head around all the different inputs and outputs in Qpwgraph there are a lot of them hahaha, it shows everything.
Got to do some more research to get the correct input and output channels set in Mixbus with pipewire, and especially which input/output belongs to which soundcard

Posted: **Wed Jan 17, 2024 6:13 am**

i see you ve decided to include carla. i personally think it s a good addition.
i have some trouble getting adapted to a new environment after many years of xfce. i need to use the live version for a while

Posted: **Wed Jan 17, 2024 9:48 am**

nudiecrudi wrote: Wed Jan 17, 2024 6:13 am i see you ve decided to include carla. i personally think it s a good addition.
i have some trouble getting adapted to a new environment after many years of xfce. i need to use the live version for a while

The beginning of the release Video shows how to make a persistent USB key with MX Live USB Maker that you can use and keep your changes for as long as you want..

Posted: **Wed Jan 17, 2024 9:50 am**

troathscream wrote: Wed Jan 17, 2024 1:28 am Yes indeed.
The Enlightenment mixer does not show the Pro Audio profile.
Yesterday tried to wrap my head around all the different inputs and outputs in Qpwgraph there are a lot of them hahaha, it shows everything.
Got to do some more research to get the correct input and output channels set in Mixbus with pipewire, and especially which input/output belongs to which soundcard

I'm curious, if you're using Mixbus why don't you just use the Mixbus ALSA backend and avoid ALL of the Audio servers and just hook the soundcard directly to Mixbus?

Posted: **Wed Jan 17, 2024 10:18 am**

I installed "pavucontrol" as a test and the Pro Audio setting can be found nicely there. Direct ALSA with Mixbus is also good and works. In normal studio work, I always use ALSA. This is now in pretty good shape here.

Posted: **Wed Jan 17, 2024 10:35 am**

This is exciting news! Can't wait to try it on my home system where I have 32GB of RAM

aside: I used to do a lot of home recording with "Sonic Foundry" Acid Pro (which later became Sony Acid Pro of course), Vegas, Sound Forge.

I wonder if there is any software similiar to Acid for Linux. I know I presented the same question probably 10 yrs ago by now †(1)
and at that time there were no known apps avail (i was prob running Linux Mint, or Lubuntu...)

I have a Line 6 POD XT (?) Pedal, and some kind of BOSS pedal which I expect they both have digital outs if not at least some sort of AD/DA conversion built in. Had those 2 items for a couple years now and never tried for recording. Perhaps now is the time!
:D

Best wishes!

†(1)
Just to demonstrate that I do have some experience with pro audio.

Posted: **Wed Jan 17, 2024 10:42 am**

AVLinux wrote: Wed Jan 17, 2024 9:50 am
troathscream wrote: Wed Jan 17, 2024 1:28 am Yes indeed.
The Enlightenment mixer does not show the Pro Audio profile.
Yesterday tried to wrap my head around all the different inputs and outputs in Qpwgraph there are a lot of them hahaha, it shows everything.
Got to do some more research to get the correct input and output channels set in Mixbus with pipewire, and especially which input/output belongs to which soundcard
I'm curious, if you're using Mixbus why don't you just use the Mixbus ALSA backend and avoid ALL of the Audio servers and just hook the soundcard directly to Mixbus?

I now use multiple soundcards with zita-a2j and zita-j2a. The PCI cards are synced through SPDIF.
If i want to use Mixbus with the ALSA backend with the multiple soundcards i have to make the ALSA bindings again in .Asoundrc.... It's been a very long time since i tried to make that work

Have your old Delta1010 funpack somewhere on my drive so i could, but really dont want to hahaha

I have everything setup so that when i boot my pc Cadence autostarts Claudia with the Zita-bridges and Carla with all my routing and FX's to use with rehearsals and recording from my band.
I have multiple studio's saved within Claudia so with a click of my mouse i can set everything up for rehearsal, recording or mixing.
The good thing of those old PCI cards is still the very low latency you can get

For just mixing alsa is great with a large buffer, don't need lowlatency when mixing or a big channelcount.
But for recording when i need all the channels this is the easiest method.
I hope one day FalkTX or the Ladish developers will make their tools compatible with pipewire.

For now i'm gonna make the new Avlinux my experimental install gonna find my way around Enlightement, since i'm very used to work with XFCE, and pipewire.
And maybe just use AVL-mXE 23.1 as my mixing and mastering build with alsa .

Posted: **Wed Jan 17, 2024 2:31 pm**

SjzstudioMK wrote: Wed Jan 17, 2024 10:18 am I installed "pavucontrol" as a test and the Pro Audio setting can be found nicely there. Direct ALSA with Mixbus is also good and works. In normal studio work, I always use ALSA. This is now in pretty good shape here.

Glad to hear that!

Can you further comment on whether you've had issues again with the Package updater? This is something I need to know to fix it in future ISO's. I can't reproduce the issue with MX-Updater at boot, I also have USB Audio devices plugged in at boot and on 2 machines here I have no boot issues with MX-Updater set to as a startup app..

Also... Have you tried Mixbus fullscreen with fullscreen compositing turned off? See the 'Rendering' tab on the screenshot below *note I'm using the 'Dark' theme:

shot-2024-01-17_14-39-55.jpg

Posted: **Wed Jan 17, 2024 3:02 pm**

Can you further comment on whether you've had issues again with the Package updater?

That thing is now as it was when it was installed. I'll use MX Package Installer for updates in the future, if nothing else.
In fact, I noticed that if I add a program that starts automatically, it causes a problem with connecting the Sound card. That is, the system can't initialize it correctly, but it seems to remain in a boot loop. It's like if you kept plugging and unplugging the USB cable. You can make it work by running pipewire-start from the menu. But it works when I don't add startup programs.

Also... Have you tried Mixbus fullscreen with fullscreen compositing turned off? See the 'Rendering' tab on the screenshot below *note I'm using the 'Dark' theme

This fixed the situation

Posted: **Wed Jan 17, 2024 3:39 pm**

@ajaxStardust wrote: Wed Jan 17, 2024 10:35 am This is exciting news! Can't wait to try it on my home system where I have 32GB of RAM

aside: I used to do a lot of home recording with "Sonic Foundry" Acid Pro (which later became Sony Acid Pro of course), Vegas, Sound Forge.

I wonder if there is any software similiar to Acid for Linux. I know I presented the same question probably 10 yrs ago by now †(1)
and at that time there were no known apps avail (i was prob running Linux Mint, or Lubuntu...)

I have a Line 6 POD XT (?) Pedal, and some kind of BOSS pedal which I expect they both have digital outs if not at least some sort of AD/DA conversion built in. Had those 2 items for a couple years now and never tried for recording. Perhaps now is the time!
:D

Best wishes!

†(1)
Just to demonstrate that I do have some experience with pro audio.

Haha, you don't have to have experience with pro audio... we'll let anyone in!

A lot of people use Bitwig which is cross platform (however commercial) it is geared toward loop based composition and was developed by some former Ableton Live developers:

https://www.bitwig.com/?gclid=CjwKCAiAk ... WYQAvD_BwE

Ardour (included in AVL) also has clip-based workflow which is good for loop-based compositions

Posted: **Wed Jan 17, 2024 4:03 pm**

SjzstudioMK wrote: Wed Jan 17, 2024 3:02 pm That thing is now as it was when it was installed. I'll use MX Package Installer for updates in the future, if nothing else.
In fact, I noticed that if I add a program that starts automatically, it causes a problem with connecting the Sound card. That is, the system can't initialize it correctly, but it seems to remain in a boot loop. It's like if you kept plugging and unplugging the USB cable. You can make it work by running pipewire-start from the menu. But it works when I don't add startup programs.

Note that you can change the order of when the startup apps start, my guess is that pipewire sysvinit and MX-Updater are executing at the same time and likely changing the order would have fixed that issue..

shot-2024-01-17_15-52-59.jpg

Posted: **Wed Jan 17, 2024 4:24 pm**

AVLinux wrote: Tue Jan 16, 2024 3:23 pm
alextone wrote: Tue Jan 16, 2024 3:15 pm Ok, thanks. An educated guess is an opportunity.
Please confirm or deny this very precarious guess..

There was nothing to fear. Jack-keyboard works, and Pipewire hasn't run off screaming into the dark.

It was a well founded precariously educated guess....

Posted: **Wed Jan 17, 2024 4:59 pm**

@alextone

Phew! And how is the performance as a hardcore JACK user? I mostly use ALSA backends and haven't routinely used JACK for a couple of years..

Posted: **Wed Jan 17, 2024 5:38 pm**

AVLinux wrote: Wed Jan 17, 2024 4:59 pm @alextone

Phew! And how is the performance as a hardcore JACK user? I mostly use ALSA backends and haven't routinely used JACK for a couple of years..

The jury's still out. If i set up an all jack midi and audio chain, then it's ok. When it's mixed, i.e. alsa midi, and jack audio (qtractor), then i've had a crash or two, and a bit of wobbly audio every now and then. I've checked all the settings, in pipewire/pavucontrol (yes, i took note of your discovery, i'm now an audio pro, allegedly), and according to those, i'm ok. Will test lots more though, before i commit to a firm response.

I'm still using a collection of apps all sticky taped and wired together, so it's not all in one app, as so many seem to prefer these days (where have all the hard core linux audio users gone?), and i wonder if pipewire is settled enough on the development path to cope with that.

Still, it's early days. Tentatively, i'd say, so far so good. But only tentatively......

Posted: **Wed Jan 17, 2024 5:57 pm**

@alextone,

Have you had any issues with the default Package updater? I'm trying to determine if this is an isolated issue or not?

Posted: **Wed Jan 17, 2024 6:13 pm**

AVLinux wrote: Wed Jan 17, 2024 5:57 pm @alextone,

Have you had any issues with the default Package updater? I'm trying to determine if this is an isolated issue or not?

Yes, it doesn't work. When i started it up in 21.3, it would popup a password window. That doesn't happen with this version, and it just keeps churning away waiting for something to happen. I've removed it from the panel, and use MXPI and/or Synaptic instead.

Posted: **Wed Jan 17, 2024 6:22 pm**

Damn... That one escaped me because my main build system here is still based on MX-21.3..

Posted: **Wed Jan 17, 2024 6:59 pm**

I can also confirm (here at least) that celluloid (mpv frontend) and VLC work properly, and Tchaikovsky's 1812, and Dvorak's Water Goblin sound excellent. Clear as a bell. Another point for Pipewire.

Posted: **Wed Jan 17, 2024 8:50 pm**

well I am having an issue on my Minisforum Neptune HX99G (Ryzen 9 6900X w/6600M - 2 x 4tb nVME Gen4x4 (1 Phison - 1 KingSpec xg7000) 64GB DDR5 5600Mhz) the live usb works perfectly, but after installing on this machine when I restart after going through the verbose text output it boots a completely blank screen no cursor even and I can't seem to get it to respond to any input... not sure what's going on... going to try reinstalling tomorrow (this setup is at my work at the moment so I can't mess with it right now or try anything until I get back to work)... so eager to get to work on this...

Posted: **Wed Jan 17, 2024 9:13 pm**

Hi!

Hmmm, odd that the live system works, but I often see similar posts around here and usually someone around here can get things up and running (unfortunately these type of issues are not my forte)

Posted: **Thu Jan 18, 2024 7:53 am**

Does it matter if you use sysvinit or systemd booting? Or is it just a matter of taste? systemd seems to boot faster.

Posted: **Thu Jan 18, 2024 8:34 am**

i do not understand.. never had such issues, that is crazy, i thought it was errors on the live usb so i have installed on dualboot, but it is pratically impossible to do anything in my case.
applications won't start, cannot see the other partition, no application is assigned to file.

shot-2024-01-18_14-17-37.jpg

shot-2024-01-18_14-16-03.jpg

Posted: **Thu Jan 18, 2024 8:37 am**

Ok, next pipewire challenge.

When i open Qtractor, Muse, and Reaper, System Audio Inputs (specifically capture_FL, capture_FR) are automatically connected, and I don't want them to do that. I've searched PW, Pavucontrol, and the interlink, and there's no noise about this as far as i can find out. I've turned off autoconnect in Reaper and Muse, and there is no autoconnect in Qtractor (aside from the individual audio busses, and they're deactivated), but the system inputs relentlessly continue to plague me at application startup. I've disconnected them and saved templates in all three apps, but it makes no difference.

EDIT: I may have found it. I needed to turn off mic input (mute), in input devices, in Pavucontrol. (which is fast proving useful)
Now the projects save without adding those pesky unwanted ports.

I'm leaving this here as a warning to others...... :)

Posted: **Thu Jan 18, 2024 10:36 am**

AVLinux wrote: Wed Jan 17, 2024 2:31 pm
SjzstudioMK wrote: Wed Jan 17, 2024 10:18 am I installed "pavucontrol" as a test and the Pro Audio setting can be found nicely there. Direct ALSA with Mixbus is also good and works. In normal studio work, I always use ALSA. This is now in pretty good shape here.
Glad to hear that!

Can you further comment on whether you've had issues again with the Package updater? This is something I need to know to fix it in future ISO's. I can't reproduce the issue with MX-Updater at boot, I also have USB Audio devices plugged in at boot and on 2 machines here I have no boot issues with MX-Updater set to as a startup app..

Also... Have you tried Mixbus fullscreen with fullscreen compositing turned off? See the 'Rendering' tab on the screenshot below *note I'm using the 'Dark' theme:

shot-2024-01-17_14-39-55.jpg

I got apt-notifier installed to start at boot according to Glen's instructions. Booting now works correctly via systemd and the sound card starts correctly. When booting sysvinit remains in a loop, as I described earlier.

There is a problem with the Startup applications tool. I had to try several times before I got the changes done. Flashed a red text error at the top of the screen

Posted: **Thu Jan 18, 2024 10:41 am**

SjzstudioMK wrote: Thu Jan 18, 2024 7:53 am Does it matter if you use sysvinit or systemd booting? Or is it just a matter of taste? systemd seems to boot faster.

For some it's a very ideological/political decision because systemd doesn't behave very 'unix-y'... I am completely apolitical about it and my advice is if your particular machine seems to work better with one of the other then use whichever you prefer... as an example my main development/build machine is quite new and I run it with systemd... My Studio box is an older Dell Optiplex doorstop/cinderblock with a very old Atheros based wifi card and I find the WiFi is much more stable with sysvinit... Some folks with 3rd party applications (especially VPN's) find systemd is a must.

Even having a choice is the MX/antiX heritage and is baked into the cake, it is not an AVL feature, the Live system only uses sysvinit at this point so having both is required..

Posted: **Thu Jan 18, 2024 10:42 am**

SjzstudioMK wrote: Thu Jan 18, 2024 10:36 am I got apt-notifier installed to start at boot according to Glen's instructions. Booting now works correctly via systemd and the sound card starts correctly. When booting sysvinit remains in a loop, as I described earlier.

There is a problem with the Startup applications tool. I had to try several times before I got the changes done. Flashed a red text error at the top of the screen

I have a better solution for apt-notifier but it requires some 3rd party testers, are you and @alextone willing to test?

Posted: **Thu Jan 18, 2024 10:43 am**

Of course. I'll just make a backup of this first.

Posted: **Thu Jan 18, 2024 10:44 am**

nudiecrudi wrote: Thu Jan 18, 2024 8:34 am i do not understand.. never had such issues, that is crazy, i thought it was errors on the live usb so i have installed on dualboot, but it is pratically impossible to do anything in my case.
applications won't start, cannot see the other partition, no application is assigned to file.shot-2024-01-18_14-17-37.jpgshot-2024-01-18_14-16-03.jpg

Hold on, help is on the way, I have some other things to sort out first...

Posted: **Thu Jan 18, 2024 11:07 am**

AVLinux wrote: Thu Jan 18, 2024 10:44 am
nudiecrudi wrote: Thu Jan 18, 2024 8:34 am i do not understand.. never had such issues, that is crazy, i thought it was errors on the live usb so i have installed on dualboot, but it is pratically impossible to do anything in my case.
applications won't start, cannot see the other partition, no application is assigned to file.shot-2024-01-18_14-17-37.jpgshot-2024-01-18_14-16-03.jpg
Hold on, help is on the way, I have some other things to sort out first...

no problem. we are not in a hurry round here

Posted: **Thu Jan 18, 2024 12:24 pm**

AVLinux wrote: Thu Jan 18, 2024 10:42 am
SjzstudioMK wrote: Thu Jan 18, 2024 10:36 am I got apt-notifier installed to start at boot according to Glen's instructions. Booting now works correctly via systemd and the sound card starts correctly. When booting sysvinit remains in a loop, as I described earlier.

There is a problem with the Startup applications tool. I had to try several times before I got the changes done. Flashed a red text error at the top of the screen
I have a better solution for apt-notifier but it requires some 3rd party testers, are you and @alextone willing to test?

Yep.

Posted: **Thu Jan 18, 2024 12:39 pm**

AVLinux wrote: Wed Jan 17, 2024 9:13 pm(unfortunately these type of issues are not my forte)

Yeah, I figure it's something silly, so I got to work today & booted it up, got to the black screen & thinking maybe I just can't see stuff because it killed the brightness I typed my user password hit enter, still nothing, I use a kinesis advantage 2 keyboard so I don't have a function key or a brightness up or down keys, so I tried hooking up a Dell keyboard I found laying around the shop hitting keys on it didn't seem to do anything, then I hit the numlock key just to see if the keyboard was even being recognized & the light came on then I noticed this funny X on the screen...

which apparently is the mouse pointer icon as it follows the mouse around the screen when I move it... Still can't seem to get any sort of other input or anything else to respond... This is so weird...

Posted: **Thu Jan 18, 2024 12:52 pm**

Ok so I managed to get to terminal, what is the command for starting enlightenment desktop?

UPDATE: ran sudo apt update && sudo apt upgrade

After upgrade I got this:

Code: Select all

(dpkg-preconfigure: 57536): Gtk-WARNING **: 12:54:39.090: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
Reading database 294815 files and directories currently installed.)
( Preparing to unpack.../mx-remaster_24.01.01mx23_all.deb
Unpacking mx-remaster (24.01.01mx23) over (23.10.01mx23)
Preparing to unpack.../ddm-mx_24.01.01_all.deb
Unpacking ddm-mx (24.01.01) over (23.12.02)
Preparing to unpack ./mx-repo-list_24.1_all.deb )
Unpacking mx-repo-list (24.1) over (23.12
Setting up ddm-mx (24.01.01)
Setting up mx-remaster (24.01.01mx23)
Setting up mx-repo-list (24.1)
Processing triggers for mailcap (3.70+nmu1)
Processing triggers for desktop-file-utils (0.26-1)...

UPDATE 2: inxi -G returns:

Code: Select all

Graphics:
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu v: kernel
Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel
Display: server: X.org v: 1.21.1.7 driver: X: loaded: amdgpu unloaded: fbdev, modesetting, vesa
dri: radeonsi gpu: amdgpu tty: 160x45 resolution: 2560x1440
API: OpenGL Message: GL data unavailable in console. Try -G-display

Posted: **Thu Jan 18, 2024 12:59 pm**

@alextone @SjzstudioMK and any others who may want to test

viewtopic.php?p=762062#p762062

Posted: **Thu Jan 18, 2024 1:00 pm**

@blast0id

What does logging in and entering 'startx' into the console do?

Posted: **Thu Jan 18, 2024 1:28 pm**

AVLinux wrote: Thu Jan 18, 2024 1:00 pmWhat does logging in and entering 'startx' into the console do?

Back to black screen & I have to ctl+alt F2-7 if I run startx in any of those I get black screen & can't get back to terminal via ctl+alt F2-7 (unless I have not typed startx on that desktop/session or whatever)

Posted: **Thu Jan 18, 2024 1:35 pm**

Ugh... weird!

I'm running a similar Video card (Radeon 6750XT) so I'm puzzled, especially when you have no issues with a Live session..

OK, I'm sure we can figure something out... I'll summon the "Charlie brigade"... @Charlie Brown @CharlesV any suggestions here?

Posted: **Thu Jan 18, 2024 1:44 pm**

Though the driver looks loaded correctly, what if you press E on Grub then type nomodeset after .. ro quiet splash (etc) then press F10 ?

Posted: **Thu Jan 18, 2024 1:49 pm**

blast0id wrote: Thu Jan 18, 2024 1:28 pm
AVLinux wrote: Thu Jan 18, 2024 1:00 pmWhat does logging in and entering 'startx' into the console do?
Back to black screen & I have to ctl+alt F2-7 if I run startx in any of those I get black screen & can't get back to terminal via ctl+alt F2-7 (unless I have not typed startx on that desktop/session or whatever)

Lets get a QSI on this machine please.
or alternatively:

Code: Select all

  inxi -Fxxxrza

Posted: **Thu Jan 18, 2024 2:05 pm**

Ok will try that after this reinstall, I just reformatted both nVME's & I am starting totally fresh... just to make sure I didn't fudge something up during install...

UPDATE: had to get home for an appointment, will have to pick it up tomorrow... but so far reinstalled and ready to reboot.

question: anyone know how to reset the persistent live-usb data as if I have never loaded this USB?

Posted: **Thu Jan 18, 2024 8:16 pm**

nudiecrudi wrote: Thu Jan 18, 2024 11:07 am
AVLinux wrote: Thu Jan 18, 2024 10:44 am
nudiecrudi wrote: Thu Jan 18, 2024 8:34 am i do not understand.. never had such issues, that is crazy, i thought it was errors on the live usb so i have installed on dualboot, but it is pratically impossible to do anything in my case.
applications won't start, cannot see the other partition, no application is assigned to file.shot-2024-01-18_14-17-37.jpgshot-2024-01-18_14-16-03.jpg
Hold on, help is on the way, I have some other things to sort out first...
no problem. we are not in a hurry round here

OK, Hi!

Yes Enlightenment is different and it has quirks (I have a lot of quirks too, that's why I like it!).. Let's start with gufw... I did notice on first launch it showed me this message:

shot-2024-01-18_18-27-05.jpg

I will have to look into why it says that but it tells us how to fix it... open a terminal and do:

Code: Select all

sudo chmod 755 /etc

After that gufw will open and you can make your settings..

Now... As far as files opening how you expect.. If you have watched the AVL-MXe-23.1 release Video you will see that Enlightenment has it's own File Manager "EFM" and that AVL-MXe also provides the Thunar File Manager from XFCE4. If you are used to XFCE4 then I expect you will want to use Thunar most of the time and you should find for most files that 'Open With' on Thunar does more of what you expect and has more predictable mimetypes..

Posted: **Fri Jan 19, 2024 12:17 am**

AVLinux wrote: Thu Jan 18, 2024 8:16 pm
nudiecrudi wrote: Thu Jan 18, 2024 11:07 am
AVLinux wrote: Thu Jan 18, 2024 10:44 am

Hold on, help is on the way, I have some other things to sort out first...
no problem. we are not in a hurry round here
OK, Hi!

Yes Enlightenment is different and it has quirks (I have a lot of quirks too, that's why I like it!).. Let's start with gufw... I did notice on first launch it showed me this message:

shot-2024-01-18_18-27-05.jpg

I will have to look into why it says that but it tells us how to fix it... open a terminal and do:
Code: Select all
sudo chmod 755 /etc
After that gufw will open and you can make your settings..

Now... As far as files opening how you expect.. If you have watched the AVL-MXe-23.1 release Video you will see that Enlightenment has it's own File Manager "EFM" and that AVL-MXe also provides the Thunar File Manager from XFCE4. If you are used to XFCE4 then I expect you will want to use Thunar most of the time and you should find for most files that 'Open With' on Thunar does more of what you expect and has more predictable mimetypes..

ok, thank you. cannot do that because it does not boot any longer.
i am going to wait for some time and let you expert guys work on it.
in the meantime i work with your last creation , that in my opinion is your best creation to date.

Posted: **Fri Jan 19, 2024 6:07 am**

A small but important point.

Qpwgraph saves connections, including those across multiple apps outside of a DAW. And it does so effectively, and so far, consistently. I've created a generic patchbay instance, and one for Qtractor (git version) connected to Linuxsampler, Jconvolver, and Non-mixer-xt, all standalone apps.

We haven't always had this stable luxury, and I for one am grateful for the time it will save, when connecting a small community of apps. The built-in midi bridging, usefully, allows me to connect jack and alsa midi ports to each other, without any extra effort, or apps.

This is progress, imho.

See the attached pic for a small testing orchestral template (using Paul Battersby's Virtual Playing Orchestra), and how it's all wired together. Qtractor is running purely as a midi sequencer, and all the audio is handled outside of it. This is a stable setup, which is why i do it this way. Additionally Jconvolver is still, imho, the best convolution app we have in Linux, so the effort of making a jconv config file, and patching it into the mixer is worth it, for the results it gives.

Pipewire is growing on me (a longtime diehard jack user), and Qpwgraph is proving its worth.

Non-mixer-xt is not in the repos (yet), but you can get the git code, and build it yourself. Important to ensure all the dependencies are in place first. This particular version has had an upgrade and now includes the option to build with LV2, CLAP, and VST3 plugin support, as well as the original LADSPA option.

https://github.com/Stazed/non-mixer-xt

Once i added the usual build tools, i had no problem compiling and installing it in AVLinux MXDE 23.1.

Paul Battersby's VPO can be found here:

http://virtualplaying.com/virtual-playing-orchestra/

Posted: **Fri Jan 19, 2024 11:25 am**

Excellent info, thanks for sharing and glad things are working for you (more or less)..

Posted: **Sat Jan 20, 2024 4:37 am**

blast0id wrote: Thu Jan 18, 2024 12:39 pm Yeah, I figure it's something silly, so I got to work today & booted it up, got to the black screen & thinking maybe I just can't see stuff because it killed the brightness I typed my user password hit enter, still nothing, I use a kinesis advantage 2 keyboard so I don't have a function key or a brightness up or down keys, so I tried hooking up a Dell keyboard I found laying around the shop hitting keys on it didn't seem to do anything, then I hit the numlock key just to see if the keyboard was even being recognized & the light came on then I noticed this funny X on the screen...
which apparently is the mouse pointer icon as it follows the mouse around the screen when I move it... Still can't seem to get any sort of other input or anything else to respond... This is so weird...

I ran into some similar issues on the live-usb:
First startup (init.d): fine (it was the checkmedia option), second and all starts after that (all init.d) ended up in a blank/black screen with mouse cursor only, no menus, no right-clicks, just the mouse-cursor.
"startx" started a "vanilla" Enlightenment-Desktop with no AVL-Modifications on, it think it was (STRG-ALT-F4) Terminal, restarting lightdm ("/etc/init.d/lightdm restart") brought back the wanted AVL-Enlightenment-Desktop.

After installing to harddisk: No issues til now. Apart from disk-manager having issues with some Icons(hicolortheme not found-blubb) and not starting because of it.

Posted: **Sat Jan 20, 2024 9:22 am**

@pffftdwarf

That's interesting, I have no idea why that is going on, I have several installs here and haven't been able to reproduce the black screen x cursor issue

I'm not seeing the Disk Manager problem either, it seems to launch without complaint here (on a live session anyway)

Posted: **Sat Jan 20, 2024 10:27 am**

In the meantime you can also try (rather than just startx):

Code: Select all

startx /usr/bin/enlightenment_start

Posted: **Sat Jan 20, 2024 10:39 am**

blast0id wrote: Thu Jan 18, 2024 12:52 pm
UPDATE 2: inxi -G returns:

Code: Select all

Graphics:
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu v: kernel
Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel
Display: server: X.org v: 1.21.1.7 driver: X: loaded: amdgpu unloaded: fbdev, modesetting, vesa
dri: radeonsi gpu: amdgpu tty: 160x45 resolution: 2560x1440
API: OpenGL Message: GL data unavailable in console. Try -G-display

@blast0id
Which graphics card are you using? (onboard Radeon 680M or discreet Radeon 6600)
What type of cable? (HDMI, Display Port, etc.)

Posted: **Sat Jan 20, 2024 10:50 am**

AVLinux wrote: Sat Jan 20, 2024 9:22 am @pffftdwarf

That's interesting, I have no idea why that is going on, I have several installs here and haven't been able to reproduce the black screen x cursor issue

I'm not seeing the Disk Manager problem either, it seems to launch without complaint here (on a live session anyway)

I thought maybe it's that i did not use the "live-usb-maker" from AVL to create the usb-stick, so I just did another run with a stick created by the AVL tool. But it is haveing the same issue, the live-system starts into an black window with cursor only.

Code: Select all

/etc/init.d/lightdm restart

brings back the AVL Enlightenment Desktop. The PC I use is a bit older, maybe some wonky stuff is happening here. If it was an widespread issue more people would complain.

As I said, I was able to install it on a sdd and it runs fine when booted into.

The "disk-manager" seems to be related to the installed version, i changed a theme there maybe thats the cause, on the live-stick it just will not start when run from the mx-tools menu, from terminal as sudo it runs fine.

neofetch.png

Thats my machine.

If needed i can provide logs etc. from the liveusb-system , you just need to tell me which ones.

Posted: **Sat Jan 20, 2024 12:03 pm**

@pffftdwarf

I think we have our wires crossed, your neofetch appears to be from AV Linux 21.X with XFCE4... The thread is about the brand new release 23.1 with Kernel 6.6.9 and the Enlightenment Desktop Environment. I just want make sure we're talking about the same thing.

Posted: **Sat Jan 20, 2024 12:42 pm**

AVLinux wrote: Sat Jan 20, 2024 12:03 pm @pffftdwarf

I think we have our wires crossed, your neofetch appears to be from AV Linux 21.X with XFCE4... The thread is about the brand new release 23.1 with Kernel 6.6.9 and the Enlightenment Desktop Environment

Sorry for the confusion, i made that neofetch while creating the AVL-23 live-usb on AV-Linux 21.X. Did not think that through...
The things i mentioned are all happening with AVL 23 LIVE-USB.

This is what i get after booting the Live-System (AVL 23):

rightafterboot.jpg

Neofetch from ttyx:

ttyneofetch.jpg

running "startx /usr/bin/enlightenment_start", looks like a vanilla-start of Enlightenment

startx.jpg

neofetch after "/etc/init.d/lightdm restart" and AVL Enlightenment-Desktop loading correctly.

shot-2024-01-20_12-18-50.jpg

I hope that clarified some things.

Posted: **Sat Jan 20, 2024 12:50 pm**

@pffftdwarf

Ok good! Thanks for the clarification and the info!

This is acting like some kind of lightDM issue, I wonder if it's a systemd vs. sysvinit thing..?

To be clear once you were able to get the system installed everything worked OK?

Posted: **Sat Jan 20, 2024 1:10 pm**

AVLinux wrote: Sat Jan 20, 2024 12:50 pm @pffftdwarf

Ok good! Thanks for the clarification and the info!

This is acting like some kind of lightDM issue, I wonder if it's a systemd vs. sysvinit thing..?

To be clear once you were able to get the system installed everything worked OK?

Yes, after installation it booted right into Enlightenment/lightdm-greeter, with both the init.d and systemd boot options. No issues there, apart from that disk-manager thingy.

I would have tested a LIVE-Boot into systemd, but I did not find an option for it in the LIVE-USB Menu.

Posted: **Sat Jan 20, 2024 1:21 pm**

pffftdwarf wrote: Sat Jan 20, 2024 1:10 pm
AVLinux wrote: Sat Jan 20, 2024 12:50 pm @pffftdwarf

Ok good! Thanks for the clarification and the info!

This is acting like some kind of lightDM issue, I wonder if it's a systemd vs. sysvinit thing..?

To be clear once you were able to get the system installed everything worked OK?
Yes, after installation it booted right into Enlightenment/lightdm-greeter, with both the init.d and systemd boot options. No issues there, apart from that disk-manager thingy.

I would have tested a LIVE-Boot into systemd, but I did not find an option for it in the LIVE-USB Menu.

Got it! No, the live system is sysvinit only, systemd is only a post-install option.

Posted: **Sat Jan 20, 2024 7:03 pm**

sorry for the slow reply, it's my on-call week for work and it's been a little hectic plus a 17mo old that has simultaneously RSV, influenza and metapneumovirus... :yeesh:

so it turns out I'm an idiot, I watched your tutorial video at work and was only half paying attention but I was on my umpteenth reinstall trying to figure out what I was doing wrong and on the computer name/domain page it hit me, you had said something about enlightenment being tied to that somehow, and when I left that page alone and rebooted VOILA!!! all working as it should on both my Minisforum desktops and my old sony vaio laptop w/legacy nvidia card... I'll pay closer attention to the tutorial next time... haha

Posted: **Sat Jan 20, 2024 8:51 pm**

blast0id wrote: Sat Jan 20, 2024 7:03 pm sorry for the slow reply, it's my on-call week for work and it's been a little hectic plus a 17mo old that has simultaneously RSV, influenza and metapneumovirus... :yeesh:

so it turns out I'm an idiot, I watched your tutorial video at work and was only half paying attention but I was on my umpteenth reinstall trying to figure out what I was doing wrong and on the computer name/domain page it hit me, you had said something about enlightenment being tied to that somehow, and when I left that page alone and rebooted VOILA!!! all working as it should on both my Minisforum desktops and my old sony vaio laptop w/legacy nvidia card... I'll pay closer attention to the tutorial next time... haha

Glad you got it working! Phew!

I empathize with what you're going through with your little one, that's a lot to to handle for everyone, sincere wishes for a quick recovery!

Posted: **Sat Jan 20, 2024 9:26 pm**

AVLinux wrote: Sat Jan 20, 2024 8:51 pmGlad you got it working! Phew!

yeah, me too! w00t w00t!

AVLinux wrote: Sat Jan 20, 2024 8:51 pmI empathize with what you're going through with your little one, that's a lot to to handle for everyone, sincere wishes for a quick recovery!

thanks, she was born @ 28wks via emergency c-section (God bless her, she almost killed her mother) @1lb 12.5oz miracle & 13in, she was in the NICU for almost 3mos but she's as rambunctious as her two older siblings, and is nearing 20lbs now... crazy, if you really wanna see something crazy you should see what they billed the insurance company for the 2.5mos of NICU

but enough about my baby lol, thanks for making us this beautiful linux baby right here! w00t w00t!

Posted: **Sat Jan 20, 2024 10:12 pm**

so for anyone who might possibly run into an issue after reboot where enlightenment doesn't load properly, try installing and leaving the settings on this page:

alone... according to this: https://youtu.be/Fl5TMM7cViI?t=865 the icons are tied to the computer name/domain from the setup page on the screenshot above, this makes me think more than just the icons are tied to it, because changing those settings on that install page is what caused all my problems with enlightenment not loading after initial install reboot.

it would be nice to know how those settings can be changed, but to also changed whatever config file for enlightenment needs to be changed/edited so as to match and not have those issues after install...

so I guess I'll do some digging.

Posted: **Sat Jan 20, 2024 10:35 pm**

blast0id wrote: Sat Jan 20, 2024 10:12 pm so for anyone who might possibly run into an issue after reboot where enlightenment doesn't load properly, try installing and leaving the settings on this page:

You can have any computer name you want. You just don't set a domain name unless you plan on running a service (web server, mail server, etc.) on that machine.

If this is a single network, and you do not intend setting up a local mail server or a DNS server that connect to the Internet,
then the domain name is of no importance at all and can be left as blank.

The domain name only serves to combine with the host-name to create the the fully qualified domain name (FQDN) of the system.
For example, if the domain name is company.com and the host name is host1, then the FQDN is host1.company.com. You will still
need to setup a DNS server to resolve that name to an IP address, or have some Internet DNS server point to your network.

Without a domain name, the computers can still be identified on their network by their host-name.

Since this is a home desktop being attributed a local IP address via DHCP, a blank domain name is entirely appropriate.
Specifying a domain name would have no effect at all in that case.

For more info see Wikipedia : Fully qualified domain name

Posted: **Sat Jan 20, 2024 11:31 pm**

@blast0id

You are right that the hostname and icon theme are connected but the hostname being changed shouldn't cause booting issues unless there's a weird new bug in the installer.. I will be doing a fresh install on my dev/build box tomorrow and I will experiment..

On an installed system you can simply edit /etc/hostname and /etc/hosts with mousepad as root to create a unique hostname.

Posted: **Sat Jan 20, 2024 11:44 pm**

Manual changes to /etc/hostname also need to be carried over to etc/hosts BTW.

Posted: **Sun Jan 21, 2024 8:04 am**

AVLinux wrote: Sat Jan 20, 2024 11:31 pm @blast0id

...snip... but the hostname being changed shouldn't cause booting issues unless there's a weird new bug in the installer..

No, so to clarify further, it booted fine but enlightenment wouldn't properly load. I ended up in one of two places, a login box that after putting in my info & hitting enter would disappear & enlightenment would never load ... Or you get to a blank screen with a cursor. Both scenarios you'd have to ctl+alt + F1-6 - type login credentials then "startx" but that would give you the vanilla enlightenment without AVL customizations...

Posted: **Sun Jan 21, 2024 8:42 am**

AVLinux wrote: Sat Jan 20, 2024 12:50 pm @pffftdwarf

Ok good! Thanks for the clarification and the info!

This is acting like some kind of lightDM issue, I wonder if it's a systemd vs. sysvinit thing..?

To be clear once you were able to get the system installed everything worked OK?

Just did some further "testing":

in QEMU/KVM with virtmanager the Live-USB boots normal

with "FAILSAFE" enabled it boots into some adventurous 720x340ish lightdm-greeter and you have to login. after login it looks normal (for 720x340ish)

I dont know if this is the normal behaviour, but when I set the Language to "German" in the Live-Usb boot menu: the TTYs get that info and use an qwertz layout, Enlightenment starts with US/english layout/language.

I assume that the "blankscreen" thing is, like you mentioned, an isolated issue on my machine.

Posted: **Sun Jan 21, 2024 9:02 am**

@pffftdwarf

Yes this is correct, I do mention it in the Video but I should have made a stronger point of it for non-English users.. Enlightenment requires the keyboard to be changed in it's own settings menu..

shot-2024-01-18_13-18-36.jpg

Posted: **Sun Jan 21, 2024 10:06 am**

Hi all,

A minor ISO update has been uploaded, info has been added to the first post..

Posted: **Sun Jan 21, 2024 10:14 am**

FullScale4Me wrote: Sat Jan 20, 2024 11:44 pm Manual changes to /etc/hostname also need to be carried over to etc/hosts BTW.

Thanks, appreciated!

Posted: **Sun Jan 21, 2024 11:13 am**

AVLinux wrote: Sun Jan 21, 2024 10:06 am Hi all,

A minor ISO update has been uploaded, info has been added to the first post..

There's no easy way to put this, so i'll be blunt.

The muse-sounds-manager has been the subject of a heated debate on the Musescore forums, because (a) the company that owns Musescore (Muse) didn't tell anyone the muse-sounds-manager required root access to a user's system, and (b) they were harvesting user telemetry as a result. (Much as they did with their other prize app, Audacity.)
Since then, and as a result of a large user backlash, they've included an option to turn off sending telemetry that the user can activate, BUT, the manager itself still requires root access, and runs in the background, unless the user deliberately kills it, stone dead.

I urge users who are considering installing the muse sounds libs, to make sure it's actually what you want. Unlike Musescore itself, which is licensed opensource, muse sounds are not, and are owned by Muse, the parent company.

I opted not to install the muse sounds, and i wasn't alone, by any means. I have no wish to give any company root access to my computer, no matter how many times they say it's harmless.

It's a user's decision, of course, but I felt it's important to have all the facts, before deciding one way or the other. Musescore is a fine program, and the new version, although it's less linux friendly than it was (no more jack midi, for just one reason), may well turn out to be their best yet, in the future. (I'm still on a 3.7 appimage, a "fork" of 3.6, with extras. It still has all the tools, including jack midi, and the SFZ synthesizer, for linux users.)

Alex.

Posted: **Sun Jan 21, 2024 11:51 am**

According to all reports, Muse was never 'harvesting data' from Audacity. The kickback from their announcement was pretty dramatic and their very limited telemetry, which was off by default, was pulled almost before it even hit the publish. And, it was pulled after the immediate thrashing they took.

I have watched via firewall if any version I used has ever 'written home' and if you turn off "check for updates' then it never does.

Posted: **Sun Jan 21, 2024 11:58 am**

Ugh!

Caught in the middle again... I don't use MuseScore (and rarely Audacity)

Someone on the Ardour forum suggested having Musescore without the Manager would have people missing out on the Orchestral sounds so I added it last minute for convenience..

Posted: **Sun Jan 21, 2024 12:10 pm**

CharlesV wrote: Sun Jan 21, 2024 11:51 am According to all reports, Muse was never 'harvesting data' from Audacity. The kickback from their announcement was pretty dramatic and their very limited telemetry, which was off by default, was pulled almost before it even hit the publish. And, it was pulled after the immediate thrashing they took.

I have watched via firewall if any version I used has ever 'written home' and if you turn off "check for updates' then it never does.

I have to ask. Why would an opensource entity want to add telemetry in the first place? And the reaction of the company reps when it came up regarding Musescore was almost predictable, giving they admitted to having telemetry in Audacity in the first place, but claimed it, and they, were harmless. I saw some of the savaging they took, and in my humble opinion,they deserved it, because they never gave users the option to opt in/out in the first place. It was coded to opt in by default. There's a checkbox in Musescore now, because users brought into the light what was happening.

The muse-sounds-manager requires root access, and it continues to run, after the user has downloaded the sounds. It's not opensource, even if Musescore is, at least for now.
That, imho, is a cause for concern, and at least a careful consideration by users, which is why I posted.

Posted: **Sun Jan 21, 2024 12:16 pm**

AVLinux wrote: Sun Jan 21, 2024 11:58 am Ugh!

Caught in the middle again... I don't use MuseScore (and rarely Audacity)

Someone on the Ardour forum suggested having Musescore without the Manager would have people missing out on the Orchestral sounds so I added it last minute for convenience..

Not your fault at all. How could you know if you never use the app.

If users want to add orchestral sounds, the default soundfont MSbasic.sf3 is not the worst orchestral soundfont i've heard, and there are others. Version 4 of Musescore removed all else but using a soundfont of some sort, and the proprietary muse sounds. (in Linux)

Anyway, i've said my piece, and there's no need for me to comment further.

Posted: **Sun Jan 21, 2024 12:43 pm**

alextone wrote: Sun Jan 21, 2024 12:10 pm
CharlesV wrote: Sun Jan 21, 2024 11:51 am According to all reports, Muse was never 'harvesting data' from Audacity. The kickback from their announcement was pretty dramatic and their very limited telemetry, which was off by default, was pulled almost before it even hit the publish. And, it was pulled after the immediate thrashing they took.

I have watched via firewall if any version I used has ever 'written home' and if you turn off "check for updates' then it never does.
I have to ask. Why would an opensource entity want to add telemetry in the first place? And the reaction of the company reps when it came up regarding Musescore was almost predictable, giving they admitted to having telemetry in Audacity in the first place, but claimed it, and they, were harmless. I saw some of the savaging they took, and in my humble opinion,they deserved it, because they never gave users the option to opt in/out in the first place. It was coded to opt in by default. There's a checkbox in Musescore now, because users brought into the light what was happening.

The muse-sounds-manager requires root access, and it continues to run, after the user has downloaded the sounds. It's not opensource, even if Musescore is, at least for now.
That, imho, is a cause for concern, and at least a careful consideration by users, which is why I posted.

I agree that their claim as to why telemetry was needed in Audacity was faulty, and was enough for me to create some firewall rules to check and stop it. I dont know anything about the musecore, but I do agree that is cause for concern.

I think it was positive for you to bring up the Musecore issue, and was just trying to state that the Audacity issue was not only benign but was pretty soundly rejected by the community en masse.

Posted: **Sun Jan 21, 2024 12:46 pm**

@AVLinux the saying of "Damned if you do and damned if you dont" kind of ring true here. I think it is good to provide the ability for people, as well as providing the 'watch out' for people to understand.

Posted: **Sun Jan 21, 2024 2:31 pm**

Agreed @CharlesV !

OK, well as far as the lightDM logging in/Enlightenment starting riddle goes... I have just done a complete AVL-MXe-23.1 install from the provided ISO on my main Dev box and I did create a new hostname and everything worked exactly as it was supposed to and it also did last week on my Studio box with completely different hardware (also numerous Gnome-Boxes and Virtualbox installs). I'm certainly not suggesting that people have not had the issues that they've described, of course they have! The only thing a little the same was an install on my son's Thinkpad T14-G1 and there seemed to be some issue with the backlight and lightDM because the Login screen (only) was very dim but still visible, I switched his machine to booting systemd and the issue disappeared completely..

All I can say is if you have issues they are probably related to your specific hardware and they are probably not something I can fix conclusively on my end unless the MX devs find something... Intermittent issues are always so much fun!!

Posted: **Sun Jan 21, 2024 2:46 pm**

ScreenshotWavbreaker.jpg

I do not know if this is the thread to ask about this but it is very AVL-MXE related since it is a game changer for us "sampler" users. I need to know what is the app or set of apps used to invoke "wavsplitter" in Thunar custom actions that use "sox" set of tools? I need this to happen in AVL-MXE 2020 MX19.4 edition which is based on Buster AHS. I downloaded "wavbreaker" and while it says it breaks wav files, it does not do it automagically at silence points but rather requires you to specify a time interval manually before breaking the wav file into smaller chunks so "not the same" as the custom action you showed in the video introduction to AVL-MXE 23.1 @1:23:18 time interval. I saw the terminal invoke "sox" but thats it. We sample collectors and sample makers really need this app or set of apps. Any help would be greatly appreciated. Sadly my older hardware just works best with the older Buster based MX19.4 based AVL-MXE releases so that is my reason for using the older release and wanting this set of apps or app.

Posted: **Sun Jan 21, 2024 3:47 pm**

Hi,

The Thunar custom actions are simply sox commands, but they are a combination of sox scripts in /usr/local/bin and xml entries in ~/.config/Thunar/uca.xml file

If you have sox installed you can also just run the waves splitter command in a terminal in the folder the wave's you want to split are in:

Code: Select all

for file in *.wav; do   sox -V3 $file ${file}-split.wav silence -l 1 0.1 -65d   1 0.60 -65d : newfile : restart;done

Good reference article here: https://madskjeldgaard.dk/posts/sox-tut ... y-silence/

Posted: **Sun Jan 21, 2024 4:54 pm**

AVLinux wrote: Sun Jan 21, 2024 3:47 pm Hi,

The Thunar custom actions are simply sox commands, but they are a combination of sox scripts in /usr/local/bin and xml entries in ~/.config/Thunar/uca.xml file

If you have sox installed you can also just run the waves splitter command in a terminal in the folder the wave's you want to split are in:
Code: Select all
for file in *.wav; do   sox -V3 $file ${file}-split.wav silence -l 1 0.1 -65d   1 0.60 -65d : newfile : restart;done
Good reference article here: https://madskjeldgaard.dk/posts/sox-tut ... y-silence/

Thankyou! I knew there had to be a method to get this done. I think Wavbreaker is more for extracted cd audio tracks or recorded cassette tracks to split the songs up but not so much for making multiple short samples for a sampler.

Posted: **Mon Jan 22, 2024 12:27 am**

siamhie wrote: Mon Jan 15, 2024 4:26 pm When I installed it in virtualbox (7.0.10), I found it to be really sluggish to taking a couple of minutes to open programs.

My guest machine specs I set up were

6 cores
8192 MB RAM
128 MB video
50GB disc

So I installed MX-23.1 XFCE using the same machine specs and upgraded it's kernel to the same as AVL-MXe (6.6.9-liquorix from the repo). XFCE booted up and ran fine.

Then I installed MX-23.1 KDE using the same machine specs and kernel and it barfed on boot up. After searching around for quite a while, I found this tip. Now all three OS's boot fine.

Open the settings for the machine and go to System > Acceleration. Change the Paravirtualization Interface from Default to Hyper-V.

Time will tell but you may have solved an issue I've been dealing with for months to the point of giving up on VBox... I just tried Bodhi Linux 7 in Virtualbox 7.0.14 and it ran wonderfully, will need to try a few more with newer kernels to be sure...

Posted: **Mon Jan 22, 2024 7:10 am**

AVLinux wrote: Mon Jan 22, 2024 12:27 am
siamhie wrote: Mon Jan 15, 2024 4:26 pm When I installed it in virtualbox (7.0.10), I found it to be really sluggish to taking a couple of minutes to open programs.

My guest machine specs I set up were

6 cores
8192 MB RAM
128 MB video
50GB disc

So I installed MX-23.1 XFCE using the same machine specs and upgraded it's kernel to the same as AVL-MXe (6.6.9-liquorix from the repo). XFCE booted up and ran fine.

Then I installed MX-23.1 KDE using the same machine specs and kernel and it barfed on boot up. After searching around for quite a while, I found this tip. Now all three OS's boot fine.

Open the settings for the machine and go to System > Acceleration. Change the Paravirtualization Interface from Default to Hyper-V.
Time will tell but you may have solved an issue I've been dealing with for months to the point of giving up on VBox... I just tried Bodhi Linux 7 in Virtualbox 7.0.14 and it ran wonderfully, will need to try a few more with newer kernels to be sure...

Which kernel came as default with your Bohdi Linux 7?

Code: Select all

Kernel 64-Bit Releases
    Standard: 5.15.0-78
    HWE: 6.2.0-26
    s76: 6.4.6-76060406

I eventually found out from the changelogs that the problem is the VBox host version running particular Linux guests kernels.
Our repo has virtualbox 7.0.10 which says this in the changelog: Linux Guest Additions: Added initial support for kernel 6.4

VBox version 7.0.12 has initial support for Linux Guest Additions: Added initial support for kernels 6.5 and 6.6
VBox version 7.0.14 fixed some RHEL kernels.

I found going back to Liquorix kernel version 6.1 (on the guest machine) made AVL-MXe run buttery smooth.

Posted: **Mon Jan 22, 2024 1:14 pm**

Hi, thanks for the info and for trying AVL-MXe in the first place, unfortunately VM's don't really demonstrate it's production features very well but any data I can get on boots and installs is very valuable!

I DL'd the sort of AHS version of Bodhi 's76' and it has a 6.4 kernel, so far so good... I'm itching to try Moksha on an MX base and looking into setting up a test tube VM for an MX/Moksha spin, I think it would be a match made in heaven.. I prefer straight Enlightenment for AVL but Bodhi deserves their credit for a very unique and beautiful OS that is incredibly light on resources..

Posted: **Mon Jan 22, 2024 2:02 pm**

AVLinux wrote: Mon Jan 22, 2024 1:14 pm Hi, thanks for the info and for trying AVL-MXe in the first place, unfortunately VM's don't really demonstrate it's production features very well but any data I can get on boots and installs is very valuable!

I DL'd the sort of AHS version of Bodhi 's76' and it has a 6.4 kernel, so far so good... I'm itching to try Moksha on an MX base and looking into setting up a test tube VM for an MX/Moksha spin, I think it would be a match made in heaven.. I prefer straight Enlightenment for AVL but Bodhi deserves their credit for a very unique and beautiful OS that is incredibly light on resources..

Another former Bodhi Linux user here. You got me curious, and I went to have a look at the latest incarnation. Moksha looks.....mystic.

Posted: **Mon Jan 22, 2024 3:21 pm**

Oh oh, there goes alextone... back to Bodhi!

Posted: **Mon Jan 22, 2024 3:34 pm**

AVLinux wrote: Mon Jan 22, 2024 3:21 pm Oh oh, there goes alextone... back to Bodhi!

Hehe, not for the studio box. You won't get rid of me that easy....

Posted: **Mon Jan 22, 2024 3:56 pm**

Oh no... it's begun...

This is MX Fluxbox 23.2 with Bodhi's Moksha Desktop installed... some hackery was required

shot-2024-01-22_15-47-33.resized.jpg

Full size: http://bandshed.net/images/screenshots/ ... -47-33.jpg

AV Linux will remain with Enlightenment for the duration of Bookworm, this is a scenic side trip, perhaps it will find it's way into a snapshot...

Posted: **Tue Jan 23, 2024 11:47 pm**

AVLinux wrote: Mon Jan 22, 2024 1:14 pm Hi, thanks for the info and for trying AVL-MXe in the first place, unfortunately VM's don't really demonstrate it's production features very well but any data I can get on boots and installs is very valuable!

@AVLinux I recently upgraded my computer case and haven't got around to installing my SATA SSD I use for other distros.

Stevo just updated VB to 7.0.14 and is in the MX 21 and 23 test repos. viewtopic.php?p=762914#p762914

Posted: **Tue Jan 23, 2024 11:57 pm**

AVLinux wrote: Mon Jan 22, 2024 3:56 pm Oh no... it's begun...

This is MX Fluxbox 23.2 with Bodhi's Moksha Desktop installed... some hackery was required

shot-2024-01-22_15-47-33.resized.jpg

Full size: http://bandshed.net/images/screenshots/ ... -47-33.jpg

Does this install alongside of fluxbox? I was skimming through the Moksha Guide.

Posted: **Wed Jan 24, 2024 12:13 am**

@siamhie

I don't want to say too much yet because the Bodhi guys are working an a Debian based ISO called 'deBodhi' (the devs are super-nice fellas BTW) and it's close to release but not out yet, they also have some scripts in development for installing on a vanilla Debian system.. I tried the script on MX and it did install Bodhi alongside MX-Flux however there are some Package tangles between MX Repos and the Bodhi Repos, for example mx-pipewire-setup removes a lot of Bodhi stuff (including the main theme...oops) because Bodhi still depends on PulseAudio and mx-pipewire-setup wants to remove it, Bodhi also provides their own Debian firmware Repos so there are some duplications in the firmware repositories.. In my trial and error I've come within inches of hosing the test VM several times and spent significant time in the console gluing the pieces back together so until Bodhi actually does their release and until I figure out all of the hot buttons to avoid I'm not going to steal anyone's thunder... Once they go live I'll be happy to test and share!

Posted: **Wed Jan 24, 2024 1:12 pm**

Gradually settling into our new reality....

Posted: **Wed Jan 24, 2024 6:42 pm**

Wow @alextone !

Impressive! If anyone will stress test PipeWire it's you, very glad and relieved to see you're getting big things done with it... Lol, maybe show that screenshot on Linuxmusicians... might impress the grumps who are double mad at me...lol

Posted: **Thu Jan 25, 2024 4:08 am**

AVLinux wrote: Wed Jan 24, 2024 6:42 pm Wow @alextone !

Impressive! If anyone will stress test PipeWire it's you, very glad and relieved to see you're getting big things done with it... Lol, maybe show that screenshot on Linuxmusicians... might impress the grumps who are double mad at me...lol

I've just posted it over there. Not a bad view I think. And that's just the small test orchestra.....

Posted: **Sun Jan 28, 2024 9:12 am**

Fresh AV MX installation here!
If I play an MP4 video file with mpv (the default video player) it plays at about 1/4 speed with stuttery audio.
I have found out that FIrefox will play it fine, and so will vlc (which I had to install to try it)
MPV says it's using pipewire for audio output. If I tell it to use 'pulse' on the command line I now find it works perfectly too.

So:
- should mpv work with pipewire, and if so, how do I make it play smoothly?
- Alternatively, is there a way to configure mpv to default to pulseaudio (or perhaps straight to ALSA, I haven't tried that)

Posted: **Sun Jan 28, 2024 9:43 am**

anahata wrote: Sun Jan 28, 2024 9:12 am If I play an MP4 video file with mpv (the default video player) it plays at about 1/4 speed with stuttery audio.
I have found out that FIrefox will play it fine, and so will vlc (which I had to install to try it)
MPV says it's using pipewire for audio output. If I tell it to use 'pulse' on the command line I now find it works perfectly too.

So:
- should mpv work with pipewire, and if so, how do I make it play smoothly?
- Alternatively, is there a way to configure mpv to default to pulseaudio (or perhaps straight to ALSA, I haven't tried that)

OK, partial solution found: I have created a config file with --audio-device=pulse in it, and that has worked with vlc from the command line (but only after a reboot.)
To get it to work from thunar I had to create a "custom command" for .MP4 files: "mpv --audio-device=pulse".

So that leaves me with a perfectly usable system, but the unanswered (and now slightly academic) question of whether there's a way to make it work with pipewire.

Posted: **Sun Jan 28, 2024 10:47 am**

Hi anahata!

Welcome! For those who may not know anahata maintains the second mirror for AVL-MXe and has to deal with all my ISO revisions and upload issues...

I'm still also learning about the trials and tribulations of PipeWire but at the very least it is supposed to be a drop-in replacement for PulseAudio so as you've found any app that uses PulseAudio should automatically work with PipeWire, to my knowledge almost no applications are written to explicitly use PipeWire, Pulse apps should connect as always and JACK apps will connect to 'pipewire-jack' so the fact that mpv seemingly has a PipeWire backend must be a very new feature, and I haven't set anything up to make it do anything outside it's defaults so I don't have a conclusive answer..

On my system mp4's play as expected with mpv so I wonder if it's a hardware difference involved there as well..? In general things should work pretty seamlessly if set for PulseAudio or JACK backends, I wasn't even aware that things already had PipeWire backends...

Posted: **Mon Jan 29, 2024 2:32 am**

I fixed several issues other editors cited here - https://en.wikipedia.org/wiki/AV_Linux and did some quick updating to reflect AVL 23.1 being available.

FYI - I help maintain the MX Linux and antiX Wikipedia pages (articles).

Glen - anything you note needing updating on the AV Linux Wikipedia article just let me know as my knowledge of AVL is pre-beginner.

Posted: **Mon Jan 29, 2024 9:36 am**

FullScale4Me wrote: Mon Jan 29, 2024 2:32 am I fixed several issues other editors cited here - https://en.wikipedia.org/wiki/AV_Linux and did some quick updating to reflect AVL 23.1 being available.

FYI - I help maintain the MX Linux and antiX Wikipedia pages (articles).

Glen - anything you note needing updating on the AV Linux Wikipedia article just let me know as my knowledge of AVL is pre-beginner.

Wow, thanks so much! So kind of you!

I've had nothing to do with the wikipedia page and was surprised to learn of it's existence a few years ago, it's probably better for me to remain at arms length to keep it unbiased. In having a quick look this morning I see the logo is quite outdated and there are a couple of articles by Jack Wallen that might be useful:

New logo:

AVL-MXE-Waveform-O-FULL.png

Tech Republic (AVL-MXE 21.3): https://www.techrepublic.com/article/av ... come-true/

ZDnet (AVL-MXe-23.1): https://www.zdnet.com/article/this-linu ... -paradise/

Posted: **Thu May 02, 2024 11:58 am**

helo
this look great BUT.... for me, it's not a good idea to be so big, I cannot put it on a DVD and also could not put on a USB, it says too big....I literally cannot install it
what to do?

Posted: **Thu May 02, 2024 2:24 pm**

papilonaa wrote: Thu May 02, 2024 11:58 am helo
this look great BUT.... for me, it's not a good idea to be so big, I cannot put it on a DVD and also could not put on a USB, it says too big....I literally cannot install it
what to do?

Good point! We should not forget, that from a security, stability, or resources point of view, every unnecessary line of code, software package, or evil proprietary program is a potential problem, or security risk.

MX Linux Forum

AV Linux MX Edition 23.1 (AVL-MXe) Released!

AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!

Re: AV Linux MX Edition 23.1 (AVL-MXe) Released!