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

#1
Tragic Lantern / Re: Tragic Lantern for EOS M
September 20, 2013, 01:09:48 AM
@DanyoO:
really nice video! the shaky stuff form 0:15-0:20 is bit strange, imho. but it's definitely the best eos m raw video i've seen so far. the uncontrasty yellowish look is fantastic.
#2
Tragic Lantern / Re: Tragic Lantern for EOS M
September 18, 2013, 04:01:04 PM
At least in germany the 45mb/s sandisk extreme cards cost just ~50% of the 95mb/s extreme pro cards (32,31 EUR vs 64,98 EUR für 32gb on amazon) and afaik they are fast enough. But if anyone has both, a direct comparison would be nice.

Are there still any problems with PDR? i'm not very active at the moment since i've to finish my diploma thesis until end of next week.
BTW latest ML version does crash for me while loading the modules. i use EOSM-COPY.zip (2013-09-04), mlv_rec.mo (2013-09-02), dual_iso.mo  (2013-09-01) and all other files from [EOSM]FullbackADTGui.zip (2013-08-30). don't know if that combination should work, but modules doesn't load for me at all.
#3
Tragic Lantern / Re: Tragic Lantern for EOS M
September 05, 2013, 12:00:09 PM
@gary2013:
had not much time for photo and video the last days... last time i tried everything worked fine. but there were also some people having problems with current ml versions on the 650d, because the dot positions changed. maybe they changed the way how the crop offset is calculated. try this dot data file:
https://dl.dropboxusercontent.com/s/j727o0iaho4i3vd/EOSM.txt
#4
Raw Video Postprocessing / Re: PinkDotRemover tool 650D
September 04, 2013, 04:50:52 PM
it's crop mode, isn't it? i have no idea why the dot positions moved. maybe they changed something how they calculate the crop position.
try this temporary dot location file, till we know why the dot positions have changed.
http://dl.dropboxusercontent.com/s/by314z0kb8pfvsb/CropMode.txt
#5
Raw Video Postprocessing / Re: PinkDotRemover tool 650D
September 04, 2013, 03:30:33 PM
hurm, i don't have an 650d, so i can't find the compatibility problem with pdr and the current 650d release.
if you send me a dng that doesn't work i can investigate and fix it.
#6
@rewind and @foorgol:
your pull request is correct. i just didn't merge it so far, since i'm not completely sure if it will perform better in every case. removing the diagonals may lead to problems with diagonal lines.
i'll test both algorithms in multiple situations and do some further investigations if we can improve the algorithm without removing the diagonals. if there is a way to get best of both worlds we may just use a single algorithm. if each algorithm performs better in some situations we may let the user choose.
#7
@rewind:
nice work! it's open source so you're free to share any builds of it.
it would be great if you could make a pullrequest on github, that it could be included into all future pdr versions.
#8
Tragic Lantern / Re: Tragic Lantern for EOS M
August 26, 2013, 07:42:27 PM
@zuzukasuma:

please download this file and replace the one in the dotData dir of your PinkDotRemover.
https://www.dropbox.com/s/j727o0iaho4i3vd/EOSM.txt

that silent dng resolution should work then too. if you find another silent dng resolution that doesn't work, please tell me that i can fix them too. in contrast to the raw movie dngs the silent dng do need special configuration for each resolution.
#9
Tragic Lantern / Re: Tragic Lantern for EOS M
August 25, 2013, 02:31:17 PM
silent dng should work with pdr... if any dots don't get removed upload an example dng please.
#10
if you're interessted in the sourcecode you can check the version with the new interpolation algorithm... very unclean so far, but it's already working with much better results if you want to try it -.-
https://github.com/mixer2/PinkDotRemover/tree/ImprovedInterpolation

it's basically the algorithm from this paper:
http://www.tanbakuchi.com/Publications/Papers/2003AdaptivePixelDefCorPub.pdf

about the IDE... i really don't do any java beside pdr. the only reason i installed a java IDE was because Foorgol wrote the pdr in java and i wanted it to be compatible to the eos m. did some java at the university before... but not much at all. so i don't know much about java IDEs. that said i would always use the IDE the other developers of the project also use. imho it's just a good idea if the whole development team has the same environment. on the pdr i work with netbeans, since Foorgol developed it with netbeans. neatbeans is ok... it's fast and it does work. but, for example, on another project i currently work on, that is written in c++, i use eclipse, because all others working on that project do use eclipse. it would be possible to develop both in eclise or both in netbeans... but just use what the others do. for small new java or c++ projects i would use netbeans, because i have it already installed and i prefer it over eclipse.
if you ask what i think would be the best IDE for java development i would suggest giving IntelliJ IDEA a try. i have never used it and don't have it installed, that's why i said i would use netbeans, which i have already installed, for small projects. since i never used it i'm not sure that it is the best IDE for java development, but i do work every day with PhpStorm, which is from the same company, and it's the best IDE i've ever used.
#11
@Rewind:
current pdr removes all dots for the defined pattern. there isn't any algorithm that checks, if it should fix the dot, or something like that.
there will be a better algorithm for interpolation in the next version which should lead to much less artifacts. have to talk to Foorgol when we'll finish the new version, that you can try it.
#12
Tragic Lantern / Re: Tragic Lantern for EOS M
August 24, 2013, 10:07:06 AM
@CinB13:
can you show me an example of the remaining dots?

