lorin schultz


lorin schultz
Last Active
  • Apple releases iTunes 12.5.5 with minor performance improvements

    Soli said:
    I did have an issue with the previous update where editing metadata in Get Info would take upwards of 5 minute to complete. I hope that this is resolved for me in this update.

    edit: Issue still exists. I wonder if it's because I used CoreServices to encrypt an external RAID of HDDs in which my iTunes Library resides.

    It's not your encrypted RAID. I have the same issue.
  • Apple says hidden Safari setting led to flawed Consumer Reports MacBook Pro battery tests

    3. According to APPLE, not CR, the problem is the result of a BUG, not the testing methodology per se. The testing method merely exposed it. How long would it have gone on unnoticed and unfixed if the test hadn't uncovered it? It may not have affected me or you, but obviously some people would suffer from it. This is a positive outcome.

    Actually I think Apple blamed both the methodology and the bug. See their statement:

    “We learned that when testing battery life on Mac notebooks, Consumer Reports uses a hidden Safari setting for developing web sites which turns off the browser cache. This is not a setting used by customers and does not reflect real-world usage. Their use of this developer setting also triggered an obscure and intermittent bug..."

    Note that they use the word "also triggered" the obscure bug. "Also", not "subsequently" triggered the bug. Right or wrong, they seem to be saying both conditions are responsible for the results.
    Noted. However, Apple's argument that the test doesn't reflect "real-world usage" is largely irrelevant in this context. What CR was doing wasn't "real-world" use, it was "testing." Testing requires controlling variables. Since caching is unpredictable, it was disabled. I would have disabled it too.

    Also, if the testing method were the cause of the reduced battery life, the battery life would have been short every time. It wasn't. There were huge variations. Since the testing method didn't change, it CAN'T be the source of the issue. The bug, on the other hand, according to Apple, is intermittent. That WOULD cause the results to vary.

    So absent any obfuscation caused by phrasing, intentional or accidental, simple deductive reasoning demonstrates that the outcomes were the result of the bug and not the testing method.

    If the bug is only evident when caching is defeated (which they haven't explicitly said) then maybe the battery issue wouldn't actually affect most users, and that's a valid objection. I just don't think it's fair to accuse CR of flawed testing when what they did actually makes sense.
  • Apple says hidden Safari setting led to flawed Consumer Reports MacBook Pro battery tests

    To those bashing Consumer Reports for what they perceive to be flawed testing:

    1. OF COURSE they disabled caching. It's a test of battery use while surfing. To make the test consistent and repeatable across multiple runs and various models, the test involves having the machines continuously load content from a fixed set of sources. There wouldn't be any point to the test if it only involved downloading the content once then storing it.

    2. The results VARIED. This wasn't a case of an artificial test that doesn't reflect real-world usage making the battery life seem worse than it would be in actual use, it was a case of sometimes the battery lasting a long time and other times running dead very quickly. Since the test was the same every time, the huge variations in results were a legitimate cause for concern, REGARDLESS of the testing method.

    3. According to APPLE, not CR, the problem is the result of a BUG, not the testing methodology per se. The testing method merely exposed it. How long would it have gone on unnoticed and unfixed if the test hadn't uncovered it? It may not have affected me or you, but obviously some people would suffer from it. This is a positive outcome.

    4. Reports from others, including participants in this forum, outlining how their real-world use of the machines has resulted in excessive battery drain, show that the problem exists outside the circumstances imposed by CR's testing. CR did NOT run a flawed test and report erroneous findings. They reported, as have others, that there are still wrinkles to be ironed out.

    5. CR didn't say it's a crappy machine. They said it's a great machine with a really big "something's not right here." They were absolutely CORRECT.

    I'm lucky that I haven't had battery problems (so far, knock wood), but others obviously have, and depending on what's causing them, maybe it's only because I haven't yet done the things that cause the problem to surface and later WILL have a problem. I welcome any information that helps lead to a cure.
  • Apple MacBook Pro saves man from bullet in Florida airport shooting

    Mikeymike said:
    Disembarking is how you leave a transport vessel.

    Debarking is a canine veterinary procedure.
    Was going to say something similar.
    I point of fact, correct term is "deplane".
    Are you sure? I thought "deplane" is what Herve Villechaize did on Fantasy Island.

    tallest skilk2kw
  • Apple has 'great desktops' on Mac roadmap, CEO Tim Cook says

    nht said:

    No, they are not the exception.  Survey the list of successful directors and see how many attended film school.  This when making films was much harder than today.

    I wouldn't know where to begin to find such information, but I'm not sure it would necessarily invalidate my position anyway. How many among those who would consider film school are likely to become big Hollywood directors compared to the number who will happily and unceremoniously toil in the crew trenches? For the vast majority of those who will work in the industry, formal training is important.

    Even among successful directors who lack formal training, the ones I've worked with can be broken down into two categories:

    1. Those who recognize there are things they don't know and listen to those on the team who have expertise in areas she/he doesn't.

    2. Those who DON'T acknowledge gaps in their own knowledge who waste money pursuing impossible objectives or working inefficiently.

    The latter may not be an impediment to critical or financial success, but it is bad for everyone around them. They succeed IN SPITE of their shortcomings, not because of them.

    Regardless of outcomes, knowledge and understanding are almost never an impediment to productivity or success, whereas lack of them often is.

    nht said:

    Not going to film school isn't the same as not taking any training.

    Then maybe we don't disagree. Maybe I'm just not understanding what you're saying. What kind of training do you think people who want to work in production or post SHOULD be getting? If you're saying "on the job" is enough, I disagree. There are some things that are better learned in the classroom, and some are things many self-taught "pros" still get wrong.

    nht said:

    And by necessity you learn a lot by doing.

    Of course, and that's why the programs I've looked at include a lot of hands-on, jump-in-and-get-your-feet dirty practical training. The advantage is that the experience is gained with the added benefit of a guiding hand from someone with knowledge of the process.

    nht said:

    The guy that will be successful is the one that actually plays football a lot as opposed to sitting in a class and watching others play football and playing a game or two a semester.

    I think it's important to have BOTH. Just playing football won't provide nearly as much benefit as having someone who knows the game critique my actions so that I do better next time, teach me strategy so I can plan my actions in advance, and provide an understanding of what OTHER players are doing so that my actions support theirs.

    Some things are only learned by doing. Other things need to be taught in a classroom. Both are important. I can't tell you how frustrating it is to spend a large chunk of a very limited post schedule fixing bad audio that happened because the people in the field don't know anything about gain staging or how using their equipment differently would save time and money while also making the product better. They won't learn things like that in the field. That's book learnin'.

    nht said:

    Tell me...who teaches at film school?  Successful directors, DPs,, etc?  Folks who are actively working?  Or folks that aren't?  What practical training to they provide?

    Like anything else, I would imagine it depends on the school. If the example is Vancouver Film School, then yes, it is people who already are or were successful in the industry before/during their stint as instructors. I imagine the salary requirements to persuade people like that to teach are part of what makes tuition so expensive. So does having current equipment for the students to use.

    Even in cases where the faculty are not active participants in the industry, the degree to which it matters depends on what they're teaching. I know less than zero about what makes the difference between a crappy editor and a great one, but I am more than capable of teaching an editor -- newbie or experienced -- the dos and don'ts of good audio. Teaching story-telling and how to support the story with pictures and sound requires someone with expertise in that particular area, but knowing what various CODECs do and how various processes affect the material is stuff that can (and probably should) be learned from a techie, for whom extensive practical experience in the specific discipline is not particularly relevant.