Using the Wacom Bamboo Tablet with ArtWeaver

On Windows7 there are multiple Control Panel applets and settings for tablets.

The Wacom Bamboo tablet is a typical old school tablet with a battery "less" pen usually called a "Stylus" today.

Using a tablet for an Input device to Windows means first; is it treated as a pen or as a mouse, then does it have "touch" recognition turned on or off so you can use your fingers or hands on the drawing surface to influence the onscreen Drawing cursor. 

Usually you want to turn off "touch" so that only the pen is recognized and turn off the "treat as mouse option" so it is treated as a "pen" on a tablet.

So first open the Control Panel.

NOTE: If the Wacom Bamboo Tablet is not plugged in and added to the device tree first! Then the Windows Control Panel [ Pen and Touch ] applet (WILL NOT APPEAR!) in the Control Panel.

Then open the [Pen and Touch] applet.

Two tabs: [Pen Options] [Flicks]


[Pen Options]

Pen Action

Single-tap > Single-click

Double-tab > Double-click

Press and hold > Right-click

Start Tablet PC Input Panel > None

Pen buttons

[_] "uncheck" Use the pen button as a right-click equivalent

[_] "uncheck" Use the top of the pen to erase ink (where available)



[_] "uncheck" Use flicks to perform common actions quickly and easily

[_] "uncheck" Display flicks icon in the notification area

Mostly - turn it all off, the way windows handles and "over powers" the tablet behavior will interfere and make using the tablet "harder" than turning it all off.

You can still use a mouse and keyboard to do all the things your already used to using the mouse and keyboard and just use the drawing tablet for .. you know.. ("drawing").

"STILL" within the Control Panel, if you have a Wacom Bamboo Tablet driver installed, there should be a separate [Wacom Preferences] applet.

This is just as important and layers on additional controls over the specifics of this tablet, the generic [pen and toch] applet knows nothing about.

Five tabs: [Tablet] [Pen][Touch Options][Touch Functions][Pop-up Menu]

Mostly > go to the [Pen] tab, Tracking [x] Pen mode

Click on [Mapping...]

Single Most Important Setting:

[_] "Uncheck"  Use Windows Ink

Windows Ink is a controversial, "Microsoft over Mind Matter"  or "Microsoft over Common Sense" setting that turns people off on any tablet inputs for windows in the millions.

Microsoft "retro-actively" tried to wrest control over tablet drivers away from users and manufacturers and defaulted this setting on in tablets and in windows, and in Win10 screwed everything up.

Adobe photoshop tried to make peace.. and Microsoft said "There can be NO Peace".. and its just broken all to pieces across many version of windows and will probably never be resolved.

Turn the setting off.. walk away.

And if you want pressure sensitivity in Adobe products, manually create a text file .ini for Adobe and tell it to turn pressure sensitivity on.


Pen buttons:

TOP Keystroke: Ctrl+z "Undo"

BOTTOM Keystroke: Ctrl+y "Redo"

ArtWeaver .. nothing special to do.

Felt tip brushes and 2B pencils are mostly what your gonna be used to.

ArtWeaver will treat the Eraser end of the pen the same as the Shrp or "nub" end and draw rather than erase. I don't know how to correct that.

ArtWeaver Free and difference from ArtWeaver Pro or "licensed" ArtWeaver.. whcih has more panels and menus and documents often refer to features not available in the "Free" edition which cna led to confusion.


Phased Array Launch Systems to Low Orbit

 This might be something unique to Earth Orbit since it makes use of the heavy and thick atmosphere to transfer kinetic energy. But one way of doing away with all of the launch vehicle might be to focus a kinetic wave front from a bowl shaped area, like the Arecibo mountain range, on to a platform or lift pallet suspended in the center of the bowl.. or just above the floor sufficient to over come dampening effect against the walls of the bowl.

Simply its like focusing many Air Bazookas on to a pallet and transferring kinetic energy into the structure at a resonant frequency of that structure and back out again accelerating the air molecules against the base and using them like impulsive rocket fuel kicking the pallet higher and higher into the sky.

The vacuum left is quickly replenished with inwardly rushing air from the sides and the whole thing would appear and operate like an aero spike engine with no moving parts.

A variant might be a microwave, or solar energy collection system that boils steam in order to expand a working fluid to drive the pallet higher.


Using Cyberlink PowerDirector for Video Capture from within SONY Vegas Pro 11

CyberLink is and was known for making a very good PowerDVD and Goto DVD set of DVD viewer and burner programs.

But they also released over 20 different versions of a NonLinear Editor called PowerDirector.

PowerDirector evolved quite logically from one strength to the next taking advantage of improvements in video capture hardware and processors and gpu processors in a straight line up to the present day on Windows 10. Its an unbroken chain.

They even have a version of PowerDirector for Mac, which I am only vaguely aware of.

The key module or "tab" of interest with PowerDirector is the Video Capture tab, which does a great job with Analog video as well as various Hardware assist compressed video formats (aka DV, HDV, MPEG1/2/3/4).

The SONY Vegas Non Linear Editor is known for robustness, training materials and ease of use far more than Cyberlink products.

It is possible to configure SONY Vegas to "outsource" the video capture of DV materials from its own built-in or bundled standalone VidCap6.exe program to an external program when Capture is started from within the SONY Vegas menus. - 

This is done from the [Options > Preferences... > Video "tab"] 

Mid-way down check the box [X] Use external video capture application:

C:\Program Files\Cyberlink\PowerDirector20\PDR.exe

When initiating the Capture process from the SONY Vegas [File > Video capture...] menu



The dialog box will note that the capturing of DV video will use an external tool and that it can be reconfigured to point at other programs, which the trick used here.. to start PowerDirector instead and perform the Analog capture first.. then the resulting video capture product file can be Imported into SONY Vegas using the Explorer Undertab in the Media Panel.

In theory VirtualDub, VLC, OBS or other custom video capture tools could be use with SONY Vegas to acquire Analog video content and Import it through the Explorer Undertab.

Its also interesting to "know" that AverMedia went a different route and wrote a Capture "Plugin" for SONY Vegas that once installed lived in the "Media Generator" Undertab plugins. Dragging and dropping the plugin on a Timeline initiated the SDK developed plugin which took that as a signal from the SONY Vegas "operating system" to display its capture window and search for AverMedia Video Capture products it knew how to use to capture video. The end result when the video was captured was a segment on the Timeline more in line with an intuitive workflow.. but functionally identical to spawning an external capture program.. which SONY Vegas itself does with VidCap60.exe.. so arguably using PowerDirector is slightly more like the normal workflow.

Video Capture - with MPC-HC

MPC-HC ended active development in 2017, but before it did they added in much of the VLC and VirtualDub video capture features in 64 bit.

This is an example of using the Raw UVYV (aka YUV) 422 video capture capability of the Dell / Lumanate Angel II TV Tuner card from an S-Video source.

It came to my attention while looking at the File drop down menu that it looked very familar (for VLC) with an option to Open a [File Device...] from there it was a matter of back tracking where the menu for configuring the Video Capture Device was located. View > Options > Capture

Another Important location is the [ Play > Filters > MPEG Device, Crossbar, TVAudio and TVTuner]

Directshow panels for setting up further details for the card through its device drivers.

For some reason with this particular capture card it can get lost and permenantly configured to not address the UVYV input stream. For one thing the YUV 422 capture capability of this device on a native Windows 7 64 bit device driver that is Windows Media Center compliant is not well documented and only specified on the Lumanate website for one channel, of the dual channel card. 

Normally Windows Media Center only uses the Time Base Correction and MPEG2 hardware compression of the card. Its likely MPC-HC gets attached to the MPEG2 output pins of of the Directshow device driver filter modules by default or merit and never search any further. The Play Filter menus "might" offer help in this area.. but I've never been able to make them work after spending maybe five minutes wrestling with it.

