Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lighting #98

Open
fsoudiere opened this issue Nov 10, 2015 · 11 comments
Open

Lighting #98

fsoudiere opened this issue Nov 10, 2015 · 11 comments

Comments

@fsoudiere
Copy link
Member

No description provided.

@fsoudiere fsoudiere modified the milestone: v1.0.0 Nov 11, 2015
@fsoudiere
Copy link
Member Author

@nuclearsugar @AndrewHazelden @KCizugar any thoughts or suggestions when it comes to lighting equipment in shooting 360 videos?

from experience, fluorescent lighting and natural lighting are the best. but i m interested in what equipment is safe to consider. I could mention that traditional lighting is possible if shooting 180 quadrants, with RED cam for example, and stitched at later time. (hiding equipment in the other 180 not being recorded.)

https://github.com/making360/making360/blob/master/latex/chapters/problems-of-shooting/lighting.tex

@AndrewHazelden
Copy link
Member

An issue with consumer / prosumer cameras is the lack of video / shutter syncing with frequency of the grid power which is used to avoid flickering in the recorded image. In Europe they are on 50 Hz power, and North America is on 60 Hz power so the correct shutter speed for interior filming would be slightly different. This would show up most when you try and film on a real "street" location like in a convenience store with florescent lighting. Looking at some of the prosumer video tips from DSLR filming people like Philip Bloom would explain the best solutions to this kind of issue.

@AndrewHazelden
Copy link
Member

If a person wanted to boost the amount of light in an interior scene filmed on a real location, a large daylight color temperature HMI lighting fixture could be used to beam extra light from outside the building through the windows to really light up an interior room scene. This light source would appear to be natural daylight coming into the room which means you don't need to do lots of post production and rig removal like adding overhead suspended lights in a scene would need. A professional lighting grip would have to operate the HMI lighting fixture as they are really large, run hot, and need special UV filters to avoid sun burns.

@nuclearsugar
Copy link
Contributor

So far I've been lucky. I've only shot using natural daylight or brightly lit rooms. I've had a little bit of trouble with fluorescent bulbs adding a very slow pulsing effect to each of the GoPro cameras. But I think this is a problem any video camera would face. But it was easily corrected with some color correction in After Effects.

I recently stumbled across this interesting lighting concept. http://i.imgur.com/NaCcpDl.jpg I'm currently working with some professors at MIT that will be doing some underwater scuba 360 video and so they are designing their own lighting rigs similar to this. I worry that the exposure of the horizontal cameras would be affected, but perhaps with the physical masking it would be ok. Just started the project, so we will see what happens and I'll share our findings with you.

@fsoudiere
Copy link
Member Author

@AndrewHazelden can you help write this chapter? I have less experience and knowledge in terms of lighting. I am working on the noise experiment, then color grading and ingestion. Let me know if you can't, its ok.

@AndrewHazelden
Copy link
Member

Hi. I added an HMI lighting section to the lighting chapter that should give people some ideas when filming on location. I also went through and conformed the spelling for several technical terms across the .tex files today too.

