Return-Path: Received: from mail-ie0-f174.google.com ([209.85.223.174] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4968322 for AE-List@media-motion.tv; Tue, 05 Feb 2013 19:20:27 +0100 Received: by mail-ie0-f174.google.com with SMTP id k10so641753iea.5 for ; Tue, 05 Feb 2013 10:26:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=rCVsrCmx4XQCLbqh0bCUHBvbP24Ez5FjhkXmp4GogEI=; b=Xms4txSw4vFJ2RH27uIKTW1jZJsXdmxWQ3PZehzJl0k0Gwk1weMR5KZ/X7pXJE7YZj KRGoCroDfttFXdi9NhPTN8RR5fGm7eW02VPMxMnTuupU2HDRsF7znuEdqHIoqMKQQjJH VAQVkLXAQsWC2S6Flkkvz9/XK7JHGt3kq3rkmHZ0vGbE4i9wu+2jHbVpjgI3wWFRhBB/ uFKXqp46IU6z2DTE4N8pgsrnb+WJV0BgXTtz/TSoyjNmBeIVvw2yXf7QZqp/L8e8f+Su vC4g+FFzk9RGpVhY522vOjB6GdTtCJ7+HuyyvmvUt+32sj6uvnmJFMx/T1FdLLhaCU5b /oOw== X-Received: by 10.50.88.226 with SMTP id bj2mr14966282igb.105.1360088778891; Tue, 05 Feb 2013 10:26:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.9.82 with HTTP; Tue, 5 Feb 2013 10:25:58 -0800 (PST) In-Reply-To: References: From: Walter Soyka Date: Tue, 5 Feb 2013 13:25:58 -0500 Message-ID: Subject: Re: [AE] New MacBook Pro To: After Effects Mail List Content-Type: multipart/alternative; boundary=e89a8f3bb01f87615e04d4fe586b X-Gm-Message-State: ALoCoQkNRzgaPFHCmkU3ZhaYEQ+SgAm4Gz6ELXRjQI1omjiJec/sVT/R9aCtheDMTwcv3M6fLKym --e89a8f3bb01f87615e04d4fe586b Content-Type: text/plain; charset=ISO-8859-1 I've been working cross-platform for about a little over a year now. Once you work through a couple issues, it can be very doable. > that "other than a few codecs" is a HUGE problem for me. not being able to > write prores is a real show stopper. I've messed with DNxHD and its not > been terribly happy because the codec has 2 color spaces and its a bag of > hurt when apps don't write / read the color space correctly. basically part > of my normal workflow is completely broken. TGA or TIFF sequences or > uncompressed QT's via AJA or BMD codecs are just not workable for work > beyond spots. I like CineForm for my own cross-platform intermediates (when I don't use image sequences, though these are usually an important part of my workflow for other reasons). Grass Valley HQX is another alternative. Though most of my deliverables now are H.264 MP4s or MPEG-2 for playout, I do also continue to deliver ProRes from my Macs. I've also tried delivering ProRes from my PC via ffmpeg/ffmbc, both of which have more user-friendly front-ends available, and it does work. then there are the win7 networking problems. not sure if they are fixed in > win8 or not... but not having network discovery work is a big deal. > basically win7 refuses to see any linux or OS X SMB shares. probably having > to do with homegroup vs workgroup and MS deciding to "correctly" implement > some part of the spec they hadn't of before breaking everything... typical > MS. while AFP works on linux and its free I don't know of anything on win > to do the same. kind of suprised that the coders who wrote AFP for linux > didn't port it to Win. Actually, I think that Apple is pretty guilty of playing fast and loose with SMB at the moment... While Win7 and Mac OS X Snow Leopard (10.6) should play really nicely together out of the box, on higher versions of OS X (10.7 and above), Apple replaced samba (the open-source SMB protocol implementation) with their own implementation -- and I've found it pretty unreliable. I highly recommend SMBUp (http://eduo.info/apps/smbup) to restore samba on OS X 10.7 and higher so that everyone can play nicely together again. On previous versions of OS X, I seem to recall you may need to use a lower encryption level on the Windows side. On Win7, hit the Start button and type "Manage advanced sharing settings" (it will search as you type, you don't need to complete the whole text string). Open this. Under File Sharing Connections, choose Enable file sharing for devices that use 40- or 56-bit encryption. I'm not seeing any issues with network discovery here, but I manage all my IPs and hostnames on my router -- maybe that makes a difference? Walter Soyka --e89a8f3bb01f87615e04d4fe586b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I've been working cross-platform for about a litt= le over a year now. Once you work through a couple issues, it can be very d= oable.
=A0
that "other than a few codecs" is a HUGE problem for me. not bein= g able to write prores is a real show stopper. I've messed with DNxHD a= nd its not been terribly happy because the codec has 2 color spaces and its= a bag of hurt when apps don't write / read the color space correctly. = basically part of my normal workflow is completely broken. TGA or TIFF sequ= ences or uncompressed QT's via AJA or BMD codecs are just not workable = for work beyond spots.

I like CineForm for my own cross-platform intermediates (when I don'= ;t use image sequences, though these are usually an important part of my wo= rkflow for other reasons). Grass Valley HQX is another alternative.

Though most of my deliverables now are H.264 MP4s or MPEG-2 for playou= t, I do also continue to deliver ProRes from my Macs. I've also tried d= elivering ProRes from my PC via ffmpeg/ffmbc, both of which have more user-= friendly front-ends available, and it does work.


then there are the win7 netw= orking problems. not sure if they are fixed in win8 or not... but not havin= g network discovery work is a big deal. basically win7 refuses to see any l= inux or OS X SMB shares. probably having to do with homegroup vs workgroup = and MS deciding to "correctly" implement some part of the spec th= ey hadn't of before breaking everything... typical MS. while AFP works = on linux and its free I don't know of anything on win to do the same. k= ind of suprised that the coders who wrote AFP for linux didn't port it = to Win.

Actually, I think that Apple is pretty guilty of playin= g fast and loose with SMB at the moment...

While W= in7 and Mac OS X Snow Leopard (10.6) should play really nicely together out= of the box, on higher versions of OS X (10.7 and above), Apple replaced sa= mba (the open-source SMB protocol implementation) with their own implementa= tion -- and I've found it pretty unreliable.

I highly recommend SMBUp (http://eduo.info/apps/smbup) to restore sa= mba on OS X 10.7 and higher so that everyone can play nicely together again= .

On previous versions of OS X, I seem to recall you may = need to use a lower encryption level on the Windows side. On Win7, hit the = Start button and type "Manage advanced sharing settings" (it will= search as you type, you don't need to complete the whole text string).= Open this. Under File Sharing Connections, choose Enable file sharing for = devices that use 40- or 56-bit encryption.

I'm not seeing any issues with network discovery he= re, but I manage all my IPs and hostnames on my router -- maybe that makes = a difference?


Walter Soyka
--e89a8f3bb01f87615e04d4fe586b--