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.

Messages - kontrakatze

Pages: 1 2 [3]
General Help Q&A / Global Draw items on display
« on: May 21, 2014, 08:18:36 AM »
I would like to use global draw in conjunction with mlv_raw, mlv_snd and the RAW histobar. But the display of soundlevels leaves no place for the histobar. As I don't need the audiolevel display (audio recording is just meant for syncing with an external recorder later on), is there a possibility to hide the leveldisplay to make place for the histobar?

Or in general, can I choose wich information gets shown on the display for each item? That would be great.


General Chat / Re: GPL issues with ML post processing software
« on: May 17, 2014, 09:27:11 AM »
In my humble opinion this problem has been discussed in the past millions of times if you take a look at the linux community. Here we have two paties as very often:
A) party one thinks of a community based project, open to everyone to his own personal degree.
You get
- a broad community
- a project getting bigger by its userbase
- support by people who wouldn't do anything if it would be a commercial thing
- transperancy for everyone who can follow the technical stuff up to a certain degree

In my personal opinion, very strong points to think abaout.

B) party two wants to make a business aka money
- they need a broad community
- they need a big project, otherwise no one would be interested in buying anything
- for small parties, they need the support by a userbase
- transperancy is nothing they are interested in, as any other guy could copy their basis for business and maybe make it somehow better.

In my personal opinion, we all need some kind of bread and butter to live. So making money is NOT an evil at all.

In the end both parties have good reasons for their points of view, but they are opposing each other and always will. And, as usually in situations like these, as done with linux, mozilla and all the others, its first come, first serve. The ones who started the project, set up the rules. Without them, there would't be the project at all.
For the second party there are still possibilities to go their own way without violating the basic ideas of the founders. Some of them are already mentioned above. So, there should't be anything to complain about, but only new ways to approach their goal.

Regards, and keep on going doing a great job.

General Help Q&A / Re: HEEEELP ! Is my 700D Broken due to ML ? :5
« on: April 11, 2014, 02:31:00 PM »
Just in case this happens again, remove the battery quickly, because there might be still something going on within the camera and it could heat up.

Good to hear its working again  :D

General Help Q&A / Re: HEEEELP ! Is my 700D Broken due to ML ? :5
« on: April 11, 2014, 02:24:47 PM »
Remove the battery and wait at least 10 sec, put it in again and turn the camera on. In case this doesn't help, remove memory card, put it in a cardreader and install ML files anew. During this time remove the battery again.

Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: April 11, 2014, 08:10:57 AM »
Isn't that the way it should be, as your are only changing the number of pics per second and not the aperture or shutter speed?

I just tried it on a tight project. From shooting to delivery I had just 48h for a 3min trailer in RAW. In the beginning, I took a two way workflow, as the logs are new and I didn't want to risk anything. But after seeing the first results, I did the rest with your cinelog files only, getting more confident clip by clip.

You did a realy great job!

So, if there is just a mismatch of ffmpeg put into the header, does apps like DaVinci actually use all bits given by the file?

I would like to ask if any other mac user has this problem with the ProRes files being 4:2:2 instead of 4:4:4.

By now these are the applications I tested:
- Finder info says ProRes 4:2:2 HQ
- Davinci resolve lite says 4:2:2
- FinalCut Pro X says 4:2:2
- Quicktime says 4:2:2
- Mediainfo says 4:2:2

I get the same results with MlRawViewer 1.1.3 and 1.1.4 regardless the .mlv I use as input.

That was one of my first thoughts, too. But Bluerayplayer can not playback ProRes 4:4:4 (screen stays blue, no audio) and the files created by MlRawViewer are played back flawless. Fcpx is based on quicktime, as far as I know, therefore both show the same codec. But Davinci resolve also states, that it is 4:2:2.
By the way, the bitrate is 186.05 MBits/s @ 23,98 fps 1080p, that would be ok, or am I wrong?
Is there a pref file anywhere on macs?


I tested it again using several different apps, like apple quicktime, FCPX and DaVinci Resolve. All apps state the same, the .mov I get from MlRawViewer on my mac are all ProRes 4:2:2 (OSX 10.9.2 and MlRawViewer 1.1.3).

The picture by Rewind is made on a linux machine (?), might this be the reason for the different results?


Interesting, quicktime on my mac says prores 4.2.2. Bluerayplayer says prores 4.2.2 LT. What do I do wrong? Do I have to change any settings?


a quick question I stumbled upon yesterday. The version of Prores Mlrawviewer uses is 4:2:2 LT, isn't it? Why not 4:4:4, or would that exceed the amount of information stored within the .mlv?


Ahh, beim 70-200 kann man die Wirkungsweise des IS auf eine Ebene einschränken. Daher habe ich noch nichts bemerkt.


Super Seite!
Eine kleine Anmerkung zum Anfang. Dort schreibst du, dass man den Stabilzer ausschalten soll. Da ich immer mit einem externen Recorder den Ton aufnehme, nutze ich auch den Stabilizer ohne bisher Einschränkungen gesehen zu haben.

