Monthly Archives: August 2015

Ad Security In iOS9 – No Thanks To Google

 

I will always endeavor to refrain from foul language here, but I almost didn’t make it this time. Yeah, sure, it makes sense that Google recklessly advises app developers on how to disable ad security, and then, after a backlash that they labeled, “… important feedback …”, they proceed to backpedal and minimize their “advise”. What does Google care, as long as their apps are on everything so they can sell page/time/clicks, it’s no real concern of theirs. The far more appropriate thing to do was refer developers to Apple’s Ad Security documentation, where, they will/would’ve learned the same thing, but in a way that let’s the developer know that this should really not be worked around, and if worked around, it should only be done so as an absolute last resort.

Dumped Google, everything, two years ago and have not missed a thing, except the very freaky experience of having general web page browsing load up a page full of ads pointing me to web sites that sell the same product or service I just bought somewhere else. (By the way, what’s that good for again?) Sheeesh! (Sheeesh isn’t a bad word is it? Foul lingo comes as naturally to me as breathing.)

iPad Pro – Just Put A Keyboard On It …

 

I’m sorry but seriously – Just put a detachable keyboard on it and face the fact that you’ve got a laptop there – not an iOS device. I’ll even overlook the fact that Microsoft’s already done it – the detachable keyboard – and trust that Apple will get it right. What’s the point? With the work that’s undoubtely going to get done on such a device, a keyboard is only inevitable. Make a MBP and add touch screen, and you’ve got a complete – um, portable computer. The iPad Pro is going to be a laptop with touch screen + keyboard – simple as that.

Next Apple TV Wish List

 

I think the published list covers all the realistic ones I can think of. It might be worth Apple’s time to at least consider providing a USB port that allows for Amazon Fire and Google’s thing, just to make it more hub-like. The big ones for me are, way better performance, (let’s get more precaching of screens and etc.), and 4K. And, as always, if Apple continues down the “streaming” path, please still allow purchase as you go without subscription required – please.

In-App NLE Notes

 

I think it’s a no-brainer. Being that FCPX happens to be my weapon of choice (the others are good too, and yes, even better at some things), I will speak to that. It’s so nakedly metadata oriented that having a full-fledged note pad built into it was something that I literally went looking for after the first couple of releases – I just thought, “… it’s gotta be in there somewhere …”. Well, it turns out there is a note field of sorts available, and after doing some research sometime ago, I think it has a fairly large character capacity. Of course, what you’re wanting is something that is more tightly integrated with the other relevant metadata of Libraries and Projects, and even the clips themselves. Add a simple but highly functional UI and we’re onto something. One of several features I’d like to see implemented in this scenario is, when the play head reaches a point or range of time where a note has been added, I’d want the ability to toggle on/off on-screen display of those notes. FCP7 kind of did this, showing on-screen (on the Canvas) whatever text had been added to a marker. Seems the infrastructure is there in FCPX, it just needs to be developed. It’s a good idea, and I might argue, an important one.

@JCalMN New Apple Music Commercials, and no … No more subscriptions for me.

No subscriptions for me. Looks good though, and I think Apple’s approach, implied in the new commercials, will go a long way to getting new artists discovered. … I’m simply not going to do yet another $10/month subscription … to anything, and I’m beginning to clean out the few that I have. The day I completely lose access to Apple media content because I’m forced to have a subscription … well, it’s going to be a sad day indeed.

@iMore – Faster, Harder and Stronger!

 

To quote one of my favorite Naturopaths – “Faster, Harder and Stronger!”

Plus, very water resistant, and, wireless charging – and not wireless dock charging – I mean wireless charging. (I don’t have to drop it on a proprietary, uh, dock, it just has to be x-number of inches/feet from the charger thingy.)

Oh! And, small please.

THX! @Alex4D – FCPX TC Overlays

 

Thanks @Alex4D! This is very cool and badly needed in our FCPX workflow where I work. For now I’ll be the only one using it to be sure it doesn’t break anything that might be vital, but I look forward to implementing this for all seven edit bays once the dust settles with all the new Apple stuff coming out this Fall.

For whatever it’s worth: I tried this in El Capitan on my home computer, (after making, renaming and relocating a copy of the FCPX app.). Works like a charm. I stacked up to 10 video clips and the Overlay showed up for each one, including a few audio-only clips. I was curioius to see how it would handle a Multicam Clip, so I experimented with that a little too.

Once you put the Multicam Clip on the timeline the TC Overlay only indicates where the playhead is on the timeline. I haven’t decided how important it might be to see the TC of the embedded clips in the Overlay, but I can immediately say that it would be nice. If you double-click on the Multicam clip and expaned it on the timeline you will then be able to see the TC of each clip in the Overlay, which, is great in those instances where one or more of the clips is just a bit off. It can also be useful on those rare occasions when you want to manually add more clips to an existing Multicam Clip and not all of the camera TC matches for the same Scene and Take.

