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 - pc_bel

Pages: 1 2 [3] 4 5 6
51
@A1lex
Thank you very much for the explanation!!!... I feel really dumb but I guess not everyone will know about everything. Coding is a unknown world for me. The most obvious things for you are absolutely unknown for me. :-[
I would like to do more than only download the builds, but outside testing that builds I don't know what can I do...

52
I'm taking a look to the Starting Point... and I don't know what to do... I have no knoweledge in any coding languaje. For me is like cheneese  :( :-[ I'm sorry but if I can do something more just let me know.

53
Quote
Quote from: a1ex

    Also got 4096x3072 working at 12 and 12.5 FPS (24/25 in Canon menu) and did some more fixes for very large resolutions. Even if you only get a few frames, I still find these modes useful with half-shutter trigger and pre-recording (e.g. for taking photos of really unpredictable subjects).

Quote from: DeafEyeJedi
Oh absolutely this will be useful. Especially for birding, sports photography & whatnot. This is incredible and should be a bit more forgiving than Canon's stock full burst mode which is only 6 frames per sec for 5D3.  :P

A dumb question maybe... but... someone are getting realtime preview in this mode? How can you focus and framing for sports and birds?... I think I'm missing something...

54
Any dev think if there is any possibility to get some signal through hdmi in the new full res live view mode?... just for framing and focussing, don't mind if res is low (VGA)...

56
Testing April 23th build 5D3 113.
When I change to a 192050p3x3 mode with fps override on, and try to switch fps override to off, camera freezes and I get Error80. Need to pull battery.

57
@quentin

+1

Thank you!!!!!

58
Testing last build april14th.
Tearing issue in 1920x96050p3x3 is gone (I understand because modification of buffering). It is almost perfect for me. I'm really grateful, thanks A1ex!!!... It was a dream some time ago, and now...
Thank you very very much...

Now the only downside is recording time with hi isos in 14bit lossless and incorrect framing, but I can live with that.

Thanks again!!!!!!!

59
Another issue in 1920x960 50p 3x3 is framing.

Here there is a composition comparing real image vs live view framing:
http://ovh.to/TpLuMh

60
Now I've got two consecutive errors... Error 70, then I turn off camera. Next an  Error 80. Camera does not show live view after both errors. After a new reboot all is apparently ok...

61
More testing with april3th. 5Dmk3 113
1920x960 50p 3x3.
Now I'm recording continuous at ISO3200.
I'm a little confused... Maybe it depends on the detail level of the image?...

62
Tested:
April3th build 1920x960 50p 3x3 mode NO TEARING ISSUE!!!! :) :) :) Continuous at ISO100 and 400. At ISO800 shorter recording times (aprox 20sec. for me).
5Dmk3 113 Lexar64Gb1066x

63
@beauchampy
I'm really interested in 192050p 3x3 mode and while I wait for a solution for the tearing issue, for me the solution is 1080p45 3x3 mode. Not same slowmotion like 50p but no tearing issue and continuous recording. Tested at ISO3200 and it works for me continuous!!!. Only framing is a little bit offset...
5Dmk3 113 Lexar 64Gb 1066x

64
Your camera appears OK, no need to worry.

 :) :) :)

Thanks Danne

65
Fantastic!!!

Be aware with ISO. For me 800 is where problems start. I can get only few seconds with 800 ISO. And as I report in post #148, I get a "cutted" image in the top of frame with paning movements... So no usable for serious work...

66
@beauchampy

Quote
First up, it's a bit sketchy getting signal from the HDMI - have to power on, go into Canon menu, back out again, screen flashes all kinds of weird, live view then appears

Same for me, but the same thing happens to me with older (and more stable) builds... To get hdmi signal I often go to play button and back out again. In my case using a Zacuto EVF.

I get continuous recording with april6th build with ISO100 1920x960 50p GD off 14bit losseless with or without hdmi in 5Dmk3 113.

67
If you need to do some "mechanical-tedious" work, if you explain me how to do it, I can do it...

68
Quote
Here's a boring task: what's the number of pixels before the cut? (min/max/median would be great)

 :-[ Sorry for that!!!... Its only thing that makes image unusuable.

I've  measured px and the pattern is very strange... min distance I've found is 7px, max is 125px, but it doesn't follow a logic. At first it seems increassing with the panning velocity, but looking close, during panning, one frame have 98px (from top to cut) the next 112px, the next 18px, one frame (in between all of this) is correct, and for example, the next have 73px...

Min I found: 7px
Max I found: 125px
Average from random 17dng:83,8px
@A1ex
Is this what you are asking for?

69
Quote
Two failures on the same build are a bit too much to be a coincidence. For now, my advice would be to avoid the Apr04 build, even though some reports say it's faster (I'm willing to bet it's not, but I'll benchmark it, just in case).

Ok, back to april6th...

