Xiaomi Yi Custom firmware with lastest revision

Hello , I have the same thing , the first file - short for 2-3 seconds , high Mbps , and then the rest of the recording in the next file with low Mbps. How to solve it ? microSD card ? mine is up to 30Mb / s to buy more expensive ? with 50-60Mb / s ? Is the fault of the firmware in the camera ??
Your microSD needs to be faster than your video. So if your card is 30Mb/s, your video can maximum have a bitrate of 30Mb/s.

Are you using aoutoexec.ash or custom firmware, or maybe both? If you attach it, I can have a look.
 
So if your card is 30Mb/s, your video can maximum have a bitrate of 30Mb/s.
...if your video has a bitrate of for example 45mbit/s (mbp/s) it needs at least a microsd writing speed of 5,625 mb/s (45:8), its different between mbit (video)and mbyte (microsd)!
Therefore a class10 card should be the minimum, but it also give cards with smaller writing speeds. But sometimes despite of that many people have file splitting problems, so the faster the better.
First format your card with fat32 (32kb) and try again with a empty card.
So i have no problems recording in 2k with 45mbits for a video about 16minutes and 7 GB splitted in 4 files--> all same bitrate and size.
Could be the card is very full of footages i became problems recording in 45mbits, but until yet no problems and the footages look smoother and sharper than with 35mbits.
Maybe its better setting via AFT all resolutions to CBR so you have always the same bitrate without heights above adjusted bitrate.

LG gente
 
but I was able to achieve 1440p ( 2,560x1,440 ) only 30fps for NTSC and PAL 25fps
...the sensor only can do 2304x1296, 2560x1440 is only made by upscaling the 2304x1296 resolution in camera with the "writel" command and that means not a better quality.
 
now my camera films a 2gb file at 35mbps then do a 2 sec video at 40 mbps and then continues with a 21 mbps....
Maybe you start the recording the first clip before the script has loaded. Then the next clip is started, and stopped shortly after because the camera can't get rid of the data fast enough. Then the throttling algorithm kicks in, and you have a third recording at a lower mbit. But this is just me guessing... I put a beep at the end of my script, to know when it's done loading.

Yes, AutoExec + fw. custom 1.2.13
If you put your script and FW in a zip file, and then click "Upload a File" under the textbox here in the forum, I could look at them if you like.

...if your video has a bitrate of for example 45mbit/s (mbp/s) it needs at least a microsd writing speed of 5,625 mb/s (45:8), its different between mbit (video)and mbyte (microsd)!
Spot on, that is how it works 🙂 I write "Mb" for mega bit, and "MB" for mega byte, and there is eight bits to a byte.
 
So if your card is 30Mb/s, your video can maximum have a bitrate of 30Mb/s
spot out, it gives no card with unit of measurement in Mb/s, they have an unit of MB/s.
It means: "so if your card can do 3,75 MB/s writing speed your video maximum can have a bitrate of 30Mb/s"
Do not confuse users...
 
Do not confuse users...
I am sorry if I caused confusion. 😳 I don't see any contrast in what you and I are saying. I just find it easier to think in terms of bits per second for the camera AND the card, for comparison. Let me clarify what I was trying to say.

Secure Digital Association currently has two ways of stating a cards speed. The first is a "C" with a number in it, for example 4 printed on the card. This number tells you the number of MegaBytes per second the card can handle. If the SD card says 4 inside the "C", that means it can handle a stream of data at a rate of 4MegaBytes per second. To find the rate of bits per second it is then necessary to multiply by eight, because eight bits make a Byte. In the case of a Class 4 card, that gives 4MBytes x 8 bits per byte = 32 Mega bits per second. To store a video with a data rate of 45 megabit per second, a class 6 card should be sufficient. Because that card handles 6MegaBytes x 8 bits = 48 Megabits per second. However there are fake and overrated cards on the market, but free tools exist to check the actual speed, so there is no need to be wondering if a card is too slow.

