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

#151
Share Your Videos / FRSP Timelapse - "Cleaning Up"
April 13, 2015, 04:36:34 PM
My first time-lapse attempt using ML's new FRSP function to capture the images. Camera was a 7D.

https://www.dropbox.com/s/8rs8pazegadi498/Cleaning%20Up_0.mp4?dl=0
#152
@chmee.... Thanks
#153
@DeafEyeJdei

Try deleting all existing .IDX files and retry?  Done before each attempt to process - They are never fully built as MLRV crashes almost immediately

Did you try changing FPS Settings? (Shift + F) see if that helps? - I have changed the FPS setting using MLV_Dump to no effect i.e: MLRV still crashes, not able to do it in MLRV.

If not, send me a copy of your MLV's. - The link is to an original file as captured with FRSP.
                                                         https://www.dropbox.com/s/6z2j2irdppappzv/54830000.MLV?dl=0   Be aware, 700mb file

I have also over the last couple of days built a Linux VM in VBOX and have installed MLRV into that. It seems to have installed ok but its not behaving as expected either. e.g.: Can't run the GUI, only via the command line and I'm having a bunch of OpenGL issues with this build.  I don't know if it is a VBOX or a Linux build issue. Way out my comfort zone with this.

I appreciate your assistance with this.


Cheers... Otto
#154
@DeafEyeJedi

MLRawViewer 1.4.3
#155
@g3gg0

Quotewith mlv_dump you should preprocess the MLV file.
e.g. mlv_dump -A 25000 -o out.mlv in.mlv

Tried this with a number of frsp.mlv files and verified the frame rate change via raw2cdng. MLRawViwer is still is still fussy when opening the output files and crashes 100% of the time when attempting to export.
#156
@chmee

Thanks for your efforts in making your app compatible with FRSP mlv's.  Today I have tested v1.7.4 with single and multi-spanned files.

All processed without error and without dropping any frames. A few things:

Is it possible to change the number of threads used into a user definable quantity or is there an ini file that can be modified? I'm not in a position to upgrade my notebook and it works quite hard with the default 4 threads.

MLV_Dump has the ability to change the frame rate via the -A parameter. Adding this feature to raw2cdng would eliminate the need to do this as a separate workflow step when working with FRSP or any timelapse MLVs. Just a feature suggestion.

Lastly, the following images are the same image and frame using both raw2cdng and MLV_Dump apps. On the image extracted via raw2cdng there is a black border an the left and top of the image. This does not occur in the MLV_Dump extractions.

A close visual inspection of both images suggests that the image is there in its entirety within the raw2cng image. Ideally, it would be better to have the DNG created without the black borders and thereby eliminate the need to crop and possibly stretch each frame in post.

Using raw2cdng
https://www.dropbox.com/s/gdrizkeyqtk7y87/5489000000005.dng?dl=0

Using MLV_Dump
https://www.dropbox.com/s/1eab8emt0c73c3x/5489_000005.dng?dl=0

Just some feedback and thoughts.  Thanks again for your ongoing support and development of this app.

Cheers.... Otto
#157
@chmee - excellent, thanks.

Happy to test for you.
#158
Sorry everyone for the long post, but I thnk that it s important for Windows users to be aware of what does and doesn't work re FRSP.mlv file extractions.

@g3gg0

Thanks for the reply. The actual parameter was -A <fps>. This had no impact.  I was however able to extract the images via the -dng parameter.

As general feedback, after more experimenting today, the below table is a summary of my experience trying to extract FRSP images from MLV files (in the windows world).

Extraction
Application        Comments
---------------    -----------------------------------------------------------------------------------------------
MLV_Dump      Successfully extracts the dng's from all frsp.mlv files attempted. With one exception the
                      quality of the images extracted was as expected. All the images extracted from the exception
                      MLV had significant artefacts (green spots) rendering them unusable. The images were
                      extracted again using mlv2dng and there were no artifacts nor were there any on the control
                      CR2 image taken. (ref examples below)

MLV2DNG       Successfully extracts the dng's from all but 1 of the frsp.mlv files attempted. The following
                     error/warning message is displayed for each file processed.
                          "Exception! Header not recognized: 'STYL'".
                     The one major issue with this aplcation is that the image off-sets are incorrect in the resultant
                     dng files (ref: example below).

MLRawViewer v1.4.3     Loads the files and allows preview but crashes on export - all frsp.mlv files

raw2cdng v1.7.1           Loads the files and allows preview but crashes on export - all frsp.mlv files

Pismo File Mount           Fails to mount ant frsp.mlv files - crashes

WebDAV                      Doesn't support mlv files. Still need to try using MLV_Dump to convert the files to
                                  standard raw and see if that works.


Below are example images highlighting the MLV_Dump artifacts issue (note that this only occured in one of the frsp.mlv files processed).
The MLV2DNG extracted image also highlights the image off-sets error (Black border across the top and the left hand side of the image)

