Messages

@AWPStar ...... Merry Christmas and a Happy New Year. Thank you for your efforts in developing MLVP this year. It really is an excellent product that gets better with each release.

Just an fyi.. I was trialling the v1944 alpha build and came across a issue with the saved presets that needs to be addressed as follows:

Save Preset under the "Edit, "Maze" and "Correction" results in preset files [name].prst1, [name].prst2 and [name].prst3 being created in MLVP/data/presets folder as expected.

Saved presets are listed under the "Edit" and "Correction" menu only. Presets saved under the "Maze" menu are not listed and there is no alternate "load preset" option available and as such the "Maze" saved presets are unusable.

Something else to consider:
I can see the sense in individual preset save modes however you might like to consider a save preset function (maybe under the "File" menu) that saves all of the settings for the active video clip to a single preset file.

If its easy to do then the answer to your question is self evident.

If it's hard or costly,  then it becomes a cost benefit decision.

Sounds like an incompatible format type on the cf card. Or some activity done on the 7D2 has caused it to be incompatible with the 7D.

Suggest that you take one card and reformat it to default ntfs settings on your computer then reinsert into the 7D. If the 7D recognizes it,  reformat in the camera. Make the card bootable and reinstall ML from the latest nightly.
If that works l'd also suggest having separate cards for each camera.

Shared links?

The 7D led doesn't blink when you open the card door.

I've been using ML on my 7D since its release and have not experienced any battery drain that I would attribute to an ML issue. i.e I have disabled the auto power off function in the canon menu and then subsequently forgotten to switch the camera off - human error each time.

I've also been very disciplined in my card removal/insertion process to minimise the risk of card corruption. It seems to work as I've not lost or corrupted a CF card yet.

Removal
----------
Power off the camera and wait for the led to stop flashing
Open the card door and wait for 5 seconds
Remove the card
Close the card door (prevents dust getting in)

Insertion
-----------
Open card door and wait a few seconds to give the Canon firmware time register that the card door is open.
Insert the CF card and wait a few seconds to give the Canon firmware time register that a CF Card has been inserted.
Close the card door and wait a few seconds to give the Canon firmware time register that the card door has been closed.
Power on the camera

Maybe some of the delays are unnecessary but it works for me. I also never change cards without powering off the camera.

If the tools you want don't work on an Apple PC then maybe consider buying a Windows PC. The Dual ISO tools work fine on Windows.

Plenty of really cheap (< $300) pcs that will do the job just fine.

@AWPStar.... Thanks

@AWPStar
A small issue with v1931.  There are two window expand buttons both of which will expand the MLVP window to full screen on the primary monitor.

https://www.dropbox.com/s/xnhsvzza37gpcjl/MLVP_Screen_minmax_buttons.JPG?dl=0

Also, a reminder that the application is not supporting multiple monitors correctly. It needs to keep track of which monitor that its window is on and treat that as its active monitor.

Lastly a suggestion for a post beta enhancement:
Full support for Full Resolution Silent Picture (FRSP) MLVP files.  A 19 frame sample file is available at the following link:
https://www.dropbox.com/s/vjj2bg5e96fmobn/54820000_Gravillia_FRSP_TL.MLV?dl=0

Interestingly MLVP does open the file and appears to already support it however the performance was really bad (slow). I think the sheer frame size is main culprit.

Cheers... Otto

Hi,

I was experimenting with CDNG and DNG exporting with version 1928 today. Both exports seem to work ok.

I don't have any adobe editing software and use CyberLink PhotoDirector (v7) and /or RawTherapee to edit my raw/dng images.

I'm running a w10 pc with the Adobe DNG codec installed.

If I double-click on either the exported CDNG or DNG image both are successfully opened in the windows default photo viewer application. The CDNG image appears a bit washed out vs the DNG one but this can likely be adjusted in photo editor. The main point that I am making here is that both export images can be opened and viewed.

The issue that I came across is that only the CDNG exported dng files can be opened in both CyberLink PhotoDirector and RawTherapee  whereas the DNG exported dng files cannot.

CyberLink PhotoDirector  returns the error "Unable to Decode the Master"

RawTherapee decodes the images and presents them as solid Black. (images are opened using the RawTherapee defaults settings)

Samples below

https://www.dropbox.com/s/orn8rni3rwopgf7/M24-082100000.dng?dl=0 image exported as CDNG
https://www.dropbox.com/s/klyzgz7e560qrae/M24-0821_dng00000.dng?dl=0 image exported as DNG
https://www.dropbox.com/s/arbao5ncbq0d66z/M24-0821_dng00000.dng.pp3?dl=0 RawTherapee sidecar file for image exported as DNG

