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

Pages: [1] 2 3
1
Raw Video / Re: Raw video on 5DMK2
« on: September 09, 2014, 08:23:21 AM »
Thank you reddeercity!

@guentergunter, To me looks like Card write problems , I use to see this with my Slower Cards at higher frame resolution (Sandisk 60Mb/s cards).
Did you try an older build of raw2cdng to convert ?
I use Version 1.4.9 as it is the only version that can be read Cross platform (Mac/PC) with out green or pink cast at 16bit.

The pink cast is no big problem - since I convert and edit the footage in ProRes4444.
But I'll try that version out! Maybe I'll switch to native CDNG-editing in the future.

So I don't think ML is the problem , More to do with Getting Hot and Card Write issue.
I know when my Lexar 1000x 64GB gets too hot it will drop frame even on lower resolution ,
usually after about an hour or so, and that's with 5D2.

What CF Cards are you using ?
What Raw build are you using ?

I'm using two Lexar 1000x card (64GB and 32GB) and one SanDisc Extreme Pro 90MB/s (32GB).
I used the "magiclantern-v2.3.NEXT.2013Sep08.5D2212" together with a.d.'s modification "6bb97bcbc0f4" (also build around this date).

Now that you say it: It could have been a heat problem.
Since the problem occurred on at least two cards (I don't remember witch ones), all brands are affected.


Would you say, that the actual nightly build "magiclantern-Nightly.2014Sep01.5D2212" is safe for production work?
Anyone knows which temperature is critical?


Thanks in advance!

2
Raw Video / Re: Raw video on 5DMK2
« on: September 08, 2014, 08:10:01 PM »
I have a really big problem with banding!

I post it here first - but maybe it's worth a new threat?
Since it's not like what I've seen over the past by myself or by others.

Here's a frame demonstrating the problem:

https://www.dropbox.com/s/ktip4trlrqriiuq/Fehler.jpg?dl=0

Here are also the 16-bit CinemaDNG files:
DNGs from RAWMagic
DNGs from raw2cdng
Both programms are the very latest versions.

After three hours on the set, the problem appeared in the middle of a take and then periodically repeated through some following takes. Then it disappeared again and after one hour or so it came back.

I tried to reproduce the problem (overheating, different frame rates (since I shot 24.000 for the first time), all CF-cards used that day, that old build and the latest build with mlv) without success.

It's recorded with raw_rec.mo from an old nightly from last year. The reason for this is:
I didn't have the time to study latest developments and wanted to go safe using a build I already and successfully recorded three short movies with.
Anyway: The problem looks like a sensor error, since it's moving through the frame from bottom to top (with a duration of 2-3 frames).

I'm also afraid of just using MLV - since I'm not sure, if the problem really comes from that old build or rather from ML or the cam.


Any help would highly be appreciated!

3
Camera-specific discussion / Re: Canon 5D Mark II / 5D2
« on: April 08, 2014, 09:57:10 PM »
Edit: use adobe color space in camera , will give you better skin tones and better color in general.

In other words: you claim, that the image recorded by raw_rec or mlv_rec differs when you change the color space of the camera?
That's not true!

"Adobe Color Space" is a RGB color space and thus NOT raw! It's used for compressing to jpg. So, the RAW buffer, ML reads from is not affected.

[However, when you shot pictures in (Canon)RAW, the embedded preview file differs (since it's compressed to RGB).]


It's up to everyone in what color space one works later on the computer. Here you will definitely get different results. But the .raw or .mlv files will always look the same!

4
Camera-specific discussion / Re: Canon 5D Mark II / 5D2
« on: April 06, 2014, 11:06:46 PM »
Magic Lantern v2.3 - Install Guide

I never saw any .cpgz file.
I suggest to delete and ignore it and/or to use another zip application.
By the way: OSX (just as windows) can unzip zip files right from the finder without any third party software. And it does it correctly!

5
Hello g3gg0,
since a few days now there's a discussion about the future resolutions available for the 5D2 (and maybe other cameras).

It started with a1ex:

The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.

So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.

This change was discussed here:

http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff


In my opinion, it would be no problem to simply discard black borders from an image while converting to dng:


...and it's also no coding effort to discard pixels while converting to dng. The user wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting (to dng) step.

I'm no programmer (just some very basic skills).
Thus it would be really great, if you could just leave a little comment about it as a programmer to help us sort things out for the 5D2 (and other cameras with the same problem):

Specific 5D2 threat

Thank you very much!

6
Hello gnarr,
since a few days now there's a discussion about the future resolutions available for the 5D2 (and maybe other cameras).

It started with a1ex:

The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.

So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.

This change was discussed here:

http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff


In my opinion, it would be no problem to simply discard black borders from an image while converting to dng:


...and it's also no coding effort to discard pixels while converting to dng. The user wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting (to dng) step.

I'm no programmer (just some very basic skills).
Thus it would be really great, if you could just leave a little comment about it as a programmer to help us sort things out for the 5D2 (and other cameras with the same problem):

Specific 5D2 threat

Thank you very much!

7
Hello marten,
since a few days now there's a discussion about the future resolutions available for the 5D2 (and maybe other cameras).

It started with a1ex:

The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.

So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.

This change was discussed here:

http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff


In my opinion, it would be no problem to simply discard black borders from an image while converting to dng:


...and it's also no coding effort to discard pixels while converting to dng. The user wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting (to dng) step.

I'm no programmer (just some very basic skills).
Thus it would be really great, if you could just leave a little comment about it as a programmer to help us sort things out for the 5D2 (and other cameras with the same problem):

Specific 5D2 threat

Thank you very much!

8
Hello tonybeccar,
since a few days now there's a discussion about the future resolutions available for the 5D2 (and maybe other cameras).

It started with a1ex:

The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.

So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.

This change was discussed here:

http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff


In my opinion, it would be no problem to simply discard black borders from an image while converting to dng:


...and it's also no coding effort to discard pixels while converting to dng. The user wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting (to dng) step.

I'm no programmer (just some very basic skills).
Thus it would be really great, if you could just leave a little comment about it as a programmer to help us sort things out for the 5D2 (and other cameras with the same problem):

Specific 5D2 threat

Thank you very much!

9
Hello scrax,
since a few days now there's a discussion about the future resolutions available for the 5D2 (and maybe other cameras).

It started with a1ex:

The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.

So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.

This change was discussed here:

http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff


In my opinion, it would be no problem to simply discard black borders from an image while converting to dng:


...and it's also no coding effort to discard pixels while converting to dng. The user wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting (to dng) step.

I'm no programmer (just some very basic skills).
Thus it would be really great, if you could just leave a little comment about it as a programmer to help us sort things out for the 5D2 (and other cameras with the same problem):

Specific 5D2 threat

Thank you very much!

10
Raw Video Postprocessing / Re: [RAW2DNG] BATCHelor 3.0 Alpha 3
« on: February 07, 2014, 09:51:39 PM »
haven't you noticed this?

lossless is lossy and lossy is lossless, options are inverted.

Does that problem still exist?

11
Raw Video / Re: RAW VIDEO 5D MARK III + Monitoring HDMI
« on: September 04, 2013, 11:11:55 PM »
Everyone experiencing wrong framing on HDMI can now vote for this issue to be solved:
https://bitbucket.org/hudson/magic-lantern/issue/1582/crop-bars-for-external-smallhd-oled-7-7

12
Raw Video / Re: RAW: Focus Peaking vs Small Hd monitor
« on: September 04, 2013, 11:07:51 PM »
HDMI + RAW:
- resolution is 1080p

- no decrease in speed

BUT:
http://www.magiclantern.fm/forum/index.php?topic=6432.0
You can activate ML Greyscale to remove the wrong frames on HDMI screen (while still having a colored image).

Also: Here you can vote for this framing issue to be solved:
https://bitbucket.org/hudson/magic-lantern/issue/1582/crop-bars-for-external-smallhd-oled-7-7

13
Raw Video / Re: 5d mark III external monitor raw, problems?
« on: September 04, 2013, 10:58:27 PM »
A huge problem with external monitors is this:
http://www.magiclantern.fm/forum/index.php?topic=6432.0

So, I'm asking everyone, experiencing this problems, to vote for this issue to be solved:
https://bitbucket.org/hudson/magic-lantern/issue/1582/crop-bars-for-external-smallhd-oled-7-7

14
Raw Video / Re: RAW liveview on PC monitor via USB
« on: September 04, 2013, 10:37:50 PM »
You may check this post:
http://www.magiclantern.fm/forum/index.php?topic=7054

If you read through, you can find the exact same problem. I even did a short demonstration video of that problem.
But sadly, nothing has changed since...

15
Feature Requests / Re: Option to remove crop box
« on: August 30, 2013, 07:03:24 PM »
Hi,... i was wondering if you can add your problem to this link, it seems there are dozens and dozens of people who started threads and topics about issues with external monitors , but these are all over the place and consequently no one thinks its an issue since they show up only one at a time in this very big haystack of threads. i started a thread at the developpers page addressing it to alex, in the hopes he can make this more priority, there is a vote and a follow option, if you wouldn't mind adding yours there as well, may be alex can then see how many people really do work with external monitors and have a hard time not seeing crop marks the right way and other issues:

https://bitbucket.org/hudson/magic-lantern/issue/1582/crop-bars-for-external-smallhd-oled-7-7

i would really appreciate your effort, may be we can all get together on those many issues with external monitors..

BR
Kuky

+1 for that!

16
Modules Development / Re: Magic Lantern (RAW) Video format v2.0
« on: August 24, 2013, 10:17:09 PM »
hello,
this all sounds very interesting..
can anyone please post a link to a 5dmk3 build with the new format.. i am looking forward to test it.
thank you.
sw
What about a look into the very first post in this threat?


By the way: 5D2 support is much appreciated ;)

17
Great! And many thanks!

Can't wait to switch completely to the new format.

18
Hardware and Accessories / Re: Monitoring on tablets
« on: August 19, 2013, 09:29:28 PM »
That depends on the data, the camera outputs on the USB port.
If it has always the same (full) resolution, then there's no drawback in performance.

By the way: I sold my Nexus again, since I don't see any hope, that it will be supported by RAW in the future...

19
Solucionated! with the new firmware 1.2.1 set mirroring in the menu, and conecct any Monitor via HDMI.
Great feature!
But it's sadly for 5D3 only  :'(

20
Hardware and Accessories / Re: Monitoring on tablets
« on: August 13, 2013, 08:07:48 PM »
So a tablet connected to the USB port is better or worse than an external monitor hooked up t the HDMI out? Can you use it for focusing? Will it provide you with false color, zebras and focus peaking?

Considering that a 7" Lilliput monitor can be had for about $250, is the Nexus worth it as an option?
Zebras and false color are pretty useless on both options (when you record RAW), since they are not computed on raw sensor data (as it's done inside the cam by ML). So, only focus peaking makes sense to be used.
I would say the HDMI is more usable, when it comes to lag time.
But the peaking function on the Lilliput is said to be average at the most. It's much better on e.g. a Nexus, due to much more computing capacity and better algorithms. Also: Apps are possibly expandable with new algorithms, zebras, meters and maybe even RAW-support.

When you plug in a HDMI cable, the internal monitor shuts down. So, if you plan to use a monitor for someone else than the cinematographer (e.g. the director somewhere behind), the cam needs to be equipped with another monitor as well.

At this point, it also want to mention that a Lilliput with a big rechargeable battery lasts 4 hours. So, you would need some more batteries and at of course a recharger.
4 hours is what the Nexus lasts out of the box. And batterie extenders for Tablets/Smartphones are pretty cheap and give you up to 3 complete recharges.


So, if lag time at a second monitor is a decisive argument for you, then you'll need HDMI (with probably two monitors, batteries, etc.).
If it doesn't matter, you're going the cheaper way with even better peaking.
___

BUT: Yet, only the 5D3 supports USB output with RAW video enabled. And I didn't find anything about whether it's possible on other ML-cams or not.
In other words: Is it accessible by software or is it a hardware limitation?

Just curious: when you disable raw video, does the image appear again?
a1ex: Did you ask with a possible solution in mind? ;)

Thanks for your time! I hope there is a way...

21
Hardware and Accessories / Re: Monitoring on tablets
« on: August 12, 2013, 05:05:42 PM »
My setup doesn't do that. And your lag, is MUCH slower than mine.
Edit: just noticed you're on a 5d2. I'm working with the mark iii
The lag is something I can cope with easily - as long as there is some picture at all.

And since I'm a student, the 5D3 is actually out of my financial reach.

22
Hardware and Accessories / Re: Monitoring on tablets
« on: August 12, 2013, 08:32:58 AM »
Hmm, I know that the EOS Live is quite slow I have tested it with Canon 5d mkII mkIII
Probably it is 10fps. But is in no way a evf or something.
Better is a HDMI streaming usb stick from Blackmagic with a Windows 8 tablet.

I tried the Note with the Android app and a special cable and it lagged similarily.
However I wonder about the new Nexus 7. Probably it is the same but it hads the capability to give us more fps.
I used the DSLR Controller by Chainfire for monitoring. Within the app, you can set fps to 30. And it looks like that.

The only real downside is a lag of around 0.5 seconds (check my test video above).
So, you're right, I wouldn't use it for framing, especially for fast movements.

But, my 5D2 is too slow for computing peaking while recording raw. This needs to be done outside the cam.
There are two possibilities: Android or an external HD monitor with peaking.

When I compare these two, I prefer Android for two reasons:
- It's much cheaper than a comparable field monitor with internal peaking (a used Nexus 7 costs around 100$ at eBay vs. 350$ for a appropriate monitor)
- Since the android device is connected to USB, the internal monitor is still active (so is HDMI) and can be used for framing (no second monitor needed, since internal display is still active!).

I would use this setup for e.g. SteadyCam shots: Framing with internal display (or a cheap SD HDMI monitor) and remote focus pulling from behind by someone else with the Android app and an electronic follow focus.

I hope that it's possible at all and that the effort to make it possible is low enough, so that someone cares beside all the other great developments like e.g. Dual ISO ;)
At least it's an option for everyone else than 5D3 owners (which is, to my knowledge, the only cam with the abbility to use USB combined with raw video).

23
Hardware and Accessories / Re: Monitoring on tablets
« on: August 10, 2013, 10:52:16 AM »
Thank you for testing. Now we know that the 5Diii has something the 5Dii and 50D does not have that enables RAW video output. All the same results on the 50D. Sudden stop/start of video on tablet as soon as RAW module is toggled. All buttons still work.
Maybe it's just enabled/disabled by luck so far - since no one seemed to look at this thoroughly, yet.

WHat a shame, I really had very high hopes to use this on the 5D2 for peaking focus during raw recording, are there any chances there might be a workaround?
I still have very high hopes. At least no one said it's impossible.
To me it looks just like an overlooked setting, which can be fixed!

What do you mean by workaround?

24
Hardware and Accessories / Re: Monitoring on tablets
« on: August 09, 2013, 11:40:04 PM »
Yes, even without unplugging the device.

When I deactivate RAW video, the display output on Android immediately continues updating.
To me it seems, like the cam completely maintains the connection (due to less writing speed), but just doesn't output video to the USB while RAW is active.

By the way: while canon or ml menu is open it also stops.

Here's a little video, just to show:

I tried latest stock nightly, as well as latest a.d.'s build. Both with and without Small Hacks activated.
Also I tried with and without HDMI monitor.
→ 8 combinations altogether
The exact same happens in all combinations.

Is there anything else, any setting or combination I should test?


May there be any possibility to solve that problem?
Using this Android combination has some nice advantages. Like Peaking outside the cam, using Android as monitor together with internal display or HDMI.

25
Hardware and Accessories / Re: Android tablet as field monitor.
« on: August 09, 2013, 06:22:04 PM »
Well, I bought myself a Nexus 7 and tried it out: http://www.magiclantern.fm/forum/index.php?topic=7054.msg65493#msg65493

Pages: [1] 2 3