The other way of stating a cards speed is the "UHS" rating. UHS stands for Ultra High Speed, and requires a UHS compatible device. If you use a UHS memory card in a non-UHS host, it will default to the standard data bus and use the Class rating. It works like the class rating above, but multiplied by 10. Also the number is inside a "U". This means that if a card has the number 1 in a little "U" printed on it, it is designed to work at speeds up to 10 MegaBytes per second. If it says 3 in the "U" then it's 30 MegaBytes per second. Now if you want to know the bitrate, multiply by 8. So for our UHS 3 card, that would be 30x8 = 240 Mega bits per second.

A rating like Class and UHS is the minimum serial data writing speed, but both read and write speeds must exceed the specified value. These are the basics, but there are many nuances and caveats further down the rabbit hole. For those that want more on SDcards, speed and compatibility there is this, https://en.wikipedia.org/wiki/Secure_Digital or this https://www.sdcard.org/developers/overview/speed_class/ or there is google.
 
Hello Guys,

I'm quit new to this firmware flashing so i have a view questions if you guys dont mind?
I flashed my YI (Z23L) with the FW on the first page of this topic. (Big thanks😀)
The flash started and it succeeded to flash the cam.

Now my Super noob questions:
How can i check if the cam records at 35mbps?
And can i still use a script when the cam is flashed with the costum FW?
Last question is where can i get a good script, with noise reduction low and all that awesomeness that makes the video quality even better then it already is?

I hope that i'm not a pain in the ass with my questions😀

Greetings Peter
 
Hi, and welcome SteadyPete 🙂
How can i check if the cam records at 35mbps?
There are several tools for this. I use "Bitrate viewer" on windows. It's free. Google for the download, I forgot where I got it. Got it from here: http://www.winhoros.de/docs/bitrate-viewer/

And can i still use a script when the cam is flashed with the costum FW?
Yes.

Last question is where can i get a good script, with noise reduction low and all that awesomeness that makes the video quality even better then it already is?
Oh, there are several flavors. You will find a lot of them here on DCT, just use the search function here on the forum. I'm sure you'll find one you like 🙂 Also, check this out: https://github.com/PJanisio/Xiaomi_Yi_autoexec and this: https://github.com/funneld/XiaomiYi

Cheers 🙂
 
Last edited:
Thanks you very much for the quick reply and detailed answers @Bitmash 😀

But its still not completely clear what scripts i can use.
I only want the video quality in 1080p 60fps to be a bit more detailed, it's all so blurry now.
Even after i focused my lens.
 
you are welcome,
...you can use all scripts discussed and posted here. You can took a line of that script and put it to another script you like so you can set your own script. Use notepad++ it is shareware.
Mostly there is a description in autoexec what the command is standing for. Scripts are usually needed for adjustments cannot done by app. The 1080p 60fps you can set via app.
You can test that one in attachment to make the footages sharper, set noise to 500, set saturation, gamma, scene to potrait mode, exposure for dark and bright scenes and fix whitebalance and exposure.
Also set Filesplitting to 4GB and gives a beep when script is ready. That line you do not need set a hashtack before it. And also some resolutions and bitrates not setable by app.
2k resolution 30fps is better for sharpness 60fps makes the motions smoother for quick scenes, test it.
For bitrate and resolution viewing you can use "bitrate viewer" for free. Reading much here in forum would help and make you many things understanding.
 

Attachments

Thanks😀

I use the yi on my quadcopter and thats why i use this cam becuase it is cheap and can do 60fps.
I flashed the cam to run 1080p 60fps at 35mbps.

So i can just take a script that i like and then change the what is needed, thats awesome but i just jumped in this and it is not clear yet.
I will read as many as i can, hopefully it will be clear then😉

But the script you just posted, can i just use that one? ore do i need to makes changes to it in order to work correctly?

EDIT:
Also it say's in the HowTo file that before you start you need to set the video mode to 1920x1080 30p and after you loaded the script you may not go in the app.
So how do i change it back to the 60fps i need inorder to get decent footage?
 
