or Connect
AVS › AVS Forum › HDTV › HDTV Recorders › How to record via IEEE 1394 (Firewire) to Windows XP
New Posts  All Forums:Forum Nav:

How to record via IEEE 1394 (Firewire) to Windows XP - Page 201

post #6001 of 6013
Quote:
Originally Posted by DSperber View Post

Alright you're probably not going to believe this since I am still having a hard time believing it, but contrary to what I'd thought was true it appears 100% possible to run CapDVHS 2003 (v0.3.0.6) on 64-Bit Win7 Pro in order to capture firewire feed from my JVC DT100U.

I know, lots of discussion here has dealt with attempts at firewire recording from Motorola DVR's of various types and firmware versions, and which always insisted that it was only the 32-bit firewire drivers that existed to support firewire connection from the DVR. So I just assumed this would also be true of trying to make PC recordings from my older DVHS (copy-freely) recordings originally made years ago from offloads via firewire from Motorola DCT/DCH DVRs (which never had serious firewire problems as the DCX family did) to my DVHS VCR's. In other words I would have to use CapDVHS with my old 32-bit WinXP system, along with the very old 32-bit firewire drivers for DVHS machines acquired many years when CapDVHS was also downloaded.

Well, today I received the 15-foot 4/6-pin firewire cable from Monoprice that I'd bought so that I could begin transferring my old "So You Think You Can Dance" DVHS tapes to TS->MPG, expecting full well to be forced back to 32-bit WinXP to do that.

You can imagine my surprise when plugging in the new firewire cable and connecting my DT100U to my PC saw what appeared to be 64-bit Win7 Pro seemingly going to the MS Windows Update site to retrieve and install the appropriate drivers for the JVC DVHS VCR. This seemed to be going without a hitch, and sure enough when it was all done the only device that did not get a suitable driver was for the "AV/C tuner" in the VCR:



Seemed ok to me, since I only cared about CapDVHS being able to control the tape deck mechanism, not the tuner. And the drivers to support the rest of the DT100U appeared to get installed successfully!! Hmmm... presumably these were all appropriate 64-bit drivers that just got installed.

So would CapDVHS work in a 64-bit environment, with the 64-bit drivers for the DT100U DVHS tape deck components that had just gotten installed??? Would I actually be able to do this tape->TS transfer from DVHS under 64-bit Win7 Pro, and never actually have to look at WinXP again even for just this very special task???

I then manually pushed PLAY on the VCR to begin playback. And with playback now proceeding I pushed the REC button on CapDVHS (which had already surprised me enough even by just starting up and running seemingly without a complaint). Astonishingly, I saw the time counter moving along normally, exactly as if it were really doing its recording!!

After a few minutes I pushed STOP on CapDVHS, and looked in the \CapDVHS folder with Explorer. Sure enough there lived a new TS file of several hundred megabytes, exactly as expected. I then OPEN'd it, and sure enough those few recorded moments from the DVHS tape now appeared on my PC!!!

So sure enough, it would appear that the automatically downloaded MS-provided 64-bit drivers for firewire access to/from the DT100U seems to be 100% compatible with CapDVHS, all of which seems to work together perfectly on 64-bit Win7 Pro!!!

To say that I am astonished would be an understatement. I really could not be happier, as I now begin the project of transferring all of my copy-freely DVHS tapes to TS with CapDVHS under 64-bit Win7, and then edited TS->MPG with VideoReDo.

Very very exciting. Good news, if you are a DVHS VCR owner.
I hadn't checked this thread for about a year, but this is an amazing find. I'm going to have to give it a try with my JVC DVHS deck, which I made many recordings with such as all the playoff games the last time the Seahawks made it to the Super Bowl. I would love to get that on disk rather than digital tape.

Thanks for the tip!

