2020-04-01, 17:22
2020-04-01, 19:06
2020-04-01, 19:43
(2020-04-01, 19:06)Kodroid Wrote:(2020-04-01, 11:03)shrugg1e Wrote: Short question: On FTV Stick 4K its still not fixed the auto framerate switching inside the original Netflix app?Related question: if I choose to use it, should framerate matching be enabled in Kodi's settings or the 4K Stick's settings?
What has kodi's settings to do with another app?
2020-04-01, 20:19
(2020-03-31, 21:01)jubilex Wrote:(2020-03-31, 18:59)fritsch Wrote:(2020-03-31, 18:51)jubilex Wrote: Any chance of the MOV stretch being fixed in Matrix?
Where is your github issue again? With the samples?
Here's my earlier post -- I'm sorry, I'm not familiar with GitHub.
I have verified that my issue with MOV files in aspect ratios of 2.35 or 2.40 being stretched vertically is unrelated to the Cinemavision add-on -- it's an issue with Quicktime and the combination of Kodi and Fire TV 4k.
Using this video as an example: https://movietrailers.apple.com/movies/u...h1080p.movI found another post of another user saying the same thing, and oddly he said they display correctly in Kodi on the Fire TV 2nd gen -- it only seems to be an issue on the 4k. I can test Fire TV 2nd gen myself later if necessary.
- Displays correctly in Kodi on PC
- Displays correctly in Kodi on Android 10 phone
- Displays correctly in Plex on Fire TV 4k
- Displays stretched vertically to 16:9 on Kodi Fire TV 4k
Debug log: licusawuki.kodi (paste)
Initial:
Quote:2020-03-19 15:13:15.406 T:26481 DEBUG: CDVDVideoCodecAndroidMediaCodec::Open m_codecname(OMX.MTK.VIDEO.DECODER.AVC), colorFormat(19)
2020-03-19 15:13:15.425 T:26481 DEBUG: CDVDVideoCodecAndroidMediaCodec::InjectExtraData
2020-03-19 15:13:15.491 T:26481 DEBUG: CDVDVideoCodecAndroidMediaCodec:: width(1920), height(816), stride(0), slice-height(0), color-format(0)
2020-03-19 15:13:15.492 T:26481 DEBUG: CDVDVideoCodecAndroidMediaCodec:: crop-left(0), crop-top(0), crop-right(1919), crop-bottom(815)
2020-03-19 15:13:15.493 T:26481 DEBUG: CDVDVideoCodecAndroidMediaCodec:: Multi-Surface Rendering
2020-03-19 15:13:15.493 T:26481 INFO: CDVDVideoCodecAndroidMediaCodec:: Open Android MediaCodec OMX.MTK.VIDEO.DECODER.AVC
2020-03-19 15:13:15.493 T:26481 DEBUG: CDVDVideoCodecAndroidMediaCodec::UpdateFpsDuration fpsRate:24000 fpsscale:1001, fpsDur:41708
After refreshrate switch
Quote:2020-03-19 15:13:15.672 T:26493 DEBUG: CDVDVideoCodecAndroidMediaCodec:: width(1920), height(1088), stride(1920), slice-height(1088), color-format(2130706433)
2020-03-19 15:13:15.674 T:26368 DEBUG: Could not acquire timestamp
2020-03-19 15:13:15.678 T:26481 DEBUG: CVideoPlayer::HandleMessages - player started 1
2020-03-19 15:13:15.680 T:26493 DEBUG: CDVDVideoCodecAndroidMediaCodec:: crop-left(0), crop-top(0), crop-right(1919), crop-bottom(1087)
2020-03-19 15:13:15.680 T:26421 DEBUG: OnAVChange: CApplication::OnAVChange
2020-03-19 15:13:15.681 T:26493 DEBUG: CDVDVideoCodecAndroidMediaCodec:: Multi-Surface Rendering
2020-03-19 15:13:15.686 T:26493 DEBUG: CRenderManager::Configure - change configuration. 1920x1088. display: 1920x1088. framerate: 23.98.
2020-03-19 15:13:15.709 T:26358 DEBUG: DeleteRenderer - deleting renderer
2020-03-19 15:13:15.709 T:26358 DEBUG: LinuxRendererGLES: Cleaning up GLES resources
Please disable "Adjust Refreshrate to match video" and try again, please.
2020-04-01, 22:27
Okay, checking with VLC: https://git.videolan.org/?p=vlc.git;a=co...8cafb9cbbf - not funny, not nice - looks like it's a firmware bug of FireTV devices., sad - yeah would have been too perfect :-). The last workaround I did for Philips broke many other devices, therefore, please ask amazon to fix it :-) thanks.
2020-04-02, 03:38
(2020-04-01, 22:27)fritsch Wrote: Okay, checking with VLC: https://git.videolan.org/?p=vlc.git;a=co...8cafb9cbbf - not funny, not nice - looks like it's a firmware bug of FireTV devices., sad - yeah would have been too perfect :-). The last workaround I did for Philips broke many other devices, therefore, please ask amazon to fix it :-) thanks.
Thank you for checking, I will notify them. Is it a bug with how it deals with MOV container?
2020-04-02, 06:14
It should affect each and every cropped video. But that's a idea to test.
Use ffmpeg -i yourvideo.mp4 -vf scale=1920:xyz outputxyz.mp4
Use 800,816,832,848,1072, 1056 for xyz and tell us which one is stretched to entire height. Remember: the forced height change will kill the aspect already, therefore check just for black bars on top and bottom. If there are none: affected.
Use ffmpeg -i yourvideo.mp4 -vf scale=1920:xyz outputxyz.mp4
Use 800,816,832,848,1072, 1056 for xyz and tell us which one is stretched to entire height. Remember: the forced height change will kill the aspect already, therefore check just for black bars on top and bottom. If there are none: affected.
2020-04-02, 07:17
And make sure to post logs, please for every file. If you name all of them e.g. output816.mp4 output800.mp4 output848.mp4 output1056.mp4 - then I can easily check in the log which "surface heights" it uses
2020-04-02, 10:31
(2020-04-01, 19:43)fritsch Wrote:I'm just wondering if enabling the 4K Stick's frame matching conflicts with Kodi's settings for framerate matching. Is the best solution to only enable framerate matching in Kodi's settings and to leave the 4K Stick's framerate match setting off?(2020-04-01, 19:06)Kodroid Wrote:(2020-04-01, 11:03)shrugg1e Wrote: Short question: On FTV Stick 4K its still not fixed the auto framerate switching inside the original Netflix app?Related question: if I choose to use it, should framerate matching be enabled in Kodi's settings or the 4K Stick's settings?
What has kodi's settings to do with another app?
2020-04-02, 12:49
I have both enabled. I think Amazon's setting only influences their Amazon prime app.
Proven to be wrong :-)
Proven to be wrong :-)
2020-04-02, 17:02
(2020-04-02, 06:14)fritsch Wrote: It should affect each and every cropped video. But that's a idea to test.
Use ffmpeg -i yourvideo.mp4 -vf scale=1920:xyz outputxyz.mp4
Use 800,816,832,848,1072, 1056 for xyz and tell us which one is stretched to entire height. Remember: the forced height change will kill the aspect already, therefore check just for black bars on top and bottom. If there are none: affected.
I can try this when I get home, and I will include a log. But so far my only issues have been with MOVs -- cropped mkvs (.264 and .265 video streams) have always displayed correctly and still do, e.g., an mkv of 1920x816 displays as 2.35 with black bars top and bottom. I'm not sure if I've ever tried a cropped MP4.
2020-04-02, 17:16
Curious to see, then we can compare. We tried your mov sample on Shield and -> all fine, therefore I don't think it's something in our ffmpeg demuxer.
2020-04-02, 17:31
(2020-04-02, 17:16)fritsch Wrote: Curious to see, then we can compare. We tried your mov sample on Shield and -> all fine, therefore I don't think it's something in our ffmpeg demuxer.
Yeah, it's strictly a problem with the combination of Fire TV 4k and Kodi and cropped MOVs -- the cropped MOVs display correctly in Kodi on Windows, in Kodi on Android phone, and in Plex on the same Fire TV 4k. Someone even said they display correctly in Kodi on 2nd gen Fire TV (not 4k) although I haven't verified that. Meanwhile, there is no problem with cropped MKVs.
I should be able to post logs with the converted vid tonight, thank you for your time. If there are any other players you'd like me to test them with on the fire4k, let me know if that would be helpful.
2020-04-02, 22:40
(2020-04-02, 17:31)jubilex Wrote: Yeah, it's strictly a problem with the combination of Fire TV 4k and Kodi and cropped MOVs -- the cropped MOVs display correctly in Kodi on Windows, in Kodi on Android phone, and in Plex on the same Fire TV 4k. Someone even said they display correctly in Kodi on 2nd gen Fire TV (not 4k) although I haven't verified that. Meanwhile, there is no problem with cropped MKVs.
If MKV containers work perfectly you could always use FFmpeg to convert your MOV files to an MKV (or likely MP4 as well) container without having to re-encode. Save the following code as a batch file, ie. FFmpeg_mov2mkv.bat, making sure your change the SET FFMPEG variable line to reflect your FFmpeg executable path.
FFmpeg_mov2mkv.bat:
@echo OFF
SET FFMPEG="C:\FFMPEG\ffmpeg.exe"
FOR %%a IN ("*.mov") DO %FFMPEG% -i "%%a" -c copy "%%~na".mkv
Then just place any MOV files to be converted to MKV container into the same folder as the batch file and double-click it. All MOV files will be converted to MKV files in seconds without needing to re-encode. If you'd prefer to convert to MP4 then just change the end of line 3 from .mkv to .mp4 and resave the file as FFmpeg_mov2mp4.bat.
2020-04-03, 00:37
(2020-04-02, 22:40)88keyz Wrote:I ran the command you gave and did all the output resolutions suggested. I also did versions of the 800 resolution converted to mkv and mp4.(2020-04-02, 17:31)jubilex Wrote: Yeah, it's strictly a problem with the combination of Fire TV 4k and Kodi and cropped MOVs -- the cropped MOVs display correctly in Kodi on Windows, in Kodi on Android phone, and in Plex on the same Fire TV 4k. Someone even said they display correctly in Kodi on 2nd gen Fire TV (not 4k) although I haven't verified that. Meanwhile, there is no problem with cropped MKVs.
If MKV containers work perfectly you could always use FFmpeg to convert your MOV files to an MKV (or likely MP4 as well) container without having to re-encode. Save the following code as a batch file, ie. FFmpeg_mov2mkv.bat, making sure your change the SET FFMPEG variable line to reflect your FFmpeg executable path.
FFmpeg_mov2mkv.bat:
@echo OFF
SET FFMPEG="C:\FFMPEG\ffmpeg.exe"
FOR %%a IN ("*.mov") DO %FFMPEG% -i "%%a" -c copy "%%~na".mkv
Then just place any MOV files to be converted to MKV container into the same folder as the batch file and double-click it. All MOV files will be converted to MKV files in seconds without needing to re-encode. If you'd prefer to convert to MP4 then just change the end of line 3 from .mkv to .mp4 and resave the file as FFmpeg_mov2mp4.bat.
In VLC and Plex on Fire 4k, all played back correctly -- black bars on all except 1056 and 1072 where I think they were cut off by overscan.
In Kodi on Fire 4k, all played back stretched, with no black bars. Since 100% of all the other hundreds of cropped MKVs in my collection play back correctly, I'm guessing there must be something different with these particular streams regardless of what container they're packaged in?
Here is the log including playback of all the files you suggested (output800.mov etc), and your cropped Pulp Fiction sync-test.mkv which displayed correctly: aduzulerim.kodi (paste)