The hackery shortcut way to reset this is to open regEdit and wipe a key to return it to a default profile and then try again. It will offer up UYVY as an output choice and start working again.

Simply delete the keys below the node "Capture" and close regEdit and it will rebuild them upon discovery of the card.

Its not a smooth way to capture with this card, there are a number of unpolished "issues" but it may be smoother with other capture devices.

Notably the versions of VLC that have similar feature menus are a bit harder to configure, even ffshow commandline methods. And people often think VLC is based on Directshow when it is most certainly "not. It reuses a libav codec library sourced from Linux.. so there is no Graph to study.

Since this exposes many Directshow filters is seems like it borrows the menu interfaces but more closely aligns with VirtualDub and Directshow filter models instead.. especially the DMO filters.

I've not tested it with many other video capture devices, but it could prove a very interesting alternative to both VLC and VirtualDub for video capture.


Lumanate and PowerDirector 20.0 and 10.0

It seems the Cyberlink (from Taiwan) PowerDirector program can capture with some of the Lumanate sourced video capture devices.

So far I've found the Angel I and II and Wave USB video capture devices do capture and with sound.

The performance and ease of use for Capture seems much better than the software that was called out as compatible.

Cyberlink removed or hid the Capture feature in later versions of their PowerDirector program, but its prominently displayed in earlier editions. Not all capture devices work with PowerDirector.. but a lot more than I expected.

Since PD spans from Windows XP to Windows 7 and up to Windows 10, there is a chance that it would be a very good long term source of at least an MPEG2/4 capture program. And it does seem to capture AVI with some devices I have tried. It is not perfect.. but its really nice to find an alternative.

I am not sure how it compares to Adobe Premiere or FinalCut Pro but compatibility with a number of brands of capture cards is desirable.

Compared to VirtualDub and OBS it fills a niche between bare bones and something targeted for streaming.

Optimized Video Capture with ATI USB2.0N TV Wonder


This works best on Windows XP, the device driver available is 32 bit only. There is no 64 bit device driver available.

Windows XP (will not!) enable the Audio subsystem for a USB Audio device unless you have a Sound Card installed.. even if you don't use that Sound Card. It has something to do with not loading the Windows Mixer service.

The Effect is being able to capture Video but with no Audio. That is you can capture video, but there will be no audio stream.

VirtualDub "seems" to be able to capture video and audio even if there is no Sound Card.. but its a heavy work around. The only test I made was to turn on the Volume Meter and see that it could detect audio input from the video capture device.

For PowerDirector 10, I had to actually install a Sound Card (Santa Cruz) and the Windows Mixer service was installed and started. Then in PowerDirector, I had to (and could) select the Video capture device as the Sound source. Its a strange sort of dependency.. but it works. Then I could capture 4:2:2 AVI or 4:2:0 "Software" MPEG2 video with sound.

Per usual playback on Windows 7 in the Windows Media Player required changing the file extension from the default .mpg to mpv2, then the video would playback in Windows Media Player, or in the Windows Explorer Preview Pane.. which made surfing videos without loading up a heavy playback viewer far easier. Trying to play the default .mpg file produces an error that the file type is not supported. I think it looks for the four CCCC inside the file to figure out the contents, or looks at the file extension for a hint as to the contents. And it defaults to not trying for plain .mpg files.. at least the ones produced by PowerDirector.. and many other capture software.

The ATI USB2.0N TV Wonder device produced good capture video.. but is Very sensitive to the quality of the external Power Brick used to provide power. If the Power Brick is getting old, banged about or is in anyway damaged. The Video captured can have a series of Diagonal lines seemingly ghosted or overlayed "Superimposed?" upon the overall image. They produce alternating lines of dark and light over the underlying image. -- This can be cured completely by switching to a new or "known to be fresh or good" Power Brick. The problem goes completely away.

I used to wonder if this was random interference or bad cables.. but it was simply a bad or failing power supply. These power supplies, even the wall adapters.. have capacitors in them that dry out and go bad.. before they completely fail.. or make the video capture device fail.. they begin producing low frequency interference probably through the shared ground connection with the video capture board in the device. There isn't really a practical way of shielding from the interference since it is a shared ground.. a filter of some sort might work.. but its an indicator the Power Brick is nearing its end of life.. and could further damage the video capture device anyway.. its best to simply get a new one.

Since most of the ATI USB2.0N TV Wonder video capture devices are over ten years old.. it makes sense that most of the Power Bricks are near end of life anyway and will be introducing interference to the video capture image.

The Power Bricks are generic enough and available from places like Digikey under the Phong brand name.

I have seen similar things with PCI video capture cards and now suspect the Electrolytic caps surface mounted to the board. They are intended to filter out low frequency noise.. but when they dry out they stop doing that and permit more low frequency noise to invade the video inputs and super impose upon the video capture raster.

Since most of the NTSC signal is based upon or synchronized with the 60 Hz line frequency (a low frequency source of interference) it makes sense that the inputs are not as well protected after the capacitors begin to fail.


GPD P2 Max - Updating the Windows 7 graphics device driver

 The GPD P2 Max is a hand held (Ultra) PC that weights around 600 grams. It comes preinstalled with Windows 10 and can run Windows 8.1 but really shines when running Windows 7.

Its not advertised as having support for installing or running Windows 7 because the underlying mainboard of the platform is beyond that which Intel and Microsoft agreed to as the cutoff point for installing Windows 7 on new hardware.

It appears however this is simply an arbitrary cutoff as Windows 7 can be installed and runs perfectly fine on the GPD P2 Max.

The BIOS of the GPD P2 Max does not have a Legacy CSM BIOS extensions for supporting the INT10 interrupt call which some of the installers and post install support systems depend on.

 This has led to many people trying and eventually giving up installing Windows 7 on platforms without the CSM support.

 Most BIOS today are not really 16 bit BIOS, but rather UEFI Firmware pre-boot operating systems. As such a small program or shim can be written and loaded into memory before the User operating system boots in order to provide features like an INT10 BIOS call routine.

The consumer program called Flashboot Pro provides such a program and offers it during the creation of a USB boot media thumb drive for installing Windows 7. In addition it offers to inject generic copies of NVMe SSD and USB3.0 device drivers to assist with boot hardware that depends upon those devices since those technologies did not exist when the original Windows 7 installation media was mastered.

After booting from the thumb drive (which requires a keyboard combo of FN+DEL to get into UEFI bios and selecting the USB boot media as preferred) . The Windows 7 installation proceeds as normal.

After first boot and user setup.

Several orange safety cones in the device driver manager alert the user to missing device driver support for some of the  hardware attached to the mainboard of the GPD P2 Max. The physical keyboard also doesn't seem to work, so I used the onscreen keyboard to complete setup.

Most driver issues can be resolved by downloading and running the Internet enabled Snappy Driver Installer application. Its advisable to take things slow and repeatedly backup using a full system imaging tool like Macrium Reflect and a bootable large USB thumb drive to capture and deploy backup images.

Device driver hunting is full of unfortunate events that often lead to unrecoverable BSoD messages.

Its faster to restore from a Macrium image backup to a working condition than to repeat the Windows 7 installation procedure.

The most important device driver to replace or update is the windows standard video driver. By default the Basic device driver runs in the maximum pixel resolution of the LCD display possible and this can be very hard to navigate.

Windows Update and Snappy Driver Installer will Not be able to deliver a working Intel HD device driver for the GPU built into the Mobile processor.

Rather you need an Intel HD device driver of a particular vintage which supports both Windows 7 and Windows 10 installs. Many of these have been removed from the web by Intel. Third party sources still abound.

The INF file for the graphics folder needs to be modified after downloading it so that the device ID when atttached ot the PCI bus matches the device driver to install in the INF file.

This works:

%iKBLULTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_591C

 Its rather confusing if you look at the problem straight on.

