Menu

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.

Show posts Menu

Messages - Aeidxst

#26
Quote from: reddeercity on March 05, 2017, 12:48:33 AM
-snip-
Yes, these tests are done in mlv_lite.

So, what you are basically saying is that mlv_lite is far from flawless, and I should use full mlv_rec instead? The problem with that is that I usually shoot clips that are 1-2 minutes long, and full mlv_rec doesn't allow me to record more than max. 20 seconds...
#27
Quote from: Audionut on March 04, 2017, 06:35:02 AM
There is.

Quote from: a1ex on March 03, 2017, 06:05:21 PM
- in menu, you have selected a resolution higher than your max resolution (here, 1920 vs max=1856)
- you start recording very quickly after returning from zoom mode

Even so, the probability of triggering the bug will be lower than 100%.

Can you confirm?

If yes, the problem is unique to mlv_lite and it's very easy to fix.

@reddeercity @Audionut @a1ex @Danne

So, I just tried reproducing the bug with the settings exactly the same as in OP. I shot the tests with a 50mm 1.2 lens. It gave me interesting results. What I did is the following:

- [1] I started recording regularly, without using the zoom function right before it.
The bug happened 0/10 times.

- [2] I started recording right after leaving the zoom function.
The bug happened 6/10 times. Two of those six MLV files don't even give me a .dng sequence when converted. Those two don't give me any frames at all. Four of those six MLV files became glitched as before. Pic related (1) is the 'completely glitched out' bug.

- [3] I started recording while in the zoom function. The camera doesn't let me record in x10 zoom (it says 'RAW detect error') but it does let me record in x5.
Another bug happened. Instead of the screen completely glitching out, all the footage had a pink/purple hue over it. This happened 10/10 times. Pic related (2) is the pink/purple hue bug.

- [4] I started recording right after I had recorded in zoom function. To be clear, I was recording exactly the way I did at [1].
The pink/purple hue bug happened 4/10 times. Pic related (3) is the pink/purple hue bug while not being in zoom function.

An important thing too: The pink/purple hue bug sometimes happens INSTEAD OF the completely glitched out screen bug. I have no idea what causes it to be either the GLITCH bug or the HUE bug.


Few more questions I am having now:

- How can I avoid/fix the pink/purple hue bug? It hasn't happened to any of my important footage yet though. But since I encountered it while trying to reproduce the other bug, I figured that it might occur at some of my 'real' recordings too.
EDIT: I just tested the MAIN.command file (from a1ex and Danne) on my pink hued footage, and it works. So that problem is also solved. Still doesn't explain why same of the recordings/MLVs contain 0 frames.

- Why does my camera/ML switch to 1920x1076 instead of the original 1856x1044 when I switch to zoom mode? Why doesn't it stay at 1856x1044? Even weirder, I cannot even select 1856x1044 when I'm in zoom mode. It's always 1920xXXXX or 1600xXXXX (or a lower first number). Why can I only tweak the second number, and not the first one? If I could set it to 1856x1044 in the zoom mode too, I might be able avoid the glitch in the first place.


ATTACHMENTS

Pic related (1) - the 'completely glitched out' bug which Danne and a1ex helped me with.



Pic related (2) - Hue bug in x5 zoom mode



Pic related (3) - Hue bug in regular (no zoom) mode


For reference, this is what the glitched images should've looked like. This is a frame from a test in which the bug didn't occur.


I really hope I'm contributing something to the development of ML with my time and tests. I'm doing it for myself regardless, since I want these questions/bugs answered as well :)
#28
Great, big thanks everyone. Wish there was a way to repay you. You have no idea how big of a problem you've solved for me.
#29
Quote from: Danne on March 03, 2017, 10:05:24 PM
Here is a patched mlv_dump with the black fix number hardcoded as well according to a1ex proposal. Tested with your corrupt file. There is a howto file inside the zip.
https://bitbucket.org/Dannephoto/magic-lantern/downloads/mlv_dump_patch.zip

Just put all the files in the folder next to mlv_dump and the MAIN.command script. DO tests with copies first!

What you do is you double click the MAIN.command script and your MLV files will be processed into folders with dng files. Make sure to give the MAIN.command permission rights. It,s explained in the howto what to do. If any questions write back. Do backups. I tested only briefly. Should work for all files including .M00 etc.



I tried it out, and worked like a fucking charm. I literally have no idea how it's possible for someone to figure out how to fix a problem like mine. Truly incredible.

