7/23/2023

Video Tape Capturing and Saving to DV, VC1, h.264 natively

I was playing with ChatGPT and discovered maybe some little known facts about Windows 7.

Capturing to native DV format produces a high quality file losslessly with slightly degraded color sampling, 4:1:1

However since the NTSC format is recorded to tape using a slightly degraded color sample by way of using Color Under sampling.. assigning less bandwidth to the color component of the signal UV than to Y, the conversion from a lessor color signal to 4:1:1 digital sampling is essentially the same thing. And nothing is lost, there simply isn't any more signal bandwidth available to carry more information that that collected by 4:1:1 digital sampling.

DV video does a noise reduction step passing a DCT - Discrete Cosine Transform over the signal, but does not 'compress' or reduce the actual number of digital samples in the Y or UV axes, this results in a large digital sample file, but should retain as much of the original signal as possible for playback.

DV does not in anyway attempt to up sample or 'invent' more information than is actually present in a signal, nor does it attempt to convert from field to frame (otherwise known as interlaced to progressive conversion).

Other compression schemes like MPEG-2 (h.262) or h.264 treat color samples somewhat differently since they were invented for film to digital conversion and the available signals when converting from film to digital video were captured using full frame cameras in a progressive to progressive conversion format. the full frame digital cameras had 4:4:4 available to them and MPEG2 or h.264 could take advantage of the higher available color sampling and down sample the color space to 4:2:0 for retaining slightly more available color signal than a Broadcast or VHS tape Color Under sample which never had anywhere near the same original bandwidth due to the NTSC remote transmission standard.

When converting from VHS tape to digital files became popular, using the latest technology was considered more attractive and owning one device for capturing as opposed to many limited the popularity of a basic DV converter.

Windows went from mostly using DV capture tools like Windows Move Maker, to Adobe Premiere Essentials and Pro, Sony Vegas, Canopus DV or Grass Valley EDIUS in the 98 thru 2000 and XP editions.

Windows 7 followed up with tools such as Windows Live Essentials installed separately which could capture in DV format, and then quickly "convert" the Lossless DV file format into Windows WMV (VC-1 .. basically Microsoft answer to h.262 or MPEG-2.. or Windows MP4 h.264 AVC) formats.

The key was not in the Save Project menus, but the [Save Movie] menu and choosing the delivery type and format. Save as DVD Burn would convert to VC-1 and automatically transfer to Windows DVD Maker to guide thru setting up a Menu structure for a Disc and then burning to a DVD disc. Choosing a delivery type of [For Computer] granted the option of giving the file to be saved a specific file name and file system destination, and then choosing a file type [MPEG-4/H.264 Video File (or) Windows Media Video File - WMV/VC1]

These tools while they could be used with a DV bridge were more targeted for use with DV technology for offloading or uploading DV Camcorder videos and then converting them to DVD or File consumer types.

They soon upgraded to working with MPEG-2 hardware capture devices since those were more popular for capturing Broadcast or Cable video files where commercials were routinely edited out and the delivery types were stored on low capacity storage devices like hard drives or limited DVD media until consumed.

The MPEG-2 hardware capture types were of lower absolute bandwidth than DV firewire, and could finally be handled not only over PCI 2.x and USB bus types eliminating the need for high royalty hardware that required firewire .. but in theory could capture slightly better color signal if the transmission type were over a medium that were totally digital, as with ATSC instead of NTSC.

Some of the details got lost in the translation and a semi-cult status of video capture in 4:4:4 uncompressed formats erupted over the intervening years, as non hardware encoding field and frame grabbers became cheap and widely available. They did not add anything to the quality of the signal capture and in fact complicated many problematic signal captures where previous hardware encoders had special time base and frame synchronizing abilities that simple frame grabbers did not.

4:4:4 was and remains the capture domain of film and studio on site rather than something easily mastered at home.

h.264 and later compression techniques were developed initially for the purpose of enabling mobile phone and internet video delivery; but later profiles enabled matching and exceeding the delivery quality of MPEG2 and have all but replaced them.

The initial age old question of DV versus MPEG-2 or h.264 capture options side steps or 'hides' the question of archiving in 'Interlaced or field based format' versus archiving in 'Progressive or frame based format'. DV from the outset was 'field based' and is based around SD or Standard Definition 720x480 video.