192050p3x3, 5D3 113, ISO 100: 10 recordings 1min/each (camera didn't stop recording, I stoped recording assuming continuous).
192050p3x3, 5D3 113, ISO 400: 10 recordings 1min/each (camera didn't stop recording, I stoped recording assuming continuous).
192050p3x3, 5D3 113, ISO 800: 1 recording, camera stops recording after 10sec. (message:"didn't make it to stimated record time")
I turn off camera.
When I turn on camera, a full screen message appears like this one:
Quote
When I boot camera again, I get this message full screen:
ML ASSERT: 0 at mlv_lite.c:2006 (compress_task), task compress_task vv:1 mode:3

srm_malloc_suite(1)...
srm buffer #1: 48600064
srm_malloc_suite(f1408)
Resolution changed: 2080x1587 -> 2080x961
Black level: 2047

Compressed size higher than uncompressed - corrupted frame?
Please reboot, then decrease vertical resolution in crop_rec menu.

ML ASSERT: 0 at mlv_lite.c:2006 (compress_task), task compress_task vv:1 mode:3

So ISO was the culprit for not get continuous recording with april6th?... My fault. :-[

No STACK OVERFLOW error for now...

Edit: in this tests I got the same corrupted image that before when panning (top part of frame with motion cutted).
Can I ask if is easy to adress this, or not? That would make the recordings usable...!!!! (at least fro me).

70
Day of testing!!! :)

I returned to crop_rec 113 april4th build due to the short recorded times I get with april6th (I don't know why...)  :(

Really surprised for the extremely low rolling shutter in 1920 50p 3x3 mode... but panning, I get a cut line in the top part of the frame, only with panning! it dissapears in static frames.

This video explains better:
http://ovh.to/b2isZ5B

Edited: I can't see the cut line in live view, only in processed dng's.

71
For now, all I could get are these error messages:

ASSERT: hLvJob->hJpegMemSuite
at ./Epp/Vram/VramStage.c:868, task Epp
lv:1 mode:3
Magic Lantern version : crop_rec_4k.2017Apr06.5D3113
Mercurial changeset   : bc99f7502deb (crop_rec_4k) tip
Built on 2017-04-06 08:28:51 UTC by jenkins@nightly.
Free Memory  : 172K + 3779K

ASSERT: IsSuiteSignature( hSuite )
at ./PackMemory/PackMem.c:599, task RscMgr
lv:0 mode:3
Magic Lantern version : crop_rec_4k.2017Apr06.5D3113
Mercurial changeset   : bc99f7502deb (crop_rec_4k) tip
Built on 2017-04-06 08:28:51 UTC by jenkins@nightly.
Free Memory  : 172K + 3778K

ASSERT: fInitialize == TRUE
at ./System/PostPostman/PostPostman.c:243, task Epp
lv:0 mode:3
Magic Lantern version : crop_rec_4k.2017Apr06.5D3113
Mercurial changeset   : bc99f7502deb (crop_rec_4k) tip
Built on 2017-04-06 08:28:51 UTC by jenkins@nightly.
Free Memory  : 172K + 3781K





72
Quote
Just tested April 6th 113.

Can't get continuous recording like before with april4th, only 10 sec. before message "didn't make it to stimated record time" and then recording stops. (1920 50p 3x3 mode).

After reboot, I get the same message as with the april4th build:
ML ASSERT: 0 at mlv_lite.c:2006 (compress_task), task compress_task vv:1 mode:3

srm_malloc_suite(1)...
srm buffer #1: 48600064
srm_malloc_suite(f1408)
Resolution changed: 2080x1587 -> 2080x961
Black level: 2047

Compressed size higher than uncompressed - corrupted frame?
Please reboot, then decrease vertical resolution in crop_rec menu.

ML ASSERT: 0 at mlv_lite.c:2006 (compress_task), task compress_task vv:1 mode:3

73
Just tested April 6th 113.

Can't get continuous recording like before with april4th, only 10 sec. before message "didn't make it to stimated record time" and then recording stops. (1920 50p 3x3 mode).

74
Quote
I shot something like 12 takes.
I tried 14lossless and got a warning at the top of the screen (couldnt read due to age)
and a series of many warnings.
I removed the battery, start from scratch, defauly ML settings, load modules.
I set 10bit
Set the Canon video to 1280x720, NTSC.
Everything as expected.

Yes, same as me. Now message is:

[76] CEC: stack warning: free=128 used=3968

I'm totally lost...
@A1ex
I'don't know what to do, so if you can point me to what to do to help, just let me know.

After the messages I can reboot and I can record continuous without corrupted frames (allways talking about crop_rec April 4th build, 1920 50p 3x3 mode)... so this is not a big problem, but I have no idea of code so no idea what all this messages mean and what to do... sorry  :-[ I'm limited to explain what happens...

75
Quote
Quote

    CTRL SRV Stack Overflow free=84 Used=163008176


Would be great if you can find a way to reproduce this.

After 2 hours I'm not able to reproduce CTRL SRV...

Quote
Suddently get this message in top of screen (in red letters):
[103] COMPRES_TASK: TASK WARNING: Free=164 Used=3932
Camera off.
When I boot camera again, I get this message full screen:
ML ASSERT: 0 at mlv_lite.c:2006 (compress_task), task compress_task vv:1 mode:3

srm_malloc_suite(1)...
srm buffer #1: 48600064
srm_malloc_suite(f1408)
Resolution changed: 2080x1587 -> 2080x961
Black level: 2047

Compressed size higher than uncompressed - corrupted frame?
Please reboot, then decrease vertical resolution in crop_rec menu.

ML ASSERT: 0 at mlv_lite.c:2006 (compress_task), task compress_task vv:1 mode:3

This ML ASSERT message appears when in crop_rec mode 1920 50p 3x3, I change (in Canon menu) from 1280x720 50 All-I to 1920x1080 25 All-I before change crop_rec to OFF. I need to reboot 2 times and then all come back to normal operation...

I will try again to reproduce the CTRL SRV message :)

Pages: 1 2 [3] 4 5 6