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

#26
This is strange, I'm constantly getting this "card/camera really exFAT?" error whenever I format card in canon menu in camera(5DM3).

Some other errors i'm getting is "frame skipped, stopping recording" with 1920x808 23.976fps on lexar 1066x 119gb card, and "this card cannot be read remove card 1"

It seems to me that every time I update to a newer build I get more problems with ML.
#27
Still till this day, I can't seem to figure out this "DUAL ISO" or "HDR".

I have all these softwares for post processing, yet still can't figure it out. I don't even know the difference between the 2 and if there is no difference, if they do the same thing, why have both in there. Not a complaint just curious.

I want to get the most out of the awesome ML features, but there seems to be no "decent" workflow video out there particularly for the 5DM3 on windows.
#28
When I first got my 5DM3 early last year.. or a little more than a year ago, I was using the 123 version and I would record 1920x1080 24fps all the time with no bad frames at all. When I started to update to newer versions of ml I started noticing bad frames, mostly when I changed to 113 version.

I wish I had never changed anything.
#29
no hasn't been fixed. Still occurring.
#30
why in the hell is davinci resolve crashing upon selecting magic lantern raw files.

https://youtu.be/A-giOSQH2Fc
#31
Quote from: DeafEyeJedi on July 15, 2015, 11:17:12 PM
@itsDPmikey:

Damnnn... from which ML nightly build did you use?

@pholler:

Sorry been out and about with work and haven't had the time to play with 5D3 until now. Will get back to you asap!


latest 1.1.3 July 1st
#32
just saw my videos I took on a trip to Lake Tahoe. I was so pissed off to find so many pink glitchy frames.
#33
Quote from: actingnurse on June 22, 2015, 11:07:04 PM
Will ML run on 1.3.3 yet?



NO

The 1.3.3 firmware [b]also known as the[/b] AMLF(Anti-MagicLantern Firmware) by CANON, was produced in efforts to [b]STOP [/b]people from using MagicLantern.

What does AMLF 1.3.3 actually fix/do? Well lets take a look at what CANON has to say.
[b]Details http://www.usa.canon.com/cusa/support/consumer?pageKeyCode=prdAdvDetail&docId=0901e02480e37761

Firmware Version 1.3.3 incorporates the following improvement and fix:[/b]

"[i]Improves the AF controllability when shooting in Live View mode with a wide-angle lens (fixed focal length or zoom).
Corrects some incorrect indications on the "English" and "Russian" menu screens.[/i]"

...thats it? Yes that's it.

In other words, this firmware update is absolutely useless. [b]BUT[/b]! What CANON did not include in this release details was that they wrote this firmware strictly for MagicLantern users to stop us and you don't have to be a "brain surgeon" to understand this.

One of the things CANON [b]DID NOT[/b] [s]disclose [/s]is that with this new firmware you can't downgrade, at least not as easily as you could before, now you need to be on the computer and have it connected to the Camera. In reality this is not too different from what Microsoft was trying to do with Xbox One, taking the rights away from the people.

One of the most Obvious things about CANON is that they [b]OVERPRICE [/b]their products. Primarily their cameras.

You can [b]accomplish [/b]just about [b]anything [/b]with 5D if not more than lets say the c100 and some of the CANON'S other high priced cameras.

For this primary reason, CANON has tried to find a way to stop the MagicLantern use on their cameras.
Consider what you can do with some of the lower end EOS cameras with MagicLantern installed, some INCREDIBLY WONDERFUL things. So you may just ask yourself.. why spend thousands when you can spend hundreds for the same thing if not BETTER! this obviously isn't something that CANON finds favorable.

Instead of lowering the prices of their cameras to reasonable prices, they continue with their foolishness by taking away from the people what BELONGS to the people.

If I paid for it and now its mine, I should be able to do whatever I want do with it. Right? I guess CANON doesn't think so.


I've blabbered on enough about this.
All in all, you are [b]NOT[/b]! missing out on anything by not installing a useless update like 1.3.3
#34
Quote from: 5Djp on June 22, 2015, 06:12:36 AM
Thanks Frank
It would be nice if it showed when it actually starts recording instead of red/yellow/green stuff.