Given that both images can be viewed successfully with Windows Photo Viewer I suspect that there are required metadata correctly populated in the CDNG export file that are either missing or not correctly populated in the DNG exported files.

Cheers... Otto

@AWPStar

Thanks.  Also, ignore my comment about collapsing the tool panels. I figured out how to do it.

Cheers

Wow, love this new version.

The only issues that I have found with the UI are:

1) The application window is not maintaining is monitor referential integrity. 

when I drag the application window to my external monitor and double click the title bar or click the maximize button to maximize it: it jumps back to the laptop screen and maximizes instead of maximizing on my monitor (screen 2).

I can manually stretch the application window to make it fill the screen to get around this issue.

2) there were instances where the render button was not visible and there doesn't appear to be any means of collapsing individual tool panels or to scroll the frame where the tool panels are docked.
I could get around this by undocumented the required panel.

You've really taken this app to another level since the I last tested it.  Well done.

Upgrade your pc to w8.1 or w10. The apps all work well on these versions of windows.

You could try using a variable neutral density filter to give you longer exposure times.

Some awesome changes. Can't wait to put it through its paces.

@AWPStar

Thanks. Pm'd you the test results.

@AWPStar

Just some more feedback. I have now tested v605 on 4 different computers.

1 x w8.1 professional
1 x w8.1 home
1 x w10 Enterprise
1 x w7

All Are 64 bit versions of the OS and all exhibit the same behaviours as previously reported.

One thing that I hadn't tried previously was adjusting the sliders prior to loading any MLV clips. What I discovered was that I could adjust the slider +/- and the highlight would appear relative to the amount of slide applied. However the value of the amount of slide applied was not calculated and presented in its value box.

The following links are screen shots demonstrating the behaviour:

https://www.dropbox.com/s/5mnmglw6erzl2ci/MLVProducer_Slider_Issue_1.JPG?dl=0
https://www.dropbox.com/s/2wjqt57w4j3gaza/MLVProducer_Slider_Issue_2.JPG?dl=0

