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

#1
This new version crashes on startup with 10.11.6. Here's the log

https://www.dropbox.com/s/2n4izxzh1ow78fh/log?dl=0

#2
@Danne
Running the uninstall.command before running again the install.command resolved the problem, now it's works. I have the good tags embedded in the DNGs.
I do not understand why, but it's works.
Thanks a lot.
Bayard1965.
#3
It's  version 10.7_align. The app was run from the applications folder, and i made another try putting the app on the desktop. The folder containing the MLV file is on the desktop.
If i open the dual-iso MLV with MLVFS i can see that the metadata tag is "Canon EOS 5D Mark III" in the DNGs.
When i use CR2HDR-R to convert the dual-iso MLV, i have a "canikon" metadata tag in the DNGs after conversion.
#4
Hi,

When i transcode a normal mlv file, i have a "Canon EOS 5D Mark III" metadata in the resulting DNGs, but when i transcode a dual iso mlv  i end with a "canikon" metadata in the DNGs. The consequence is to not be able to choose camera profile in ACR. It is not specific to this last version, i think.
Have i missed something?

Regards,
#5
I asked Clifton Stommel about this possibility.

Hi,
I just wanted to know if this system could work with a 5Dmark3 (using MagicLantern), i mean interfacing with normal CF cards, not only with CFast 2.0 cards.
Regards,

Answer:
We are looking into that, as well as XQD and SD. I think it's safe to say that the response this campaign is getting has proven that there is an interest in being able to record straight to SSD on any camera. Once the campaign closes, we'll be allocating resources to various avenues depending on which has the most room for growth and the most public interest (and obviously, getting the CFast boxes out the door and to their backers is #1 priority).
#6
Hi,

I have on some tests shots, sometimes a bad frame, like a flash on the upper part of a frame using mlvrec from the last build from march 2015.
Raw Video / bad frames with using mlvrec from 2015Mar16.5D3123 build on 5d3

I did too test shots with rawrec recording: no problems
So i downgraded to 1.1.3, loaded the last build for 1.1.3 and make new mlv test shots and had same results, sometimes a bad frame.
Then i upgraded to 1.2.3 and used the last 2014 7 August version of the 1.2.3 ML firmware, and did mlv test shots again. No problem

I did a last test. i loaded again the 2015Mar16.5D3123 build but replace the mlvrec module by the one of the 2014 7 August version. Test shots. No problems, no bad frames.

It seems then related to the mlvrec module on the last build, for 1.2.3 and 1.1.3.

Any ideas?
I did too test shots with rawrec recording: no problems
#7
Hi,

I have on some tests shots, sometimes a bad frame, like a flash on the upper part of a frame using mlvrec from the last build from march 2015.
I did too test shots with rawrec recording: no problems
So i downgraded to 1.1.3, loaded the last build for 1.1.3 and make new mlv test shots and had same results, sometimes a bad frame.
Then i upgraded to 1.2.3 and used the last 2014 7 August version of the 1.2.3 ML firmware, and did mlv test shots again. No problem

I did a last test. i loaded again the 2015Mar16.5D3123 build but replace the mlvrec module by the one of the 2014 7 August version. Test shots. No problems, no bad frames.

It seems then related to the mlvrec module on the last build, for 1.2.3 and 1.1.3.

Any ideas?
I did too test shots with rawrec recording: no problems