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

Camera-specific Development / Re: Canon 700D / T5i
January 07, 2014, 12:06:00 AM
Quote from: mk11174 on January 05, 2014, 10:54:01 AM
I have been looking for addresses for audio and this is what I have so far.

I was able to get beep working fine, I can change volume, type and frequency just fine.

Audio meters working but freeze cam when you record and the meters stop working if you run a beep test.
Audio remote shot works in photo mode, in record mode it will freeze cam once starts to record.

With CONFIG_AUDIO_CONTROLS commented and defining meters and remote shot
Audio meters only work while recording no freeze cam
Audio remote shot works while recording no freeze cam, doesn't work in Photo mode.

Need to try FilterRec fix to see if it helps, pretty sure I found correct address just need to add the code for it to test.

Of course Wav recording does not record anything, it works, just records nothing.

At least meters sort of work and beep works good.

I have been using 600D as Ref and I am pretty sure my stubs are correct, threshold was differ to find but Im guessing it is good since meters are working, seems like something else freezes cam because even if I disable meters it still freezes when I record if I have CONFIG_AUDIO_CONTROLS uncommented.

Awesome! Never got round to doing this, too many things going on atm. I guess this is where you disable things one by one to find out what's causing the freezing.
Camera-specific Development / Re: Canon 700D / T5i
December 27, 2013, 03:54:07 PM
New firmware? Interesting!
Archived porting threads / Re: Canon 70D
December 12, 2013, 01:45:13 AM
Quote from: a1ex on December 10, 2013, 09:40:23 PM
Almost there. In my opinion, there's a large difference from getting a port into a "seems to work" state and effectively maintaining it and fixing all those little quirks.

