Fu 360 view doesn't work with proxy

Moderator: Chad

User avatar
Chad
Fusionator
Posts: 1429
Joined: Fri Aug 08, 2014 1:11 pm
Been thanked: 16 times

360 view doesn't work with proxy

#1

Post by Chad » Tue Aug 08, 2017 4:55 pm

Fusion version:
Fusion 9 build 13

OS and version:
Windows 8.1

Description of the bug:
When ProxyScale results in an image that is not 2:1, the 360 viewer reverts to a rectangle if the mode is set to "auto"

Severity (Trivial, Minor, Major, Critical)
Minor, except if you use the 360 view a lot

Steps to reproduce:
Put an image output into a viewer and enable the 360 view
Set the 360 mode to "auto"
Set ProxyScale to a value that would cause the image size to round to a non-2:1-aspect

User avatar
AndrewHazelden
Fusionator
Posts: 1491
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 6
Location: West Dover, Nova Scotia, Canada
Been thanked: 82 times
Contact:

Re: 360 view doesn't work with proxy

#2

Post by AndrewHazelden » Wed Aug 09, 2017 2:52 am

Hi Chad.

Can you try adding a SetMetadata node to your comp like the examples below to see if it solves your 360° viewer auto detection issue when viewing 1:1 aspect ratio LatLong images?

Without having panoramic metadata present the only way to correctly guess what image projection is in use is for Fusion to assume a 2:1 image is a LatLong.

On the metadata less autodetection implementation side of things what is to say that a 1:1 aspect ratio is not any other panoramic format scaled into a 1:1 frame size, no? A 1:1 image could also be a pair of stereo over/under 2:1 LatLong images, a raw individual 90° FOV cubic face, or even a scaled h-cross or v-cross cubic panorama.

Try adding the "Pano" metadata tag to an image:

Code: Select all

{
	Tools = ordered() {
		SetMetadataPano = Fuse.SetMetaData {
			CtrlWZoom = false,
			NameSet = true,
			Inputs = {
				FieldName = Input { Value = "Pano", },
				FieldValue = Input { Value = "{Format  = \"LatLong\"}", },
			},
			ViewInfo = OperatorInfo { Pos = { 53, 80 } },
		}
	},
	ActiveTool = "SetMetadataPano"
}
And for Stereo VR imagery try using the "Stereo Vertically Stacked" metadata tag in your image:

Code: Select all

{
	Tools = ordered() {
		SetMetadataStereo= Fuse.SetMetaData {
			CtrlWZoom = false,
			NameSet = true,
			Inputs = {
				FieldName = Input { Value = "Stereo", },
				FieldValue = Input { Value = "{Method  = \"vstack\"}", },
			},
			ViewInfo = OperatorInfo { Pos = { 162, 80 } },
		}
	},
	ActiveTool = "SetMetadataStereo"
}

User avatar
Chad
Fusionator
Posts: 1429
Joined: Fri Aug 08, 2014 1:11 pm
Been thanked: 16 times

Re: 360 view doesn't work with proxy

#3

Post by Chad » Wed Aug 09, 2017 7:06 am

Yeah, it does seem to require the metadata that almost no input will have.

The way Unity does it is to not check if it's exactly 2:1, but if it's CLOSER to 2:1, 4:3, or 6:1. Would such a heuristic work well in Fusion?

Also, PanoMap should add metadata, but doesn't.

User avatar
AndrewHazelden
Fusionator
Posts: 1491
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 6
Location: West Dover, Nova Scotia, Canada
Been thanked: 82 times
Contact:

Re: 360 view doesn't work with proxy

#4

Post by AndrewHazelden » Wed Aug 09, 2017 7:43 am

From my initial tests PanoMap only seems to add the metadata if you are re-targeting the image projection between two different formats.

I'm working on a small macro node now that will provide an easy way to add the Stereo and Pano metadata tags to existing imagery using a pair of ComboControl based UserControls. I will email the macro to you when it's done.
Last edited by AndrewHazelden on Mon Oct 16, 2017 3:50 pm, edited 1 time in total.

User avatar
AndrewHazelden
Fusionator
Posts: 1491
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 6
Location: West Dover, Nova Scotia, Canada
Been thanked: 82 times
Contact:

Re: 360 view doesn't work with proxy

#5

Post by AndrewHazelden » Wed Aug 09, 2017 7:49 am

Chad wrote:The way Unity does it is to not check if it's exactly 2:1, but if it's CLOSER to 2:1, 4:3, or 6:1. Would such a heuristic work well in Fusion?
What image projection would a 16:9 frame be autodetected as though? :D

Going forward Facebook is likely going to be pushing Cubemap 3x2 mono content resized into a standard UHD frame size for distribution, and Facebook Cubemap 3x2 Stereo content is going into a 3840x3840 Over/Under frame format with a non 1:1 aspect ratio cubic face on each view. (from what I have heard...)

User avatar
Chad
Fusionator
Posts: 1429
Joined: Fri Aug 08, 2014 1:11 pm
Been thanked: 16 times

Re: 360 view doesn't work with proxy

#6

Post by Chad » Wed Aug 09, 2017 8:49 am

16:9 is closest to 2:1, so equirectangular. Almost all the pocket 360 cameras shoot to 16:9 equirectangular mp4, which would come in without metadata, so to give them the best shot at being viewed correctly without having to manually inject metadata, I think a less rigid test of the aspect ratio would work.

User avatar
AndrewHazelden
Fusionator
Posts: 1491
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 6
Location: West Dover, Nova Scotia, Canada
Been thanked: 82 times
Contact:

Re: 360 view doesn't work with proxy

#7

Post by AndrewHazelden » Wed Aug 09, 2017 10:32 am

Hi Chad.

I emailed you a "SetMetadataVR" macro node which you can use if you want.
You do not have the required permissions to view the files attached to this post.
Last edited by AndrewHazelden on Mon Oct 16, 2017 3:49 pm, edited 1 time in total.

User avatar
Chad
Fusionator
Posts: 1429
Joined: Fri Aug 08, 2014 1:11 pm
Been thanked: 16 times

Re: 360 view doesn't work with proxy

#8

Post by Chad » Wed Aug 09, 2017 12:42 pm

Cool. I'll try it on the next shot.