Ukn Unknown wrote:
> I can confirm that I am using HW transcoding VAAPI using iGPU (Intel) for live transcoding. I tested also SW transcoding (resized to 384). My tuner is USB.
> My recommendation is to try to compile your own deb (from Master) ... in order to get support.
> Is not clear when mmarley spined off from Master ... bellow is my configure results.
> My codec has the following settings and is able to transcode H264 HD and MPEG SD to h264 (libx264).
> SW transcoding (decode + encode) is very CPU intensive ... what CPU and RAM speed you have?
>
> !codec.png!
>
> [...]
Thanks for replying.
Ugggh, this is a long story, but in the end I got it working.
This all started long ago (and on a planet far far away) when I was trying to follow the ubuntu install instructions.
I was expecting that the ubuntu ppa instructions would be like every other ppa instructions, and would say something like "add this ppa".
Instead, it doesn't say that. At the top (for the offical package) it has a header labelled "setup" with a wget instruction to download and run some bash script.
Ugggh, no explicit instructions on what to do, and some command to download and run some sketchy bash script as sudo. Might as well walk across a minefield ;-)
So I downloaded the script, inspected it, ran it, and crossed my fingers.
After that, tried an "apt update" and it just errored out.
I had enough of that.
I moved on to the the below section labelled "ubuntu ppa" where the mamarley stuff is.
Ok, this is looking more familiar, as it instructs to add the ppa.
Tried to "stable" ppa and...bzzzzt.. it doesn't exist!
We're 2 for 3 on these instructions now.
Moved on to the last chance, and tried to install the unstable mamarley.
Success, it installed.
Then I ended up with software where transcoding does not work, and had to make the above post.
So then I tried as you suggested, and tried to compile myself.
Since I was having such bad luck, I decided to do it on a VM (because I sorta knew I'd be doing this over and over).
I ended up getting it compiled, however when it ran, it would just crash.
Spent hours on that with no success.
With all options exhausted, I decided to go back and take another look at the very first install method (the official package that has you run some bash file).
I had a look at what it was doing, and found that it was generating a ppa file (in /etc/apt/sources.list.d) with completely wrong information.
It was populating the file with info from my linux mint install (I forget, it was stuff like "vanessa", etc).
So I just manually edited the file, and changed that linux mint info to ubuntu info (ubuntu/jammy).
I then got apt to work, and it could now find the repo.
Uggghh, like I said at the top, why not just have ppa instructions like everywhere else, instead of a bash file that generates wrong info.
Ok, so I'm still doing this on a VM. After I installed the official package from the repo, the software ran and crashed (just like the compiled version).
Can't catch a break!
So with nowhere to go, for the heck of it, I installed the one know working version on the VM (the mamarley unstable).
It too crashed!
So I figured, maybe all this crashing is just because it is running on a VM, and with any luck, there's nothing wrong with the compiled versions or the official package if I run them on a HW machine.
So I installed the official package on a HW machine (now that I know how to fix the install) and it ran AND transcoding works.
So I got to my destination through the longest possible path.
Hopefully there is some info above to shorten the path for others:
* mamarley stable doesn't exist
* mamarley unstable doesn't transcode
* for the official package, run the bash script and then check your /etc/apt/sources.list.d file to make sure it has the right info in it
* for some reason, all versions crash on a vm
Not sure what's up with running on a VM. I was using Virtualbox. I tried enabling every kind of "hardware" feature (pae, vts, graphics 3d accel).
