Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Skinny

Pages: 1 2 3 [4] 5 6 ... 8
76
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 05:46:32 PM »
New test build for 550D:
ok here we go:
0xC0400008 value initially: 363110f
after taking a picture: 1363110f very briefly, and it immediately goes to 363110f

-From "Apply patch" submenu, keep 0xC0400004 as it is, change 0xC0400008 to 2 --> click on "Apply patch", write down 0xC0400008 value
the value is still 363110f,
benchmark shows the same default speeds,
and the value is still 363110f after that.


Yes, it's available on my 700D (even if it not mentioned in ROMs, there is preset which result in 25 MB/s).
Further more, even on 5D3 without overclocking there is a built in preset which result in 25MB/s write speed (that's outside UHS-I mode, without 1.8 Signaling too).

Also, 550D have 16/24/48 MHz built in presets and 16 MHz isn't multiple of 12 MHz.

Canon has configured clock speeds in a way, I am trying to understand Canon's way on DIGIC 4. ;)
ah, ok, I see now :) I thought it was just simple divider or something..

77
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 05:26:38 PM »
Sorry, but I'm unable to decypher your message.
Do you have a card labeled with V30 but not showing write rates above 30 MByte/s using a cardreader?
exactly, I mentioned it in previous post. it can only go to 21,9 read speed in camera and in cardreaders too. The same number.
I don't know what SDS50/DDR50 is, but I think cheap card readers just use 48 MHz..

Well guys I'm sorry if my messages are hard to decypher sometimes, I don't know why I write so. English is not my first language, but even when I speak in my native language people sometimes can't understand what I mean :) I'll try to express my thoughts more clearly.

I am trying to achieve *50 MHz* (25MB/s write speed). It should be possible according to SD Association :P .
is 50 available on other cameras? you mentioned:
Quote
In DIGIC 5 models there is a function which can toggle between the built in presets (24/48/96 MHz)
but 50? I mean, it is not multiple of 12... maybe 50 can not be generated from existing clocks. who knows..

UHS-I mode requires 1.8 Signaling (voltage switch), not presented in DIGIC 4 ROMs, this has to be implemented in a ML function (we are not doing this right now).
Is this required for SD card itself? I can make an adapter in hardware if it will be too hard to do in ML. Just for tests.

78
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 04:27:29 PM »
Ah, I see, good to know. Then maybe the card is somewhat capable but only in UHS-I, because 15/16 mb write is sloooow... Thank you :)

79
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 04:15:01 PM »
@theBilalFakhouri well.... seems like my card is slow. In the card reader crystal disk mark shows the same numbers as in the camera, 21,9 for read maximum.

I found it on the internet, it is adata premier pro with green line. It is the same as this one:
https://www.memoryc.com/26902-32gb-adata-premier-pro-microsdhc-cl10-uhs-i-u3-v30-a2-memory-card-with-sd-adapter.html

but older, it is A1 not A2 class and SDHC and not XC, but UHS-I U3 and V30 too, so it should be at least 30mb/s or 50 if UHS? anyway it was rated as more, 60 or so. I don't think my card readers (they are old) can operate at UHS-I so maybe it's just card readers limits.

I think if the camera uses 48 mhz, and it gives 21,9 mb/s, then maybe the USB card readers also use 48 mhz? could be, because I know cheap USB devices usually get their clocks from usb, and usb is 12 mhz, so 48 is just a multiple of 12, they can easily get it with PLL. And numbers are the same then.


Ok so I did some tests again with new patch_ap.



After formatting the card in camera, stock settings:
(I did test three times for good measure)
first:
write 16.7 <--- strange
read 21.9
write 15.9
read 21.9

second:
write 15.7
read 21.9
write 15.9
read 21.9

third:
15.7
21.9
15.9
21.9

then everything was similar to what Walter Schulz measured.
0:
93.2
4923.0
4876.1
4970.0

2:
9.1
11.0
9.1
11.0

3: (just to check again)
15.7
21.9
15.9
21.9

4:
93.7
4923.0
4807.5
4970.8

5:
6.4
7.4
6.4
7.4
I didn't notice any strange camera behavior with 5..

6:
9.1
11.0
9.1
11.0

7:
15.9
21.9
15.7
21.9

8: Value goes to C,
93.3
4970.0
4853.0
4923.0

9:
6.4
7.4
6.4
7.4



So the only difference this time was in 4 and 0 and 8 behavior. Now I can get unrealistic numbers too :P :D
Are we trying to activate 50 mHz or UHS-I? what if 50 is just not possible in hardware?

80
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 01:19:58 PM »
I've added some info to the previous post..