The literature says this CPU should have an Intel HD 615 GT2 GPU. However that device driver does not work.

What does work is the device driver for an Intel UHD 620 GT2, but once all the Intel support tools are installed they report the GPU as an Intel HD 630 GT2

 Basically.. ignore the confusion and declare victory and move on.

The device driver is fully functional and video playback is superb and quite reliable.

If I had to guess I would think the confusion arose because they released an enhanced version of the Mobile CPU and partnered it with a later more capable GPU and didn't bother updating or creating a specific device driver for Windows 7. Instead they used a later GPU which was already partnered with older CPUs which already had working Windows 7 device drivers. So effectively it has an older higher performance GPU for which there is a Windows 7 device driver.

This CPU was the first 14 nm process (smaller) die which could accomodate the larger older higher performance GPU.. so the result was a win-win for the customer.

 Effectively.. I "guess" they preleased what they thought would be accurate information at the time, and changed the die design during production, once they found they had the capability.

Windows 7 Aero is fully functional, DirectX11 is available. The Windows Experience Rating is 6.8 out of 7.9 possible exceeded only by the higher performance of the CPU. The weakest link is the high performance GPU.

I am not a Gamer.

But I would assume this is a sweet spot for gamers, this is the scenario you would prefer.. to have a more capable CPU partnered with a high performance GPU. Closely matched in fact to take best advantage of the strengths of each.


Black Snow, A Fast way to Warm up Mars

The Martian moons Phobos and Deimos are made up of some of the darkest material in the Solar System. If a solar powered mass driver were placed on Phobos it could be mined for the dark material and used as a kind of rocket fuel by the recoil of the mass driver hurling mined slugs of the material into and over the Martian Polar Ice Caps. 

This would also change the orbit while also lowering its mass, and eventually place it in a Polar orbit. Larger chunks could then be deployed to continue to cover the Polar caps with Dark Carbon like material which could absorb light and melt the polar caps.

The lowering of the mass of Phobos would make it more likely to break apart and easier to mine, close to the Roche limit it should be very easy to redirect huge portions into a controlled break up over the Martian polar caps to maximize coverage and heating effects.

As relics of the Frost belt and being in orbit about Mars when it lost most of its water there is also a good chance a significant portion of the material may contain water and could be salvaged for rocket fuel for orbital travel and deceleration of incoming spacecraft.

Deimos being in a higher orbit and smaller, could also be used as an Electromagnetic dynamo to create a sustained magnetic field. Powered by its orbital kinetic energy, by trailing a long dipole antenna from the moon a distance towards the planet. 

This was proven in an experiment conducted on the space shuttle in Earth orbit. Scaled up.. it should provide some protection at certain altitudes for any travelers or bases in orbit.. as from a solar flare.. and on the surface at certain latitudes.


Artweaver How to Unlock Background Layer

If you Save an Open Image file as PNG and choose 32 bit not 24 bit.

Then close the PNG file and reopen it.

The Image opens as 'Layer 1' with no Background Layer, and its unlocked.

If you save this same file with no Background Layer as an Artweaver .AWD file it retains this property.

If you save this same file with no Background Layer as a Photoshop .PSD file it retains this property.

 If you save this same file with no Background Layer as a JPEG file it looses this property and gets converted back into a locked Background Layer..


Ancient history, time base correction and frame sync or genlock

Time base correction (TBC) for a VCR or used during VHS tape capture seems to relate mostly to correcting the Horizontal sync pulse and the length of the video line timing as it passes through a one or two line buffer.

A line buffer type of TBC was the most common until digital memory prices fell far enough to make field, or full frame "synchronizers" more practical.

What this means is a Level 1 - TBC (a small number of lines buffer tbc) would potentially "band" or stagger its fixes across the entire field and frame of the picture when it was output.. but usually it was unnoticeable unless scaled up, during which aliasing artifacts could appear. - This appears to be why it can be a good thing to disable an older "line-based" time base correcting circuit built-into a VCR when planning to capture and or scaling up a capture using an external device called a "scaler".

What this means is a Level 2 - TBC (only a field tbc) could potentially "jump" or de-sychronize between fields.. perceived more as a glitch, mostly depending on how bad the vertical sync retrace or VTI were between frames. Since "field based" tbcs were not on the market long before being replaced by the more expensive "full frame" capture time base correctors.. these problems are not as common as others. However they could produce a superior capture experince.. since they would not attempt to de-interlace the picture with an out dated poorer quality de-interlacing method.

What this means is a Level 3 - TBC (a full frame tbc) would normally be best.. with one exception, at some point the frame output (which may also perform a poor version of de-interlacing.. since that as a simpler output circuit than leaving it interlaced) may have to drop or repeat a frame in order to remain broadcast "locked" to a data frequency that matches broadcast standard.. while this could be minimized by using genlock.. it could also cause frame jumping vertically in a free running work flow with no genlock use. - While a free running full frame tbc would place that burden on the capture card.. since at some point it will have a a buffer over run or underrun.. and the capture card hardware or software will have to make a decision as to how to handle the situation.. its a choice.. of leaving the decision up to the TBC.. or leaving the choice up to the capture card.. as to how to handle the situation.

TBC - "time base correction" traditionally focused on "curing" problems with the Left "edge" or horizontal portion of the scan lines. While "genlock" or frame sychoonization focused on curing problems with the Top "edge" or the Top and Bottom edges of the field or frame as the field or frames were displayed and the next was setup by moving the focus of the scanning beam back to the top of the visual field.

So "tbc" is mostly about Left edge problems and "frame sync" is mostly about Top edge problems

When things go wrong, 

A flag waving from the Upper Top Left edge is fixed using a TBC or a TBC that specifically "locks" its Left edge "frame clock" before additional lines are displayed.. a TBC that waits and samples more lines may "drift" back and forth releasing some of the Top Left lines before it settles down and locks. It "locks" fast.. as opposed to a broadcast TBC which is seeking to lock on an over the air transmission which may have additional problems related to signal ghosting and locks "slow". Some broadcast TBCs have a setting specifically to support use with a "VTR" in the studio environment.. that locks "fast".

A "vertically jumpy" or "rolling" problem is a frame sync problem and relates to stably outputting a field or frame at the right rate and time to match the expectations of the broadcast standard, or house timing genlock called a black burst.

Ideally and in practice.. a tbc does not do the job of a frame sync.. and a frame sync does not do the job of a tbc. They are two very different things. However some early devices for broadcast and for the consumer combined the two functions in a single box. Whether it actually did correct the Left "Edge" or not is often the question.

And they use digital computer memory to store different parts of the picture.

A tbc samples and stores and corrects and outputs line information.

A frame sync stores all of the "assumed" correct line information for a field or frame and outputs field or frame information.

Performing a tbc on the line information before its captured by the frame sync is important.. since it avoids over and under runs in the frame sync which can make problems with the vertical "jumps" and frame sync output "worse" if it is not performed.

TBC's for the most part are no longer made.. and if so its mostly for SDI.. or serial digital inteface output. All video signals are assumed to have already been converted to some digital format and are rendered analog only in exceptional circumstances and probably not likely to be broadcast in native form.

Frame synchronizers are still made and SD or HD versions are available, often with scalers. But these regularly go for many thousands of dollars used.

Video switchers and DVD recorders are looked upon as potential sources for TBC and Frame sync work.. as pass thru devices.. but for the most part are frame sync devices only. They "appear" to be time base correctors because they have to digitize the entire field.. but more often also de-interlace and output the complete frame.. the effect is the output can have many Left "edge" problems and problems with line length since those devices never attempted anything in the slightest to correct problems with line length. Worse.. the problems are "fixed" by simply "chopping off" badly timed lines and throwing the rest away.. baking in the problems.. from which there is no current way to recover missing information.

