Messages

Really love the gimbal. It is compact and easy to balance. It even worked connecting 600D to gimbal and use gimbal controls for av, tv, iso, video start/stop etc.

I used DNxHD to export from davinci. Handbrake encodes way better than davinci but it takes hours.

Concerning youtube I have a feeling that they re-encode videos to lower bitrate to save space if it does not get the view counts.

Hi KirbyLikes525,

appreciate your comments and glad you liked the video!

The gimbal is Weebill Lab.

Most of the gimbal movements were done intuitively as it the first time I'm using one. I watched quite a few youtube tutorials and tried to apply the information to the shooting. There is a big "pitfall" with a gimbal. Because it is so easy to move with it it is hard to stop moving and you end up with clips that have movements in all directions. Now you have to edit it to something meaningful.

Regarding youtube - you hit it right. It is actually the second version of the video that I did using handbrake and insane 60Mbps. It took several hours to upload. I did it because I did not like the quality davinci resolved produced with youtube output preset. Now comes the conspiracy part - right after upload the video looked great, but the following days it turned to what you see. Now I am confused and do not know what to think and how to work with youtube.

My summer camp footage made with 600D and tragic lantern.

I'm not a professional videographer filming only occasionally during vacations. This is my second fully edited video and first time ever using a gimbal.

Vignetting on some clips is not an artistic choice but a cheap variable ND filter that was found to be bad after the shooting.

I showed the rought cut at the closing of the camp and got overwhelming response from kids and parents. Thank you magic(tragic)lantern for that feeling!

Shot with:
- Canon 600D
- Tragic Lantern
- Tokina 11-16 F2.8 (IF) DX
- Sigma 28-70mm 1:2.8 EX DG
- Weebill lab gimbal

Soundtrack:
- Birds - Imagine Dragons
- Blue Jeans - Lana Del Rey - Vintage Reggae Café 

Having the same issue with 600d and latest nightly.
I thought it was only me who has this problem

The maximum speed of 600D is about 25MB/s. That's the bus interface limitation. You can test your card using the benchmark tool inside ML.
You can probably stretch some more seconds disabling Global Draw (using HacKeD preview on MLV menu) and disabling sound rec (use external recorder).

thanks for the benchmark tool tip!

I was under impression from this posts:
https://www.magiclantern.fm/forum/index.php?topic=15360.msg178287#msg178287
https://www.magiclantern.fm/forum/index.php?topic=15360.msg176951#msg176951
that 600D can do more then I'm getting now.

So what is the highest continuous resolution you get from 600D with 10bits?

Hi guys,

I can not get my 600d with san disk ultra 64GB 80MB/s exfat and latest experimental build to run continuously in 10 bit raw, 1280 @ 2:35 / 24fps mode with sound. Recording stops after 10-12 seconds.

Is there something special I should be aware of?

Thanks.

@honza123  - any info on your config?

I'm getting pretty bad frame skipping  at 1728x648 23.976 10 bit with sound.

Are there any other specific config settings to get it stable?

Finally tried the video on my tv - it works for video!
For audio there is a message, that "audio format is not supported"

P.S. Great features in the new version.

I'll try the mov on Thursday evening as I`m away from my tv a the moment.

Great news on multi thread and upscale - take your time as you are doing some great work.

Hi Andy,

Thank you for the reply.

So it is "only" incorrect working gamut that stands in the way of using MLVProducer with Cinelog?

Sorry if my questions sound silly, I just getting to know all the technology and terminology.

Hi Andy600

just bought the Cinelog package and trying to get all the options sorted.

I have the same question as @ruber - does Cinelog work with MLVProducer?
If yes - could you describe the common workflow?
if no - what are the reasons?

Group editing - great feature!

some questions:

- do you spawn ffmpeg instance per core to increase multicore usage when doing group renderings, or do any other multicore optimization?
- could you add the upscale option from different camera raw resolutions like 960x540 to 1920x1080?

Thanks,
xaled

Here is the link to the mov file that plays out on samsung tv:

http://www.filedropper.com/mvi1138

yes - all mov files from 600d original video function and high bitrate tragic lantern firmware are played with no issues at all at both 24 and 25 fps with sound.

Do you need a sample mov?

tried  new h.264 common profile - still not working on my Samsung tv

It is not more frames that give me the wrong feeling
It is the fact that my crappy five years old laptop without ssd etc provides a quarter of performance of the new laptop with all the goodies.
It just does not feel right to pay five times more after five years and get only four times the performance and that is not even real time.

Other issue is that the fps does not even vary much depending on h.264 profile.

It appears to me that there is some bottleneck that is not the processor.

What fps numbers do you get?

There is generally something wrong with win10.
With MLVProducer I`m getting:
- 3-4 fps H.264 encoding on my old Intel® Celeron® Processor SU2300 (1M Cache, 1.20 GHz) WIN7 laptop
- 14 FPS H.264 encoding on my new Intel® Core™ i7-4712HQ (6 MB Cache 3,3 GHz) WIN10 laptop

Great tool!

It includes everything that I wanted so far to work with mlv.

Few things I noticed that deserve to be fixed/enhanced.

- presets for hot pixel removal and corrections do not get picked after being copied from old to the new MLV Producer presets folder
- none of the h.264 renderings can be played out on my samsung TV. H.246 movs directly from my 600d camera play out without problem.
- During tryouts of h.264 renderings I pulled sd card out of reader slot and then after noticing that TV wont play it I put sd card back in to reader. Trying to rerender the mlv from the sd card using a different h.264 preset gave an error that the volume has changed. The error makes sense, but If I click ok on the notification the rendering continues for few seconds and then the same error notice pops up. Some volume error handling routine or maybe recovering from volume change would be great.
- Adding configurable strings for ffmpeg invocation presets would be nice as well.

General question to all MLV Producer users - what FPS do you get on h.264 renderings?
I`m having 14 FPS independent of h.264 preset on my new i7 laptop running win10 an it does not sound like a lot to me.

Thank you again for the great tool!

But why do gopro clips look sharper?
Gopro does not capture raw and the lens are not better than on eos

vote for mac!

now that - cold pixels and mlv_dump would be just great!

Had the same problems with the black dots on my 600d with TL versions. I just gave up on RAW back then as the tweaked TL H.264 version is fine for my use cases.

It would be great though if there is an answer to the issue.

Hi Odlan,

what firmware, configuration do you use on Raspberry PI?

Thanks,
xaled

@kopfsalatmedien

Just as I wanted to give esscable a call...

I mailed them on 15th and they repled, that it is decontinued.

I'll try to call them, may be if there will be a substential interest say 100 pieces, they would be interested.