Quote
p.s. before battery discharged, I tried to record something in raw with 0x7000003, and it seems like it is slightly better, again. I am not sure, because the numbers are different every time, but for example I tried to do about 10 recordings with default value and I could record 60-80 frames every time, and 85 frames ONCE. But with 0x7000003, I've got 85 frames 4 times, but sometimes it is still only 62 or so. So it seems slightly faster, but I am not sure.

Maybe I should try 0x700000X with X something without zero in second lsb, because it doesn't work when I tried 0 and 4 which is 0b000 and 0b100, everything goes black with 1 which is 0b01, but 2 works (0b10) and 3 too.
So I expect black screen at 5, working at 6 and 7, and corrupted display at 8. and then again black screen with 9 and so on.


ok let's skip raw recording for now...

I tried formatting the card in camera, and fat32 and exfat, with different cluster sizes and everything back in the day... doesn't change anything really. But I'll do it again because why not :)

And on my camera it never showed any unrealistic values. And Only value with 0, 4 and 8 changes to something else (to 3 or 7 or b), and as I can see in raw, only after the first recording. so I expect the same behavior with new module, although we'll see.. I'll report soon.

81
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 12:46:02 PM »
Oh, I did all the tests in photo mode without liveview, with mirror closed. I mean the ML interface get corrupted. Don't know why I wrote liveview, maybe my mind was somewhere else.. sorry :)

What software do you recommend to test a card on PC?


About speed - for example, when I record in raw, it stays at 20mb/s for about 2/3 of the time, but sometimes it drops to 10 or even 5-7, so the common speed is always lower than 20. Maybe same thing happens during the test..
The speed fluctuates all the time with all SD cards, even if I lower the resolution sometimes I can record for example only ~240 frames, but sometimes ~360. And it is not consistent every time.
Which is very strange because 5D2 for example can do almost exact amount of frames over and over again +/- one frame.

Okay, I will provide another patch_ap version, to force the selected value (for the left digit), hopefully the value wouldn't change during the tests.
It seems that it changes the value only after one recording. I tried to record raw video with "print value" active, and it holds it's value during recording. only switching to new value after recording stops. But the speed is always worse in these three modes (0, 4 and 8 ). Although I need to test it more, now battery is charging. And other values stays as is.


p.s. before battery discharged, I tried to record something in raw with 0x7000003, and it seems like it is slightly better, again. I am not sure, because the numbers are different every time, but for example I tried to do about 10 recordings with default value and I could record 60-80 frames every time, and 85 frames ONCE. But with 0x7000003, I've got 85 frames 4 times, but sometimes it is still only 62 or so. So it seems slightly faster, but I am not sure.

Maybe I should try 0x700000X with X something without zero in second lsb, because it doesn't work when I tried 0 and 4 which is 0b000 and 0b100, everything goes black with 1 which is 0b01, but 2 works (0b10) and 3 too.
So I expect black screen at 5, working at 6 and 7, and corrupted display at 8. and then again black screen with 9 and so on.

82
Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 10:56:15 AM »
Very interesting... I made some tests with 550D using some adata micro-sd, can't say exact model name, I don't remember, but manufacturer's speed ratings was I think around 60/70mb for r/w. It's the fastest sd card that I have.


for the left 3, this one:
0x3000003
   ^

What I found, if I override it with 0x4000003, then it goes to 0x7000003 after the speed test, when I override with 0x8000003 it goes to 0xb000003.

so I think, 4 is 0b100, and 8 is 0b1000, and it seems that camera doesn't like zeroes and switches these numbers to 0b111 and 0b1011. (7 and b)
0x0000003 also switches to 0x3000003. so 0 to 0b11, as expected.




stock
write 15.5
read 21.9
write 15.7
read 21.9

0x2000003
write 9.1
read 11.0

0x1000003
write 6.4
read 7.4

0x4000003
write 14.4
read 21.9
write 15.9 <-- this is different, I think camera already switched to 7 after first write test
read 21.9
this is where I noticed value changed to 0x7000003!

0x5000003
write 6.4
read 7.4

0x6000003
write 9.1
read 11.0

so 5 and 6 are the same as 1 ans 2, which is logical in binary.

0x7000003
15.7
21.9
15.5
21.9
about the same as stock value but sometimes rec can go to 15.9(!)

0x8000003
15.6
21.9
value changed to 0xb000003

0x9000003
6.4
7.4
(here we go again)

I also tried e,
0xe000003
9.1
11.0
(again similar to just 2)

0xf000003
15.4
21.9
F is all ones, 0x1111, slightly lower rec speed?



and tests for the right digit:

0x3000004 liveview the interface get corrupted with horisontal/diagonal lines, camera not responding
0x3000001 everything goes black (crashes?)
0x3000000 same as 04

