Thread for AV Linux 2020.4.10 Issues

[rohitverma1]

Also, mpv freezes when open large files. Maybe it is not able to buffer on-the-fly. Could be because of transparent_hugepage=never ? This has not happened before.

When i tried to run mpv from terminal, mpv reported "[ao/pulse] The stream is suspended. Bailing out."
One solution is to let ALSA handle everything.
For detailed explanation, read this.

Interestingly, freezing doesn't happen when dedicated gpu is used for mpv playback.

I am still finding a better solution. Let me know when you find one or know one

[GMaq]

Hmmm

That is a strange bug in mpv.. What if you use it with JACK? It does also connect directly to JACK

Also you probably could remove the transparent hugepage boot parameter, it was supposed to improve performance but we started using it a long time ago, it's possible it's not even relevant in newer kernels.. *shrugs

https://mpv.io/manual/master/#audio-output-drivers

[Robin Cherry]

I've been using your distribution for the last year. Awesome work!

I'm excited to try the new version but searching around I haven't been able to find if there are any means to upgrade an existing install. Do I take it then that I am meant to download to a USB and do a fresh install or am I missing something?

[GMaq]

I've been using your distribution for the last year. Awesome work!

I'm excited to try the new version but searching around I haven't been able to find if there are any means to upgrade an existing install. Do I take it then that I am meant to download to a USB and do a fresh install or am I missing something?

Hi Robin,

Because this version of AV Linux has an entirely new base (from Debian 9 -10) it is not a matter of upgrading a few core packages. On top of that there are a lot new integrated features so AVL 2020 has to be installed from the new ISO.

[Robin Cherry]

Okay, that's understandable. Thanks for the quick reply.

Keep up the good work,
Robin

[rohitverma1]

Hi GMaq,

