-->

Friday, July 13, 2018

author photo

Technology - Google News


Full version of Photoshop for iPad on deck for 2019, reportedly

Posted: 13 Jul 2018 07:39 AM PDT

lightroom-cc-collections

Lightroom CC gives us an idea of how Adobe will approach a full version of Photoshop running on the iPad.

Lori Grunin/CNET

Finally, it looks like Adobe's bringing "real" Photoshop to the iPad and other mobile devices, according to a report today. The cross-platform development effort was more or less confirmed by Adobe's chief product officer of Creative Cloud Scott Belsky, though the 2019 target was not.

Bloomberg calls this a "strategy shift" as if it's a new development, but it really isn't. That shift really occurred in October of 2017 when Adobe introduced its ground-up reimagining of its batch photo-processing software, Lightroom CC, shunting the more powerful "Classic" to the back burner.  It then followed up last month with a sneak peak of its upcoming video equivalent, Project Rush

Now Playing: Watch this: See how the Apple Pencil works with the new iPad

1:14

While a more complete cross-platform version of Photoshop would likely look like Lightroom CC, it will probably work a lot like Rush: A stripped down, mobile-first interface designed to work across all devices, driven by Photoshop's desktop engine and Adobe's Sensei AI technology, with seamless handoff across devices. (Lightroom CC works in a similar fashion, but it's simply unsuited for at least one major use case, working with raw+JPEG files, so it's not really "full Lightroom." )

With iPad creatives defecting to apps like Affinity Photo, Adobe's been under pressure to offer a complete photo-editing solution to compete. But now's probably the right time. The market's changed a lot and the perception that desktop applications should cost more because they're weightier has given way to accepting that anything that comes with an accompanying cloud service will require you to pony up monthly.

But Adobe really needs to fix some aspects of Creative Cloud's syncing if it's going to push Rush and Photoshop as major cross-platform solutions. If you have multiple Creative Cloud accounts -- or need to work with clients who each have different accounts -- it's a major pain. Shared libraries only partially ameliorate it.

And right now, you still can't selectively sync assets. On the desktop, if you've got 50GB of assets, it syncs all of them. The only way around it is to constantly move folders in and out of the local Creative Cloud folder on a desktop. On mobile devices it syncs on demand, rather than keeping local copies of everything. Library assets and mobile creations still exist in a completely separate location from your other assets (though both are "moving there soon").

If Lightroom CC serves as a model, don't really expect a "full" version of Photoshop. But you really don't want that; at this point Photoshop is the Winchester Mystery House of software. What it really means is that it will use the current desktop engine (running in the cloud) so that the quality and speed of processing isn't constrained by the lack of power of the device. That's really where Adobe's advantage lies compared to many of its competitors.

The ability to work seamlessly across devices? Great. Begin stuck working in a mobile-optimized interfaces on a full-size display? Not so much. Unfortunately, we're stuck with that, as well as the lack of color management on mobile. At least for now.

Let's block ads! (Why?)

The 2018 MacBook Pro keyboard doesn't seem to improve reliability, and that's not great

Posted: 13 Jul 2018 06:59 AM PDT

  While repair data collated by AppleInsider continues to suggest that Apple has made some reliability improvements in the MacBook Pro keyboard in the past year, there appears to be no changes made to the third generation butterfly switch keyboard beyond a quieter typing experience —but there should have been.


First, lets talk about the data. We've done this once before, but let's recap the findings from April, and update the numbers with a full year of data from the 2017 MacBook Pro

All data has been collected from a series of Apple Genius Bars in the U.S. that we have been working with for several years, as well as Apple-authorized third-party repair shops.

The 2014 MacBook Pro model year saw 2120 service events in the first year, with 118 related to keyboard issues necessitating an upper case replacement —5.6 percent of all MacBook Pros serviced in the first year. The 2015 has 1904 service tickets, with 114 relating to the keyboard, making 6.0 percent.

The two numbers are very similar, which is to be expected. The keyboards were essentially unchanged since the 2012 Retina MacBook Pro, and should have failure rates similar to each other.

Apple released the new keyboard with the MacBook, and moved the design to the 2016 MacBook Pro. In the first year of the 2016 MacBook Pro, our data gathered 1402 warranty events, with 165 related to only the keyboard and not including the Touch Bar —11.8 percent.

As we mentioned, we now have a full year of data. Since the MacBook Pro release in June 2017, our data set has grown to 1369 captured service events in the first year of availability with 112 related to keyboard issues also not including any Touch Bar issues, very slightly growing the share to 8.2 percent.

Failure rates over time across all four models are relatively static, with no appreciable increase or decrease in events reported at any time after the surveyed first year. Percentages of failures were comparable between the third-party authorized shops, and the Genius Bar data.

For the 2014 MacBook Pro, of the 118 repairs, 8 came back for a second go-around on the repair within 90 days. With the 2015, 6 did. None came back for a third time.

Regarding the 2016 MacBook Pro, of the 165 keyboard repairs, 51 came back again once, and of those 51, 10 more came back for a third time in that first year. The 2017 fared better in this regard, with 19 of the 112 coming back once, and 4 of those coming back for a third time in the same timeframe.

The effect of the repair program

We'd mentioned that there was a fairly static failure rate across the entire timespan. However, what we weren't expecting is just about the same rate of service on keyboards after the repair program was issued on June 22 —and no increase in the 2016 model's rate.

Resetting the counter to only incorporate the keyboard repair program, the percentages as a whole of the service calls are essentially unchanged —at least for now.

In the three weeks since the program was launched, there have been 83 2016 MacBook Pro service incidents captured in total, with 10 of them being keyboards —about the same as the pre-service percentage.

The 2017 model has seen 110 service events captured since the repair program launch. Of those, 7 were keyboard repairs —again, about the same as the pre-service program rate. None of the machines we've captured data on have gone back for a second repair after a repair under the new program.

In both repair pools, no machines repaired under the program have come back for service a second time. It hasn't been that long, though, so there's no real conclusion to draw from that data points as of yet.

If the repair program was causing a flood of service requests because of pent-up demand for repair, we'd have seen an uptick in both service events per month, and the keyboard repairs as a percentage of the total service calls. At present, both numbers are virtually identical.

Like we said, it has only been three weeks since the repair program launched. We acknowledge that the data set is small since the repair program, but we're continuing to keep an eye on it.

Key takeaways

Overall, the total number of service calls is lower for both the 2016 and 2017 MacBook Pro, versus the older models, even including the keyboard failures. Given that the volumes of MacBook Pros sold over the years are pretty static, this points to a more reliable computer overall —which is good considering that there are no user-replaceable parts.

Also, clearly, there is some kind of change between the keyboard originally in the 2016 MacBook Pro, and the one that is being used to repair the older machine with it standard in the 2017 MacBook Pro.

But, what those changes are, Apple isn't saying. Plus, they appear to have not made any more improvements in the 2018 MacBook Pro keyboard, given recent statements —or the lack thereof.

Wait, no further reliability improvements in the current keyboard?

The keyboard is the new machines is different. It has been re-engineered to give the users a quieter typing experience, which Apple has told us is the number one user complaint about the machine.


Apple hasn't said anything directly about keyboard reliability improvements in the third generation butterfly keyboard. When asked directly, they either verbally dance around the topic like AppleInsider's sources, politely defer saying that the issue only impacts a small percentage of users, and in rare instances say nothing has been changed.

The Verge asked directly, and was reminded that the failure rate was low. CNet was told that the keyboard contains "no new engineering or tweaks" to alter reliability.

We were told by a source within Apple corporate not authorized to speak for the company that "CNet's account is probably not right." But, we were rebuffed when we pressed for more information. Certainly, the statement is not a strong declaration that there are fixes.

Improvement in the keyboards used for repair, but still could be better

Since the MacBook Pro 2017 launched, the repair service data is very clear that the keyboards were different. They certainly are on the outside, from a marking perspective, with the symbols on the control and option keys differing from previous.


Repaired keyboard on a 2016 13-inch MacBook Pro

It was suggested to us that users may not know about the keyboard repair program and are either living with it, or trashing a machine because of it. Information on the program is not hard to find, and a Google search just on "MacBook Pro Keyboard" finds Apple's page on it in the first few results —so we really don't buy that argument.

To solve that particular issue, if you can even call it that, there is a fix. Apple knows who owns the machines. We'd have liked a mass-email to all of the 2016 and 2017 MacBook Pro owners telling them that the program exists.

Furthermore, with the 2018 MacBook Pro release, we'd have liked explicit confirmation that there are keyboard improvements beyond quieter typing, even if framed as a response to customer concerns. Something like "while the failures are only affecting a very small percentage of customers, we're doing the right thing and have made further enhancements" with the de rigueur marketing speak after it.

But, we didn't get that. And we probably won't.

Three months later