0x3000002
15.7
21.7
seems like original, but read speed is always 21.7 and not 21.9

0x7000002
15.4, 15.5
21.7
read speed again 21.7 and not 21.9



So....... I need to do more tests to see if 7000003 is really better than original 3000003, it can go to 15.9 mb/s rec speed and original value can only go to around 15.7, but I am not 100% sure, I need to do more tests with the original. Maybe it's just doing nothing.
And for right digit, only 2 and 3 are working, and 2 has slightly lower read speed.

83
General Chat / Re: Buying a Canon 6D for €180 - is it worth it?
« on: April 15, 2022, 03:13:38 PM »
find out how much it will cost to replace the shutter, and count it as a potential increase in price. if it is still ok, then get the camera :)
it's 50/50 chances anyway because nobody will know for sure, but if you only record videos then maybe you can live with this shutter count..

and this site (shuttercheck) is collecting data fom users with alive cameras, which is not really the shutter life expectancy metrics... it basically shows how many photos typically were made with these cameras. lol :D

84
cool, I want to do the same for 5D2 using the case from an old battery to make the adapter. If you have an access to 3D printer you can print some kind of a holder for the whole thing, and screw it to the bottom of the camera to the tripod mount.

85
1920x1080 doesn't leave any margin for stabilization or cropping, 3840 even stretched from 1280 but with real 2160 vertical should be much better in this aspect.. at least I think so. Of course I can only compare it to ML 1920x1080 and not other cameras.

86
General Development / Re: LiveView hacks (write speed improvement)
« on: April 07, 2022, 03:15:19 PM »
wow, this is pure magic! congratulations!

87
Raw Video / Re: Best camera to choose (even for RAW)
« on: April 06, 2022, 08:07:37 PM »
only one thing - fast CF cards are very expensive these days. for example, 6D has SD card..
and 5D2 still doesn't have working 1x3, you can activate it by doing some manipulations for ~10 minutes :D, I tried it, it works, but there is no preset for it.

88
Raw Video / Re: Best camera to choose (even for RAW)
« on: April 05, 2022, 06:08:25 AM »
Absolutely, tiny color outline around the objects with high contrast, and you can not get rid of it by focusing. Only by closing the aperture. And if for example I'm gonna use the crop mode and film 2-2.5k footage, it will be more obvious with crop-sensor cameras...

It's not only with old lenses, there are somewhat modern wide-angle lenses in which it can be noticeable even without zooming in on the photo, so you have to close the aperture 1-2 stops if you want to get rid of these color outlines. So it's a common thing, at least for me. For example, with green leaves on trees against the sky, on the edges of a buildings and so on.

89
Raw Video / Re: Best camera to choose (even for RAW)
« on: April 04, 2022, 05:49:01 PM »
hmmmmmm it probably sounded too unclear, I mean in the center of a frame, especially if we are talking about crop modes. Edges are worse on the FF obviously.
I'll google it of course...

For real world scenarios, last time I did some tests. Just black text on the white paper was looking sharper using the same lens on the full frame. In the middle of the frame, when exactly in focus.
Of course I was closer to the paper when I was using the FF camera, to get the same field of view. It is how most people will photograph the same object with the same lens but different camera.

I also have some old lenses that are not really sharp wide open when used on the ASP-C, they are just a little bit soft. But it is not a problem for the full-frame camera, everything seems to be ok. Corners may be especially bad, but who cares about corners, right? :) well, I mean if somebody want them to be 100% sharp, for landscape photography or something - maybe they need crop camera and modern razor sharp lenses..
It just depends on what you want to get...

90
Hardware and Accessories / Easy way to find broken cable fault point
« on: April 04, 2022, 10:14:01 AM »
This is not exactly related to cameras, but if you also do a lot of audio recordings or make custom cables for your cameras this trick can be very useful. I know many of you guys are into the electronics. So I think it can be helpful.
I hope this stuff is OK in the hardware section of a forum. I invented this interesting method of checking cables myself, and never saw anyone doing this, but similar techniques are used in industrial applications.


91
Raw Video / Re: Best camera to choose (even for RAW)
« on: April 04, 2022, 09:59:54 AM »
Utter nonsense. No evidence for your conclusion provided. No hard data -> Just "feeled truth". Nothing to talk about.
In 1:1 cropped mode you will have a hard time to tell ML cameras apart.
We bought used 5D mk2 and it was..... somewhat not exactly sharp. It almost drove me crazy, but when we cleaned the sensor the problem was solved. So I think it was micro dust particles on a sensor that stick to it over the years of heavy use. So clean your sensor, if you notice something strange. Other than that - it is just pixels. And pixels on FF body are larger so the image should be sharper even with the same lens. Less CA.