True "time base correctors" probably stopped being made about the year 2013 and the use in consumer projects and some commercial projects have probably accelerated the degradation of the supply in the used market.. making them all but  unobtainable in good working condition. Some are servicing the short term electrolytic capacitors.. but these are rare and not often found.

FPGA efforts in the "line doubler world" or inexpensive "scaling" for the Gaming community for streaming is developing an ability to perform many of the functions of not only frame sync.. but also encroaching on the true - time base corrector realm as some older game consoles also had Left "edge" problems.


Blackmagic Thunderbolt Shuttle Video Capture on Windows XP

 Finally got a chance to look at a Shuttle on XP, not the same as an Extreme.

VLC seems to sort of work with it.. but with a lot of trouble.

The Decklink device drivers reject a 720x486 or 720x488 resolution and default to something ridiculous like 720x30.

But trying the Blackmagic WDM driver seems to behave ok with 720x480, but doesn't provide an audio stream.. so right now its very confusing.

The Blackmagic Desktop Video and Driver suite on Windows XP is the first version that I know of that included support for both XP and Thunderbolt Shuttle.. so I guess its a bit early and unstable.

Noel AMCap seems to work just fine with it, and Blackmagic Media Express, and GraphEdit seems to work with it.


Blackmagic Thunderbolt Extreme Video Capture on Windows XP

It would appear the Media Express capture program is not DirectShow based. 

This would make sense as Blackmagic makes a version for other platforms. It appears to use the QT user interface library which is also cross platform.

A best guess would be like VLC, they use a libavcodec or a wrapper like ff to use libavcodec.. but I'm betting they had to keep it simple. There is an LGPG notice included with the program that might refer to the QT libraries used.. or deeper in the code. I did not see a separate libavcodec dll included with the program, so if it is used.. its function are integrated with Media Express binary as a static compile. It is a medium sized executable. dedicated to one purpose.

The weak link in all of my captures has been Uncompressed at 8 and 10 bit resolution direct to hard disk.

Media Express does a good job of capture and maintains sync as far as I have tested.. but my hard drive speed is borderline and would probably not keep up long term.

VLC so far has not been able to keep up and appears to loose sync between the audio and video tracks when captured with the default Raw Record button. Adding a Transcoder to capture as MPEG2 or H.264 would seem to be a loosing proposition.. but might work, if the CPU is not overloaded and can reduce the stream speed such that the hard disk can keep up. Huffyuv is also possible with VLC and might make a reasonable compromise. -- noted that VLC is also capable of decoding and playing back Huffyuv on the fly! Which is quite impressive.

The Blackmagic Intensity Extreme is about ten years old, and in those days the limitations were as now the hard disk speed, in fact they include tools to test the speed.. and recommendations of always using a RAID0 situation to stripe the speed load across multiple disks. Today SSD might be able to keep up, but the individual SATA drive connections may still be too slow.

Noel's AMCap for Windows XP is no longer sold.. however due to his kind response to a plea for help, he did sell me a copy.. and that does appear to work excellently with the Blackmagic Intensity Extreme on the Windows XP laptop across the Thunderbolt connection.

Noel's AMCap for Windows now focuses on 64 bit versions of Windows and more modern versions of the Windows Kernels.. and had to leave Windows XP compatibility behind with the Version 9 of AMCap.

VirtualDub 1.9.11 does a respectable job of capture, but I am concerned compared to Media Express, or even VLC.. its a rather Large and Excessive program just for capture.. it has measures to try and help with hard disk speed like preallocation and buffers.. and logic for dealing with hard disk overruns.. but they are kind of overwhelming to master right away. But it does a good job from what I can see.


The Internals of VLC and How it works

VLC or VideoLAN client, retconned to just VLC.

It is (or was) planned as a media player in a suite of tools for sharing audio video media files from a Satellite downlink on a University campus in France.

It was a student led effort that evolved and led to it being open sourced in the year 2000.

Because not all students used a Mac or a PC or Linux desktop they chose to design it such that it was portable across all those platforms. It has since been ported to iOS and Android as well.

Basically the terminology changes depending on which era of programming, or desktop PC platorm your currently on but its a collection of 'mini" programs called "Modules" linked together in a chain by a "Core" interface being used.

Its mostly a "loader" with a user interface stuck on the front.

The Interface can be a command line string of commands like in a command processor script, or it can be a GUI user interface for a windowing system like wxWidgets, or Qt or Cocoa.

In the background however, once its started, its just making calls to load and start up "modules" and pass them commands parsed from the user instructions to configure them.

Its very similar to the way a GraphEdit Graph works in DirectShow to load "filters" but it does not use "filters" to achieve its goals. People often assume it should expose a filter graph using the graph builder interface on Windows.. but it does not. Instead all of its functions are handled by a series of monolithic "modules" which accept commands from their own type of user interfaces.

So basically VLC was not designed "only for Windows" and does not adopt the DirectShow method of creating filter graphs for performing its functions.

At its center VLC is a ("muxer") which means it takes audio and video streams in, performs some things on them and blends them together and then shoves them out in a new format. While its doing that it can also split off a duplicate stream and "Display" what is currently going through the stream.

Initially it was intended to accept UDP and TCP streams, later reading a DVD device or .ISO file were added, then taking in the Output from a Capture device or a TV Tuner.. these were all added one at a time.. to bring it where it is today.

Just like splitting off the Display duplicate stream, the Record button on the advanced User interface can direct a duplicate stream of the Input data straight to a file, which is automatically named and stored in a pre-configured directory for videos. No processing is performed on a Stream "Capture" as a Record file.. which is rather the exception than the rule with VLC.. and a default Capture/Record processing cannot be configured from the GUI interface.

Separate from a ["Capture/Record"] is a ["Capture/Convert" or "Save"].

Using the "Convert"  button instead of "Play" (which "Play" starts a stream already configured and stored in the Playlist, or completes the process of adding a stream to the stream list and then starts playing it) spawns a Wizard for configuring an Input and selecting a predefined "Profile" which will perform processing on a twin set of audio and video streams to mux them before sending them to a final directory and file destination.

Profiles are preconfigured as VLC default installed, but new ones can easily be created.

The same Convert "Wizard" can be used to complete a File, DVD, Network or Capture Card stream along with its mux processing profile.

The "Stream" button is basically the same thing but tailored more towards "re-streaming" as fast as possible .. possibly without "muxing"

The GUI user interface layers a conceptual way of looking at the the command line way of building up a 'filter graph' in DirectShow terminology even though.. it is not a DirectShow filter graph.. its basically the same thing. "Conceptually"

The VLC command line invocation does not replicate the GUI user interface, the GUI is task based oriented. Where the command line better represents the actual process of building up a single minded, single task process of configuring a input source, configuring the modules that will operate on those source with "VLC filters" and then multiplexing them into a single stream and delivering them to a file or other destination.

Because of the way VLC is built, and its core is libavc.. its sometimes desired to "use" VLC as a DirectShow "filter" itself.

Doing this is possible.

Sensorray opensourced a VideoLAN client bridge

The DirectShow filter appears as a Sink and is preconfigured to save a stream as a processed mux file, currently only as an MPEG1 or MPEG2 file.


Using VLC to Capture from Blackmagic Intensity Extreme on Windows XP

This took a while.

And I'm still not sure I totally understand it.

But to get a "Perfect" capture and Preview on Windows XP SP3 with Thunderbolt and a Blackmagic Intensity Extreme.

Here are the manual steps:

1. Open VLC

2. Go Tools > Preferences > Video 

3. Use the drop down for "Display ----- Output ----> [Windows GDI video output]"

The default "automatic" will produce a blocky chunky slow video window with multiple artifacts all over the place, so be sure to manually set the "Display Output method to Windows GDI video output"

4. Save

5. Media > Open Capture Device...

6. Video device name: Decklink Video Capture

7. Audio device name: Decklink Audio Capture

8. Video size: 720x486

9. Advanced options: check, Device properties


B. Play

C. First "popup" Properties > Video Format

D. Use the drop down for Video Format: (Scroll Up to pick the First: NTSC - 8 bit 4:2:2 YUV)

The default identical looking (NTSC - 8 bit 4:2:2 YUV) is an accidental abbreviation for NTSC "Progressive" which appears to be improperly rendered on Windows XP at the moment. The "Top" position in the list is actually the same "Interlaced" which takes less time for VLC to process and display.

VLC has its own internal software De-Interlacing options which appear to work without the long delay or lag of the Intensity Extreme "profile".. so I am uncertain what is going on.

Also the Blackmagic Control Panel applet is responsible for actually setting up the Intensity Extreme for input.. so it could be the pop up panel is confusing the DirectShow pin that feeds VLC and it may be mininterpreting the input as Progressive when it actually is not.. I do not know for sure.

For now.. just do it.

E. Apply: OK

F. Second "popup" Properties > Audio Format


It takes about 1 or 2 seconds for the window to launch, audio and video are "rock solid" and in-sync.

All  of this was figured out by trial and error.

Windows XP SP3

Blackmagic Intensity Extreme

HP Thunderbolt laptop

VLC Player 2.2.6 Umbrella

Pressing the [o] red dot "Record" button saves the currently viewing Preview as a Lossless .AVI file to:

C:\Documents and Settings\{my-username}\My Documents\My Videos

The videos are lossless, but the audio, video playback are very far out of sync.. and the file information reports a frame rate of 21.xx below 29.97

So I don't know if its a difference in format interpretation or dropped frames or samples.. or something else I do not understand.

Blackmagic went to a lot of trouble to not playback audio while capturing in Media Express and calls the process out as harmful to maintaining sync while capturing. VLC plays back audio while its capturing.. perhaps introducing a delay in the audio stream when writing to disk.

I am not entirely sure how to disable audio playback in VLC while capturing both audio and video. It could be a challenge.

VLC Preview however the audio and video are in lock step.


Enabling Blackmagic Intensity Extreme Input Monitoring on Preview on XP

On XP various sound chips may or may not have internal loopback circuitry to support monitoring the Mic Input.

This is important to understand because the Blackmagic Intensity Extreme device drivers do not appear to have an internal loopback for monitoring the Audio Inputs during capture and appear to pass-thru the audio and video to either the HDMI or the S-Video or Component Outputs.

For HDMI output the audio is embedded in the single connector.

For S-Video or Component outputs the audio is duplicated on the RCA output jacks.

I didn't run down the specific example with the chipset on my laptop, but more generally plugged in an M-Audio Sonic Theater sound card to the USB port and connected the RCA output jacks of the Intensity Extreme to the "Line Input" of the Sonic box and the Sonic box speaker outputs to a set of external speakers.

Routing the output through the Speakers was relatively easy and not much had to be setup, except the M-Audio control panel applet had to be used to "Enable Monitoring".

This sounds annoying.. but because Input Monitoring was not a "class supported" featured during the XP era, there was no "one way" of doing it for all chips. In Vista and 7 and beyond it was adopted as a class function and could be automated by visting the Input device "Listen" page to switch Input monitoring on.

Using an external "loopback" by using an external USB sound card.. was just a simpler.. more consistent work around that should work on all brands and model of PC.. since the M-Audio USB sound card has a "Monitoring" check box exposed in its Control panel.. and its portable.

Blackmagic Media Express "might" have a "monitoring" registry key.. but I haven't found it.. and judging from the old Blackmagic forums.. it probably doesn't exist.


422 Capture Blackmagic Intensity Extreme on XP using Thunderbolt

Not the easiest chain to put together.

But yes. There is a laptop brand and model with a Thunderbolt port, that fully supports Windows XP 32 bit.

And a BlackMagic Designs Intensity Extreme (Thunderbolt) with a version of Desktop Video and Media Express which works on Windows XP and installs a 32 bit device driver in XP for Audio and Video capture on Windows XP.

This kind of gives me "ideas" about how to create an Auxilary "Crossbar Control" that is independent of the DirecShow device drivers.. but can also help toggle bits that the normal DirectShow Control Panels do not. Pinnacle "Marvin" device usb-500, usb-700, usb-510, usb-710 come  to mind.

The old ATI TV Wonder 2.0N also is a possibility. USBSnoopy and USBRobot can bring over the 32 bit device driver to the 64 bit space, but then the DirectShow model doesn't fit. I'm not sure of the entire path.. but it gives me ideas.

In any event, the Intensity Extreme (Thunderbolt) under XP works.

However.. like all other platforms, to get it working you must first visit the Control Panel and use the BlackMagic Control Applet to manually set the Input and Signal format. (Not through the DirectShow device driver control panels.. they do not work!)

Windows Movie Maker 2.1 does not seem to have a problem using the Intensity Extreme after its setup. But there is some Audio device strangeness. It can record Video, it can't record Audio and it can't make clips after the capture. - So effectively only  BM Media Express can create .avi capture files with both audio and video captures.. which is very good.

 I only tested Component and S-Video inputs, and with a good signal, they are on par with one another. Crisp solid and invariant. 

I also tested with VirtualDub 1.9.11 - 32 bit, it works flawlessly. Captures audio and video.


Pinnacle "Marvin" video capture using the DV port on Win 7 x64

Until recently I didn't think the Pinnacle Sys device driver for the Pinnacle USB-500, USB-700, USB-510 and USB-710 would support the Firewire (IEEE 1394) port on each of these devices under a 64 bit operating system like Windows 7.

It turns out they do, but the Device Driver Installer does not properly install a separate [System class] device driver at the same time as the Sound, Audio, Video capture device driver.

Since the installer on Windows 7 64 bit is effectively ('broken') it took some time to figure this out.

It does not appear to be a full featured "Firewire" port, and does not appear as a IEEE 1394 port under the Device Manager tree. It does not support mass storage devices for exampled, like a firewire external hard drive.

Rather what appears to happen is, if a self-powered DV video capture device is connected to the DV port, after a long silent, no-feedback pause. Windows Device Manager will add a new [Image class] AV/C Tape device which represents the video capture device, and will proceed with autorun to auto-start the Windows Movie Maker and suggest capturing video from the device.

This is surprising and very convenient.

Even though it is not a full fledged universal Firewire port, it provides the Video capture feature for a video capture device which is often one of the easiest methods of importing DV camcorder, or VHS or other types of video capture footage into a PC.

Further the Pinnacle software is rather long in the tooth and doesn't often work well with Raw YUV 422 video capture from the USB device itself at full bandwidth. The device drivers sometimes work if the specifications of the capture PC are high enough and the stability of the operating system is good enough. 

But then the audio capture device driver for Raw YUV 422 often shuts itself off or disables it so that if invoked by any other third party software, remains silent. This can be worked around and turned on, but must be turned on after the device driver is loaded each and every time.. since it will disable itself each time the device driver is unloaded or the PC is reboot.

The DV port has none of these problems, nor any problems with audio/video sync drift. And since the bandwidth of a hardware compressed stream is significantly less than a Raw YUV 422 stream a low specification PC often suffices.

This is very different from a "powered" DV port, like the 7 watts of power a Thunderbolt 1.0 port connected to an Apple Thunderbolt to Firewire adapter can provide. In this case the video capture device has to provide its own power source.. often an optional power port on the firewire device which the manufacture saved money by not providing an "optional" external power adapter.. but they can be obtained.

One of the Huge advantages however is that many laptops no longer have Firewire/DV port and one cannot be obtained, especially with Airbooks, or travel laptops. This only requires a USB 2.0 port, and can be adapted down to a USB-C port if needed to allow those devices to become super simple and easy video capture devices with no audio/video sync drift.

These devices are no longer made or sold, but they are really nice to have around.

