Recording with Firewire

[dmfrey]

I am experiencing some bizarre behavior when trying to record with firewire. I am getting intermittent recordings. If a show records, there is no issue, however, if I see in the logs that no signal was received within 15 seconds, the recording proceeds to record nothing for the duration and when complete, myth-backend dies.

My setup:
AMD 64 3200+
Asus nvidia 6200 turbo
250 GB hd
PVR 150 - Tuner 1
Firewire from DCT-6200 - Tuner 2

I can record from the pvr 150 without issue.

I did a fresh install of the latest beta, mythbuntu-7,10-071002-amd64.iso, and obtained all the latest updates from the repo. This only appears to be since the update from the repo occurred.

I understand that there are issues with recording with firewire, i.e. the port seems to want to change from 2 to 1 whenever it feels like it. I tried getting around this issue by plugctl at regular intervals to reset the firewire subsystem so that it is reading the information accurately. However, after doing this, I see that the plugreport showed the correct information and myth-backend still died.

Thanks for any help. Please let me know if there is anymore information I can provide.

[tgm4883]

Unfortunatly that is a problem with firewire. It sounds like a poorly broadcast signal from the cable company. Is the backend log showing any errors?

[dmfrey]

Unfortunately, the mythbackend.log doesn't show anything because the backend server has died. The only message is that a recording has finished.

I was attempting to do a cronjob at 28 and 58 minutes past each hour to reset firewire with plugctl so that it is always up to date. Not sure if that helped or hurt anything. Maybe I should try this in the mythty-backend init script instead of every half hour.

I was thinking of looking at IEEE1349 Commander project on Sourceforge to see if that utility can perform the reset.

[tgm4883]

Yes, and the backend log should tell you why it crashed. If nothing is in there you should look into the depth of logging that is being done.

[dannyboy79]

the latest firewire_tester can reset the firewire bus just fine. You have to make sure that your firewire input is associated to a source that only has the channels that are "in the clear". I used test-mpeg2 to find out all of mine. I get 8 of them.

[dmfrey]

Here is the output from my logs

