mythtv-33.1/mythtranscode ... working for anyone?

eccerr0r

I'm still on mythtv 32 on my backend and my mythtranscode segfaults when trying to do

$ mythtranscode --chanid 20503 --showprogress --starttime 20240109060000 -m --honorcutlist

on my backend.

Anyone have this working on any version of mythtv? I haven't updated the backend to 33.1 yet in worries of some database chaos, though some of my frontends are up to 33.1. Might be worth to try to update to 33.1 if someone reports it working?

My backend is using too much disk space ...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

Ralphred · Guru Joined: 31 Dec 2013 Posts: 501

I've not actively used it in a long time, but you can transcode it yourself, then just poke around in the database and pointing to the new file.
It was version 20 ish I last wrote anything that did that, but i can't see that part of the DB structure changing that much TBH.

sam_ · Developer Joined: 14 Aug 2020 Posts: 1678

Please give a backtrace, per https://wiki.gentoo.org/wiki/Debugging#Per-package.

eccerr0r · Posted: Thu Jan 18, 2024 11:38 pm Post subject:

Yeah I was about to get gdb on it, but that would mean I need to re-merge it with debug symbols. Might be easier to update to 33 first, and not quite ready for that just yet -- just wanted to see if anyone had it working or not first before I make a decision on what to do next.

Hardware could also fix software problems too in this case. My underlying problem is that I'm running out of disk space, but I hope someone's not going to call this a X-Y problem when I want to cut out commercials to save disk space :)
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

sam_ · Developer Joined: 14 Aug 2020 Posts: 1678

sure, but we could've debugged this by now...

eccerr0r · Posted: Fri Jan 19, 2024 10:24 am Post subject:

hmm...progress!

seems to be working on my 33.1 frontend machine, just manually invoking mythtranscode! however if I just replace the recording file, the database isn't synced up anymore, thinks it's the old file size, but definitely saved a bunch of disk space on this one test recording...

Now the question is if there's something about the backend box that's causing it to crash mythtranscode-32 but work on mythtranscode-33.1 ...

and yeah this might be a reason I should now really look into upgrading to 33.1 on the backend!

---

mythcommflag --file $FILE --rebuild # worked on a backend

fixes the seek table and length...ah. Might have to just chop the files on the frontends through nfs for now since this seems to be reliable.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?