[mythtv-users] mythtranscode 0.32 segfaults
John Pilkington
johnpilk222 at gmail.com
Sat Jun 18 16:58:30 UTC 2022
On 18/06/2022 16:44, James Abernathy wrote:
>
>
> On Sat, Jun 18, 2022 at 11:42 AM Calvin Dodge <caldodge at gmail.com
> <mailto:caldodge at gmail.com>> wrote:
>
> Thanks, John!
>
> On Sat, Jun 18, 2022 at 10:37 AM John Pilkington
> <johnpilk222 at gmail.com <mailto:johnpilk222 at gmail.com>> wrote:
> >
> > On 18/06/2022 15:11, Calvin Dodge wrote:
> > > I grabbed the latest update from the rpmfusion site.
> > >
> > > The good news: I can now ask Mythtv to transcode files
> > > The bad new: mythtranscode consistently segfaults after a few
> seconds
> > >
> > > This is related to 0.32, since I tried it manually when that Mythtv
> > > bug prevented me from requesting it via a frontend.
> > >
> > >
> > > Here's the last bit of an strace. Note that it crashes shortly
> after
> > > opening the output file.
> >
> > >
> > >
> > > The system is running Fedora 36 on a Ryzen 5 5600G.
> > > This is rpm information:
> > >
> > > Name : mythtv-common
> > > Version : 32.0
> > > Release : 1.36.20220605git7077a824d2.fc36
> > >
> > > Does anyone have a clue as to what's happening?
> >
> > See issues #581 and #588. 32 fixes said to be cured, but it
> won't be in
> > the rpmfusion repo yet.
> >
> > https://github.com/MythTV/mythtv/issues/581
> <https://github.com/MythTV/mythtv/issues/581>
> >
> >
>
>
> I hate to butt in on this issue, but if I have a new Fedora 36
> installation and used ansible to build the dependencies and then built
> fixes/32 from source would I have any issues?
>
The issue seems to have affected people moving from fixes/31 to
fixes/32. A new build of fixes/32 from github will presumably have
today's fix.
But do you have a need or wish to do the 'transcode'? I think the
recent work has been mainly on the 'lossless cut' aspect for mpeg2
video. Many of the facilities and options look to be from the analog-tv
era.
More information about the mythtv-users
mailing list