A more comprehensive method of installing the secondary [System class] Pinnacle Marvin 64 device driver needs to be documented.. but one tip appears to be that Win7x64SP1 base installation without any flight time, and no Updates applied .. simply seem to work, they install the [System class] Pinnacle Marvin 64 bit device driver. -- I suspect its either the 'flight time' on a laptop or desktop or one of the later device driver updates that ultimately foobar's the device driver installation process.

This has been tested on both Windows desktops and laptops for Windows 7x32SP1 and Win7x64SP1 but has not been tested with Win8/8.1 or any variant of the Windows 10 versions.

Video capture with I-O DATA GV-MDVD2 and GV-MDVD3 on Win7 x64



Is a product line of video capture boxes from Japan , they aren't often seen outside of Japan because they use the NTSC-J variant of the NTSC color signaling standard which has a wider sampling range than in North America with the Pedestal Set-up. 

They are "capture" boxes, and so are not detected as Broadcast Tuner capable devices and Windows does not support their use with the Windows Media Center products.

They produce a rather unique MPEG-2 stream which contains both audio and video in their output pin, which can be directed to a file, or decoded and displayed within programs that understand the MPEG-2 stream. VLC is the most often used. VLC is also capable of saving the output to files in various formats.

The GV-MDVD2 has no 64 bit windows device driver, however it does work with the later GV-MDVD3 64 bit device driver. In fact it is detected as a GV-MDVD3 device. The hardware MPEG-2 encoder chip is the CX2316-12 and the video decoder chip used to process incoming video signals is reported to be the PHILIPS SAA7115HL. It is my guess the difference between the GV-MDVD2 and 3 is only with the driver disc provided and the Windows versions marketed towards. They appear to be the same hardware with different labeling.

One difficulty is routine access to the hardware switch within the device called a video switching Crossbar. This can be accessed either using the 32 bit version of GraphEdit with a GRAPH.GRF file. Or with the widely available "Crossbar Thingy" application. Either of these will load the Windows DirectShow component installed along with the device driver which allows a dialog window that allows selecting the Input source, to switch from Composite to S-Video.

Fair warning, the GRAPH.GRF file must be "opened" or "dropped" on an x86 (32 bit version) of GraphEdit or it will fail to open. Some components are not compatible with the 64 bit only version of the GraphEdit program, but work just fine with the 32 bit version of GraphEdit running on Windows 7 x64 bit natively.. and "not" in Windows XP mode.

I have not tested, but its suspected versions of MyDVD, Intervideo WinDVR and ULEAD capture products will "probably" work, since those cater more towards the MPEG-2 streams.

Windows Movie Maker, being for Raw YUV 422 or UVC products does not work with the GV-MDVD products.

The GV-MDVD (1) product is not like the GV-MDVD2 or GB-MDVD3 products, being from an earlier time it is based on the popular WisGO007 pre-compression hardware chip.. which produced a YUV output or a soft compression GO stream which could be software compression "finished" into MPEG1/2/4 versions. This sounds more versatile, but it is not by today's conventions.. because it relies on many software libraries that are only available on the Windows XP platform and were not brought forward. The Monsoon Snappysoft software from Luminate is known to work with it on the Windows XP 32 bit platform only.

I-O Data seems to have had a very long import line into the Japanese market with the GV-MDVD product line which seems to have favored importing the YUAN video capture products.. but details are scarce.


Using VirtualDub 1.9.11 to capture Video from ADVC-55 on WinXP

VirtualDub is a pretty old, familiar program to most people.

It starts in Edit mode, but you can go into Capture AVI mode from the File menu.

However with the ADVC-55 the initial window is Blank or Black with no sound.

To begin preview, the AVC Tape controls must be used to "Start" the Preview.

This is rather un-intuitive.

Normally you:

1. Go to Device  "to select" > Microsoft DV Camera and VCR (DirectShow)

2. Go to Video "to select"  > Video source (not necessary with ADVC as it auto selects Input)

3. Go to Audio "to select" >  Enable audio playback


But the display will remain Blank / Black


For a Firewire or ADVC device you also need to:

4. Go to Video " to select" > Capture filter ...

A Dialog called "Digital VCR Control" appears, simply Press the green Play button [ > ] and then Press [OK] to close the dialog and return to the running Preview.

This is rather different from other programs like Windows Movie Maker, in that in those you have to configure the program to allow "Manual" rather than "Automatic" capture control. -- In fact its the opposite procedure conceptually.

It makes apparent that most capture programs will attempt to "Start" the stream by itself automatically when the program starts, rather than waiting for the User to queue up video manually on a playback device, or to start the stream. This can be a problem for things like DV codecs since they cannot start until a video signal is actually coming into them.. they will produce an error code. With a real DV camcorder or video camera capable of reacting to the Start command, the video signal starts playing before the codec is engaged and there is no error.. but not so for a standalone DV codec which expects a video signal to be present and will fail and shutdown if one is not present before starting the encoder.

Its just not a step that most people consider, they assume "something" will send a blank signal which the encoder can use to start producing blank frames before the video signal is actually queued up.. but such a device is generally very expensive in the video world and is called a "frame synchronizer" and would have driven the cost of a device from those years up.

Instead, the user starts the Video to generate frames which the encoder then starts to process to produce a stream, and then the VirtualDub program assumes the encoder is sending frames that it can preview.

For raw video capture its similar, but frames are always there from the moment video is presented.

Its the option to "automatically" command the DV camcorder that makes all of this "different" from a stream that is always running. The pros and cons of having complete control.

How to block Phantom Floppy device / drivers from setup and loading in Windows XP

On a recent new laptop setup that had no Floppy drive. 

I kept getting a Phantom Floppy Drive in the Device Manager.

It would load the fdc floppy drive controller service and the floppy device driver and fail to start, producing the familiar Error 10 "fail to start" and a Yellow cone Warning sign opened in the Device Manager tree.

This was annoying, while from Vista forward you could use a Group Policy Object security policy to "Block" loading device drivers for specific Hardware IDs. You can't do that on Windows XP. And if your using Home Editions you often don't have Group Policy Objects or a GP Editor.

I found you could "Fix" this by first uninstalling the Phantom drive from Device Manager then going to C:\Windows\Inf and temporarily removing the fdc and floppy (.inf) files from that directory (both the .inf and precompiled .pnf versions) (say move them to the Desktop) then perform a Manual Scan for Hardware Changes in Device Manager.

It will fail to find the fdc and floppy device drivers, and setup failed "stubs" in the Device Tree.

Manually selecting and installed the "Modem/Unknown Modem" device driver for the Phantom will not set up a "service" and will collapse the Device Manager tree as "satisfied" Permanently... with no Yellow Cone Warnings.

It is a "trade" from a Phantom Floppy Drive to a Phantom Unknown Modem device, but much less alarming.. and typically the Unknown Modem is used as a proxy for the example of a "Null Device Driver" that doesn't install or register any start up service for a device in literature.. so its kind of a "lazy mans" way of writing a Null device driver for a Hardware ID that is either wrong or fake.. that you would rather did not produce a false positive error in the logs or on the Device Manager dashboard.

 After doing this replacing the  fdc and floppy .inf /.pnf files into C:\Windows\inf does not return to trying to dislodge the manual assertion between the device and the Unknown Modem "device driver". Future reboots and manual hardware scans continue to report the device is installed and associated with the Unknown Modem "device driver" and do nothing annoying. This is good in case you do install a really floppy device via USB or some other port means.

Using Firewire and Thunderbolt 1.0 with Windows XP Professional

So.. the other shoe drops.

Windows XP works perfectly fine with a laptop that has a Thunderbolt 1.0 port (the mini-display port kind).

And at least when the HP Thunderbolt Firmware modification too is used to disable the "Only Certified for Windows" Thunderbolt port block. 

Windows XP works fine with the Apple Thunderbolt to Firewire adapter.

I am not talking about using Apple hardware with Bootcamp. I am talking about using HP hardware running Windows XP Professional (and its probably not specific to "Professional").

