New native recording patch

[gplasky]

It works well. Not jerky but no super smooth. My PowerDVD 8 works smoother. Probably the hardware assist.
(windows 7 64bit)

Gerry

[stanger89]

Hm, I'm getting HA since my HD PVR recordings use about 0% CPU. But the video basically pauses once a second....

[gplasky]

Yes. Same here. What I meant was because PowerDVD 8 does hardware assist and is also directshow it might be smoother than using the MS h.264. Maybe a little tweaking still needs to be done with the Sage components. I'm definitely not seeing a pause. This is on a 780GX mb with embedded HD3300 (ATI).

Gerry

[stanger89]

Originally Posted by gplasky

Yes. Same here. What I meant was because PowerDVD 8 does hardware assist and is also directshow it might be smoother than using the MS h.264.

Not sure what you mean, that was my point, with the MS decoders I appear to be getting full hardware decode in Sage.

[Rico66]

Originally Posted by stanger89

Not sure what you mean, that was my point, with the MS decoders I appear to be getting full hardware decode in Sage.

Yes, the Windows 7 inbox decoder does full hardware acceleration. I don't really see a difference compared to the PDVD 7.3 decoder that I was using previously. Playback is smooth on my x64 machine.

But as mentioned above, rewind/forward is broken for recordings that are in progress.

[donkey]

Originally Posted by jmv

Where can I find the MpegDeMux.log...I searched under the full c: drive and nothing showed up...I thought maybe my debug settings were wrong so I went into the app and turned debugging on, reset the server, and still no file.

thanks,

mv

Turn on native log and MpegDeMux log by creating an empty file MPEGDEMUX_LOG.ENABLE in SageTV folder. check your created file has a hidden .txt extension in a file explorer if it dosen't work.

Qian

[gplasky]

Originally Posted by gplasky

Yes. Same here. What I meant was because PowerDVD 8 does hardware assist and is also directshow it might be smoother than using the MS h.264. Maybe a little tweaking still needs to be done with the Sage components. I'm definitely not seeing a pause. This is on a 780GX mb with embedded HD3300 (ATI).

Gerry

Originally Posted by stanger89

Not sure what you mean, that was my point, with the MS decoders I appear to be getting full hardware decode in Sage.

Sorry for the quick posts. I agree that both decoders are providing hardware assist. I just figured for me PowerDVD was working better because it was a directshow player/decoder where the MS h.264 is providing directshow through backward compatibility on Windows 7.

Gerry

[Taddeusz]

I'll have to double-check which formats when I get home but I am not getting proper color-space conversion in SageTV using Microsoft's codecs. I do when the files are played in WMP but not in SageTV.

I have always_use_dshow_player set to true. And I have the registry option to enable flagging for color-space conversion for EVR.

[Taddeusz]

Ok, just got home, switched drives around, and did some testing. BTW, this is Windows 7 Pro x64.

All files play fine in Windows Media Player with the proper color-space conversion.

In SageTV recorded material from both my HDPVR and HDHR play fine. Blacks are where they're supposed to be. All imported videos, whether they are MPEG2 or H.264, play with improper black levels.

[Comitizer]

OK, so I followed the instructions and installed everything on my client. However, I don't think the Windows 7 codes are actually being used. When I play the H.264 (mkv) files in WMP I use almost NO CPU (cause the built in codecs use hardware acceleration). However, when I play in Sage my CPU usage goes through the roof.

Is there a way for me to test this?

[jmv]

Still having no success generating an MpegDeMux.log. I put the empty file with the name specified into 3 different directories (when putting it in Program Files (x86) / SageTV / SageTV failed to generate the log file, I also put it in the upper level SageTV and the Virtual Store SageTV directories) but still no luck. I run with always show extensions, and can confirm the extension is ENABLE.

I did see something weird...I reviewed the sagetvclient_0.txt file, and it appeared to be using the ffmpeg H.264 decoder
(Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
[InputStreamConsumer@d731c4] stdout:ID_VIDEO_CODEC=ffh264...

I've attached an exerpt from the sagetvclient_0.txt. The other thing I've noticed is that CPU utilization under Win7 media player is ~6% for these files...under sage it runs 22~24 and does have frame drops and the FF/RW seeking issues...

[TommyGonk]

Should the new code work with encrypted channels that use a CAM/CI module ?.

So far it's working fine with BBC HD but I can't get it to tune any encrypted channels. Using DVBViewer on the same FireDTV S2 card it can tune those channels ok.

[donkey]

Originally Posted by jmv

Still having no success generating an MpegDeMux.log. I put the empty file with the name specified into 3 different directories (when putting it in Program Files (x86) / SageTV / SageTV failed to generate the log file, I also put it in the upper level SageTV and the Virtual Store SageTV directories) but still no luck. I run with always show extensions, and can confirm the extension is ENABLE.

I did see something weird...I reviewed the sagetvclient_0.txt file, and it appeared to be using the ffmpeg H.264 decoder
(Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
[InputStreamConsumer@d731c4] stdout:ID_VIDEO_CODEC=ffh264...

I've attached an exerpt from the sagetvclient_0.txt. The other thing I've noticed is that CPU utilization under Win7 media player is ~6% for these files...under sage it runs 22~24 and does have frame drops and the FF/RW seeking issues...

It's why there isn't a mepgdemux.log, SageTV didn't pickup MpegDemuxer.ax.
currently MpegDemuxer.ax supports H.264 in ts, m2ts, ps (sagetv recording) format, not mkv.

Qian

[donkey]

Originally Posted by Rico66

This new splitter seems to have a problem regarding the timeline, when watching recordings that are in progress.
When you play a recording that's not yet finished, it doesn't start at the beginning, but instead starts at the current "live" time. The display of the time bar does not reflect the correct time, since it shows the times that you would expect (start at the beginning not a real time, green/white colouring is wrong). These don't match what is actually played.
The behaviour when skipping forward is also pretty strange, since one skip sends you back to "recording" time and the next skipping brings you back "live".
Once you skip forward enough that you really are at real time according to the time bar everything seems to be OK. Now you can skip backward and forward again as expected (the colour green/white of the bar is now correct as well)

I'm running the latest Sage version (+SageMC) on Win7 x64 (shouldn't matter). I noticed this with a OTA/mpeg2 recording, but will try it on a mpeg4 hdpvr recording as well later...

Could you post sagetv log and MpegDemux.log?
We set up a Win7 x64 computer as a sagetv client, didn't reproduced your timeline problem.

Qian

[jmv]

ok, I converted my mkv to m2ts...still no log file joy...any new ideas?

[donkey]

Originally Posted by jmv

ok, I converted my mkv to m2ts...still no log file joy...any new ideas?

post your client sagetv.log.

Qian

[jmv]

I must have something wrong with my configuration, as I am also not getting that .log file either...the only file I can see that is being generated is sagetvclient_0.txt in my virtual store directory...I've attached that. Just for reference, where should the .log's reside?

I'm really anxious to get this working since their is good news...while the .mkv file runs at 20~28% CPU utilization, the same file transconded to .mt2s runs nicely in the 5~8% range. Is the plan to enable .mkv's to work with this native Demux, or should I start my migration to mt2s? Secondly, are there plans to get VC1 working with Win7 native like .264?

thanks,

mv

[Rico66]

Originally Posted by donkey

Could you post sagetv log and MpegDemux.log?
We set up a Win7 x64 computer as a sagetv client, didn't reproduced your timeline problem.

Qian

Here's the MpegDemux.log of a short recording, where I jumped forward about 6 times, and the timebar was jumping back and forth as described.

[donkey]

Originally Posted by Rico66

Here's the MpegDemux.log of a short recording, where I jumped forward about 6 times, and the timebar was jumping back and forth as described.

try recording in PS format,
change "mmc/encode_digital_tv_as_program_stream=true" in Sage.properties

Qian

[donkey]

Originally Posted by jmv

I must have something wrong with my configuration, as I am also not getting that .log file either...the only file I can see that is being generated is sagetvclient_0.txt in my virtual store directory...I've attached that. Just for reference, where should the .log's reside?

I'm really anxious to get this working since their is good news...while the .mkv file runs at 20~28% CPU utilization, the same file transconded to .mt2s runs nicely in the 5~8% range. Is the plan to enable .mkv's to work with this native Demux, or should I start my migration to mt2s? Secondly, are there plans to get VC1 working with Win7 native like .264?

thanks,

mv

The current MpegDeMux doesn't support mkv, so MSFT's video decoder isn't used. we have plan to get mkv native supported after those code stable and released.

Qian