Later versions of DV such as HDV utilized a form of MPEG-2 compression without the interfield/interframe temporal distortion inherent when converting a field based video to a frame based one, and the unavoidable artifacts that result from that step. HDV however was never popular and very short lived. 

The arrival of TiVo and DVD recorders and their popularity, and the arrival of EyeTV and Windows Media Center eventually led to the broad assumption that MPEG-2 and DVD formats were superior to DV or HDV for all purposes. After 2009 and the conversion from NTSC to ATSC formats most TV transmissions became Progressive with ever enlarging frame sizes much higher than 720p .. leading to further interest in high compression ratio codecs like h.264 and presently h.265

The conversion step from DV to MPEG-2 was not without forethought, color samples are 'co-sited' withing a field and frame so that minimal color aberrations are possible. Also MPEG-2 formats allow for profiles that are 'interlaced' as well as 'progressive' .. and later h.264 formats also allow for field based video storage formats.. which are rarely used or supported in normal hardware playback equipment.. leading back to the observation that only a sophisticated and complete software playback system can hope to cope with archaic full resolution and un-temporaly distorted playbacks of old content that are artifact free when the content has been compressed, especially if it has been converted to framed based 'Progressive' formats with no way to undo the irrevocable choice made in the era in which it was 'mashed together'.

This all leads to me to personally conclude, for VHS or possible Betamax video capture to an archival format; DV is probably the best format. MPEG-2 and h.264/h.265 formats are smaller and are still serviceable delivery formats.. and because of their size and rapid portability may make survival of 'a copy' even if not the best quality available more likely.

This has to be taken as a recommendation for SD content only, since DV did not support larger frame sizes. And all content after NTSC to ATSC would already be in Progressive format with a larger color sample budget.

Dealing with DV bridges inevitably leads to questions of time base correction, frame synchronization and how to use a firewire device in Windows 7 or later operating system.

Time base correction and frame synchronization is a prerequisite to submission to a hardware codec device, even a DVD recorder.. so effectively a DVD recorder with pass-thru processing is a combo tbc+frame synchronizer. Timebase correction is mostly about detecting a VHS versus Broadcast signal to compensate for the noisy head switching at the beginning and ending of a field of video to prevent 'flag waving or tearing' at the top or bottom of the screen. These are often hidden by bezels on CRT monitors as they are in the overscan region of the picture but become visible when watching the video in a video preview or playback on a digital monitor. 

Swimming or variable length drift between horizontal sweep lines must also be corrected by devices capable of detecting this and reformatting the time of the lines relative to each other through a process known as "Velocity" compensation to square up and make uniform the stack of horizontal lines from top to bottom in a field and frame.

Frame synchronization is more about coping with a damaged or incomplete field or frame of video and automatic recovery such that it always delivers a 'standard' frame rate. Whether it does that by repeating a frame to make up for the unusable remnants, briefly inserts a black, blue or blank frame into the stream, and whether it attempts to simultaneously throw out audio samples to keep audio and video in lock step.. are all design decisions or settings options unique to the specific frame sync being used.

DV bridges could react to a loss of signal, by aborting or end a capture, ending and staring a new one as soon as a signal becomes available again, or pausing a capture and requiring manual intervention by a human being. Some would even make a time code note so these could be revisited and addressed later.

Firewire DVRs were not common in the United States, LG and Samsung provided a couple examples, but by then TiVo, EyeTV and Windows Media Center had claimed the larger share of the public business. Formac (UK), I-O Data (Japan), and EyeTV(mostly EU countries) did dabble in Firewire Tuners relegating the DVR piece to software on a connected PC but for the most part people were largely not aware of their existence.


7/21/2023

Playing audio from Adobe Audition 4.0 - Win7 a "better way"

Found this "related" work around for later versions, and it makes a little sense to me now.

Normally I disable the built-in Realtek speaker and microphone device in Playback and Record sound devices, and leave only the Bluetooth headphones and Bluetooth headset [enabled].

Blueooth Headphones usually (do not) have an audio Input microphone, but Adobe Audition tries to set that as the Input.. the Audio Hardware drop down doesn't list any other possible Input source because I have the built-in Realtek audio source disabled.

Bluetooth Headsets are usually for gaming and have a mono or stereo Mic Input .. and thats probably why that work around works. Audible is able to sort or detect both and things just work. I would suppose something goes wrong when trying to open the Bluetooth Headphones and only one stream, the Input is silent and it fails silently to figure out how to deal with them as an Output.

