Tag: error

[SOLVED] Premiere Pro: “The importer returned a generic error” when loading media

Posted on by Jody Bruchon

(Fellow video dudes: while you’re here for help with Premiere Pro’s bad behavior, maybe you’d also be interested in my article about why you shouldn’t be shooting with flat, log, or “cinema” picture profiles. It’s the second most popular article on the site. The one on disabling Adobe’s ever-growing log files might also be of interest.)

I recently had a Premiere Pro project I’d been working on for a couple of weeks that refused to import some clips. When I attempted to link the media again, I’d get a box that said “the importer returned a generic error.” What’s especially annoying is that the failing clips were from the same camera as several successful clips; there seemed to be no reason for these three or four clips to simply not work and I could play them in a media player just fine. The failure didn’t even happen after an update because I’d been working in the project using the latest updated version.

I checked file permissions on the network server and everything was good.

I deleted all of the Adobe caches and manually killed all Adobe processes in Task Manager.

I restarted the computer and even tried opening an auto-save of the project, yet all of these failed to resolve the problem.

Adobe suggests that these generic errors on import can be caused by activation issues, so I signed out of my Creative Cloud account and signed back in. Didn’t work.

In the end, what I had to do was open Creative Cloud, uninstall Premiere Pro (keeping preferences), and reinstall Premiere Pro. No reboot needed! I still don’t know why this worked, but it did. Maybe my experience and solution will save you some valuable time troubleshooting this odd error.

Did you open your Kodak EasyShare camera and now it says “high camera temperature?”

Posted on by Jody Bruchon

I recently got my hands on a Kodak EasyShare Z730. It’s actually a really neat little point-and-shoot from 2005.

I originally bought this cute little camera for $25 with the intention of converting it to full-spectrum (infrared) but it didn’t focus at all with the hot mirror removed. Unfortunately, I “broke” the camera while reassembling it the first few times because I didn’t push a flat ribbon cable all the way in. The camera would power on, then report “high camera temperature” and shut down. As it turns out, the flat cable that goes to the top board in the camera has two levels of contact pins and is pretty hard to get all the way in. I had actually failed to reconnect it properly and as a result the camera thought it was overheating. Once I realized that the end of this cable had multiple levels of pins and it obviously wasn’t in the socket far enough I was able to fix it. Obviously the camera’s temperature was never the real issue.

This camera is 13 years old as of this post, but I hope that anyone else who tears into a Kodak camera and gets this error message will be helped by it. Please leave a comment if this helped you!

[SOLVED] Netflix DRM errors with HTTPS Everywhere or NoScript installed

Posted on by Jody Bruchon

If you are using Firefox and certain security, HTTPS, or script blocking  extensions, you might not be able to use Netflix and get a “Digital Rights Management (DRM) error” such as N8156-6003, N8156-6013, N8156-6023. Many websites say that the solution to the problem is to delete the file “mspr.hds” located at %ProgramData%\Microsoft\PlayReady, but this does not always work because this isn’t always the underlying problem.

The problem is caused by scripts from microsoft.com required to use Silverlight DRM not loading properly. The fix is simple and does NOT require disabling NoScript or HTTPS Everywhere nor does it require restarting Firefox in Safe Mode just to watch Netflix. Make sure that you’re already allowing scripts to run from “netflix.com” and “nflxext.com” as these are also required for Netflix.

For NoScript, visit microsoft.com, open the NoScript menu, and choose “allow microsoft.com” from the list.

For HTTPS Everywhere, open the Add-ons Manager (usually under the Firefox menu, or under Tools -> Add-ons) and beside HTTPS Everywhere, click “options.” Type “microsoft” in the Search box. Look for “Microsoft (partial)” in the list and click the green check beside it to change it to a red “X” instead.

If you are running other script blocking software or extensions, you should be able to find a way to both unblock scripts from as well as don’t force HTTPS on the domains netflix.com, nflxext.com, and microsoft.com.