I later spoke to one guy from the service center, and he said he saw a couple of such cameras, where after cleaning the image became noticeably better in sharphess. This is not exactly the science, but I can imagine very fine dust particles (less than a pixel in size) scatters light and creates softer image. I can be wrong though.

92
wow, initially I thought it was shot using a steadicam. I can hardly see any stabilizer artefacts. do you mind sharing your handheld technique?

93
Raw Video / Re: Which codec is better to use in the MLV app?
« on: March 26, 2022, 11:43:27 AM »
Well, you can try DNxHR, ProRes and DNxHR are two professional codecs for post-production.
But I think if you have a weak computer maybe it is better to upgrade the Premiere to the version where they included the ProRes support. I'm using Premiere 2018 on a 15-years old pc, yeah it is slow but it works.. And ProRes is slightly faster than DNxHR on old computers, at least in my experience.

94
Share Your Videos / Re: Cinematic time-lapse
« on: March 23, 2022, 05:17:52 PM »
yes you're right, I failed to record using 1 fps on the bright scene and I got error, the fps overrides always changing back and forward from 1 to 25 fps I don't know why.. the live view is so lag too.
the liveview and all stuff will work with 1fps too :o :D :D so it's better to set everything before turning the fps override on.

have you tried the original nightly build for your cam? maybe it will lack some functions and SD card overclocking, but for such low speed recording it is not necessary anyway. which makes it possible to shoot timelapses with cameras that have even the slowest SD controller.

95
Share Your Videos / Re: Cinematic time-lapse
« on: March 23, 2022, 03:57:24 PM »
yeah I used to film timelapses with fps override too :) It's just so easy. I think 1..2 FPS is ideal... try using shutter speeds as long as possible, 360 degree wold give the most beautiful movement. well, at least I think so, 180 degree rule doesn't really work here.
But 360 requires long exposures (1s on 1fps) so for day - ND filter is necessary.. I mostly did evening/night timelapses with auto iso, because of that.

96
wow. so this is not only on my computer..

Two years ago I messaged ilia3101 and he mentioned.... I will just quote him (well, I hope it is ok to quote a line from PM)
Quote
I used to use MLV App on a thinkpad X61 (laptop from 2006), and I had to fix a couple of bugs that only happened on the old cpu
And I don't know, maybe it is something like this. unfortunately.
I tried to use some programs that can show some info on exe files, dependencies and stuff, but didn't find anything different from v1.12.

97
@masc I'm using slightly cut down win 10 version (some unnecessary things disabled like store and so on). I had doubts the full version will work on that hardware.. So there is a chance something is missing, but I don't know tbh, all other programs seems to run ok.
Is there an option to diagnose what exactly happening, why MLV App quits? because it's doing it absolutely silently I can't even google the error and maybe see what could be done.

p.s. I'm gonna google what software can diagnose potential problems with running exe's, maybe I'll find something

It seems like I have all the necessary dependencies, and they are the same for 1.12 version

98
General Help Q&A / Re: EOS M searches confusion
« on: March 20, 2022, 04:36:48 PM »
try "EOS M"

usually including your search word in "" means that you want to search this exact phrase.

another option is to use google, and sometimes it is more convenient or if site doesn't have a search box, or if you need to register for search and you don't want to.
the syntax will be:

site:sitename.com search term

for example:
site:magiclantern.fm EOS M


p.s. I modified the message and didn't see that google was already recommended below, sorry ???

99
Hi guys, I recently switched to a "new" (very old) computer and I can't run MLV App 1.13 on it for some reason. While 1.11 and 1.12 are working but only 32-bit versions (although I didn't check 1.11 x64).
But 1.13 just can not start, it doesn't show any error messages or anything, I can see it process in task manager for maybe a second, and then it just silently disappears.

I'm on fairly "fresh" installed windows so maybe I need to install something? like .NET or something else?
The config is (don't laugh!! :D) Intel Core 2 4400 2.0GHz so it's a dual core machine with 4gb of ram and ati radeon hd 4850 installed. Windows 10 x64 21H2 and by the way it runs ok, very smoothly. motherboard and cpu are from ~2007 so it's 15 years old :o but this is all I have for now..

100
@Skinny

Tried to compile a same build for 5d2, but didn't succeed, error messages and no build.
Probably because the source is the "crop_rec_4k_mlv_snd" branch, where the 5d2 is not fully supported  ???
@Levas thank you anyway :)

@ML700D but.. is this a standart canon preview? what about actual recorded raw footage?
Edit: you can't see changes to raw type in canon liveview, but it will do show up in ML preview, the slow low resolution preview option available in raw video menu.

Pages: 1 2 3 [4] 5 6 ... 8