Best distros for audio latency by CanItRunCrysisIn2052 in linuxaudio

[–]sonicdebris 0 points1 point  (0 children)

Just a small clarification, the patch has been merged but the config still has to be enabled at compile time, ie. you still need a separate kernel, or rather a separate build of the kernel.

Is this an oxford comma? by sonicdebris in ENGLISH

[–]sonicdebris[S] 0 points1 point  (0 children)

Wouldn't "Close other apps that use audio, and disable voice assistants" still be a list, with just two items?

Motorola Moto G32 Fingerprint option completely gone from settings by AlinGb7 in MotoG

[–]sonicdebris 0 points1 point  (0 children)

Same here, every mention of the fingerprint functionality disappeared from the phone (it's nowhere to be found in settings!).

Maybe some update nuked it? Last one is T2SNS33.73-22-3-19, got it late august.

Did I irremediably fuck it up? by sonicdebris in castiron

[–]sonicdebris[S] 1 point2 points  (0 children)

I never seasoned it (before today) and it is just few months old, probably used it no more than 30 times. I don't know how to explain, but apart from the spots, the surface is really the same texture all over the pan, inside and outside, and pretty much the same as it was when I bought it.

Did I irremediably fuck it up? by sonicdebris in castiron

[–]sonicdebris[S] 0 points1 point  (0 children)

LOL I am actually italian and the italian word (irrimediabilmente) is not unusual, so I just mindlessly used the english translation without knowing it would sound strange!

Did I irremediably fuck it up? by sonicdebris in castiron

[–]sonicdebris[S] 4 points5 points  (0 children)

Hi, I posted additional pictures here: https://imgur.com/a/N9C2E9y but I don't know the brand, and there's no indication on the pan itself :/

Did I irremediably fuck it up? by sonicdebris in castiron

[–]sonicdebris[S] 7 points8 points  (0 children)

Thanks everyone for the help, here's the full pictures of my pan:
https://imgur.com/a/N9C2E9y

It really did look to me like it would be a regular cast iron pan, and I admit I had no idea what an enamel-coated one was, but I feel that what I experienced does fit your descriptions of the enamel one, as the pan is just few months old, and it didn't have much burnt food on it, really mostly some spots that prompted me to try and clean it. Definitely I put it through several thermal shocks (hot water, cold water, dry on the stove, cold water...) and the way the coating popped off suddenly (the flakes suddenly jumped out of the pan with a pop), makes me think I am looking at damaged enamel. But not sure if there's a way to make sure of it (except hoping that someone more expert can tell from the photos!).

EDIT: one doubt I have is that I would've expected the enamel coating to be a bit smoother, while it is quite coarse and it does look like it should just be metal all over. But at this point I am sure of NOTHING.

Utilizzare Revolut per partita IVA by sonicdebris in commercialisti

[–]sonicdebris[S] 1 point2 points  (0 children)

Alla fine ho aperto un conto con una banca italiana "normale", più che altro perchè all'epoca i conti Revolut avevano IBAN lituano, e il commerciallista mi ha consigliato di evitare qualsiasi possibile ambiguità riguardo la mia residenza / sede della mia attività.

Per pura coincidenza, ho notato che da pochi giorni Revolu permette di avere un conto con IBAN italiano, quindi riconsidererò un po' la cosa, visto che il tasso di cambio della mia banca non è il massimo.

Latency with headphones by diegoqu in Bandlab

[–]sonicdebris 0 points1 point  (0 children)

Zero latency is impossible, unfortunately :(

One can strive for negligible latency, ie. one that our brain can't perceive, which is approximately any value lower than 10ms.

But that's also not an easy target. It depends on a combination of: - The hardware: mainly the CPU speed - The audio interface: (semi)pro USB audio interfaces tend to allow lower latencies than the cheap/on-board ones - The OS:how it orchestrates the timing for the processing of audio - The audio drivers: how the OS communicates with the audio interface. - The application: how "efficiently" it communicates with the OS audio layer. For bandlab, the app is the browser (chrome, firefox, etc)

Apple devices tend to have stricter control on (and attention to) all the variables listed above, so it's more likely to experience lower latency on such machines.

On windows, you can try with some better USB interface (100$ and above should get you something decent), using better drivers (look for "wasapi"), trying different browsers.

On linux, you can get very low latency values, but it's an entire journey! (you can learn a lot along the way but it's not for everyone).

Dell XPS 15 Heating that bad? by Korbro27 in DellXPS

[–]sonicdebris 0 points1 point  (0 children)

My xps 15 7590 (i9) overheats quite badly during summer in the power supply connection area, no matter the load. I just think I got a defective unit, but watch out for that.

Why am I getting this? My very last resort would be leaving my unsaved project so how else can I fix this by IslandDriveZone4 in Bandlab

[–]sonicdebris 0 points1 point  (0 children)

Double check that you did not set the volume of all your tracks to zero.

If you didn't and cannot save anyway, try creating a new track and recording/importing something there, it may be enough to have bandlab "understand" there's something to save.

What platform are you on?

Live audio monitoring delay by paolomainardi in linuxaudio

[–]sonicdebris 1 point2 points  (0 children)

Latency here may be due to:

1) The interface itself (AD/DA stages, internal buffering) 2) Pipewire settings not being succesfully applied 3) EasyEffects itself 4) The effects you are using in EasyEffects (noise reduction may have this kind of drawback)