2007-10-09 20:38:58.056 AFD: Opened codec 0x830e60, id(MPEG2VIDEO) type(Video)
2007-10-09 20:38:58.057 AFD: Opened codec 0x917330, id(AC3) type(Audio)
2007-10-09 21:00:02.422 TVRec(2): Changing from None to RecordingOnly
2007-10-09 21:00:02.442 TVRec(2): HW Tuner: 2->2
2007-10-09 21:00:04.037 FireRec: Buffered packets 2000 (8000 KB)
2007-10-09 21:00:04.037 Started recording: The Unit "Always Kiss Them Goodbye": channel 2181 on cardid 2, sourceid 2
2007-10-09 21:00:04.074 scheduler: Started recording: The Unit "Always Kiss Them Goodbye": channel 2181 on cardid 2, sourceid 2
2007-10-09 21:00:19.058 FireRec: No Input in 15 seconds [P:0 N:2] (select)
2007-10-09 22:00:00.252 TVRec(2): Changing from RecordingOnly to None
2007-10-09 22:00:00.261 Finished recording The Unit "Always Kiss Them Goodbye": channel 2181
2007-10-09 22:00:00.264 scheduler: Finished recording: The Unit "Always Kiss Them Goodbye": channel 2181
2007-10-09 22:34:54     firewire ownership acquired
2007-10-09 22:34:58.268 Using runtime prefix = /usr
2007-10-09 22:34:58.438 New DB connection, total: 1
2007-10-09 22:34:58.482 Connected to database 'mythconverg' at host: localhost
2007-10-09 22:34:58.486 Current Schema Version: 1160
Starting up as the master server.
2007-10-09 22:34:58.511 mythbackend: MythBackend started as master server
2007-10-09 22:34:58.532 New DB connection, total: 2
2007-10-09 22:34:58.537 Connected to database 'mythconverg' at host: localhost
2007-10-09 22:34:58.539 EITHelper: localtime offset -4:00:00 
2007-10-09 22:34:58.543 New DB connection, total: 3
2007-10-09 22:34:58.544 Connected to database 'mythconverg' at host: localhost
2007-10-09 22:34:58.689 EITHelper: localtime offset -4:00:00 
2007-10-09 22:35:00.252 New DB scheduler connection
2007-10-09 22:35:00.253 Connected to database 'mythconverg' at host: localhost
2007-10-09 22:35:01.656 Main::Registering HttpStatus Extension
2007-10-09 22:35:01.656 mythbackend version: 0.20.20070821-1 www.mythtv.org
2007-10-09 22:35:01.657 Enabled verbose msgs:  important general
2007-10-09 22:35:01.669 AutoExpire: Found 2 recorders w/max rate of 210 MiB/min
2007-10-09 22:35:01.671 AutoExpire: Required Free Space: 2.6 GB w/freq: 5 min
2007-10-09 22:35:02.271 Reschedule requested for id -1.
2007-10-09 22:35:03.491 Scheduled 468 items in 1.2 = 0.85 match + 0.37 place
2007-10-09 22:35:03.497 scheduler: Scheduled items: Scheduled 468 items in 1.2 = 0.85 match + 0.37 place
2007-10-09 22:35:03.500 Seem to be woken up by USER
2007-10-09 22:35:08.521 mythbackend: Running housekeeping thread
2007-10-09 22:36:29.823 MainServer::HandleAnnounce Monitor
2007-10-09 22:36:29.827 adding: mythcenter as a client (events: 0)
2007-10-09 22:36:29.828 MainServer::HandleAnnounce Monitor
2007-10-09 22:36:29.830 adding: mythcenter as a client (events: 1)
2007-10-09 22:37:10.301 JobQueue: Commercial Flagging Starting for The Unit "Always Kiss Them Goodbye" recorded from channel 2181 at Tue Oct 9 21:00:00 2007
2007-10-09 22:37:10.307 commflag: Commercial Flagging Starting: The Unit "Always Kiss Them Goodbye" recorded from channel 2181 at Tue Oct 9 21:00:00 2007
2007-10-09 22:37:10.429 Using runtime prefix = /usr
2007-10-09 22:37:10.444 New DB connection, total: 1

You will notice at 21:00 the program starts to record.

At 21:00:19, the message FireRec: No Input in 15 seconds [P:0 N:2] (select) is displayed in the logs.

At 22:00, This message is displayed: Finished recording The Unit "Always Kiss Them Goodbye": channel 2181. The resulting recording is nothing but a black screen. This is where the backend shutdown.

I restarted it at 22:34:54 when my mythtv user obtains ownership of /dev/raw1394. As you can see, there was no message as to why mythbackend died.

I have been noticing these messages when reviewing dmesg, however, I cannot tie them to outage in the mythbackend.log.

[80995.801581] mythbackend[5137] general protection rip:2afb074cb6ab rsp:428077d0 error:0

Thanks again for any help.

[tgm4883]

just to be sure. Have you checked to see if there is copy protection enabled on that channel?

[dmfrey]

It was the HD CBS offered by RCN in Allentown, PA. This channel has not been encrypted in the past. None of their broadcast channels are encrypted. I guess I could test that this same behavior occurs by setting it to record something off of, say, HBO, which I know to be encrypted.

[tgm4883]

Or you could just check the channel. Wouldn't that be an easier test to see if it is encrypted. I believe the button combo is like power then quickly press exit (or something like that, check the guide) then check for the two different encryption/drm settings.

[dannyboy79]

or you could just do what I suggested and check the channels with test-mpeg2. then if it doesn't record a stream (fole size is 0) that means it's encrypted whether you thought it was or not. That's just the way it goes. You'll then have to tune to a KNOWN CLEAR CHANNEL, and use the firewire_tester with the -R switch to reset the firewire bus.