Messages

BUG: 1.7.0
The 12th frame of the video being exported drops on 1.7.0. I tried deleting the settings file and it does not work. Reverting back to 1.6.1 corrects the issue and I can confirm there is a non-blank frame in the position. I tried deleting the file again after switching versions and it is still skipping the 12th frame on every different video I export.

Going to try 1.6.5 and see how that works since it seems like many have used it and liked it. The 1.6.1 has just been so rock solid for me!

dude how has no one commented on this? that was awesome!

do you notice a huge different with the IR vs just going black and white? any link to your conversion?

LMAO!

@Steven

But seriously, try shooting h.264 as flat/cinestyle (there is a picture style available for download here: http://www.technicolor.com/en/solutions-services/cinestyle-download/cinestyle-faq), basically it's these camera style settings...

Sharpness: 0
Contrast: -4
Saturation: -2
Color Tone: 0
ISO: a multiple of 160

The flat picture style will get your h.264 footage out of the camera looking as close as possible to raw. Then apply Visionlog or Cinelog LUT in post to both as a starting point for color grading.

QFE! This is how I do it. Also helps to use a higher quality export h264 codec than the standard ones like MainConcept (part of premiere). I put the vision log 64bit LUT on the upstream, setting the cinemaDNGs to BMDFilm and then using the rec 709 blackmagic cinema camera LUT on the downslope. If you shot your original material well, it will come out quite nicely.

In beta 6, I still cannot scroll through the files without the app crashing

@evanbuzzell
re-check: what's the framerate for this videos? please write some video/audio timecode pairs, if theres maybe a correlation.. is the audiofile playing fine in any audio/mediaplayer?

23.976 on all the clips.
Video length is 02:18:10, audio is 02:17:38400
V: 01:12:01, A: 01:11:38400
V: 01:43:07, A: 01:42:19200
V: 02:13:11, A: 02:13:00000

Different day, More Recent than most:
V: 00:23:06, A: 23:09600
V: 02:12:18, A: 02:12:00000
V: 03:13:07, A: 03:12:09600
V: 00:46:12, A: 46:28800

Most recent build:
V:00:21:16, A: 21:28800
V: 00:39:07, A: 39:19200
V: 05:43:03, A: 4:25:28800
V: 02:08:05, A: 02:07:38400

older one
V: 00:28:23, A: 28:19200
V: 00:56:17, A: 57:00000
V: 00:51:23, A: 51:19200

The audiofile plays fine for the most part, it is the sync that is the issue. 5d2 is the camera I'm using apr 23, 14

mates, thank you for testing and response.

* RAW-Error is fixed, will be in beta4, found it days ago.
* Resolve-Sync - i tried to realize it, it seems to work. @evanbuzzell please check, if both mediafiles have the same timecode - this was my first intention - the second one was, to change the path/files behaviour into the regular path-as-mediafile. i didnt found the key for that, i need more samples, i said it before..
* @RedRocks. ok. in beta4 there will be a proxy-jpeg-output, as i stated, they are not color accurate, have a wrong gamma, but for simple cutting it should do. and: ffmpeg has implemented mlv, this could be your way (maybe mine too for other codecs).
* ah, btw. do you use mercury-playback on gpu? my yellow marked sequences play quite fluid, even if i use gpu-accelerated effects.
* clearly saying, my intention was/is to get the user as fast as possible editing his stuff
* @piloui "sometimes destinationpath not working". only under raw or with mlv as well?

regards chmee

So the timecode for the audio and the video are different. I could have sworn that the audio files were synced in Premiere just a few days ago and now I'm not seeing any audio sync in premiere or resolve. This just made this project a million times harder aye! I've tried changing the file names to something different when exporting, any other ideas?

audio not syncing in resolve as well

had a crash with a large amount of files being imported.

The debug doesn't say much, just that where it stops. It can't seem to load a file that is 11gb. It just doesnt do anything when I try to add it to the batch on its own.

**Update* But it loaded a 5 file one just fine. I wonder if that file is corrupt now that I'm looking

I'm on 1.5.0 beta3 btw

magiclantern-Nightly.2014Apr13.5d2212

Great record times, but at 10 minutes on 24fps I hit a frame skip which caused almost like a debug menu to show up, and stay there. This also happened after about 5 minutes at 30fps. Here are the logs
ML ASSERT:
hdr->blockSize >= (sizeof(mlv_vidf_hdr_t) + hdr->frameSpace + frame_size)
at mlv_rec.c:2002 (process_frame), task LiveViewMgr
lv:1 mode:3


Magic Lantern version : Nightly.2014Apr13.5D2212
Mercurial changeset   : fb558c7ded91 (unified) tip
Built on 2014-04-12 22:10:29 UTC by [email protected].
Free Memory  : 122K + 3966K


ML ASSERT:
hdr->blockSize >= (sizeof(mlv_vidf_hdr_t) + hdr->frameSpace + frame_size)
at mlv_rec.c:2002 (process_frame), task LiveViewMgr
lv:1 mode:3


Magic Lantern version : Nightly.2014Apr13.5D2212
Mercurial changeset   : fb558c7ded91 (unified) tip
Built on 2014-04-12 22:10:29 UTC by [email protected].
Free Memory  : 122K + 3968K

Had issues previewing on camera for some files, we will see if it remains a problem once they are extracted

Looks awesome! What was your HDR Raw workflow like?