BentiGorlich @ BentiGorlich @gehirneimer.de

Beruflich Web-Entwickler, privat ein Ober Nerd und Links-Grün versifft...

---

Read more

Posts

13

Comments

267

Joined

2 yr. ago

@Blaze@lemmy.dbzer0.com @fediverse@lemmy.world @mkmusic@torishiro.com @melroy@kbin.melroy.org Yes we support basically everything mentioned here. Peertube videos, Lemmy posts and Mastodon / Misskey, etc. (called mircoblogs in the UI) On the microblog side mbin still has a long way to go to be perfect, right know you just know that it is not the primary focus.

Mbin is written in php together with the smyfony framework. We always welcome new devs and I'll do my best to answer any questions that will arise :)

Are you sure? I would expect AMD to have their own download & install instructions that could be used on any distro

Oh you don't have to do anything like that for everything else, because it is just in the kernel and in mesa... This "pro" driver comes with some custom stuff like apparently their proprietary encoders, but I read multiple times that it has just terrible performance for everything else so don't bother...

By rips, do you mean your source media is already in a container, like a .mkv or .mp4 file?

yes mkv files

you might take a look at MVKToolNix

I will :)

HandBrake supports AMD VCN hardware video encoding

yes, but that is not viable as the amdgpu-pro drivers are only available on LTS releases and on a few selected distros

You haven't said what source material you're encoding

Mostly BluRay rips, so movies and TV-Shows

Are you aware of Vulkan Video?

I actually was not. Is it any good? But Handbrake does not support that either, does it?

you might consider investing some time in learning ffmpeg commands.

I am, but for anything involving multiple audio and subtitle streams and stream selection in general it is not an option for me...

Never heard of it, but it looks very intimidating 😅

With handling all the subtitles and audio streams I really prefer a GUI especially since it is not a one size fits all with the files I am dealing with

I had a similar, but not as bad situation with my power button (it was just stuck sometimes, causing restarts and what not). I regularly waited 2-4 weeks for a reply... So yeah customer service is really bad at the moment... Still love the product, though

they are already actively working with e/OS and iodéOS. Don't know if e/OS already supports Android 15 like iodé does, but they could just focus on that next release...

I own a FP4 and I've been on Android 15 for a while now, as I run iodéOS ... To me it is astonishing how a thrid party OS can have better support than the first party one 😅

I used to use OnlyOffice, but switched to Nextcloud office because I like the UI and the documentserver better. Easier administering and the official solution

I fullheartedly agree... My mbin servers have been targeted multiple times by stupid AI scraper bots and even google didn't adhere to the request limit set in the robots.txt...

Ok so exactly how mbin spots cross posts at the moment. But combining the comment sections is a cool idea. Obviously requires your server to be subscribed to the different communities, but still cool 👍

What happens when three different users post libks to the same article? Or when the test is different? Basically how do you match these posts?

https://youtu.be/-8bTquKjzos That sums it up. The definition of what counts as "selling data" changed...

The mozilla thing seems to be mostly bad PR, but yeah...

More than once 🙈

I second that :D

So these are the log messages right after the device failed:

Jan 21 11:20:41 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:41 fedora pipewire[2460]: pw.link: 0x55db4830afa0: one of the nodes is in error out:error in:suspended Jan 21 11:20:41 fedora pipewire[2460]: pw.link: 0x55db485f9360: one of the nodes is in error out:error in:suspended Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db48355240: one of the nodes is in error out:suspended in:error Jan 21 11:20:44 fedora pipewire[2460]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.Direct__Direct__sink-56) suspended -> error ((null)) Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db482bdca0: one of the nodes is in error out:idle in:error Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db47b39140: one of the nodes is in error out:idle in:error

I have no idea how to unsuspend the device after it errored, nor do I know why it errored. Like I said in the OP I've tried turning it off and on again, but the only solution I have found is to reboot which sucks... I changed the sampling rate from 41k to 48k but that didn't change anything. I have no idea how to change the bit depth of the device though. I applied the fixes from the repo you linked, but I am not able to install the version of alsa they referenced in there. Fedore 41 only comes with the 2 most recent versions it seems...

I will look into that, thanks for your help, time and effort ❤️

A small capture of the log (these errors were repeating multiple times):

Wed 2025-01-15 15:09:47 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.audioadapter: params Spa:Enum:ParamId:EnumFormat: 1:0 (follower format) The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.HiFi__Line1__sink-55) suspended -> error ((null)) Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.audioadapter: params Spa:Enum:ParamId:EnumFormat: 1:0 (follower format) The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: pw.node: (alsa_input.usb-046d_Logitech_Webcam_C925e_AE792FAF-02.analog-stereo-60) suspended -> error ((null)) Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: spa.audioadapter: params Spa:Enum:ParamId:EnumFormat: 1:0 (follower format) The device or resource is busy/occupied Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error

I translated the error messages, because they were in German.

I think the most important line might be this one as this is the audio device I am actually using:

Wed 2025-01-15 15:09:49 CET fedora user@1000.service/pipewire.service[2482]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.HiFi__Line1__sink-55) suspended -> error ((null))

Since they are started with the user session these services do only exist there. If you try to restart them without the flag they just don't exist.

The journal would be a nice way to look for sure, but the command you posted throws an error for me:

Using --boot or --list-boots with --merge is not supported.