futeko.com FORUM
Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: qqq1971 on July 17, 2016, 02:17:29 PM
-
Hi
I'm using firmware 1.0.3 + autoframerate patch for HMP.
Test video (23.976) http://www59.zippyshare.com/v/PzbF9IhC/file.html.
At 26 and 60 sec when pendulum jump forward. I think it's frame drops. It happends with firmware 1.0.5 too.
I've run command to check display state when video was playing. Display is switched to 23.976Hz. You can see log:
C:\Users\....\>adb shell cat /proc/msp/disp1
---------CFG_VDP_MMU_SUPPORT---------
---------Hisilicon DISP 1 State---------
State :Open
Formt/DispMode :1920x1080_23.976/2D
RightEyeFirst :Disable
VirtualScreen :1920/1080
Offset(L/T/R/B) :0/0/0/0
AspectRatioMode :Custmer Setting
AspectRatio :16:9
ColorSpace :BT709_YUV_LIMITED->BT709_YUV_LIMITED
Bright :50
Contrast :50
Saturation :50
Hue :50
Background (R/G/B) :0x0/0x0/0x0
Zorder(Bot->Top) :VIDEO->GFX
AttachRole :source
AttachDisp :display0
Interface :HDMI0
InitCount :7
OpenCnt[User/Kernel]:1/1
LowbandCount :0
DispType set :NORMAL SDR
WorkMode :SDR Path
C:\Users\....\>adb shell cat /proc/hisi/hiplayer*/fileinfo
************************Hisilicon HiPlayer00 Media File Info Begin*******************
Stream type: ES
Source type: LOCAL
File size: 32520192 bytes
Start time: 0:0:0
Duration: 0:1:7
bps: 3881542 bits/s
Is Divx File:NO
Program 0:
video 0 info:
stream idx: 0
format: H264
w * h: 1920 * 1080
fps: 23.976
bps: 0 bits/s
duration: 0:1:6
************************Hisilicon HiPlayer00 Media File Info End*********************
It's a HMP's bug I'm sure. I've installed Kodi autoframerate add-on and it's played that pendulum very smooth without any jumping. May be duration will help to find bug.
Can anyone check test video and confirm that HMP behavior?
-
I can't even figure out how to play it. It just gives me "Video problem" message.
-
1. Download file - Judder_Test_BD_3.zip
2. Unzip it - you will take Judder_Test_BD_3 catalog. It is Blu-Ray disk.
3. Copy Judder_Test_BD_3 catalog to internal disk or your file server to play from LAN.
4. Open Media Center and find Judder_Test_BD_3 catalog from your disk or LAN.
5. Run it. Media Center can not play BD menu so first title will run. First title has 23.976 framerate.
If you have HMP patch then TV will switch to 23.976Hz automatically. If you don't have patch turn on 24p on settings page. It's important to play that video with 23.976Hz.
-
I have test with pendulum too with Original Framerate from HMP and with the patch and yes same problem with jumping frame at same time of you
-
I got "Content can not be read" with media center when I hit the Ok button on the folder Judder_Test_BD_3.
-
Eriol, try open 00000.m2ts:
1. Open ES Explorer and go to folder Judder_Test_BD_3/BDMV/STREAM
2. Run 00000.m2ts - it's 23.976 video clip
3. Select Himediaplayer when popup window opens
vdevil, can you check 00003.m2ts too? It's 29.970 video clip and it is played with stutering for me.
00001.m2ts (24p) - is played fine
00002.m2ts (25p) - is played fine
00004.m2ts (30p) - is played fine
-
@pcristi,
I've reinstall autoFMTswitch: firstly uninstall old version and then install 1.0.7. It does not help. The pendulum still jumping at 26 and 60 sec (23.976).
I've checked installation. adb shell cat /system/etc/autoFMTswitch.sh | more - version 1.0.7 and adb shell cat /system/etc/init.bigfish.sh - there is call autoFMTswitch.sh. HiMedia 24Hz setting set OFF.
I'm still using firmware 1.0.3.
-
@qqq1971,may I was tired and placebo effect, let's continue on private message, not chat here
Thanks
-
I changed the thread title slightly to reflect that this is a potential problem with himediaplayer _ autofmtswitch patch and not a problem generally with standard firmware without patch.
-
I changed the thread title slightly to reflect that this is a potential problem with himediaplayer _ autofmtswitch patch and not a problem generally with standard firmware without patch.
Without patch is same, I have try with patch remove and 24p playback option activate and its same pendulum jump frame at same time so its himediaplayer problem and not the patch only
-
@futeko,
I disagree. I've tested it with clear 1.0.3 and 1.0.5 firmware without patch and setting 24p ON . The problem exists.
-
Do you get the same result with the 23.976 test files here: http://kodi.wiki/view/Samples
Specifically:
Section 4, numbers 1, 10 and section 5, number 2.
-
With and without patch, firmaware 1.0.3:
Section 4, numbers 1, FPS_test_1080p23.976_L4.1.mkv - the same problem.
Section 4, numbers 10, VC-1_23.976_sample.mkv - it's hardly to find jumper. at 60 sec clip ends, at 26 sec bang and not sure, motion too quickly.
section 5, number 2 - don't test
-
I managed to play the files.
Tried 00000.m2ts, 00003.m2ts, FPS_test_1080p23.976_L4.1.mkv and I don't have frame jumps. I have 1.0.5 without HMP patch 1080p/60Hz with 24Hz and Imprex Off.
-
I see the frame jumps on the same files with 24p mode enabled. i.e. output at 1080p 23.976hz. I also re-encoded the .m2ts as mkv to test the sample file and got the same jump. In 60Hz mode you wouldn't see them.
As qqq1971 says in OP, it would appear to be a bug with himediaplayer app because box output is set at 23.976.
-
I experienced frame drop only when using 1.0.5 Custom software . No frame drop in the official 1.0.5 firmware without the patch.
-
It's a weird bug to see now. There have been many Q5/Q10 Pro sold and a huge amount of testing done. It can't be a general problem experienced by all users.
Anyway, I've reported it to HiMedia together with samples. They will be able to test it more thoroughly.
-
In 60Hz mode you wouldn't see them.
So say I don't see drops because I use 1080p/60Hz as my Display setting?
-
In 60Hz mode you wouldn't see them.
So say I don't see drops because I use 1080p/60Hz as my Display setting?
Yes. It appears to be caused by 23.976fps video being output at 24.000hz rather than 23.976hz when in 24p mode (24p mode is actually 23.976hz or 24hz output depending on input).
If you're in 60Hz mode then everything gets output at 60Hz.
-
Do we know why do we have a frame jump/shutter at all? I mean if it's a rounding error between 23.976 and 24 we should get the same framejump with 60 as well because we have the same rounding problem there as well.
-
Do we know why do we have a frame jump/shutter at all? I mean if it's a rounding error between 23.976 and 24 we should get the same framejump with 60 as well because we have the same rounding problem there as well.
This is where it gets complicated!
https://en.wikipedia.org/wiki/Three-two_pull_down
https://en.wikipedia.org/wiki/Telecine
-
HiMedia are aware of this problem and will fix it.
In the meantime, installing the pcristi/looun autoswitch patch fixes the problem completely (as well as adding auto framerate switching output matching input frame rate for all fraemrates): http://www.futeko.com/newforum/index.php?topic=1043.0
-
In the meantime, installing the pcristi/looun autoswitch patch fixes the problem completely (as well as adding auto framerate switching output matching input frame rate for all fraemrates)
It doesn't fix the problem for me. I've tested:
1. Firmware 1.0.3 with and without patch, 24p setting ON and OFF, Imprex Engine N and OFF.
2. Firmware 1.0.5 with and without patch, 24p setting ON and OFF, Imprex Engine N and OFF.
Jump occurs in any cases.
-
Hi
me too have same issue. I notice with mkv movie 1080p (or less) 23.976 fps.
Also it seems (when it happens) go backward by a frame then forward by a frame. The result is a strange effect as "go-back-go frame" .
Q5 Pro with Firmware 1.0.5 and no patch at all.
I'll try with test suggested by futeko.
However it's singular when it appears. it seems appears every 30 sec (more or less), that match with other collegues.
Also (i have same issue with different old mediaplayer "xtreamer"), when it tend to play a 23.976 fps source by 24 fps output, mediaplayer must drop a frame every 42 sec (not every 34-26-60 sec).
But... how can it happens with a new/advanced media player as himedia claims.
Hope in a quick solution
-
Jump occurs in any cases.
After more pendulum watching I agree.
So only kodi add-on with Kodi dvdplayer works as it should.
I have fed this back to Himedia and am pushing them as hard as I can for a quick fix.
-
-
@Futeko
Do you mean in your last post, that kodi with his own player and the "Kodi ADDON- Frequency Switcher" can handle 23.976 fps without microstutters?
Because i have Kodi 16.1 with "Kodi ADDON- Frequency Switcher 3.3.3" and i have stutters with 23.976 files every 50sec (more or less). Wrapper is off.
Perhaps i make something wrong in Kodi?
Thank you Futeko :)
Yes. At least with the test samples mentioned in this thread playback appears perfect with dvdplayer and the kodi switcher addon. I've just watched them again and no stutter 9perceptable to me at least), not at 26 seconds or 50. The stutter problem with himediaplayer doesn't appear to be Q5/Q10 Pro hardware, which has HDMI output set to 23.976Hz, it's the himediaplayer app.
-
-
Can you point me to a testing sample (e.g. one of the Kodi wiki sample files) where you see stuttering every 50 seconds with Kodi dvdplayer + Kodi autoswitch add-on?
-
FPS_test_1080p23.976_L4.1.mkv
Microstutter at 54sec, 104sec, 154sec and so on.
-
Same here, only wrapper.
Kodi works well, but no AAC 5.1. :(
-
I have the same problem and we need a solution ASAP please!
-
For me, no stuttering at all. Just problem of passthrough AAC 5.1 (only pass as LPCM).
-
I have the stuttering also. Only purchased a few days ago. Very distracting. Have went back to my Mede8er 600xd already.
Disappointing as 4K playback via USB looks amazing, but watched a full movie in 1080p last night (mkv) and the judder was very distracting.
-
HiMedia are aware of the problem and it's cause.
They are working on fixing it.
-
HiMedia are aware of the problem and it's cause.
They are working on fixing it.
I hope so, talking about the frame drop problem which is horrible in most movies @1080p!
-
Yes, I mean that problem.
It's been discovered that it's caused by a mismatch in reported fps to output Hz. The hardware is perfectly capable, it's just being fed wrong information. So cause is known. HiMedia just have to fix it.
-
Yes, I mean that problem.
It's been discovered that it's caused by a mismatch in reported fps to output Hz. The hardware is perfectly capable, it's just being fed wrong information. So cause is known. HiMedia just have to fix it.
Many MKV movies report 24P when they really should report 24P/1001 instead. Have seen this numerous times as this problem has been around for many years already. You may expect players to play crummy content correctly by adjusting itself to this condition but calling it a bug is not really honest. Yes it is a real bug but within the program used to create the container with.
Why do many (older) other brand players not have this problem then? This is fairly easy to answer as most of current players just support 24P/1001 and call it 24P support, this regardless if 24P or 24P/1001 is reported. There are only very few real 24P movies circulating so very few people ever notice.
Now that Q10 Pro moved to the next level supporting all frame-rates correctly including distinguishing 24P from 24P/1001 it is observed as a degradation instead of an improvement. Very understandable but not technically correct. Mapping 24P back to 24P/1001 is a quick workaround which will bring one back to what other players are doing. In almost all cases it will have the desired effect as I repeat only few real 24P material exists. It can easily be done with a configurable auto frame-rate switch APP.
To deal correctly with this the frame-rate can be derived from the transport stream itself as a workaround. Doing so may in fact increase startup times for all movies checking for incorrect header information. If implemented that way then I hope this will be done for MKV only or made an option if performance is influenced noticeably.
You can on the other hand solve it yourself easily by correcting the container which remedies the root cause. I am clearly in favor of solving it that way. It also will make these videos play correctly with any other media player straight away. Honestly I would prefer Himedia to provide a simple (integrated) APP which adjusts/validates the header with the correct frame-rate information. This way the problem is eradicated instead of being spread. Together with the configurable auto frame-rate switch it provides an excellent and simple solution.
Always make BD ISO's myself from MKV movies again which re-inserts correct header and picture timing information. These files never give this error. Yes I know the file grows slightly bigger as the consequence and you may loose some by BD unsupported audio and subtitle streams. Recommend using the excellent freeware program tsMuxeR for this job. It is simple to use and is blazing fast as it never re-encodes.
By the way the whole 24P/1001, 30P/1001 and 60P/1001 confusion and standards is a leftover from the good old analog TV world with NTSC (Never The Same Color) as the US standard. Needing different carriers for the video and color signals it was implemented that way. Europe had PAL and SECAM not needing this.
-
About testing frame-rate mismatching. Saw a few test files producing jitter posted here but these were unsuitable for testing frame-rate mismatches.
Also all image processing on your TV (and AMP) should be turned off. On some TV's that is already a challenge as some features are build related.
Frame-rate mismatches work on horizontal lines and produce line over-runs or under-runs at fixed time intervals. To test this one needs a vertical moving image preferable with a fixed content. I use myself standard movie material for this being the end credits available on most movies. Get a nice scrolling black and white text image and look for horizontal disruptions. The total image should scroll smooth as silk when the correct frame-rate is applied. Seeing the difference between 24P and 24P/1001 or other mismatches is easy and undeniable as they produce horizontal line disturbances at regular intervals.
In the past saw many media players with a similar problem they always used 24P also where they should apply 24P/1001 instead. They did it as a consequence for commercial BD's which in fact all are 24P/1001 and never 24P.
Obviously different video problems may overlap each other. Not getting confused or distracted by looking at different problems Is key in solving them.
For persons having problems please do this simple test and report if it is your problem or a different one. As most movies include end credits finding one to test should not be a real problem.
-
Many MKV movies report 24P when they really should report 24P/1001 instead.
Do you want to say test video from first post has wrong header? If you saw first post you can see that HMP detect 23.976 video framerate and turn TV to 23.976Hz. And it is not mkv. It's m2ts container.
Saw a few test files producing jitter posted here but these were unsuitable for testing frame-rate mismatches
They are suitable to point that something is wrong with the player. It can be frame-rate mismatches (it's more possible) or another problem or multiple problems overlaping. It can be even wrong header if you shows that. There is not enough information to exactly say what root cause is. But if I see such drops on every 23.976 material I just believe my eyes and that test video i've found just simplifying demonstration of the problem.
-
Many MKV movies report 24P when they really should report 24P/1001 instead.
Do you want to say test video from first post has wrong header? If you saw first post you can see that HMP detect 23.976 video framerate and turn TV to 23.976Hz. And it is not mkv. It's m2ts container.
Saw a few test files producing jitter posted here but these were unsuitable for testing frame-rate mismatches
They are suitable to point that something is wrong with the player. It can be frame-rate mismatches (it's more probably ) or another problem or multiple problems overlaping. It can be even wrong header if you shows that. There is not enought information to exactly say what root cause is. But if I see such drops on every 23.976 material I just believe my eyses and that test video i've found just simplifying demonstration of the problem.
No that file has very probably no frame-rate problem. My message is don't throw all problems on a heap but try to identify different problems where possible. That way they can be solved quick and efficiently. Looking for a needle in a haystack is not the thing to go for.
I am trying to help unbundling frame-rate originated problems from others like probably yours. Himedia seems to be looking into frame-rate problems right now which I am sure exists too. But I am pretty sure by now that there is a mixed bag of problems reported here.
Of course everybody should report any problems found, but helping Himedia excluding/grouping reporting's will speed up fixes and that is good for everybody. Just saying "I detect a problem and they just should fix it asap" is very understandable but not the most effective. Of course everybody is entitled to do so, but I am convinced that extremely complex products like media players only can be improved well with the help of the community.
-
Of course everybody should report any problems found, but helping Himedia excluding/grouping reporting's will speed up fixes and that is good for everybody. Just saying "I detect a problem and they just should fix it asap" is very understandable but not the most effective. Of course everybody is entitled to do so, but I am convinced that extremely complex products like media players only can be improved well with the help of the community.
I agree in common with you. There is more then one problem. But since Himedia don't give us any diagnostic tool in most cases we can say only "I detect a problem and they just should fix it asap". And then there is a field of possibilities to do nothing - "it is no problem for me", "may be your mistake", "your AVR incompatible" and so one. So if I can provide some information and my supposes of most possible root cause I will. Else Himedia will do nothing.
-
I have posted a thread with a simple diagnostic tool. HiMedia are doing their own work on the problem but any help/info from the community is appreciated. http://www.futeko.com/newforum/index.php?topic=1086
-
Always make BD ISO's myself from MKV movies again which re-inserts correct header and picture timing information. These files never give this error. Yes I know the file grows slightly bigger as the consequence and you may loose some by BD unsupported audio and subtitle streams. Recommend using the excellent freeware program tsMuxeR for this job. It is simple to use and is blazing fast as it never re-encodes.
Cannot agree with it! Made a BD ISO from a mkv (untouched video, no reencode) and have the same frame drops! :(
-
Cannot agree with it! Made a BD ISO from a mkv (untouched video, no reencode) and have the same frame drops! :(
It only helps if you have the incorrect frame-rate reported problem. Run the diagtool and do the credit scroll down test to verify.
If the tool says 24P in then you have the problem. For movies it should almost always be 24P/1001 (=23.976).
I presume the MKV is the same size as the original BD for the movie part (typically 30G to 40 G) if not it probably was already re-encoded when you got it.
-
I hope this fix comes soon. I have retried the player 3 times now on different movies and it is unusable in its current state for me. No movie has played back without this issue.
-
It will be fixed in next firmware. HiMedia have a beta with the problem fixed (perfect match fps to output hz) for nearly all formats.
-
Just curious, but when is the new firmware expected ?
-
Just curious, but when is the new firmware expected ?
Sorry but I don't know. If I had to guess I'd say end August.
-
Thanks
-
Thanks from me also. Please note I am not bashing the player, besides this issue it is very good.
-
Thanks from me also. Please note I am not bashing the player, besides this issue it is very good.
Thanks. A very good thing about HiMedia above all other Chinese media player brands is that they will fix things.
-
Thanks from me also. Please note I am not bashing the player, besides this issue it is very good.
Thanks. A very good thing about HiMedia above all other Chinese media player brands is that they will fix things.
That's good news, I know many people who want to buy a Q10 Pro, but only when this problem is soon fixed!
-
So I assume the new firmware hasn't fixed this? On the basis I a watching something right now and see the same issue. Are we expecting another fire are update by end August?
-
So I assume the new firmware hasn't fixed this? On the basis I a watching something right now and see the same issue. Are we expecting another fire are update by end August?
The next European/international firmware (after 1.0.6) will fix this. The 23.976 problem is caused by a mismatch between the fps reported by himediaplayer and the output via HDMI. It has been fixed already in private beta.
Multiple references to 'next firmware' at different times on the forum are probably confusing, but this has been the plan since before 1.0.5.
HiMedia told me last week this new firmware might be this week. I would realistically expect end of this week at earliest, more likely early next.
-
So I assume the new firmware hasn't fixed this? On the basis I a watching something right now and see the same issue. Are we expecting another fire are update by end August?
The next European/international firmware (after 1.0.6) will fix this. The 23.976 problem is caused by a mismatch between the fps reported by himediaplayer and the output via HDMI. It has been fixed already in private beta.
Thanks futeko,
cross our fingers
Multiple references to 'next firmware' at different times on the forum are probably confusing, but this has been the plan since before 1.0.5.
HiMedia told me last week this new firmware might be this week. I would realistically expect end of this week at earliest, more likely early next.
-
Awesome news. Thanks!
-
I think this is fixed in FW 1.0.7..
24p mode on.
Anyone care to test?
-
i only test 2160p60 24P ON, with the test 23.976 pendule and it was OK as the previous ''Beta''1.0.7, but i do not tried resolution 1080p.
EDIT :
i will test ISO 3D this evening.
-
I think this is fixed in FW 1.0.7..
24p mode on.
Anyone care to test?
@futeko, firstly thanks for your efforts!
But there are still two possible bugs:
1. FrcInRate :47.94 |FrcOutRate :23.97
If decoder works with stream 23.970 then every ~166 sec will microfreeze.
2. From "Picture Information":
FieldMode : Frame
Type : Interlace
But source is progressive. Possible player does not correctly determine it and makes deinterlace progressive video. This is indirectly confirmed by doubling FrcInRate.
And can't interpret FrameRate(fps) : Real(23.99) FrameInfo(23976)
Why Real(23.99)?
[attachment deleted by admin]
-
@pcristi,
Can you check if DVD NTSC is 119.88 with audio out of sync and post result to forum.
I'm in vacation so I can't test it myself.
I've checked dvd-iso. See attached OUPUTINFO.txt
No out of sync. All seems ideal.
[attachment deleted by admin]
-
BTW what is "24p mode on" exactly?
-
BTW what is "24p mode on" exactly?
Home screen - Settings - Playback - 24Hz.
It should be on for frame rate matching video fps.
Needs to be relabelled really because it also enables 29.970 switching.
-
BTW what is "24p mode on" exactly?
Home screen - Settings - Playback - 24Hz.
It should be on for frame rate matching video fps.
Needs to be relabelled really because it also enables 29.970 switching.
So the answer to my question is something like: It's an option to enable 23.976, 24, ...?, ...?, 29.970 FPS playback with matching frequency (Hz) to the device's output. Without this setting the video output frequency will always be the one set in the Home screen - Settings - Display menu.
Do I understand this correctly?
-
So the answer to my question is something like: It's an option to enable 23.976, 24, ...?, ...?, 29.970 FPS playback with matching frequency (Hz) to the device's output. Without this setting the video output frequency will always be the one set in the Home screen - Settings - Display menu.
Do I understand this correctly?
Yes, you understand correctly. :)
-
Yes, you understand correctly. :)
Great, thanks! :)