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

#176
General Chat / Re: Any new updates yet?
June 27, 2013, 11:32:55 PM
Quote from: g3gg0 on June 27, 2013, 10:45:26 PM
it would be helpful of course.
but especially since the file format is not considered stable, not many groups are developing stuff for it.
this might change as soon the "final" format has figured out.
there are a lot of theories how to design the container format so that writing data is most performant.
I can understand that. I hope the individual who uploaded the vimeo video I posted above releases what he claims he's come up with. He came here, showed it working and has since uploaded a 2nd video showing it working and disappeared. smh
#177
General Chat / Re: Any new updates yet?
June 27, 2013, 10:41:06 PM
Quote from: g3gg0 on June 27, 2013, 10:38:30 PM
the same restrictions apply to raw video as to raw photos.
those are not meant for direct viewing and require post processing.

so i dont think someone is going to make a file reader for vlc.
but who knows....

I guess I'm the only one who believes it would be nice to view shots before editing...
Would be cool to find the keepers and throw aways without having to pull them all into premiere/AE...

by the way, I can view raw photos without photoshop/lightroom
#178
General Chat / Any new updates yet?
June 27, 2013, 10:29:23 PM
Has anyone come up with a software or some way to playback the native RAW files from these cameras yet?
Something like this vimeo video shows(or something in like a VLC player)
https://vimeo.com/67542994#comment_9394519


Also, has anyone come up with a solution to use native raw files in adobe(premiere/after effects) OTHER than Ginger HDR plug in?
#179
Quote from: noisyboy on June 26, 2013, 09:16:13 PM
Ha! No way :) Jonathan sent me the Beta profile this morning! Can't wait to give it a whirl - those guys always know how to impress me. Shame I can't use the damn thing yet :(

think they'd allow you to post the profile?
#180
Quote from: Audionut on June 27, 2013, 07:04:35 AM
In my limited testing, the pattern noise in video mode is not fixed, http://www.magiclantern.fm/forum/index.php?topic=5609.msg55352#msg55352

This will make it all but impossible to remove.
are you talking about the vertical black bars? Im getting those too using ginger. I stopped using it. when my trial expires, don't think I'll spend 100 bucks on it without that fix
#181
Quote from: rebelj12a on June 27, 2013, 03:50:29 AM
Build 6dfbee9 June 25th - Canon 5d Mark III - Komputerbay 1000x CF
Im getting an error with raw recording.

Happens somewhat intermittently, did not happen on first test of recording, however 2 subsequent upload times it happened.

The error was a footer mismatch. 2 extra files appeared the first time besides the raw file.

M26-1932.R00
M26-1932.R01

Removed the card uploaded the raw file, unreadable by raw2dng.

Error Message
This ain't a lv_rec RAW file

Deleted files from CF card and tried again. Same error however with this raw recording only .R00 showed up.

Figured I'd dump the error. Ill try again in a bit.

I believe those are from 4gb file splits. when you record to a fat32 formatted card, a file can't be larger than 4gb, so the camera automatically splits them. The r01/r02... are the seperate parts of the same raw file. Try formatting your card ExFat and recording a huge file and see if you still get those files.
#182
The highlights hold most of the information. So with that said, I use the histogram and expose as far to the right as possible without clipping.
#183
Quote from: sergiocamara93 on June 24, 2013, 05:09:21 AM


As I have previously stated in the forum, I was truly excited when the RAW hack appeared since it opened a new world of possibilities for my 5D Mark III. We shot this music video a couple weeks ago with the 25th May Build. I've found the hack to be incredibly reliable and I haven't lost a single file due to corruption or similar issues to the date.

We needed to monitor the video output so we shot in 2.20:1 which allowed me to feed the image through the USB to a Windows 7 laptop running EOSUtility while simultaneously recording continuous 24p. I also shot some 30p scenes. The slow motion shots in the end of the video were shot in 1920 (2.20:1 squeezed aspect ratio). The ISO employed through the shoot goes from 100 to 6400 (last 2 scenes, obviously denoised in postproduction).

The cards I used were two Transcend 64gb 1000x cards (not the fastest but they never let me down and they handle 1080p RAW quite well). I had to offload one card per shooting day (a total of two shooting days) but the cards read fast so it wasn't a problem.

The post workflow I chose was quite a nightmare but I decided to cope with it to get the ultimate image quality. I used RAWMagic to convert the .RAW files to CinemaDNG Files. At the time Driftwood hadn't published yet the Resolve workaround for the pink fringing so I imported all the frames (almost 83.000) to Lightroom and output them to 16bits TIFFs. Then I imported those into Resolve where the final grading was performed. Since the Lightroom processing took over a day (in a quite powerful desktop computer), I did quick Cineform proxies with RAWmanizer which I used for the offline edit. In the end, I didn't have to wait per se, I just used some more batch-processing :) Now, let's talk about the hideous roundtrip. I can't understand how Resolve can't match by itself files with the same name and the same number of frames. I mean, at least it could try. I had to force-conform each file in the project which took "just" 3 hours (1 hour per minute of final video edit approx.).

But, when the files are in Resolve and you see the RAW information... all the pain is gone. I LOVE the format, I couldn't be happier with the results and the image quality. I'll certainly be using it A LOT in the future. It's really hard to go back to H.264, all my shots seems out of focus now!!!

I wanted to share with you the video, I'd love to hear any comments about it! Of course, thanks again to all the developers and the wonderful ML Community. This video couldn't exist without you, guys.

If you had shot any bigger than 2.2:1, you wouldn't be able to monitor through eosutility?
So if you wanted to shoot in 2.35:1 or 16x9 and you hooked it up to usb, the image would no longer show in EOS utility?
#184
It slowed down for me on the newest build.
I don't have the option to have the preview set to 'HaCKed'
The "preview option is no longer there.
FPS over ride set to 23.976
I got over 10 seconds with the 3 files you posted(258 frames)
with the newest build that Lourenco posted(last commit: 363a968), I'm only getting 202 frames.
#185
Quote from: xNiNELiVES on June 22, 2013, 04:46:44 AM
You never started and tried it in video mode. Just a guess...

If not I really feel like you have an old version of ML.  I really do. Look at the link I posted a couple posts ago. The videos are good tutorials.
I meant to say that I started in video mode NOT photo mode.

I have the newest version of ML, with Alex's new findings..
I update it almost every day.
#186
Quote from: xNiNELiVES on June 22, 2013, 04:31:21 AM
I'm using a 6d, I think you should boot in video mode and hit the don't touch me button in video mode. Starting in photo mode, I think it is not necessary.

http://www.magiclantern.fm/forum/index.php?topic=6099.0 some good guides are poster here on this page.
tried it again starting in photo mode
hit the do not click me the tried to hurry and hit record. also tried hitting record then going into menu and hitting the do not click me

each time I got 'err 70' on the top lcd and camera moves weird then tells me to take out battery

don't think I'll be trying that again.
#187
Quote from: xNiNELiVES on June 22, 2013, 04:23:38 AM
You should probably reinstall ML. You may have acquired an incorrect version for your 5D3. I mean you are trying to record raw video right? Maybe it disables h264 video. Look in the tutorial section of this forum to see proper instructions.
I can record raw video fine. I can also record the h264 video when I disable raw. But when hitting the don't click button and then switch from photo to video mode, nothing records.
Maybe it just works differently on the 5d3. You're using a 60/6d, right?
#188
Quote from: xNiNELiVES on June 22, 2013, 04:02:24 AM
That's what it's supposed to do. It's supposed to cut CPU utilization which therefore allows a higher write speed.
After going to video mode I hit record. Nothing recorded to camera
#189
when in crop mode(hitting the magnifying glass)
I want to do a 180 degree shutter, but 1/48 and 1/47 is not available. The closest options are 1/45 & 1/55 but the 1/45 option is in red, the other in green. What do you all select?
#190
Quote from: teo770 on June 22, 2013, 02:55:17 AM
The "procedure" is:

- Turn cam on in PHOTO mode
- load raw_rec.mo
- in Debug menu, click "Don't click me"
- switch LV to MOVIE mode

then record.

On Canon 6D, I have recorded 8.30 minutes (22GB) @1600x640 on a Sandisk Extreme PRO 32GB (95MB/s) card formated Exfat.

Im on a 5d3, after clicking 'dont click me' and flipping the switch for movie mode, nothing happens. No matter what I do, I can't get any screen to come up
#191
Quote from: noisyboy on June 22, 2013, 02:06:48 AM
Interesting developments over in the 6D Dev thread!

