The Hobbit film leaves fans with an unexpected sickness

Status
Not open for further replies.
The Hobbit film leaves fans with an unexpected sickness


Latest J.R.R. Tolkien adaptation was filmed at a higher frame rate, but the results have left viewers queasy

LAST UPDATED AT 12:33 ON Sun 2 Dec 2012

MOVIEGOERS who went to see the first screening of The Hobbit in New Zealand have complained a cutting edge new filming technique employed by director Peter Jackson left them feeling dizzy and sick.

Jackson filmed The Hobbit: An Unexpected Journey, the first in a two-part adaptation of the J.R.R. Tolkien novel, in 3D and at a camera speed of 48 frames per second, which is double the normal rate, The Sunday Times reports.

The result is supposed to make 3D look smoother, eliminating flicker and motion blur. But the results have been too realistic for some.

The first complaints came six months ago at CinemaCon in Las Vegas, where Jackson showed clips of The Hobbit in 48 fps. One tech writer summed up the general feeling thus: "It's a subtle change, but one that makes a huge difference. Your favourite shows all of a sudden look like amateur productions. It is very unpleasant."

The issue has come back to haunt Jackson following last week’s premier in New Zealand.

“My eyes cannot take everything in, it’s dizzying, now I have a migraine,” said one fan, who nevertheless can’t wait to see it again.

Another tweeted: “It works for the big snowy mountains, but in close-ups the picture strobes. I left loving the movie but feeling sick.”

One fan said watching the film was like a being on a rollercoaster. “You have to hold your stomach down and let your eyes pop at first to adjust. This is not for wimps.”

The Sunday Times attempts to explain the reason for the queasiness scientifically by quoting the work of Adrian Bejan, author of Design in Nature.

Apparently, eye movement normally combines “long and fast horizontal sweeps with short and slower vertical movements”.

However, 48fps film “requires the eye to sweep up and down faster than usual in close-ups to absorb unparalleled detail on a big screen, causing cognitive strain”.

Happily for fantasy fans with weak stomachs, hardly anyone will actually be able to see The Hobbit in its 48fps glory, because fewer than five per cent of cinemas have the necessary equipment.
http://www.theweek.co.uk/film/50375/hobbit-film-leaves-fans-unexpected-sickness
 
Not that I think this couldn't be true, but surely a bastion of journalism like The Week wouldn't try to make some headlines using the latest media sensation.
 
Sounds silly to me. Like really silly. These must be the same kinds of people who get motion sickness from playing video games.

I can sit with my face in the screen at 60 FPS and it's pure joy.
 
I never seem to get a headache BY anything. I just wake up in the morning with a headache. But by video or audio, nope.
 
Bah, that's some garbage saying it looks cheap just because it's a higher FPS. Though, I won't be watching in 3D just because I hate that shit in general. It never looks like real objects really in front of me, just some freaky artificial crap. In Harry Potter it only worked for magical items and mostly just ruined the mood.

People getting sick probably needed to back up. Sitting close to the screen can easily make you sick.

No thanks. No judder, less blurring is the way to go.
What? Judder comes from asynchronous film and screen refresh rates. There isn't a reason why a film projection would have it.
 
Wow stupid post

60i... AKA 60fps. (Or 50i(50fps) for PAL viewers)

Which is a higher framerate than 48fps.

Care to add more to that comment?

Bah, that's some garbage saying it looks cheap just because it's a higher FPS. Though, I won't be watching in 3D just because I hate that shit in general. It never looks like real objects really in front of me, just some freaky artificial crap. In Harry Potter it only worked for magical items and mostly just ruined the mood.

People getting sick probably needed to back up. Sitting close to the screen can easily make you sick.

What? Judder comes from asynchronous film and screen refresh rates. There isn't a reason why a film projection would have it.

The panning in Alice in Wonderland 3D was terrible due to the judder I experienced in the theater.
 
Sounds like something people need to acclimate to. I remember the first time I went from the N64 to the GameCube, me and my brothers got motion queasy from the Venom level in SSB:M.
 
60i takes 2 interlaced fields to make 60fps motion.

When converting interlaced video that's how I usually produce 60fps (progressive) videos without interpolation.

i has nothing to do with frame rate though.

i is a connotation of interlaced or not interlaced, and goes with the resolution. So you can have 480i, 1080i or 480p, 1080p and with in those have 24fps, 30fps, 48fps, 60fps, what ever you want. It is not tied to if the image is interlaced or not. 480p, 720p, 1080p, 480i, 1080i can have any frame rate they want regardless of the i or p.

There is no such thing as 60i, it would be resolution(i, or p) framerate. IE 480i 30fps, or 480p 30fps. Both are 30fps one is just interlace and one is full resolution. 60i would mean you only had 60 lines of interlaced vertical resolution.
 
i has nothing to do with frame rate though.

i is a connotation of interlaced or not interlaced, and goes with the resolution. So you can have 480i, 1080i or 480p, 1080p and with in those have 24fps, 30fps, 48fps, 60fps, what ever you want. It is not tied to if the image is interlaced or not. 480p, 720p, 1080p, 480i, 1080i can have any frame rate they want regardless of the i or p.

