Edit 20/9/2022:
Latest sd_uhs which works perfectly on 5D3 / EOS M / 100D and other DIGIC 5 models can be found in:
SD Overclocking - DIGIC 5 only (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228)
Info 1 (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240328#msg240328)
Info 2 (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240421#msg240421)
Original OP: (keeping it for documenting some of the info is outdated)
Hi!
One of my goals was to get stable 240 MHz SD overclocking preset across all DIGIC 5 models, so I was digging into SD stuff again for few weeks. and Thanks to 100D (https://www.magiclantern.fm/forum/index.php?topic=26250.msg236842#msg236842)(where 240 MHz doesn't work (https://www.magiclantern.fm/forum/index.php?topic=12862.msg239202#msg239202)) I could compare it directly to my 700D (where 240 MHz does work flawlessly).
I did find new things (related to SD configuration) which helped to move 240 MHz on 100D from "it doesn't work at all (https://www.magiclantern.fm/forum/index.php?topic=12862.msg239202#msg239202)" to it works partially, but not really usable.
After a lot of tests I noticed a pattern, and I thought . . and came up with a magic trick . . current state with the Magic Trick:
-5D3:
1. So far managed to record 512 GB of data at ~86 MB/s write speed (hacks enabled) with 240 MHz SD overclocking using Sandisk Extreme PRO UHS-I U3 170 MB/s SD card without problems.
2. We don't need to worry anymore about read/write operations while running overclocking process, I found a way to pause read/write operations --> Which mean better stability while overclocking and "Keep ML" option will work fine after formatting SD card in camera.
-100D / EOS M:
1. You will be able to record around **4 Minutes and 30 Seconds on average at ~80 MB/s write speed (hacks enabled), after that it will drop to 21 MB/s (switch to 48 MHz).
2. That's better than nothing.
3. On one try I could fill 64 GB SD card with 240 MHz at ~80 MB/s write speed without dropping to 21 MB/s on 100D.
4. After some more tests I noticed that when SD card becomes hot, the drop to 21 MB/s begin to happen, example (I think ambience was around ~31° C):
● First try I could record around 5 minutes then it dropped to 21 MB/s
● I restarted the camera and got another ~5 minutes then it dropped to 21 MB/s (SD card is hot at this stage)
● I restarted the camera again, this time recording was limited to ~3 minutes then it dropped to 21 MB/s
● I restarted the camera again, recording time was limited to ~2 minutes then it dropped to 21 MB/s
● I restarted the camera again, recording time was under 2 minutes then it dropped to 21 MB/s
High SD card/SD controller temperature seems a stability factor here for 100D and probably the same thing for EOS M.
To verify: I put 100D inside the Fridge, I managed to fill 64 GB SD card twice at 240 MHz @ ~80 MB/s without problems (~25 minutes of recording), it didn't drop to 21 MB/s.
I don't think the heat is the only factor for this issue, it might be there a some related SD configuration tweaks which we are not aware of might solve this problem,
I mean solves instability at 240 MHz at high temps. I doubt if it a hardware limit. And it seems only cams with shared Card/Battery door are effected by this issue.
5. Bonus: Also the new things I found allows some SD card to work at higher OC, my Sandisk Extreme PRO 95 MB/s U3 UHS-I now works on 100D at 192 MHz (instead of 160 MHz (https://www.magiclantern.fm/forum/index.php?topic=26250.msg239112#msg239112)).
I am expecting that more cards should work in general at higher OC for 100D/EOS M, no guarantee though.
**It seems to depends on SD controller/card temps!
-It's not for free:
Yes, you have to pay in order to get it.
Reverse engineering work takes a lot of hours and effort, *initially I wanted ML users to give back their support to ML project in someway since they are getting our support for free.
My other ML goals are to work on lossless, SD overclocking, Crop modes on a DIGIC 4 model . . which is 600D, and give some of my support to DIGIC 4 models.
The price is based on averaged used 600D cost here (in my country).
*Yeah, that was my initial plan a month ago, but things changed a little. Unfortunately I started to loss my energy on ML project, I still don't know if this a temporary thing.
But I am still selling 240 MHz at 600D cost, I might not buy a 600D or might buy it, take a look into it then sell it again.
Selling forks under GPL is completely normal, getting a fair price for a dev efforts is okay too.
-Price:
Total of 265 USD (Edit: Paid (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240214#msg240214))
Download (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128)available
-How to pay:
● Contact me here on the forum by sending a PM or on Discord (@thebilalfakhouri#1803) or on Reddit (https://www.reddit.com/user/bilal_fakhouri), Telegram (https://t.me/bilal_ml), Facebook (https://www.facebook.com/theBilalFakhouri/), Instagram (https://www.instagram.com/bilal_fakhouri/)or Twitter (https://twitter.com/FakhouriBilal).
● PayPal and Cryptocurrencies are accepted.
● 265 USD can be split across all interested users or supporters. When the total is reached, all code will be released to everyone
● I will update the collected amount frequently after each payment.
-Notes:
● Tests were done using Sandisk Extreme PRO U3 UHS-I 170 MB/s
● There is no 100% guarantee of success, don't blame me
● No refund
● Both source code and the new sd_uhs.mo would be released after we collect the full amount (265 USD)
You will have to wait after you pay . . until we reach the goal, nothing would be released if we didn't reach the goal.
What if there were no enough buyers? Let's wait 30 days at least. Then we will talk.
● The trick I used could be risky, and might damage SD card or SD controller . . but to be fair, I don't know. So far I didn't notice issues.
● The new 240 MHz preset has been tested by me (100D/5D3), ilia3101 (5D3/EOS M) and Walter (EOS M). Their reports were similar to as I described in "current state" above.
● Will you need a fast CF card anymore for 5D3? --> you might save some money by relying on SD cards and slower CF cards.
● Worst case scenario if new 240 MHz failed on 5D3 during recording, the card will become inaccessible and you might the lose the recorded clip. Until now that didn't happen to me (managed to record 512 GB) of MLV clips without issues.
More tests are needed by the community (by you) to verify that on 5D3.
-Old vs New sd_uhs :
Old: 192 MHz and 240 MHz doesn't work on 5D3, you are limited to 160 MHz (~63 MB/s write speed).
240 MHz doesn't work on EOS M / 100D, you are limited to 192 MHz (~70 MB/s write speed).
New: 192 MHz and 240 MHz does work on 5D3, 240 MHz goes up to ~86 MB/s write speed.
240 MHz does work on EOS M / 100D (as described above), 240 MHz gives ~80 MB/s write speed.
Currently I am away from cameras, will post demo videos soon! (for 5D3/100D).
Feel free to ask questions, chat and throw suggestions!
-Collected amount:
265 USD from 12 people.
-Remaining amount:
0 USD.
-Goal:
265 USD.
Goal reached!
Download:
The compiled version of the new module + source code have been posted in Reply #1:
TAKE ME THERE! (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128)
Happy testing!
Results:
Users reports recap (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240250#msg240250)
Credits:
Thanks to to buyers who helped to bring the new module to everyone:
TrincaEspinhas
gabriielangel
Danne
vastunghia
David Khoirul
notthesame
AceCom
Grognard
ilia3101
revelations
SebastianC
th0ma5
-Special thanks to ilia3101 for handling PayPal!
The module:
Source code and compiled version of the module can be found here:
New_240_MHz_and_sd_uhs.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/New_240_MHz_and_sd_uhs.zip) (Outdated)
Latest one + source code in SD Overclocking - DIGIC 5 only (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228) topic
Important infos in first post:
Take me to the first post (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240127#msg240127)
Details:
1.New GPIO registers:
Explaining will be added soon!
(Edit: Explaining was added in 9-1-2023)
These registers seem to be related to SD controller registers?
Their values change depending on clock speed in the function which toggle among default clock speeds e.g. like 48 MHz and 96 MHz (on 700D the function is ff337b78).
on 650D/700D these registers change from:
(used in default 96 MHz)
0xC022C634 = 0x577
0xC022C638 and others = 0x544
to
(used in defualt 48 MHz)
0xC022C634 = 0x555
0xC022C638 and others = 0x555
I called these registers GPIO because that what QEMU calls them, which are:
0xC022C634 (Has either same value as the rest of registers or has a value higher than them)
0xC022C638 (This register and below always share the same value)
0xC022C63C
0xC022C640
0xC022C644
0xC022C648
all of the following values are default values from Canon in default 96 MHz preset, except for 5D3 default clock is 48 MHz):
650D/700D:
0xC022C634 = 0x577
0xC022C638 and others = 0x544
6D: all of them 0x555
70D:
0xC022C634 = 0x566
0xC022C638 and others = 0x555
100D:
0xC022C634 = 0x655 (240 MHz never worked with these values (https://www.magiclantern.fm/forum/index.php?topic=12862.msg239202#msg239202))
0xC022C638 and others = 0x733
EOS M:
0xC022C634 = 0x734
0xC022C638 and others = 0x733
5D3: (tweaking them didn't have an effect on 5D3?)
0xC022C634 = 0x755
0xC022C638 and others = 0x755
If you look closely in DIGIC 5 models where 240 MHz works out of the box like 650D/700D/6D/70D, you will see the good GPIO range for high OC (like 240 MHz) is around 0x5XX.
in source code I called:
0xC022C634 as GPIO1
0xC022C638 and others as GPIO2
for my 100D:
0x599 for GPIO1, 0x555 GPIO2 worked, and it seems the best for 240 MHz preset.
0x588 for GPIO1, 0x555 GPIO2 works too on 100D
0x599 for GPIO1, 0x566 GPIO2 works too on 100D
0x577 for GPIO1, 0x544 GPIO2 (700D values) don't work very well.
Without tweaking these registers, 240 MHz never been stable on 100D/EOS M, so they are required and they are a part of SD puzzle.
2.The Magic Trick:
How the trick works:
On 5D3, 240 MHz is stable but only with SD write operations, as soon as the camera does read operation it make the card inaccessible (Block Transfer error), I made tests around a year ago on 5D3 and made sure and the problem was instability only with read operations (I wrote this info in forum, nothing new).
Same applies e.g. on 100D (and other models at some settings), when running benchmarks, write benchmark would be completed normally, then when benchmarks start reading test it either switch to 21 MB/s or make the card inaccessible.
The trick is to switch to 160 MHz before reading operation happens, then switch to 240 MHz before write operation happens, so whenever card is reading the clock speed would be 160 MHz (has stable read speed), and whenever card is doing writing it would be 240 MHz because the write speed is stable at 240 MHz, that's for 5D3. For EOS M / 100D same thing except for using 192 MHz for read operations.
No idea if it risky, well, in general the CPU changes its clock speed all the time, no idea if it comparable to storage clock speed.
I am wondering if some of SD card readers does that too for some cards.
During my tests, write speed performance was very stable, didn't notice any side effects, it seems the trick works flawlessly.
Think about it as downclocking, what if we used default 96 MHz (~40 MB/s), and underclocked it for read operations to 48 MHz (21 MB/s), would you think it's risky?
I don't think so, but who knows.
Nice work! Will donate soon 8)
Definitely going to pay.
Tbh as a very personal (and somewhat marketing) note I would be encouraged to pay more if I knew that this may cover future development of clean HDMI output on 5D3... that would make the 5D3 a really complete and powerful RAW camera. Why DIGIC 4? But hey, it is a matter of personal interest!
So again, going to pay.
Bilal, are you planning to provide a frequent update on the progress of the campaign? I think that would be helpful.
Thanks
Sergio
Hello, good idea and I will donate some as soon as I get your Paypal address.
Like vastunghia, if some of the Devs pledge to tackle Centering of presets, HDMI and other Hard to do fixes on EOS M, I would definitely chip in again (whether they succeed or not).
I think it is a good initiative, since all the devs here have been dedicated, they deserve a little something for their time, test gear, etc.
Thanks folks!
Quote from: vastunghia on September 07, 2022, 07:17:08 PM
Tbh as a very personal (and somewhat marketing) note I would be encouraged to pay more if I knew that this may cover future development of clean HDMI output on 5D3... that would make the 5D3 a really complete and powerful RAW camera. Why DIGIC 4? But hey, it is a matter of personal interest!
Please note the payment will go only for new 240 MHz preset at its current state!
Also, please don't pay if you are expecting other stuff.. Sorry, currently I don't have plans to work on 5D3 on other aspects.
off-topic but 5D3 already have clean HDMI output using 1.2.3 firmware, what are you looking for?
Maybe you referring to real-time preview at high resolution preset?
Re DIGIC 4: I wanted to work on it around two years ago for many reasons, it's not a really new interest . . working on certain model or features depend on dev inspiration, and on many factors
Quote from: vastunghia on September 07, 2022, 07:17:08 PM
Bilal, are you planning to provide a frequent update on the progress of the campaign? I think that would be helpful.
Of course! already wrote that in OP:
Quote from: theBilalFakhouri on September 07, 2022, 05:26:20 PM
-How to pay:
...
● I will update the collected amount frequently after each payment.
Quote from: gabriielangel on September 07, 2022, 07:43:44 PM
Like vastunghia, if some of the Devs pledge to tackle Centering of presets, HDMI and other Hard to do fixes on EOS M, I would definitely chip in again (whether they succeed or not).
I think it is a good initiative, since all the devs here have been dedicated, they deserve a little something for their time, test gear, etc.
It's a good idea yeah to support and say thanks to dev for their work (speaking in general).
Unfortunately I don't have new plans for working on other aspects for now, perhaps other devs might be interested.
off-topic:
On 100D/650D/700D using my build all crop modes is centered on sensor. There is a Hardware limit for centering RAW image on CMOS, so it's not 100% perfect but very close to center.
On EOS M I don't know, it should be very easy to adjust centering of crop modes presets there. If it's reached the limit, then nothing to do.
Quote from: theBilalFakhouri on September 07, 2022, 09:53:20 PM
Please note the payment will go only for new 240 MHz preset at its current state!
Duly noted, thanks for clarifying.
Quote from: theBilalFakhouri on September 07, 2022, 09:53:20 PM
Maybe you referring to real-time preview at high resolution preset?
Correct. HDMI out is pretty unusable with 5D3 in crop modes.
Quote from: theBilalFakhouri on September 07, 2022, 09:53:20 PM
Of course! already wrote that in OP:
Sorry I missed that part.
Thank you!
Update: 10 USD have been collected from one person.
Quote from: theBilalFakhouri on September 07, 2022, 10:02:06 PM
It's a good idea yeah to support and say thanks to dev for their work (speaking in general).
Unfortunately I don't have new plans for working on other aspects for now, perhaps other devs might be interested.
off-topic:
On 100D/650D/700D using my build all crop modes is centered on sensor. There is a Hardware limit for centering RAW image on CMOS, so it's not 100% perfect but very close to center.
On EOS M I don't know, it should be very easy to adjust centering of crop modes presets there. If it's reached the limit, then nothing to do.
It was only a general suggestion. I'll donate for the 240MHz, no problem. Don't forget to msg me your paypal address.
@gabriielangel
Your suggestion and any suggestions are welcome, I just talked about myself and described my current state regarding ML.
Even if things got a little off-topic, that's okay for this thread, we can move to other threads if you want to continue the discussion.
PayPal address has been sent.
excellent news!
regarding the 5d3, was any testing done to determine if the maximum recording bitrate using card spanning and overclock increases beyond the "limit" we found when overclocking to 160MHz?
@70MM13
Thanks!
Nope, write speed limit with Card Spanning is still about ~133 MB/s in LiveView with hacks enabled. Higher SD OC like 192 MHz and 240 MHz won't improve this if you already reached ~133 MB/s limit.
But due to faster SD card bandwidth (@ 240 MHz), the write speed almost would be splitted equally among CF and SD, ~50% of total write speed will go to CF and ~50% will go to SD, which means both cards would fill almost equally.
Update: 21 USD have been collected from two people.
Remaining amount: 244 USD.
That could seems strange to pay for a ML feature. But we had already asked to find a way to help ML devs! So I Will contribute for sure to thank you for what you achieved Bilal even if this feature will not be very useful for me.
I know you don't want to work on 5D3 to unblock correct framing liveview. but if you change your mind, you could ask money for the price of a new R5 ;)
thank you.
Quote from: Grognard on September 08, 2022, 10:41:54 AM
I know you don't want to work on 5D3 to unblock correct framing liveview. but if you change your mind, you could ask money for the price of a new R5 ;)
That's for sure!! ;) ;) ;) ;)
Quote from: Grognard on September 08, 2022, 10:41:54 AM
So I Will contribute for sure to thank you for what you achieved Bilal even if this feature will not be very useful for me.
Exactly the same here. I must confess that Bilal's achievement at first gave me the false hope of being able to achieve overall (CF+SD) higher write speeds... but I will pay nevertheless, even though the feature does not seem to be very relevant to me (it may even turn out to be counter-productive actually, as I currently have a 256 GB CF card and a 128 GB SD card, so my optimal recording ratio is 2/3 on CF and 1/3 on SD, which is approximatively the one I'm achieving now w/o SD overclock.)
Quote from: theBilalFakhouri on September 08, 2022, 02:03:11 AM
Nope, write speed limit with Card Spanning is still about ~133 MB/s in LiveView with hacks enabled.
Mmh in my experience I can reach far higher rates than 133 MB/s with Global Draw = OFF. Check the following shot:
(https://github.com/vastunghia/vastunghia.github.io/raw/main/ML.jpg)
152 MB/s as in the above image is pretty on the edge, very close to automagical stop, but I think something closer to 145 MB/s is definitely compatible with continuous recording on my 5D3. Should check better with the latest chunk of MLV files I took during August holiday trips, but I'm pretty sure.
Is this higher rate I'm observing simply enabled by the deactivation of Global Draw? So once again, just to be sure, is it confirmed that there is no effective write speed enhancement expected to come from the enabling of SD overclock?
Quote from: Grognard on September 08, 2022, 10:41:54 AM
I know you don't want to work on 5D3 to unblock correct framing liveview. but if you change your mind, you could ask money for the price of a new R5 ;)
+1 here!
Sergio
The numbers I get during recording on EOS M (and other cams) are misleading.
I recommend to use actual file numbers and recording durations to determine actual data write rates instead. Because lossless compression may cause a high variance I recommend to use non-lossless modes for benchmarking.
And because buffering may have some influence, too: Just recordings durations 4 minutes or above for good measurement.
Quote from: Grognard on September 08, 2022, 10:41:54 AM
That could seems strange to pay for a ML feature.
Is it strange or we are not used to it :P. many open source projects actually do that.
BTW, ML before 2013 was charging for new builds releases.
Quote from: Grognard on September 08, 2022, 10:41:54 AM
But we had already asked to find a way to help ML devs! So I Will contribute for sure to thank you for what you achieved Bilal even if this feature will not be very useful for me.
Thanks!
Quote from: Grognard on September 08, 2022, 10:41:54 AM
I know you don't want to work on 5D3 to unblock correct framing liveview.
I don't want? Nope! :)
I already tried many times during the last year on 5D3 but without success, improving preview in general is one my goals for DIGIC 5 models, that's why I started LiveView Investigation (https://www.magiclantern.fm/forum/index.php?topic=25287.msg230160#msg230160) two years ago. LiveView is really complex, working on it requires a lot of time and effort and also some good experience. I might get back to it at some point, no idea when. or may never get back, I don't know currently . .
Quote from: Grognard on September 08, 2022, 10:41:54 AM
..you could ask money for the price of a new R5 ;)
R5 sounds cool :)
I was thinking about R7 or R10 for a price of preview, R5 sounds too much :P
Quote from: Dmytro_ua on September 08, 2022, 11:10:50 AM
That's for sure!! ;) ;) ;) ;)
Quote from: vastunghia on September 08, 2022, 01:44:25 PM
+1 here!
Holy $h!t! getting a R5 would be an enough reason to let me leave ML, why would you do that? :P
Thanks for your support!
Quote from: theBilalFakhouri on September 08, 2022, 02:24:51 PM
Holy $h!t! getting a R5 would be an enough reason to let me leave ML, why would you do that? :P
C'mon dude, you would start porting Doom to the R5 as soon as you had it in your hands! :P
Quote from: vastunghia on September 08, 2022, 01:44:25 PM
I must confess that Bilal's achievement at first gave me the false hope of being able to achieve overall (CF+SD) higher write speeds.
When using Card Spanning (with fast cards), we will hit Memory (RAM) limit:
in 5D3, 240 MHz overclock used for SD, Play mode:
My CF benchmarks ~120 MB/s Write
My SD benchmarks ~90 MB/s Write
So in theory with Card Spanning it should be 90 + 120 = 210 MB/s but that
won't happen if you run CF + SD benchmarks, total write speed with card spanning benchmarks would be limited to ~
150 MB/s.
In LiveView it's around ~133 MB/s.
My CF: Sandisk Extreme PRO 64GB 160 MB/s UDMA7
My SD: Sandisk Extreme PRO 64GB UHS-I U3 170 MB/s
Quote from: vastunghia on September 08, 2022, 01:44:25 PM
152 MB/s as in the above image is pretty on the edge, very close to automagical stop, but I think something closer to 145 MB/s is definitely compatible with continuous recording on my 5D3.
Reported write speed during recording isn't accurate, I don't rely on it, it will always be higher in most cases.
And accurate way to measure max write speed in LiveView is by running benchmarks with hacks enabled, already did that in LiveView hacks (write speed improvement) (https://www.magiclantern.fm/forum/index.php?topic=26443.0), here (https://www.magiclantern.fm/forum/index.php?topic=26443.msg238364#msg238364).
Update: 95 USD have been collected from four people.
Remaining amount: 170 USD.
Huh, 95 and 170 . . remind me of something :P
Note: It's
not 265 USD per user, but it's total of 265 USD for one time can be paid by by multiple interested users or supporters. You only need to pay a part of 265 USD, not all of it.
Check the end of first post for current state:
Quote from: theBilalFakhouri on September 07, 2022, 05:26:20 PM
-Collected amount:
95 USD from four people.
-Remaining amount:
170 USD.
-Goal:
265 USD.
will join effort tomorow, whats the atatus of it anyway?
and i dont understand, we pay but wint be able to het it untill 265 reached ?
Sent from my SM-N975F using Tapatalk
Quote from: koopg on September 08, 2022, 11:46:55 PM
will join effort tomorow, whats the atatus of it anyway?
Thanks, status of what exactly?
Quote from: koopg on September 08, 2022, 11:46:55 PM
and i dont understand, we pay but wint be able to het it untill 265 reached ?
I didn't get your question . . but nothing would be released until we reach 265 USD goal. If you paid and if we didn't hit the goal yet, you will have to wait.
Already wrote that in first post.
Do you mean something else?
Quote from: theBilalFakhouri on September 08, 2022, 02:34:19 PM
Reported write speed during recording isn't accurate, I don't rely on it, it will always be higher in most cases.
Just ran a new test, with Global Draw disabled I get continuous rec. and
- Reported write speed: ~89 MB/s CF, ~60 MB/s SD, total ~148 MB/s
- Actual write speed (calculated from final MLV file size): 90.1 MB/s CF, 60.7 MB/s SD, total 150.8 MB/s
So reported write speed looks pretty reliable to me, at least on my 5D3.
Also, I do not understand if my results are in line with your expectation. When you say "in LiveView" you mean with Global Draw enabled, right? So cannot compare these with your 135 MB/s I guess.
Thanks for your clarifications
Sergio
@vastunghia
Let's continue in What is the Maximum write speed for 5D3? (https://www.magiclantern.fm/forum/index.php?topic=26641.msg240181#msg240181)
no, u nailed it, i was lost in the firat post
Sent from my SM-N975F using Tapatalk
Update: 160 USD have been collected from eight people.
Remaining amount: 105 USD.
Note:
PayPal seemed to take fees which I weren't aware of, I was updating the collected amount without fees. currently we have 160 USD (after fees).
To avoid fees, I think you need to use "Friends and family" option as payment type.
Thanks
Update: 189 USD have been collected from nine people.
Remaining amount: 76 USD.
Update: 194 USD have been collected from ten people.
Remaining amount: 71 USD.
Note: There is no low limit, any amount is welcomed.
Update: 229 USD have been collected from 11 people.
Remaining amount: 36 USD
You are so close to the new 240 MHz by now!
There is no low limit, any amount is welcomed
Buyers credit list will be posted after reaching 265 USD.
Update: 265 USD have been collected from 12 people.
Remaining amount: 0 USD
Goal reached!
The new module will be posted shortly
Testing time:
The a compiled version of the new module + source code have been posted in Reply #1:
TAKE ME THERE! (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128)
Happy testing!
EOS M with Samsung PRO Plus 128 GB
160MHz
Write≈68MB/s
Read≈75MB/s
192MHz
Write≈77MB/s
Read≈86MB/s
240MHz
Write≈ 93MB/s
Read≈ 23MB/s (got too hot probably or doesn't handle it correctly)
I'll later edit the post with some RAW video recording results at 192MHz.
For Devs: The Magic Trick has been revealed (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128), is it risky?
Users:
Please report your results/test here!
Thanks
EOS M @240 MHz
Working with
1) Sandisk Extreme Pro R170/W90 128 GB (SDSQXCY-128G-GN6MA)
2) Sandisk Extreme Plus R170/W90 128 GB (SDSQXWG-128G-GF6CA)
not working @240
- Sandisk Extreme Pro R200/W140 256 GB
- Sandisk Extreme R190/W130 256 GB
- Samsung Pro Plus R160/W120 256 GB
Quote from: theBilalFakhouri on September 10, 2022, 03:20:28 AM
For Devs: The Magic Trick has been revealed (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128), is it risky?
Yes , did you check it in quem? you don't know for sure what going on so , it just a "
poke in the dark"
and you got lucky until someone burns up there cam. In my opinion you need to find out what going on , a very good way is Log files
with I/O trace build , it log all activity for 30 to 60 seconds can't remember right now .
That how i got crop rec ,Liveview , High frame rate(48fps FHD) 3x1 5k & 4K full res. to work on 5d2
and crop_rec on the 50d . Plus including the very early compressed raw on d4 cams , there's just no other way to be sure.
My 2 cents
EOS M @240 MHz, with lvface hack
Tested with Danne's Aug 4, 2022 and Bilal July 31, 2022 Builds
I have two cards, both Sandisk Extreme Pro 170 MB/s, 128GB
1st card does not work @240 MHz (Records about 2 sec regardless of resolution , benchmarks at W 20.9 MB/s)
2nd card works:
I can record 2.8k 14bit continuous (Green)
3K 1:1 19.99fps 14bit Continuous (Green)
3K 1:1 23.976fps 12bit, I stopped after 3:30 minutes (Orange), recorded three clips in a row
As usual, the first clip recorded after preset change doesn't record long, then it records Correctly afterwards.
I use a power bank and dummy battery, the temp reached 54 degrees C after recording 3 clips (Ambient temp was 28 degrees).
@192 MHz, it usually peaks at 52 degrees when 3K 1:1 14 bits, 20fps or 48 degrees when 2.5K 14bits, with 28 degrees ambient temp.
I will run a full test to check frame corruptions next week.
Quote from: reddeercity on September 10, 2022, 06:22:07 AM
Yes , did you check it in quem? you don't know for sure what going on so , it just a "poke in the dark"
and you got lucky until someone burns up there cam. In my opinion you need to find out what going on , a very good way is Log files
What is quem?
Logs doesn't and won't help, changing clock speed is something normal in DryOS and I am not expecting I would got anything from LOGs, e.g. Canon does change SD clock speed many times during SD initialization.
My wondering if changing clock speed many times is harmful or not for SD cards and SD controllers, also as I said, think about it as underclocking, and in general underclocking is something considered to be safe.
My 700D does work at 240 MHz all time for both read and write, by using lower clock speed for reads it would seem safer to me, because it's underclocking.
So, the only way to know is by asking SD experts.
Quem is typo of qemu.
The IO trace log reddeercity is talking about is not a normal log, and can give you lots more info than you normally see, and can help. Fundamentally, he's saying that since you don't understand why it works, you can't know if it works safely. Which is a reasonable argument.
I do wonder if this is really related to dropping the speed for reads, it seems weird that would help (possible! But strange - the card is rated to do higher speed reads than writes). Here's a few tests you could run:
- do a 240 write, then change clock to 240 before doing a read: perhaps it's not 160 that fixes the read, but doing a mode change.
- do a 240 write, then change clock to 160 (or whatever is supposed to be good), but don't do any reads, then change to 240, then do the read. Perhaps 160 is relevant, but not required to be the final selected mode.
- do a 240 write, don't change clock for the read but do trigger a small pause. Perhaps the change to 160 helps simply because it takes some time, and this lets some other part of the system become happy.
These kinds of tests could be combined with IO trace to help us work out what the critical factor is.
Quote from: names_are_hard on September 10, 2022, 09:31:51 AM
Quem is typo of qemu.
......
Fundamentally, he's saying that since you don't understand why it works, you can't know if it works safely. Which is a reasonable argument.
sorry I have dyslexia :-[
Exactly!! :D
I'm using a1ex's locgic here , that the same argument he would make when many people come up ways of doing things that
couldn't be explained "
just work when you set xxx parameters in the reg's" will that didn't fly with him until it was understand fully.
Case in point the compressed raw , it was known about almost right from the beginning but it was a blackbox "still is to a certain extent"
e.g. 4.2.2. MJpeg (AVI) it there ,only cam to show promise so far (40D) , i have being poking at it for years so i hope 40D MJpeg development continues
once it work ok then i'll try to get it on 5d2 & 50d . (I don't have time to do reverse engineering anymore but i do have some time that i can code it to
5d2 &50d.
I could go on & on about examples of short cut that have some success in certon fearture but at best there posed a dangerest risk
and I don't what to be that guy that coded a short cut that caused damage or just simple Softbreak the cam.
Just trying to promote safe reverse engineering & coding :)
My 5D mark iii 3k 3.3k 3.5k UHD 14bit or 12bit can't more than 77mb(SD) at 240MHz.
Global draw off
1920 1080 mode can achieve 90-100mb(SD),CF is 61mb.
240MHz.
Global draw off
5760 3240 anamorphic fullres mode can achieve 117mb(SD)
CF is 61mb.
240MHz
global draw off
Benchmark
write is 95mb
read is 72.5mb
Global draw On
All mode 12bit or 10bit can record more times.
I used Sandisk micro sd 128G V30 A2,
CF card is Sandisk 128G Ext pro 160mb
Thank you!
I've tried.
It works flawless!
On 5D mark iii it's very stable, but it's not a real improvement because of the 133mb/s limit.
But I've noticed something intresting. My SanDisk 256g 170mbs use to work now with the brand new sd-uhs hack while it wasn't the case before, even in 160mbs. But use to work before on Eos M with old sd_uhs but not the New one!
on EosM it's very usefull! Now we can reach continuous 3k 10bits or continuous 5k anamorphic 14 bits lossless.
thank you Bilal.
Quote from: SebastianC on September 11, 2022, 02:12:23 PM
All mode 12bit or 10bit can record more times.
Really ? I didn't notice any improvement about records times. By the way it was already continuous in 3.5k 12bits and uhd 10 bits.
EOS M
ML Nighty build 2022Apr30
Glabal Draw off
Card Sandisk extreme pro 170 MB/s 512GB
192 Hz
write speed 59 MB/s
240 Hz
write speed <20 MB/s
Could you test this version?
https://www.magiclantern.fm/forum/index.php?topic=25781.msg240247;topicseen#msg240247
Same code more or less. Test it with 2.8k preset and turn bitdepth to OFF to enable 14bit.
Recap users reports for the new sd_uhs:
5D3:
192 MHz and 240 MHz works without issues.
-SebastianC's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240238#msg240238).
-Grognard's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240240#msg240240).
-vastunghia's report (https://www.magiclantern.fm/forum/index.php?topic=26641.msg240252#msg240252).
EOS M / 100D:
1. 240 MHz doesn't work with all Sandisk Extreme PRO 170 MB/s SD cards:
-SebastianC's report (https://www.magiclantern.fm/forum/index.php?topic=26511.msg240234#msg240234) on 100D using Sandisk Micro SD 128G V30 A2?, 240 MHz seems to work with new sd_uhs
-Walter's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240220#msg240220) using Sandisk Extreme PRO/Plus 170 MB/s on EOS M, 240 MHz does work with new sd_uhs
-gabriielangel's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240224#msg240224) using two Sandisk Extreme PRO 170 MB/s cards on EOS M, one of them worked at 240 MHz, the other one didn't work.
-anto's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240248#msg240248) on EOS M using Sandisk Extreme PRO 170 MB/s 512GB, it didn't work with 240 MHz.
-Danne's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240256#msg240256) using four Sandisk Extreme PRO cards on EOS M, all of the cards worked!
2. Some SD cards now works at higher OC presets with the new sd_uhs:
-TrincaEspinhas's report (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240216#msg240216) using Samsung PRO Plus 128 GB on EOS M (only 160 MHz was working with old sd_uhs)
-GianlucaM83's report (https://www.magiclantern.fm/forum/index.php?topic=26511.msg240231#msg240231) using Sandisk Extreme Pro 170 MB/s (only 160 MHz was working with old sd_uhs)
Thank you all for testing and feedback!
I expected the new sd_uhs and 240 MHz preset to work on EOS M / 100D using all 170 MB/s SD cards, unfortunately that didn't happen.
This a new issue to me, no idea why certain Sandisk Extreme PRO 170 MB/s doesn't work while other do work.
This would require more digging. I hope someday we will reach perfect 240 MHz on EOS M / 100D.
I tested on Extreme PRO 170MB/s V30 256gb card and working(eosm).
EDIT:
Also tested now and working on an Extreme PRO 95MB/s V30 32gb card.
Just for the record, tested 5D3 113 and all is well apparently (check detailed results here (https://www.magiclantern.fm/forum/index.php?topic=26641.msg240252#msg240252)).
Sergio
Quote from: Danne on September 12, 2022, 01:15:27 PM
Could you test this version?
https://www.magiclantern.fm/forum/index.php?topic=25781.msg240247;topicseen#msg240247
Same code more or less. Test it with 2.8k preset and turn bitdepth to OFF to enable 14bit.
tried, same.
Could formatting the card do something. I use it on Mac and erase it with exfat
I erase with dos fat on mac:
Tested 4 cards, all works! around 89Mb/s when doing benchmark and in practice around 77-80Mb/s when recording 2.8k 14bit(eos m).
These cards.
(https://i.postimg.cc/tgnW41PK/20220912-181416-jpg-800px.jpg)
Cool results, thanks Danne for testing. Lucky Sandisk Extreme PRO SD cards :P
I have added all new reports to this reply (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240250#msg240250).
Also I put a link to reports in first post.
I tried formatting the Sandisk Extreme Pro 170, 128GB card which doesn't work @240 with the Mac,but sadly, it still doesn't work.
The card which doesn't work is more recent than the one that does. Maybe it is a firmware revision thing?
Is there a tool I could use to display the SD Card's info.? This would help us find compatible cards.
Working Card serial begins with 213
Non-Working Card serial begins with 221
Formatted dos fat?
My 512 170MB/s serial is 212
btw found that formatting in exfat it reaches 62 MB/s with 192 Hz ::)
Sounds like LV mode, not play mode.
Cards not working maybe needs to be tested not being fakes. Benchmark in some fast card reader.
More likely Sandisk Extreme PRO SD cards which work at 192 MHz they aren't fake. And the problem could be that just the new 240 MHz on EOS M / 100D isn't perfect for every Sandisk Extreme PRO 170 MB/s SD card (for some reason).
The fake cards can't write faster than ~25-30 MB/s (from my own experience), I bought before one 95 MB/s and two 170 MB/s fake Sandisk Extreme PRO SD cards.
Other similar example, the new 240 MHz preset still doesn't work on EOS M using Sandisk Extreme PRO 256 GB 200MB/s R, 140MB/s W SD card. While the same card work on 650D at 240 MHz (Walter report).
More likely there are some unknown variations among 170 MB/s SD card (just guessing). And the issue should be fixable somehow in first place by changing some SD configurations which we are not aware of on EOS M / 100D.
Offtopic: Just another benchmark. Extreme Plus but no 5D3, M, 100D and not @240 MHz.
(https://abload.de/img/bench2067fdx.png)
Quote from: theBilalFakhouri on September 12, 2022, 09:17:42 PM
More likely Sandisk Extreme PRO SD cards which work at 192 MHz they aren't fake. And the problem could be that just the new 240 MHz on EOS M / 100D isn't perfect for every Sandisk Extreme PRO 170 MB/s SD card (for some reason).
Hard to tell for sure but if testers keeps reporting we'll get a better perception.
Funny when I tested an extreme 90Mb/s card both 240 and 192Mhz patch would perform about 65Mb/s.
Quote from: Danne on September 12, 2022, 08:20:52 PM
Formatted dos fat?
Yes.
I tried Dos fat, then I tried ExFat, then I tried formatting with the Camera.
It doesn't work! My card that works has been formatted ExFat with the Mac.
my serial number starts 213 and doesn't seem to work.
Would be better with screenrecordings of benchmarks before and after patch applied. Recording should show the exact card clearly. No way of validating otherwise.
Quote from: Danne on September 13, 2022, 07:04:23 AM
Would be better with screenrecordings of benchmarks before and after patch applied. Recording should show the exact card clearly. No way of validating otherwise.
I can't get the camera to "See" the writing (Too small, I need a magnifier to see clearly) , but could you look behind your cards?
Sandisk Extreme Pro 170 MB/s 128GB
Right below the serial number on the back of the card,
Working card says "Made in Malaysia"
Non-Working says "Made in China"
So try to benchmark your card to see maximum speed. Here´s few programs that might work. I have no experience in using them but feel free to have a look.
https://www.maketecheasier.com/check-sd-card-speed-capacity/
Published results are always better with screencaptures or recordings.
My sandisk 256Mb/s is made in china.
EOS M SD Card Speed Test With The latest Build: crop_rec_4k_mlv_snd_raw_only_2022Sep13.EOSM202.zip
https://bitbucket.org/Dannephoto/magic-lantern_jip_hop_git/downloads/
The cards have also been tested in a MacBook Pro 2010 (Built-In SD Card Reader), with Blackmagic Disk Speed Test:
https://itunes.apple.com/us/app/blackmagic-disk-speed-test/id425264550?mt=12
Note: All the cards tested here have been used a whole day, recording various clips to the point where it says "Card Full" in the EOS M, on at least 8 occasions each in the past 3 months,
with the previous builds crop_rec_4k_mlv_snd_raw_only_2022Jul31.EOSM202 and crop_rec_4k_mlv_snd_raw_only_2022May29.EOSM202,
@192 MHz. Cards worked as expected.
For the Test, cards have been formatted in camera with Low-Level Format enabled (ExFat).
Camera: EOS-M
Short Version (Write Speeds, EOS M Global Draw On):
Sandisk Extreme Pro 170 MB/s, 128GB (Made in China, Serial 221xxx)
Mac Test: 70.4 MB/s
@192 MHz: 78.9 MB/s
@240 Mhz: 20.9 MB/s
Sandisk Extreme Pro 170 MB/s, 128GB (Made in Malaysia, Serial 213xxx)
Mac Test: 70.0 MB/s
@192 MHz: 78.7 MB/s
@240 Mhz: 94.4MB/s
Sandisk Extreme Micro SD, 256GB (Made in China, Serial 14 7xxx)
Mac Test: 70.3 MB/s
@192 MHz: 76.8 MB/s
@240 Mhz: 20.8 MB/s
Details:
Cards Tested:
(https://i.ibb.co/9Tkdk6N/Cards-Used.jpg) (https://ibb.co/k8sPsjx)
Sandisk Extreme Pro 170-128MB Mac Speed Test (ML-1, Made In China)
(https://i.ibb.co/88zfjdv/BMD-Sandisk-Extreme-Plus170-128-MB-China.png) (https://ibb.co/9Yw1qVK)
Sandisk Extreme Pro 170-128MB @192MHz (ML-1, Made In China)
(https://i.ibb.co/cvsz8qh/bench-Sandisk-Ex-Pro170-128-MB-SD-China-192-MHz-GDOff.jpg) (https://ibb.co/7z07pht)
(https://i.ibb.co/ynJL8jp/bench-Sandisk-Ex-Pro170-128-MB-SD-China-192-MHz.jpg) (https://ibb.co/WW1ScJ0)
Sandisk Extreme Pro 170-128MB @240MHz (ML-1, Made In China)
(https://i.ibb.co/0FsGBJz/bench-Sandisk-Ex-Pro170-128-MB-SD-China-240-MHz-GDOn.jpg) (https://ibb.co/yY4Qhsx)
Sandisk Extreme Pro 170-128MB Mac Speed Test (ML-2, Made In Malaysia)
(https://i.ibb.co/dQ2sXcD/BMD-Sandisk-Extreme-Plus170-128-MB-Malaysia.png) (https://ibb.co/LCtDBP1)
Sandisk Extreme Pro 170-128MB @192MHz (ML-2, Made In Malaysia)
(https://i.ibb.co/WDvb27H/bench-Sandisk-Ex-Pro170-128-MB-SD-Malaysia-192-MHz.jpg) (https://ibb.co/M8kYCKg)
Sandisk Extreme Pro 170-128MB @240MHz (ML-2, Made In Malaysia)
(https://i.ibb.co/X2WxY1T/bench-Sandisk-Ex-Pro170-128-MB-SD-Malaysia-240-MHz.jpg) (https://ibb.co/Bzf2nbR)
Sandisk Extreme 256MB Micro SD, Mac Speed Test (ML-3, Made In China)
(https://i.ibb.co/5v7JqDn/BMD-Sandisk-Extreme-256-MB-China.png) (https://ibb.co/mtxPQsX)
Sandisk Extreme 256MB Micro SD, @192MHz (ML-3, Made In China)
(https://i.ibb.co/fN58gyg/bench-Sandisk-Extreme-256-MB-m-SD-China-192-MHz.jpg) (https://ibb.co/s1G5fNf)
Sandisk Extreme 256MB Micro SD, @240MHz (ML-3, Made In China)
(https://i.ibb.co/2kkQs6J/bench-Sandisk-Extreme-256-MB-m-SD-China-240-MHz.jpg) (https://ibb.co/Jss4ydZ)
Thanks a lot for a very good test 👍.
Should test the shit out of that china card :P.
My two Sandisk Extreme PRO 170 MB/s SD cards are made in china, and they work on 100D with new 240 MHz.
Edit: more likely gabriielangels' Cards are not fake SD cards.
No performance gain with 64GB Sandisk Pro Extreme 200MB/s Made in China. Just as another 170MB/s user https://www.magiclantern.fm/forum/index.php?topic=25781.msg240289#msg240289 (https://www.magiclantern.fm/forum/index.php?topic=25781.msg240289#msg240289) posted, 240MHz gives 20 MB/s and 190MHz gives 60.5 Mb/s actual recording speed, same as previous build.
Cards not working might work with trial and error modifying small increments in 240Mhz patch. "Unfortunately" I don´t have one of these cards myself to play with.
Quote from: Danne on September 12, 2022, 02:07:34 PM
I tested on Extreme PRO 170MB/s V30 256gb card and working(eosm).
The same on Sandisk Extreme PRO 170MB/s V30 64gb card working (eosm). Made in China.
@240MHz Write - 92.1 MB/s
@192MHz Write - 77.5 MB/s
@160MHz Write - 68.9 MB/s
Quote from: Danne on September 14, 2022, 12:22:00 PM
Cards not working might work with trial and error modifying small increments in 240Mhz patch. "Unfortunately" I don´t have one of these cards myself to play with.
If you or any dev here is willing to work on solving the mystery, I don't mind sending you my non-working card for experimentation. You could send it back if it survives the treatment :)
As being able to record 3K 1:1 continuous is serious business... If a few of us are willing to do the same, it would give a capable person enough reference points to maybe find a way.
Bilal is the man here. I think you could do tests otherwise by simply compile and try out different possibilites.
I don't know how to compile. It would be too much of a time investment to learn all of that now (I'd rather spend my spare time using the new and improved 3K mode.)
But if there is a simple way for me to clone your repository and only have to worry about changing specific values in a specific file or two,
I am willing to try that... Or just send my card to Bilal :)
p.s. Danne's build has the 240 MHz setting in the movie tab (As opposed to only in the debug tab), which is a very useful spot for the setting,
as we may sometimes need to switch to 192 MHz to allow the camera to cool down while still using it, if needed.
Quote from: gabriielangel on September 14, 2022, 05:36:35 PM
I am willing to try that... Or just send my card to Bilal :)
Which may be way more complicated than you think. Plus Bilal doesn't own an EOS M.
Brandnew Samsung Pro Plus not getting past 20. I'm sending it back to the store.
Trusty old SanDisk Extreme Pro 170 U3 is working on 240hz
Benchmarked with Danne's build of sept 12th on EOS M
Thanks a bunch guys. Keep up the good work
For users who has 170 MB/s SD card which didn't work with new 240 MHz, could you try this version:
new_sd_uhs_SDR104_patch.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/new_sd_uhs_SDR104_patch.zip)
Change in these lines (source code included in .zip file too):
from:
if (sd_overclock <= 2)
{
patch_hook_function(sd_set_function, MEM(sd_set_function), sd_set_function_log, "SDR104");
SD_ReConfiguration();
}
to just:
patch_hook_function(sd_set_function, MEM(sd_set_function), sd_set_function_log, "SDR104");
SD_ReConfiguration();
The only difference now is SDR104 patch would be applied for 240 MHz, in original new sd_uhs version (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128) SDR104 won't be applied for 240 MHz preset because my Sandisk Extreme PRO 170 MB/s card becomes not stable (drop to 21 MB/s) with SDR104 patch on 100D.
It could be that some of 170 MB/s SD cards need SDR104 patch (see here (https://www.magiclantern.fm/forum/index.php?topic=26511.msg239402#msg239402)and here (https://www.magiclantern.fm/forum/index.php?topic=25781.msg240315#msg240315), SDR104 patch was required for 160 MHz and 192 MHz preset there).
Feedback please!
If it didn't work, I am assuming that you either need to play with GPIO registers with SDR104 patch enabled or without SDR104 patch for 240 MHz preset.
Will add some info soon about GPIO registers.
Edit: Nope, it doesn't work.
didn't work on mine 170 256gb
Quote from: theBilalFakhouri on September 14, 2022, 08:16:16 PM
For users who has 170 MB/s SD card which didn't work with new 240 MHz, could you try this version:
new_sd_uhs_SDR104_patch.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/new_sd_uhs_SDR104_patch.zip)
Feedback please!
If it didn't work, I am assuming that you either need to play with GPIO registers with SDR104 patch enabled or without SDR104 patch for 240 MHz preset.
Will add some info soon about GPIO registers.
Doesn't work @240 MHz here (But Works @192 MHz) Sandisk Extreme Pro 170, 128GB on EOS M
Mine sandisk 170mbs 256g doesn't work on Eos M but works on 5DIII with the new patch.... and it works with the previous patch on Eos M but not on 5D mark iii
Thanks for testing
EOS M / 100D users:
Yet another new 240 MHz preset to test:
-It works better at high temps using my Sandisk 170 MB/s and 100D, it didn't drop to 21 MB/s after 5 minuets of recording :D
-SDR104 patch which required to enable high OC for some cards now works with the newest 240 MHz preset, and it's stable
I am expecting that 170 MB/s SD card which didn't work previously using the original new 240 MHz preset (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128) to work with the newest 240 MHz on EOS M / 100D (hopefully)
Download: newest_sd_uhs_SDR104_patch.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/newest_sd_uhs_SDR104_patch.zip)
-Side effect I noticed (at least using my card and 100D):
● It happens after SD controller/card become too hot (I mean it) write speed performance will drop from 90 MB/s to 72 MB/s in benchmarks (Play mode), or from ~80 MB/s to ~62 MB/s for RAW video recording.
● After a camera restart SD card will restore full write speed (90 MB/s in Play mode, ~80 MB/s in RAW video recording) and you should be able to record more minuets until it drop again to 72 MB/s in Play mode or 62 MB/s while RAW video recording.
● I am not 100% sure if the drop happens because of high temps, I will need to make more tests and a test inside the fridge (at cool temps). Will do that later.
Note: use any of new 240 MHz presets at your own risk, I am not responsible for any type of damage!
For me I will be using it until bad things happen.
-The Method:
I have used an overclocked 240 MHz preset which could be achieved by keeping 0xC0400600 = 0x3 and by reducing 0xC0400610 to 0x1 with other registers adjustments, full preset:
static uint32_t uhs_regs[] = { 0xC0400600, 0xC0400604,/*C0400608, C040060C*/0xC0400610, 0xC0400614, 0xC0400618, 0xC0400624, 0xC0400628, 0xC040061C, 0xC0400620 }; /* register addresses */
static uint32_t sdr_240MHz2[] = { 0x3, 0x3, 0x1, 0x1D000001, 0x0, 0x100, 0x100, 0x100, 0x1 }; /* Works better on 100D, also SDR104 is stable with this preset (for Write operations) */
I am using 240MHz2 preset only for write operations (WriteClock) beside keeping 192 MHz for reads.
static void WriteClock(uint32_t* regs, uint32_t* stack, uint32_t pc)
{
memcpy(uhs_vals, sdr_240MHz2, sizeof(uhs_vals));
}
Removed this part of code for EOS M / 100D too:
/* SDR104 patch casues instability for 240 MHz preset */
if (sd_overclock <= 2)
SDR104 patch will be applied for all overclocking presets.
Source code is included in zip file.
Feedback please!
Results from Walter using EOS M with the newest 240 MHz (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240328;topicseen#msg240328) preset:
These SD cards now works @240MHz on EOS M!
-SanDisk Extreme R190/W130 256 GB
-SanDisk Extreme PRO R200/W140 256 GB
-Samsung EVO Select 256 GB MB-ME256KA
Benchmark using SanDisk Extreme R190/W130 256 GB using newest 240 MHz on EOS M:
(https://i.ibb.co/gMMJGmG/bench8.png) (https://ibb.co/ynnqDdD)
Hell Yeah :D
-Not tested yet with RAW video recording
-That wasn't possible with original new sd_uhs (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128) , previous results (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240220#msg240220).
-Walter said: It could be a breakthrough enabling cheaper cards for highest res with EOS M.
-To be tested by you!
More SD cards might work on EOS M @ 240 MHz ;) (oh also on 100D)
First report (https://discord.com/channels/671072748985909258/671072748985909264/1019951947018682428) on Discord from @AceCom:
Previously his Sandisk Extreme PRO 170 MB/s SD card didn't work with original new sd_uhs (//http://) on EOS M, by using the newest sd_uhs (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240328#msg240328)
it works now:
QuoteWrite speed is at 92.7 Average on the new preset and 83.3 constant read speed @240MHz
Another hell yeah :D
Hehe 👌💪
edit
To enter play mode press play after starting benchmark run. Your numbers look like liveview modes.
ye, I didnt know about that difference. in playmode its 87.9MB/s and 92.3MB/s. so its ok now!
Extreme pro 512gb 170MB/s
EOS M users
reports with the
newest sd_uhs and 240 MHz:
@cedricp:
Quote from: cedricp on September 15, 2022, 02:47:59 PM
In play mode the 128Gb Extreme pro 170MB/s reports a fabulous 95Mb/s
@cannibalferox
Quote from: cannibalferox on September 15, 2022, 02:57:02 PM
By the way I wanted to mention while I did a couple of minutes test recordinings as in the fourth picture I started to smell something :D Which was the hot sdcard so I can definetly confirm higher temperatures.
Towards the Liveview/Play Mode I have now only repeated it with the last version plus patch I am running now:
Writespeed1 95.3MB/s
Readspeed1 85.6MB/s
Writespeed2 94.7MB/s
Readspeed2 85.6MB/s
@Possie
Quote from: Possie on September 15, 2022, 03:47:45 PM
Holy cow ! Redid the benchmarks.
Samsung hitting 99 write speed - high 80's read. Insane !
SanDisk 92/85 write/read (most consistent performer)
Lexar does only high read speeds 80's - low write 50
After low-level format of the card it's reversed -barely hitting 60 write. It's a wonky card I use for my M2.
That play button trick worked a charm
@gabriielangel
Quote from: gabriielangel on September 15, 2022, 03:50:09 PM
... even my Sandisk Extreme 256GB (Red and Gold) works @240MHz!!!!!
(https://i.ibb.co/SNb9KGL/bench10-Sandisk-Extreme-256.jpg) (https://ibb.co/2qxfjHb)
The Sandisk Extreme Pro 170 MHz 128GB which did not work a few days ago @240 also works now!
Ah, did we reach that day? :D
Quote from: theBilalFakhouri on September 12, 2022, 01:37:18 PM
.... I hope someday we will reach perfect 240 MHz on EOS M / 100D.
A new report from Walter using
newest sd_uhs and 240 MHz on
EOS M:
-Card used: Samsung PRO Plus 256 GB, R160/W120 MB-SD256KA
Quote from: Walter Schulz on September 15, 2022, 06:25:27 PM
And another one stable @240 MHz:
Samsung PRO Plus 256 GB, R160/W120 MB-SD256KA
(https://abload.de/img/bench36ydcuy.png)
Seems to have same performance as 128 GB variety. Lower capacities should perfom not as well according to Samsung specs.
Slightly off-topic and shape of things to come. Stable recording? Nope, just benchmark!
Running with 280 MHz now:
(https://abload.de/img/bench15vze0d.png)
Hello there
What means 280MHz?
New sd hack?
240MHz hack most high speed can not help 5D mark iii 14bit 3k 3.3k 3.5k 4k,
just Benchmark show high speed,high speed just used in 1920 1080 and full 5760.
100d 3k 14bit also can not use high speed more.
For 5DIII it could be used replacing CF card in some cases but biggest win is for 100D/EOSM.
Samsung Pro Plus 128GB. With the original hack, the card would be very unreliable. I managed to pull 240Mhz speed only for a few seconds before it reverted to 20MB/s. 192Mhz was also unreliable. With the 15th of September build, however, it seems the card is very stable at 240MHz. I can shoot for minutes non stop, even in 2.8k!! This was unthinkable just a few months back! Needless to say I'm excited...(https://ibb.co/2WvJ2T1)
Hm, I do believe the code for 192Mhz is the same from september 15th. Maybe I missed something. Anyway. I´ll wait for a few more reports.
What camera by the way?
Edit: sorry. Misread. Code seems good.
Quote from: Danne on September 16, 2022, 08:03:39 AM
Hm, I do believe the code for 192Mhz is the same from september 15th. Maybe I missed something. Anyway. I´ll wait for a few more reports.
What camera by the way?
Yes, in fact, before these new developments, I was stuck with 160MHz for the samsung card to work (192 didn't work)
I'm on the M. getting 93MBs write speed on benchmarking.
Quote from: Danne on September 16, 2022, 08:03:39 AM
Hm, I do believe the code for 192Mhz is the same from september 15th. Maybe I missed something. Anyway. I´ll wait for a few more reports.
Your original sd_uhs lacked SDR104 patch which is seems to be required for some SD cards at high OC.
@Ernani
Thanks for reporting!
Cool. I misread before. Bilal did a good job finding this patch.
An impressive report (https://www.facebook.com/groups/mlvraw/posts/1260492164775064/?comment_id=1260864684737812)from EOS M FB group:
Card used: LEXAR UHS-II V90 @ 240 MHz on EOS M:
(https://i.ibb.co/yVC7cJL/307006505-10160083455853563-6688025535724854510-n.jpg) (https://ibb.co/d7vxwyn)
Quote from: Danne on September 16, 2022, 09:06:16 AM
Bilal did a good job finding this patch.
Actually SDR104 patch is totally a1ex work 8)
I just wasn't aware it was required.
Quote from: Walter Schulz on September 16, 2022, 03:25:27 AM
..
Running with 280 MHz now:
(https://abload.de/img/bench15vze0d.png)
Toasty :)
Quote from: SebastianC on September 16, 2022, 05:37:40 AM
What means 280MHz?
New sd hack?
Yes, currently trying to make it stable in LiveView (for RAW video recording), no idea if it would be stable at some point, because this actually exceeds official UHS-I limits on paper.
Quote from: Danne on September 16, 2022, 05:38:53 AM
For 5DIII it could be used replacing CF card in some cases but biggest win is for 100D/EOSM.
True for 5D3.
Also if we got 280 MHz working that would mean all DIGIC 5 models with SD interface would benefit, not only 100D / EOS M. Above benchmark was done using 650D.
Quote from: theBilalFakhouri on September 16, 2022, 09:39:59 AM
Toasty :)
Also if we got 280 MHz working that would mean all DIGIC 5 models with SD interface would benefit, not only 100D / EOS M. Above benchmark was done using 650D.
also if we get 280hz we need cooler system for the M. :P
I think other DIGIC 5 models can manage heat better
We should do some merch: insulated heat resistant gloves with ML logo?
Hm... would like to join the party, but I've no idea how you all get those values. For me it isn't working on my M with SanDisk Extreme Pro 95MB/s 64GB.
160MHz: ~68(W)..75MB/s(R)
192MHz: 20MB/s (R/W)
240MHz: 20MB/s (R/W)
With old build I got 75MB/s (W) and 86MB/s (R).
@masc Welcome to the party!
I know exactly what is causing this, I have SanDisk Extreme Pro 95MB/s 32 GB SD card which doesn't work at high OC (192 MHz and 240 MHz) when applying SDR104 patch, only 160 MHz works with SDR104.
I made some benchmarks in the past in PC using many card readers and it benchmark at ~45 MB/s which mean more likely PC card readers is using SDR50 mode for that card or SDR104 mode but at low frequencies (below 100 MHz).
However, by using SDR50 mode on camera (disabling SDR104 patch) and applying high OC like 192 MHz and 240 MHz, my SanDisk Extreme Pro 95MB/s 32 GB *works fine.
*(not stable at 240 MHz though, drops after some time to 21 MB/s, this issue is not related to the new sd_uhs).
That's a little weird, according to SD Association SDR104 mode should be used for frequencies higher than 100 MHz (~50 MB/s).
SanDisk Extreme Pro 95MB/s 32 GB is weird on its own ways (at least for the one I have) . .
New Universal SD Overclocking module version for DIGIC 5 models:
Universal SD Overclocking module - DIGIC 5.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/Universal_SD_Overclocking_module_-_DIGIC_5.zip)
-Added Access Mode toggle setting:
You can select SDR50 or SDR104, SDR104 is selected by default which should work on all recent fast SD cards.
Only try SDR50 when SDR104 fails. Like in SanDisk Extreme Pro 95MB/s case.
(https://i.ibb.co/Dw6nPd8/SDR104.png)
(https://i.ibb.co/gdRdBQv/SDR50.png)
You need to restart the camera after changing this setting.
You can find this setting in SD Overclocking submenu.
-Also added EOS M2 1.0.3 support, to be tested.
@masc
Your SanDisk Extreme Pro 95MB/s 64GB might be stable at 240 MHz (might not drop to 21 MB/s after some time like my SanDisk Extreme Pro 95MB/s 32GB). Give it a try!
Quote from: theBilalFakhouri on September 17, 2022, 12:56:50 AMNew Universal SD Overclocking module version for DIGIC 5 models:
Wait, what? 'Universal' as in 'will work with other people's builds on other DIGIC 5 cameras, specifically 70D'?
@elenhil
I mean by "Universal":
-It contain all of the good stuff from old and new sd_uhs
-It support all DIGIC 5 models
The module will work under crop_rec_4k branch
70D has custom crop_rec_4k build (https://www.magiclantern.fm/forum/index.php?topic=25786.msg213074#msg213074), you can try the module using that build, report back your results!
Sorry if the "Universal" word was a little confusing.
@theBilalFakhouri: yay... paaaartey... thank you! That's it. Seems to work fine with SDR50.
(https://i.ibb.co/YhN4y01/bench0.png)
It feels like there are speed drops sometimes. You also see this in the 2nd write speed value: numbers are counted with constant speed, until it stops for a second or so, and then counts again fast. Same seems to happen when recording: I get green icon (e.g. for 14bit 1440x1836) and then I get a stop... whyever. MLVApp told until the stop, I recorded at 66MB/s.
Edit: low level format seems to help.
It is anecdotal "evidence" though but I got my misbehaving card cured after low-level format in cam.
Thanks Walter. Same here. Looks better now.
@masc
Cool, nice result :)
And yeah, whenever you see drops in benchmarks between two write speed passes or during RAW video recording, perform a low level format.
Quote from: masc on September 17, 2022, 10:55:32 AM
@theBilalFakhouri: yay... paaaartey... thank you! That's it. Seems to work fine with SDR50.
(https://i.ibb.co/YhN4y01/bench%3Cbr%20/%3E%3Cbr%20/%3EIt%20feels%20like%20there%20are%20speed%20drops%20sometimes.%20You%20also%20see%20this%20in%20the%202nd%20write%20speed%20value:%20numbers%20are%20counted%20with%20constant%20speed,%20until%20it%20stops%20for%20a%20second%20or%20so,%20and%20then%20counts%20again%20fast.%20Same%20seems%20to%20happen%20when%20recording:%20I%20get%20green%20icon%20(e.g.%20for%2014bit%201440x1836)%20and%20then%20I%20get%20a%20stop...%20whyever.%20MLVApp%20told%20until%20the%20stop,%20I%20recorded%20at%2066MB/s.%3Cbr%20/%3E%3Cbr%20/%3EEdit:%20low%20level%20format%20seems%20to%20help.%3Cbr%20/%3E%5B/quote%5D%3Cbr%20/%3E0.png)
Bilal again. Wizard. Will add his workaround in my build as well.
After LowLevel format, just for documentation: SanDisk Extreme Pro 95MB/s 64GB
(https://i.ibb.co/GFyPhQm/bench0.jpg)
I now can record 14bit 1440x1836 over 5min and more... in average >60MB/s, testfile was ~19GB after 5min.
Another: 14bit 2800x1190, I stopped after 2min... in average 78MB/s, testfile was ~10GB.
Great work Bilal!
I wish we had a 5D iii subforum for this topic.
the overclock option used to be placed in raw menu page and moved some were else, wasnt it ?
i think i found it in one of the pages it seens to work as well :), i am getting 70mb on sd.
I use to get notification letting me know overclocking is done, but I didnt see that coming after inital msg telling me its starting th oc process. is it still on ?
so, if i did get this right then then:
i was continiusly shoiting 3.5 14 bit lossless 2:20
with dual iso and liveview on
and not just that,
I hade a green indicator all along !!
this is out of this world !! thanks
Sent from my SM-N975F using Tapatalk
Thanks @masc, glad it worked for you!
Edit: Could you confirm if it didn't drop to 21 MB/s during your tests with SanDisk Extreme Pro 95MB/s 64GB at 240 MHz?
Quote from: Danne on September 17, 2022, 11:21:05 AM
Bilal again. Wizard. Will add his workaround in my build as well.
Thanks!
Quote from: koopg on September 17, 2022, 11:49:42 AM
I wish we had a 5D iii subforum for this topic.
Why will we need that?
Quote from: koopg on September 17, 2022, 11:49:42 AM
the overclock option used to be placed in raw menu page and moved some were else, wasnt it ?
In Danne builds he moved it a long time to the Movie tab, original place is Debug tab which I am using.
Quote from: koopg on September 17, 2022, 11:49:42 AM
i think i found it in one of the pages it seens to work as well :), i am getting 70mb on sd.
Cool, what is your SD card and which overclocking preset you have used?
Quote from: koopg on September 17, 2022, 11:49:42 AM
I use to get notification letting me know overclocking is done, but I didnt see that coming after inital msg telling me its starting th oc process. is it still on ?
When "SD Overclocking..." disappears that mean it's done and you are ready to go. I made it my version like that for 5D3.
And you are welcome, thanks for reporting.
Quote from: theBilalFakhouri on September 17, 2022, 03:03:20 PM
Thanks @masc, glad it worked for you!
Edit: Could you confirm if it didn't drop to 21 MB/s during your tests with SanDisk Extreme Pro 95MB/s 64GB at 240 MHz?
Can confirm (until now). Still no drop to 21MB/s for this card at 240MHz. I recorded a hand full of longer clips at high data rate...
Cool, I think Levas have also same as your card SanDisk Extreme Pro 95MB/s 64GB or maybe with a higher capacity.
My SanDisk Extreme Pro 95MB/s is only 32 GB which doesn't work very well at 240 MHz.
yes no drop for over a min
at 24 fps(https://uploads.tapatalk-cdn.com/20220917/ed08ab036be1e2ce231e8d6b1c2c7c7d.jpg)
Sent from my SM-N975F using Tapatalk
Is it possible start recdording to CF card only and continue by overlocked SD card (after filling CF card) without interruption (stop/start record)?
I just recorded without 14bit lossless.
First magic lantern settings:
Presets > OFF
1920x1290
Movie> RAW videw >. Data format > 14-bit lossless\14-bit.
With Sound
Basically I completely FrozenLV. So there was absolutely no preview.
Anti global draw {ON}
Movie>Shoot>Focus>Display
Anti Canon GUI {ON}
Second magic lantern settings:
Danne's 5K I set to 12bit.
Presets > anamorphic
Movie> RAW videw >. Data format > 14-bit lossless\12-bit.
Anti global draw {ON}
Movie>Shoot>Focus>Display
Anti Canon GUI {ON}
So there was absolutely no preview.
In the normal Canon menu I completely disabled sound recording. And of course. Enable sound {OFF} in magic lantern.
Quote from: domasa on September 18, 2022, 09:41:26 PM
Is it possible start recdording to CF card only and continue by overlocked SD card (after filling CF card) without interruption (stop/start record)?
I think it should be possible, but I don't know how to do it.
So, I've been testing the hell out of my Samsung Pro plus 128gb micro. I get constant recording at around 70MB/s. Green pretty much all the time. On ML benchmark it goes above 90MBs every time, usually around 94MBs. No matter how much I tried, I experienced no drops to 20MBs like I did before the 15th build. Now 240mhz seems very stable even after long clips, no significant overheating either.
People, I think this is it. This is the build. I don't remember feeling this excited since Danne pulled MCM rewire! Good job, Bilal!
eosm user
Side note: I wonder if other than 14, 12 and 10 bit, it would be possible to choose 8bit... in cases where the end product would be B/W and color depth is not paramount. I know this is off topic, just a curiosity.
Yes, 8bit possible but there will be tearing regardless if color or b&w.
Quote from: Danne on September 19, 2022, 05:41:56 PM
Yes, 8bit possible but there will be tearing regardless if color or b&w.
:o Really now? I wonder what the difference in size would be from 10bit...
2/10 = 20 percent.
you made it! ;)
Version: Sept19.EOSM
Sandisk Extreme Pro 64GB 200MB/s
Benchmark: 85/85/85/85 MB/s
Actual Recording Speed: 3k 10-bit 2.35:1, E4.3, approx: 74.5MB/s on the yellow continuous, except brightest exposures, momentary peaks up to 77.2 MB/s
@koopg @Bruno Italiano @Ernani @wyup
Thanks for the tests. Glad it worked for you :)
Another
new sd_uhs version can be found here:
SD Overclocking - DIGIC 5 only (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228)
Quote from: theBilalFakhouri on September 21, 2022, 02:20:39 PM
- Contain latest Universal sd_uhs code
- Added show CID info option
- Little fixes and modifications
Check it out (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228)
- Test "Show CID info" on all models (on 5D3 / 100D / 700D it seem to work fine)
- The module should work fine, report back if there is regression
- Test the module on EOS M2 1.0.3
Quote from: theBilalFakhouri on September 21, 2022, 07:19:48 PM
- Added show CID info option
Very clever addition to help us identify differences... Thanks!
Quote from: theBilalFakhouri on September 21, 2022, 07:19:48 PM
Another new sd_uhs version can be found here:
off to testing...
Thanks Bilal.
Hey all. I know this is just testing here and I'm new(and still learning) but I want to try it too.
Can someone give me the download link(s) needed for this?
Also I don't really know how ML works completely yet but once this is decided stable enough will someone make a fully combined build download for this?
Thanks
Get build from here:
https://www.magiclantern.fm/forum/index.php?topic=25784.0
Get sd_uhs.mo from first post of this thread
Replace sd_uhs.mo.
Thanks a lot. sorry about the slow reply
Another SD card works with the new sd_uhs:
Quote from: Papa-Yeti on September 16, 2022, 01:07:35 AM
..
SD Card: Lexar Professional 256GB 1066x SDXC UHS-I (Silver Series)
Read:Write (OEM claimed): 160MB/s:120MB/s
(https://i.ibb.co/1KcsTBK/lexar-256-GB-1066x-UHS-1.jpg) (https://ibb.co/Y8gDhJ8)
..
A new card tested today on EOS M:
Sandisk Extreme Pro 200MB/s-256GB
PNM: SR256
OID: 2022/06
Rated R/W: 200/140 MB/s
Tested with Danne's Latest Build Sept29-2022
(https://i.ibb.co/M2R8C0V/Sandisk-Extreme200-MBs-256-G-New.jpg) (https://ibb.co/qyR0rQs)
Tested with Latest Module on Bilal's post.
(https://i.ibb.co/gFJCt1n/Sandisk-Extreme200-MBs-256-G-Stock.jpg) (https://ibb.co/5xLVsD7)
Records on par with the earlier Sandisk Extreme Pro Cards.
Thank you again to everyone involved!
Quote from: Walter Schulz on September 16, 2022, 03:25:27 AM
Slightly off-topic and shape of things to come. Stable recording? Nope, just benchmark!
Running with 280 MHz now:
(https://abload.de/img/bench15vze0d.png)
Is this build available to test for EOS M? I just received my 140MB/s Rated Write card. Might as well test it while I'm doing the resolution tests.
Quote from: gabriielangel on October 01, 2022, 02:33:08 AM
Is this build available to test for EOS M? I just received my 140MB/s Rated Write card. Might as well test it while I'm doing the resolution tests.
Currently it's not available in public. It still doesn't work on EOS M / 100D / 5D3.
It works on 650D / 700D in Play mode only, in LiveView it drops to 21 MB/s.
Currently I am not working on it. 280 MHz shared benchmark was more like a proof of concept.
So maybe I'm reading this wrong, as I'm a noob, but you it's not working on the eos m?
I put the module in danne's build and I am able to shoot 3k and 4K modes 1minute for the later longer for the previous. Only thing is that its frame rate drops to around 15-20. I'm going to check my settings again later. Before I got seconds. (I did turn over clocking on).
If I'm wrong, be gentle. Haha
With new sd_uhs.mo 240 MHz is stable for all W90 (or higher) UHS-I cards. New module is available for 5D3/EOS M/100D. See thread title.
Benchmark quoted by gabriielangel is unstable 280 MHz test run which can do just benchmarks ATM and won't work at 280 MHz in EOS M.
You should be able to get your actual fps number by looking into MLVapp. It will tell you frames taken and duration and fps numbers.
Quote from: ChiefZer0 on October 02, 2022, 07:29:45 AM
So maybe I'm reading this wrong, as I'm a noob, but you it's not working on the eos m?
I put the module in danne's build and I am able to shoot 3k and 4K modes 1minute for the later longer for the previous. Only thing is that its frame rate drops to around 15-20. I'm going to check my settings again later. Before I got seconds. (I did turn over clocking on).
If I'm wrong, be gentle. Haha
3k and 4k comes with reduced frame rates. I think 3k 2.39:1 is 24 fps if I remember correctly.
Quote from: Walter Schulz on October 02, 2022, 08:47:20 AM
With new sd_uhs.mo 240 MHz is stable for all W90 (or higher) UHS-I cards. New module is available for 5D3/EOS M/100D. See thread title.
Benchmark quoted by gabriielangel is unstable 280 MHz test run which can do just benchmarks ATM and won't work at 280 MHz in EOS M.
You should be able to get your actual fps number by looking into MLVapp. It will tell you frames taken and duration and fps numbers.
Oh ok. I missed the part about them talking about the 280 MHz and assumed it was 240. My bad.
I understand that about MLV but I can't look at the app for a little just the video.
Quote from: Danne on October 02, 2022, 09:05:41 AM
3k and 4k comes with reduced frame rates. I think 3k 2.39:1 is 24 fps if I remember correctly.
Oh I see thanks. I'll take a look
As of the cards falling back to low speed. If the temperature is really the cause, maybe this hack would work: a micro SD adapter whose sides are partially replaced with metal, the micro SD card glued between the metal parts with a thermal glue.
Quote from: theBilalFakhouri on September 07, 2022, 05:26:20 PM
Edit 20/9/2022:
Latest sd_uhs which works perfectly on 5D3 / EOS M / 100D and other DIGIC 5 models:
where is the source?
dpjpandone@MSI:/mnt/d/DEVELOPMENT/Crop_Rec4kMAIN/modules/sd_uhs$ make
make: *** No targets specified and no makefile found. Stop.only .c file and .mo was in the zip
sd_uhs.c is the source code, you will need other files to compile it "Makefile" and probably "README" too, example:
https://foss.heptapod.net/magic-lantern/magic-lantern/-/tree/branch/sd_uhs/modules/sd_uhs
You can get them from the link or create them.
Or check the latest sd_uhs version (which include show CID info) here:
Overclocking - DIGIC 5 only (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228)
This:
Quote from: theBilalFakhouri on February 12, 2021, 10:32:15 PM
../ Source code (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/sd_uhs.zip) / ...
This include "Makefile" and updated "README".
Quote from: theBilalFakhouri on January 03, 2023, 11:15:19 AM
sd_uhs.c is the source code, you will need other files to compile it "Makefile" and probably "README" too, example:
https://foss.heptapod.net/magic-lantern/magic-lantern/-/tree/branch/sd_uhs/modules/sd_uhs
You can get them from the link or create them.
Or check the latest sd_uhs version (which include show CID info) here:
Overclocking - DIGIC 5 only (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228)
This:
This include "Makefile" and updated "README".
works! thank you!
Excellent work man! 240mhz obtained 80.8MB/s write speed on 5D3 (play mode) with sandisk Extreme Pro 170MB/s which totally negates the need for CF cards! (for me) If I don't need this much speed (I typically just shoot 1080p 14-bit lossless @ less than 50MB/s) do you think reducing the clock speed to 160mhz would increase the longevity of the hardware? or is it simply there for backwards compatibility with older cards?
There is one little quirk I've managed to reproduce. "Free memory" in debug menu throws ERR70 every time
Quote from: anto on September 12, 2022, 08:31:10 PM
My 512 170MB/s serial is 212
btw found that formatting in exfat it reaches 62 MB/s with 192 Hz :) (https://reactoonz.org/)
seems to be mate
looks it helps in my case
appreciated!
Quote from: theBilalFakhouri on September 07, 2022, 05:46:28 PM
Details:
1.New GPIO registers:
Explaining will be added soon!
Just added the info for
GPIO registers for documenting, check it here (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128):
Quote from: theBilalFakhouri on September 07, 2022, 05:46:28 PM
1.New GPIO registers:
Explaining will be added soon!
(Edit: Explaining was added in 9-1-2023)
These registers seem to be related to SD controller registers?
......
Quote from: theBilalFakhouri on January 09, 2023, 09:42:36 PM
Just added the info for GPIO registers for documenting, check it here (https://www.magiclantern.fm/forum/index.php?topic=26634.msg240128#msg240128):
Very interesting, I'm amazed how you figured all this out of nowhere! 😯
i'm a little late to the 5d3 240mhz party, but here's my results!
in case the image doesn't work, it's 96 MB/S :)
[gifv]49p54rd[/gifv]
Quote from: iaburn on January 10, 2023, 06:58:06 AM
Very interesting, I'm amazed how you figured all this out of nowhere! 😯
Thanks!
Time + Patience + Log analysis + Experiments (a lot of them) + Anyone helped to get logs and run tests . . resulted in these findings :D
There are a lot of other amazing work have been done in many sections (like Lossless, RAW video, new ports, increasing RAW resolution, Real-Time preview stuff :P ... etc) by other devs, and many of them are even more complex than this.
Quote from: 70MM13 on January 10, 2023, 02:28:55 PM
i'm a little late to the 5d3 240mhz party, but here's my results!
in case the image doesn't work, it's 96 MB/S :)
Cool results :)
The image doesn't work, seems like the link is missing or incorrect.
Quote from: dpjpandone on January 08, 2023, 01:23:13 AM
Excellent work man! 240mhz obtained 80.8MB/s write speed on 5D3 ...
Thanks!
Quote from: dpjpandone on January 08, 2023, 01:23:13 AM
... do you think reducing the clock speed to 160mhz would increase the longevity of the hardware? or is it simply there for backwards compatibility with older cards?
Correct, some SD cards aren't fast enough and doesn't work with high frequencies like 192 MHz and 240 MHz. That's one reason why 160 MHz is there.
I don't know if lower clock speeds help with "increasing the longevity of the hardware".
Quote from: dpjpandone on January 08, 2023, 01:23:13 AM
There is one little quirk I've managed to reproduce. "Free memory" in debug menu throws ERR70 every time
That's not related to SD overclocking, but to RAW video. When RAW video is activated (mlv_lite) it allocate all available memory, and once you higlight (or maybe click?) on "Free memory", an ML function which analysis free memory would run and would conflict somehow with RAW video, because of RAW video allocated all memory. I had this problem before.
Quote from: theBilalFakhouri on January 11, 2023, 10:02:11 PM
That's not related to SD overclocking, but to RAW video. When RAW video is activated (mlv_lite) it allocate all available memory, and once you higlight (or maybe click?) on "Free memory", an ML function which analysis free memory would run and would conflict somehow with RAW video, because of RAW video allocated all memory. I had this problem before.
OK thank you for explaining this. I noticed the ML menu reports "not exactly clean" patching when the module is activated, I thought there was some correlation here but I forgot to test for the same behavior with the module deactivated. :-X
maybe we will have a new card to test?
https://www.anandtech.com/show/18809/samsung-updates-pro-plus-uhsi-memory-cards-with-improved-speeds
Sure, will be tested if coming with a good deal.
No high expectations, though.
2021 versions run fine and 10 percent higher benchmark numbers with proprietary cardreaders is nothing to write home about.
BTW: EVO Plus 256 GB, 2021 offered right now for 17 Euro = 0.66 Euro/GB.