BTW, I still have one Comcast Motorola DCT3416 box left. The box itself is getting glitchy (probably a struggling hard drive), but firewire capture to W7x86 continues to work fine.
post #6002 of 6013
TN0821, I was hoping you would share with me the specifications of your Windows 8 capture station. Is it a 64 bit or 32 bit system?
What is the firewire chip set? Can you give me a link that contains the latest drivers and instructions? Thanks in advance for any advice that you can share.
Lee
post #6003 of 6013
I have compiled the Microsoft DVHS Sample app from the DirectShow samples library under Visual Studio 2010 for Windows XP SP2 or newer as a 32 bit executable. I have been interested in this app for some a long time and finally got around to installing Visual Studio, the Windows SDK, and DirectX SDK, and spent the time fighting with the build system over include paths and header inclusion order headaches and successfully built this application.

I am planning on moving soon and have all my DVHS decks packed up and in storage, and therefore I dont have any DVHS decks hooked up to my workstation, so when I ran the app, it hit an assert statement since it couldnt find any devices using the MSTape driver. Simple fix, but clearly MS didnt spend a lot of time testing this sample source code.

The GUI is not all that polished, but I worked with the resource editor last night and re-arranged things a bit to make it work better.
It has been several years since I have worked with Visual Studio and 2010 is very different from the last version I used, which was 2003 I think.

Anyhow, I would ask any folks with DVHS decks still attached to their PC's to try out this application and let me know how it works for them.
It should allow you to select a DVHS deck from a list of those connected to the firewire network and use the transport controls to control playback. It should also render the MPEG2 transport stream (un-encrypyed) with only using Microsoft provided decoders to the GUI.

Questions:
1. Which deck are you using and do the transport control work?
2. Is the transport stream rendered on the GUI.
3. If you have multiple DVHS decks, does switching between them work?

What you need are 2 things:
1. Un-encrypted recordings like HDNet titles or something recorded off broadcast or on cable which was not encrypted (ie copy freely).
2. Microsoft AVCTape driver installed and working.

I may go pull one of my DVHS decks out of storage tonight after work.....so I can test this out myself.

I would like to add capture functionality to the app and was trying to build a DirectShow filter graph which would simultaneously render the stream to the GUI and also write the stream to disk. I tried inserting an infinite tee filer between the file source and demux, but it would not connect pins.

Microsoft DVHS Sample Application (32 Bit Debug Build)
DVHSApp.zip 219k .zip file
Edited by qz3fwd - 1/21/14 at 8:31am
post #6004 of 6013
Quote:
Originally Posted by 1992lee View Post

TN0821, I was hoping you would share with me the specifications of your Windows 8 capture station. Is it a 64 bit or 32 bit system?
What is the firewire chip set? Can you give me a link that contains the latest drivers and instructions? Thanks in advance for any advice that you can share.
Lee

The Windows 8 system is x86 (32-bit). Nobody using Windows is performing FireWire captures from cable boxes using x64 (64-bit) Windows. And they won't be anytime in the foreseeable future.

Note: People are capturing from DVHS tape decks on x64 Windows Vista\7\8\8.1\Server 2008\Server 2008 R2\Server 2012\Server 2012 R2, because unlike the cable box driver, which only exists as an x86 driver, the DVHS driver exists as both a x86 and x64 driver and gets auto-installed by Windows when you plug in your DVHS deck.