Last edited:
...the modes you set via script overwrite the setting on app. If you change later resolution by app you have the new one you set in app. If restarting xiaomi you become that one from script again. If you do not loke script only rename or delete it. If you do not like a command in script set a hashtack (#) before it like in description of that line in autoexec.ash.
You can use and test that script without changing something , it is modified for sharpness and exposure.
Have fun...
 
Okay i just used the script and the quality is allready awesome! Big thanks!😀

It is indeed a bit noisy but it is quite dark in my house now so i will test it again when there is daylight.
Again thanks!
 
Okay i just used the script and the quality is allready awesome! Big thanks!😀

It is indeed a bit noisy but it is quite dark in my house now so i will test it again when there is daylight.
Again thanks!
...to noisy you can set the value for noise reduction from 500 to 1024, in daylight you can test with value 0!
 
...to noisy you can set the value for noise reduction from 500 to 1024, in daylight you can test with value 0!

Amazing, i will try it out tomorrow.
Thanks for your time mate! 😀
 
I noticed that the 1080p 60fps 35mbps footage is not that smooth anymore after using the script are the custom FW.
Any idea what can cause this?

I use the Samsung Pro 32GB sd UHS-1 Class 10 90MB/s.
 
you could try to bypass all script lines and then add one by one so you find which one create smoothness problem
 
you could try to bypass all script lines and then add one by one so you find which one create smoothness problem

Thats a great idea, but i'm super new to this and i don't quite understand how i can turn a line on ore off.
I know you need to set a hashtag (#) before a line, but i only see one continuous line of code.
Meaby you can give me a example on where to set the # ?

EDIT:
Okay i'm such a noob haha, i used notepad instead of notepad++😳
Now its al clear🙂
 
Last edited:
I don't see any difference in less or more noice when i change the value in the seccond line.
Is it because i dit not remove the # in the top line?

#noise reduction 0:no reduction(noisy but sharper)/16383:full noise reduction(no noise but less sharp)
t ia2 -adj tidx -1 500 -1
 
Last edited:
#noise reduction 0:no reduction(noisy but sharper)/16383:full noise reduction(no noise but less sharp)
t ia2 -adj tidx -1 500 -1
setting for example to:
"t ia2 -adj tidx -1 2048 -1" makes the footage less sharp but the noise becomes less to,
"t ia2 -adj tidx -1 0 -1" makes it noisier but the best of sharpness.
You must see an difference.
The last line of script must be an empty line (you see it at line number at the end)!
You are sure the script has started while booting cam and performing all lines?
You can hear it on long beep finishing boot.
I noticed that the 1080p 60fps 35mbps footage is not that smooth anymore after using the script are the custom FW.
Any idea what can cause this?
I am wondering why the footage not as smooth as without script, changing only gamma, noise, saturation, vibrance, scene mode, shadow/highlight exposure, file splitting that has nothing to do with the spped of video transmission. No problems on my xiaomi 23L.
Maybe you should test another player to watch videos.
Or copy footage thirst to harddisk and than view with player.
The resolution is set correctly to 1080p 60fps?
Delete that lines in script, they are made for a user had not set his firmware to 35mbit, this resolutions you can switch with modified firmwares by app. Or be sure you have the hashtacks in front of each line not to start that resolutions:

#2304x1296 30 fps 35mbps
#writeb 0xC06CC426 0x02
#writew 0xC05C1EB2 0x420C

#1920x1080 60 fps 35 mbps
#writeb 0xC06CC426 0x03
#writew 0xC05C1EE2 0x420C

#1920x1080 45 fps 35 mbps
#writeb 0xC06CC426 0x04
#writew 0xC05C1F12 0x420C

#1920x1080 30 fps 35 mbps
#writeb 0xC06CC426 0x06
#writew 0xC05C1F72 0x420C
MFG
gente
 
Back
Top