Saturday, November 24, 2018

Dependency issue and fix upgrading Ubuntu 17.10 to 18.04


When attempting to upgrade Ubuntu 17.10 to version 18.04 it would give a message about 'failed to update Ubuntu-Desktop.'

Failed to start session after the upgrade and restarting. Issue was dependency that was broken: "ligbm1"

Answer from k.child90 from askubuntu.com below:

https://askubuntu.com/a/1080242/731657

"I took this along to a laptop clinic who solved the issue. The login screen, importantly, looked identical to the 16.04 Unity login screen which betrayed the problem in transferring to 18.04 (which has a very different looking login screen).

In TTY attempting to install certain packages gave unmet dependencies, and following the chain down gave the ligbm1 package at the base. This is the dependency for a lot of unity and xserver packages (attempting startx also failed). Uninstalling ligbm1 and then installing it again allowed installing ubuntu-desktop without error." --k.child90


Monday, September 19, 2016

vim (gVim 8.0+ on Windows) configuration notes and settings

1. In Windows, drag and drop OLE (:drop) functionality will be disabled if the program is launched as an Administrator. So remember to NOT set launch as administrator in the app's properties dialog box so drag and drop will continue to work. This also allows the right click context menu to work for 'edit with vim' and 'edit with vim (existing)' commands to open files properly. Windows won't allow drag and dropped files to escalated programs or at least it didn't work with vim.

2. As a side effect of #1, not launching as admin, means the program might not have write rights to the vimrc config file (c:\Program Files (x86)\Vim\_vimrc) so even doing :w! didn't work. E212 Can't open file for writing was the error.

Also,
cmap w!! w !sudo tee % >/dev/nul
didn't work. What DID work was going to the _vimrc file in Windows file properties security dialog and change the file permissions to allow users full access.

3. colorscheme (filename without .vim) only read from c:\Program File (x86)\Vim\Vimfiles\colors and not the default %HOME%\vimfiles\colors folder. Solution: copy the filename.vim to the program files folder.

4. Airline not showing patched font properly. Out of the prepatched fonts available the OTF fonts didn't seem to work. One font that did work that I like is Inconsolata-g.

set guifont=Inconsolata-g_for_Powerline:h11

with
set guioptions-=e "guitabs off

and
let g:airline#extensions#tabline#enabled = 1
let g:airline_powerline_fonts = 1

turned on it worked fine. I had to make sure the following WASN'T set as this killed the special symbols.

"if !exists('g:airline_symbols')
"  let g:airline_symbols = {}
"endif
" unicode symbols
"let g:airline_left_sep = '»'
"let g:airline_left_sep = '▶'
"let g:airline_right_sep = '«'
"let g:airline_right_sep = '◀'
"let g:airline_symbols.linenr = '␊'
"let g:airline_symbols.linenr = '␤'
"let g:airline_symbols.linenr = '¶'
"let g:airline_symbols.branch = '⎇'
"let g:airline_symbols.paste = 'ρ'
"let g:airline_symbols.paste = 'Þ'
"let g:airline_symbols.paste = '∥'
"let g:airline_symbols.whitespace = 'Ξ'

and to have it show properly with airline updating the status line and tab line upon starting gvim:

autocmd VimEnter * silent AirlineRefresh | wincmd p | wincmd p

That seemed to fix it to get working right at startup.


Tuesday, September 13, 2016

Disable UAC prompts on Windows 10 and still have metro apps working

Not from me but from http://www.tenforums.com/software-apps/12065-cant-open-any-windows-app-uac-disabled-2.html#post557465

04 Feb 2016 #11
Greg R

This fix worked for me