My Windows 8 capture system is currently dead frown.gif I was using a Sony laptop and had it precariously balanced and wound up knocking it down and breaking the FireWire connection.
The system I'm running FireWire caps on currently is an old Pentium 4 3.2 GHz Northwood system, which doesn't support the NX bit, which means that Windows 8 refuses to install. (The NX bit wasn't introduced until the Pentium 4 Prescott processor). So I'm currently running Windows 7 Home Premium x86 (32-bit) with SP1 on my FireWire capture system. It seems that that particular system will top out running Windows 7 or Windows Server 2008 R2

At some point I'll probably resume using the Sony laptop for FireWire captures...I'll just need to pick up an ExpressCard FireWire card.

When I was using Windows 8 for my FireWire captures, my system was Windows 8 x86.
The FireWire has no driver other than what Windows 8 ships with. The FireWire details are:
Chipset = Texas Instruments 1394 OHCI Compliant Host Controller
Hardware IDs: PCI\VEN_104C&DEV_803A&SUBSYS_9005104D&REV_00

Note: Unlike with Windows 7, you DO NOT switch around the default Windows 8 FireWire driver. With Windows 7 you are required to change to the "legacy" FireWire driver, but this is not needed (and I think impossible) on Windows 8. Windows 8's FireWire support spanks Windows 7 up and down.

My install order on a fresh Windows 8 x86 (32-bit) is as follows:
1. Install Windows 8.1 x86 (32-bit). If you want to try the free Windows 8.1 x86 (32-bit) Enterprise Edition 90-day evaluation, you can download it from Microsoft here. This is a direct download link from Microsoft, so there's no having to create a Microsoft account or anything. Just download the .ISO file and burn it to DVD. The Windows 8.1 eval is pre-activated and is good for 90-days.

[rant] Fact: Anybody that prefers Windows 7 to Windows 8 is delusional. A couple of pinned Taskbar shortcuts and BAM! Windows 7 on super steroids with FireWire support that shames its predecessor. File copies are way faster than Windows 7 and can be paused, Task Manager is amazingly better, and I just plain ignore the Windows Store...I never open those sad one dimensional iPhone wanna-be apps. I mean, I would for sure use them on a tablet (a sad one dimensional PC wannabe), but I'm not subjecting myself to that on a real machine.[/rant]

2. Before plugging in the cable box FireWire, install the cable box driver (You can use my v4 cable box driver install package, which was updated for Windows 8 and Windows 8.1. You may need to use a download manager, as I now see that Google Chrome is flagging it as potential malware. No doubt that's because I'm now including MPEG2Repair, which uses an EXE packager for compression\code obfuscation and that same EXE packer has been used by malware in the distant past (BTW, nice sh*tty malware detection algorithm Google, I thought you clowns only hired smart people; fix it, and while you're at it fix your awful FireWire bugs on your Motorola DCX cable boxes. K, Thx).

3. Connect your cable box FireWire to your PC and run CapDVHS (which is included in my v4 cable box driver install package)

That's it. Everything should work great. And if you need a good easy to use HD editor for removing advertisements, I recommend grabbing a copy of VideoReDo TVSuite. It's crazy easy to use.

-TNO821
Edited by TNO821 - 1/26/14 at 2:17am
post #6005 of 6013
Quote:
Originally Posted by tluxon View Post

I hadn't checked this thread for about a year, but this is an amazing find. I'm going to have to give it a try with my JVC DVHS deck, which I made many recordings with such as all the playoff games the last time the Seahawks made it to the Super Bowl. I would love to get that on disk rather than digital tape.

Thanks for the tip!

BTW, I still have one Comcast Motorola DCT3416 box left. The box itself is getting glitchy (probably a struggling hard drive), but firewire capture to W7x86 continues to work fine.
The DCT3416 is a good unit. I would upgrade that hard drive to 1 TB if I were you.

As for the Windows 7 and 8 support for JVC DVHS decks, yes. Both the x86 (32-bit) and x64 (64-bit) releases of those operating systems come with or can automatically download drivers for them. However, they can not do that for cable boxes. For FireWire capturing from a cable box, you must use the x86 (32-bit) edition of Windows and install the cable box drivers.
post #6006 of 6013
Quote:
Originally Posted by qz3fwd View Post

I have compiled the Microsoft DVHS Sample app from the DirectShow samples library under Visual Studio 2010 for Windows XP SP2 or newer as a 32 bit executable.
.
.
.

Anyhow, I would ask any folks with DVHS decks still attached to their PC's to try out this application and let me know how it works for them.
It should allow you to select a DVHS deck from a list of those connected to the firewire network and use the transport controls to control playback. It should also render the MPEG2 transport stream (un-encrypyed) with only using Microsoft provided decoders to the GUI.

Questions:
1. Which deck are you using and do the transport control work?
2. Is the transport stream rendered on the GUI.
3. If you have multiple DVHS decks, does switching between them work?
I have tried it with a JVC HM-DH30000U but I can't get the transport controls to do anything. They remain grayed-out. It does see the device. It shows up as "Microsoft AV/C Tape Subunit Device". I can click on that and then click the "Select Device" button, but nothing happens. The VTR Controls area remains grayed-out and nothing shows up under the Programs or Streams areas.

Also: Typically the "Microsoft AV/C Tape Subunit Device" entry vanishes after maybe 30 seconds or so, forcing me to close the app and relaunch in order to see it listed again.

I am able to use CapDVHS and capture from this JVC HM-DH30000U. My system is running Windows 7 Home Premium x86 with SP1.

I may try to restore an old XP image to this system and upgrade it to SP2 or SP3 and see if I get better results.

-TNO821
Edited by TNO821 - 1/26/14 at 9:01pm
post #6007 of 6013
OK I restored an XP SP1 image and I can not find the AVC tape driver, so I'm stuck on testing it on XP. On Windows 7, the OS auto detects and downloads the driver, but not on XP.
post #6008 of 6013
The application is built against XP SP3 or newer.
I will pull a DVHS deck out of storage tomorrow night, and also hook up a LG 3410 and RCA AVHDD.

A slightly modified GUI version is attached. (No significant code changes)

DVHSApp.exe.zip 230k .zip file
post #6009 of 6013
Someone mentioned getting this working under Windows Server 2008, what needed to be done? Did you need to use the legacy firewire drivers from Windows 7 32?
post #6010 of 6013
Quote:
Originally Posted by dafoomie View Post

Someone mentioned getting this working under Windows Server 2008, what needed to be done? Did you need to use the legacy firewire drivers from Windows 7 32?

Yes, I had to copy over qedit.dll (a file that doesn't ship with Windows Server 2008 for security reasons) from Windows Vista (and also edit the registry a bit). If you can avoid doing this on Windows Server 2008, I would. My experience is that Windows Server 2008 has even worse FireWire support than Windows 7. One of my FireWire cards (TI chipset) refuses to cooperate with CapDVHS on Server 2008, but that exact same system works beautifully when using Windows 8 or 8.1. Windows 7 and Server 2008 have horrid FireWire support.

The registry I had to add was:


Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{C1F400A0-3F08-11D3-9F0B-006008039E37}]
@="Sample Grabber"

[HKEY_CLASSES_ROOT\CLSID\{C1F400A0-3F08-11D3-9F0B-006008039E37}\InprocServer32]
@="C:\\Windows\\System32\\qedit.dll"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11D0-BD40-00A0C911CE86}\Instance\{C1F400A0-3F08-11D3-9F0B-006008039E37}]
"FriendlyName"="SampleGrabber"
"FilterData"=hex:02,00,00,00,00,00,20,00,02,00,00,00,00,00,00,00,30,70,69,3­3,\ 00,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,30,74,79,33,00,­\ 00,00,00,60,00,00,00,60,00,00,00,31,70,69,33,08,00,00,00,00,00,00,00,01,00,­\ 00,00,00,00,00,00,00,00,00,00,30,74,79,33,00,00,00,00,60,00,00,00,60,00,00,­\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"CLSID"="{C1F400A0-3F08-11D3-9F0B-006008039E37}"


Even with the above, I have one FireWire card that refused to play ball on Windows Server 2008, but worked great with other versions of 32-bit Windows.

The following is from my FireWire .msi driver installation package. It explains the qedit.dll situation on Windows Server 2008:




Info About a Problem with CapDVHS on Windows Server 2008
C:\Windows\System32\qedit.dll is not included with Windows Server 2008. This file is required by CapDVHS. In order to use CapDVHS, you must copy qedit.dll from a 32-bit copy of Windows XP, 2003, or Vista (but NOT from Windows 7, as it is not compatible).

If you insert a Windows XP CD, the following command line can be used to extract the qedit.dll file to your System32 folder:

extrac32.exe "Full path to\qedit.dl_" "%SystemRoot%\System32\qedit.dll"

So, if your CD\DVD\BD drive is E:\, you could use this command line to copy qedit.dll:
extrac32.exe "E:\I386\QEDIT.DL_" "%SystemRoot%\System32\qedit.dll"

(The extrac32.exe file comes with Windows Server 2008 and is used to extract the qedit.dll file from the QEDIT.DL_ file, which is compressed.)

*Note: I have tested this using qedit.dll from Windows XP with SP3 and Windows Vista (no service pack, but all critical and important patches applied). I have not tested this using qedit.dll from Windows Server 2003, but I would truly be shocked if it didn't work. I have also tested it with qedit.dll from Windows 7 (no service pack, but all critical and important patches applied) and it DOES NOT WORK. Apparently there are differences with Windows 7's qedit.dll that render it incompatible. I suspect that I could do some research and create another .reg file that would get it to work, but I'm not going to. Sorry. Use XP's or Vista's. (and, just to be clear, Windows 7 has no problem running CapDVHS; it's just that you can't transplant it's qedit.dll over to Windows Server 2008 and get CapDVHS to work).