Here are some misc notes from my proof reading:

  • The ingestion.tex chapter has a heading "Weasfd" - what is it?
  • The official formatting for WIFI is WiFi or Wi-Fi. Which do you prefer?
  • It would probably be a good idea to change the mbps to megabits per second as quite a few artists won't know MBps is megabytes per second, and mbps or Mbps are megabits per second.
  • When writing words like 4GB it should really be 4 GB as there should be a space between the number and the SI unit.
  • FPS should be standardized and not alternated between fps Fps and FPS.
  • H.264/H.265 is the standardized term so h264/h265 is a bit lax spelling wise.
  • Mettle spells the product in their docs as SkyBox not skybox or Skybox.
  • vr should be standardized as VR for capitalization
  • I noticed Samsung's Gear VR product officially has a space between the Gear and the VR part. That is something new for me to see.
  • For conversational style text writing about 8 bit / 10 bit / 16 bit imagery might be better phrased as 8 bit per channel / 10 bit per channel / 16 bit per channel as some people will get confused when floating point formats like linear floating point 32 bit TIFF / EXRs come out more and people get continuously mixed up term wise between a 32 bit per channel EXR format and a 32 bit PNG that actually has only 8 bit per channel RGBA data.
  • sd card should be written as SD card.
  • micro sd card should be written as microSD card.
  • 2d and 3d should probably be standardized as 2D and 3D in the text.
  • youtube and facebook should probably be standardized as YouTube and Facebook.
  • HTTP hyperlinks should be written as formatted text like \textbf{\href{http://www.google.com}{Google}}

@fsoudiere
Copy link
Member Author

this is awesome, thanks so much for doing this edit work! Will merge
tomorrow.

On Wed, Nov 18, 2015 at 7:39 PM, Andrew Hazelden notifications@github.com
wrote:

Hi. I added an HMI lighting section to the lighting chapter that should
give people some ideas when filming on location. I also went through and
conformed the spelling for several technical terms across the .tex files
today too.

Here are some misc notes from my proof reading:

  • The ingestion.tex chapter has a heading "Weasfd" - what is it?
  • The official formatting for WIFI is WiFi or Wi-Fi. Which do you
    prefer?
  • It would probably be a good idea to change the mbps to megabits per
    second as quite a few artists won't know MBps is megabytes per second, and
    mbps or Mbps are megabits per second.
  • When writing words like 4GB it should really be 4 GB as there should
    be a space between the number and the SI unit
    http://www.engadget.com/2010/12/16/32-gb-versus-32gb-almost-everyone-is-writing-it-wrong/
    .
  • FPS should be standardized and not alternated between fps Fps and
    FPS.
  • H.264/H.265 is the standardized term so h264/h265 is a bit lax
    spelling wise.
  • Mettle spells the product in their docs as SkyBox not skybox or
    Skybox.
  • vr should be standardized as VR for capitalization
  • I noticed Samsung's Gear VR product officially has a space between
    the Gear and the VR part. That is something new for me to see.
  • For conversational style text writing about 8 bit / 10 bit / 16 bit
    imagery might be better phrased as 8 bit per channel / 10 bit per channel /
    16 bit per channel as some people will get confused when floating point
    formats like linear floating point 32 bit TIFF / EXRs come out more and
    people get continuously mixed up term wise between a 32 bit per channel EXR
    format and a 32 bit PNG that actually has only 8 bit per channel RGBA data.
  • sd card should be written as SD card.
  • micro sd card should be written as microSD card.
  • 2d and 3d should probably be standardized as 2D and 3D in the text.
  • youtube and facebook should probably be standardized as YouTube and
    Facebook.
  • HTTP hyperlinks should be written as formatted text like
    \textbf{\href{http://www.google.com}{Google}}


Reply to this email directly or view it on GitHub
#98 (comment).

@fsoudiere fsoudiere assigned fsoudiere and unassigned fsoudiere Nov 26, 2015
@fsoudiere
Copy link
Member Author

@making360/m360 do we need pictures for this chapter? if so, does anyone have any?

@AndrewHazelden
Copy link
Member

I added a new illustration exterior_hmi_lighting.png to the psd-ai folder for the lighting chapter. Fabien, would you be able to add it to the lighting.tex file as I'm not really competent with the LaTex formatting yet.

@AndrewHazelden
Copy link
Member

I noticed a really neat idea for a custom 3D printed LED macro ring light that attaches around the front lens area on a GoPro camera and sits just outside the field of view of the fisheye lens.

It looks to me like it would have great potential for making an "invisible" panoramic 360° lighting solution as it should be possible to customize that idea to 3D print a set of attachable macro ring lights that are compatible with a GoPro 360 style rig.

thingverse ringlight

GoPro Ringlight Baseplate:
http://www.thingiverse.com/thing:1247695

Maybe something like a circular piece of industrial velcro could be used to affix the ringlights to the outside of each GoPro camera holder on a panoramic 360° video rig?

Cheers,
Andrew

@AndrewHazelden AndrewHazelden reopened this Jan 8, 2016
@HarryDownunder
Copy link

nuclearsugar commented Nov 14, 2015 said...
"I recently stumbled across this interesting lighting concept. http://i.imgur.com/NaCcpDl.jpg I'm currently working with some professors at MIT that will be doing some underwater scuba 360 video and so they are designing their own lighting rigs similar to this."

Not even a nice idea, won't work, tried this approach on a Cousteau job years ago. It's all got to do with water quality (suspended solids) which affects its diffraction qualities, so no matter how much unfocused fill light you pump in it just creates a glowing cloud around the lamps. Then we realised micro was more interesting, swapped out the lenses for short wide macros and a whole new minature world was revealed. Would never have had happened if the intended design delivered what its designer dreamed of... well intentioned but ignorant of simple optics and physics, great drawings though and that's why the money was approved by people even less intelligent than he was :)

We live in hope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants