MikesMultiMedia

Bridge Illumination Project – Started, notes

October 28, 2016 by MikesMultiMedia Leave a Comment

Scenario:

Historic bridge sits without lights at one side of the bridge. A piece of it was left for historic purposes.

This section, about a football field long, and about 30 feet wide, is unlit and only receives ambient light from parking lot lights and lights which shine down on it from the replacement bridge which towers above it nearby.

Goal is to illuminate the intricate steal structure of the bridge using various lighting techniques which yield a desired result. Currently experimenting with portable strobe flashes, and exposures which are below 30 seconds. Light painting is also being used at this time.

It is not sought to create a composite or HDR illustration. The final shot will be obtained in camera during a single exposure.

Project Log:

Log:

(10-28-2016 21:00)

Initial survey and test setups of portable flashes to light the bridge.

(10-31-2016 23:00)

Continued testing light exposure settings and effectiveness of using flash units to light bridge. Also improved ability to focus on structure (at pitch black from about 300 feet away) for final composition shot.

To be continued.

Filed Under: Project Tagged With: architecture photography, Bridge Illumination, light painting, Nikon D800, Project, SB-910, structure photography, twilight photography

Microsoft Surface Pro 4, Windows 10, and High-DPI Display Scaling Fix for Sony Vegas Pro 13

October 21, 2016 by MikesMultiMedia Leave a Comment

[su_dropcap style=”flat” size=”5″ class=””]I[/su_dropcap]n case you haven’t already noticed, Windows 10 applications graphical icons and text fonts sometimes do not scale properly when viewed onÂ high-DPI displays screens which areÂ becoming standard on various portable computer systems such as the Microsoft Surface Pro 4.

Sony Vegas Pro v13 Retail Box.

Compounding the problem is the smaller 12.3 inch screen size on the SP4 which has a native resolution ofÂ 2736 x 1824. Â So things that are small and not properly scaling appear really small.

Additionally, getting a larger display doesn’t solve the problem either.

For instance, applications not properly scaling and shown on a high-DPI display such as the Dell P2715Q 27″ Ultra HD 4K monitor still have disproportionately sized images and text. The reason for this is because the high-DPI monitor, though larger in size, also has increased pixel density.

So who is to blame for these scaling problems?

Should we placed the burden of properly scaling applications solely on the shoulders of Microsoft Windows 10? Or is it primarily the responsibility of the software manufacturer to be responsible for designing software capable of correctly adjusting itself to the high-DPI environment?

In addition, how much blame should be assigned to the computer system manufacturer for offering products with high-DPI display capabilities without ensuring backward compatibility by coordinating with industry software developers?

Though this article focuses on fixing Sony Vegas Pro v13, it is not the only leading media software failing to properly scale when displayed on high-DPI displays.

In this regard, many of Adobe’s flagship applications, to include Photoshop, Premiere Pro, Bridge, and InDesign, also fail to properly scale when shown on high-DPI displays.

Coincidentally, a variation of the fix used in this article for Sony Vegas Pro is also being used on Adobe products making them once again usable on systems using high-DPI displays.

As one blogger described improperly scaled graphics and text as being the size for “ants to read.”

[su_divider][/su_divider]
[su_box title=”Test System Specifications”]