teo77 has made a great discovery that formatting to exfat dramatically increases recording times. Basically I was banging my head against a wall all day, wondering why he was getting 5:05 mins @ 1600x640 and I was getting 02:15 with latest hack. Anyway - he then figured that formatting his Sandisk Extreme Pro 95MB/s to exfat (4096 clusters), combined with latest module and don't click me from 02:15 mins all the way up to SEVEN MINUTES! If anyone else can try this out and share your results it could help :)

A1ex - do you think this is a problem caused by the files being split @ 4gb?
What does dont click me do?
He clicks that AFTER he's started recording for 2 minutes(while still recording)?
#192
Quote from: crazyrunner33 on June 21, 2013, 04:28:05 AM
Great job, I was able to hit 2560x1024 for over 1000 frames and 2880x1154 for around 130 frames.  After a little bit I started getting the "nothing saved, card maybe full" error.
I got that error as well. but I've also gotten it before this newest hack
#193
Question, I seem to have a problem with my CF not wanting to record(camera reporting card may be full, when it's really only half full). So, I have to format the card to get it to work. Im now using ExFat to format the card. Is the only way to format with ExFat, to hook up to my mac?
#194
I figured it out.
SHIT Alex, this is amazing!!!


Recording 2560x1090 on a Sandisk 600x CF 16GB card

with the june 16th build
72 frames with memory hack off, and preview set to auto
120 frames with memory hack on, and preview set to 'HaCKed'



With the new 3 files you posted, i;m getting
142 frames with memory hack off, and preview set to auto
258 frames with memory hack on, and preview set to 'HaCKed'

as you can see, it doubled!

With the CF that I have, I've always been able to get continuous 1920x1080, so I thought I'd go with something a little more demanding.

BRAVO!!!
#195
Quote from: a1ex on June 20, 2013, 06:51:56 PM
Straight from the card, not packaged:

autoexec.bin, raw_rec.mo and 5D3_113.sym
I replaced the files on my sd with these 3 files and the camera wont boot.
Should I be doing something additional?
#196
Probably not going to be much help as I don't know the names or anything.

Philip bloom uses a tool which is just about the shape and size of an external hard drive, you simply put your cf card in and it transfers all of the data directly onto the drive. You can then put it back into the cam and delete the media off the card. No computer needed. Check Philips site for further info. I could be wrong, but I think it's battery operated. No wires(except when charging
#197
Quote from: Sthirasukha on June 18, 2013, 12:29:38 AM
Sorry A1ex, I'm not sure to understand about the ISO:
Does it mean that ISO 800eq is the value at which I'm recording when the Canon is at ISO 640?
And why the ISO in Raw is different to the ISO in H.264?
I believe because the iso in normal canon software has BASE ISO's (100/200/400/800...) and then to get the intermediate values, the software PUSHES these iso's. But with ML it only keeps the base iso's instead of doing a software push.
Maybe Im completely wrong, but I read something about that here on the forums.
#198
Quote from: dlrpgmsvc on June 17, 2013, 11:55:20 PM
+1 for windows!
The mac version doesn't even exist. I honestly don't believe it works. No word since posting...
#199
Quote from: iaremrsir on June 17, 2013, 04:40:05 AM
In the GingerHDR plugin folder, there are two importer plugins: one for AE and one for PrP. Having the two in the same folder might cause AE to get confused, because, if I'm not mistaken, AE can use PrP importer plugins as well. Also, did you install the plugins to the respective program folders, or did you install it to Adobe\Plug-ins\Common\CSx\MediaCore\ ? I think the dev mentioned somewhere, that having the plugins there could cause problems.

they were all in the plug ins common folder as you've listed.
I had to move two files
GingerWrapper-PRM-mac64
and another one that looked like the one I just listed but had AE in it as well. When I did that it worked!
When I left those two files in both folders I got a warning stating that they were on my system twice.
How do I move them both to the AE folder, but still leave them so that Premiere may use them?
#200
Another issue I'm having. When bring my raw files directly into premiere, Im getting the vertical black bars. The other software has fixed this issue, do you plan on making a fix for this?

I've downloaded the demo, it expires in 30 days, right?
If so, will I no longer be able to import these RAW files into premiere at all?
$100 seems a bit steep for a tool to simply import files into premiere.