BobbyCiraldo.com

the “interpretation rules.txt” and Avid 23.98 exports

admin — Mon, 24 Jan 2011 06:09:10 +0000

I had to figure this out again and here’s what I don’t want to forget for next time:

720, 480, 23.980, "MooV", "AVdv" = 40/33, *, 23.976, *, *, *

The above line, when added to After Effects’ “interpretation rules.txt” file, will force quicktimes exported by Avid erroneously as 23.98 FPS to be correctly interpreted as 23.976 FPS.

It also forces the interpretation to be D1/DV NTSC Widescreen (40/33, or about 1.2121) because I am mainly working on stuff shot with an anamorphic lens on the panasonic DVX100a. This may not always be the case, and I have to remember to re-interpret as standard 4×3 if importing that type of stuff.

Open a new Finder window from a Terminal window

admin — Tue, 21 Dec 2010 02:31:15 +0000

It’s easy when you know how: just type

open .

Xcode can’t debug iPhone 3G

admin — Tue, 21 Dec 2010 02:27:14 +0000

Note to self:

http://stackoverflow.com/questions/4432886/jailbroken-iphone-3g-with-ios-4-2-1-cant-be-debugged-with-xcode

Mac OS X Terminal Application Slow to Start

admin — Tue, 21 Dec 2010 02:25:30 +0000

I think this solution has worked for me in the past, and I want to remember where it is:

http://www.webapper.com/blog/index.php/2009/03/26/consoleapp-freezes-on-launch-terminalapp-slow-to-launch/

Looping movie playback on the iPhone

admin — Wed, 16 Dec 2009 19:42:36 +0000

Note to self:
http://benbritten.com/2009/03/01/looping-movie-playback-on-the-iphone/

Quantum Jump – “Lone Ranger”

admin — Tue, 08 Dec 2009 03:04:25 +0000

[youtube]http://www.youtube.com/watch?v=hchOYs_d_Bw[/youtube]

thanks joe.

Say You'll Be There

admin — Sun, 06 Dec 2009 09:36:06 +0000

http://www.youtube.com/watch?v=ynBtZqurKaQ

I'm Testing Out Google Voice.

admin — Sun, 06 Dec 2009 05:34:30 +0000

…and here’s what it transcribed:

Hello, Hi. This is Bob Easter. Although I’m calling to leave a message to myself to test out the new google voice voicemail and voicemail transcription and I’m nah. Talking too fast. At this point in time because I am trying to go easy on it but and I think I might try to talk a little faster and morning. What might seem like if I talked with fast or if I can really understand people want to talk about. Okay. Well let’s see what else is there a to be here. Not to be that is the question whether it’s his noble er in the Marin to sell for the siblings in arrows of outrageous fortune, or to take arms against the see if please. And by opposing and, to die to sleep, no more, and by asleep to say we and the 1,000 that roll past that flashes there too. There’s a confirmation does that lead to be wish the guy to sleep to sleep per chance to drink. If there’s the rub. Goodbye.

Final Cut Pro: Dip-to-Color Vs. Fade-to-Color

admin — Tue, 24 Nov 2009 06:20:14 +0000

In Final Cut, sometimes you want a clip to fade in or out from a specific color. Like white, say. If you’re just using a single layer, you should use the Dip-to-Color effect. But the problem is that you’ll see the color in the middle of the transition, as opposed to the beginning or end like you’d expect. In order to fix the situation, just change the ‘Start’ or ‘End” parameter of the effect to be 50%. That’ll basically convert the ‘Dip-to-Color’ into a ‘Fade-to-Color’. Who uses a Dip-to-Color anyways?

From SiteGrinder to WordPress

admin — Sat, 15 Aug 2009 09:55:35 +0000

I’d like to jot down some experiences using SiteGrinder 2 and how one might integrate it into a WordPress theme. Specifically I am interested in using SiteGrinder’s “-grow” hint to allow for WordPress content. So far my experience has been that it’s a slightly challenging maneuver.

This is still REALLY rough, but here’s what I’ve discovered so far. My overall plan involves modifying an existing WordPress theme so that the WordPress header and footer are more or less replaced with the SiteGrinder header and footer. You can also do this with SiteGrinder’s -xmedia hint and the “require PHP” option, but I’ll save that for another post.

Steps

Design a site in Photoshop. Think in terms of (a) the stuff at the top of the page, (b) where the WordPress content will go, and (c) what stuff will get pushed down when the WP content grows.
Draw a text box where the WP content in its own layer. Add the hints “-text” and “-grow” to the end of this layer’s name. Layers with content above this text box will not get pushed down with the WP content. Also, any layers with stuff that vertically intersects this text box will not get pushed down. But any layers with stuff below the text box will get pushed down as the WP content grows. Put the text “FOO” in that text box.
Run the SiteGrinder plugin and build the site. This will give you (a) an HTML file named after your photoshop file, (b) a common.css file, and (c) a media folder with all your SiteGrinded images.
Install a simple theme on your WordPress site. We’ll remove the header and footer, so pick one based on the middle bits. Or duplicate one of the default themes and edit the top comments of “style.css” in order to give it a distinct theme name.
Upload the media folder and the common.css file to the theme’s directory on the web server.
Open up the WP theme’s header.php file. Add a link to the new common.css file after all the other .css includes. You know, something like:
Open the SiteGrinder HTML file and copy the code beginning from (but not including) the tag, through to the word “FOO”. Back in header.php, paste in the SiteGrinder html you copied, right at the end of the file.
Disable the theme’s header elements by enclosing them in comments: Leave in the container, content divs?
Open footer.php. We’re going to copy some more code from the SiteGrinder html file, so make sure that’s open too. Copy the SiteGrinder html from the text “FOO” through to just before the tag. Paste it into footer.php at the top of the file.
Disable the theme’s footer elements with comment brackets.
In some case you may have to change the name of a SiteGrinder div such as “footer” if the name is already in use in the php file. Make sure to change in the common.css file too.

Still Very Rough, not meant for actual use yet.

Special Note to frustrated users of require PHP! If you can’t figure out where the option to choose “require PHP” is, then you’re like me and probably wasted shit-tons of time searching the forums for where it is. You click on the thing everyone tells you to click on, but all it says is “No Match”. WTF? Well, it turns out you have to type the name of a php file (eg, “wtf.php”) into the text field first, followed by clicking Update. Then everything changes, and “require PHP” is automatically selected. Pretty intuitive huh?! No, not really. YAY!