The Age of Small iPhones

 

With regard to phones I’m pretty sure, along with many others, that Apple’s not going to release a small phone this year, and that’s too damn bad. But, if correct, that means I have another year to save up for Fall of 2016’s new releases. Unfortunately, I think that any future “small” iPhone gear will feel a lot like getting an iPod Touch – the hardware specs will intentionally be a step behind whatever their current-year, new releases will be – that always drove me nuts using an iPod Touch – but, in the end it worked, Apple got me to buy an iPhone 5S with their antics … I mean, strategy.

All of that is to say, I fear the age of small phones is gone and I will be compelled to get a monster phone by this time next year if I want to upgrade. I’m a performance-driven user of all things Apple. When I upgrade I’ve got to have the latest CPU, maximum RAM, best video components, screen technology and etc. Besides needing the performance in my reality, it dramatically helps downplay hardware obsolescence over time.

So, I’m going to spend the next thirteen months getting use to the idea of carrying around a monster-sized iPhone. When I pickup the phone and look at the big, beautiful screen, and luxuriate in the responsivness of the UI, I will have absolutely no issue, but, when it’s time to put it away and hit the road, in the pocket it will not go. That means, back on the belt, (which I came to really loathe), and, I just don’t do the back pocket – just don’t.

 

Life is tough – isn’t it?!

Allowing Comments and Reviews While Beta Testing

As I get ready to start a new week there’s something I remain troubled by. Early last week I began to notice on certain support web sites, which will remain nameless, rather severe reactions from developers toward some of its users who are using beta versions of the upcoming iOS or Mac OS, who merely attempted to notify fellow users that the beta versions of these OSes render the developer’s application unuseable. In several of these cases I noted that the user attempting to post the notice made it perfectly clear that the notification was not a review or a criticism, only a notification to those who may be contemplating trying the beta versions of Apple’s OS(es). The barely polite chastisment by the development company’s moderator, of the enlightened user, was surprising to me and it has continued to trouble me off and on throughout the last week.

Apple itself has disabled their Review function on their app stores if the store senses you’re using a beta version of the OS. (I don’t remember if this was the case during the OS 8 beta.) In short, I get it. Prior to last week I found myself endlessly frustrated with individuals who were running beta versions of one or more of Apple’s OSes and proceeded to give soaring criticisms of how bad the OS was, or the app, or both. I’m reminded of the scene from the first Jurassic Park movie where the nefarious genetic engineer comes face to face with a smallish dinasour, and while holding a stick in his hand says something like, “… see the stick … it’s a stick, stupid.” Well, if my admittedly rough analogy holds any water at all, then I’ll leave you to make the final connection. If I were a software developer this kind of thing would be frustrating, at least.

So heres the “but”: I wanted to give the current public beta of iOS 9 a go, but, there are one or two iOS apps that are fairly important to my daily life and I didn’t feel I could afford to lose their functionality, so I went looking for information that might tell me if these apps were going to break if I installed the beta iOS. Ultimately, the virtual censorship that is going on by Apple and by app developers disallowed anyone from openly sharing that information. I find this disappointing, even irkesome. I totally get that no one in their right mind should judge an OS or an app in its beta phases – that’s easy, but I believe there needs to be some appropriate culpability by the developers toward users of their products. I’m not referring to a developer just sayng their product won’t work under the beta OS, whether or not they’ve actually tried it, just to cover their hides, I’m talking about developers at least opening their app with each beta iteration and posting the results for all to see, so that users can gauge for themselves how much of a risk they’re willing to take.

Personally, I like being able to take part in public betas, but, it has become hard to assess reasonable risk, because from where I sit, app developers are unwilling to cooperate with users who wish to do so. I don’t believe it would cost developers anything in time and effort to use their support pages to post a simple set of results along with the obligitory and inevitable reminder that, users always use their products at the user’s own risk, and all the more so if you’re using a public beta of the OS.

Rather than censorship maybe there needs to be some basic public education about what a beta version of any software really is, combined with examples of what reasonable expectiations might be. There also needs to be voluntary and full disclosure by developers as to whether or not their product is going to be unuseable with a public beta version of an OS. This whole concept can still be really good, but there’s clearly a communication gap between app developers, Apple and end users.

Apple’s Video (Pro) Application Priorities

Apple’s video application priorities – Alex4D http://t.co/g1X1geua76

 

Sometimes I think that Apple is so torn between providing professional solutions, using their hardware, and competing in the consumer market place, that I think they should either farm out their pro software solutions or create a professional corporate branch. Maybe this will happen with some of the things I’ve been hearing about the Apple/IBM collusion, but something tells me that IBM is not going to jump into the media production market place. They’ll sell Macs with software to the accounting departments of these institutions, but probably are not going to sell FCPX along with network management solutions for that product.

 

Reading Alex’s take on Apple’s job openings just leaves me with more questions about whether or not Apple is ever going to take its professional users seriously, permanently.