This is from mid-December, but fairly typical of the meals we’ve been having around our house recently. Add a bowl of soup, and you get the picture!
Review: The Hobbit – An Unexpected Journey
In an effort to express my “anticipation level” for this movie, let me first point out that I read the book, “The Hobbit,” for the first time this Fall, and I re-watched the “extended edition” versions of “The Lord of the Rings” trilogy over Christmas Break (about 11 hours of content, give or take). It’s about as “prepared” as I could get. Having just read the book, I was at a loss to explain how exactly they were going to turn a relatively short book into another three movies.
Surprisingly, “The Hobbit: An Unexpected Journey” didn’t really feel all that long to me. Yes, it’s longer than it needs to be (running time is 169 min), but I’m honestly surprised that it gets you about a third of the way into the book, while also “filling in some gaps” that are left out, in tying it more closely with “The Lord of the Rings” (henceforth referred to as “LotR”…).
Perhaps I should back up a step. “LotR” covers the adventures of a hobbit, Frodo Baggins, and his crew as they attempt to destroy the Ring of Power so it cannot be used by the evil Lord Sauron to take over Middle Earth. Frodo obtains this ring from his uncle, Bilbo Baggins, but we aren’t really told how he got it, except that another character, Gollum, had it before Bilbo and desperately wants it back. The book, “The Hobbit,” was actually published almost 20 years before “LotR,” and it contains the back story for how Bilbo got the Ring. In movie form, it’s being presented as a prequel, even though the book was actually published long before.
To be honest, going through the story here isn’t going to be all that interesting. It follows the book, but also includes a few additional scenes with actors from “LotR,” including Ian Holm and Elijah Wood, and others from the movies. Unfortunately, in this case, they’re looking quite a bit older than they did in “LotR” (perhaps I did a disservice by re-watching them a few weeks ago…), even though in this film, they’re shown prior to the events of “LotR.” Ian McKellen also looks remarkably older, despite the presence of a huge beard, though it’s worse in some scenes and barely noticeable in others.
Generally speaking, the acting was great, the pacing was slow at times, but was far better than I expected, and the effects were spectacular. Seriously, they were good 10 years ago, but it’s noticeable how far the technology has come to the point where CGI and “real life” blend together better than before. Again, there really isn’t anything special to mention here as, if you saw the previous movies, you should know what to expect. Though, I should note that the CGI work on Gollum is pretty spectacular, and has really come a long way in 10 years. I’ve read some complaints (in relation to the “48 fps” debate…) about the quality of the makeup and the props though, personally, I didn’t think the effects in that regard were that bad. Maybe here and there, but certainly not offensive.
We saw the movie in 48 fps IMAX 3D, which is something of an “experiment” in modern filmmaking. Briefly, most movies are filmed/shown in 24 fps (“frames per second”), so this movie was filmed in twice that. This change has the effect of displaying more images to your eyes in the same amount of time, making all the motion look smoother and more vibrant, but also having the side-effect of losing “motion blur” that is sometimes helpful in disguising “plastic-y” looking props. Needless to say, film critics either love or hate this, depending on who you ask. If you ask me, I didn’t notice anything bad about it, yet then again, I was watching the movie “as the director intended.” It was good 3D, it didn’t hurt my eyes or give me a headache, and I thought the 3D effects were added in sparingly, yet effectively. If anything, 3D should be easier on your eyes at this frame rate. You don’t need to see the movie in 3D to enjoy it, but for my part, I just wanted to see it at 48 fps and see what the fuss is all about.
If there’s any problem I’ve got with “The Hobbit,” it’s that the story didn’t really “grab” me. I could say the same thing about “Fellowship of the Ring,” the first movie of the previous trilogy, but I think part of the reason is that, during that first viewing, you’re trying to keep track of a lot of characters at one time. At least in “Fellowship,” they were pretty distinct and easy to remember (e.g. the elf, the dwarf, the ranger, the wizard, etc.). In this movie, they’re almost all dwarves, and I couldn’t tell you what any of their names are. Granted, there are only a few people you’re “supposed” to care about at this point, but some of those dwarves get a bit more focus later on in the book. We’ll have to see how it plays out, and I can’t see how they could avoid this problem, but it deserves mention.
In the end, I’m glad I saw it and I’m glad I saw it in 48 fps 3D. Is it better than the movies from the previous trilogy? Hard to say, without the next two movies available to get the full comparison. The first movie of the previous trilogy was the weakest of the three, in my opinion, and it could very well hold true for this one as well.
But if it says anything, I’m still looking forward to the next one.
The Holidays
To be honest, I haven’t been posting all that much recently because I haven’t had much to say. At the same time, it’s been pretty busy, for one reason or another. With Christmas falling in the middle of the week, I feel like my schedule has been thrown radically off course for the past few weeks, and am only just now getting back in the swing of things.
Christmas was good, of course. We went to Louisiana, MO for the Baumann (extended) family Christmas on Sunday the 23rd, then continued north to Hannibal for the Baumann (immediate) family Christmas on the 24th. It was odd seeing how much snow was on the ground up there, as we really hadn’t gotten any in St. Louis beforehand. At the very least, it still felt like we got a “White Christmas” out of the deal. After that, we attended our traditional Christmas Eve service back in Louisiana before heading down to St. Louis that night, so that Meg could open her presents under her own tree on Christmas morning.
However, since we didn’t get home until 10:00 pm on Christmas Eve, Meg was quite content to stay in bed until 8:00 am the next morning, meaning we had to wake her up to get her to church on Christmas Day (thus, leaving Meg enough time to open one present before leaving). Still, it all worked out. Meg wanted to play with everything she opened immediately, rather than waiting until after everything was opened to choose something to play with. Perhaps it was better to only get one first.
We typically don’t go to Christmas Day services, but as we were in town, didn’t have to go anywhere, and our new pastor wanted to have a service on that day (we usually don’t), we went along and had a good time. There were even some folks in pajamas, bringing a good “family atmosphere” to the proceedings. It was a short-ish service, but was nice to participate in.
Brooke went to work the next few days, and Meg went to school. I, being the lazy one, stayed home, getting a few things done while watching the Extended Editions of “The Lord of the Rings” (in preparation for “The Hobbit,” which I still haven’t seen!). I assembled Meg’s new “big girl bed” (which she’s now sleeping in, most nights), hung out with a few friends, kept up on laundry, etc. Overall, a good mix of productivity and laziness, so I was satisfied!
We then went to Columbia last Friday for the Linsenbardt (immediate) family Christmas. Jake and Kristen couldn’t get there around Christmas, so this is the first year I can remember where we pushed things off a few days. In the end, it was probably better this way as we didn’t feel as rushed, traveling between towns without much lag time. Still, we had a good time and got to hit up Flat Branch and Shakespeare’s while we were there (making it more than worth the trip).
Meg stayed in Columbia with my parents while Brooke, Edie and I returned to St. Louis for New Year’s. Brooke actually went in to work for a little bit on New Year’s Eve while I took down the tree and did a few other things around the house. We hung out with Adam and Kelley that night, which was rather nice because we typically have them over to our house (as Meg is usually in bed by 7:30, and they live 20+ min away from our house, making dinner a difficult prospect). Regardless, good food and good times with friends, so it was a nice way to ring in 2013.
And now, I’m back at work. I had a good time over break, but am ready to get back to a typical routine, even if it means getting up “early” and putting clothes on instead of staying in PJs all day. We won’t have any easy weekends coming up, though, as my cousin gets married on Saturday (the bachelor party is tonight, and the rehearsal is tomorrow…I’m an usher and Meg’s flower girl-ing…), so we’ve got our work cut out for us.
But thankfully, Cabin Fever is next Saturday. Can’t wait for that one. 🙂
Merry Christmas!
12.07.12 Dinner
A Few Changes
WordPress released updated software today, so in setting it up, I opted to mess with the new default theme and new image features. Specifically, the ability to add galleries like…well…this one!
Anyway, as usual when I do silly things like this, I’ll probably change a few things around aesthetically before I settle on something I’m happy with. For now, this is what you get. So far, I’m pretty happy with all the options within the default theme (being used currently) and am pretty impressed with now nice images look within the galleries. Also, the site should work pretty well on cell phones and tablets now.
Neat stuff!
12.02.12 Dinner
11.29.12 Dinner
Lemon pepper chicken, peas and carrots, and noodles. This was a definite win!