New native recording patch

[Lahr]

Will this help in xp setup?
Is the MpegDeMux.ax improved or just modified to allow for changes in win7?
If MpegDeMuxer.ax is improved, is it necessary to replace MpegDeMuxer.ax in both WHS and Client for best results?

[jerryt]

Originally Posted by Lahr

Will this help in xp setup?
Is the MpegDeMux.ax improved or just modified to allow for changes in win7?
If MpegDeMuxer.ax is improved, is it necessary to replace MpegDeMuxer.ax in both WHS and Client for best results?

Read post #6

[Lahr]

Originally Posted by donkey

MpeDeMux.ax on Window 7 Client
TSSpliiter.ax DShowCapture.dll DShowPlayer.dll on WHS, if you would like to test.

Qian

Sorry jerryt that post doesn't even come close to answering my questions.
I know where to put them and how to install them, my questions were altogether different but thanks anyway.

[PRKIDD]

I'm running windows 7 (64bit). I'm running the latest Sagetv server software.
I been having problems just installing the software an I came across your documentation. I follow the instructions and then I started SageTV still the same problem. I went into the Sage.properties an notice that the entry I just inserted videoframe/additional_video_filters=Microsoft DTV-DVD Video Decoder
videoframe/h264_video_decoder_filter=Microsoft DTV-DVD Video Decoder

was not in the file. I added the entry once again started SageTv didn't work edit the Sage.properties file again an sure enough the entry are not there.

[gplasky]

Originally Posted by Lahr

Will this help in xp setup?
Is the MpegDeMux.ax improved or just modified to allow for changes in win7?
If MpegDeMuxer.ax is improved, is it necessary to replace MpegDeMuxer.ax in both WHS and Client for best results?

From the first post:

Here is a new native code for the next release, in which many long time problems have been fixed such as audio track issues in DVB stream,format detecting wrong, M2TS format native support..., and windows 7 video decoder supported (H.264).
Give it an run, if any problem, post your logs.

So if you have a long time problem in your xp installation then it may help. MpegDemux is used for the playback. So unless you're playing back on your WHS it goes on your client

Gerry

[Opus4]

Originally Posted by PRKIDD

I went into the Sage.properties an notice that the entry I just inserted ... was not in the file.

See the FAQs for more info:
How do I edit the properties file? The settings don't change when I change them.
and
Where does SageTV store its data files in Windows Vista?

- Andy

[reggie14]

Originally Posted by FlyingDoc

Does anyone have an answer (or suggestion ) about this. I am doing the same thing and getting the same result. I want to save the firewire data as PS because this seems to improve comskip accuracy.

This is why I've been avoiding the patch...

But, is this even a problem? If I install this patch will my firewire recording graph automatically start using the new TSSplitter, or will it keep using the old one? If it just keeps using on the old one, why not just stick with that?

[FlyingDoc]

The splittter file names are different so your capture graph will continue to use the old one unless you explicitly change it. I am experiencing some A/V sync problems and was hoping that using the new splitter to do the TS - PS conversion would improve this. The fact TSSplitter3.0 doesnt work in this mode (ie no file gets produced at all) was something i wasnt expecting.

[korben_dallas]

HD PVR recordings played back on my Win 7 x64 SageTVClient PC, about once every recording roughly about once every 10 or so FFwd's, the whole desktop screen goes black/gray, and then the ATI video card driver reports it recovered from a failure. SageTV Client picks right up where it left off usually without a hitch, but I got this last night.



Had to shut down SageTV Client and restart it. I'm using the Update 10 + files to add to update 10.

[jerryt]

Originally Posted by korben_dallas

HD PVR recordings played back on my Win 7 x64 SageTVClient PC, about once every recording roughly about once every 10 or so FFwd's, the whole desktop screen goes black/gray, and then the ATI video card driver reports it recovered from a failure. SageTV Client picks right up where it left off usually without a hitch, but I got this last night.

Had to shut down SageTV Client and restart it. I'm using the Update 10 + files to add to update 10.

I had this on a Win 7 32 bit machine and fixed it with the lastest ATI drivers (9.13?)

[SHS]

Originally Posted by jerryt

I had this on a Win 7 32 bit machine and fixed it with the lastest ATI drivers (9.13?)

There no 9.13 it move to 10.1 if talk about latest beta

[koan00]

I am not sure if this is related, but I am having a lot of trouble watching "LiveTV" when the source is MPG2 (HDHomeRun). Usually setting the show to record and then watching the recording works. However, often when trying to tune a QAM station from the Guide with the HDHR, I see just a frame or two of the show, and then playback stops. Sometimes I will notice a weird garbled long negative number for the start of the time line. After the failure, if I choose to restart from the guide, sometimes I can get playback to start properly. Other times I can keep attempting to start watching over and over again, with successive failures.

I am using the latest update 10 and updated 2 files, and I see a lot of stuff like this in the native.log, I figured it maybe related?:

01/15/2010 21:44:14 PS Parser is created  version 2.0.1  ZQ.
01/15/2010 21:44:14 **** SageTV Recording Data ver. 5 ****
01/15/2010 21:44:14      ES:0:0 esid:0xbd80 audio    AC3  MPEG2 eng   
01/15/2010 21:44:14      AV:0:0 audio    AC3  
01/15/2010 21:44:14      ES:0:1 esid:0xe000 video    MPGV MPEG2    
01/15/2010 21:44:14      AV:0:1 video    MPGV 
01/15/2010 21:44:14 SageTV recording: video:1 auido:1 main video:0 main auido:0
01/15/2010 21:44:14 Stream Ready pos:2768
01/15/2010 21:44:14 ****** PARSER STATUS: STREAM READY (slot:0) ******
01/15/2010 21:44:14 INPUT-AVINF|MPEG2-PS;br=1575500;[bf=vid;f=MPEG2-Video;fps=29.970030;fpsn=30000;fpsd=1001;ar=1.777778;arn=16;ard=9;w=1920;h=1080;lace=1;main=yes;tag=e0;index=0;];[bf=aud;f=AC3;sr=48000;ch=6;br=48000;main=yes;lan=eng;tag=bd-80010000;index=1;];
01/15/2010 21:44:14 **** Find AVINF(pos:2768) ****
01/15/2010 21:44:14 Disable track 1, it's not connected 
01/15/2010 21:44:14 Disable track 0, it's not connected 
01/15/2010 21:44:14 **** SageTV Recording Data ver. 5 ****
01/15/2010 21:44:14 **** SageTV Recording Data ver. 5 ****
01/15/2010 21:44:14 **** SageTV Recording Data ver. 5 ****
01/15/2010 21:44:14 ERROR: No MEPG start code found in a block (49 bytes), data is dropped
01/15/2010 21:47:37 **** SageTV Recording Data ver. 5 ****
01/15/2010 21:47:37 ERROR: No MEPG start code found in a block (2048 bytes), data is dropped
01/15/2010 21:47:45 **** SageTV Recording Data ver. 5 ****
01/15/2010 21:47:45 ERROR: No MEPG start code found in a block (24 bytes), data is dropped
01/15/2010 21:47:45 **** SageTV Recording Data ver. 5 ****

[Taddeusz]

Lately I've gone back to H.264 encoding my DVD rips. I've noticed that for some reason my client isn't displaying the correct anamorphic aspect ratio. These videos play fine in Windows Media Player. They look incorrect from SageTV though. I'm using MeGUI to encode them to an MKV file. Any ideas?

[grbsaaber]

I find all my QAM channels for FIOS, but when I go to play them either through windows 7 or the hd200 I get no signal. some work some don't, seems the sd ones work, hd don't. I also noticed the mapping is wrong. 4-1 is 4-2 and 4-2 is correct. There are other too wher3 channel 5-x referrs to channel 13-1.

What do I need to do to troubleshoot this.

windows 7 machine.

Let me know and I will walk through what needs to be done and post the fix.

[grbsaaber]

Well, replaced the directshowcapture.ax filter with the original keeping everything else from the update10 and rescanned.

I now have QAM working. Will test more, looks like the channel thing was a fluke maybe.

but the diectshowcapture i think may have fixed my issues.

[babgvant]

Found a problem where Sage will get stuck importing M2TS files with the patch applied.

[farfromuman]

I can confirm the same on some M2TS files, the CPU gets pegged and it sits there for hours but nothing happens, also time lines are buggy in padded recordings that are not yet finished.

Originally Posted by babgvant

Found a problem where Sage will get stuck importing M2TS files with the patch applied.

[jerryt]

Originally Posted by Straykat

Something odd is going on with M2TS import scans and it has something to do with Update 10 DShowplayer.dll

Problem: new M2TS files (ripped BD backups) are taking an impossible amount of time to scan and import. Were talking about many hours for 1 M2TS file.

Symptom: Scanning for new files hangs on the first new M2TS file is finds, locks both CPU cores at ~50% (Core 2 duo running @ 3.12), takes up 50% of my GB LAN (files are on a NAS), and doesn't stop for hours. Native.log shows that it starts parsing the file and keeps going without reported error.

Solution: I narrowed it down to DShowplayer.dll. Reverting to the last known .DLL from July or so, allows the M2TS files to be scanned, imported, and displayed within 5 seconds.

When I want to put new M2TS files on the storage:
1) I revert to the old Dshowplayer.
2) Start Sage and do a media scan.
3) Check to see that the movies are showing
4) Stop sage
5) Change the DShowplayer to the newer, Update 10 version
6) Restart Sage

This post has been very helpful, I would not have figured this one out myself.

Thanks

[guho]

I applied update10 to my sagetv and it solves all my playback problems. Channel/changes are way slower now as playback takes so much longer to get going. This was ok on vista32. Now I moved to w7 x64 and found that update10 causes sagetv to crash. According to the hs*.log, it is due to dshowcapture.dll which does an illegal memory access. Please fix and test using w7 x64. In the meantime I reverted the dlls and it is stable again. Thanks.

[Ender]

Originally Posted by guho

I applied update10 to my sagetv and it solves all my playback problems. Channel/changes are way slower now as playback takes so much longer to get going. This was ok on vista32. Now I moved to w7 x64 and found that update10 causes sagetv to crash. According to the hs*.log, it is due to dshowcapture.dll which does an illegal memory access. Please fix and test using w7 x64. In the meantime I reverted the dlls and it is stable again. Thanks.

Did you try the updated files for update 10 posted here:
http://forums.sagetv.com/forums/show...774#post390774