So I was let know that LastPass version 4 does in fact work with e10 multiprocessing in Firefox. The normal update does not work, so you need to install LastPass 4.0 from the web site.
There is no word on Xmarks though.
So I am now running the iCloud Bookmarks Plug In on my Surface Pro 4 to sync between Internet Explorer, Firefox and Chrome. And using Firefox bookmark Sync to sync from my mac to my Surface Pro.
So it looks like neither Xmarks or Lastpass will ever support e10 Multiprocessing in Mozilla Firefox. For years Mozilla Firefox has been my browser of choice because of all of it’s extensions. There was a short period where I used Chrome, but it is not as customizable. Firefox though is changing and is becoming multiprocessor, and that requires re-writing plugins to work with e10, or they won’t work. Right no Firefox will still work without e-10, by keeping Firefox in the old mode without mulit-processor support.
I contacted Xmarks/Lastpass support to see about their e-10 support, and I got this response.
Hello,
Thanks for reaching out to Xmarks Support.
Through testing that we were unable to install Xmarks in Electrolysis e10. At this time, we have no plans to launch Xmarks compatibility with e10. I will submit a formal feature request ticket advocating your desire if you’d like.
Thanks,
Jeremy
So basically a paid service will never update their software and will very shortly lose all support for Firefox my favorite browser! Time to kill my accounts for xmarks and lastpass!
Of course now the question is how to replace these essential programs. I am going to try out Firefox Browser sync, and iCloud sync. Unfortunately iCloud Browser sync only runs on windows, but I have my Surface Pro 4 running Windows 10, so I can try Safari Browser sync to sync between Chrome, Firefox and Safari on Mac. And it is e10 supported, so that might work. I will keep my backup in Firefox on my mac so I can keep replacing my good backups.
Some more test footage with my DJI Osmo+ in the big rain storm in Los Angeles, on February 17th, 2017. Shot in D-Log with Sharpness of 0, Saturation of -2 and Contrast of -2. I did a simple color correct in Premiere Pro 2017 with Lumetri Color. Still not 100% happy, but I think it looks pretty good.
The footage is a bit shakier than I would like, but the wind was strong and it kept gusting and hitting me and the camera with water.
DJI OSMO+ Footage with Sharpness set to 0 and Saturation and Contrast set at -2 and Standard footage set at 0, and then color corrected in Lumetri in Premiere pro 2017. Still not quit happy with the look, though I love the stabilization.
DJI Osmo+ Footage test walking footage trying to get flat footage with color correction. Setting set to D-Log with Sharpness set to -2, Saturation to -2, and Contrast to -3.
Still not quit happy with the color correction or flat image.
Test Footage with my DJI OMSO+ and the Z-Axis in low mode for stabilization. Looking more stable for sure, but not yet there. And really not happy enough with the color correction.
So this is a new test with my OSMO+ and DJI extension rod working in Low mode with my Shar Pei’s Indiana Bones and J.K. Growling.
I did a quick, though insufficient color correction in Premiere Pro 2017 Lumetri, though I have not gotten the image flat enough as of yet. It was on auto exposure and UHD settings.
Meagan Keane at Adobe Creative Cloud blog has the info on the latest release update.
This is a big one for me since I did just did a big captioning job and had issues with Captions not being editable in many Workspaces, so hopefully this has fixed that. And the whole Title tool crashing if you copy within it is another big one.
I was able to work around all these issues, but having them fixed is a big plus.
So RedShark has posted an opinion piece on Final Cut Pro X 10.3 and why you should give it a second look now because it is so fast and has become so powerful now. The author gave it a new look after looking at this video.
It is interesting and it does look powerful now, and full of most of the features it should have had on release.
Still a couple of things give me pause. Number one being this quote from the article on the magnetic time line:
The stress of knocking your entire sequence out of sync is gone.
I can honestly say that I never had any stress about knocking a timeline out of sync in any NLE. You learn how to use it and never have an issue with knocking stuff of of sync. To me that is not a reason to create an all new paradigm for the timeline, because I have never had a problem with knocking things out of sync!
And second I just don’t trust Apple anymore. Sure I love OS X and wish I could stay on it forever, but without having a customization “Pro” machine like the old MacPro I can’t see them as Pro. And that is why they have to make FCP X work on less powerful machines so well, because they don’t have a viable alternative. And no way am I ever getting a trashcan even if they do upgrade it. Not having it upgrade able or internally expandable means it will not last like my MacPro from 2009 has! And I don’t trust apple to not just kill FCP X one day. They did it with Shake. They did it with FCP 7. They did it with Color. They did it with DVD Studio Pro. They did it with Aperture. I just don’t trust them anymore.