While working in Ardour, if i try to add a yoshimi plugin on a midi track when there is already a yoshimi plugin on any other track(not on the one i'm trying to add on), ardour crashes and there is an xrun count on Qjackctl. You can reproduce this with following steps :-

1. Start Jack server with Qjackctl using your choice of interface
2. Open Ardour and connect with Jack. Make a new project.
3. Add a MIDI track, add a yoshimi instance on it. No matter stereo or mono
4. Add another MIDI track, add new yoshimi on it.
5. Ardour crashes. See an xrun count on Qjackctl interface.

Please take a look into it. No need to hurry though

[varpa]

What size partition is needed for AVLinux 2020.4.10? I'm trying to install on 19GB partition and it fills up entirely at the
60% point of installation. In the past this size of partition worked. Thanks.
...Later, create a 35GB partition and successfully install AVLinux 2020.4.10 which requires 26GB. Perhaps this size should be put in the manual, because it currently shows installation to a 15GB partition. ... OK now I see your reply. Thanks. In the past I had created a number of 20GB partitions so I could install different Linux versions. I see I need to update my OS partition size.

[GMaq]

What size partition is needed for AV Linux 2020.4.10? I'm trying to install on 19GB partition and it fills up entirely at the
60% point of installation. In the past this size of partition worked. Thanks.

I build and work on AVL in 24Gb Virtualbox VM's and that hasn't changed, but somebody else reported that the partition size required had gone up from previous versions when they installed as well. Since drive sizes have increased and storage has gotten so cheap in recent years I kind of got away from a recommended install partition size figure.. I would say to be safe maybe a rough rule of 10 from the ISO size? So 3Gb ISO= 30Gb partition?

[GMaq]

Hi GMaq,

While working in Ardour, if i try to add a yoshimi plugin on a midi track when there is already a yoshimi plugin on any other track(not on the one i'm trying to add on), ardour crashes and there is an xrun count on Qjackctl. You can reproduce this with following steps :-

1. Start Jack server with Qjackctl using your choice of interface
2. Open Ardour and connect with Jack. Make a new project.
3. Add a MIDI track, add a yoshimi instance on it. No matter stereo or mono
4. Add another MIDI track, add new yoshimi on it.
5. Ardour crashes. See an xrun count on Qjackctl interface.

Please take a look into it. No need to hurry though

Actually just to clarify..

My part in AV Linux is a limited one, collecting the apps, looking for versioning and shooting for as many bug fixes as possible and assembling them on the ISO with common-sense defaults and making sure they function at a basic level... (ie do they run when the launcher is clicked). If an application needs or functions better with other helper applications I try and have those set up and prepared as well. On top of that my responsibilities are convenience features like the AV Linux Assistant and nipping tucking and tweaking some configuration files here and there to fix known issues before the User knows they are there. Of course getting a good solid kernel that allows me to build and distribute the ISO and for the user to be able to install it within the capabilities of Systemback. And lastly documenting and trying to answer as many FAQ's as possible with the User Manual.

My area of quality control is in the presentation of the applications but I am not really the maintainer and bug fixer of the applications themselves.. For your Yoshimi example, actually Yoshimi is a custom build because I know the developer through this site and he sent me a private request to ensure an up to date build because Yoshimi is not under the umbrella of KXStudio's repo and the version in Debian is several versions old.. So for my part I have built the package, made sure the standalone runs and made sure the LV2 plugin instantiates in Ardour. That is the point where I stop and if there are further more complex issues like the one you are experiencing it is really a matter of directly talking to Yoshimi or Ardour's developers.. I am a casual user of both but I certainly have no more in-depth knowledge of their code than any other casual user.

@folderol is one of the principal developers of Yoshimi who frequents this forum and the Yoshimi help page is here:
http://yoshimi.sourceforge.net/contact. ... iling-list

[glowrak guy]

Hi, gmaq...A couple days ago, I was able to install the free Cakewalk By Bandlab, using it's Bandlab Assistant.
This was in Ubuntu Studio 19.10, with wine-staging 5.6, and a new wineasio that appeared in synaptic
(I think from KX repo?)

Anyway, the install was a little bumpy, but eventually finished, and after a reboot,
registering wineasio, and adding a few wine over-rides, It started up, scanned vsts,
and I was able to use SampleTank 3 and Syntronik frok IK Multimedia.
I suspect your AVLinux might be better configured than my Ubuntu, and if time
and interest exist, Bandlab Assistant is the portal from which the Cakewalk daw
is downloaded and then installed. Perhaps Cakewalk was one of your
pre-linux audio tools? Cue the wayback machine...

https://www.bandlab.com/products/desktop/assistant

I think the bandlab assistant defaults to being a start-up app, not sure
if wine cares much.
Cheers

[GMaq]

@glowrak guy,

Hi! Thanks for the heads up, I may check it out although I was a Turtle Beach (Voyetra) Digital Orchestrator then CubaseVST guy back in the day... I never did use CW, but had some friends who really liked it... I recently exhumed EnergyXT... lol why not CakeWalk!

[Robin Cherry]

I'm having an odd problem installing avl2020. I'm using a bios Sandy bridge computer and an ssd on sata installing from a USB key made using dd in avl2019 with a freshly downloaded avl2020 that passed its md5 test.

I've followed the instructions to a T so far as I can tell with the one exception being that I am dual booting with manjaro and thus have a seperate home partition. For some reason rather than being given the option of installing live system I'm only given the option to install current system. When I try to install I keep getting a failure on systemback when it's copying the files that says

"The system installation has been aborted!

There has been critical changes in the file system during this installation"

This happens whether I check the format boxes in systemback or not, whether I transfer user files or not, and whether I reboot after making my partitions in gparted or not.

Any help or tips would be much appreciated appreciated.

[GMaq]

I'm having an odd problem installing avl2020. I'm using a bios Sandy bridge computer and an ssd on sata installing from a USB key made using dd in avl2019 with a freshly downloaded avl2020 that passed its md5 test.

I've followed the instructions to a T so far as I can tell with the one exception being that I am dual booting with manjaro and thus have a seperate home partition. For some reason rather than being given the option of installing live system I'm only given the option to install current system. When I try to install I keep getting a failure on systemback when it's copying the files that says

"The system installation has been aborted!

There has been critical changes in the file system during this installation"

This happens whether I check the format boxes in systemback or not, whether I transfer user files or not, and whether I reboot after making my partitions in gparted or not.

Any help or tips would be much appreciated appreciated.

Hi Robin,

How large is your AV Linux partition? Is it possible you're running out of HDD space during the install? I've had a few reports that AVL 2020 requires more disc space than previous versions when installed. AV Linux is built in 24Gb virtualbox drives but an install rule of thumb may be 30Gb to allow a comfortable amount of space..

[Robin Cherry]

29.8gb for the root and 51gb for the home. It fails after only copying a few Gb to it but at different percentages every try. I should also maybe mention that the swap partition is on my HDD to save read/writes on my sdd if that makes a difference.

I'm going to try installing without the seperate home partition activated and move things over later and see if that makes a difference.

Edit: it made no difference

Edit #2: I mistakenly was dd'ing to sdg1 instead of sdg. If I dd to sdg it reformats the whole drive and eliminates the second partition, if dd to sdg1 it won't boot. I'm not sure why unetbootin won't work, and in the manual you don't recommend it for non uefi systems anyway if I understood your meaning.

Edit #3: To rule out my own stupidity I installed debian 10 on the key using the same method, dd'ing to sdg. It booted and installed on the first try.

[pledge]

Hi,

I have a question due to the WLAN Module Intel ax 200. And sorry, if my question seems to be stupid - I'm not a OS-Specialist.

In generally my WLAD should be supported in Linux if the kernel is 5.1 or higher (https://www.intel.de/content/www/de/de/ ... rking.html).

But in the test with the Live-System from USB the wifi Intel ax 200 does not work, only some older Wifi-USB-Stick.
But the kernel of the live System seems to be 5.4, if I understood this correctly. Therefore it should work theoretically.

Then I read that the kernel is somehow custom built - if I understood correctly.

So my questions:
1. Is this the reason why the AX 200 doesn't work and
2. does this mean, that even after installation of AV Linux on my HD and getting all updates, my WLAN Module Intel ax 200 still won't work?
3. If this is the case, are there as well security updates, that usually come with new kernels and as well won't reach the kernel of AV Linux in a timely manner?

Thank you!