The one thing different between Windows 7 x86 32 bit edition and Windows XP x86 32 bit edition when setting up a Thunderbolt connection is that after its hot plugged into the Windows XP system, it requires a reboot to start the service setup for the PCI bridge that is detected, until then it will have a Yellow Warning cone in Device Manager for it.. after it reboots it will finish enumerating and finding the OHCI port on the other side of the adapter.. this kind of makes perfect sense for the way that Windows XP does things.

On the laptop I have the ACPI HAL works for Windows 7 x86 32 bit, but does not for Windows XP x86 32 bit.. I had to use nLite to shoehorn the AHCI device drivers into the installer, make a .iso image.. and used an IODD external CD/DVD drive emulator to boot from the .iso image to start the installation.

When it got to the F6 additional device driver step, I used the undocumented F5 to select the specific HAL. This had the side effect that ACPI can never be used to finish shutdown in Windows XP.. and I did try all the other HALs.. but only Standard PC (legacy support) worked on this particular laptop. 

Until I selected a specific HAL it would always shutoff after the F6 step and not complete XP installation.

Once I bypassed the autodetect of the HAL and continued the installation process.

I connected a Canopus ADVC-55 to the Apple Firewire adapter and it was dutifully setup and the Autoruns service of Win XP offered to start Windows Movie Maker to capture video.. which worked as expected.

In any event, the Movie Maker captured video also captured sound and imported it into the Movie Maker application for editing.

This particular example of using Thunderbolt 1.0 with XP on an HP laptop is rather unique in that at the time the laptop would have been over $1500 in 2012 dollars, so not many people may have tried it.

What stands out as very interesting is that while Thunderbolt has a firmware layer, it is independent of the general operating system. Once configured with tools for other operating systems it can be used with any operating system. To all operating systems it just appears as a hot plug PCI bridge device, any scanning of the other side of the bridge is at the discretion of the operating system once the port is in use.


Using Firewire and Thunderbolt 1.0 with Windows 7 x86 Professional

 Along about 2010 Firewire was beginning to be abandoned in favor of USB and faster alternatives in laptops. However there was still a good use for Firewire or IEEE1384 ports for connecting legacy hard drives, cameras and video capture equipment.

For a time laptops could still be found with Expresscard ports and used with Expresscard to Firewire / IEEE1384 ports but eventually those went away as well.

Sony Vaios, Lenovos, Dell and HP products initally had some laptops with "mini" IEEE1384 ports but they too disappeared.

Apple Macbook Pros eased the transition by including a Firewire 800 port and a Display port, and then replaced the Display port with the identical port on Macbook Retinas with a Thunderbolt 1.0 port.

It wasn't called Thunderbolt 1.0 but retroactively can now be referred to as Thunderbolt 1.0 since there were Thunderbolt 2.0 and Thunderbolt 3.0 versions later.

Thunderbolt 1.0 is basically a Display port connector with additional lines to support  PCIexpress connections in the same connector as the original mini Display port connector.

Thunderbolt 2.0 is essentially the same as Thunderbolt 1.0 using the same mini Display port connector with a logical speed boost from 10 Gbps to 20 Gbps.

Thunderbolt 3.0 uses a different connector (USB-C) and also supports a USB 3.0 mode as well as getting a speed boost to 40 Gbps.

Besides Apple, a few manufacturers also made early laptops with Thunderbolt 1.0 connectors. HP being one with the Spectre XT 15 Ultrabook line. These had one mini Display port Thunderbolt 1.0 connector. 

Designed for Windows 8 (and later upgradeable to 8.1 and 10) out of the box, they would only support Thunderbolt 1.0 devices certified for the Windows OS.. and would not support The Apple Firewire to Thunderbolt adapter.

However HP retroactively released a Thunderbolt 1.0 port configuration tool for their Thunderbolt firmware that could enable support "Any" Thunderbolt connected device whether it was certified with Windows or not. This enables Windows 8/8.1/10 to support the Apple Firewire to Thunderbolt 1.0/2.0 adapter.

Basically once this tool is run the Thunderbolt port is set to enable all Thunderbolt devices connected to its port. This is not the default because of the Intel specification barring support for certified devices for specific operating systems. Its rather nonsensical and unintuitive. Without doing this inserting the Apple Firewire to Thunderbolt adapter only adds six PCI to PCI bridge devices to the device manager tree and stops.. it does not enumerate the 1394 OCHI device on the other end of the adapter.

The HP Spectre XT 15 is based on the Intel IVY chip architecture which means it fully supports Windows 7 and has a Legacy CSM BIOS mode for booting from MBR partitions.. which means not only is Windows 7 x64 (64 bit mode) supported, but Windows 7 x86 (32 bit mode) is also supported.

Once the Thunderbolt port is configured "open" to support uncertified Thunderbolt connected devices.. this carries over if Windows 7 x64 is installed, even for Windows 7 x86.

What happens when the Apple Firewire to Thunderbolt adapter is inserted (hot swapped) into Windows 7 x86 (32 bit) is six PCI to PCI bridge devices are created attached to one of the PCI express root ports, off of one of those a 1394 OCHI device is enumerated, and then an AVC and AVC Tape device is created.. if you have a firewire video capture device like an ADVC Canopus video capture codec attached.

The default 1394 OHCI device driver is not best and should be swapped for the (Legacy) version for regular work.. but it works.. in 32 bit.

This is a pretty slick method of using a Thunderbolt port on a Windows PC to connect up a native Firewire device for video capture and feed that into many 32 Bit Non-Linear Editor workflows from the past.. like Sony Vegas, Adobe Premiere and so on.

This also worked for later HP Zbook and Folio Ultrabooks.. as long as you manually downloaded the HP tool for re-configuring the Thunderbolt port and opened it up.. for Thunderbolt 2.0 and Thunderbolt 3.0 later chip architectures however make it less compatible with older operating systems.

The HP Spectre XT 15 is a little unique in having the IVY chipset since in theory it can also support Windows XP .. a rare thing today.. if you need it. And it will be interesting to see if Thunderbolt 1.0 can be supported under XP in a native manner.. stay tuned.


What if we're Pinball Machines not Memory Machines?

 Thinking about thought.

We tend to categorize by like is like, associations.

So we think of our brain and our thoughts like a computer programming running on a central processor.

Its something we sort of intuitively understand, and is sort of like the machines we hold in our hands. Turn crank, procedural kinetic motion produces output.

Memory is a little more like referring to a pen and paper and referring to a book for past mechanical motions.. the results.. become memory.

And we think our memory is like a book, the end result of our past mechanical actions.

But what if its more like a result machine, not that it methodically copies and encodes inputs like writing on a strip of paper.. but more like a spikey soccer ball with lots and lots of spikes.. that the envionment twists and turns and tumbles and leaves it laying in a pseudorandom state.

Not in a methodical easy to copy and recompose manner.. but the end result of a wad of paper crumpled and torn, and shaped by endless unpredictable blows and interactions with its environment.

More like a 'pinball' in a pinball machine.. its not as much a copier of the inputs from the environment.. as it is a reactor machine that seeks merely survive to experience another day.. an endless purgatory machine endlessly suffering.. the best outcome is not to cease functioning.

To extract memories.. or something more portable to easy to download and upload then.

Might be much harder.

We might rather need to  subject this tumbling soccer ball to a virtual environment to observe how its current state 'reacts' to all of its past experiences and currently interprets that which we erroneously perceive as the 'past' at the present time.

