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

#1
Tragic Lantern / Re: Tragic Lantern for EOS M
September 23, 2013, 08:58:19 PM
Quote from: gary2013 on September 22, 2013, 05:30:36 PM
I just got a remote control for the M. It's the RC-6 model from a third party. It works good at even 16 feet away for taking pics, BUT, I can't get it to start and atop the movie mode for videos. I have read in forums that it does also work for video,even the third party models, but I cannot see how. It always takes a pic in movie mode and a message pops up saying "switch to movie mode, something went wrong". But, it then starts recording video. Odd. BUT, I then cannot get the remote to stop the movie recording. It just keeps taking pics with each push of the button on the remote.

Is this something Magic Lantern can do to make it work for video start and stop without taking pics? Or, is there something I am doing wrong? I am setting the Self-Timer: 1o secs/remote to get the remote to work. I see no other way to do this for video start/stop.

Gary

If you read the manual, you will see if you set the remote to "2", and set the self-timer on the camera to remote (as you did), and set the camera to video, the remote will start and stop video instantly when  you press the remote button. This has absolutely nothing to do with ML.
#2
Tragic Lantern / Re: Tragic Lantern for EOS M
August 29, 2013, 08:19:06 PM
Just another vote for live audio monitoring (and audio meter fix). Meanwhile I am enjoying playing with RAW shooting.
#3
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 06:20:10 PM
Quote from: gary2013 on August 22, 2013, 06:15:45 PM
I have been creating a new folder for each Raw file. Then PDR on each camera Raw file. Then raw2dng. Then Photoshop CC, open the first file of the sequence and all of them load. Select All files and do a quick grade. Then Save All files to Tiff. Then import the Tiff sequence into Premiere Pro CC to edit. Add Neat Video to clear up all the noise from the Raw sensor. Change the scale to 166% on height. Sheesh. Can someone make one utility that does that all in one step to the camera Raw files and even batch a group of camera Raw's? And the highest full quality Tiffs.

Gary

My workflow is the same, except instead of Photoshop CC I use Lightroom 5 and instead of Premier Pro CC I use Vegas Pro and I do not need to stretch, since I shoot crop mode 720p. The steps that are most cumbersome are the placing of RAWs in folders (21 clips = 21 folders) and the conversion from dng to tiff in Lightroom for me.
#4
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 05:37:22 PM
Quote from: maxotics on August 22, 2013, 05:16:58 PM
I'm using the GUI version, which looks like this.  I started using it because I had that problem in RAWanizer (half-size TIFFs).  My guess is there is a way to tell RAWanizer to make a full-size TIFF through DCraw "Use Cusotm DNG to TIFF".  One of us needs to go figure those settings out ;)



That's what mine looks like too (not surprisingly), and the 'HQ Interpolation' hints at the lossy compression. I do not see the DCraw on my computer, or any configuration other than the basic one. It is a big pain using Lightroom to simply make the conversion from .dng's to Tiff's, so it would be nice if this RAWDrop program would not assume what we want and allow us to choose.
#5
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 03:45:12 PM
@maxotics: I agree with you completely that shooting technique trumps RAW versus compressed out of camera. One more issue: RAWdrop produces Tiff files that are half the size of those produced by Lightroom when I tell Lightroom not to compress when going from .dng's to Tiff's. So it looks like the Tiff files produced by RAWdrop are compressed. If this is lossy compression, then it seems to me again the purpose of RAW is compromised. Do you know what RAWdrop is doing in terms of the conversion?
#6
Tragic Lantern / Re: Tragic Lantern for EOS M
August 20, 2013, 06:34:23 PM
Quote from: maxotics on August 20, 2013, 05:04:49 PM
@markr041

I have a 50D which shoots amazing RAW video, was curious to see just how much resolution I could get from the EOS-M, if I wanted to match on that basis (though at a lower FPS).  I can imagine certain types of shots where this high resolution, at a lower FPS, might be useful.  I am also curious to try 16fps with sound later.  What do you think are the best settings, aspect and resolution, for both 24p and 16p?  Also, I meant "continuous" as in the camera won't lose frames or plain shut-down or worse, corrupt the card.


@All

My silly tests have had one benefit which should hopefully provide better footage in the future.  Because I couldn't get the right-size TIFFs from RAWanizer, I was forced into a higher quality RAW workflow which I hope to use from now on, instead of straight to cineform.

RAW --> RAW2DNG --> RAWSpot (to TIFFS) then ffmpeg:

16fps:

ffmpeg -r 16 -i 000%3d.tiff -c:v libx264 -crf 10 -pix_fmt yuv420p out.mp4

24fps:

ffmpeg -r 16 -i 000%3d.tiff -c:v libx264 -crf 10 -pix_fmt yuv420p out.mp4

I then take the mp4 and put into Vegas Studio.  If you have better ffmpeg setting PLEASE let me know.

1. I don't understand how the final product has "higher resolution" when the vertical resolution is less than HD standards. What is the benefit of having higher horizontal resolution and lower vertical resolution to get an odd aspect ratio? What does the final editor do with the strange aspect ratio? You can set the ML not to skip frames. ML tells you how many seconds you can shoot at the given resolution and frame rate, so you do not have to shoot until the thing breaks down. At real 720P resolution at 24fps you can shoot for over 2000 frames before it stops, which is plenty. You then can make a nice 720P video at a reasonable frame rate that people might want to watch.

2. You do NOT have to convert the TIFFS to any video like MP4  or Cineform before using Vegas Pro. Your workflow makes no sense (if I understand it). Vegas Pro will read TIFFS natively as an image sequence. By converting TIFFS to MP4 (or Cineform) before you use Vegas you are defeating the whole purpose of RAW - to avoid multiple compression and retain all the info from the sensor.  Why not RAW -> TIFFS (all digital, all info)->Vegas for grading, sharpening and making the final 24fps 720p video. That is what I do (which merely means I know this works).
#7
Tragic Lantern / Re: Tragic Lantern for EOS M
August 20, 2013, 02:58:16 PM
Quote from: maxotics on August 20, 2013, 05:23:51 AM
I do a quick test, comparing video produced from Magic Lantern's maximum resolution on the EOS-M at 24 FPS, 1472 x 592 (continuous recording) with the 1728 x 684 resolution possible at 12 FPS.  I think there may also be a bug (or it's on purpose for scaling?) in RAWanizer.  It didn't create the TIFFs at the higher resolution.

I created the TIFFs manually using RAW2DNG, then RAWDrop to TIFF and ffmpeg to high quality MP4, I hope ;)

Anyway, as you can see, you do get better quality, and less moire, at the higher resolution, though lower frame rate.


Your posts are useful, but I do not understand why you shoot at the resolutions you chose - they are not on the horizontal dimension HD. Why not shoot at 1280 x 720? When you process your clips they are less than HD.

Why are you not shooting in crop mode, which has far less aliasing and moire, at 720P? The camera will shoot for at least a couple of minutes in 720p in that mode (24fps) and it is real HD. You clips are seconds, so "continuous" capability seems irrelevant (as it is for most video shooting).
#8
Tragic Lantern / Re: Tragic Lantern for EOS M
August 17, 2013, 04:59:27 AM
@maxotics: Glad to hear your EOS M is back up, and that the fix was simple. I agree, there is more to videos than resolution, and color and dynamic range should be better from RAW, and that is important.
#9
Tragic Lantern / Re: Tragic Lantern for EOS M
August 17, 2013, 12:50:58 AM
Well, for example, the popular intermediate codec ProRes, and used in the BlackMagic cameras for example, has a bitrate in the 100's (224Mbps). So, 60Mbps seems low, and thus something must be sacrificed. The Cineform avi still has 4:2:2 sampling and presumably keeps the RAW dynamic range, so it has advantages over the AVC from the camera,  but subjecting the video to double compression (Cineform and then the NLE), given the Cineform bitrate, may not be ideal. I certainly don't know. And the RAW to TIFF conversions are a big hassle.
#10
Tragic Lantern / Re: Tragic Lantern for EOS M
August 16, 2013, 10:47:39 PM
Quote from: maxotics on August 16, 2013, 08:17:37 PM
My steps with EOS-M so far
1. Follow steps in other posts to get it ML to work with Firmware 2.02 (if that's what you have)
2. Boot camera, load ML, load modules (set to autoload), set to RAW, resolution, etc., in ML.
3. Press MENU, take some RAW video.  I wouldn't shoot a lot your first try. 
4. Copy RAW file over to computer
5. Load PinkDotRemover (THANK YOU AUTHOR OF THAT).  You'll need Java installed.
6. Make a copy of your RAW file if important (PinkDotRemover) modifies original.
7. Drag copy or original to PinkDotRemove, pick camera, and run.  NOTE: You won't see a status message, but it should finish in a minute or two. It will say so.
8. Open RAWanizer, select RAW file
9.  Pick Cineform and have it create video output

That's my easy workflow at moment.   I use that for 50D too (except for PinkDotRemover, which isn't necessary for that camera).

PinkDotRemover does have a moving green status bar as it proceeds, with reports of number of RAW files processed as well.

This workflow using an intermediate lossy codec (Cineform) may not provide the best results, compared with taking the .pngs from the RAW and converting them losslessly to tiffs and working with them in an NLE. In any case, I could not find a way to change the characteristics of the Cineform file (bitrate) in RAWanizer. The Cineform bitrate I got was around 60Mbps, a bitrate I can get using ML for the AVC video produced by the camera (EOS M) without RAW, and AVC uses more sophisticated compression.
#11
Tragic Lantern / Re: Tragic Lantern for EOS M
August 16, 2013, 02:24:37 AM
What was your workflow? What resolution? what frame rate? crop mode?

You can remove the red dots quickly and easily with a little software program:

http://dl.dropbox.com/s/m0bxzd23p4zow8o/PinkDotRemover_2013_08_08.zip

It works directly on the RAW files and you can do all of them at once (in batch).

See my video from RAW: https://vimeo.com/72310879

No dots.
#12
Tragic Lantern / Re: Tragic Lantern for EOS M
August 14, 2013, 04:13:05 AM
I made a video from shooting RAW at 1280 x 720, 24 fps, in crop mode. Using a Sandisk Extreme sd card, I was getting about 35 MBps and could shoot, according to the camera, over 2400 frames before stopping.



My workflow:

Dot-removed the RAW clips.
Obtained the .dng frames from the dot-removed RAW files.
Used Lightroom 5 to convert the .dng files to uncompressed .tiff files using default settings.
Used Vegas Pro 11 to edit the string of .tiff files to create the 720p video at 24p, using AVC compression and light sharpening using unsharp mask.
#13
Tragic Lantern / Re: Tragic Lantern for EOS M
August 10, 2013, 05:26:41 AM
Help: How do I set WB back to AUTO in ML. I set the Kelvin temperature and can change that but I no longer see AUTO as a choice. When I turn off the camera and do not boot into ML, I cannot change WB. The Wiki says nothing about getting back to AUTO.

I had to reset all settings to default in the Canon menu to get back WB control. Is this normal?
#14
Tragic Lantern / Re: Tragic Lantern for EOS M
August 08, 2013, 04:57:43 PM
Quote from: feureau on August 08, 2013, 09:15:44 AM
That is awesome. What make/model card are you using? :3

Sandisk Extreme 32GB (class 10, UH-1). Claims 50 MB per second write speed.
#15
Tragic Lantern / Re: Tragic Lantern for EOS M
August 08, 2013, 07:04:53 AM
https://vimeo.com/71944234

This is one sequence shot in RAW mode with the EOS M. Then, the single RAW file (one take) was split into its 800 frames as 800 sequentially numbered .DNG files. The .DNG files were read into Adobe Lightroom, where white balance was set (I chose the daylight setting). I also lowered ev by one third and then all 800 files were outputted as .Tif files. The set of 800 Tiff files (really frames) were read into Sony Vegas Pro and then rendered out as an MP4 file with a bitrate of 40Mbps at 29.970. The original frame rate was 29.970, shot at 720p in 2:35 aspect ratio (1280x544) - and that is what you see. The sequence bitrate in the camera was about 35 megabytes per second and continuous shooting (I could have shot until the file size limit). The original RAW file was almost 1 Gigabyte for this 25-second sequence shot in extremely bright sun.
#16
Tragic Lantern / Re: Tragic Lantern for EOS M
August 07, 2013, 10:11:09 PM
Quote from: markr041 on August 07, 2013, 02:30:38 AM
OK, I installed ML no problem.

I turned on GlobalView: Live View. Set zebras on and histogram on. But I do not see them on the screen.

I turned on REC/Standby for video: I do not see them on the screen. Again, no ML overlays at all.

What is working (for me):

In video, I can up the bitrate - got it up to 63 Mbps.

I got the log working. But, no report of ISO (just = 0). It does report time, shutter speed, focus distance (I moved that around to check), and aperture. Why no ISO?

There is no audio in video mode. Will this be fixed?

I understand there are limitations, but let's fix the overlay issue (which may be me, but I can follow instructions and they should show as far as I can tell).

I of course appreciate very much the work that went into this and the supposed feature set, so these are not complaints, just questions.

You're an idiot, Markr041:

1. All you needed to do was press the 'Display' button to get rid of the Canon icons (as the ML instructions say in the camera!) and everything shows up - histogram, zebras, STANDBY. and a lot of info on settings, even the name of the file.

2. Audio is disabled only when you add some features (Video hacks).
#17
Tragic Lantern / Re: Tragic Lantern for EOS M
August 07, 2013, 10:08:30 PM
Quote from: gamerblot on August 07, 2013, 08:26:07 PM
Zebras, focus peaking and Global Draw overlays are all working for me without need to do the on/off trick. I just need to do the on/off trick for shutter release type ML functions.

Thanks. All I needed to do was press the 'Display' button to get rid of the Canon icons (as the ML instructions say in the camera!) and everything shows up.
#18
Tragic Lantern / Re: Tragic Lantern for EOS M
August 07, 2013, 08:12:58 PM
Quote from: gamerblot on August 07, 2013, 07:49:55 PM
OK, I found that you don't have to invoke the Intervalometer first. All you have to do Update Firmware to load ML, once on, just hit Power On/Off quickly twice (once to turn off, once to turn on) within a second (if you take longer than a second, ML is unloaded again) and Intervalomater and Auto Bracketing (and I am sure other ML features) work. This workaround is probably simulating what the bootflag would have done in the first place but for all those like me that got our EOS-M with 2.02 and not an upgrade from 1.06 with a ML bootflag previously, this is a workaround for now.

Hope %1 can figure out the bootflag for 2.02 firmware users soon

With my 2.02 firmware EOS-M and ML I can't get zebras to work or focus peaking or anything to show up overlaid on the screen - does this also require the on-off trick, or do you have those working? I do get the menus and higher bitrate video and other features working , so my install is fine.
#19
Tragic Lantern / Re: Tragic Lantern for EOS M
August 07, 2013, 02:30:38 AM
OK, I installed ML no problem.

I turned on GlobalView: Live View. Set zebras on and histogram on. But I do not see them on the screen.

I turned on REC/Standby for video: I do not see them on the screen. Again, no ML overlays at all.

What is working (for me):

In video, I can up the bitrate - got it up to 63 Mbps.

I got the log working. But, no report of ISO (just = 0). It does report time, shutter speed, focus distance (I moved that around to check), and aperture. Why no ISO?

There is no audio in video mode. Will this be fixed?

I understand there are limitations, but let's fix the overlay issue (which may be me, but I can follow instructions and they should show as far as I can tell).

I of course appreciate very much the work that went into this and the supposed feature set, so these are not complaints, just questions.