[mythtv-users] 0.25 mpeg2 lossless transcoding works again! hallelujah! except...

[Steven Adeff]

On Sat, Mar 17, 2012 at 5:03 PM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 03/17/2012 03:43 PM, Steven Adeff wrote:
>> On Fri, Mar 16, 2012 at 10:14 PM, Steven Adeff wrote:
>>> On Thu, Mar 15, 2012 at 2:51 PM, Raymond Wagner wrote:
>>>> Within Recording Profiles, you should be limited to accessing those
>>>> corresponding to card types you currently have configured, and
>>>> transcoders.  Transcoders should always show up unless its either
>>>> missing, or marked as not default, and I don't see how the code could
>>>> cause either state to occur.  Could you post the output of...
>>>>
>>>> SELECT * FROM profilegroups WHERE cardtype="TRANSCODE";
>>>
>>> mysql>  SELECT * FROM profilegroups WHERE cardtype="TRANSCODE";
>>> Empty set (0.00 sec)
>>
>> I used my parents sql database to add the TRANSCODE entry into my
>> profilegroups then I was able to add an MPEG-2 profile as a lossless.
>> now I see it as an option. if I choose "default" this is what I get in
>> the trancode log:
>
>
> Since theirs is a different version and since there's a lot more to
> recording profiles than what you see in profilegroups, your setup is
> probably still broken.
>
> MythTV does not allow deletion of the default profiles, so there's no
> mechanism for you to re-create them.  That means that either yours were
> deleted due to someone's directly editing the database or lost due to a bad
> database restore (i.e. someone trying to pick and choose what to restore
> rather than using a full restore).  Either way, you may not want to trust
> your database/schema.
>
> That said, for someone running 0.25beta, the below SQL should restore the
> recording/transcoding profiles to defaults.  You will then have to
> re-configure any that you changed.  However, you unless you know exactly how
> you lost your recording profiles, you may want to use the
> only-useful-to-"salvage what data I can from a corrupt database or schema"
> partial restore approach (
> http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup
> ).
>
> No one running any other version of MythTV should use the below SQL (for
> those reading archives).  Doing so will cause problems.
>

Mike,

thanks for the help. I would not be surprised of any issues with my
database, it's had a rough life =P
I will go with a partial restore to fix things.


first though, I ran your sql to see what would happen, it still fails,
here's the output:
$ sudo -H -u mythtv /usr/bin/mythtranscode -j 37071 --profile
autodetect --honorcutlist --verbose most --loglevel info --syslog
local7
2012-03-18 09:21:13.700407 C  mythtranscode version: master
[v0.25-beta-165-g53761e2] www.mythtv.org
2012-03-18 09:21:13.700477 N  Enabled verbose msgs: most
2012-03-18 09:21:13.700542 N  Setting Log Level to LOG_INFO
2012-03-18 09:21:13.700686 I  Added logging to the console
2012-03-18 09:21:13.700740 I  Added syslogging to facility local7
2012-03-18 09:21:13.700758 I  Added database logging to table logging
2012-03-18 09:21:13.700887 N  Setting up SIGHUP handler
2012-03-18 09:21:13.701018 N  Using runtime prefix = /usr
2012-03-18 09:21:13.701037 N  Using configuration directory =
/home/mythtv/.mythtv
2012-03-18 09:21:13.701184 E
(old)Settings::ReadSettings(settings.txt) - No such file settings.txt
2012-03-18 09:21:13.701308 I  Assumed character encoding: en_US.UTF-8
2012-03-18 09:21:13.709061 E
(old)Settings::ReadSettings(settings.txt) - No such file settings.txt
2012-03-18 09:21:13.709356 E
(old)Settings::ReadSettings(/usr/share/mythtv/mysql.txt) - No such
file /usr/share/mythtv/mysql.txt
2012-03-18 09:21:13.709377 E
(old)Settings::ReadSettings(/usr/etc/mythtv/mysql.txt) - No such file
/usr/etc/mythtv/mysql.txt
2012-03-18 09:21:13.721677 E  (old)Settings::ReadSettings(./mysql.txt)
- No such file ./mysql.txt
2012-03-18 09:21:13.721749 I  Using localhost value of mythbackend
2012-03-18 09:21:13.722089 I  DefaultUPnP() - No default UPnP backend
2012-03-18 09:21:13.722115 I  Testing network connectivity to '192.168.1.151'
2012-03-18 09:21:13.724446 I  Managed child (PID: 6741) has started! *
command=ping -t 3 -c 1  192.168.1.151  >/dev/null 2>&1, timeout=0
2012-03-18 09:21:13.724874 I  Starting process signal handler
2012-03-18 09:21:13.725402 I  Starting IO manager (read)
2012-03-18 09:21:13.725485 I  Starting process manager
2012-03-18 09:21:13.725559 I  Starting IO manager (write)
2012-03-18 09:21:13.825676 I  Managed child (PID: 6741) has exited!
command=ping -t 3 -c 1  192.168.1.151  >/dev/null 2>&1, status=0,
result=0
Segmentation fault

if I run it with -m instead of the --profiles argument though, it works fine.

I'll do this partial restore and continue to try this.

-- 
Steve
http://www.mythtv.org/wiki/User:Steveadeff
Before you ask, read the FAQ!
http://www.mythtv.org/wiki/Frequently_Asked_Questions
then search the Wiki, and this list,
http://www.gossamer-threads.com/lists/mythtv/
Mailinglist etiquette - http://www.mythtv.org/wiki/Mailing_List_etiquette