If I then subsequently loaded an MLV clip (via drag n' drop) I got the following error:

https://www.dropbox.com/s/z6ik1y7mqcfmqnc/MLVProducer_FileLoad_Issue_3.JPG?dl=0

I know that you have previously mentioned that you are unable to reproduce the errors that I have reported re: the sliders (and I accept that to be true). Given that I have 4 different computers with various versions of Windows and all exhibiting the same behaviour, it suggests that I am missing something.

Are there any per-requisites that I've overlooked or am not aware of re:

32bit vs 64bit OS versions?
Run time libraries?
Graphics Card/Chipset  compatibility? eg: Intel HD vs Nvidia vs Radeon etc
OpenGL compliance?
Minimum memory requirements? all have 2gb or >
Other?

I have validated that my processors support MMX and SSE

So now that you have a proper cf card why not give it a go?

@AWPStar

To my knowledge both are standard installs. I tend not to fiddle with the os settings (If it ain't broke I don't fix it).

What code changes if any have been made between alpha 2 v the current release?

[Note]

@AWPStar

I don't really understand what the problem do you have with sliders. Its smooth and accurate. Left click to set value,mid click to reset value, shift to improve accuracy.
What OS do you use?

I have tested this on two different laptops with the same result.

My primary laptop is an ASUS S550C (w8.1 pro, Intel HD graphics driver). The following link is a screen shot of it specifications.

https://www.dropbox.com/s/6u8eealwc62tc0q/Computer%20Spec.JPG?dl=0

The other laptop is a DELL Latitude E6400 (w10, Intel HD mobile graphics driver)


The following link is a screen shot highlighting the slider issue:  https://www.dropbox.com/s/gue4cf5r6hugxnn/MLVProducer_Sliders_issue.JPG?dl=0

The Black Slider works perfectly (including the mid click and shift for accuracy controls).

The same is not true for the White Balance and Correction sliders:

   
• If you look at the values of the White Balance and Correction sliders vs the highlight of each slider you will see that they are not aligned with each other. The example was obtained by applying a single left mouse click in each of the sliders. A second left button mouse click (after a brief delay) will align the highlight with the slider value.
• Holding the left mouse button and dragging left or right will adjust the values of the control (visible in the value box) however the highlight always displays the extreme (positive or negative relevant to the drag direction). Again, a second left button mouse click (after a brief delay) will align the highlight with the slider value.
• The Mid click centering control does work for each slider.
• The Shift/Accuracy functions works for each slider as well however slider highlight jumps to the extreme (positive or negative relevant to the drag direction).

Note that in the mlvp.alpha.build002 all of the sliders work correctly as per your latest feedback as well as the entry of decimal values where appropriate.
        The only issue that I have observed is this build is that I can enter values greater than than the min/max values intended for the individual parameter.

Cheers.... Otto

@AWPStar

Have sent you a PM with testing feedback for v.605

[Correction]

@AWPstar

I have been testing MLVProducer Alpha build 556 on both a W8.1 laptop. Some feedback below.

   
• The initial size of the size of the application screen, whilst a windowed screen is larger than most laptop screens (e.g.: 15.5inch).
  I have a larger second screen that I can use and as such this is not a issue for me. I'm sure that there a many users for whom the Laptop is their primary screen.
  Maybe consider changing the the app to open in a smaller windowed size or just open into full screen mode on in the primary monitor. This may require interrogating the OS to determine the primary monitors size and then scaling accordingly.
• It successfully opens standard video MLV files as well as FRSP MLV files however I was only able to do this by dragging and dropping the file on the video preview screen. The file open dialogue allows me to select the file but then doesn't load the file.
• The app allows for multiple MLVs to be loaded however when attempting to minimise the active video window the entire app is minimised.
  On this theme, if multiple MLVs have been loaded,  via experimenting, I discovered that I could switch between videos by double clicking the relative entry in the render queue. If this will be the standard method for switching between videos within the app, then being able to minimise the clip window becomes unnecessary and could be removed.
• The adjustment sliders have become unusable as any attempt to adjust the values by sliding results in it jumping to the maximum values.
  Double clicking on either side of the center mark allows a more granular selection but with zero accuracy.  Entering values directly in the value boxes only works if whole numbers or 0 are entered. (in the alpha2 version the sliders worked as expected).
• I have added a number of addition LUT files into the \data\luts folder. It now contains 62 LUT files. The colour LUT selection dialogue cannot handle a large quantity of LUT files and needs to be modified such that it presents the available files in a scrollable list.
• Rendering a clip results in no output file being generated irrespective of whether the default out location and file names are used or alternate locations and file names used.
  Correction - If I set an in and out point, rendering results in a file being generated. I suggest that by default it should render the entire clip if in and out points have not been specified.
• When rendering the same clip again I received a "File is already exists" message. I can see many reasons why someone may wish to render a clip multiple times (e.g: different parameters, LUT etc.). This can be overcome by manually adjusting the file name however I suggest automatically appending a date and time stamp or an incremented number to each rendered clip and thereby giving it a unique name.
• I received an out of memory run time error Although I had 2.5gb of available memory. Reproducible while performing the following:
  -  Loaded 4 clips
  -  Switched from the active clip to another
  -  modified the black level, exposure and local contrast
  -  Applied a LUT
  -  set an in and out point
  -  Switch to another clip
  -  Switched back to the previous clip where the adjustments had been made
  
  The out of memory error consistently occurred when switching from the active clip to an alternate or to the alternate and then back to the clip where adjustments were made.

Happy to test releases as you develop them, maybe provide a list of changes in the release notes so that we know what to test.

Canon 7D
------------

Immediately after the camera is turned on.

https://www.dropbox.com/s/12p8ijguoy6big0/VRAM0.PPM?dl=0

Live View turned on

https://www.dropbox.com/s/fa8exuqqsi4fehw/VRAM1.PPM?dl=0

Live View on, after picture taken

https://www.dropbox.com/s/jfpwszk3ho2ztax/VRAM2.PPM?dl=0

Whilst capturing video

https://www.dropbox.com/s/d9uhgw57205m3gu/VRAM3.PPM?dl=0


Cheers.... Otto

Nice... Even works on my mobile.

I can confirm that the "leave menu" works fine. Also, Even though your camera will likely be on a tripod, I would also set a start delay of a few seconds. Just a bit of insurance  to ensure that there is no camera shake due to a heavy handed button presses when exiting the menus.

@DeafEyeJedi

Thanks for testing the clip out for me. It looks like the issue is in my PC although I can't think what at the moment (W8.1 professional, 6GB ram, Intel i5 processor, Intel HD graphics).

Are there any dependencies that I need to install? i.e. my old notebook had Python and Pearl installed?

Cheers... Otto