Simply, with the Realtek built-in audio Source set as the Input, and the Bluetooth Headphones set as the Output under Audio Hardware.. everything starts working properly.. and the Bluetooth Headphones are playing back in high quality with few to no dropouts.

Headset mode has limited Bluetooth bandwidth, and part of that is reserved for the Input channel, so dropouts and quality suffers quite a bit with Robot'ing frequently occuring.. but with the full Bluetooth bandwidth available when using Bluetooth Headphones mode.. there are no dropouts.. and no Robot'ing.

Smooth as silk.

Playing audio from Adobe Audition 4.0 - Through Bluetooth Headphones while in the Editor

Adobe Audition 4.0 is part of Adobe Premiere Pro CS5.5 - if you open an audio file and hit the playback button in Windows 7 the Levels will move and it will appear to playback, but no audio will be heard from the Bluetooth connected headphones.

You can make the audio playback by manually changing the Edit > Preferences > Audio Hardware

Default Output: 

< from: Bluetooth Headphones (2- Bluetooth Audio) >

< to: Bluetooth Headset (2-Bluetooth Audio) >

This will trigger a Pop up warning that channel mappings many change, and ask for a confirmation to proceed.

Headphones are normally preferred for audio quality in the playback, but for some reason they do not produce an error, but also do not produce any audio.

Headset "mode" is lower quality and has more dropouts, but at least it works.

Any editing of the audio file will still proceed and save in top quality, and will playback in top quality from other audio playback programs over the normal Bluetooth Headphones setting for the overall system.

I don't pretend to understand what is going on.. but this is a minimal work-around.

7/19/2023

Saving Emails from Thunderbird - That Open in Win7 Preview Pane Complete

You can Re-Save a Blocked Email, or Email that opens but does not display some Inline Images in the Windows 7 Preview Pane, using IE-11 as an (.mht) Web Page Complete File version.. and it "Will" open with the Inline Images Unblocked.

This seems to be 'Unique' to the file format IE-11 on Win7 saves it as, saving as an HTML file with Attachments or using some other Browsers Save As complete does not work.

I assume back in the Day, Microsoft made sure that IE-11 Save As would in some way specially prepare the html in .mht files that it alone generated, that would by-pass the Windows 7 Preview Pane filter controls.

I did try Unblocking using Windows Defender exceptions or turning that off, but it did not Unblock the Inline Images.

It might work all the way up to Win11 or using IE-11 to Re-Save or Preprocess since Microsoft tends to  not deprecate old code paths in new software

IE has of course been deprecated itself these days with the new Chrome based Bing browser. But you may be able to get IE-11 in a VM or some other place and use it simply as a tool for re-processing unviewable files.


5/31/2023

Expression Encoder Pro 4 from (without Codecs) to fully (with Codecs)

Its been a long time since Microsoft abandoned Expression Encoder 4 Pro. 

And I have read horror stories about their license activation system.

But confirming, today 05/31/2023, you can still Activate, and that the Install of a Retail Copy will (convincingly) say "without codecs" until you manually "Change the Product Key" it won't prompt you during install, it will install in "without codecs" mode only first.. and it will say Licensed, but until you enter / change the Product Key to exactly the one for your copy of the Product and Activate.. it will not go into "with codec" mode.

You also only get two Activations before the Key is no longer usable, so DO NOT Activate the first time before changing the Product Key.

The default install is to go into a mode it says blatantly is "without codecs" after initial install.. when its properly changed with a valid Product Key and Activated it does not say "with codecs" its just blank.

From the Expression Help > About menu option, from a machine Simply installed, there was "No" prompting for a Product Key.


The only way you have to know its now in with codecs mode, is to create a new project, add some source, and try to change to MP4 format and your presented with the H.264 options and nothing stops you from Encoding.. its the absence of problems that confirms its fully Enabled and Activated, not simply "without codecs" and activated and therefore crippled.

 
From the Expression Help > About menu option, from a machine Simply installed, there was "No" prompting for a Product Key. (AND) then the Help > Enter Product Key and Activate was used and it "removed" the (without Codecs) message that was originally there and the MP4 and H.264 Encoding options started appearing, and worked.