Vielleicht erklärst du noch in einem Satz, warum man ihn ausschalten soll?

Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 23, 2014, 09:08:17 PM »
i forgot something totally. My cf cards were both formatted with Fat32. I guess this would make a difference to exFat, but now it's too late for testing today...

Should we set exFat to the list of standards for testing?

Something to add:
It is weird, the lighting situation seems to influence the write speed during the benchmark. With a lenscap on top I get repeatedly different speeds compared to lenscap off...
Could someone test this to be wrong or true?


Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 23, 2014, 06:30:20 PM »
today I did some more comprehensive testing with my 5d mark III.

I benchmarked both my lexar cards, a 32gb 1000x and a 128gb 1066x on the latest nightly build for the canon firmware 1.2.3 and 1.1.3

I think the idea "eyeland" had, to compile a standard test setup is quite nice and convincing.
Therefore I took some time to think about it and came up with this setup I used:

Safety Shift OFF
Tone Priority OFF
Auto Power off OFF
1920x1080 @ 30fps All-I

Magic Lantern
Global Draw OFF
FPS override OFF
LV DIGIC peaking OFF
Card settings Preferred card CF, others OFF
Modules: mlv_rec, mlv_play, nothing else

almost everything else is set to OFF
Benchmark in movie mode (live view on)

Camera was not moved during the benchmarks and the lighting was constant. I don't know if this is relevant, but it might be as the liveview is on during the benchmark and therefore the cpu has things to do.

I did all benchmarks three times, but got always the same results:

Firmware 1.1.3
Lexar 32gb 1000x      w   91.7      90.6      91.9      @16384k
                                r    122.3    122.3    122.1
Lexar 128gb 1066x    w   91.9      93.4      93.3      @16384k
                                r    122.3    122.4    122.2

Firmware 1.2.3
Lexar 32gb 1000x      w   86.3      89.3      89.6      @16384k
                                r    118.2    118.2    118.5

Lexar 128gb 1066x    w   85.4      89.1      89.0      @16384k
                                r    118.3    118.2    118.4

Next I did a brief test on the power consumption and the heat up of the camera, but these test were not really scientific as I took different batteries, relied on the display (temp) used a plain simple stopwatch and had to press a button every now and than to hinder the camera to shut the display down. Therefore take the result with care.

Anyway, the powerconsumption on 1.2.3 was much higher, the heat raised significantly faster.

By now, the datarate is significantly lower, the power consumption higher and the heat (37°C compared to 45°C after 3 minutes) also.
But hey, I stay with 1.2.3  :D I'm sure this can be sorted out.

Tell me what you think about the setup and let us compile a standard for testing.
And no, I can't do any programming, but if I can do anything else, like serving virtual coffee, I'll do it  :D


Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 23, 2014, 12:35:30 PM »
they do this at 30fps? So you get a write speed of 106MB/s in video mode?
With or without spanning?
Could you please tell me your settings regarding buffers, hacks and so on?


Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 23, 2014, 12:28:09 PM »
True, but I can't change cards every couple of minutes. That's why I choose the 128GB 1066x. In photo mode it reaches about 115MB/s solid, therefore I think a faster card would not change anything. Read speed is about 158 MB, which is about the max of UDMA7 as far as I know.

Maybe it is he cpu which is to heavily utilized in video mode, so there are to less cycles left for writing?


Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 23, 2014, 09:19:50 AM »
on my 5d Mark III with 1.2.3 installed and Nightly 2014 Mar 17:

- Powersave in liveview can't be enabled or disabled (always grayed out), submenues work, Battery Level is only informational, but selectable

Maybe this can be made somehow more obvious (a hint at the bottom in green?):

- Preview mode ML Grayscale in mlv_rec works only if global draw is set to allow (of course)

Best results recording raw I seem to achieve with:
Global draw OFF
Memory hack OFF
Extra Hacks ON
Buffer fill method 3
CF-only buffers 0
Card spanning ON

This appears to be the highest working resolution for my camera: 1792x1008 16:9 @29.97 fps continuouisly without any bad frames (CF 128GB Lexar 1066x and 128GB SanDisk Extreme 45MB/s).

Others seem to get full 1080p @ 30fps continuously, but I absolutely have no clue how they get there...


Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 22, 2014, 04:34:59 PM »
I'm new to this board, although I read it quite a while. I hope I don't do anything wrong here.
I have a 5d Mark III with 1.2.3 installed and wanted to give some feedback.

Nightly 2014 Mar 17
+/- Tab ExpSim toggle on/off is shown but can not be selected
+/- Tab pressing SET instead of Q to enter values activates LifeView with ML Menues printed on top (you can still scroll), another SET and you are back.
colors differ slightliy between raw_rec and mlv_rec using mlvmystic (might be mlvmystic?)
"Auto power off" is often set to 2 minutes again after reboot.

But anyway, a great job!


Pages: 1 2 [3]