MLV_Dump extracted image
https://www.dropbox.com/s/gutb5jl56pjf615/MLV_DumpTest_5496_000005.dng?dl=0

MLV2DNG extracted image
https://www.dropbox.com/s/vqq1y8x6ir8c6rn/MLV2DNG_Test_5496_000005.dng?dl=0

Canon CR2 image
https://www.dropbox.com/s/1l8h20b3lkzcr4g/IMG_5496.CR2?dl=0

@Kharak,
This may answer your questions, if not pm me please. Just remember when capturing tha the camera must be in manual mode and liveview (not movie mode} exposure should be 1/15 of a second or slower (Alex please correct me if this is no longer true). A variable ND filter will help with his.

I'm still having fun and games getting my exposures right. A topic for another post after a controlled test that I have in mind.
#159
@dmilligan,

Thanks.  I'll look into the vm option. never set one up before, so a first time for everything.
#160
@dmilligan

I have an old Pentium 3 at home. Might have to dust it off and make a Linux box out of it. (slightly off topic.... any recommended distro?)

The good news for now is that I managed to extract the DNG's using MLV_Dump.
#161
Firstly, well done to Alex and everyone else involved in developing/testing FRSP.

I have been using/testing it over the last few days capturing stills in DNG as well as MLV format. I have also taken a number of FRSP timelapse captures in MLV format.

From a capture perspective, all appears to be working correctly. I can review the DNG's and MLV files within the camera.

Unfortunately, after transferring the files to my PC I am not able to process the MLV files. Methods tried are:
mlrawviewer v1.4.3:
      Can navigate to the file location but it stops responding and hangs when trying to open the file.
      Individual files contain from 4, 16, 20, 110 and 150 frames.

raw2cdng v1.7.1
      For MLV files containing 4 frames it completes the extraction process but only extracts 3 of the 4 frames.
      For MLV files containing more than 4 frames, the file loads into the batch queue correctly and it can previewed.
      however when trying to convert, the application crashes with the following windows error:
                 Problem signature:
                 Problem Event Name:   CLR20r3
                 Problem Signature 01:   raw2cdng.1.7.1.exe
                 Problem Signature 02:   1.67.0.0
                 Problem Signature 03:   551fe5f8
                 Problem Signature 04:   mscorlib
                 Problem Signature 05:   4.0.30319.34209
                 Problem Signature 06:   534894cc
                 Problem Signature 07:   2bd7
                 Problem Signature 08:   8
                 Problem Signature 09:   N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
                 OS Version:   6.3.9600.2.0.0.768.101
                 Locale ID:   3081
                 Additional Information 1:   5861
                 Additional Information 2:   5861822e1919d7c014bbb064c64908b2
                 Additional Information 3:   a10f
                 Additional Information 4:   a10ff7d2bb2516fdc753f9c34fc3b069

Pismo File Mount:
      Unable to mount any FRSP MLV file. The application crashes with the following windows error:
                   Problem signature:
                   Problem Event Name:   APPCRASH
                   Application Name:   pfmhost.exe
                   Application Version:   1.0.0.175
                   Application Timestamp:   5517b2bd
                   Fault Module Name:   StackHash_c488
                   Fault Module Version:   6.3.9600.17668
                   Fault Module Timestamp:   54c850f5
                   Exception Code:   c0000374
                   Exception Offset:   PCH_C4_FROM_ntdll+0x000000000009133A
                   OS Version:   6.3.9600.2.0.0.768.101
                   Locale ID:   3081
                   Additional Information 1:   c488
                   Additional Information 2:   c4887998465a0053994a59c41760d391
                   Additional Information 3:   a2d1
                   Additional Information 4:   a2d1fc25570421d6d613ec3976b986db

Camera:       7D
ML Version:  April March 30 nightly build
PC OS:         w8.1, 8gb ram, 500gb HD.

I'm at a loss re: what to try next. any suggestions?

Cheers....Otto
#162
For those of us using the PISMO file mount utility in Windows for our MLVS files:  It works fine for normal MLVS videos but won't mount/open an MLVS file created via FRSP Silent_Pics.
#163
Done.

https://www.dropbox.com/s/lrcyydx5re98ysq/7D_Magic_Rescue_screenshot.jpg?dl=0

My original attempt failed due to the CF card having had its bootflag reset (probably something that I did the last time I used it)

For the above screenshot, the image was displayed without my needing to power on the camera. (is this how it should work?). I had to remove and reinsert the battery in order to get the camera working again.

Cheers
#164
Thanks for the reply. That's what I did,  Just replaced the autoexec.bin on one of my ML CF cards.
#165
Loaded this onto my cf card (7D). When I turned on the camera, the led flashed a couple of times and nothing.

That is:
- no image appeared on the screen
- ML didn't load
- canon menu operational

The autoexe.bin used was downloaded from the link in Alex's 1st post.

Should I be doing anything else to "run' it?
#166
With the 7D set in 'M'anual mode I am no longer able to adjust the exposure compensation.

