[kidderhooker]

Thanks its nice to have all this info in one spot. Thanks for taking the time to post, this info.

[dl.oldschool]

thanks a lot for this useful info.

[loedertje]

tnx, this is useful stuff!

[Renzokuken.]

very very complete info!!!!!
thanks

[kamilz]

Danke m8
Learnt something new

[ticonderoga]

Thanks for the info.

[roselawn]

Good one. Thanks for posting it.

[forcrp]

Thank you for the clarifications!

[finex69]

Thanks.....Useful information......

[girly_77lk]

Very useful information. Thank you very much...

[povereem]

At last a good explanation!

[nullnull]

Thank you for the explanation. I'm wondering, are there any tags yet for 3D? Or would it be possible to require certain tags in this forum, even though they are not globally accepted among groups?

For starters, there's no "3D" tag. People use it sometimes to describe 3D-rendered material. So how can 3D content be marked in general?

STEREOSCOPIC is sometimes used and seems like a reasonable term. Or maybe 2SCOPE if it's too long.

Then there's the kind of encoding, falling broadly into two categories: Destructive and non-destructive. Destructive means that the two source images for every frame were combined using a method that cannot be undone (and I don't mean that it will reduce resolution, but not at all). Anaglyph is the usual example and differentiating between the two is key to not letting people download that they can't use. Since ANAGLYPH is the only common destructive method I'd say it's fair to use it as keyword. But what for non-destructive method? DUALIMG or 2XIMG could work (indicating that indeed two separate frames can be constructed somehow from the given data).

Then there's the encoding system, namely the color masks for Anaglyph or the encoding type for frame-pairs. For color masks I'd stick with the usual. Color1Color2 where position in the color wheel determines priority (i.e. red before yellow, yellow before green, green before blue...):
REDGREEN
REDBLUE
CYANMAGENTA

For dual frames it would be the encoding type, MVC (Multi-View-Coding, a.k.a. BD3D), SBS (Side-by-Side, no matter if horizontal of vertical or even seperate streams/files), FS3D (field sequential/interlaced)

Next there's the source it's coming from: Is this natively filmed/rendered/composited in 3D? Or has someone produced the file from a 2D version with depth map painting and algorithms? I don't think it has to be too specific but a "converted" version should be named different than a "native" version. TRUE3D is sometimes used for native, but there's no common code for converted versions. How about SYN3D for synthetic?

And finally the resolutions should be meaningful and express the true resolution. For Anaglyph that's easy: The resolution of the stream (720p/24...) but for true 3D it's a bit different. Specifically, has the resolution been divided by two among any axes or are both frames full-size? I'd suggest an extension to the usual syntax: VerticalresolutionEncoding/Framerate is the usual. A single letter H (for half horizontal) V (for half vertical) or F (for full frames) could work: 720p/24F

The full string would then be something like
2SCOPE DUALIMG SBS TRUE3D 720p/24F
or
2SCOPE ANAGLYPH REDGREEN SYN3D 720p/24

Acceptable? Suggestions?

UPDATE. I created a new thread to discuss this since it doesn't really belong here: Link

[devlin]

thanks!!!

[devlin]

thanks mate