It starts recording when the countdown or count-up starts. When the timer starts then it starts recording.
#35
Quote from: itsDPmikey on June 19, 2015, 08:14:33 AM

This is Correct. But I did download it before it was removed

I'm going to correct myself. I misread the comment, I do not have 1.2.3, I for some reason saw 1.1.3. sorry for the confusion
#36
Quote from: tron on June 18, 2015, 03:21:53 AM
June 9th firmware for 5D3 1.2 3 seems to have been removed!


This is Correct. But I did download it before it was removed
#37
Quote from: italobrito on June 12, 2015, 06:52:48 AM
itsDPmikey, thanks a lot, you really helped. I was mainly thinking about 113 because it's said to have slightly faster write times but I already have a sufficiently fast CF card so I guess I'll stick with 123.

Just one last thing, should I format both the SD and the CF in exFAT or do I leave the SD card with ML in FAT32?

Thank you very much.

Yes but it is not necessary due to the fact that ML FIRMWARE files don't take much space at all and don't require very high speeds. It's more the CF(or the card that is being recorded on) that really improves when you format to exFAT.

The maximum file size for FAT32 is 4gb, which if you record in raw and depending the FPS and resolution size, you will pass 4gb very quickly like around 5min or less. This is why FAT32 is not recommended.

exFAT allows a maximum file size of 16eb. That's 16 EXABYTES! As in 16 QUINTILLION, As in 16,000000000000000000...so as you can obviously do the math that's an incredible amount of difference.

So theoretically if you have a card that is 4gb or less, it's not really necessary. But OBVIOSULY if it's a card with more than 4gb space then yes exFAT that lil sucker!

#38
Quote from: italobrito on June 09, 2015, 07:20:37 PM
Sorry for the dumb questions but I still have some:

- Do I install ML on an SD card and put the extra fast CF card in the second slot? Or do I forget about the SD slot and everything goes in the CF?

- Is the uninstallable bootflag modification still present in both 1.1.3 and 1.2.3? Or is it possible to completely and cleanly uninstall ML in both firmwares?

I'm mainly trying to decide whether to go with 1.1.3 or 1.2.3. I won't need the official Canon things in 1.2.3 but there's some extra info in the 1.2.3 thread that isn't present here and I just want to make sure the 1.1.3 also have these options (clean uninstall, optional EosCard, ML restores itself after format etc).


You can either split the process like so
. Put ML on SD card and use the CF card for recording files (this is highly recommended and easy to set up in the ML menu).

or

. If your SD card is fast enough with enough space you can put both the ML and set to record files on the SD as well. (not recommended. Only if you have no CF option and only have SD card)

*Yes its possible to completely and cleanly uninstall ML in both firmwares. Whether you are on 113 or 123, when you enter in canon menu to update firmware(while firmware card is in the camera) Install ML and when it installs and says "done", At that point it will start to count down. IF you want to uninstall let it count down all the way and that will uninstall it. THAT'S IT.

currently there are some issues with the 113 with pink frames and whatnot, but this wasn't always the case its only been happening in the most recent builds(have not tested the June build yet)
123 is steady but lacks some options so it depends on what you are doing.

I have formatted my CF card in exFAT and I'm using 1.1.3 again, everything is good for me so far.
#39
Quote from: DeafEyeJedi on May 26, 2015, 06:52:48 PM
exFAT is a lifesaver... As always!


right exactly. I recommend everyone to do so if they have not already.
#40
Quote from: paisleybrew on May 23, 2015, 04:38:41 PM
itsDPmikey: What nightly are you running with 1.1.3?

I recently noticed some pink/bad frames in some clips a shot a while back and wondering which version you were running. Would also be interested in knowing which nightly you are running Alex, as you say you don't experience this issue?

itsDPmikey, I'm not sure that FPSoverride is the issue, as I was running 25fps Canon menu as well as in the ML settings. When I get a chance I'll run some tests and see what I find.

Is there another thread for this issue yet?


Honestly I always update whenever I see an update available. I will tell you that I have gotten the pink glitch frame on every release since march. Right now I'm on the latest May 2nd release.

I had accidentally deleted some files from my CF card and I used LEXAR Image Rescue 5 that came with it and recovered deleted files. I then had to format the card and decided to read up on the diff format options available and Exfat is the best so I did an exFAT format on the computer and got the card in to the camera and shot a 17min non stop 1920x1080 24FPS video which no pink frames. I had realized that I had formatted the cards originally in FAT32 which was limiting the cards to 4gb increments. Please read more on exFAT and other formats.

Also the recording status icon in fat32 use to be yellow and red in 1920x1080 24fps
With exFAT its just green! and I even shot over 2K at 2560x1024 24FPSoverride, and it was still green with no skips. This was AMAZING to say the least. So I recommend to get your cards formatted in exFAT

Try this and please let me know how it works out for you.
#41
Quote from: johannsebastianbach on May 14, 2015, 08:42:59 PM

Bad news  :-[



When I turned off FPSoverride out of the 10gb clips I only got 1 single pink frame. But at this point its more frustrating to find out that its really a "random" type of issue.

one more thing that I noticed: When you hit record you will either see a RED, YELLOW, or GREEN camera status icon. I noticed that the clips that end up with the pink frames(other than  high FPS) are clips that had either the YELLOW or RED status while recording.  Ironically you get YELLOW or RED due to HIGH FPS settings.
#42
Quote from: woron310 on May 07, 2015, 05:34:43 PM
Added support H.264.ini?  There was an assembly?
<H.264.ini not found>



This has been an issue with me since first day I got ML which was last year around March. In the video menu of ML, The H.264.ini has always displayed not found for me.
#43
Quote from: johannsebastianbach on May 06, 2015, 07:51:42 AM
I noticed, that I got extremely many (same kind of) bad frames, when used 67fps -override, so this could be a indication for it.

I shot for about five days over 350GB with different 113Nightlys, with bad frames almost every second/third MLV's. Now I have one last shooting day ahead this weekend and will test it. Thanks in advance, you will hear from me.

And by the way, for changing the fps in slow-motion. One could switch between NTSC 59,940fps and (in my case) continuous PAL 50.000fps very quickly trough MyMenu Settings.



I am going to keep that in mind for tomorrows shoot.

Sort of off-topic but I need to get an external viewfinder/monitor for my 5d. I work on a lot of CGI stuff and being in front of the computer isn't helping my eye condition out. I can't rely on my eyes and the tiny 5d screen anymore. So before I go and spend some of my moms money, can anyone recommend me a Monitor that obviously has HDMI supports MagicL  but also has dci high end port options because I'm going to probably upgrade to sf700 or RedEpic or C300MII. I don't want to buy a separate monitor If I can just buy one now that I can use later for other cameras.

IT MUST SUPPORT MAGIC LANTERN

So the real question is, Can I get any monitor as long as it has HDMI support? I'm looking at the Atomos Shogun, Video Devices PIX-E7, Odyssey 7Q 4K, and DP7-PRO OLED

ALSO.. I know that some of these monitors also are recorders but I just need a monitor not necessarily looking for recording feature.
#44
UPDATE****

Today I had to do a shoot for baptism at the the river and it was that very beautiful sunny California weather that I'm so use to. Any who, I decided to downgrade to the latest 113(4/27/15 this morning) and try to tackle the issue with this pink/glitchy frame problem. I think I may have found the problem.

I always set my 5dm3 to 1080-30fps and in ML override fps to 23.976. This has been my personal settings and have always worked fine with no issues. The reason behind this method is because I do some shoots that require 30fps for tv and its easier to switch between 30 and 24 In ML instead of going into the canon menu everytime. Whenever I need 30 I turn off override and whenever I need 24 I turn in on simple as that.

Well Apparently FORME this has been the cause of the pink glitch frames. It just kinda came across my mind and I decided to test it out right what the heck why not.

I recorded 3 min with CANON 30FPS with override ON to 24fps            and              3 min with 3 CANON 24fps with NO fps override.

As you may already have assumed,  the one with override ON came out with pink glitching frames AND the one with no ovveride came out all 4320 Frames came out clean. I did the same test again and got same results. So I now have decided to keep the 113 and not use override in ML and just take an extra second or two and make the necessary changes in the CANON menu.

Well this was my personal experience. If this was helpful to ya I'm glad if not  sorry.

Please try this out and see if you get the same results.

THANKS FOR READING!
#45
Hey johannsebastianbach,

Thanks for sharing your experience It helps others to see my point.

One of the major problems with this frame issue is that you can shoot a long video and as you cut and edit it ITS very possible that you can miss the pink frames because they are like 1 or 2 frames out of hundreds maybe thousands of frames depending on the length of your video. They are spread out so you have to go frame by frame to locate them and delete them.

In one instance I shot and edited an 8 min video. After finishing and rendering the video and getting ready to upload to internet I watched it and noticed the pink frames and I had to delete the rendered file and re-work on the project again.

So if some of you haven't already I would recommend that you go back and slowly check the frames and make sure a pink frame didn't sneak up on you.

IF YOU ARE USING ML FOR SERIOUS PROJECTS*(JOBS)
I highly recommend using 1.2.3 because it is more stable(reliable). I understand that you might not get the same recording length results but at least you will get usable footage.
#46
Quote from: DeafEyeJedi on April 12, 2015, 07:17:29 AM
Instead of formatting as exFAT?

IMHO, I feel more confident when shooting in 113 versus 123* only because I like to be able to squeeze every ounce of speed as much as possible and I also don't really need the clean HDMI out nor the F8 autofocus fix....

*Unless I'm using it on paid gig when field monitors are required.

That's JM2C!


Yeah I understand trust me I know its pretty ironic since everyone says "1.1.3 is more stable", but what can I say this is my personal experience and I even provided some proof of it.

#47
Quote from: unfilmde on April 11, 2015, 07:58:47 PM
"Ok AL3X, I again did a few tests and had same issues.
"

I just watched the video.  Boy those pink flashes are very reminiscent of digital dropout you used to get on digital video tape.  Is it possible the write speed of the card is not fast enough?  Have you low level reformatted the card so it is not fragmented?  I'm curious if the card is fragmented, could it be trying to write to contiguous space and it causes dropout.


Well I'm no expert and can't really be sure what the cause is but I don't think its the card because I have 3 of them and all 3 get the same results. I have 2x 32gb LEXAR 1066X UDMA7 65 and 1 128gb LEXAR 1066x

Also One more thing that makes me think its not the cards is that just last night I upgraded to 1.2.3 and used the latest 1.2.3 build and recorded bunch of diff FRAMERATES and resulutions up to 2.5k wide cinematic ratio and NOT 1 single drop of frame or pink frames or glitch effect(did not test on all cards, assuming would be same results)

Again this is my own personal experience and thoghts that 1.2.3 is more stable and reliable.

But I'd like to get more of your opinion on the defrag situation which I don't think I have ever done. I always format cards IN THE CAMERA when I'm done offloading the files.
#48
AL3X: I've ran some tests with MLV for about 45 minutes, trying to push it beyond limits (30/60fps, 3.5K, magic zoom or focus peaking while recording), but could not get a single pink frame or crash.

Tried on both 1.2.3 and 1.1.3.

Therefore, without proper feedback from those experiencing the issue, there's nothing I can do. I'm looking at you, itsDPmikey, bayard1965, swinxx, dubzeebass, and others who may have reported it in other threads.


Ok AL3X, I again did a few tests and had same issues.


23.976FPS
1920X1080 mlv
EVERYTHING normal default settings.
#49
H264.ini not found


How is it that no one has figured this out or anyone from ML responded back with a resolution?
#50
AL3X what exactly are your settings to achieve 3k?