futeko.com FORUM
Old Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: futeko.com on July 27, 2016, 03:44:34 PM
-
The batch file below gives some audio/video output information for Q5/Q10 Pro which may be useful in diagnosing problems.
It is UNOFFICIAL.
It outputs log info from Q5/Q10 Pro which is always present in the background but usually you'd not get to see. It doesn't change anything on Q5/Q10 Pro and therefore is completely safe. I don't know what all of the headings mean(!), but this tool may be of use in diagnosing some specific playback problems.
The FrcInRate and FrcOutRate heading are of particular interest. How they match up may be related to when and how often frame skips occur. HiMedia are doing their own work on fixing the framerate mismatch problems, but input from the community is also appreciated.
Instructions:
1. Decompress this zip file to a Windows PC (Q5Q10PRO-OUTPUTINFO.1): http://www.mediafire.com/download/6a22nvcb5gczmza/Q5Q10PRO-OUTPUTINFO.1.zip
2. Run the /Q5Q10PRO-OUPUTINFO.bat file. It will launch in a Command Prompt window.
3. Enter IP address of Q5/Q10 Pro.
4. Initially you'll only get the lower portion of the screenshot below. The rest will appear when you play video.
(http://www.futeko.com/misc/Screenshot (9).png)
-
thanks futeko,
i will try this evening and i will post my results
-
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/EEROR%20Q5Q10PRO-OUTPUTINFO_zpswbc45yul.jpg)
-
@LeFric
Check in HiMedia Box setting report IP-Address is some with IP-Address input in Q5Q10PRO-OUPUTINFO.bat.
-
2160P60
keep ratio
24P OFF
without autoFMTswitch_1.0.10
i made some test with MKV 1080p
Edge to Tomorrow
(http://img15.hostingpics.net/pics/981656edgetotomorrow.jpg)
Batmann vs superman
(http://img15.hostingpics.net/pics/787431batmanvssuperman.jpg)
the revenant
(http://img15.hostingpics.net/pics/816083therevenant.jpg)
-
a) It reports 48P in! Never seen that frame-rate on commercial releases. Is this a mistake or you have special sources for it?
The only place I see 48P being used is HFR reproduced by some HQ cinema projectors. It is not a current standard for home cinema and as far as I am aware of neither planned for.
Obviously it will have a frame-rate mismatch. You can test it during the subtitle scroll down.
Forcing it down to 24P might produce better results. The auto-frame-rate switch tool could potentially do that for you.
b) Asked pcristy if a test version for the auto frame-rate switch tool can be made available doing 24P to 24P/1001 mapping.
That would eliminate one source for the signaled problems.
c) We need explanations what the different values actually represent. Specifically fps: At the top, FrcInRate: and FrcOutRate
The examples give 3 different values.
-
New version with more info. Thanks pcristi.
-
@Nice Monkey
look to be intended for some codec, but this not exclude bug for H264, DVD NTSC, or others.
LE: autoFMTswitch_1.0.10 --> ON
H264 == 48.0
(http://www.mediafire.com/convkey/9ef4/tlgj3amyg6z01njzg.jpg?size_id=5)
MVC == 24.0
(http://www.mediafire.com/convkey/b75a/m758cx8hxpski9nzg.jpg?size_id=5)
DVD PAL == 50.0
(http://www.mediafire.com/convkey/9cf6/7pv5426xyabbggbzg.jpg?size_id=5)
DVD NTSC == 48.0
(http://www.mediafire.com/convkey/e983/crt8k5hsn6vr63gzg.jpg?size_id=5)
Altered FrcInRate playing video can be audio out of sync.
-
a) I am afraid it still is too cryptic for me and probably others. Still don't capture what each variable means regarding frame-rates (where measured and used)?
b) Could you explain to me why H264 ==> 48.0 is a match. I do own a lot of BD's and some are encoded with H264 but these are all 24P/1001. The answer to the previous question may explain it?
c) In all your examples "FrcOutRate = fps at the top" except a probably PAL DVD source which probably is interlaced and reported as 25P. But the example of OlivierQC produces different values which I can't place at all.
-
@Nice Monkey
a) new version of Output Info Diagnostic Tool, show a lot infomation, and still can be add more, but too much information witch is not understandable for many user not usefully in public forum witch is not developer(HiSilicon) support forum.
LE: b) NO. I don't see logic, but force to 24.0 video is slow motion, double playing time, audio out of sync on specific codec.
24000/1001 = 23.9760, and I don't get how to set FrcInRate = 23.97, just integer value work for me.
c) using autoFMTswitch ON.
a) I am afraid it still is too cryptic for me and probably others. Still don't capture what each variable means regarding frame-rates (where measured and used)?
b) Could you explain to me why H264 ==> 48.0 is a match. I do own a lot of BD's and some are encoded with H264 but these are all 24P/1001. The answer to the previous question may explain it?
c) In all your examples "FrcOutRate = fps at the top" except a probably PAL DVD source which probably is interlaced and reported as 25P. But the example of OlivierQC produces different values which I can't place at all.
-
@Nice Monkey
a) new version of Output Info Diagnostic Tool, show a lot infomation, and still can be add more, but too much information witch is not understandable for many user not usefully in public forum witch is not developer(HiSilicon) support forum.
b) NO. I don't see logic, but force to 24.0 video is slow motion, double playing time, audio out of sync.
c) using autoFMTswitch ON.
a) I am afraid it still is too cryptic for me and probably others. Still don't capture what each variable means regarding frame-rates (where measured and used)?
b) Could you explain to me why H264 ==> 48.0 is a match. I do own a lot of BD's and some are encoded with H264 but these are all 24P/1001. The answer to the previous question may explain it?
c) In all your examples "FrcOutRate = fps at the top" except a probably PAL DVD source which probably is interlaced and reported as 25P. But the example of OlivierQC produces different values which I can't place at all.
Thanks. I know that cinema projectors typically show each frame twice. So a 24.0 movie input comes out visually as 48.0 out of the projector. If that source is captured (mostly referred to as telecine) then you get 48.0 for sure. They do so to eliminate flicker.
Telecine captures in a MKV container do circulate for sure. Personally never use(d) those . All TV's do the same but at much higher display rates, but that signal stays inside the box .
-
@futeko
Our question for HiMedia is still remaining in order to get rid of drop frame with 23.976 fps movie.
- H264 playing with FrcInRate = 48.0 is maybe bug, they have to change to 24.0 or 23.976 or 47.952?
- FrcInRate change from 24.0 to 23.976 need to be done for all codec when video is 23.97* fps?
-
@futeko
Our question for HiMedia is still remaining in order to get rid of drop frame with 23.976 fps movie.
- H264 playing with FrcInRate = 48.0 is maybe bug, they have to change to 24.0 or 23.976 or 47.952?
- FrcInRate change from 24.0 to 23.976 need to be done for all codec when video is 23.97* fps?
I think the core of the problem is the mismatch between FrcInRate and FrcOutRate. There appears to be a misreporting of fps for FrcInRate.
All this info (previous to this thread - i.e. your earlier emails) has been fed back to HiMedia and they have responded acknowledging it. They are working on getting playback perfect.
-
I am still getting this, even with the newer version:
"error: device offline"
Yes, the IP address is correct :)
Yes, the box is on line :)
The box even reports success in starting the service?
Using FW 1.0.6 + "autoFMTswitch_1.0.11".
Something I have missed?
-
Thanks for answer.
HiMedia/HiSilicon are best team witch can know what they programming witch parameter can be change with out creating more problems audio/subtitles out of sync to reach clear crystal playing.
Keeping my finger cross get this with next update firmware.
@futeko
Our question for HiMedia is still remaining in order to get rid of drop frame with 23.976 fps movie.
- H264 playing with FrcInRate = 48.0 is maybe bug, they have to change to 24.0 or 23.976 or 47.952?
- FrcInRate change from 24.0 to 23.976 need to be done for all codec when video is 23.97* fps?
I think the core of the problem is the mismatch between FrcInRate and FrcOutRate. There appears to be a misreporting of fps for FrcInRate.
All this info (previous to this thread - i.e. your earlier emails) has been fed back to HiMedia and they have responded acknowledging it. They are working on getting playback perfect.
-
@LeFric
Check in HiMedia Box setting report IP-Address is some with IP-Address input in Q5Q10PRO-OUPUTINFO.bat.
Here I show you how the HiMedia is detected and operating the network.
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/ERROR%20Q5Q10PRO-OUTPUTINFO_2_zpsuvbtlonp.jpg)
I still have the same error screen ...
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/EEROR%20Q5Q10PRO-OUTPUTINFO_zpswbc45yul.jpg)
How can it be?
-
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is 100% correct and the errors you are getting indicate that the IP address you are using is incorrect or perhaps incorrectly formatted.
-
@pcristi or futeko.com
Would it help you if I do 4k demo tests or is it not necessary ?
-
All testing is useful.
One thing I would say is that this thread is running parallel to the work HiMedia are doing. It would be great if users could figure out something to help resolve this problem but HiMedia are doing their own testing and have access to better diagnostics.
-
maybe something with the router.
-
@pcristi or futeko.com
Check 720p 23.976 video. It has diferent from 1080p behavior - no flicker. Unfortunally I can't check it myself before next weekends.
-
@LeFric
Check in HiMedia Box setting report IP-Address is some with IP-Address input in Q5Q10PRO-OUPUTINFO.bat.
Here I show you how the HiMedia is detected and operating the network.
I still have the same error screen ...
How can it be?
check your firewall
-
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is 100% correct and the errors you are getting indicate that the IP address you are using is incorrect or perhaps incorrectly formatted.
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/ERROR%20Q5Q10PRO-OUTPUTINFO_3_zpsvtwvqobx.jpg)
-
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is correct. It works.
The problem is incorrect IP address or something else to do with your network. It's a simple batch file, with the error messages you're getting the problem cannot be anything else.
-
autoFMTswitch_1.0.10 --> ON
TV output 1080p, 720p 23.976 video
(http://www.mediafire.com/convkey/a30b/j3uc53ba9u5a9r0zg.jpg?size_id=5)
@pcristi or futeko.com
Check 720p 23.976 video. It has diferent from 1080p behavior - no flicker. Unfortunally I can't check it myself before next weekends.
-
All testing is useful.
One thing I would say is that this thread is running parallel to the work HiMedia are doing.
It would be great if users could figure out something to help resolve.
yes i agree with you, in my case i do not have acknowledge, i'm so sorry.
this problem but HiMedia are doing their own testing and have access to better diagnostics.
-
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is correct. It works.
The problem is incorrect IP address or something else to do with your network. It's a simple batch file, with the error messages you're getting the problem cannot be anything else.
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/ERROR%20Q5Q10PRO-OUTPUTINFO-4_zpspul7e3xd.jpg)
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/ERROR%20Q5Q10PRO-OUTPUTINFO_3_zpsvtwvqobx.jpg)
-
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is correct. It works.
The problem is incorrect IP address or something else to do with your network. It's a simple batch file, with the error messages you're getting the problem cannot be anything else.
Now the quoted is not an answer to my feedback, but it could have been.
I am sure what the IP for the box is, it is using a static address.
I don't have a firewall between my PC and the Q5 box.
The batch file may be simple/basic but it doesn't work on my by box.
I hope somebody is able to come up with a fix or at least some work around.
-
Hello jeps
"error: device offline" --> adb service not run in box
"error: device not found" --> adb can't connect to device
reboot router
autoFMTswitch --> Did you post you successfully install, so run RUN_ME.bat and choose 9 Reboot Media-Player.
If Media-Player reboot this mean working, copy Q5Q10PRO-OUPUTINFO.bat in some folder with RUN_ME.bat and give try.
If Media-Player NOT reboot reinstall HMD 1.0.6, 1st try with menu update, and if not help then with restore button.
if Q5Q10PRO-OUPUTINFO.bat NOT work but RUN_ME.bat work edit Q5Q10PRO-OUPUTINFO.bat
- comment (rem) line 13 --> rem set /p var= IP:
- edit line 17 adb connect %var%:5555 to adb connect 192.168.1.38:5555, and give try.
I am still getting this, even with the newer version:
"error: device offline"
Yes, the IP address is correct :)
Yes, the box is on line :)
The box even reports success in starting the service?
Using FW 1.0.6 + "autoFMTswitch_1.0.11".
Something I have missed?
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is correct. It works.
The problem is incorrect IP address or something else to do with your network. It's a simple batch file, with the error messages you're getting the problem cannot be anything else.
Now the quoted is not an answer to my feedback, but it could have been.
I am sure what the IP for the box is, it is using a static address.
I don't have a firewall between my PC and the Q5 box.
The batch file may be simple/basic but it doesn't work on my by box.
I hope somebody is able to come up with a fix or at least some work around.
-
What is the IP address when checked using the Q10 Pro in Settings - Network?
The batch file is correct. It works.
The problem is incorrect IP address or something else to do with your network. It's a simple batch file, with the error messages you're getting the problem cannot be anything else.
Now the quoted is not an answer to my feedback, but it could have been.
I am sure what the IP for the box is, it is using a static address.
I don't have a firewall between my PC and the Q5 box.
The batch file may be simple/basic but it doesn't work on my by box.
I hope somebody is able to come up with a fix or at least some work around.
this is only Diagnostic Tool , it's NOT necessary for smooth playback the important is the patch (http://www.futeko.com/newforum/index.php?topic=1043.0)
-
if Q5Q10PRO-OUPUTINFO.bat NOT work but RUN_ME.bat work edit Q5Q10PRO-OUPUTINFO.bat
- comment (rem) line 13 --> rem set /p var= IP:
- edit line 17 adb connect %var%:5555 to adb connect 192.168.1.38:5555, and give try.
Yes now !!!! but to see the information I had to add the pause you see. Is this correct?
(http://i1317.photobucket.com/albums/t637/LeFric2/HiMedia%20Q10%20Pro/ERROR%20Q5Q10PRO-OUTPUTINFO-5_zpshif7ytbg.jpg)
-
Normal script is assume 192.0.2.2 is not use on your network, and wait time is 5000 milliseconds.
To have more time to read you can change timeout in milliseconds to wait for each reply (-w 5000) or Number of echo requests to send (-n 1) in ping command.
ping 192.0.2.2 -n 1 -w 5000 > nul
Pause is good if you want refresh information when press key.
Maybe is good to change Command Prompt windows layout from 80x25 to 80x50.
PS. You can custom scripts like you want/need.
Yes now !!!! but to see the information I had to add the pause you see. Is this correct?
-
Here are my results... made a BluRay ISO from a mkv (1080p movie @23,976fps)...
[attachment deleted by admin]
-
As with other testing, the tool reports incorrect FPS (FrcInRate 48fps). This is the core of the problem.
Good news is that Himedia already have a beta firmware which fixes most of this problem. I'm confident that it will be fixed 100% in next firmware.
-
As with other testing, the tool reports incorrect FPS (FrcInRate 48fps). This is the core of the problem.
Good news is that Himedia already have a beta firmware which fixes most of this problem. I'm confident that it will be fixed 100% in next firmware.
Very good news Futeko and wish the new firmware soon ;)