Messages

As I am want to do, I tried combining the old, hacky, but still functional 5d2 dual_iso module I had laying around with the exciting new 3K experiments on the 5d2.  However, I am met with a note on the module saying that it is an old API. "Expecting 7.0".

So it appears that a new attempt at dual_iso on the 5d2 might be timely. Hope someone is willing to give it a shot!

Appreciate it! However, I am getting some errors when I load raw_diag.mo and adtg_gui.mo

https://drive.google.com/file/d/1k9bWM2Wz3gorjws2lC36iam9-ngTwFau/preview

I've been enjoying keeping up with this thread, but I'll admit that changing registers is a bit above my skill level. I'd really appreciate a step-by-step to try some of this out on my 5d2.

I've messed with DSLR Controller and Raw... definitely not ideal.  I believe it wasn't possible to trigger video via the app, but it was possible to see the phone screen during recording. Could be wrong as this was a long time ago, on my 5d2.

Normal video recording, however, works fine. I believe DSLR controller has a 1:1 pixel feature, too.

Some of us watch this thread for actual developments and not speculation, please have this discussion somewhere else.

@Masc - For a 5 frame, 12bit dual-iso clip it took 23 seconds from clicking "save" to convert to H.264. Not amazing but could be a lot worse. I'm running an Acer R11, Intel Celeron CPU N3160 @ 1.60GHz, 4GB Ram.

For standard conversions I'm getting about 2 frames a second.

My guess is a Pixelbook or any of the as-of-yet overpowered chromebook offerings would perform pretty damn well.

I've been playing around with Linux more in anticipation of native Linux container support in ChromeOS (codename Crostini), possible only on the Pixelbook but getting pushed out to most recent models probably within the year.

@all
guide for compiling Mlv-App (english) in Linux: https://sternenkarten.com/tutorial-englisch/
This guide is updated now too.

I was still having problems with qmake, unfortunately.  Wanted to let you know that I think "gitclone" should be "git clone" in your translated instructions.

Please try out and report if it works (success on Ubuntu 14.04 and 18.04).

Just tried it on Kubuntu 16.04 and it was very easy to get going.  Already processed a dual-iso video on my chromebook, very pleased. This puts chromebooks on the map for me in a real way!

Still having trouble compiling, anyone mind helping me? I'm running 16.04

Code Select Expand


$ make
g++ -std=c++11 -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DSTDOUT_SILENT -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o MainWindow.o MainWindow.cpp
MainWindow.cpp: In member function 'uint8_t MainWindow::drawZebras()':
MainWindow.cpp:2913:34: error: 'class QImage' has no member named 'pixelColor'
             QColor pixel = image.pixelColor( x, y );
                                  ^
MainWindow.cpp:2918:23: error: 'class QImage' has no member named 'setPixelColor'
                 image.setPixelColor( x, y, Qt::red );
                       ^
MainWindow.cpp:2925:23: error: 'class QImage' has no member named 'setPixelColor'
                 image.setPixelColor( x, y, Qt::blue );
                       ^
MainWindow.cpp: In constructor 'MainWindow::MainWindow(int&, char**, QWidget*)':
MainWindow.cpp:58:70: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result]
     chdir( QCoreApplication::applicationDirPath().toLatin1().data() );
                                                                      ^
Makefile:905: recipe for target 'MainWindow.o' failed
make: *** [MainWindow.o] Error 1


I think you have to use -std=c++11 on g++ options... at least that's what the error log is saying.

Thanks! Way out of my depth here - g++ is a different compiler method than qmake, right? Or should I just add some specifications to the qmake or make commands?

Code Select Expand

(xenial)jessepeej@localhost:~/MLV-App/MLV-App-master/platform/qt$ qmake
(xenial)jessepeej@localhost:~/MLV-App/MLV-App-master/platform/qt$ make
/usr/lib/x86_64-linux-gnu/qt5/bin/uic MainWindow.ui -o ui_MainWindow.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic InfoDialog.ui -o ui_InfoDialog.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic StatusDialog.ui -o ui_StatusDialog.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic ExportSettingsDialog.ui -o ui_ExportSettingsDialog.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic EditSliderValueDialog.ui -o ui_EditSliderValueDialog.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic Updater/updaterUI/cupdaterdialog.ui -o ui_cupdaterdialog.h
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DSTDOUT_SILENT -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o main.o main.cpp
In file included from Updater/updaterUI/CUpdater.h:11:0,
                 from MainWindow.h:38,
                 from main.cpp:8:
Updater/updaterUI/../cautoupdatergithub.h:52:2: warning: identifier 'nullptr' is a keyword in C++11 [-Wc++0x-compat]
  UpdateStatusListener* _listener = nullptr;
  ^
In file included from Updater/updaterUI/CUpdater.h:11:0,
                 from MainWindow.h:38,
                 from main.cpp:8:
Updater/updaterUI/../cautoupdatergithub.h:33:20: error: 'function' in namespace 'std' does not name a template type
         const std::function<bool (const QString&, const QString&)>& versionStri
                    ^
Updater/updaterUI/../cautoupdatergithub.h:33:28: error: expected ',' or '...' before '<' token
         const std::function<bool (const QString&, const QString&)>& versionStri
                            ^
In file included from Updater/updaterUI/CUpdater.h:11:0,
                 from MainWindow.h:38,
                 from main.cpp:8:
Updater/updaterUI/../cautoupdatergithub.h:35:67: warning: defaulted and deleted functions only available with -std=c++11 or -std=gnu++11
  CAutoUpdaterGithub& operator=(const CAutoUpdaterGithub& other) = delete;
                                                                   ^
Updater/updaterUI/../cautoupdatergithub.h:50:13: error: 'function' in namespace 'std' does not name a template type
  const std::function<bool (const QString&, const QString&)> _lessThanVersionStr
             ^
Updater/updaterUI/../cautoupdatergithub.h:52:36: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11
  UpdateStatusListener* _listener = nullptr;
                                    ^
Updater/updaterUI/../cautoupdatergithub.h:52:36: error: 'nullptr' was not declared in this scope
In file included from MainWindow.h:38:0,
                 from main.cpp:8:
Updater/updaterUI/CUpdater.h:28:67: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11
     void onUpdateAvailable(CAutoUpdaterGithub::ChangeLog changelog) override;
                                                                   ^
Updater/updaterUI/CUpdater.h:29:61: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11
     void onUpdateDownloadProgress(float percentageDownloaded) override {Q_UNUSE
                                                             ^
Updater/updaterUI/CUpdater.h:30:35: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11
     void onUpdateDownloadFinished() override {};
                                   ^
Updater/updaterUI/CUpdater.h:31:44: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11
     void onUpdateError(QString errorMessage) override {Q_UNUSED(errorMessage);}
                                            ^
Makefile:849: recipe for target 'main.o' failed
make: *** [main.o] Error 1



Anyone have a guess what I did wrong?   

Why do you use v0.8 (released 227 days ago) when v0.15 (latest) is out? Link

Edit: Ahh.. yes because of the only linux release MLV.App.v0.8.alpha.x64.Linux.AppImage

If on Crouton XFCE4 can be installed Linux version of QT 5.9 you could compile latest Git version on your chromebook.

I'm such a noob - any chance you could point me to a tutorial that could get me started?  I've never compiled nothing

Very low priority issue here, BUT

I tried out QTv0.8alpha on Crouton XFCE4 on my Chromebook Acer R11.  The machine isn't cut out for this kind of work but I wanted to see if I could use it for MLV processing in a pinch.

Crouton on Chromebooks is already hacky, so I didn't have high hopes, but MLV App worked as expected except on export - it only gets to 50% and instead of putting out a movie it puts out PNG frames.

Again, I doubt anyone is seriously depending on a Chromebook for this kind of work but I thought I'd report it as Linux container support will (fingers crossed) soon work natively within ChromeOS.

Very nice lighting and color work - really impressive.  Would you mind talking about the turntable a little bit?  I've been considering building something like that of my own but I have very little experience in the field.

There is an Audio tab in the menu that has an option for Analog Gain.  Also make sure that sound recording is enabled and on manual in the Canon menu.

Set that to whatever you need and check audio levels with the ML menu enabled in Liveview (Press display until you see audio levels)

This: https://drive.google.com/open?id=19ZgqOpGWgs0af6HF0DFAqVh7ZYdacsbg

It's an old module that was being tested on the 5D2.  I don't have any documentation on who created it.

You can replace the old dual-iso module in your modules folder on the card with this one.  No need to reinstall ML. Just drag and replace.

You will probably have varying degrees of luck with different programs in trying to convert and view these easily.  I highly recommend MLVApp.

Yes - and the MLVapp developers have made it work pretty flawlessly. I can do dual-iso 12bit with darkframe subtraction to get some pretty nice frames.

I know someone questioned why I'd pair 12bit with dual iso as 12bit loses some dynamic range, but I find that to be an ideal combination, especially with continuous shooting being an option at 12.

I'm using it for 12-bit & dual-iso and haven't had any serious problems beyond the ones you mentioned.  I also haven't tested it in that many conditions yet - I'll try HDMI soon and report back.

USE WITH EXTREME CAUTION.

I'm such a 5D2 Stan that I tried pairing this with the experimental Dual Iso module, and the experimental 10/12 bit broken 3x crop build and MLV Lite.  Camera initially seemed to be performing at 1DX / Alexa Mini levels but started smoking and I got an error 20.  Currently unusable and has serious fogging on the screen.

Edit:  Damnit.  What's it called when you are tricked into thinking something is a trick?  100% thought everything a1ex posted was fake.

Yeah, had this same problem after upgrade.  I liked MLRawviewer a bunch because I knew it very well, but have switched to MlvApp now and am enjoying it's robust features, while still getting used to some of the basics of image control.

Check out Switch, too, it has some pretty robust features that could make your life easier working with prores.

@jpegmasterjesse, @Danne

Anyway using dualiso means wide DR is needed, data bits less then 14 already restricts DR and this makes no sense b/c, during 14bit lossless raw recording, writing speed is good enough.

Interesting - do we know the exact degree to which bit reduction reduces dynamic range?

I still greatly appreciate the easy work-arounds, in this case, as the 5d2 build I used to create the dual-iso 12 bit .mlvs has dysfunctional 14bit raw (I should test this again to be sure.)

@jpegmasterjesse

I guess you already have switch so grab mlv_dump from it and with this command convert bit depth:

Code Select Expand


./mlv_dump -b 14 -o output_14bit.mlv your_12bit.mlv

Then try to open it in MLV App, process as dualiso and report back please.

I wish I had the necessary knowledge! I'm a bit out of my depth.  Here's the 12 bit dual-iso file:
https://drive.google.com/open?id=1W9IG53Nn-AG1EWKV-trCVyfpPNt5VtTA

Can you also upload the dark frame original (not averaged) MLV for this 12bit clip?

Here you go!
https://drive.google.com/open?id=1pMlInFFL2kb-TXY6rPeVbJTiWG8OXiYK

It is possible and g3gg0 was doing this long time ago for experimenting/developing. However I can not imagine the use case of that backward conversion now

After a (forced) update to High Sierra I am short on workflows for raw.  I used to use MLraw viewer but the .mov export no longer works on High Sierra.  MLVApp can't import DNGs (as far as I know) and premiere doesn't like the sequence either.  Even Lightroom crashes kinda frequently  after importing these  DNGs (although it's also been crashing dealing with standard 20bit dual iso files.) I haven't tried after effects yet.

So yes, it is backwards, but I'm low on options.

I will upgrade the dark frame in a few hours! It may not have actually worked as I tried it - it automatically ran dark frame subtraction without me providing mine.

Loving the app!  There is an old experimental version of the dual-iso.mo for the 5d2 that actually works pretty great!  The tough part was finding a post-processing workflow that worked for it.  The current version of switch works fine.

Unfortunately MLVApp has a hard time doing anything with it - my guess is that it's almost certainly a black level issue.

As I'm a complete fool for bleeding edge 5d2 stuff, I paired this experimental 12/10 bit build: https://www.magiclantern.fm/forum/index.php?topic=5601.msg198349#msg198349
with the dual-iso module, and attempted to do some darkframe subtraction as well.

Normal (non-dual) 10/12 bit stuff from that build works just perfectly in MLVApp.

By turning Switch to default settings, and then setting it to full-auto I was able to do 12 bit, dual-iso, darkframe subtraction in one fell swoop - which felt lucky.

Here's the problem - I end up with converted DNG's and would like to import them into MLVApp for editing/organizing.  I don't know of any way to repackage DNG's back into an MLV.

I know that's a lot of info, but I included some sample files, including the experimental Dual-Iso module here:
https://drive.google.com/open?id=1O2P64L0uvF3ai2GPuj3s5foJYL-rHyB9

Hi everyone!  I come from a background of taking videos all the time with my friends, but it's been a few years since I've made one!

I use magic lantern on my 5d2.

Check it out!

https://www.youtube.com/watch?v=JwF6Iefz8cg