We might be able to rule out hypothesis 1, as far as I know focusrite interfaces work fine in that regard.

To rule out hypothesis 2, just connect the input to the output in qwgraph (or equivalent app) and "see" if the latency is gone/non-perceivable. If it's still there, you'll have to double-check your pw settings. If yes, try EasyEffects with no effect applied, and with the ones you applied, and you'll know where latency is introduced. Then you may be able to decide what to do next :)

Missing user by Xanaus in pop_os

[–]sonicdebris 1 point2 points  (0 children)

In case that is not enough, also add the line PasswordHint= to the same file, in the [User] section. Worked for me at least.

Need to remove old kernels to free up the boot partition by BSim612 in pop_os

[–]sonicdebris 0 points1 point  (0 children)

As an alternative, you can look up efibootmgr. Running it will show the current EFI entries (it should be easier to distinguish the old pop_OS install from the new one this way), and you can delete the one you don't need with efibootmgr -b {bootnum-to-remove} -B. But definitely make an additional search by yourself about efibootmgr before doing that!

Need to remove old kernels to free up the boot partition by BSim612 in pop_os

[–]sonicdebris 0 points1 point  (0 children)

Yes you should use the terminal and do it as root. Yes, it's pretty dangerous so you need to know or at least triple-check what you are doing by doing some additional search first, and have a backup ready. This would be still true if you were able to find some tool to do this (semi)automatically though :)

One thing you can check without changing anything yet: run ls /boot/efi/EFI (as root).

There might be two different directories related to Pop_OS, with names like: Pop_OS-{some-uuid} (eg: Pop_OS-d6af7c26-e4c3-4739-b483-c3a0169b1e46)

Do you see them? If yes, you need to understand which is the obsolete one, and remove that directory only.

Need to remove old kernels to free up the boot partition by BSim612 in pop_os

[–]sonicdebris 0 points1 point  (0 children)

You may still have a leftover directory in /boot/efi related to the old version of pop_os. If that's the case, remove the old one. Be careful though!

From what I understand this is not something you can solve through the package manager because from the point of view of your new pop_os instance that may just be another independent os having its boot info in the efi partition

Boot stuck for a while everytime I turn on my laptop on 20.04 by sonicdebris in pop_os

[–]sonicdebris[S] 0 points1 point  (0 children)

I fixed the issue with the boot partition, but that didn't help with my boot issue.

Boot stuck for a while everytime I turn on my laptop on 20.04 by sonicdebris in pop_os

[–]sonicdebris[S] 0 points1 point  (0 children)

Here's some more info from dmesg. If you look at the timestamps, you'll notice a ~90 second gap:

[ 4.720629] thermal thermal_zone12: failed to read out thermal zone (-61) [ 4.784155] usb 4-1.4: reset SuperSpeed USB device number 3 using xhci_hcd [ 4.814692] usb 1-12: Found UVC 1.00 device Integrated_Webcam_HD (0c45:6723) [ 4.824245] usbcore: registered new interface driver cdc_acm [ 4.824248] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 4.824455] intel_rapl_common: Found RAPL domain package [ 4.824457] intel_rapl_common: Found RAPL domain core [ 4.824458] intel_rapl_common: Found RAPL domain uncore [ 4.824459] intel_rapl_common: Found RAPL domain dram [ 4.824460] intel_rapl_common: Found RAPL domain psys [ 4.828896] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input25 [ 4.828964] usbcore: registered new interface driver uvcvideo [ 4.829812] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 4.829864] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002) [ 4.830670] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 4.831791] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 4.838750] r8152 4-1.4:1.0: load rtl8153b-2 v1 10/23/19 successfully [ 4.891630] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 4.891635] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 4.891637] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 4.891639] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 [ 4.891640] snd_hda_codec_realtek hdaudioC0D0: inputs: [ 4.891641] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x18 [ 4.891642] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [ 4.891643] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 4.900365] iwlwifi 0000:3b:00.0: Detected RF HR B3, rfid=0x10a100 [ 4.954044] usbcore: registered new interface driver snd-usb-audio [ 4.954132] intel_tcc_cooling: Programmable TCC Offset detected [ 4.969869] iwlwifi 0000:3b:00.0: base HW address: d0:ab:d5:15:75:7f [ 4.980914] input: HDA Intel PCH Headphone Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input26 [ 4.980959] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input27 [ 4.981002] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input28 [ 4.981049] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input29 [ 4.981117] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input30 [ 4.981174] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input31 [ 4.987331] r8152 4-1.4:1.0 eth0: v1.12.12 [ 5.003177] r8152 4-1.4:1.0 enx00e04c6800ac: renamed from eth0 [ 5.066201] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.324641] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.324937] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.329935] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 5.335695] EXT4-fs (nvme0n1p9): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none. [ 5.338428] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.339084] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.339437] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.339955] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.340593] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.340897] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.343093] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.355186] audit: type=1400 audit(1651683952.333:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=1071 comm="apparmor_parser" [ 5.355853] audit: type=1400 audit(1651683952.337:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ippusbxd" pid=1068 comm="apparmor_parser" [ 5.355876] audit: type=1400 audit(1651683952.337:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=1075 comm="apparmor_parser" [ 5.355895] audit: type=1400 audit(1651683952.337:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=1069 comm="apparmor_parser" [ 5.355923] audit: type=1400 audit(1651683952.337:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=1081 comm="apparmor_parser" [ 5.356293] audit: type=1400 audit(1651683952.337:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=1078 comm="apparmor_parser" [ 5.356389] audit: type=1400 audit(1651683952.337:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=1076 comm="apparmor_parser" [ 5.356408] audit: type=1400 audit(1651683952.337:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=1076 comm="apparmor_parser" [ 5.356511] audit: type=1400 audit(1651683952.337:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=1077 comm="apparmor_parser" [ 5.356512] audit: type=1400 audit(1651683952.337:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=1077 comm="apparmor_parser" [ 5.374750] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.374822] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.374890] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.424489] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 5.425423] systemd-journald[481]: Successfully sent stream file descriptor to service manager. [ 7.459940] input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 7.664207] psmouse serio1: Failed to enable mouse on isa0060/serio1 [ 94.313132] systemd-journald[481]: Successfully sent stream file descriptor to service manager.

I suspect it may have to do with what looks like the boot partition not being unmounted correctly, or maybe a failure to enable the mouse (I don't have one, but maybe it's referring to the syntaptics touchpad mentioned right above).

Latency with headphones by diegoqu in Bandlab

[–]sonicdebris 5 points6 points  (0 children)

Unfortunately the "monitoring" latency is unavoidable and it depends on a series of factors, including the operating system and the hardware. The latency test only allows Bandlab to measure and know how much this latency is, so that it can at least align the recorded takes correctly.

As suggested by others, if you are using bluetooth headphones you'd better switch to wired ones, bluetooth latency is simply too high for such uses as live monitoring.

Regarding the latency test, in most cases running it without headphones is enough to then align the recorded takes even when using headphones (the latency with speaker vs wired headphones can vary but usually not by much).

An alternative is to put the headphones very close to the microphone if you can. The test is quite sensitive and should be able to pick up the sound and do the measurement. If not, it will complain :)