Upon investigation I discovered that the large thumbwheel appears to be mapped to the "Bracketing" exposure control normally linked to the small thumbwheel. Note that the 'Bracketing' exposure control was still associated with the small thumbwheel at the same time. (this is a repeatable problem)

Also, when I switched from 'M'anual to 'AV' mode and tested the exposure override it worked as per normal however, whilst making the adjustment, the camera froze. Battery removal was required to power down and reset the camera. I could not reproduce this on demand so will monitor this.

Auto ETTR seems to be a workaround for the lack of manual exposure control but it needs to be fixed.

Cheers.... Otto
#167
Thanks for the builds licaon_Kter I will endeavour to test over the next few days. In answer to your question re: the 7d Builds:

Quote6. For 7D there are 2 builds, maybe 7D owners know why/how.

I have downloaded both. From what I can see the magiclantern-Nightly.2015Mar25.7D_MASTER203_DoF_FRSP_commit5ce2235.zip file does NOT include the following files:

-  7D_203.fir at the root level
-  7D_203.sym in the modules folder

That would suggest the build contained in file "magiclantern-Nightly.2015Mar25.7D203_DoF_FRSP_commit5ce2235.zip" is the correct one to download and test with.

Cheers... Otto
#168
If I was able to code I would. Unfortunately I can't hence my request.

I don't have the facility to compile either.

Always willing to test though.
#169
Hi,

Any chance of a fresh build for a 7D please.

Cheers.... Otto
#170
Share Your Videos / Re: Falls // 7D Raw
March 21, 2015, 09:30:48 AM
Thanks
#171
Share Your Videos / Re: Falls // 7D Raw
March 19, 2015, 02:21:01 AM
Nice, what resolution / crop modes did you use?
#172
Hi,

DeafEyeJedi was kind enough to forward me a link to this thread and I have tested the full-res silent.mo posted by g33g0 on 2015/01/16.

Below is my feedback on the tests performed:

Just as background, my 7D is running the latest nightly build dated 2015/01/15.

Initially I overwote the files on my CF card with those downloaded from g33g0's links dated 2015/01/16 (autoexec.exe, 7D_203.sym, silent.mo and mlv_rec.mo files).

Upon starting the camera the following errors were displayed and none of the modules loaded. This is similar to DeafEyeJedi's initial experience.

Quotetcc: err: undefined symbol 'is_native_movie_mode'
tcc: err: undefined symbol 'is_custom_movie_mode'
[E] faqiled to link modules

I then:

       
  • Formatted the CF card in the camera and retained ML
  • Deleted the autoexec.exe file and all of the modules and settings files from within the ML directories.
  • Then copied the files supplied by g33g0 to their respecitve locations on the cf card.
  • Loaded the card back into the camera and was then able to successfully load the silent and mlv-rec modules. (note that these are the only modules on the card).
Time to test:

Test 1: Silent pics - full-res, DNG format images, no intervalometer.
            Sunny with light clouds, ISO, 100, 200 and 400, f5.6

           Result: failed.  Error message "exposure too long"

           Interesting given that the indicated exposure on the top screen was 500th of a second or greater.
           Reverting back to simple silent-mode resulted in images being captured as expected.

Test 2: Silent pics - full-res, DNG format images, intervalometer enabled.
            Sunny with light clouds, ISO, 100, 200 and 400, f5.6

           Result: failed.  same as test 1, Error message "exposure too long" and no images taken
                                   (note the intervalometer did cycle through it's range as per its paramaters).

Test 3 & 4 : Silent pics - full-res, Multi-MLV and Single_MLV format images, no intervalometer.
                  Sunny with light clouds, ISO, 100, 200 and 400, f5.6

                  Result: failed.  same as test 1, Error message "exposure too long"

I don't have the tools or skill to grab the source codes and recompile a custom build. Any thoughts, on what the issue may be?
(Happy to test any new versions)

Also, I haven't tried to test the MLV-REC.mo yet as I don't know what has changed and as such, don't know what sort of testing is required. If someone can enlighten me I'll put this module through its paces as well.
#173
Quotegreat. thx dmilligan.
so we now only need silentpic fullres working for canon 5d mk3 123 :))))
5 month no progression.. hope alex is back soon..

And the 7D.....  ;)

Cheers
#174
How do you get the BarracudaGUI settings dioalogue box to appear as in the first post or has it been done away with?

Sorry, found it.
#175
Canon firmware v2.0.3 is a requirement as the current version of ML has been written around this version. Getting it from the Canon site is fine and yes you can upgrade from your current firmware version directly to v2.0.3.

Note: do not use any other version of Canon firmware as ML is not compatible with them.

Installation instruction and guides can be found for ML here http://wiki.magiclantern.fm/install

Take the time to read the instructions and please use search in the forum to try and find answers to your questions. I personally found, and still find this an invaluable way of learning the do's, don'ts and functioanality of ML.

From a 7D owner, The latest nighlty build of ML for the 7d is very stable.