This screenshot is from a different machine in which it had the "without codecs" message and a Product Key was then entered and Activated. I'm not screenshot'ting from the exact same machine both ways since removing and Re-Activating will burn a usage of the key. Discovering the issue was rather non-intuitive and stumbled upon and I don't want to upset the current system until a Full Backup. 

My recollection is a tiny checkbox below the field for entering the Product key that says  "Activate Product Now" and its pre-checked.. so as part of Entering the Product Key and hitting the [Continue] button, it will "also" contact Microsoft to attempt to "Activate" the Product, success will change the About screen to remove the "(without codecs) message and MP4 and H.264 Encoding will now be possible. This should also unlock the MPEG2 and other codecs available for import.

When I think about it (Activate) should be thought about as a synonym for (Unlock) to enable features in this product.

There is no (Deactivate) function to save an Activation so you can re-Activate on a different system, the Key usage is "burned" which is very sad. Most of the rest of the Industry supported "De-Activations" but apparently this Product line or Microsoft had not got to that level of maturity by the time the Product was discontinued.




This was from about they years 2010, with products new to CLR or "Managed Code" and Bill Gates edict to license and activate everything.. so it was awash with confusion.. and they were laying off "legacy" talent and constantly competing with incumbents like Apple and Adobe for tool market share, including with Opensource alternatives.

So they didn't really have any guard rails and they weren't listening to the general public and had their own personal problems internally.. (I think) the effect and intent was all versions (did) install the Codecs, but they were by default (crippled or "de-activated") and the original intent was to make Buying online and (enabling) a simple action of entering a Purchased Product Key from a website, the effect would have been instant and no re-installation would have been required.. but the behavior of this workflow was massively confusing and hard to troubleshoot.. since they were striving for "Customer Self-Service and checkout.. but it rather backfired traumatically and probably doomed the product line.

Other vendors adopted a download the "Full Featured Copy" with codecs and patch or add-on the necessary Codecs after.. and that became the "normal behavior" but this was so alien and ad-hoc it made the experience simply too foreign and difficult to support.. every problem or interpretation took human intervention.. which could not scale.

And instead of making it easy to upgrade hardware or move or reinstall a Copy from machine to machine, they "burned" Product Keys / License keys after two uses.. making it further difficult to support, and requiring human intervention "again".. it was a textbook demonstration of a product role out disaster.

Sure that made it difficult to "pirate" but it also made it "tossable" and "never use again" non-repeat business.. the chaos that was occurring at the time and the brain drain and decision maker drain and people laid off made it easier to just shut it all down.. and that appears to be what happened.

Another thought from the year 2023 is in an effort to safe guard against malware and virus infection they constantly kept updating and upgrading the Windows 7 kernel and Signing certificates for accepting and installing drivers and application software, these are also used to validate Activation mechanisms when visiting Microsoft sites.. SHA1 to SHA2 that sort of thing.. at least Windows 7 has to be updated sufficient to be able to communicate with the activation servers in order to activate. Its not that the services have been shutdown, its that the certificates for communications are out of date on the client side of the communications.


5/11/2023

Starlink App for iOS gets remote control VPN

The title might not be quite accurate, but the Behavior is the same.

When your away from home, or not connected to your homebase Starlink network, you can "still" use the Starlink App "remotely" to connect back to your homebase and control your Starlink router.

I have mine set to only fire up at certain times of the day rather than run all night long burning up kilowatts when I'm not there or I'm asleep. 100 watts can add up over time, and I can failover to a cheaper backup provider for when I decide to pause service in RV mode.

The app doesn't "expose" this capability right away, its not intuitive. Perhaps they will update the online docs later.


Tapping on the "word" > NOVUS (cloudy symbol)

Produces a new set of options;


Notice how option one, the Top - has a "go to" > arrow 

Notice how option two, the Bottom - has a "ready to connect" > checkmark

 

Top or "Local" assumes you will shortly be connecting to a Local Wifi to find your Starlink router.

Bottom or "Remote" knows your far from home, but is ready to connect back over the Internet (cloud) to your homebase.. its "VPN" ready since your not at home.

But in both cases I have (red dots) because my Starlink router is currently {powered down} based on its offline power saving mode. Its not really offline per sec.. its "sleeping" and therefore not communicating. It should be waking up in about one hour and then the [Remote] option should go (green dot) and be ready for a virtual private network remote session to update and configure its settings.

