Quote from: a1ex on May 22, 2013, 07:00:45 AMCool - I'll get to work finding the edmac stubs now.
The 40D has lv_save_raw inside, so it's likely to work.
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 MenuQuote from: a1ex on May 22, 2013, 07:00:45 AMCool - I'll get to work finding the edmac stubs now.
The 40D has lv_save_raw inside, so it's likely to work.
Quote from: Andy600 on May 21, 2013, 06:32:18 PMI pushed the stubs for the 50d yesterday, someone try it out
It looks like raw_rec hasn't yet been ported, only silent pic bursts?
Quote from: Andy600 on May 20, 2013, 09:01:25 PMFrom my testing with the 5d2 it can only do 1880x840 so the 50d should cap out somewhere around this as well (slow CF interface).
The sensor is read at a specific size from what I understand. A1ex mentioned earlier in this thread that the 50d is 1592x1062 in 1x mode and 1992x1080 in crop mode so 1080p should be doable in crop mode only. The 1x mode will need to be upscaled.
I think this is probably on par with the 5d MkII for write speed but as the files will be smaller it might get a little extra push in the fps dept etc but not much.
It has the same processors as the 5d MkII and likely the same CF interface. A fast UDMA 7 card should let this run at full transfer speed in the same way as a UHS-I does for SD to it's maximum but we'll see.
Not sure about the moire being any less.
It would be great if this had 720p H.264 enabled some time as a fallback. I've seen some of the 50d footage at 24fps 1080p (H.264). Not too bad. I think the 600d has the edge though slightly + audio which the 50d hasn't got ... not that any of this is relevant now
Quote from: brianymarsh on May 15, 2013, 10:43:33 PMwat, i have the same card and I can only do about 300 frames at that resolution before it starts dropping frames. Do you mean continuously as in no dropped frames?
I used the latest stable build of magic lantern and just copied the MODULES folder into the ML folder and replaced AUTOEXEC
I am getting consistent recording 1880x840 on the 5D MK2 (until file size limit) with a Lexar 32gb 1000x card.
Quote from: JohnBarlow on May 15, 2013, 06:54:13 PM
This got me thinking - what if the board from a 700D has a faster transfer rate and can be used in the 550D/600D etc OR what if a cable can be hooked up to an exterior device like a CF or SSD?
Quote from: bronson on May 15, 2013, 04:01:02 PMthis is about how good I can get too.. seems the cf interface is slower on the 5d2. 1880x720 can record infinitely (until file size limit).
Hi,
I tested my new fresh transcend 1000x 32Gb and i can't record raw video beyond 65mo/s.
I saw many people recorded full 1920x1080 with 5dM3, but with the last raw build, and with this card, I do 1880x840 max with dropped frames at 300.
Is there any record limitations with 5dM2 compared to 5dM3.
I know it's just an alpha and there's no official nightly build.
Does anybody has achieved better results ?
Quote from: g3gg0 on May 15, 2013, 11:25:04 AMchdk has a file manager gui i think, I remember using it back in my point & shoot days.
its time for a file manager module
who does it?
Quote from: a1ex on May 14, 2013, 05:08:17 PMI think a counter similar to how canon does it would be wise, does canon use the same image counter as images for movies, just with MVI instead of IMG? Maybe we could just affix RAW_ and use canon's naming convention (i think there's a property saying what number to use next).
What about DDhhmmss.RAW (day, hour, minute, second) ?
We are limited to 8 characters.
Quote from: Colemar on May 14, 2013, 02:10:13 AMthe filename says 5d2, of course it won't work on the 5d3.
on the 5DmkIII with that autoexec.bin the camera will not start up. When reverting to lorenco's autoexec.bin and using the modules you provided, the error messages appear. When reverting everything to lourenco's build, the camera functions properly but there is some image tearing. Just to make sure, the autoexec.bin and modules you kindly provided are for the mkIII ?
Quote from: Colemar on May 14, 2013, 01:45:36 AMuse the autoexec.bin in that zip.
coutts,
thank you for the post. unfortunately that was a small step backwards for me as now an error message is generated when attempting to load the module. I do not know how to attach things or I would include a .422 screenshot...
and
-Colemar
Quote from: 1% on May 13, 2013, 10:01:16 PMstart writing a raw compressor?
I think that means you picked a size that doesn't work. Lemme know all the ones that don't work and I'll take them out. We can try some different anamorphic ones.
Coutts made it for 5d2.. not sure where he put it.
Also these clips are useful for short stuff. How big is an average cutaway really? The 1280 will probably uprez to 1080p and the 960 will probably pull off 720P compared to the H264. I don't think you will all need 5d3s... just CF cameras unless something can be done to compress the frames to 1.5MB.
Quote from: bumkicho on May 13, 2013, 07:38:46 PMconfirmed happening on 5d2 for me during my testing.
Has anyone had an issue with either top third or bottom third tearing on a frame?
Quote from: aaphotog on May 13, 2013, 06:41:08 PMuse the linux version in terminal, dont' use the windows version
anyone got 'raw2dng' working while using a mac?
I am using a mac. downloaded the raw2dng.exe file posted in this thread.
Tried running raw2dng.exe in both 'wine' and 'crossover' and I can't seem to get this figured out.
Anyone successfully converting their files using a mac system?
Page created in 0.082 seconds with 14 queries.