I've only halfway read the posts in this thread, it's not something I was looking to actually do myself, but for some reason I've been sorta following along.... That being said, perhaps I'm totally off base here, but wouldn't this wiki article address what you are trying to do here?

http://www.knoppmythwiki.org/index.php? ... DArchiving

_________________
Currently Running:
Too lazy to update this with my current hardware, I'll redo it during my next install =)

Grante, it looks like you are using a PVR 350 as a capture card,
You can adjust the capture bitrates for that card down some. They are in the recording profiles under Utilites/Setup on the main screen.


Rando, I looked at that option too, it like the incldued myt2xvid3 script do a nice job although they both create a "unique" file that is not reentered into the mysql database and available as a "Recording". Usually you would mount them in your video directoy and use idmb to get thier specifics.

The main key is the ability to have the xvid file inserted back into the recording db.

mogator, I am not up to compiling code yet and of course like you zero to very little time but trying to learn this stuff more everyday..

Regards

Ah, you are right, I just gave it a quick glance and I thought I saw that it took and reinserted the file into the database, but in fact it appears it doesn't.

Sorry for the misdirection =)

_________________
Currently Running:
Too lazy to update this with my current hardware, I'll redo it during my next install =)

Yes, thats the rub. I was also thinking to make a modified version of myth.rebuilddatabase.pl to use as a "wrapper" around nuvexport. It would accept options to pass to nuvexport and then insert the resulting file into the database, but that would take me probably several hours during primetime. If I ever get to it I'll make a new post for it.

I did for several years, but a few months back I switched to an
HDHR ATSC tuner (Ethernet attached).


In the past I set up a user-job that automatically transcoded
ATSC recordings using mencoder so that the resulting file was
playable using a PVR-350, and that user-job replaced the
original file. However, though I could replace the file OK, I
was never able to re-generate a seek table that worked right.
So, that approach wasn't entirely satisfactory. A few weeks ago
I pulled the PVR-350 and replaced it with an NVidia FX5200
video card under the (mistaken) assumption that I could use xvmc
for ATSC playback.

Since the OSD and xvmc don't work together I'm still limited to
SW-only SD playback. But, I no longer needed PVR-350 compatible
MPEG2 output, so I thought I could switch from my user-job to the
built-in transcoder (which does a much better job re-building
the seek table). However, though the backend was quite happy
auto-scheduling the user-job, it won't do the same thing for
the built-in transcoder. So my choices are an auto-scheduled
user-job that can't rebuild a seek-table (and looses A/V sync
on signal dropouts), or a manually scheduled transcode job that
maintains A/V sync and builds a working seek table.

It'll work if you just replace the file and delete the seek
table. Skipping forward/back won't be as snappy, but it'll
work.

_________________
Grant

Setup a different job to test the queue function.

Set a movie to record, CommFlag is set to follow, then User Job #1 (an encode to xvid using myt2xvid3 script)

Show recorded just fine, Comm Flag is running now and there is a queued job for User Job #1 waiting it's turn.

I know it is going to dump it in the Video directory and then I have two files. I just wanted to test that it would automatically queue the job.

If it uses the same queueing process for the default transcode profiles(like Lossless) as the User Jobs then the Queue function seems to be fine.

Is my logic ok here?

Been there, done that.

I think so. It's just the auto-queuing of transcode jobs that
doesn't work. Auto-queuing of comm-flagging and user jobs works
fine. Manual queuing of transcode jobs works fine.
Processing of both transcoding and user jobs from the queue
works fine.

Why this is necessary is beyond me.

_________________
Grant

fwiw, my userjob #1 ran just fine after the commflag process.

Since I've never had any problems with userjobs, that's how I'm
doing auto-transcoding now. Instead of configuring the backend
to queue a transcode job (which it refuses to queue
automatically), I configure it to queue a userjob. That
userjob is just a shellscript that queues a transcode job. If
it's an HD recording, it queues the transcode job normally (so
it will run ASAP). If it's an SD recording, I don't want to
transcode it unless it's been sitting around for a while. So,
it sets the transcode job's status to CANCELED: that prevents
the job from running. Then there's a cron job that runs once an
hour and enables any such SD jobs that have been delayed for
more than 36 hours. That way I don't waste time transcoding SD
programs that are watched and deleted right away. The cron job
also deletes the completed user jobs so they don't clutter up
the queue.

If anybody else who can't get auto-transcoding to work is
interested in the details, let me know and I'll post the
scripts and the user-job configuration.

_________________
Grant

FWIW, I've noticed that auto-transcode jobs _will_ get
scheduled by the backend as long as they're using transcoder
number 0 (default/autodetect). Selecting a non default
transcoder profile appears to be what triggers the bug in the
backend.

Unfortunately, I could never get the "autodetect" profile to
work. :/

That said, my user-job that schedules medium-quality transcode
jobs is working fine. I'm particularly pleased with the way
transcoding of SD recordings is delayed for 36 hours.

_________________
Grant

It looks like the same issue I posted about (should have read this one first).
I'll try using autodetect/default and see if that makes a difference. One thing different for me is that my auto-transcode jobs run and create a smaller file but they do not remove the commercials. I wonder if lossless transcoding is not enabled on the low quality profile I'm trying to use...hmm.. have to look at that.

I did some digging and I think I have found out how to get transcoding to trigger automatically after a recording finishes on R5f27. In my current test the job queued by automatically after the recording finished -- it is waiting behind a job that is already running. The complexity is that there are multiple places you need to enable it.

1. utils/setup->setup->tv-settings->general->General (Jobs) (screen 3)
set default transcoder drop down to the default you want (I use medium).

2. utils/setup->setup->tv-settings->recording profiles->mpeg2 encoders->Default->screen 1
Select the flag "Enabled auto transcoding after recording".

Step 2 needs to be done for all recording profiles that you use. You also need to select the auto-transcode setting when you schedule the recording.

Marc

As I described eariler in the thread, I did all that. It just plain didn't work. Recordings have transcode jobs queued. It didn't matter whether the rule's transcoder and enable were set because of the defaults or if they were set manually.

_________________
Grant

Grant, it is working on my machine. Let me know if you want to compare notes on configuration settings.

Marc

No thanks -- been there, done that (several times). I've
compared configs before and come to the conclusion that it just
doesn't work on some machines (I'm not the only one with this
problem).

Setting it up to automatically schedule a user-job works fine,
and that lets me delay transcoding for 36 hours.

_________________
Grant