This is my best guess at this time.

Its a powerful option if correct.

I began investingating this path due to finding a recent blog entry here;

https://www.starlinkhardware.com/how-to-remotely-connect-to-starlink-app/

Update:

 


 

I was able to remotely connect, it did go (green dot) but the Sleep Schedule setting is not Adjustable remotely, you can't even disable it. Currently it reports you must be connected locally in order to edit the sleep schedule.. which points to this not being  a comprehensive VPN like solution for remote management, rather its a targeted remote command system, which probably depends on some sort of bespoken API based on REST or some other post apocalyptic , web 2.0 protocol.




4/29/2023

TDK indiCapture VC-2600 UE drivers and insides

I happened across this TDK IndiCapture with driver and software disk today. Curious I took a look inside and at the device drivers.

This comes from around the year 2002-2004 when video capture from camcorders, and later television became popular.

 



The device driver hints that its actually based on a Lumanate / Emuzed / Bali USB device which uses the Broadcom KFir-II hardware compression chip.

TDK 2002

IndiAvIn.inf

HKLM,Software\Sonic\OEM\Capture,"BaliDevice",,%IndiAvIn.DeviceDesc%


;;; ---------------------------- REGISTER EMUZED DIRECTSHOW FILTERS
[EzdFilters.AddReg]
HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce,"EzIKfir.ax",,"RunDll32.exe %11%\EzdReg32.dll,RegisterControl %11%\EzIKfir.ax"
HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce,"EzdFWrtr.ax",,"RunDll32.exe %11%\EzdReg32.dll,RegisterControl %11%\EzdFWrtr.ax"
HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce,"EzdFCtrl.ax",,"RunDll32.exe %11%\EzdReg32.dll,RegisterControl %11%\EzdFCtrl.ax"

;----------------
; Localizable
;----------------
STRING.PINNAME_MPEG_OUT       = "MPEG Out"

IndiAvIn.InstallationDir    = "TDK INDI AV-IN USB Drivers"
IndiAvIn.Provider              = "TDK Electronics Corp."
IndiAvIn.Manufacturer      = "TDK Electronics Corp."
IndiAvIn.DeviceDesc        = "TDK INDI AV-IN USB Device"
IndiAvIn.Crossbar             = "TDK INDI AV-IN USB Crossbar"

The TDK Suite disc is in BIN CUE format but easily converts to .ISO format

It includes ArcSoft ShowBiz 1.2

Since it is designed for Windows XP only with a 32 bit device driver, its probably not of as much interest today, but the KFir-II chipset was often used in Rovi Tivo devices of that day and of fairly good quality.

The Moonsoon capture utility SnappySoft might also work with it.. and since SnappySoft works with many MPEG sources of the day, PowerDirector 8,9,10 may also be a viable capture software.

The primary Video decoder chip was the Thompson / Philips / NXP SAA7115 although the device driver clearly suggests its the SAA7114

;
; SAA7114
;
HKR,SAA7114,"DeviceAddress",0x10001, 42,00,00,00
;HKR,SAA7114,"CrystalFrequencyKHz",0x10001, 24576 ; 24.576
HKR,SAA7114,"CrystalFrequencyKHz",0x10001, 32110 ; 32.11



The SAA7115 also supported "frame locked" audio sampling which suggests it discarded audio samples for which there was no frame data, and thus avoided loosing synchronization between audio and video where frames were lost.


 Versions of the Bali USB appeared as Pinnacle / Avid bundles and as combo video capture and NTSC / PAL TV tuner capture devices.



[IndiAvIn.Device]
%IndiAvIn.DeviceDesc%=IndiAvIn.Install,USB\VID_04BF&PID_0A28

or just

USB VID 04BF PID 0A28

I believe there was a slight update that TDK made available for ShowBiz 1.2 but it was never archived and did not seem related to the device driver.

The design and implementation of the device driver is extremely simple and minimal. and being associated with Luminate / Emuzed it was probably fairly stable.. L & E went on to manufacture and import devices for Dell Computers.. and their selection as a provider probably speaks to their costs, simplicity and stability compared to the competition at the time.

The original MSRP was at the time I think $199 .. there is no equating that to today, in todays dollars even with inflation adjusted figures.. since the whole process of video capture has changed substantially.