Closed Captioning Update?

[mets3145]

motion to sticky this post for CC reference for other users.

I believe this matter is 100% solved from when I first started it.


Thanks everybody!

[hemicuda]

well nuts... guess I should have saved a copy of the default registry entries that I changed to "0E" for the DVD recording types. Some were "00" others were "A2" or some such.

[ke6guj]

I took a screen shot of my registry settings so you could set yours back they way they should. I haven't touched mine.

I figured giving you a screen shot would be safer than giving you an unknown registy import


edit: although, I dunno if you still need those set to 0E if you want CC on your PVR-350. But looking at the faq, http://forums.sagetv.com/forums/show...4757#post44757 , it only mentions the CCinDVD registry edits, not the 0E edits, or any of the other edits on the hauppuage page that is linked. I dunno, could the 0E edits be for WinTV capture profiles?

[hemicuda]

thanks, Jack. the section of my registry that has those recording settings is about 2x that many entries just for DVD formats.

[ke6guj]

Looking at my list compared to yours, I'd take a guess and say that Sage probably doesn't use those settings at all. But it would be a WAG at that.
I'm guessing that those are WinTV settings.


OK: I just confirmed it, I think . I looked at my parents box and they don't have any settings at all. Their registry tree has no sub-folders below hcwTVWnd at all. When I built it, I manually installed the drivers and only the drivers, I didn't use the installer disc program to install the drivers and the other hauppuage software.

[morfinx]

When will ATI Theater 550 users get CC options?

[ke6guj]

I think you would need to contact ATI and see if they have plans to support CCinDVD through their drivers. Windows MCE uses a different feature set of the driver to do CC so it may not be that important to ATI to do so. So, users may have to ask for it to get included. And that assumes that if the driver had CCinDVD that Sage would use it the same way it uses it in the Hauppauge drivers.

[Wheemer]

Ultimately it is a moral responsibility for sage to have cc available.

It's got nothing to do with the drivers really, as you pointed out MCE does cc with any card. Because microsoft owned up and accepted responsibility...

Maybe we'll see universal cc in sage one day, not soon enough though.

[ke6guj]

Originally Posted by Wheemer

It's got nothing to do with the drivers really, as you pointed out MCE does cc with any card. Because microsoft owned up and accepted responsibility...

Actually I think it has everything to do with the drivers, and how the driver features are used. AFAIK, Microsoft, being the 800 pound gorrilla, was basically able to write the driver featureset they needed for MCE and were able to go to the manufacturers and say that if you want to write a driver for MCE then it must do X,Y, and Z.. Every card usable in MCE has the microsoft CC feature. Sage, on the other hand, uses a different way to get CC, the CCinDVD feature. It would be nce to be able to find out why Sage uses such a driver limited way of doing CC.

If I understand correctly, part of the reason is that MCE doesn't put the CC in the MPEG file the way that Sage does, but saves in in the MS-DRM wrapper that goes around the MPEG file. Maybe Sage could something similar and dump the CC to an .smi or .srt file instead of imbedding into the MPEG file, because once you have Sage convert the file to a smaller format, you just lost your CC.


Universal CC would be nice. With those new drivers for the PVR-150/500, I just got CC back onto my TV after 2 years of not having it so I am happy right now. Now to figure out how to get it to work off my firewired STB.

[morfinx]

So if MCE can do CC, theoretically Sage should be able to do CC using the same method?

[dvd_maniac]

What about CC and the USB2 devices?

[ke6guj]

Originally Posted by dvd_maniac

What about CC and the USB2 devices?

I checked the latest drivers from SHS's forum and read the release notes for the latest USB2 driver. I didn't see anything mentioned regarding CCin DVD support like it showed in the PVR-150/500 release notes.

Fire off an email to Hauppuage and see if they have any new info on the subject.

[Mysticeti]

...but where does one get the "24205" drivers?

Thanks.
(PVR-500 owner)

[ke6guj]

Originally Posted by Mysticeti

...but where does one get the "24205" drivers?

Thanks.
(PVR-500 owner)

I got the 24205 drivers here, http://www.jtdsoftware.com/LNA_Tray_App_Install.zip . It was a zip file hauppauge sent to some people to try to fix the Samsung tuner issues.

edit: I just updated the driver manually, I didn't use the driver installer in the zip. There are also newer drivers in http://www.shspvr.com/smf/index.php?topic=10479.0 or http://www.shspvr.com/smf/index.php?topic=10505.0 . I have not tried the version in there, 24227, which looks to only fix and FM audio issue, which we don't use in Sage.

[SHS]

ATI Theater 550 in order to get CC it has be mux in to MPEG file which SageTV dosen't do.
For SageTV to work with CC
Example for enbeded CC.
mmc/python2_encoding/MyDVDcc=videobitrate=4500000|width=720|height=480|audiobitrate=224|vbr=1|peakvideobitrate=6000000|outputstreamtype=11
You must specify the parameters "outputstreamtype=10" which is DVD compliant stream with enbeded CC
As for I know the USB2 29xxx dosen't support enbeded CC but newer model 24xxx may.
WinTV capture profiles should be 0a which also = 10 the 0e = 14 that is for what is as know DVD MCE Steam which used be know as DVD Special Steam