Thanks a lot. My important footage that was corrupted is completely restored. Can I keep using this download for future reference, in case this problem keeps occuring? :)
#30
Quote from: reddeercity on March 03, 2017, 08:41:17 PM
@Aeidxst , I can help you I'm downloading your MLV right now . I'll be off line for a few hours thou but I will check this thread after that.
Hey that's awesome, thanks. I have more than only one file that has to be taken care of. Do you need them as well? Let me know when you're back online. I'm at GMT +1.
#31
Quote from: a1ex on March 03, 2017, 06:34:52 PM
The fix I've posted does not depend on your operating system. Any community member with command-line skills can help you with OS-specific steps.
Ehm, okay, but I'm kind of stuck now. What would be the next step to recover the damaged/corrupted files?
#32
Quote from: a1ex on March 03, 2017, 06:05:21 PM
The good news is that your file can be recovered with a simple patch to mlv_dump:


--- a/modules/mlv_rec/mlv_dump.c
+++ b/modules/mlv_rec/mlv_dump.c
@@ -3173,6 +3173,9 @@
                 
                 lua_handle_hdr(lua_state, buf.blockType, &block_hdr, sizeof(block_hdr));

+                block_hdr.xRes = 1856;
+                block_hdr.yRes = 1044;
+
                 video_xRes = block_hdr.xRes;
                 video_yRes = block_hdr.yRes;
                 if(verbose)


then:


mlv_dump M02-1834.MLV --dng --black-fix=1780
Okay, awesome to hear that my files can still be saved. Very happy about this, since 20% of everything I shot became corrupted like this.

However, I have absolutely NO clue how to do what you said. I just read what you typed (the entire code thing) and I don't undestand anything of it. What do I do, and how do I do it? Oh, and please mention on what OS you're working. I'm using a Mac atm, but I can do this on Windows if it's needed.




Quote from: a1ex on March 03, 2017, 06:05:21 PM
I believe the bug only happens when the following conditions are met:
- in menu, you have selected a resolution higher than your max resolution (here, 1920 vs max=1856)
- you start recording very quickly after returning from zoom mode

Even so, the probability of triggering the bug will be lower than 100%.

Can you confirm?
No, I haven't selected a resolution higher than my max (which is 1856x1044) because my camera doesn't let me.

Yes, I indeed started recording very quickly after returning from zoom mode. I find zoom mode very handy if I focus manually, especially with shallow depth of field. So I think that's the problem then.
#33
Quote from: a1ex on March 03, 2017, 04:17:15 PM
Can you upload a sample MLV?
Sure.

Here's one that isn't broken:
https://we.tl/U8cYSOLQEH

And here is its .dng sequence:
https://we.tl/bj19posJK4



Here's one that's broken. I think I even shot it within the same minute, with no change in settings whatsoever.
https://we.tl/efk870YaM5

And here is its .dng sequence:
https://we.tl/MMBDS8x11k


I included the .IDX and .M00 and .M01 and .MRX files too.

I really hope you or someone can help me with this. I have already tried other converters such as cr2hdr, same result. So there's really something wrong with the files.
#34
Hi everyone,

I encountered yet another problem, which is even more devastating than my previous one. I have always used raw_rec on my Mark II and I've never really had any problems. I recently switched to the new RAW (mlv_lite).

First, here are my settings:

I'm recording 14-bit RAW video at 1856 x 1044, 23,976 fps. There are no other ML features being used, except the mlv_lite and mlv_play.

I'm using a Canon 5D Mark II, with 50mm 1.2 and 24-105mm 4.0 lenses, using SanDisk Extreme PRO as storage (64GB, 160 MB/s). No external monitors connected


This is in my ML folder > Settings > raw_rec.cfg.

# Config file for module mlv_lite (MLV_LITE.MO)

raw.video.enabled = 1
raw.write.speed = 7335



Yesterday I recorded some (very important) footage. When on the set, I already wasn't able to view back some of the footage with mlv_play. The weird thing is that it was only some of the footage. It just gave me a black screen with an error along the lines: "Could not load blocks" or something.

I just converted all my footage to .dng sequences using MLVFS. All of the footage I couldn't view on the set suddenly turned into 1920x1078 footage, instead of the 1856x1044 I originally shot at. And even worse, all those clips became completely glitched out. See pic related. All the frames of the clips of which the resolution changed (which I couldn't view on set) became like this. About 20% of all the clips I shot turned into pic related.


What caused this, and what can I do about this? Can I still save my 'corrupted' files/footage?



#35
Hey, have you already found a solution for this? I also just switched from RAW to MLV, and I'm also still looking for a converter that works the same as RAWMagic. I think RAWMagic and such are specifically used for RAW, and not for MLV.
#36
Weird, I tried to reproduce it, but I can't manage to do it. However, it may be because I uninstalled and installed ML for the fourth time. I'm now using the latest Nightly Build, using mlv_lite. Thanks for all the help, no idea how I eventually solved it. Didn't do anything special.

Last question: Which MLV converter is similar to RAWMagic Lite? Mac preferred. Since I'm using MLV now I'm looking for a new converter that converts to .dng sequences. I loved the workflow and design of RAWMagic, hence I'm asking for a similar program suited for MLV. Thanks!
#37
No, I did not have a HDMI monitor connected. Frame rate: 23,976. Here are my settings:

I go the the ML folder > Settings > raw_rec.cfg. This is what's inside:

# Config file for module raw_rec (RAW_REC.MO)

raw.video.enabled = 1
raw.res.x = 14
raw.write.speed = 7565



Normally I was always able to record 1856x1044 14bit RAW video without frame corruption. I was sometimes even able to record continously for ~3 minutes straight.

Is this information useful to you?
#38
Hi, thanks for your reply. To be very honest, I do not really feel the urge to explore what exact set of settings produces this bug. Yes, of course I want to prevent it in the future. But isn't there a concrete way to fix this problem?

I used the older raw_rec, not the mlv_lite.
#39
Hey everyone,

I have always used raw_rec on my Mark II and I've never really had any big problems. Maybe one 'broken' frame per every 256 GB or so. But since a few days ago I'm noticing around 6-7 broken frames for every 1 minute of footage. I have changed literally nothing about my setup since last time when I didn't have this problem.

I'm recording at 1856 x 1044. There are no other ML features being used, except the raw_rec.

I'm using a Canon 5D Mark II, with 50mm 1.2 and 24-105mm 4.0 lenses, using SanDisk Extreme PRO as storage (64GB, 160 MB/s).


Any help would be greatly appreciated. I tried installing the most recent version of ML, but no difference. Could it be the cards aging? I've had these cards for almost a year now, using it about once a month for RAW recordings.

Pic related, it's the problem I'm talking about:

http://i.imgur.com/YvrSIta.jpg

#40
thank you. Sorry, my english is very bad
#41
Sorry, my English is really bad. And from that post, I can't really make up what's new, and what the EXACT differences are between RAW_REC and MLV_LITE.

Perhaps you could explain it to me?


Thank you
#42
Hi,

I've always been using Magic Lantern on my Canon 5D Mark II. Recently I figured my Nightly build was heavily outdated (2014) so I just downloaded and installed the latest one. I've alway used raw_rec, but that option is nowhere to be found anymore. Only things I can find are mlv_rec and mlv_lite.

Is mlv_lite the exact same thing as the old raw_rec? And what are the differences in quality when it comes to mlv_lite vs. mlv_rec?

EDIT: I'm also getting MLV files, instead of RAW files, which tells me that there's something significantly different. Can anyone clarify?

Thanks.
#43
Title.

https://www.youtube.com/watch?v=VGO7JtYCun8

https://www.youtube.com/watch?v=ZhCbsAWguu0

I keep on thinking this is Canon + Magiclantern, but something tells me this is GH4. Does anyone have the knowledge to tell me what this is filmed with? Lenses are not necessary, just system.

Thanks in advance :)
#44
General Chat / What is this filmed with?
January 05, 2017, 03:32:27 AM
Title speaks for itself.

https://www.youtube.com/watch?v=VGO7JtYCun8

https://www.youtube.com/watch?v=ZhCbsAWguu0

I keep on thinking this is Canon + Magiclantern, but something tells me this is GH4. Does anyone have the knowledge to tell me what this is filmed with? Lenses are not necessary, just system.

Thanks in advance :)
#45
Yeah, it is definitely the card. I just borrowed someone else's card that has 60MB/s and it worked for 20+ seconds.

A few questions left:

What should I go for? RAW or MLV? I'm getting myself a (or two) 64GB SanDisk for the shoot, so memory/write speed won't be a problem.

and

Sometimes it shows '1ms idle' or '2ms idle' while recording, next to the write speed. What does that mean?
#46
Which benchmark do I run? Just the top one? The Card R/W benchmark (5 min)? And then press the 'play' button afterwards?

Because if I do so, I can't see the word 'card' anywhere. The only thing I see when doing this is:



EDIT: And it takes over 20 minutes to complete.

EDIT 2: And these are the results.



What to do?
#47
Where can I see that (where benchmark would show 'Lexar')?
#48
Alright, so I'm fairly new when it comes to ML but I'm not retarded.

With my old card (SanDisk 8GB 30MB/s) I was able to record about 5 seconds of the highest possible RAW resolution in 24 fps. Yesterday I bought myself a Lexar 32 GB 1066x 150MB/s CF card and I decided to try again. Next thing you know, it still only records for ~5 seconds max. The overlay when recording says it's writing 25MB/s though, so I'm guessing either there's something wrong with my Mark II or with the CF card. Or is it something that has to do with the ML settings? The only thing I did was turn on raw_rec, and later turn on RAW video with the desired resolution.

I already tried recording a few times to 'warm up' the card, I already tried the 'Card Warm Up' function, and I already tried mlv_rec, and none of those worked. Still 5 seconds max. recording.

I also performed a benchmark to give you guys some additional info:




I really need this fixed, as I'm having a very important shoot this weekend. Hope to hear from you soon.