Hello,
I disabled UAC and when I try to open Edge, Calculator, etc I get a window message that says that I cant open it with UAC disabled, I find it something very annoying that makes me think about going back to Windows 7, is there any around this?
In Windows 7 for example, I was able to open the calculator with UAC disabled.
Thanks!
I have a fix that will allow you to still keep UAC enabled, provide no prompting for a user, while still being able to run all Metro apps - calculator, Edge, weather, news, calendar, etc
Either through Group Policy or Local Security Policy
Computer Configuration\Policies\Windows Settings\SecuritySettings\Local Policies\Security Options
User Account Control: Admin Approval Mode for the Built-in Administrator account = Enabled

User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode = Prompt for Credentials
Next, make some registry changes ....
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Make the following changes
ConsentPromptBehaviorAdmin 0x00000003 becomes 0x00000000

ConsentPromptBehaviorUser 0x00000003 becomes 0x00000000

EnableLUA 0x00000001 stays at 0x00000001
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\UIPI
Change (Default) from the (value not set) to 0x00000001(1)
Reboot your Windows 10 machine and enjoy all the metro apps that require UAC/escalation without the nags

 Remember to reboot first!

Wednesday, October 24, 2012

Sony Movie Studio 12 Platinum (Vegas) and x264vfw64 on Windows 7 64bit

I had a heck of a time getting the 64bit version of x264vfw to work with Sony Vegas...I mean "Movie Studio" as it is now called in version 12. You have to use the 64bit codec to encode with the 64 bit version of Movie Studio but after installing the codec wouldn't show up when I go to Render as....

OS: Windows 7 Home Premium 64 bit (Google Affiliate Ad).

Note: If you want to use 64bit windows with the 32bit version of vegas and the 32 bit version of x264vfw it will work fine. The below information is for getting x264 encoding to work with the 64bit version of Vegas (Movie Studio).

Problem: 64 bit version of x264vfw (x264vfx64) would not show up in Sony Movie Studio Platinum 12 (or Vegas Pro) for encoding with the 64 bit version of Movie Studio.

Solution: Default install location of x264vfw is c:\Program Files\x264vfw64 instead of C:\Windows\SysWOW64....so the fix is to change the install path when installing x264vfw64 to:

C:\Windows\SysWOW64



I guess if you install it to the default location (Program Files) that you might be able to add that to the Windows path environment variable and have it work...maybe (haven't tried it).

Long story:

I tried many different versions of this 64 bit codec and got it to work but only sorta....when i updated to the newer version it wouldn't work anymore and I couldn't figure out why version 20 of the codec would work yet version 37 would not. By 'would not work' I mean it would install and I could run the configure shortcut it installs to the start menu but it would not appear in Movie Studio's codec list to actually use it from within Movie Studio....finally figured it was the install location (an think it might work if adding to the Windows path if using the default codec install location...but haven't tested that).


Tuesday, October 2, 2012

Notes from X's Art of the Let's Play Audio Editing for Video Game Recordings

Notes from X's Art of the Let's Play Audio Editing for Video Game Recordings


I watched the above video by davidr64yt (a.k.a. "X") and made these notes. I'm going to use these to create my own work flow. There's a lot of good advice and reasoning in his video so I suggest you watch it. I took these notes so I wouldn't have to re-watch the 1.5 hour video again to remember how to do some of things mentioned in it.

