Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2024-02-11 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Changes (by kagami):

 * cc: kagami (added)

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2024-02-11 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Comment (by kagami):

 Not fully ontopic, but I think this belongs here.

 There's new app for the Quest headeset, 4XVR. It claims support for both
 AVC MVC and MV-HEVC. I don't have Quest, but I've checked the apk contents
 and found that it uses ffmpeg (v4.4.3 LGPL2.1+) but to my knowledge
 nowhere in the app or on the website FFmpeg's license is mentioned and
 source code isn't available.

 Furthermore, the prefix used for compilation `--prefix=/ffmpeg_443v_mvc
 /ffmpeg-arm8` and few symbols inside libavcodec binary such as `Missing
 reference picture, mvc_ref_pic_ptr default`, `h->mvc_ref_pic_ptr = NULL`
 make me think that the developer added support for the MVC decoding to the
 FFmpeg (I've checked both current and v4.4.3 ffmpeg's source code and
 haven't found similar lines). Although I'm not enitrely sure.

 Shouldn't the developer upload modified source code of FFmpeg as the LGPL
 license requires?
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2023-12-31 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Comment (by philcerf):

 For the records:
 Looks, as if 3D profiles have also been specified for HEVC
 
(https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding#Version_3_and_higher_profiles),
 though I guess it's not really used yet (at least not by UHD BluRays)
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2023-11-29 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Comment (by philcerf):

 I guess, that when one has an output device (like a 3D capable projector,
 a 3D TV screen or glasses/VR-headsets like the "Bigscreen Beyond" or the
 "XREAL AR glasses") and if that does support MVC itself, then ffmpeg
 wouldn't need to do much except for passing the stream on as is (and the
 only thing that would be required was some Linux driver, for the said
 device.

 But it seems that quite some devices do not support MVC directly, but
 require e.g. SBS (side by side) input.
 Right now, many people seem to use
 [https://download.videohelp.com/r0lZ/BD3D2AVS/index.html BD3D2MK3D], but
 its not open.

 So would be nice if any ffmpeg MVC support could be used together with its
 {{{stereo3d}}} filter to generate e.g. SBS output.



 "3D is dead" - so is it even worth it?
 Well, there are still many movies released as 3D movies, not only in the
 cinema but also on home media (i.e. BluRays).
 And while 3D TV screens are probably indeed rather dead, there seem to be
 still quite many 3D projectors and glasses/VR set being released and in
 development.
 Also there are 3D camcorders which seem to produce the format.


 I have found [https://github.com/carrardt/h264-tools h264-tools] which
 seems to be able to decode MVC and create SBS versions of it.
 [https://github.com/Britz/FFmpeg Britz/FFmpeg] was already mentioned
 above.
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2023-11-29 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Changes (by philcerf):

 * cc: philcerf (added)

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2023-08-25 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Comment (by jake downs):

 Hello, I'm curious if there's been any progress on adding support for
 this?

 I noticed that the LAVFilters project seems to add support for PCs
 https://github.com/Nevcairiel/LAVFilters

 And applications like Stereoscopic Player appear to be able to decode the
 additional view and render it as a SBS view in real time (perhap with some
 buffering?) without needing to fully re-encode the file.

 I'd love to see if we could get support added to FFMPEG and, beyond that,
 VLC for Mac / Linux (for x86, x64 and ARM64 ideally)

 Is anyone aware of any progress being made on this front?

 I'll be diving into the Jochen Britz repo in the meantime:
 https://github.com/Britz/FFmpeg (Thanks to HÃ¥kon Struijk Holmen for
 posting that)
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2022-03-05 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:  (none)
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  1|
-+-
Changes (by DustBird):

 * cc: DustBird (added)

Comment:

 My JVC Everio GS-TD1 camcorder produces these files as well.  If I'm not
 mistaken, there are actually two different formats that get called MVC.
 One, called "MP4/MVC" on the camera, produces a normal video stream and a
 data stream that contains delta information.  The other format, called
 "AVCHD 3D" on the camera, contains two video streams, and should be easier
 to support.  The sample on this thread seems to be from the dual-video-
 stream "AVCHD 3D" version.

 Here's the result of ffprobe:
 {{{
 >ffprobe AVCHD3Dtest.MTS
 ffprobe version N-105832-g72684d2c2d-20220303 Copyright (c) 2007-2022 the
 FFmpeg developers
   built with gcc 11.2.0 (crosstool-NG 1.24.0.533_681aaef)
   configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static
 --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64
 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug
 --enable-shared --disable-static --disable-w32threads --enable-pthreads
 --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype
 --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig
 --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf
 --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-
 avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac
 --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme
 --enable-libass --enable-libbluray --enable-libmp3lame --enable-libopus
 --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp
 --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable-
 libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-
 libopenmpt --enable-librav1e --enable-librubberband --enable-schannel
 --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1
 --enable-libtwolame --enable-libuavs3d --disable-libdrm --disable-vaapi
 --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-
 libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-
 libxvid --enable-libzimg --enable-libzvbi --extra-
 cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread
 --extra-ldexeflags= --extra-libs=-lgomp --extra-version=20220303
   libavutil  57. 22.100 / 57. 22.100
   libavcodec 59. 21.103 / 59. 21.103
   libavformat59. 17.102 / 59. 17.102
   libavdevice59.  5.100 / 59.  5.100
   libavfilter 8. 27.100 /  8. 27.100
   libswscale  6.  5.100 /  6.  5.100
   libswresample   4.  4.100 /  4.  4.100
   libpostproc56.  4.100 / 56.  4.100
 [mpegts @ 020e61edc4c0] Stream #1: not enough frames to estimate rate;
 consider increasing probesize
 [mpegts @ 020e61edc4c0] start time for stream 1 is not set in
 estimate_timings_from_pts
 [mpegts @ 020e61edc4c0] stream 1 : no TS found at start of file,
 duration not set
 [mpegts @ 020e61edc4c0] Could not find codec parameters for stream 1
 (Video: h264 (HDMV / 0x564D4448), none): unspecified size
 Consider increasing the value for the 'analyzeduration' (0) and
 'probesize' (500) options
 Input #0, mpegts, from 'AVCHD3Dtest.MTS':
   Duration: 00:00:09.02, start: 1.033367, bitrate: 26003 kb/s
   Program 1
   Stream #0:0[0x1011]: Video: h264 (High) (HDMV / 0x564D4448), yuv420p(top
 first), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 59.94 tbr, 90k tbn
   Stream #0:1[0x1012]: Video: h264 (HDMV / 0x564D4448), none, 90k tbr, 90k
 tbn
   Stream #0:2[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo,
 fltp, 256 kb/s
   Stream #0:3[0x1200]: Subtitle: hdmv_pgs_subtitle ([144][0][0][0] /
 0x0090), 1920x1080
 }}}

 And again with the probesize and analyzeduration increased:
 {{{
 >ffprobe -probesize 1 -analyzeduration 10
 AVCHD3Dtest.MTS
 ffprobe version N-105832-g72684d2c2d-20220303 Copyright (c) 2007-2022 the
 FFmpeg developers
   built with gcc 11.2.0 (crosstool-NG 1.24.0.533_681aaef)
   configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static
 --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64
 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug
 --enable-shared --disable-static --disable-w32threads --enable-pthreads
 --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype
 

Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2014-10-04 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  1|
-+-

Comment (by hawken):

 A small collection of resources I think can be useful:

 Jochen Britz's MVC thesis:
 https://github.com/Britz/FFmpeg

 Koda tried to clean this up for libav:
 https://github.com/kodabb/libav/tree/mvc_redo4

  michaelni hawken, also maybe ask/contact Peter Wimmer and Gerion
 Entrup, i do see mails from them about MVC on the ML

 Webpages:
 http://blogs.gentoo.org/lu_zero/2014/04/04/the-road-to-mvc/

 libav information:
 https://wiki.libav.org/Blueprint/MVC

--
Ticket URL: https://trac.ffmpeg.org/ticket/3009#comment:6
FFmpeg https://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2013-10-17 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  1|
-+-

Comment (by cehoyos):

 Samples are now in
 http://samples.ffmpeg.org/3D/AVC_codec_in_m2ts_not_recognized/

-- 
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:5
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc (was: AVC codec in m2ts file not recognized by ffmpeg)

2013-09-28 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  1|
-+-
Changes (by cehoyos):

 * status:  new = open
 * reproduced:  0 = 1
 * component:  FFmpeg = avcodec
 * priority:  normal = wish
 * version:  2.0.1 = git-master
 * keywords:  AVC, m2ts = h264 mvc mpegts
 * type:  defect = enhancement


Comment:

 Please explain how the samples were created (did you use software to
 separate the two streams or do you have a device that produces two
 separate streams) and please provide both samples.

-- 
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:1
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2013-09-28 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  1|
-+-

Comment (by skifreak):

 Replying to [comment:1 cehoyos]:
  Please explain how the samples were created (did you use software to
 separate the two streams or do you have a device that produces two
 separate streams) and please provide both samples.

 I obtained the samples through a passthrough bluray rip using DVDFab from
 a 3D bluray. These streams have not been altered from the bluray in any
 way. I provided both samples, as stated in the bug report, under
 incoming/AVC_codec_in_m2ts_not_recognized/. Inside there are three files:

 AVC_codec_not_recognized_README.txt
 AVC_codec_not_recognized_right_video_sample.m2ts
 AVC_codec_recognized_left_video_sample.m2ts

 As stated before, AVC_codec_recognized_left_video_sample.m2ts's codec is
 recognized with ffmpeg and playable with mplayer, while
 AVC_codec_not_recognized_right_video_sample.m2ts 's (same AVC) codec
  is not recognized by ffmpeg. mediainfo is able to recognize the codec in
 both files.

 Please let me know if I can provide any more information. I greatly
 appreciate all of your assistance and help in this matter.

-- 
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:2
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2013-09-28 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  1|
-+-

Comment (by cehoyos):

 (Sorry that I missed the uploaded files)

 Am I correct that the original files on the Bluray are named 1.MTS,
 2.MTS, ... and that they contain two video streams (the left and the
 right one) in one file and that DVDFab created the files you uploaded by
 separating the video streams? Or do I misunderstand? (Sorry, I don't have
 a bluray player.)

-- 
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:3
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac


Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc

2013-09-28 Thread FFmpeg
#3009: Support mvc
-+-
 Reporter:  skifreak |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 mvc |   Blocked By:
  mpegts |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  1|
-+-

Comment (by skifreak):

 Replying to [comment:3 cehoyos]:
  (Sorry that I missed the uploaded files)
 
  Am I correct that the original files on the Bluray are named 1.MTS,
 2.MTS, ... and that they contain two video streams (the left and the
 right one) in one file and that DVDFab created the files you uploaded by
 separating the video streams? Or do I misunderstand? (Sorry, I don't have
 a bluray player.)

 The (full, not sample) files are named 0014.m2ts (left I believe) and
 0015.m2ts (right I believe). Each contains one video stream, the left
 containing sound and subtitle, the right containing neither. I'm not
 certain how the files are exactly contained on the disk, if separation was
 involved or not when they were created. From my past experience in
 passthrough with the software though, it would seem the files are exact
 duplicates of the contents on the disk. (There isn't a way I know of to
 check this for certain, since the disc needs to be decrypted to be viewed
 and DVDFab will not let me look at exactly which m2ts file(s) represent
 each stream.) You understand correctly, from what I can gather. (I don't
 have a bluray player in the sense either, just a bluray sata drive.)
 Thanks again for all of your work, I greatly appreciate your and all of
 the developers' help. ffmpeg has, and always will be, my one stop software
 for encoding.

-- 
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:4
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac