MX Linux Forum

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/

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.

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...

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

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..

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

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 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