@maxotics:
why have you bought the simga 10-20mm instead of the canon ef-m 11-22mm? imho it would be much better choice for eos m, especially for shooting video.
1. much smaller
2. less distortion
3. IS (!!!)
#13
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 10:39:13 PM
sure that ml isn't active? try tapping with two fingers on the screen.
#14
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 07:29:03 PM
@maxotics and Gary2013:

the pdr has a cli you can use to automatically remove dots in your script.
#15
Tragic Lantern / Re: Tragic Lantern for EOS M
August 21, 2013, 02:21:39 PM
you can add as many files as you want to the pink dot remover file list and convert them all.

PDF = pink dot fix?
have you tried to remove dots in the dngs or the raw? can you upload a dng that isn't working?
#16
Tragic Lantern / Re: Tragic Lantern for EOS M
August 20, 2013, 06:02:53 PM
sounds like you're not in movie mode. switch to movie mode and it should work.
#17
Tragic Lantern / Re: Tragic Lantern for EOS M
August 20, 2013, 05:42:36 PM
@maxotics:
if you increase the resolution setting it just crops a larger part of the sensor. if you record 1728 x 684 and throw away 256 pixels from the left and right and 46 pixels from top and bottom, you'll get exactly the same image as you would have recorded 1472 x 592. and this obviously won't affect aliasing effects of the remaining pixels.
of course, if there is less crop, you can increase focal length or put the camera closer to the subject, which may help that the texture isn't fine enough to cause aliasing.

@1%:
i read the pdf and most of the thread. the method described in the pdf sounded really temporary. therefore i thought that it doesn't match the current implementation. i'll check the sourcecode.
#18
Tragic Lantern / Re: Tragic Lantern for EOS M
August 20, 2013, 04:22:42 PM
@maxotics:
changing resolution afaik shouldn't have any impact on moire and other aliasing effects. as markr041 wrote changing to crop mode does dramatically reduce aliasing.

@1%:
again a dualiso question, even if it's not available :)
do you know which exact algorithm is used to calculate the hdr result from the 2 interlaced iso imageparts? is there any documentation, link to a paper or something like that?
i ask, because the af dots on eos m and 650d may cause some problems in that procedure and maybe they need some special treatment. maybe a modified algorithm that is aware of the dots could be included in the pinkdotremover. if there is some info about the algorithm i would check how it may be affected by the dots.
#19
Tragic Lantern / Re: Tragic Lantern for EOS M
August 19, 2013, 01:10:35 AM
oh... nice.
thx!
#20
Tragic Lantern / Re: Tragic Lantern for EOS M
August 19, 2013, 12:42:13 AM
@1%: sorry that i ask again, but i don't know if my question few days ago got read.
do you already know if dual iso may be possible on eos m? that it's working on 600d makes some hope, but since it doesn't work in lv...
#21
Tragic Lantern / Re: Tragic Lantern for EOS M
August 17, 2013, 09:23:09 PM
can you send me a frame as dng? then i'll check why they don't get removed.
#22
Tragic Lantern / Re: Tragic Lantern for EOS M
August 17, 2013, 06:44:12 PM
@gravitatemediagroup:
looks like they should get removed by pinkdotremover. have you used pdr and they're still there?
#23
Tragic Lantern / Re: Tragic Lantern for EOS M
August 16, 2013, 04:01:37 PM
@gary2013:
normally you'll find new versions there:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/

@maxotics:
with crop mode there won't be those aliasing effects at the edge of the glasses.

@gravitatemediagroup:
can you upload a pic to show us the dots?

@manly:
sorry, i don't know the exact details. maybe one of the ml developers may answer it more detailed.
as far as i know there is no way to get the full sensor resolution. and even if it would be possible the cpu is to slow to do any processing in camera. and it's not possible to do the processing in post, because the sd-controller is to slow to save all the data.

@handbanana:
i don't know any details here, too. it's just the way it seems to be on eos m. maybe canon saves some resources in the small body. again, maybe one of the ml developers may give a more exact answer. they know better what's going on in the cameras.
i can just tell you what my experiences using it are. and they are that non crop mode has horrible quality.
#24
Tragic Lantern / Re: Tragic Lantern for EOS M
August 15, 2013, 11:19:53 AM
i think the eos m handles the downscaling different from other canon cameras... but really don't know.
have you watched the video i posted some days ago: http://dl.dropboxusercontent.com/s/p1qo960nrhmcd7g/crop_vs_non_crop.webm

the first 10 secounds show crop mode vs non crop mode... and what i see is that non crop mode has really bad quality compared to crop mode.
maybe 1% can tell you why the downscaled videos on other cameras don't look that bad.
#25
Tragic Lantern / Re: Tragic Lantern for EOS M
August 15, 2013, 10:40:31 AM
@manly:

sorry, no... i think everyone wishes that would be the "only real limitation".
it's not possible to record 5120x2880 because of the speed of the sd-controller. there are 2 raw streams to choose from. one is downscaled via row and lineskipping (which leads to really bad quality) and the other is a 100% sensor crop (1792x1028 cropped from the center).
but, since 1792x1028 are still to much pixels to record (continuously... you can record a few frames till it stops), it's even more cropped to ~5% of the sensor size.
=> you can get thise 5% of the pixels from all over the sensor with a lot of aliasing, or from the center, which leads to a high crop factor.

main limitations are sd-controller speed and the bad quality of internal downscaling.