This is not to underestimate your work, but we have several ML ports that have not been maintained in the last few months, up to one year, so the code started to rot (I'm talking especially about 40D, 5Dc, 1100D, 6D, 7D, EOS M, and, to a lesser extent, 600D and 50D). In this situation, starting a new port doesn't seem the best thing to do right now in my opinion.

I can see your point of view because if I was to upgrade my 700D -> 70D then I guess there would be nobody to maintain the 700D and then that would be added to the list of dormant ports. Although, most of those cameras are old and people have upgraded to newer cameras (like the 70D) and from what I can see nobody seems to be keeping ML up to date with these new releases. Which in my opinion is a bad thing to do, since ML will be loosing out on a growing audience.

The 70D just needs lifting off the ground then new adopters/developers will maintain it. That's basically my story, bought my first DSLR (700D). Found out about ML and noticed the 700D wasn't at all up to scratch. So I got to work on it and got it to a usable state where I could use it on my trip to NY a week later.

"If you're not growing, you're dying."
Archived porting threads / Re: Canon 70D
December 07, 2013, 09:39:49 PM
I'm wondering if I should sell my 700D and work on the 70D IF you guys could make up the difference between the 700D-70D price range. That's unless some kind soul donated one to me.

I currently don't have enough to buy one myself. But I am willing to work on it.

My previous work was getting the 700D ML up to scratch with the rest, which I believe I achieved.
It's not as simple as enabling a tab, the audio functions in 650D/700D firmware have changed. Audio needs re-working.
Camera-specific Development / Re: Canon 700D / T5i
November 28, 2013, 02:42:22 AM
Disabling the bootflag is very easy, one line of code in fact. The problem arises because of how risky it is to disable it, the devs don't want people claiming ML bricked their camera and so to prevent this the ability has been taken away for now until a more reliable way has been found.

a1ex should be able to create a .fir to disable the bootflag safely.
Camera-specific Development / Re: Canon 700D / T5i
October 23, 2013, 12:37:43 PM
I'll look into it, just haven't had any time lately :S
Camera-specific Development / Re: Canon 700D / T5i
October 17, 2013, 12:57:56 PM
What do you need help with? (what are you trying to port over to the 650D?)
Archived porting threads / Re: Canon 70D
October 06, 2013, 12:28:08 AM
If I had a 70D I'd be more than happy to help get it off the ground.
Camera-specific Development / Re: Canon 700D / T5i
October 05, 2013, 10:13:42 PM
Well after taking a break I'm in the mood to start continuing my work maintaining the 700D of ML ;)

Priority at the moment :

- Pink Dots on RAW video (work out which method/solution gives the best results)
- Sound (this might be a bit tricky since a few things have changed)
- 10-bit RAW video recording? (I will experiment to see what I can achieve or fail, 700D's DIGIC5 could just be powerful enough for this?)
Magic Lantern RAW doesn't change any of the settings, you should get the exact same image using RAW2DNG. Son of Batch must be changing the settings.
The TIF images do look like they loose quality, this is due to the rendering done by the Adobe SDK. I'd stick to using DNG's. The DNG's shouldn't be different if Force Linear is UNTICKED.
- 16-bit TIF
- Fixed colour issues

I will try to add support for MLV when it get merged.
Quote from: janoschsimon on August 25, 2013, 03:45:39 PM
hey there dont know if im right here but its a try worth :D

i build my own MiniRAW1 Camera which shoots 720p 120fps 12bit raw
my workflow is a little bit awkward:
1. i record from the camera controll software and stream .raw files
2. a friend of mine and i made a .raw converter on mac which convertes the 12bit .raw to .dng which works pretty good resolve and adc can open and edit the files.

but with 120fps and each frame is 1,4MB my HDD is nearly full and so i found the cineform RAW thing which reminds me a little bit of Redcode :-)

no here is the problem:
when i import a folder which contains the .dng sequenz into the cineform studio pro trial version 1.3 on my windows 7 64bit machine the first thing is that i cant see the preview and no matter what i put into the settings (avi, mov) the second i click on convert the program crashes :-(

any idea what i can try? cheers and thx janosch
attached is a sample dng which crashes cineform studio pro

cheers janosch

Sorry, I was away (went NY)

Unfortunately I don't have Cineform Studio (never used it). My guess is it must crash because of incorrect/missing tags in the DNG header?
Quote from: 3pointedit on August 26, 2013, 02:17:23 AM
Any chance of a 16bit tif option?

sure, I'm on holiday at the moment (in New York) so I'll have to fix all these bus when I get back (30th)
Quote from: arrinkiiii on August 23, 2013, 03:06:22 PM
Version 1.0.0.

Works good and fast
Wend i put the dng's in after effects and make play the video is all scramble, no good.

Version 1.1.2

Works good but problems in the colors.
Wend i put the dng's in after effects and make play everything go's good as should be.

Can we merge the first version  and the last version?  ::)

The thing is, I haven't actually changed any of the image processing stuff, I've just changed the way it creates the threads to process the image AND I also cant reproduce the problem on my PC. Your files are fine when I make them.
Quote from: Rewind on August 23, 2013, 08:01:00 AM
Well, I don't think these raw_type manipulations are exactly the Solution. Pink dots around high contrast edges are still there.
I mean, this method doesn't excludes the focusing pixels from raw stream, it just adds correct hot/dead pixel info, so we can chose whatever soft we want to deal with them. Right?

Also, TheUnknOwn said, that "With raw_type 14 you don't get any image anomalies using Adobe software". Anyone can confirm that? In my experience, when i change the string in raw.c to #define PREFERRED_RAW_TYPE 14, compile and process with ACR, i see the same pink-green artifacts around high contrast edges:

Use RAW_TYPE 78 or 99

I missed the focus points in 14
Quote from: Danne on August 23, 2013, 01:45:22 PM
Tried to find the 32-bit option as suggested but couldn, t find it. Will upgrade eventually.

It's compiled as a 32-bit binary since it wont compile correctly using 64-bit (it messes the RAW structures up). I don't have a Mac and therefor don't know a lot about them. I highly suggest you upgrade to 10.8

WINDOWS - Magic Lantern RAW 1.0.0 OLD
Quote from: arrinkiiii on August 23, 2013, 04:29:02 AM
OK, thanks. I will not use Force Linear. I thought since Force Linear produced a larger file (5MB) the dng's would be with more quality, opposite from No Force Linear  that give's me a 1,96MB each dng.

Until now for me the first version, 1.0.0. works good. Only the Force Linear gave me some purple fringe.

*If i go to File and open a raw file, then i chose my settings... and hit the tab Process, chose my output folder and voilá, it make the magic and give me the dng's. Everything is good, so far... Then i chose different settings, hit the Process tab, chose folder to output... and voilá, it make is magic... BUT wend i go to the output folder i just got black dng's, same amout of frames but all black... with 434kb each dng. Is not possible to correct this? For not all the time need to open/load the same file?

Here is the file from last version, 1.1.1 and a black dng for comparing. I think is the same from last version.

Raw file for testing (300MB)

I can't reproduce your problem. The this is a DNG it just created : looks fine to me.

Could you try this?
Quote from: arrinkiiii on August 23, 2013, 04:04:28 AM
1- No Force Linear, Uncompressed = same strange colors

2- Force Linear, Uncompressed = same strange colors

For me, 7D user, what is different from force linear and unchecked force linear? Beside the big file in Force Linear...

Force Linear rebuilds the DNG file and processes the information (demozaic) into a more compatible format. I suggest you don't use it unless you have problems without it.
Try this, see if this fixes the problem?

WINDOWS - Magic Lantern RAW 1.1.1
Quote from: Rewind on August 23, 2013, 12:19:50 AM
Guys, may I ask you please to share a build with RAW_TYPE 14. I compiled it by myself, but I cant see any difference: the pink dots pattern is the same. May be i'm doing something wrong.
Quote from: arrinkiiii on August 23, 2013, 02:30:03 AM
It got 300Mb, its ok?

Yes that's fine, I can make it only process the first frames.

Does this happen with ALL OS versions? Do you have a small RAW file I can use for testing that shows these artifacts?
Quote from: arrinkiiii on August 23, 2013, 12:43:18 AM
Test ML Raw in Canon 7D in Win7 64bits

Version 1.0.0

Work good in all options. With Force Linear checked it give's me some purple fringe but give's me more big files. More quality with Force Linear?

Version 1.1.0

Work good in all options. But in the dng's all the colors acts strange. The dng's look like they are grey, in some part of the frame or other colors look like they are smooge/ghost image/color. Difficult to explain, if needed i can post some examples.


Its possible to load more then one file and output automatic the folders for the several loaded raw files?

I like this piece of software. It's easy to operate and maybe need some more options for configurations. But for me is ideal, extract more quality as possible from the raw file and then i make proxys in after effects with the dng's.


If i compare one dng from raw2dng and other from ML Raw 1.0.0 looks that ML Raw saturate more. Opposite from the rawmagic.

Could you post some DNG examples, comparing the output from raw2dng with the output of ML-RAW (Force Linear disabled)?

Quote from: ewinemiller on August 23, 2013, 12:54:21 AM
I couldn't get 1.1 of either the Mac or Windows version to work.

On Mac click process button, select RAW file from dialog, nothing happens.

On Windows, select File|Open, select RAW file from dialog, nothing happens. Click process, nothing happens.

That's strange, nobody else has had that problem? A directory window should appear for you to select where you want to store the DNG outputs.