Record separate commentary/narration using Audacity (or Dxtory's separate audio track) from the game sound. If using FRAPS, use Audacity for your voice instead of FRAP's mixing both game and voice into a single track.

Work in Audacity starting with the voice over/commentary/narration track.

1. Eliminate Spikiness:
 Select whole track, Effect -> Compressor...
 Find your own settings (ex. from X: -20db threshold, ratio 6.5:1, X uses a Koss SB45 headset). Compressor increases volume on track so best to start recording at a quiet volume if your microphone supports that.

2. Eliminate Background Noise:
 Select a quiet section of audio, Effect -> Noise Removal...
 Click Get Noise Profile.
 Select whole track, Effect -> Noise Removal...
 Again, Find your own settings (ex. from X: 15db reduction, 1.79 Sensitivity, Frequency smoothing 130, Attack/decay time 0, Noise remove)
 Click OK.

It's a good idea to save frequently and here is a good time if you haven't already.

3. File -> Export... as WAV file your narration/commentary.

4. Add exported WAV file to your video editor (X uses Premiere Elements which I don't recommend due to its bugginess, try Sony Vegas instead) and place it on the video timeline. X's video actually shows some of the audio import bugs of an older version of Premiere Elements.

5. Play narration along with game to get an idea of how they sound together. X's example shows his game audio is still too loud and overpowers his voice narration. This will be fixed in Audacity after extracting the game audio track.

6. Extract game audio as a WAV file using your video editor or another tool for use in Audacity.

7. Import the extracted/exported WAV of the game audio into Audacity.

8. Select whole game audio track. Effect -> Compressor...
 Find your own settings (ex. from X: -35db threshold, ratio 5:1, check compressed based on peaks).

9. With whole game audio track selected still, Effect -> Amplify...
 Find your own settings (ex. from X: -20db, That's negative 20 (not positive) Tip: you can use the gain slider to temporary change the gain to see what your offset for amplifying should be). A negative amplification will bring the total volume of the track down (and bringing the game audio volume to a better, more balanced, level which goes nicely with your narration).

10. Preview game audio with narration for balance again. How do they sound together? Anything too low or too loud?

11. Export game audio from audacity. Remove original audio from video editor and replace with imported game audio we edited.

Good time to save your work :)

12. Watch/Listen to entire video in your video editor and make notes of any places that need emphasis or de-emphasis. Mute any parts of your narration that need muting such as when talking over a NPC.

13. When overall balance is good go back to Audacity.
 Be sure to have your game track up top and voice over/commentary underneath the game track. Select the entire game track for the autoduck effect. Autoduck decreases game audio when you're talking (when there is audio in the bottom/lower/commentary track).
 Effect -> Autoduck... A subtle effect is better. Find your own settings. (ex. from X: -3db, probably not more than -5db).

14. Export finished game audio as WAV.

15. Re-import finished game audio back into video editor.

16. Maybe lower game audio again a bit if still slightly too loud (can do in video editor adjust gain negative db slightly.)

17. Using notes file, emphasizing quiet parts. X does this by creating key frames in Premiere Elements and the audio volume fades up and then down. Use subtle fade increases/decreases in volume of about 1-3 db.

18. Listen using speakers...make possible adjustments to audio if it sounds different from using headphones.

19. Pay attention to details. Watch final video and make final adjustments.

Friday, July 29, 2011

FRAPS, Vegas, x264vfw codec, SFK files and Black Screens Showing in Video Previews and Rendered Video

PROBLEM:

I noticed other's have an issue sometimes with their FRAPS footage showing black or blank screens for a second or two as if the frames were dropped in their videos. I encountered this problem myself and found a solution. The blank screens were not only in the rendered video, when the problem occurred they were also in my Sony Vegas Video Preview window before rendering -- YET playing back the source avi movies (the raw FRAPS footage using Media Player Classic Home Cinema (using the k-lite codec pack and x264vfw codec) there was NO blank screens in the raw footage -- only in the video preview and rendered video.

SOLUTION:

Delete Sony Vegas's SFK files which are found were the original source files are located (C:\FRAPS\Movies) and re-render if needed. Might be a good idea if you run in to the problem frequently to do the long solution below.

LONG SOLUTION:

Import all of you source FRAPS footage movies by dragging them into Vegas, save your project, then DELETE the created SFK files. Apparently, importing everything at once, Vegas has trouble sometimes randomly and the SFK files become corrupt. They will be recreated after you delete them, then close and reopen the project. I have no idea why this happens but the solution is pretty easy and the re-rendered footage rendered fine.

TL;DR:
Blank screens in FRAPS not a FRAPS issue, was a Sony Vegas issue, fix is to delete the SFK files and reopen project. Restarting Vegas may also work if deleting the SFK files does not.

Thursday, May 26, 2011

Seatools for Windows 1.2.0.5 and DOS 2.20, 2.23 and Nvidia's older nForce 4 (ultra amd) chipset SMART error with Nvidia SW IDE driver

I purchased a new Seagate 1TB 3.5" SATA hard drive and wanted to ensure it was good before using it as my main new hard drive in my most used computer.

Problem:

Seatools in Windows reports SMART error and my chipset is nForce 4 ultra AMD using Nvidia's IDE driver. The IDE driver is the problem for the SMART fail in Seatools for Windows and poor coding is the reason for Seatools in DOS (and Seagate's software not understanding the Nvidia IDE driver's response to the SMART test in the Windows version).

Solution:

For the SMART error appearing in Seatools under Windows: remove Nvidia's IDE driver. (Start, Control Panel, Nvidia Drivers, Check Remove only Nvidia IDE). For the DOS crashing of Seatools: use the older text based (non-crashing version) of Seatools to run a test on the drive. Version 1.09PH worked for me no problems.

Long story:

So I started Seatools for DOS 2.20 and did long tests and Seatools would crash, meaning the long test after several hours running would not report a pass or fail and the majority of the graphical interface was still visible behind the text based interface which was in the upper left corner of my screen. The graphical interface crashed and did not reset the resolution or text mode back so that the text screen would show, the one where it tells you about viewing the log or saving to floppy. If I tried to view the log it would give an error message about it being an invalid display mode. I could copy the log to a floppy drive however and view that log which only stated that the long test had started and gave no result or mention of a pass or fail for the test.

So I figured I upgrade to the latest version of Seatools for DOS which at the time of this writing in May 2011 is/was 2.23. Same results except this time for the long test in DOS it would show passed and then it would freeze at the end of the test (couldn't use alt-keys or mouse to exit Seatools). Seatools doesn't like the Nvidia nForce4 chipset it seems.

I should also mention at this point in dos versions of Seatools SMART has not been tripped is mentioned in all versions.

Now in the Windows version of Seatools 1.2.0.5, All tests would pass except SMART (basic test was the only option I had).  This would say:

SMART - FAIL 5/25/2011 6:14:46 AM
SeaTools Test Code: A9E9E24A

I couldn't find information on this test code but did find some forum thread about Segate's failing the SMART test. This is a brand new drive in fact and I do understand how brand new equipment can fail but I just wanted to point that out. Note that every other hard drive SMART monitoring program I tried reported SMART status had not been tripped (as Seatools for DOS correctly reported) and that the drive is in perfect health after running a scan with diagnostic tools other than Seatools.

Here are two such thread I found:
http://forums.seagate.com/t5/SeaTools/drive-status-SMART-FAIL-incorrect/td-p/7944
http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/SMART-FAIL-in-SeaTools-Diagnostics-and-Drive-Detect-results/td-p/18901

The latter thread points to the SMART fail as a possible driver issue. Which is what the problem was the Nvidia IDE driver in fact. Removing it and running the Seatools for Windows again did not give a fail. Instead I get:
SMART - Pass 5/26/2011 9:25:19 AM

And for a second and third opinion: I tried HD Sentinel and HDDScan for Windows and the drive is in perfect health and passed all tests including the SMART tests and none of the SMART data on the drive has exceeded any thresholds.

So Seatools for Windows...you just don't like the Nvidia's IDE driver...and Seatools for DOS (graphical version)...your coding just sucks....Seatools for DOS (text-based)....you still work with no issues.

All tests now pass once I removed this conflicting Nvidia IDE driver.

General disclaimers:

If you get a report about a SMART failure it may be a false positive from Seagate's Seatools as above with the driver conflict but you should check it out with other diagnostic tools just to be sure you don't actually have a failure.

And, as always, Have a good, verified backup before running any intensive hard drive tests or what not.

More info:
http://www.google.com/search?hl=en&biw=1390&bih=839&q=+site:forums.seagate.com+smart+fail+seatools