Things may have improved since the days of the iPhone 3GS, but there are much faster ways to achieve the same thing. A full-screen fade was impossible, because the engine was way too slow. I actually made one of the first iPhone apps using Flash, and you can still download it today if you want:Īuthoring in Flash is simple for simple apps, but the moment you want to do serious animation, it all falls apart. It's worth noting that you can still use Flash to make iOS and Android apps - you can export direct from Flash Professional and have been able to since Flash CS5. It's a real shame that transparent video was lost in the mix, though. HTML5 can do almost all the animation that Flash did, JavaScript can handle the compute side, and browsers play back H.264 video much more efficiently. If you have to re-architect your code to avoid hover and avoid the keyboard, there are better technologies to use. Many Flash interfaces use hover in one way or another.Ģ. It was the biggest security hole, had poor performance on anything but Windows, poor battery life if you left Flash running, hardly anyone bothered with accessibility in Flash, but none of that was the reason it doesn't work properly on touch devices. But it wasn't entirely Steve's fault that it got killed. I have a bit of a soft spot for Flash - the first app I taught was Flash 2. Though I still create presentations with it for people who want more than powerpoint can offer.*** OFF TOPIC I spent years learning Flash, and Steve Jobs pretty much killed it overnight. It was really fun integrating video into Flash - you could do some amazing creative things. I really like media encoder for the occasional flash/SWF project when I need a strange frame size - it can really deliver a small file with good quality, too. They seem to have included auto-sharpen as part of their encode, at least during the past, and it's fast, using all the cores your machine has. Though I prefer FCP X, I do like Adobe Media Encoder for final encodes. Doesn't help if the client wants text changes, but great for showreels and an emergency backup. Just my workflow, YMMV.Yes, good idea, I always keep a ProRes archival master. And I can keep a library of recent edits on-line - you never know when someone wants you to quote on a gig and you think "wow, I did something just like that" and have it right at hand. restoring the whole project from archive and re-working it. If a month or year down the road the client needs a new copy, or just wants a section chopped out, keeping the final ProRes is really handy vs. Consistently smaller files and way-faster renders that going H264 from FCP. file size, super-fast, and no messing with compression settings. Not the smallest file ever, but a great level of quality vs. QT player does a great job of compressing. ![]() When the final looks good, I can do a 720 or 1080 H264 for final use (90% of my stuff ends up on the web or a tradeshow or lobby screen).Īnd, for almost every case where I deliver for non-broadcast, non-blueray. Even if clients want to see a 720, I still save-as from QT player - it's lightning fast (compared to a timeline render). Every approval edit seems to save me a good hour between renders and uploads going this way. (Just today's project: about 8GB 1080 ProRes, 100mb 480 H264. I may have 3 or 4 480p approvals before the final, so it's a quick way to keep things moving. I usually open the pro res edit in QT player and save-as 480p for a quick approval upload, mainly so clients can see edit decisions, color, etc. ![]() Rendering a ProRes 1080 timeline out to Pro Res 1080 seems to take about 1/4 the time as H264. I consider it my archive copy for compressing, scaling, etc. I'm on a Mac using Premiere Pro CC, editing clips shot with my Pocket in ProRes format.Įvery final edit I render out from FCP goes to Pro Res. The file sizes vary with the ProRes HQ being about 6x as large. I've tried all 3, uploaded to Vimeo and can barely tell the difference but the ProRes HQ seems to have fewer artifacts. Quicktime, selecting Apple ProRes 422 (Proxy).Quicktime, selecting Apple ProRes 422 (HQ).H.264, selecting a high bitrate like 20MBPS.When you're ready to export your movie do you export as: I've read on various sites and forums that some people prefer to export their movies as ProRes and not to have their NLE compress it using H.264, especially when there's film grain applied that may get lost during the H.264 encoding with the editing software. ![]() I'm looking to maintain as much of the clarity and quality of the original video I shot and want to minimize the # of times my final movie is compressed, knowing that uploaded movies to Vimeo and YT will be compressed. Question for those of you out there that have uploaded your videos to Vimeo/YT.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |