April 19, 2024

AdBlocker Ultimate Limited to Working with iPad Safari, not Chrome

AdBlocker Ultimate Home Page Screenshot(Mar. 29, 2019) I was annoyed having recent online purchases and product viewing activity result in stalking-like targeted advertising while surfing the web.

I typically use Google Chrome on a 2019 iPad and have grown increasingly discussed by the targeted advertising layered on every page I viewed. Tantamount to stalking like behavior.

Frustrated, I quickly searched the Apple store and found a reasonably interesting prospective app called AdBlocker Ultimate.

After downloading and installing it, I followed the instructions to enable it.

I would soon realize, however, there would be no options to enable the App to work with Google Chrome, my preferred iPad browser app.

Well that sucked. 

Continuing on. After enabling the app, I reluctantly opened Safari to see how AdBlocker Ultimate worked. Well, it actually did work. Only in Safar, however.AdBlocker Ultimate webpage before

Interestly, it seemed to block the adds I have grown to hate. Instead of the adds, white  space is shown. Better than nothing for now.

Wanting the app to work in Chrome, I scrolled down into the App configuration area and clicked on the Google Chrome app icon.

AdBlocker Ultimate webpage with blocked advertisements resulting in white space areas.There, however, were no settings to enable AdBlocker Ultimate in Chrome.

Looking at this app’s description in the Apple Apps store, I discovered there was no language describing which browsers it works with. This was an indirect confirmation to me that AdBlocker Ultimate was not as diversified as I thought to potentially be that one-stop add-blocker for all my iPad browsing.
 
Apps normally highlight key functionality in their descriptions for marketing purposes. AdBlocker Ultimate did not. In fact, there is no mention of any browser compatibility mentioned in the description.
 
Unless otherwise determined, this app appears designed to work with Apple safari and does not integrate with the Google Chrome browser App on an iPad.
 
Update pending.