In such a scenario then, the 'past' or 'memory' becomes an endless sense of partially true, but also partially self described recollections of what its been through.. its not so much what it remembers.. as it is how it dictates or understands as its current view of the past. So.. in order to 'recall' the past.. it must forma virtual environment.. a virtual machine inside its head.. and use its imaginary narrative pointer and point it at this virtual machine in order to play out scenarios.. sort of 'imagine its 10 years ago and I'm walking through my house.. what do I see?' Then the current brain or mind 'state' begins reacting to the virtual environment and feeding senses of sight, hearing, smell into its current inputs via virtual imaginary sensors and playing out the Theater as if it were a play.. and holding those experiences  in something akin to a temporary memory buffer in our heads.. much more akin to a linear computer memory buffer.. so we can use those experiences as a near term second set of senses that can act as a mini-brain in a virtual environment to model a scenario we are trying to solve for.. to predict a near term desirable outcome.. sort of a Monte Carlo situation where we try try again in our tiny version of minecraft to come up with a solution we think will be worth betting on an the real world with our bodies.

If true.. if you want to tap into that.

It might be to extract or copy a memory.. or make new ones by uploading.. you need to tap into the virtual machine used for near term temporary memory.. and the senses it uses for input and output.. be they real or imaginary.

The real senses.. using head gear and tactile feedback like mice our keyboards.. we kind of have a grasp upon.

The temporary virtual machine senses of near term memory, we kind of don't have a good grasp of.

Magnetic Induction, neuralink.. are pokes in that direction.. but until we have a more solid connection to the temporary memory virtual machine and can spawn a set of neuralink virtual senses which the brain will accept as 'like' those it creates on the fly for visualizing scenarios for solving problems.. it could be a tough road.

Video games and game console controllers are close, they can immerse a person in a world without physical contact.. even trigger an imaginary experience where we use our perceived memory of reaction based on our past experiences. In such a situation the first person shooter is literally building their own bridge to the outside world and reacting based on their memories.. downloading  in that scenario is akin to interrogating a player for what they recall.. in real time.. since their arms and legs.. can only move in real time.

But we know we can think much faster than physical action.. the effective bandwidth can be increased in a dream state.. abbreviating or hopscotching across a dreamscape to lessor or more important elements of the story.

And in fact we know we can Upload memories very easily.. by watching a movie. Again the brain finds a way to bridge the gap.

Given the way the brain uses glucose and oxygen.. it may be that a person can only upload and download at faster than real time in a subdued, physically inactive dream state.. in which they are paralyzed to optimize nutrients and oxygen and blood supply for the brain.


Startech USB2TVTuner is based on EMPia Audio and EMPia Video chips Not WIS GO007


So it turned out the Startech USB2TVTuner is not a hardware compression based device. Hailing from the year 2002 and sold up thru 2007 it was basically a simple YUV digitizer with USB bridge to get the raw 4:2:2 from the capture chips to the software on a PC.

I found this out after examining a unit that no longer worked.. the hardware was busted in some manner. 

And confirmed looking into a device driver .INF file which only referenced EMPia capture chip technology.

This leaves the ADS DX2 Express and the Pinnacle dazzle AVC-130 and AVC-170 as the most common WIS GO007 hardware capture devices. But only the ADS DX2 had a not ready for prime time 64 bit device driver that was never signed and roughly works under Windows 7 x64 with difficulty.

It appears Micronas and then TDK acquired the WIS chip rights and it might have been taken off the market or folded into another portfolio.. but WIS based hardware compression capture chips disappeared after XP support basically ended for things like the Plextor M402 and related series.

ATI had a go at continuing MPEG2 hardware compression until the end of that company being acquired by AMD. ATI had the 550, 650 and later 750 chips with mostly Windows Media Center support under XP and then Vista.

Lumanate would produce the excellent Dell Angel MPEG USB series, which targeted the Windows Media Centers worked with Monsoon SnappySoft capture software.. and AMCap (after a fashion).

AverMedia of Taiwan and Hauppauge of New Jersey/China (?) are still offering products and had a long line of offerings both with recognized and individually proprietary and their supported versions of capture software.


Categories for Render, Capture and Nodetypes Microphones, Line Connectors and Speakers

In addition to the KSCATEGORY_AUDIO Categories, the INF file can also "decorate" the device driver as having other interfaces that the builder might want to probe.

These can help in directing the builder to probe and fill out a description for the device when making its Audio Endpoint.

For some of these types it attempts to discover abilities and interconnected topologies so that the Endpoint makes better sense to the end user when complete.

Video capture and Audio capture applications typically try to "find" or make sense of the resources of a video capture card by strumming theses "inventories" of endpoints and interfaces when building up a list of choose-able sources and sinks of video and audio data.

Video Capture applications aren't very sophisticated when looking for sources beyond the current year in which they are written.. so a re-think or re-conceptualization of how to present usable resources can lock them out of running properly on newer re-thought operating systems.

"Some" device drivers hook themselves into the default audio or "desktop" when loaded.. some do not.. those that do are easier to support with legacy capture software because they merely have to capture from the default channels of the system.

UVA and UVC seems to be the latest "re-think" in the way video and audio information is presented as a resource to the operating systems and programs. And they are generally across USB serial buses.

Since Analog video capture is mostly long gone.. supporting moving between XP to Vista and 7 or 8 and 8.1 is unlikely to be something that can be done for much longer. Even the device driver signing methods and keepers of the hardware and kernel keys is consolidating at Microsoft.. and locking more and more of the developer community out.. which could lead to an upheaval in computer programming moving forwards.. abandoning Microsoft and Apple products for a more flexible and open system.. unlikely Linux since that too seems to have started blocking flexible development models. A stagnation of original thinking seems to be beginning a new dark age.

Ironically the XP operating system without hardware device driver signing.. is the easiest to develop for.. and the ReactOS may eventually prove to be the favored operating system of the future. Its hard to imagine Microsoft will mentor and shoulder the burden of solving problems for indiscernible and not immediately profitable motives long term.

Why Video Capture boards don't display Audio Endpoints in Vista and 7

I'm real fuzzy on this at the moment.

But it appears when going from XP to Vista, they re-thought how Directsound or Directshow audio devices were presented to programmers.

They invented something called the "audio endpoint builder service" which monitored the PnP insertion of device drivers, registering various characteristics about loaded device drivers in the registry or class tree.

When one added itself to the "KSCATEGORY_AUDIO" class category, it went to work "probing" the "device" attached to the system by inspecting its pins and their default parameters.. automatically constructing an "Audio Endpoint".

These virtual "Audio Endpoints" were conceptually thought to be "better" than using the Directshow API which was based on filters for accessing and manipulating the hardware on a device directly.

Instead, users and programmers were able to "think about" the Audio Endpoint as a fully fleshed out object which they could use more generic commands to control to setup an "Endpoint Session" which was assumed "Blocked" until it was "un-Blocked" and began streaming data, either In or Out of its device.

Once these Endpoints were constructed, they populated the Sound Control panels where they could be designated as the default Playback or default Recording Endpoint.. 

The reason video capture cards do not appear as Audio Endpoints, is apparently because they're device driver INF files do not "decorate" themselves as "KSCATEGORY_AUDIO" class type.. and the "audio endpoint builder service" ignores them and does not build up the Endpoints the Sound Control panels use to populate the choices in the Playback and Recording endpoint choices.

It seems the "pins" for In or Out should also be decorated with descriptions of whether they are WaveOut or WaveIn or some other type.. but mostly the rest of the Directshow description should map to parts of the constructed Endpoints, since the Vista revised "re-conceptualizing" allowed for supporting legacy communications protocols and interfaces.

So.. its possible their devices will just work once their device drivers are revised to carry the badge of "KSCATEGORY_AUDIO"

One potential problem however are "signed" device driver packages.. since they are supposed to come with a .CAT and certificate set that ascertains the device driver has not been tampered with.

It might be possible after the device driver is installed.. to manually patch the registry to "add" the device driver/device to the "KSCATEGORY_AUDIO" by adding its guid.. if thats how it works.. but might also need to do that for its Pins.

Win7 x32 seemed easier to avoid device driver signing problems for a test.. or self signed was at one time possible with Win7 x64