In addition to copying qedit.dll, you must register qedit.dll by running the Qedit_Registration.reg file located in the CapDVHS folder.
More information can be found here:

http://groups.google.com/group/microsoft.public.win32.programmer.directx.video/browse_thread/thread/2f508e5944d2111e?pli=1


If you read the thread (and other similar threads), it seems that Microsoft made the decision to remove qedit.dll because they felt there was too much crap in there that was insecure and/or deprecated. I speculate that Microsoft made a lot of changes to qedit.dll for Windows 7 in order to shore up security. It's likely that I would need to run some analysis tools and build a different .reg file in order to get Windows 7's copy of qedit.dll to satisfy CapDVHS on Windows Server 2008.

Anyways, have fun.

-TNO821
Edited by TNO821 - 3/6/14 at 4:04am
post #6011 of 6013
I had done all that but CapDVHS would still throw the screengrabber error, and VLC wouldn't work either. I gave up and installed Vista, which won't recognize my firewire card. Ugh.

Windows 8 works beautifully though. Zero problems getting everything working.
Edited by dafoomie - 3/6/14 at 10:25am
post #6012 of 6013
Dear All,
My old DCT-6416 died today and Comcast replaced it with the DCX-3500. I manged to get the inf file from here and got Win7 to see the STB. I can use the Hauppauge Colossus to see the tv, but I can not for the life of me change channels via firewire. I tried the firestb channel arguments to no avail. it seems that the DCX-3500 can recognize some of the signal for the channel change, but it seems to be all gabbled up. Anyone have luck changing channels? Or any good tips? I am about to trash this thing and ask comcast for an older box.

Thanks.
Elviso
post #6013 of 6013
This is about the only place on AVS(and the internet) where there is any active discussion at all about DVHS. This thread was quite valuable to me a few years back, I was able to use the CapDVHS utility to capture stuff off my Comcast DCT3416 DVR and things that I taped to my Mits 1100 DVHS VCR.

Anyways, I'm getting rid of a lot of things due to a move, and would love to pass along my Mits 1100 unit to anyone who could benefit from using it. It still works great and looks new. I also have a JVC 30k that doesn't record or play any tapes, but was used simply as a converter from the firewire outputted by the Mits to regular component video/optical DD5.1, which can then be plugged into an HD display device. I have remotes and documentation/manuals for both, as well as a few DVHS tapes too(that were used with the Mits). PM me if you are interested or want any more details.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: HDTV Recorders
AVS › AVS Forum › HDTV › HDTV Recorders › How to record via IEEE 1394 (Firewire) to Windows XP