[su_list icon=”” icon_color=”#333333″ class=””]

Microsoft 12.3″ Surface Pro 4 Multi-Touch Tablet
Intel Core i7 6th Gen (Skylake)
8GB RAM, 256GB SSD
2736 x 1824 Screen Resolution (267 ppi)
WindowsÂ 10 Pro (x64)
Sony Vegas Pro 13.0 build 453

[/su_list]

[/su_box]

The in-house scaling feature in Windows was set to the recommended enlargement to 200%. Even though I was able to go up to 300%, this was not having the desired effect. In some cases only the font would enlarge past its intended field size. So this was not even a quick-fix option.

Lets first start by looking at a couple of before and after comparison images below.

By hovering your mouse over the image and by moving the scale from left to right you can see the difference between the non-scaling GUI on the left compared to the properly scaling GUI image on the right.

This side by side comparison helps demonstrate the benefits of apply the fix making a once too small GUI usable again. I’ve included two version of the side by side comparison images, a full screen shot of the entire Sony Vegas Pro GUI, and a zoomed in version of the upper left hand corner.

[su_divider][/su_divider]
[image-comparator title=”Compare IllustrationÂ 1: Sony Vegas Pro GUI fullÂ screen”Â left=”https://lh3.googleusercontent.com/snKf14IAZsDdtiH40zNAtkhFohibyc4Z5jCCTnFGJmtmtIhXrUL7ses7bckp6c5XtXcppZ-qNPPPMDL7FrfeokOWr4m33Noui5kW0b_QYJk8sp7cx_7faz_5z0B0t3JPerTCnsqMIS2ELn–dNj0rAWMIbZCneIEIfloKVg7zO0f0ylJqR9BH1uPGKPjrCsfvtwxWt0wfALY4aV-Msgcp1hLre1TAPQTvmXg68zy60r7_i8g63rlapXsDITR2tPVYwI9yj_sQ04kkHUVrVmRurYJU99agBNzOeaH17PTqU9KkB5jJe2Lpiv68zqO-T0OtgUaNE1AL8TW4xXYDU5dQTakMb2g8qMr3ReaTAKXnmNGuQoOjQWTbf9AErMrCxU8x4Ba-ecDMWJ9XMTnvkfHVdR1vRD6sMoVPYQozIMPOwahlNtOcNvyBt_IF_u52wjI9iJIAKlZZn1xjZgwD6LEcQJLuBch8qMeIkoIlFVJ-1x9hAwf0kfHDZW32Cfd0Mg9zPzbOp-S_SjyBgdjufvZPy_jCqoHDyddO9oE-dlGqY4WhkQko9Iy1_h2GMZodVLvRo_mLLpDrAYRTtcOYHstUSdYpMB4iGy6WMfDLTIqgIJIDBFw=w1024″ right=”https://lh3.googleusercontent.com/MXljibG1bj8-RMrIGzvclnmemripgVZHbZYpI96r6PCt83dx7ije1kfRnrLRSAs-1bFYxOVL7IjWe6cbcCOikmF86pT2ynGx121mEi090wcS2IBkqkbVWeI9NErDlpQNdtVS9J57VY1_fAcyoYfZe6SHaY-c85qgx6cA99sY9d80cTV9tJ6gRf9NJFQQaxxRY-8viFSNIcD5VTFeLZi-wxygnUdcu0dC2bJ4YGvAAUTDJMq_Df64q-W15SWCx79nZJKv07o163Xw1-EQY0m_zF3zUQsUmKQu7lcAbf2QuLO7bAUj2agrcCQKtWepsFXWEsCITgfwweyK2UrOOKP-bd0zhaWn9OWUF-UPYr78TI6uZgypCervzhy1FrTNWM8OLILN-gCA_t6tPZ8pseHhSAyRVr81ndQxKpx1vn4QvJdZ2IxcsrU_TUzWQX2NUnwXeMxx7C1zlwQcJ2DC9bEdoDyXPetOfIzET0fXaAfo1tgFBj-gEbiXpIpWAwyt9FmLoe6_Lu8ZLM-BodrhJRCeJT6g_xj9AizmhWqlAltp3MgrgKJODrAFLVk9v180M35IYnrR1MZlwZMUo-DgV6VkOScTr5DEa6Y2SLc0jm9TH5SzUjQs=w1024″ width=”150%” classes=”hover”][/image-comparator]

[su_divider][/su_divider]
[image-comparator title=”Compare Illustration 2: Sony Vegas Pro GUI cross section view” left=”https://lh3.googleusercontent.com/Z_cGJTkkHhf0Rv7mosethUi1qEx70G9SNwU3gHO6Qz1JT7-tNX4reWNLaqS169Q4FkA73tLyX_FOtVdrKgs6x_Q4UzR3Sr7GOsknVIq30VBYNqpXjsJYl6vI8bqdR9hSWvt3wInzUlEMkMNBWGOYTgntr1LrPH47IwDQYQF9btVlzexrTv9adrJhuMJ_r9sPQnHqQIKHXe-ysRHa24klkUMjCmk82iKPOgGXTi5dPuVxtZlXLtmg0ZeGVXgl5IJegMfqPPjhSmXjMDD9XahVjZtVDfgVuTZZoImw67LCormIOd6jMvebbG3eZkWEBMJP_c_LmkwyLvzr-b79H6uBLQbFsihEqQNh1U1TOrhYfgeboLfaWLo6ITHbAr22OOtkbvkBiukSQ61ppVwT68bBrDL7h-v3H3yozXA46NJ03tosH4xwQoDAUAsIZuUwLho_EdrWyzd9IXVgxQf-mf2d7W7FHFVLOw5r26pTFnLyFkSJLa7L2d7CqRCM8IWAwxu-gmzrpmgxaZehSrsB1f1-Yx1DsIMzH7vEZkKFGvLY_U-G5P3PWP5-WNCKCGLG8y1eBwhdGcK6atK05e8eD15jdmWiUieCBuiplOZeGz94GQPGKH8u=w1024″ right=”https://lh3.googleusercontent.com/S3qHbWHjCwSSKuEsejWCX84fat2XzSx-_-QLz-7jVynr7ZkXVr7sXlw2ZJmzFZBtKB0YJUM5AaIj0t-nWtDi70_vkN7LYxrBNhU6ufLYpAlMjNxc7oBWV0oo7IAbp-rhfjLZQu3fm6da-wZ1uUjqfij5eIzs58UmIZ9r_WJs_goM7FHz2PVuVxy-4gX9Nqh0kFBrUQ-VFsem26XKtdAHoKOJ08T7IVzF4KqKvei7hvgBm54fPBDIcKq1fz1lEHhfnoW6rngnNFm7k8irwVAwxSwlljUPjzgdP35DalBrZvTB09AteQ_czht9EkaVnkEL9hNsFV5suUHU1TzatDWqLTrkwkgjNeuTGz6zYSw3lQ1n4q9iYX8BBFtAnWFmGCXipNq9Jr6HT6Ny5iogzBPCSJq5u6B9pW-XOAqE0Fyize5tJpkxCrsuilxBecXDR5-V3E3XVxpA_i8ShexxuJTMgBAthPsPIPn0QcmhydyIokpZhlQV-iCzrOVvv4v_M8o-jcg4LJGHp8-VFEo7tBQgcYym6nUWKtzSCMjKcfgu8vw0zmpSEQ9Gw8yOgDJ7DhZ4bvegmN7AOjOBWXnBcEEicitWuhpZ0qp0x569mE0glOSy0qb3=w1024″ width=”150%” classes=”hover”][/image-comparator]

Below I walk you through the step-by-step procedure to apply the fix using screen captures of the relevant screens so you will feel comfortable using this fix.

A companion video capture of the procedure has also been prepared and will be attached to this article later.

Some things that I wont spend time discussing are the technical details surrounding the areas of Windows configured to apply the fix. This includes the Windows system registry, PreferExternalManifest designations, and issues pertaining to the need to obtain administrator access privileges to your system’s protected areas.

Other things not going to be covered in will be manufacture conventions. This includes concepts and terms pertaining to DPI (dots per inch) and PPI (pixels per inch).

These types of discussions regarding various standards imposed on products by manufactures are interesting, however, are beyond the scope of this article.

[su_divider][/su_divider]

Before Proceeding

What worked for me may not work for you.

So do what ever you need to protect your system and data before deciding to apply the procedure outlined in this article.

[su_box title=”Step 0: Prepare System”]
[su_spoiler title=”Backup Files”]

You can backup you files using internal Windows backup resources.
You can also use third-party backup applications such as Acronis True Image.

[/su_spoiler]
[su_spoiler title=”Create System Restore Point”] Create a system restore point using Windows. This feature may already be working. If so, explore where it keeps its log of previously stored restore points and how to restore them. Its very simple and is click-n-play.
[/su_spoiler]
[su_spoiler title=”Application Software”]Locate and have ready any application software disks or license information in case the information is requested. It was not needed in my case.

[/su_spoiler]
[/su_box]

[su_divider][/su_divider]

[su_box title=”Step 1: Download & Install Resource Hacker”]

The first thing you will need to do is download and install a small program called Resource Hacker. See steps below.

[su_spoiler title=”Download Resource Hacker”] Download ResourceHacker from this link http://www.angusj.com/resourcehacker/reshacker_setup.exe [/su_spoiler]

[su_spoiler title=”Install Resource Hacker”]After downloading Resource Hacker. Install it onto your system.

[su_lightbox src=”https://lh3.googleusercontent.com/hrpGXoGo2RzjmIK6IEealFU3dr7qxrlyN2OXoefmxk8H4PJxkprAq2avBndUQOAgjf1_IWcaajJZgoCMwTvwUfhlw39lHhmi4fsa5Nu0ME2WIcVXNtJZzq_7bVMnxUGeplNotvJjGBwvbpWAEqCJFhyygXjOEGVOwqZiQcq59z97h4uytzdwZMPMKIJ_kBNgXlp_qdyb4gn3kyVvg-e8y4Ct5vqkY9b14tpGdeYoSCqc3HqxrBG9ooOQ86YB6_lXMgOgpNNf6cl8qMFJRPv-LI7o2ImNTc_bvylPsrv6kwyZaAwYiWVdr7arTER84QSjyZekSdszblcGTaHEQQMN1BQaC2G4nsXz5qtC2mjwc_K2-boPioP46EJwBC9x-m7zVs94HOnRHaIZE8SZRNuiUXcljnoUx9wDZBCYG4-to9KcYReVmeyX_pe0Xy6tnutntSaqkI8QaFADc9HFt4kSYGBlC117o8N2Fxqupw5H9AYRJR6c7oCEGYanBqnecelwBrcXcAnzOyFDMpl3fSCY1vWbxdxLcFO_3CDAQzTV6_GI1RoHXtdFnSbWn3Gv31TtR5aMWhYpEUD0TCfYNj4ptxaiQ9M0_vpleidiAXx9UYz3vLaC=h500″]

Alt TEXT
[/su_lightbox]

[/su_spoiler]

We won’t need to run Resource Hacker just yet. Proceed to the next step.

[/su_box]

[su_divider][/su_divider]

[su_box title=”Step 2: Access and open up Windows System Registry”]

Next, open up the Windows System Registry and make a couple of adjustments.

[su_lightbox src=”https://lh3.googleusercontent.com/tMg8AqKC0upazpsVZPFkXYIVcnAAajXhvUipRSYvvqk0EYtJ31h6-zAqEbntvlCZJrvqNX04HHDXv0fBFgR3K1aVAcRlp56GM0xqZxypi2aqQnkd1fMTOknM5xKFhHQYddS1GZj8sCYSU23QCzolbZFUvTmwdMKgcXDLnURZYPID8iFsc9J9KklmZed1Dt-s6CPUgE2UihSahBBAm41XEiw5w7_zhkzNs1mbkAmblDzTcWepVbxTawLog8ISXNG9qOawicxQZZVNNvF7EI9JdOAyBfcFqOwtls1Fw_hO27PwBGPsz8KKycj0VxeLvWO9XfDL339qi_3IpEC8n3AcPkj_k6jWIUVwpqZfZsVRUxx7oTO6tpsi-hq6pOdEbngmZ5V35rS3_BKHCf0XU1X8jAF7pgkuTQ6wkQD6kItKGKVNq1grTiN0P7DHxC9khggicH80ajL34Nj55Z_tZDNoERnCPboponB7nyoXMyY7tEjQQqAnR7U0Dk0HDJvTBLBtpEHDW7oDJbIWxzpT_1xNUcurpCdoXBnZksatCVxCh5bzoYIPNZcXIiG5hyRWJYtn-mZSuMKPEPJVtKvMPmxStY3mHNlWLHpGfaU47jF0JA-wlJXc=h500″]

Alt TEXT

[/su_lightbox]

[/su_box]

[su_divider][/su_divider]

[su_box title=”Step 3: Use Resource Hacker to Explore Sony Vegas EXE file”]

Summary:

In this step we use Resource Hacker program to access Sony Vegas Pro’s exe file information for its internal manifest information.

We then copy out the internal manifest information, and the close Sony Vegas Pro’s EXE file without making any changes.

We then apply the extracted internal manifest information to the next step.

[su_spoiler title=”Run Resource Hacker”]Run Resource Hacker[/su_spoiler]

[su_spoiler title=”Use Resource Hacker to open Vegas130.exe”]

Open Resource Hacker
Navigate to and open Vegas130.exe
Navigate into MANIFEST directory
Copy all text inside MANIFEST/1033
Go to next step

[/su_spoiler]

[su_spoiler title=”Open Resource Hacker”]Open Resource Hacker[/su_spoiler]

[su_spoiler title=”Navigate to and open Vegas130.exe”]Navigate to and open Vegas130.exe[/su_spoiler]

[/su_box]

[su_divider][/su_divider]
[su_box title=”Step 4: Create External Sony Vegas Manifest file”]

Summary:

In this step we create an external manifest file for Sony Vegas Pro’s EXE (Vegas130.exe).

We do this by opening note pad using the “Run as Administor” option.

We then past the Internal Manifest information into this text file.

We then save the newly created text file as Vegas130.exe.manifest inside Sony Vegas Pro’s program directory the same place where Vegas130.exe is stored.

At the end of this step, we would have completed all the changes needed to configure Windows and Sony Vegas Pro to now scale its GUI properly when using a high-DPI display.

[su_spoiler title=”Open Notepad.exe as Administrator”]Open Notepad.exe as Administrator[/su_spoiler]

[su_spoiler title=”Paste Manifest Info into Notepad”]Paste Vegas130.exe internal Manifest Information into text file[/su_spoiler]

[su_spoiler title=”Save File as Vegas130.exe.manifest”]Save text file as Vegas130.exe.manifest in Sony Vegas Pro program directory[/su_spoiler]

[su_spoiler title=”Exit programs and Restart Windows”]Exit programs and Restart Windows[/su_spoiler]

[/su_box]
=================================================
Definitions:

API-Aware

An API-aware process is a process that properly updates its process status through the type-specific API that is provided, such as COBOL or Crystal.

======================================
DPI and Windows

https://en.wikipedia.org/wiki/Dots_per_inch

How Microsoft Windows handles DPI scaling[edit]
Displays with high pixel densities were not common up to the Windows XP era. High DPI displays became mainstream around the time Windows 8 was released. Display scaling by entering a custom DPI irrespective of the display resolution is a feature of Microsoft Windows since Windows 95. [5] Windows XP introduced the GDI+ library which allows resolution-independent text scaling. [6]

Windows Vista introduced support for programs to declare themselves to the OS that they are high-DPI aware via a manifest file or using an API.[7][8] For programs that do not declare themselves as DPI-aware, Windows Vista supports a compatibility feature called DPI virtualization so system metrics and UI elements are presented to applications as if they are running at 96 DPI and the Desktop Window Manager then scales the resulting application window to match the DPI setting. Windows Vista retains the Windows XP style scaling option which when enabled turns off DPI virtualization for all applications globally. DPI virtualization is a compatibility option as application developers are all expected to update their apps to support high DPI without relying on DPI virtualization.
====================

SetProcessDPIAware function
Link: https://msdn.microsoft.com/en-us/library/ms633543(VS.85).aspx

Remarks
Warning
SetProcessDPIAware is available for use only in the operating systems specified in the Requirements section. This method may have unexpected behavior in subsequent versions of the operating system. Use SetProcessDpiAwareness instead.

DLLs should accept the dpi setting of the host process rather than call SetProcessDPIAware themselves. To be set properly, dpiAware should be specified as part of the application (.exe) manifest. (dpiAware defined in an embedded DLL manifest has no affect.) The following markup shows how to set dpiAware as part of an application (.exe) manifest.
XML
…

true

…

============================

Writing DPI-Aware Desktop and Win32 Applications
https://msdn.microsoft.com/en-us/library/dn469266%28v=vs.85%29.aspx

(See. Using an Application Manifest)

Declaring DPI Awareness
When an application declares itself to be DPI-aware, it is a statement specifying that the application behaves well at DPI settings up to 200 percent DPI. In Windows XP, DPI awareness has no impact on the application or the operating system, but it has meaning on both Windows Vista and later versions. In Windows Vista and later versions, when DPI virtualization is enabled, applications that are not DPI-aware are scaled, and applications receive virtualized data from the system APIs, such as the GetSystemMetric function.
Note By default, the DPI virtualization feature is enabled only when the DPI display setting is greater than 120 (125 percent).

Although the Win32 API provides a function declaring an application as DPI-aware, its use is discouraged, except in very specific circumstances. For more information, see the SetProcessDPIAware function. In general, using an application manifest is the recommended process for declaring an application to be DPI-aware.
Using an Application Manifest
To declare your application to be DPI-aware, add to the application manifest. Here is an example of how to use the element in an application manifest.

true

====================

High DPI Settings in Windows
Link: http://www.kynosarges.org/WindowsDpi.html

============================

https://blogs.msdn.microsoft.com/chuckw/2013/09/10/manifest-madness/k

============================
Application Manifests:

https://msdn.microsoft.com/en-us/library/aa374191%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

Filed Under: Microsoft Surface Pro 4, Vegas Pro v13 Tagged With: dpi, DPI scaling, High-DPI display, Microsoft Surface Pro 4, ppi, Sony, Sony Vegas Pro, Windows 10 Pro

Manfrotto 577 Video Adapter Plate (501PL) & Vello V-Rig Bracket Reviews

December 31, 2015 by MikesMultiMedia Leave a Comment

Manfrotto 577 Adapter (501PL) & Vello V-Rig Bracket Reviews

1. Manfrotto 577 rapid connect adapter with sliding mounting plate (501):

In this video the Manfrotto 577 Video Adapter Plate is reviewed highlighting two issues regarding the 577’s glitchy safety catch and dysfunctional lever.

2. Vello Tripple Shoe Bracket (V-Rig):

The Vello V-Rig Tripple Shoe Brackets is also discussed which comes in 4.1, 5 and 6.5 inch sizes.

The V-Rig provides three additional shoe mounts and is attached to a camera’s existing shoe mount.

The V-Rig has a 1/4″-20 mount as well at its base. It also has built-in backstops for secure mounting and is made of machined aluminum-alloy construction.

An issue I felt could be a problem with the V-Rig is the restricted use of the center shoe.

Because it is in the middle portion of the “Y” of the bracket, the space can tight when trying to fit a device on this middle shoe.

A Video Mic just fit when mounted on the middle shoe. In addition, after mouting a device on the middle shoe, this completely takes up the inside space a device can use when mounted on the lower outer shoe.

Another issue related to the middle shoe there is no sideways space inward from the lower outside shoe. This means only outward facing devices can be used.

Please subscribe, rate and follow MikesMultiMedia if you found this video to your liking..

http://www.MikesMultiMedia.com
Tweets by mikesmultimedia
http://www.youtube.com/mikesmultimedia

(MikesMultiMedia)(PID20151227_2030)

Filed Under: Brands, Manfrotto, Vello Tagged With: Manfrotto, Manfrotto 501PL, Manfrotto 577, PID20151227_2030, Product Review, review, Shoe mount, Vello, Vello V-Rig

Krog Street Tunnel Graffiti Jib Shoot using Kessler Pocket Jib Traveler Portable Jib System

December 25, 2015 by MikesMultiMedia Leave a Comment

This video shows the practical application of a portable jib system in a field environment inside the Krog Street Tunnel in Atlanta, Georgia.

The jib system used is this video is the Kessler Pocket Jib Traveler. The system lived up to its claims to be a lightweight, one piece portable jib solution promising smooth results. User dependent of course.

One has to pay attention while using the jib. I would say the degree of effort and concentration to get to the threshold point for a smooth shot is like poring a glass of beer into a glass without creating a foam of bubbles.

Over the course of several weeks, I managed to record some solid pieces of me putting the portable jib system to use at a number of different locations. What may not have been covered at one location, may be revealed at the other location. So be sure to watch them all to get the full breath of my use of the jib system.

I call it a jib system because it requires a number of different pieces to work beyond the actual jib. A solid tripod and head, to include a secondary ball head on the end of the jib for the camera mounted there as well. The weights are also vital as well.

Once the physical hardware is put together, you will then need to add the electronic portions to the system which include the camera, and monitoring systems as well.

Various adapters and mounting arms are also needed to tweak the mounting of the monitor and other accessories, such as an external microphone, should you desire to record quality audio from the jib’s camera as well.

Across the several location, I tried to focus on a few key areas of using the portable jib system. The most important of which, is actually using the jib at a real “in-the-field” location, as part of a solid visual composition.

I mention this because many of the video’s I’ve reviewed as part of my research seem to be backyard demonstrations.

I actually try to show the entire process of actually getting to a location with the jib, which I feel sets the stage of the actual effort that is needed for a particular project. Things like properly testing your gear before departing to the jib site are covered.

In addition, the packaging of the gear to transport is also important not only to safely get the gear to the location, but to also repack the gear when your done. Some locations require a good walk to get to. So you don’t want to be just walking around with all your gear dragging behind you. There are clear steps to getting to the location. So that means properly packing, transporting, and then repacking the gear when done. This will ensure that the project is successfully accomplished with no loss or breakage of gear.

I also try to illustrate various composition considerations as well once the gear is setup. Such as carefully exploring the beginning and closing shots of a jib movement. Sometimes this is clear from the start. Other times, its an evolutionary process uncovered once the jib is set in motion.

Since I used a DSLR to record video during the jib shot, properly setting the exposure and focus are an entirely different category of the shoot which is also important to get right. The need to bring extra external lighting will also need to be considered if the jib shoot is going to be done at a location with limited or low lighting conditions.

The Krog Street Tunnel

This particular jib shoot takes place at the Krog Street Tunnel. It is one of my favorite places to explore. It is an historic site in Atlanta, Georgia. Basically it is an underpass which goes underneath the CSX Transportation rail operations allowing traffic to get from one side of the tunnel to the other.

Inside the tunnel, there are two pedestrian pathways on each side of the two lane street. There are three rows of supporting concrete columns holding up the overpass above the tunnel. Graffiti painted over metal hand rails spanning the entire length of the tunnel’s pathways too.

The dusty road debris ridden pathways are lit up by a row of cob web covered lights that lead from one end of the tunnel to the other. The lights, even though sufficiently bright, reveal the graffiti riddled surroundings in an almost gloomy manner.

Because the tunnel interior construction is made up of concrete, with the exception of the two hand rails leading down each of the pathways, it echoes any and all of the sounds which enter it. This means that when cars, trucks, motorcycles, walkers, bikers, skateboarders enter the tunnel at one end, their presence is made know quite vibrantly until spewed out the other.

As you can see, the tunnel really can make an impression. I recommend visiting it at night. During the day, it seems to lose its mysterious qualities almost like when all the lights are turned on in a night club at closing time. So, yea, visit it at night. Oh, after 9 p.m. to allow rush hour traffic to pass. This way you can experience the Krog Street Tunnel at its fullest.

If your lucky, you may even observe a graffiti artist at work.

Getting back to my jib shoot video.

As an ongoing student of using a jib system, my shots are a work in progress.

That means, developing and honing in on the skills needed to achieve adequate jib shots with smooth action and quality compositional demands takes work and practice.

But that is both the fun and challenging part of deciding to use a portable jib system.

Once you get the hang of it, you really can start designing some cool shots.

The Kessler Pocket Jib Traveler

In terms of my decision to use the Kessler Pocket Jib Traveler system for my series is concerned. The actual system you decide to acquire will undoubtedly be decided by your style of shooting and budget.

In my research before getting the Kessler system, I took a look at the other brands out there. For the most part they all seemed to offer the same degree of performance balanced with a system designed for portability. Prices also varied, but not by much.

The one you choose will ultimately be up to you and your budget.

I hope your able to pick up a couple of things from my jib series. They were difficult to produce, adding to the gear I had to lug around from one jibbing location to the next.

I found the use of the jib system a welcomed tool to use for composing video shots. It surely changes a static tripod shot to something that is dynamic full of parallax. Parallax is the funky perspective shifts between foreground and background objects which takes place as the camera is moved using the jib.

I would compare the significance of the parallax video effect when using a jib system to stark difference in still photograph taken at a shallow depth of field using an F/1.4 lens. The two results are that dramatically different and appealing. But each effect come at a price one in effort, perhaps, while the other is with specialized gear.

In addition, for the most part video footage obtained using a jib system is only part of the bigger picture of a production. It will primarily be used as B-roll material on the timeline, much like the material gotten when using a slider.

There are many ways to use the jib system, and I’m sure your find your niche if you choose to explore the tool and use it to create create compelling video imagery.

So sit back and enjoy the series. I hope you find it both informative, insightful, and entertaining.

Filed Under: Jib Shoot Tagged With: Air on the G-String, Atlanta, Bach, Camera Movement, Graffiti, Jib, Jib shoot, Kessler Pocket Jib Traveler, Kessler Traveler, Krog Street Tunnel, Nikon D4, Nikon D800, video production

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

December 10, 2015 by MikesMultiMedia 1 Comment

[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” ]

Filed Under: App - iPhone, Software Tagged With: bit rate, DSLR video, Filmic Pro, ipad video editing, iphone video editing, luckyclan, video bit rate, Video Editing, video production, Videon

Fixing Vegas Pro 13 Initializing GPU-accelerated video processing Crash

October 8, 2015 by MikesMultiMedia 1 Comment

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:

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
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)

Filed Under: Vegas Pro v13, Windows 10 Tagged With: Initializing GPU-accelerated video, Intel(R) HD Graphics Family, Radeon HD 6770M, Sony Vegas, Sony Vegas Pro 13, Windows 10

On-Screen Work-Flow: Microsoft Surface or Apple iPad Pro

October 6, 2015 by MikesMultiMedia Leave a Comment

I recently commented on a PCWorld article, and wanted to share my remarks here because they are insightful.

Original Article How Microsoft’s Surface Book compares to Apple’s MacBook: Let’s play CPU detective:

I can’t stand working with a keyboard and mouse!

Why?

Well over the past year I sought to do my video editing on an iPhone or iPad, which ever one that was fastest and up to the task. The primary reason was that I wanted the portability of being able to work on my video projects “anywhere.”

Anywhere as in waiting in lines, while sitting in the car, or while sitting outside in the fresh air in the yard on the patio. Lugging a laptop around tethered to its power cord, keyboard, and a mouse was not the answer. Remember, you still need a flat surface to use the mouse.

Even though the screen based solution offered by the iPad and iPhone were promising. I still needed to find professional featured rich applications, or at least do the basic tasks well, for the iDevices.

It was challenging to find reasonable application solutions for the basic core work-flow such as image manipulation, video editing, and file access (i.e., renaming, storing, transferring, backing up, etc.).

After that, the next challenge was to learn how to use the iDevice applications, discover their limitations, develop work-flow workarounds. All the while getting used to working with a stylus.

Then, once the iDevice, application and work-flow issues were somewhat resolved. Realizations of the limitations of the iDevices (i.e., limited ram) started taking place, further complicating true portable work-flow practices.

My current hardware “tools” are theÂ iPhone 6 Plus, which is primarily used as a video recorder, and an iPad Air 2, which I use primarily for editing, cutting, trimming, and final producing.

The limitations of the application software on the iDevices is still there. But I’m able to push out basic productions to some degree of satisfaction. I’m able to still pursue projects which I would have otherwise disregarded due to the “old school” methods and limitations of using a keyboard/mouse, and truly limited portable device.

After several months now, I’ve managed to stay busy, but still get bogged down with the clunky file system access offered by the iDevices.

Both needed to be jail-broken so the file storage areas in the applications could be accessed using third party software on my MacBook Pro laptop. Yes, the laptop is still in the work-flow equation, but is used to facilitate file relocations from one application to another, or from one device to another. The files are also mass renamed, and any batch file procedures are also done on the Mac Book Pro as well.

I will add I am running windows 10 on the MacBook Pro under Bootcamp. Primarily because of Windows based software which is not designed for the Mac OSX.

Now, even though the initial goal was to gain portability by using the iDevices, one expected benefit gained from the experience was to develop a knack using the stylus.

The knack has turned into a preference, and I truly dredge using the mouse/keyboard system when working on my projects.Â The on-screen experience is more organic making me feel more connected to my work. This then inspires more creativity to take place without the mouse/keyboard barrier interfering with connecting to the work-flow.

Forward.

I’m looking forward to Microsoft’s next iteration of their Surface device. Especially now that they have gone around the block a couple of time’s with their earlier version in order to work out the technological kinks.

Admittedly, and after spending my time working with the clunky iDevices, I look forward to the promise of a true on-screen stylus working environment on a fully Windows software compatible device. I’m not just talking touch screen either, I’m talking about direct on-screen work-flow writing with a stylus like I would a pencil, pen, or paint brush.

Anything to get away from the iDevices’ limited file access systems capabilities. Something Apple’s iPad Pro doesn’t seem to appear to variate from. Sure, it will be bigger, more powerful,

One reason why Apple hasn’t offered a touch screen option with theirÂ MacBook Pros is that it will directly impact their sales of their iDevices. Surely a consumer would opt to buy a touch screen based MacBook Pro over the iPad Pro simply for the USB ports you’ll get. LOL.

Furthermore,Â it surely would impact the marketing performance of the upcoming iPad Pro, which isn’t even out yet.

However, if a fully functional touch screen based MacBook Pro hits the market any time soon, the Microsoft Surface’s glow in the market share limelight may beÂ short lived.

In that sense, Microsoft has played a marketing and manufacturing chess game by selling their fully functional device at a time when Apple is forcing their customers to choose between one or the other, or both.

In this respect, I look forward to being able to use windows based video/photo/media management software on the Surface Pro without any loading or running limitations.

What will that mean?

For one, I will be able to incorporate my preferred stylus-based work-flow into the mix. I will finally be able to use my Windows based software with my stylus to really start producing.

In this sense, yes, the Surface Pro has been a waited for edition to my digital media tools. It will truly trump the limited “not for work but for play” functionality of the iDevices. Not to mention their limited file access capabilitiesÂ which ultimately draw you back to a laptop deviceÂ (i.e., iTunes file transfers, etc.). I mean, really, if I have 50GB of raw camera files to edit, what are my non jail-broken options to transfer that data to and from the applications?

However, even if the Surface Pro is great, there still is the issue of fully on-screen/stylus based functional software.

Sure, old mouse/keyboard based software mayÂ load and run on the Surface. However, will it be another frustration working with incompatible GUI’s designed for the older pointing devices, versus one that was truly designed to work with the ergonometrically superior stylus based, on-screenÂ work-flow?

A true tablet/stylus based software will need to incorporate stylus based on screen manipulation capabilities and not just offer backward compatibility of the old mouse/right-click functionality. It will have to do both. That is, run the older software, and the new. You can’t expect people to also run out and spend what money they have left upgrading all their software to truly catch up to the Surface’s on-screen capabilities.

In any case, on-screen GUI’s are here to stay.

Once the stylus technology and Windows, or MAC OSX software catch up, there shouldn’t be any turning back.Â I expect the stylus to be a fullyÂ functional with engineering that stands on its own, and even leans forward into unchartered stylus waters.

Filed Under: Apple, iPad, iPad Pro Tagged With: Apple, iPad Pro, Microsoft, Surface Pro

Otterbox Defender Case iPad Air vs iPad Air 2 Review

August 11, 2015 by MikesMultiMedia Leave a Comment

The Otterbox made a stark change to their Otterbox Defender Case series for the iPad Air 2 as compared with their previous version of the same case for the previous iPad model, the iPad Air.

This review takes a look at the flawed design change which reduced the ability of the Otterbox Defender Case for the iPad Air 2 to perform as well as Otterbox’s previous model of the same case for the iPad Air.

Prospective customers should be made aware of Otterbox’s modification to their case before buying the case for the iPad Air 2.

More Info:
http://www.mikesmultimedia.com/store/Otterbox Defender Case

VID: 20150811_1615MXV v4

Filed Under: Apple, Defender Case Series, iPad, iPad Air, iPad Air 2, Otterbox, Video Tagged With: design change, iPad Air, iPad Air 2, iPad air vs iPad Air 2, MikesMultiMedia, Otterbox, Otterbox Defender Case, Product Review, review

Open Box – NETGEAR Nighthawk AC1750 MN 6700 WiFi Smart Router (review)

December 5, 2014 by MikesMultiMedia Leave a Comment

Open Box – NETGEAR Nighthawk AC1750 Model Number 6700 WiFi router.

This video walks through the process of opening up the box to a new NETGEAR Nighthawk AC1750 MN 6700 Smart WiFi Router.

This video includes three parts showing the opening, putting together and then conclusion of the open box and review of the NETGEAR Nighthawk.

This was just a quick Open Box video project. I would like to include further videos perhaps discussing the admin panel and setting up the system using its setup menus.

VID: 20141130_2345MX

Filed Under: NETGEAR, Open Box, Video Tagged With: AC1750, MikesMultiMedia, MN 6700, netgear, NETGEAR Nighthawk, Nighthawk, Open Box, review, smart WiFi router, video production, WiFi router

An Easy Solution to the MacBook Pro’s Blanking Out Screen Problem

October 10, 2014 by MikesMultiMedia 1 Comment

[pe2-image src=”http://lh5.ggpht.com/-9N2rStolbH4/VDm051csZWI/AAAAAAAAAO8/ydQ59oth8kc/s144-c-o/20141008_1642PA_01%252520Windows%252520v8.1%252520Window%252520Under%252520Parallels_FULLxAuto.JPG” href=”https://picasaweb.google.com/106423603886853212149/WindowsOSUnderParallels#6069080878551426402″ caption=”20141008_1642PA_01 Windows v8.1 Window Under Parallels_FULLxAuto Photography by MichaelUribe.com” type=”image” alt=”20141008_1642PA_01 Windows v8.1 Window Under Parallels_FULLxAuto.JPG” ]

(Oct. 10, 2014) — I recently came across a problem with my MacBook Pro 15″ Mid 2012 Retina computer screen going blank when I unplugged the power cord from the system.

The obvious solution escaped me because I was at the tail end of installing Windows 8.1 Pro, along with all of my other software applications. I naturally assumed the problem was some kind of driver conflict or incompatibility resulting from all of the installs and updates I was undergoing during the installation processes.

To further cloud my troubleshooting efforts, I was installing W8.1 onto my MBP using Bootcamp. Bootcamp is one of a number of applications which allow you to install windows on the MBP, while keeping the OSx partition as well. This way, you can boot into either Windows or into the OSx environments.

All said and done, with all of the peripheral software tasks I was imposing onto the system at the time, it’s no wonder why I didn’t tune into the simplest solution to the problem at first involving the MBP’s automatic screen dimming (ASD) feature eventually.

There are a number of resources online, which of course I explored, and which involved more of a configuration or software based approach to dealing with a screen blanking out situation. Solutions such as resetting the MBP’s â€œparameter random-access memoryâ€ or PRAM, or “Non-Volatile random-access memory” or NVRAM, are discussed generously online. Feel free to explore those options should your troubleshooting adventure take you there. They, however, were not exactly causing the problem in the scenario I faced resulting in a blanking out screen.

I am not going to get into the resetting of VRAM solution here, because that wasn’t my problem. However, there are many articles on the web discussing how to reset the MBP’s VRAM cache, which may be a workable solution should a similar blank-out-screen problem occur.

So, the culprit here involved the MBP’s automatic screen dimming (ASD) feature.

In short, the ASD feature basically dims the screen, or reduces the brightness of the MBP’s screen when you disconnect it from an AC Power source. This is done as a battery power conservation approach when the MBP goes off AC power for any reason.

To make my situation even more complicated, my MBP’s screen actually would go blank when I plugged the AC power connector in, and not when I disconnected it.

My AC power connector is a Magsafe 2 connector, which is a great way to avoid breaking off your connector or damaging your MBP’s connector port in the event of a cable mishap.

Before Proceeding

Catagories