Lucky Clan’s Videon Degrades Video Bit Rate During Trim and Split Editing

 
[pe2-image src=”http://lh3.googleusercontent.com/-NY0olK17Wak/VmoqXJiOUkI/AAAAAAAAAUM/K9BAnGg7e_Y/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252014%252520Videon%252520Icon%25252002_800xAUTO.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226836011977953858″ caption=”Lucky Clan’s Videon logo. Videon Bit Rate Reduction Screenshot 14 Videon Icon 02_800xAUTO Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 14 Videon Icon 02_800xAUTO.JPG” ]During a recent project, I discovered that Videon iPhone video application degrades the video bit rate from that of a source video clip during split and trim functions.

Gravitas

Over the past year I’ve been fortunate to have discovered and use Lucky Clan’s Videon iPhone video recorder and editing app as a goto app for recording many of my projects.

Videon had a far superior video image quality, provided manual control of exposure and focus, and contained powerful trim and split editing features which saved time by allowing the use of the iPhone to conduct initial post production tasks portably and before the real work took place behind a desk at the editing workstation.

I recently had to abandon Videon for the video recording portion of my projects in order to use DSLR video cameras to take advantage of their refined manual settings control and interchangeable lens options.

One feature, however, I regret not having at my finger tips. That is Videon’s simple and highly efficient trim and split feature.

[pe2-image src=”http://lh3.googleusercontent.com/-NfjYdnbzuVA/VmoqUIjyCmI/AAAAAAAAAT0/Y4a4WKukNH0/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252010%252520Videon%252520Trim%25252002_800xAUTO.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226835960176446050″ caption=”Lucky Clan's Videon iPhone app's user GUI during splitting operation. Multiple split points are able to be selected resulting in a batched split operation capability, streamlining workflow. However, the splitting and trimming process results in a 2.7 times bit rate quality reduction. Videon Bit Rate Reduction Screenshot 10 Videon Trim 02_800xAUTO Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 10 Videon Trim 02_800xAUTO.JPG” ]Videon’s interface is far superior and simple to use over other top iPhone video recording and editing apps.

The manner in which Videon allows the user to set multiple split points on a source video clip, before sending it off for splitting, saves time and acts like a batch splitting tool.

Videon’s split and trim tools are intuitive, and are simple to use providing frame accurate placement of in and out points.

Videon further incorporated a logical renaming scheme when producing the resulting sub-clips after a trim or split procedure. The created sub-clips are subsequently chronologically numbered with an extension to the source video file name.

This keeps the new sub-clips closely associated with the original file name so they don’t loose their place in the directory listing. Unlike some iPhone video editing apps which sometimes merely create new file names added to the last name or number on the device which creates chaos and drastically reduces work-flow efficiency.

Trying to Keep Videon in the Workflow

Without fully abandoning Videon from my production workflow, I found I was able to copy my source files recorded using a DSLR camera into the root working directory of Videon on the iPhone. This requires a hack these days, given Apple’s insistence to prevent users from accessing an app’s directory area, forcing the user to resort to clunky iTunes in an attempt to quickly add or copy files from these areas on the iPhone or iPad.

Once the prospective files needing to be trimmed or split are in the apps work director on the device, they will appear much the same way as any file created by the app, in this case Videon. The files can then be freely worked on using Videon for splitting or trimming.

Tricky File Naming Scheme

Working on video clips in Videon’s working directory on the iPhone was a bit tricky at first.

I had to first figure out compatible names for my source files before copying them to the apps working directory. If named incorrectly the app may not see them, or, when creating sub-clips after a trimming or splitting operation, as in the case of Videon, it may truncate the file names when characters such as the underscore “_” are encountered.

If a file was being worked on by Videon which contained an underscore in its name, the resulting sub-clips would be renamed by truncating from the underscore and by adding the three digit file name extension (i.e., 001, 002, 003, etc.).

For instance, if a source clip named 20151210_1500_001.mov was copied to the working directory of Videon on the iPhone. Then, if the clip underwent a trim or split procedure in Videon, Videon would look for the first underscore after 20151210_, and then start its chronological renaming scheme at that point, naming the new sub-clips as 20151210_001, _002, and so on.

The way around this is to remove all the underscores from the source file names to 2015121015001.mov. Then, when Videon goes to apply the renaming scheme to the clip after a trim or split procedure, it would rename the sub-clips to 201512101500001_001, _002, and so on. Keeping the clips in their respective order in overall file name scheme.

MP4 vs. MOV Renaming Trick

I also found out that if you rename a source file clip originally recorded in .MP4 format to .mov, Videon would find and work with the file without any problems. Afterward, the file could then be copied from the Videon working directory and later renamed back to its original *.mp4 name as needed.

Future LuckyClan Updates Unknown

All said and done, it is most desirable to keep the portability and time saving characteristics of using Videon and the iPhone to work on mundane tasks such as trimming and splitting source video clips to be later used at the editing workstation. However, given the revelation that Videon reduces the bit rate of the source video clip by as much and 2.7 times is a critical quality control issue of concern.

Shooting video using a DSLR camera is already handicapped in terms of image quality by the limited amounts of stops of light it is capable of recording. So every little “bit” helps. And a reduction as much as 2.7 times in the bit rate is not something to ignore.

Developer Awareness

Before writing this article, LuckyClan.com was emailed advising them of the issue regarding the underscore “_” file naming truncating issue, as well as the source video bit rate reduction issue during Videon’s trim and split procedures. Unfortunately, Lucky Clan did not respond by the time this article was published, so they were not able to shed any light on the issues.

[pe2-image src=”http://lh3.googleusercontent.com/-OAkdE1sWCuE/VmoqPuHNAfI/AAAAAAAAATU/iPGN_lA5EIY/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252006%252520Videon%252520Apple%252520Store%252520v2_800xAUTO.11%252520Nov%2525208%2525202014%252520Info.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226835884357779954″ caption=”Lucky Clan's Videon Apple Store iPhone app listing showing last update over one year ago, Nov. 8, 2014 version 2.11. Videon Bit Rate Reduction Screenshot 06 Videon Apple Store v2_800xAUTO.11 Nov 8 2014 Info Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 06 Videon Apple Store v2_800xAUTO.11 Nov 8 2014 Info.JPG” ]In any event, Lucky Clan has been made aware of this issue, and hopefully will find it noteworthy enough to include any improvements and modifications along these lines in a future Videon update. Consequently, Lucky Clan, at the time of the writing of this article, had not updated the Videon app since November 8, 2014, so it may be time for an update from its current version 2.11 (Rel. Nov. 8, 2014).

Case Scenario

All that said and done, lets look at the specific case scenario and resulting degradation by Videon after splitting a source video clip from a modified Nikon D800 recording at 1080p 24fps at 36Mbps.

After the clips was recording by the D800, it was then transferred to Videon’s video clip working directory.

Videon was then opened up, and the clip was retrieved where it underwent either a trim or spit procedure.

The resulting sub-clips were then copied back to the editing computer and a media report was conducted on both the source and sub-clip files revealing the following results.

Videon source clip:
37.1Mbps (1920x1080p (16:9), at 23.976 fps
AVC (High@L4.0)(CABAC/2 Ref Frames)
(1,536 Kbps, 48.KHz, 16 bits, 2 channels, PCM (Little/Signed)

Videon Sub-clip:
13.7Mbps (1920x1080p (16:9), at 23.976 fps,
AVC (High@L4.0)(CABAC/2 Ref Frames)
(256 Kbps, 44.1.KHz, 2 channels, AAC (LC)

[pe2-image src=”http://lh3.googleusercontent.com/-ofM8R01aeKY/VmoqN2KO-YI/AAAAAAAAATE/X42S4hgA1Ss/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252004%252520Videon%252520Clip%252520Info_800xAUTO.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226835852158237058″ caption=”Lucky Clan's Videon trimmed video specifications after splitting. Shows a 2.7 times reduction in video bit rate and an audio quality reduction after splitting. Videon Bit Rate Reduction Screenshot 04 Videon Clip Info_800xAUTO Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 04 Videon Clip Info_800xAUTO.JPG” ]

Simple division between 37.1Mbps and 13.7Mbps, the difference between the source and resultant split sub-clip, results in a 2.7 times reduction in quality. So again, that is a 2.7 times less video bit rate density than the original source clip bit rate which Videon started off with before the split.

To explore this issue further, I then tested another iPhone video and editing app, FilMic Pro on the same clip.

After copying the editing the source clip in the same manner done using Videon, it was discovered that FilMic Pro had little to no degradation applied to the video bit rate of the resulting sub-clips.

FilMic Pro source clip:
35.4 Mbps (1920x1080p (16:9), at 23.976 fps,
AVC (High@L4.0)(CABAC/2 Ref Frames)
(1,536 Kbps, 48.0 KHz, 16 bits, 2 channels, PCM (Little/Signed)

FilMic Pro Sub-clip:
32.7 Mbps (1920x1080p (16:9), at 23.976 fps,
AVC (High@L4.0)(CABAC/2 Ref Frames)
(1,536 Kbps, 48.0 KHz, 16 bits, 2 channels, PCM (Little/Signed)

[pe2-image src=”http://lh3.googleusercontent.com/-lGPiaNkYLK8/VmoqWOCWJBI/AAAAAAAAAUE/SgcX0jao83M/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252013%252520Filmic%252520Pro%252520Logo_800xAUTO.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226835996006556690″ caption=”FiLMic Pro logo. Videon Bit Rate Reduction Screenshot 13 Filmic Pro Logo_800xAUTO Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 13 Filmic Pro Logo_800xAUTO.JPG” ]There is negligible difference here in the bit rate. Also notice that FilMic Pro did not modify the audio quality either.

Spitting and Trimming

Using FilMic Pro for basic trimming and splitting of large extraneous clips resulting from a video production was definitely not as easy nor ergonomic as Videon.

[pe2-image src=”http://lh3.googleusercontent.com/-lHouSk3e7fE/VmoqSEOQPBI/AAAAAAAAATk/SjfiEblvuT8/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252008%252520FilMic%252520Pro%252520Trim%25252002_800xAUTO.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226835924652669970″ caption=”FiLMic Pro's user GUI while trimming a selected video. User must perform repeated trims individually when seeking to chop of the source clip. Videon Bit Rate Reduction Screenshot 08 FilMic Pro Trim 02_800xAUTO Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 08 FilMic Pro Trim 02_800xAUTO.JPG” ]FilMic Pro’s trim only interface is clunky to say the least. And FilMic Pro did not seem to offer a split feature. The user is limited to one instance of a trim to the source clip which was then saved as a sub-clip. Then next trim would have to be “reloaded” and done again along another point on the source clip. Wash, rinse and repeat.

On the other hand, Videon offers a multiple point designated split feature which allows the user to designate multiple split points within a clip through the designation of tick marks.

[pe2-image src=”http://lh3.googleusercontent.com/-NfjYdnbzuVA/VmoqUIjyCmI/AAAAAAAAAT0/Y4a4WKukNH0/s144-c-o/Videon%252520Bit%252520Rate%252520Reduction%252520Screenshot%25252010%252520Videon%252520Trim%25252002_800xAUTO.JPG” href=”https://picasaweb.google.com/106423603886853212149/VideonTrimSplitVideoBitRateDegrading#6226835960176446050″ caption=”Lucky Clan's Videon iPhone app's user GUI during splitting operation. Multiple split points are able to be selected resulting in a batched split operation capability, streamlining workflow. However, the splitting and trimming process results in a 2.7 times bit rate quality reduction. Videon Bit Rate Reduction Screenshot 10 Videon Trim 02_800xAUTO Media by MikesMultiMedia.com” type=”image” alt=”Videon Bit Rate Reduction Screenshot 10 Videon Trim 02_800xAUTO.JPG” ]The user simply scrubs through the source clip, placing split point ticks along the time line of the clip. Then, when ready, the ticked up clip is sent to the splitting process resulting in multiple sub-clips being generated for each of the designated split points. With the option to preserve the original source clip of course, or not, user specified.

I recommend preserving the source slip, because sometimes there is a system memory log jam which may corrupt long video editing operations.

So to play it safe, preserve the original source clip until the split or trim operation has been completed successfully.

Sub-Clip Naming Conventions

Each of the sub-clips generated by Videon’s split feature are named with chronological extensions added to the original source file name. This allowed the resulting sub-clips to say in chronological order to its source file, if preserved. Or at the least, continue on in the master directory list of source files.

Lucky Clan’s Future Development of Videon Uncertain

It is uncertain if Lucky Clan will modify their Video product to address this degradation in video bit rate issue when their Videon app performs split and trim procedures on a source clip.

There last Videon update was over a year ago, and perhaps having been made aware of this issue as a result of this article, they may seek to include an update in the near future to address the bit rate reduction issue.

It seems like it would be simple fix, and any current bit rate modifications currently being applied to split clips may merely be a proposed default setting used in the programing of Videon.

A proposal would be to have Videon inspect the source clip’s format and quality settings, save them to a variable, and apply them when rendering any sub-clips resulting from spitting and trim operations.

FPS and Bit Rate Configurability

Videon also does not provide refined configurability of its bit rate settings in its app. It simply allows the user to use percentage based settings (i.e., 100%, 200% quality, etc.). This is consistent to the theory that the bit rate issue was not given full granular design which given today’s iPhone capabilities, with 2K, 3K and 4K offerings, can’t be overlooked.

Especially when other iPhone video recording apps such as FilMic Pro, though limited in its ergonomic functionality, offer more refined configuration menus options. Additionally, FilMic Pro does not degrade the bit rate quality of its source clips when conducting trim operations.

(Screen shots to be uploaded at a later time.)

Screenshot Gallery:

[pe2-gallery album=”http://picasaweb.google.com/data/feed/base/user/106423603886853212149/albumid/6226835783110846897?alt=rss&hl=en_US&kind=photo” ]

Fixing Vegas Pro 13 Initializing GPU-accelerated video processing Crash

Today I resolved a Sony Vegas Pro 13 startup crash problem which started happening after I upgrading my HP DV6-6190US Pavilion laptop’s operating system from WIndows 7 Home Premium x64 to Windows 10 Home x64.

The purpose of the Windows 10 install onto the older HP DV6 6190US system was to test Windows 10″s compatibility with my applications software before upgrading my main computer, a MacBook Pro A1398 15 inch system currently running Windows 8.1 under Bootcamp, to Windows 10.

Fortunately I was able to use the HP DV6 system as a test system before attempting the Windows 10 upgrade on my primary MacBook Pro system. And given the degree of problems I experienced just with getting one of my core video editing programs to work, that is Sony Vegas Pro 13, using a test system turned out to be a beneficial situation  given the problems I encounter getting it to run properly.

So let’s get the specifications out of the way for my test system as follows which has recently been upgraded from Windows 7 Home Premium to Windows 10. Its specifications are and what Vegas Pro 13 was installed onto are:

Windows 10 Home x64
HP DV6-6190US
2nd generation Intel Core i7-2630QM Processor 2.00GHz with Turbo Boost Technology up to 2.90 GHz
8GB DDR3 System Memory (2 DIMM)
Radeon HD 6770M
15.6″ diagonal Full High Definition HP Anti-glare LED Display (1920 x 1080)
750GB (7200RPM)
Digital Media Card Reader for Secure Digital and Multimedia cards
2 SuperSpeed USB 3.0
2 Universal Serial Bus (USB) 2.0

Just for clarification, Vegas Pro 13 build 290 was previously installed and working fine on the HP DV6-6190US system. However, I had to install a fresh basic copy of Windows 7 onto it during the Windows 10 upgrade process.

You see, the only way you get Windows 10 to install for free under Microsoft’s free upgrade scheme is for users of valid activated Windows 7  and 8.1 to perform an “upgrade” and not a “fresh” install of Windows 10 onto their systems.

Because I first tried installing Windows 10 onto the system as a fresh clean install, I later found out that the subsequent activation process would reject my old Windows 7 key.

This is probably where my Windows 10 install journey really started. That is, to simply get it installed and activated properly in the first place.

So even before encountering this recent Vegas Pro 13 startup crash problem, many hours have already been spent on this journey into Windows 10.

As a side note, and to Microsoft”s credit, with respect to the proper way to install Windows 10 onto your system in order to qualify for the free upgrade offer, both types of installs worked seamlessly.

The upgrade, which consequently saves all your applications, and the  fresh install procedures worked flawlessly and confidently.

To even get further off topic. The process of restoring my DV6-6190US system back to a fully functional, activated Windows 7 system was is itself another meticulous process. especially when HP (i.e., Hewlett Packard), did not include original install disks in the box when the system was first purchased. Don’t worry, you can still get the disks but of course for a price. I think HP tried reducing customer resentment by calling these disks they will now sell you a “Recovery Kit” instead of “original install disks which is really what they are.

One thing I will add when thinking about recovering your system back to Windows 7 so you can then try installing Windows 10 as an upgrade vs. a fresh install. Remember, you will also need all the special, and now mostly outdated device drivers for each piece of hardware on your system.

simply finding a clean copy of Windows 7 Home Premium x64 bit is not enough. As I do apply found out.

Again, HP will generously provide these drivers to you free of charge online. But you will have to go to their product page for your system and download them one by one. But here is the catch, how do you get the drivers installed onto a naked HP system with a generic copy of Windows 7 installed? Remember, without the hardware drivers, the disk drive, thumb drive, SD card port, and most severely, the network adapters, both of them, the wireless and the LAN ports all don’t work after simply installing a naked copy of Windows 7 onto a system.

Lets just say several hours were spent slicing and dicing ways to get the drivers installed without any working hardware except the CD-ROM drive. This is where creative trouble shooting kicks in. I have yet to have everything work as expected when performing a high level procedure on a system. And installing Windows 10, free or not, drew upon my many years of trouble shooting experience to get me this far.

I think Microsoft anticipated users would try to install Windows 10 as a fresh install vs. an upgrade install. Then, when those users saw the daunting task of having to reinstall their old Windows 7 operating system back onto there systems, without the original install disks and, without the patience, will power and determination to weather the re installation storm, paying the $112 or a Windows 10 Home key makes perfect sense. Especially when your system is directing you to the Microsoft store immediately upon notifying you your old key is not valid, and you need to buy a new one. This all the while your system is smiling at you with a fully functioning Windows 10 GUI.

if you ask me, Microsoft did the bean counting and banked on a high percent of people installing their advertised as “free upgrade” as a fresh install. And like any sane person would, just fork over the $112 and be done with it. It’s inconceivable anyone in there right mind would op to ensue the painstaking task to recover their system back to Windows 7 in order to then properly “upgrade” to Windows 10 all to save $112.

Unless your a techno geek like me.

I”m waiting for the class action lawsuit to be filled against Mucrosoft for unfair and deceptive trade practices with their “upgrade for free” arresting to entice users to own load and install Windows 10.

Time will tell.

Anyway, where were we?

Oh yea, why I had to reinstall Vegas Pro 13 in the first place. That is why. I had to reinstall it because I first wiped the system when installing Windows 10 as a fresh install.

The clean install was done primarily to avoid any remnants of the old Windows 7 operating system contaminating the “new and improved” Windows 10 system. Boy, that was a time consuming and educational experience.

Okay, back on track. Oh yea, the fix to the “Vegas Pro 13 crashing on startup after installing on Windows 10” problem.

The fix:

Good news is that I finally got Vegas Pro 13 build 453 to start in Windows 10 today after a few hours of tinkering and troubleshooting.

What DID NOT work:

1. Installing the latest build Sony Vegas Pro 13 build 453. This did not work. Note: I was previously running build 290;

2. Disabling the AMD catalyst manager from starting. Or actually uninstalling it completely; and

3. Going directly to the AMD website and downloading and installing the latest AMD catalyst manager driver for my Radeon 6770M graphic card.

What DID work:

1. Going into device manager and locating the graphics adapter driver, which was set, by the Windows 10 install procedure, to a Intel(R) HD Graphics Family adapter and driver designation, and completely uninstalling it. The thinking here was that the Intel(R) HD Graphics Family graphics adapter designation was preventing the actual AMD Radeon HD 6700M Series adapter and software from designated and installed respectively.

2. Upon restart, my video resolutions were not set to optimum setting, which is 1920 x 1080P, but what the basic driver was able to handle. What is important to note is that the AMD Radeon HD 6700M Series adapter was not showing in the Device Manager but with errors (i.e., icon had an “!” over it). This still was good news, because it confirmed the theory that the Intel(R) HD Graphics Family designation was some how preventing the actual Radeon adapter and software drivers from being recognized and designated.

Note: I think it’s important to note, that the Device Manager properties window reporting that the best driver was still in use while the Intel(R) HD Graphics Family driver was designated. I say this because this is a false negative. That is, a premature determination could be that the the graphics adapter settings are okay, and the problem must lie elsewhere (i.e., with the Song Vegas Pro 13 software). Nonetheless, in this case, the Intel(R) HD Graphics Family designation, confirmed by its removal, was causing Vegas Pro 13 to not start up..

This does not necessarily mean that Windows 10 is the culprit either. It did its best to determine the best graphics adapter settings suitable to run the machine, and not necessarily the Sony Vegas 13 software.

Now that the primary problem has been resolved, that is to get Vegas Pro 13 to complete its start up process, I now have to find out why, even when latest AMD catalyst manager and the AMD Radeon HD 6700M Series display adapter have been installed and designated, why the Device Manager is reporting an error (i.e., “Windows has stopped this device because it has reported problems. (Code 43) over the AMD Radeon HD 6700M Series‘ icon.

While in this error state, the system is relying on the Microsoft Basic Display Adapter to determine the resolution configuration which has a maximum depth of 1280 x 1024.

In summary, it turns out that the “Initializing GPU-accelerated video processing” crash experienced by Sony Vegas Pro 13 during start up problem is not necessarily a Sony Vegas Pro 13 problem.

If a finger has to be pointed, it should start to be pointed at AMD, or at AMD and Microsoft at the same time. Why? Because even after loading its latest driver software into Windows 10, it reports the error indicated above.

I would add, this troubleshooting can say that the problem does not reside in the either the Vegas 13 build 290, or build 453 software versions respectively either. Or at least with the test system this matter pertains to.

Now that Vegas Pro 13 has successfully started up under Windows 10, the next task is to figure out:

  1. Why the AMD Radeon HD 6700M Series graphics adapter, even with AMD’s latest driver software installed, is reporting an error in Windows’ Device Manager; and
  2. Ultimately to get the system to be able to configure itself to its maximum graphics adapter resolution.

 

For screen shots of this ordeal, see my post on CreativeCow below:

Vegas Pro 13 Initializing GPU-accelerated video processing CRASH RESOLVED! (Windows 10)