Messages

[magiclantern-Nightly.2014Apr07.5D2212]

I just found another difference:
This new build magiclantern-Nightly.2014Apr07.5D2212 seems to be slower than 2b804e8cdd3c when recording:

Today I could record with 1728x972@25p on a 128GB 1000x KB CF card for as long as nearly 10mins (before I pressed stop). Now I only get about 30seconds (~1500 frames).
I use the same settings as before, which are:

Did I miss something which I could change to get faster speed? I also did all the other things described in the first post of this topic in the Canon menu. This settings I had before and differ from the guide:I hope this somehow can help you guys with merging the forks.

Hi, it's me again. After I reading in some commits about changes from g3gg0 in mlv_rec I decided today to test it again with magiclantern-Nightly.2014Apr22.5D2212. Same setting as posted above. It seems a little bit faster, 1728x972 can now record up to 1 minute, tested with all 5 buffer methods. 1600x900 records continues (tested with buffer method 0 & 3).

So whatever you did, please keep up the great work and maybe soon we can record again continuously with higher resolutions!

Thank you for your quick response. Interessting fact: MLV Converter also says it has 0 frames. Maybe there is an Integer Overflow happening, how long is the frame count integer?

[magiclantern-Nightly.2014Apr07.5D2212]

I just found another difference:
This new build magiclantern-Nightly.2014Apr07.5D2212 seems to be slower than 2b804e8cdd3c when recording:

Today I could record with 1728x972@25p on a 128GB 1000x KB CF card for as long as nearly 10mins (before I pressed stop). Now I only get about 30seconds (~1500 frames).
I use the same settings as before, which are:

Resolution: 1728x972
Aspect ration: 16:9
Global Draw: OFF
Frame Skipping: OFF
Preview: AUTO
Status when recording: ICON // wasn't in the other build, so I don't change it
Start delay: 4sec
Digi Dolly: OFF
Card warm-up: 128MB
Extra Hacks: ON
Fix black level: OFF // also because new
Debug trace: OFF
Show buffer graph: OFF
Buffer fill method: 4
Reserve card space: OFF // new
Tag: Text none
Tag: Take OFF

Did I miss something which I could change to get faster speed? I also did all the other things described in the first post of this topic in the Canon menu. This settings I had before and differ from the guide:

peripheral illumin. correct: ON
color space: sRGB
high ISO speed noise reductn: 0: Standard

I hope this somehow can help you guys with merging the forks.


EDIT: since I'm rather new here, I hope it's okay I posted this here. Or should it go into the Nightly Builds thread (http://www.magiclantern.fm/forum/index.php?topic=3072.6258)? I don't want to crosspost...

[EDIT: whitout compression, it's roughly the same size (36GB). so this means, it's not the data it's mlrawviewer? anything I can do to help?]

EDIT: whitout compression, it's roughly the same size (36GB). so this means, it's not the data it's mlrawviewer? anything I can do to help?


Unfortunatly I used loseless compression, I don't know how much it is suppose to compress.

Anyway the DNG are 19.4GB, the combined MLV about 35GB. Does that help you. Should I try to convert it again without compression and get back to you?

[magiclantern-Nightly.2014Apr07.5D2212]

Hi there,

first of all. really awesome guide with all the infos needed in one compact place. thank you. also thx to the devs of course!

I just updated to the last nightly magiclantern-Nightly.2014Apr07.5D2212.

everything seems to work just fine, but one small thing changed from the a.d build I had before ( 2b804e8cdd3c ), which kind of bothers me. there, when you disabled global draw, it still showed you a white rectangle which indicated the size which gets recorded. sry, english is not my first language. what I mean is you had a small rectangle if for example you choose 1728x972 and an smaller one if you choose 1728x824. would it be possible to implement this again?

Reason: I like to let the other stuff (waveform, vectorscope, etc) turned on when working on my image. it's bothersome to turn it all on and off everytime you record. thank you

EDIT: Ah, pravdomil already posted here that this is one of two features which were not brought back to the main branch. so this is already known. I'm just kindly asking, is there any work going on to bring this features to the unified branch?

Hi,

using 1.1.4. I also have a blackscreen/seems to doesnt load at all. I can't verify playing sound because I recorded without sound.

I'm on a Windows 7x64, 16gb ram, i5-2500k.

Things is, it does this only with one file, which is rather huge (.MLV up to .M07). Could this be the problem. An other file which only goes to .M03 plays just fine.

Also this is a snippet from the log, this lines get repeat a lot:

Code Select Expand


MlRawViewer v1.1.4
(c) Andrew Baldwin & contributors 2013-2014
Using GLFW
wavnames []
wavfilename C:\Users\Joe\Work\movies\2014\ML Raw Test\M08-1426.WAV
Opening MLV file C:\Users\Joe\Work\movies\2014\ML Raw Test\M08-1426.MLV
Black level: 1791 White level: 15000
FPS: 25.0 (25000/1000)
Audio frame count 0
Traceback (most recent call last):
  File "C:\Projects\mlrawviewer\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 283, in __draw
  File "<string>", line 755, in onDraw
  File "C:\Projects\mlrawviewer\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 234, in renderScenes
  File "<string>", line 414, in prepareToRender
ZeroDivisionError: float division by zero


Is the file corrupt or is it something with the player? When I convert it MLV Converter 1.9.2 it seems to only take the .MLV, but maybe that's just the converter.

ps.: thanks for your awesome work btw!