When we first published the numbers, there was no solution to the problem other than an expensive repair for machines out of warranty costing users right around $480 for an entire upper case assembly. Two months after our report, Apple launched the service program providing not just free repairs for it, but refunds to repairs already made. It is an adequate solution to a bad situation.

It appears that they are using improved keyboards in the program —and may have been for some time —even if that redesign is not quite up to the lower failure rate on the earlier model.

We're glad for the program, and the improved keyboards across the board that started getting used at some point for the repairs. But, we're still not happy that it is a problem at all.

Some of this issue is a perception one, exacerbated by the Apple echo chamber. Apple's "small percentage of users" afflicted by the problem still adds up to tens of thousands of complaints and service calls. This is then amplified by social media —which is the main reason why we collected the hard data in the first place, to see if there was actually an issue worth discussing.

It turns out there was a problem, and is worth discussing. And, it is one worthy of a repair program. But, it is not an "epic fail" or any other declaratives that we've seen lately. Headlines like "The new MacBook Pro keyboard is ruining my life" remain hyperbole out of proportion to the actual issue.

While other venues are lamenting the lack of hard data, we can confirm that the keyboard failures are indeed technically a "small percentage." At the same time, the 2016 model generated double the service calls for the keyboard itself, completely obscuring the fact that the machine is more reliable overall than predecessors.

Couple the echo chamber effect with the polarizing nature of other changes made in the MacBook Pro like USB-C Thunderbolt 3 ports, and the Touch Bar, and it makes a bad situation worse from a PR perspective.

From a user perspective, for now, AppleInsider recommends that if you've got the problem, go get it fixed. It's free, after all. If you're getting it done with the myriad of shops that we're working with, we'll count it.</span>

Let's block ads! (Why?)

Siemens&#039; autonomous 1965 Ford Mustang is a horse that can&#039;t be tamed

Posted: 13 Jul 2018 04:18 AM PDT

Siemens staged an unlikely (and unprecedented) marriage between classic cars and autonomous cars at this year’s Goodwood Festival of Speed. It sent a custom-built 1965 Ford Mustang retrofitted with a full suite of autonomous technology to compete in the annual event’s famous Hillclimb. Unfortunately, the prototype’s first run didn’t go as planned.

Footage showing one of the Mustang’s first autonomous runs up the hill reveals it’s not ready for prime time yet. The prototype sets off at a glacial pace with four passengers on-board and immediately starts zig-zagging across the track like a ping pong ball. The safety driver behind the wheel takes control several times during the run to prevent the car from driving into the hay bales on either side of the track. Siemens hasn’t released information about what happened yet. We contacted the company and we’ll update this story if we hear back.

The German firm explains it designed the Mustang with the help of Cranfield University, a science and engineering school in England. Though Siemens hasn’t detailed the precise type of hardware and software it installed in the Mustang, it notes it used location scanning technology provided by Bentley Systems to create a 3D scan of the track and load it into the car’s onboard computer. In other words, the Mustang doesn’t scan the road ahead; it know where it’s going ahead of time because it simply needs to follow preprogrammed instructions — at least in theory.

This important distinction explains why the car looks largely stock. Most autonomous prototypes (like the ones built by Waymo, and Uber) are festooned with bulky radars, cameras, and sensors that scan what’s ahead, analyze the data, and react appropriately. In contrast, the Goodwood-bound Mustang only stands out from a regular-production model with small, beer coaster-sized sensors on the hood and on the trunk lid.

Though we don’t have technical details, the chromed 289 emblems on the front fenders suggest the Mustang uses a carbureted 4.7-liter V8 engine. It makes either 200, 225, or 271 horsepower depending on its state of tune — Ford offered all three in 1965. It presumably shifts through the optional three-speed Cruise-O-Matic automatic transmission, which was only available with first two variants of the eight-cylinder. But considering the Mustang is now autonomous, nothing guarantees Siemens retained the period-correct engine and transmission combination.

Siemens’ autonomous Mustang is scheduled to race up the Goodwood hill twice a day from July 12 to July 15. Cameras inside and out will stream each run to screens scattered across the vast outdoors event.

In recent years, the Hillclimb has morphed into a stage where companies from all over the automotive spectrum strut their stuff. Spectators can check out a dizzying array of machines including the Volkswagen I.D. R that recently set a new record at the Pikes Peak International Hill Climb, the record-setting Porsche 919 Evo, classic Formula One cars, and regular-production models.

Editors' Recommendations

Let's block ads! (Why?)

This post have 0 komentar


EmoticonEmoticon

Next article Next Post
Previous article Previous Post