There is no such thing as 60i, it would be resolution(i, or p) framerate. IE 480i 30fps, or 480p 30fps. Both are 30fps one is just interlace and one is full resolution. 60i would mean you only had 60 lines of interlaced vertical resolution.


After converting 60i video to progressive, run it in FRAPS for a surprise.
 
After converting 60i video to progressive, run it in FRAPS for a surprise.

If your video is 60fps already then converting it to progressive is just doubling every other pixel to fill in the interlaced image. Its not doing anything to the framerate. Unless you're doing a 3:2 pull down or something similar, just converting to progressive from interlaced isn't changing your framerate. You're just letting the computer fill in pixels that weren't there.

There is no 60i. It's resolutioni (or p) framerate. 60i would mean you have a vertical resolution of only 60 lines, and 60i would me you'd be showing 30 lines each frame. It is not telling you the frame rate.

Interlace just means the image is shown odd lines first ie lines 1, 3, 5, 7, 9, 11, 13, etc etc and then the next frame the even lines are shown ie lines 2, 4, 6, 8, 10, 12, 14. Progressive means all lines are shown at the same time, ie lines 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14. So with interlace you have half your vertical resolution being shown each frame, and with progressive you have your full vertical resolution being shown each frame.

It has NOTHING to do with framerate.
 
Meh, every showing here has a break in the middle, so everyone can go out and throw up a little.
 
Wimps. I do almost all my gaming in 3D @1080P/60fps.

The current game I'm playing is Lego: Batman 2. Sounds like they'd absolutely hurl at the opening title sequence in 3D. As you're rushing down, then over the traffic, and up a building at 500mph.
 
Not calling bullshit on it or anything, but there are also people saying that gaming at 60fps is tiring for the eyes, so.. i'll wait a few more impressions.
 
Wimps. I do almost all my gaming in 3D @1080P/60fps.

The current game I'm playing is Lego: Batman 2. Sounds like they'd absolutely hurl at the opening title sequence in 3D. As you're rushing down, then over the traffic, and up a building at 500mph.

I think folks are also missing a point the article makes (which it does seem to not state enough) the difference is you're playing on what a 47 - 60 inch screen tops, here we're talking about 15 - 30 foot screens. It's a little different than what you are experiencing at home.
 
If your video is 60fps already then converting it to progressive is just doubling every other pixel to fill in the interlaced image. Its not doing anything to the framerate. Unless you're doing a 3:2 pull down or something similar, just converting to progressive from interlaced isn't changing your framerate. You're just letting the computer fill in pixels that weren't there.

There is no 60i. It's resolutioni (or p) framerate. 60i would mean you have a vertical resolution of only 60 lines, and 60i would me you'd be showing 30 lines each frame. It is not telling you the frame rate.

Interlace just means the image is shown odd lines first ie lines 1, 3, 5, 7, 9, 11, 13, etc etc and then the next frame the even lines are shown ie lines 2, 4, 6, 8, 10, 12, 14. Progressive means all lines are shown at the same time, ie lines 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14. So with interlace you have half your vertical resolution being shown each frame, and with progressive you have your full vertical resolution being shown each frame.

It has NOTHING to do with framerate.

Video wasn't originally 60fps. The 60fps motion was created by combining 2 30i fields.

But for reference...

30fps

http://hubblesource.stsci.edu/sources/video/clips/details/images/centaur_1.mpg

60i (2 30i fields combined forming 60fps motion. What you generally see on TV)

http://hubblesource.stsci.edu/sources/video/clips/details/images/centaur_2.mpg


60fps (Progressive)

http://www.peejeshare.com/files/363417730/centaur_2.mp4.html
 
Reminded me to book!
I wasnt going to watch in in Mega 3D but my friend pushed for it so I guess I am now. Hopefully it adds rather than takes away..
 
Video wasn't originally 60fps. The 60fps motion was created by combining 2 30i fields.

But for reference...

30fps

http://hubblesource.stsci.edu/sources/video/clips/details/images/centaur_1.mpg

60i (2 30i fields combined forming 60fps motion. What you generally see on TV)

http://hubblesource.stsci.edu/sources/video/clips/details/images/centaur_2.mpg


60fps (Progressive)

http://www.peejeshare.com/files/363417730/centaur_2.mp4.html

You are using interpolation then, it's doing a different form of a 3:2 pull down. Any time you increase the framerate you're using interpolation. You can not simply combine the odd fields of frame 30 and the even fields of frame 31 and suddenly have full wonderful frames 30, 31, 32, and 34.

This is the kind of image you get if you just combine frame 30 and frame 31 from an interlaced video

Interlaced_video_frame_%28car_wheel%29.jpg
 
You are using interpolation then, it's doing a different form of a 3:2 pull down. Any time you increase the framerate you're using interpolation. You can not simply combine the odd fields of frame 30 and the even fields of frame 31 and suddenly have full wonderful frames 30, 31, 32, and 34.

This is the kind of image you get if you just combine frame 30 and frame 31 from an interlaced video

Interlaced_video_frame_%28car_wheel%29.jpg

Not using interpolation. (Because if I did you would be seeing interlaced artifacts, or interpolation artifacts)

You're not converting the video correctly.
 
Status
Not open for further replies.
Top Bottom