[ke6guj]

Originally Posted by SHS

ATI Theater 550 in order to get CC it has be mux in to MPEG file which SageTV dosen't do.
For SageTV to work with CC
Example for enbeded CC.
mmc/python2_encoding/MyDVDcc=videobitrate=4500000|width=720|height=480|audiobitrate=224|vbr=1|peakvideobitrate=6000000|outputstreamtype=11
You must specify the parameters "outputstreamtype=10" which is DVD compliant stream with enbeded CC

Actually SHS, I didn't even need to set up any encoding parameters at all in Sage for CC to work. The default (hidden from sage.properties) settings in Sage already worked for CC. I tried some of the DVD ones and even the SVCD one worked, I think. The only one I didn't see work out of the box was the VCD setting.

[feilerd]

Has anyone seen anything like this:

I set up a new server and installed a PVR-150. Closed captioning worked fine. I then installed two PVR-250s (and their drivers) and added the CCinDVD registry keys for them (using the Hauppauge Tweaker application which I'd originally used to set them up on my previous server). Now two of my tuners (#1 and #3) encode CC and #2 (presumably a 250, although I don't know for sure how they get numbered) doesn't.

The registry settings for the two 250s appear identical, and as I said, CC worked on the 150 when it was the only encoder card.

All cards are encoding DVD Long Play.

???



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0025]
"DevLoader"="*ntkern"
"NTMPDriver"="hcwPVRP2.sys"
"PageOutWhenUnopened"=hex:00
"DontSuspendIfStreamsAreRunning"=hex:01
"FriendlyName"="Hauppauge WinTV-PVR PCI II (Encoder-16)"
"InfPath"="oem12.inf"
"InfSection"="p2.Dev16"
"InfSectionExt"=".NT"
"ProviderName"="Hauppauge"
"DriverDateData"=hex:00,80,e2,3f,bf,b8,c5,01
"DriverDate"="9-14-2005"
"DriverVersion"="1.18.21.23257"
"MatchingDeviceId"="pci\\ven_4444&dev_0016&subsys_48010070"
"DriverDesc"="Hauppauge WinTV-PVR PCI II (Encoder-16)"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0025\Driver]
"SubDeviceID"=dword:00070448
"DisableEventNotification"=dword:00000001
"EnableVIMProtection"=dword:00000001
"StopCaptureBeforeChannelChange"=dword:00000000
"HcwSerialNumber"=dword:0078464e
"HcwDecoderPNP"=dword:00000013
"HcwDecoderUsed"=dword:00000002
"InsertCCinDVD"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0026]
"DevLoader"="*ntkern"
"NTMPDriver"="hcwPVRP2.sys"
"PageOutWhenUnopened"=hex:00
"DontSuspendIfStreamsAreRunning"=hex:01
"FriendlyName"="Hauppauge WinTV-PVR PCI II (Encoder-16)"
"InfPath"="oem12.inf"
"InfSection"="p2.Dev16"
"InfSectionExt"=".NT"
"ProviderName"="Hauppauge"
"DriverDateData"=hex:00,80,e2,3f,bf,b8,c5,01
"DriverDate"="9-14-2005"
"DriverVersion"="1.18.21.23257"
"MatchingDeviceId"="pci\\ven_4444&dev_0016&subsys_48010070"
"DriverDesc"="Hauppauge WinTV-PVR PCI II (Encoder-16)"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0026\Driver]
"SubDeviceID"=dword:00070448
"DisableEventNotification"=dword:00000001
"EnableVIMProtection"=dword:00000001
"StopCaptureBeforeChannelChange"=dword:00000000
"HcwSerialNumber"=dword:007845e5
"HcwDecoderPNP"=dword:00000013
"HcwDecoderUsed"=dword:00000002
"InsertCCinDVD"=dword:00000001

[ke6guj]

Well, to test to figure out which tuners are actually which, you could pull your input signal from one tuner at a time and see which tuner# records static. I'd also try disabling/pulling individual tuners and see if you can figure it out that way.

Perhaps pull the 150 and see if both 250s record in CC. Then, pull the 250s and see if the 150 still does CC. Then pop 1 or both 250s in and see if all 3 get CC. If you have all the drivers and regedits, then its gonna be trial and error to figure out the problem.

[feilerd]

OK, so I went into "color calibration" for each tuner and pulled cables to identify which was which. The problem is with one of the 250s--which is really strange because they both look identical (at least to me) in the registry.

It's the one w/serial #: 007845E5

I updated to the latest 250 drivers from Hauppauge's site, but no change.

I guess I can bounce this over to Hauppauge--but do you have any thoughts?

Thanks

[ke6guj]

thats weird. I don't have a 250, so no first hand knowledge. If you want to play around with it, I'd see if different combos of cards work, and cards in different PCI slots.