Messages

I understand that the "bottleneck" is the camera as far as write speed, but I wonder, can someone explain to me if this is solely a hardware limitation, or if there is potential room for improvement via ML? Thanks.

Was testing out the most recent build and had a slew of errors when I tried recording video (there is one possible mistake I made, reinstalling ml now to see if I can reproduce error). I tried to start recording, and it did so for a few seconds, but then said card full. I didn't realize at the time, but it didn't switch over from cf to sd card, so I couldn't test to see if it would still have worked if I had switched manually. That said, since that happened I have been experiencing two kinds of errors. One, when I go to record video if I am using anything above 3k resolution a "script" will run indefinitely, saying that "mean is incorrect" and something about black level, and a range of numbers in the 2000-3000s. At the moment, I am able to reproduce this, but am unsure if reinstalling ML will fix. I have crash logs, etc. as well. The main thing that is also happening, is that I kept seeing text saying "video end not working". When I ran the self test, this message popped up quite a bit. Any thoughts? Should I provide any of the stuff I've got, crash logs and such?

to be honest, not the best way. because of so much hurdles, that are somewhere inside the os and some wrappers. Why dont u try to start from the beginning with the help of my sourcecode and (of course!) the code from ml.

@chmee Ok. Can you be a little more specific? I've tried compiling from source code before, but I didn't have too much luck. Where should I begin exactly? Perhaps we could continue this via PM?

Thanks : )

Sorry for the repost (was trying to find this thread earlier, but only found the 14bit silent picture thread, so I started my own thread, here: http://www.magiclantern.fm/forum/index.php?topic=19679.msg185345#msg185345)
But this is what I was driving at:

is it possible to to separate the functionality of the liveview feature into "that which enables silent picture" and "that which must move the mirror away from the eyepiece?" eyepiece?"

Thanks.

Things can change .. just check the "1080p 60fps, 2K, 4K, RAW video..."

Maybe someone could at least update this thread/the first post?

Just make it happen already @spec42! 

@Danne: we'll see. I literally have no experience coding or scripting, so this would certainly be a project. I've wanted an excuse to learn about this kind of stuff though, so I'm going to make the attempt, at least.

Just wondering/thinking out loud here: I prefer shooting through the eyepiece on my 5d, however, "in a (my) perfect world" it'd be possible to use the silent shutter feature without having to buy one of those fancy back screen eye piece things to keep the screen visible in broad daylight. I was just shooting at the beach, and I wound up shooting without silent picture because I couldn't see what I was doing, but I'd love it if I could mess around with the module.
So, bearing in mind that I am describing this merely from my superficial understanding of how the liveview function works (just by looking at the camera), my thought/question is this:
is it possible to to separate the functionality of the liveview feature into "that which enables silent picture" and "that which must move the mirror away from the eyepiece?"
And I suppose more immediately, should I be posting this instead in the "feature request" section? I mainly want to know if it's possible, but if it is, then I would certainly be pleased if someone did decide to take this upon themselves. Thanks.

My friend just told me that cdngs and dng files are virtually the same, metadata notwithstanding. It was simply a fool's ignorant whim (meaning myself)

Ok. So again, bearing in mind I don't really know what I'm doing or what to look for, I am willing to give it a shot
(unless someone else who knows what they're doing wants to).
Here's what I've found so far:
WPF–Silverlight compatibility: https://msdn.microsoft.com/en-us/library/cc903925(v=VS.95).aspx
Some porting speculations: http://stackoverflow.com/questions/2948770/convert-wpf-application-to-silverlight
I also found out that Wine has up to ver. 4.0 of the .net framework bundled with the .dmg. There are more recent versions which I can download and install into my copy of wine via winehq, but I don't know what's necessary and what is not.
I also just found what seems, albeit from my ignorant perspective, to be a good resource for this exact process:
https://www.codeproject.com/Articles/111356/Porting-from-WPF-to-Silverlight-The-Missing-Pieces
And then, I also found something about this on microsoft's website: https://blogs.msdn.microsoft.com/silverlight_sdk/2007/04/30/converting-a-wpfe-application-to-a-silverlight-scripting-application/
Any pointers?

This app uses WPF, you won't be able to use it on a Mac.

So, at the mono project website (http://www.mono-project.com/docs/gui/wpf/) it says:

Silverlight implement a subset of the WPF APIs and is available on Windows, MacOS X and through our own open source effort Moonlight it is available on Linux and other Unix systems.

Silverlight does not have all the capabilities of WPF, but both technologies are converging API-wise.

I found a tutorial online, seemingly, about how to get silverlight working in wine (https://www.youtube.com/watch?v=C3q9ECt1rAg), will that work?

Hey now, I'm trying to install this thing on my mac (running mavericks) using wineskin winery (granted I know absolutely nothing about what I'm doing...)—I performed a test run, and it produced two .txt files, one indicating that it could read the contents of raw2cdng, and another saying that:

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>

Idk how much of this information is needed (if at all), but here's the result of the test:

WineskinX11: main(): argc=12
Waiting for startup parameters via Mach IPC.
WineskinX11: do_start_x11_server(): argc=12
Attempting to use pixel depth of 24
[258379.097] WineskinX11 starting:
[258379.097] X.Org X Server 1.13.0
[258379.097] Build Date: 20120921
[258379.098] _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
[258379.101] Initializing built-in extension Generic Event Extension
[258379.101] Initializing built-in extension SHAPE
[258379.101] Initializing built-in extension MIT-SHM
[258379.101] Initializing built-in extension XInputExtension
[258379.101] Initializing built-in extension XTEST
[258379.101] Initializing built-in extension BIG-REQUESTS
[258379.101] Initializing built-in extension SYNC
[258379.101] Initializing built-in extension XKEYBOARD
[258379.101] Initializing built-in extension XC-MISC
[258379.101] Initializing built-in extension XINERAMA
[258379.101] Initializing built-in extension PseudoramiX
[258379.101] Initializing built-in extension XFIXES
[258379.101] Initializing built-in extension RENDER
[258379.101] Initializing built-in extension RANDR
[258379.101] Initializing built-in extension DAMAGE
[258379.101] Initializing built-in extension MIT-SCREEN-SAVER
[258379.101] Initializing built-in extension DOUBLE-BUFFER
[258379.101] Initializing built-in extension RECORD
[258379.101] Initializing built-in extension X-Resource
[258379.101] Initializing built-in extension XVideo
[258379.101] Initializing built-in extension XVideo-MotionCompensation
[258379.101] Initializing built-in extension GLX
[258379.101] x: 0, y: 0, w: 1280, h: 778
[258379.115] (II) GLX: Initialized Core OpenGL GL provider for screen 0
[258379.115] [dix] Could not init font path element /opt/X11/share/fonts/75dpi, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/100dpi, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/cyrillic, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/misc, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/OTF, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/Speedo, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/TTF, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/Type1, removing from list!
[258379.116] [dix] Could not init font path element /opt/X11/share/fonts/util, removing from list!
[258379.223] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
Engine Used: WS9Wine2.6
Hardware:

    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: MacBookPro9,2
      Processor Name: Intel Core i5
      Processor Speed: 2.5 GHz
      Number of Processors: 1
      Total Number of Cores: 2
      L2 Cache (per Core): 256 KB
      L3 Cache: 3 MB
      Memory: 4 GB
      Boot ROM Version: MBP91.00D3.B0C
      SMC Version (system): 2.2f44
      Sudden Motion Sensor:
          State: Enabled

Graphics/Displays:

    Intel HD Graphics 4000:

      Chipset Model: Intel HD Graphics 4000
      Type: GPU
      Bus: Built-In
      VRAM (Dynamic, Max): 1024 MB
      Vendor: Intel (0x8086)
      Device ID: 0x0166
      Revision ID: 0x0009
      Displays:
        Color LCD:
          Display Type: LCD
          Resolution: 1280 x 800
          Pixel Depth: 32-Bit Color (ARGB8888)
          Main Display: Yes
          Mirror: Off
          Online: Yes
          Built-In: Yes

Can somebody help me out step by step, or point me to some resource or whatever? Thanks.

If you shot at 7,5 fps and you put the shot on a timeline for every software the minimum you can get it's a timeline at 24 fps so the shot it's about 3 times faster.
So with twixtor you slow down the time at about 33,333% to get right time

Well, part of what you're saying makes sense, but I guess I don't fully understand the implications of shooting at 7.5fps. I was under the impression that if one shoots at a lower fps that the camera doesn't capture as much visual information, since it's taking in frames at a lower rate. Granted that it seems I don't understand this, with that assumption, I can't understand how it is possible to make smooth 24fps out of 7.5. Thanks.

Listen, Walter, I don't mean to be rude when I say this, but you're being rather presumptuous. I am asking about this precisely because I went to that company's website to try and answer my own question first, and when I was unable to figure it out myself, I came here.

But getting back to my question, beyond just moire/noise patterns, I've noticed in most ML footage that I've seen on Youtube that lines on an angle (e.g. telephone lines, wires, etc.) tend to come out very piexelated and inexact. That is to say, they almost fluctuate (maybe this is just moire? I don't know...). But I have seen footage where it's not very drastic at all: https://www.youtube.com/watch?v=vkJNf61BdA0
And, again, in the footage at the start of this thread, I notice no such irregularities. Is this to do with the footage being downscaled, or what?

@walter schultz: Ok. I kind of get what you're saying. What I don't understand then is how does this plugin help? Again, I don't understand most of this, it seems like if it's shot at 7.5 fps, then there would be "information" missing keeping one from making "real time" equivalent footage (for lack of a more accurate way of speaking).

One other thing @baccinoluigi (or whomever, I suppose, so long as someone can explain this to me):
I've noticed in a lot of raw 4k/3k/etc. footage on youtube from ML that a lot of moire persists, yet I don't see that in your footage. Neither is yours the first which I have noticed a relative lack of moire, so I'm wondering if there is an element of your post process that is different, or if you (or in general) different settings on the camera can prevent this. Thanks.

Pardon, perhaps I am merely ignorant, but what is the purpose of "retiming"?
Did you shoot in slow motion originally? Thanks.

[*THERE ARE THREE LINKS BELLOW THAT ARE INTEGRAL TO THE QUESTION I'M POSING*]

*THERE ARE THREE LINKS BELLOW THAT ARE INTEGRAL TO THE QUESTION I'M POSING*
I happened upon this thread http://www.magiclantern.fm/forum/index.php?topic=13982.msg134987#msg134987, and wondered: is anyone out there exploring something like this currently? Or does anyone have any insight to offer into this issue? Obviously, bearing with the motion "jello" notwithstanding, this is the bane of the low budget dslr project.
For myself, when I finally get time to devote to solidifying my setup and workflow (assuming that ever happens...), I'm the kind of person who's not looking for anything but an all in one solution, as far as is possible. I'm using a 5d3, and hopeful since seeing content like this, especially after years of accepting that I would just, you know, not film anything moving too quickly, or settle for a less than satisfactory image. Following are the relevant links I got out of the aforementioned thread.

1. Original test video by some guy (reducing/eliminating "jello" artifacts via some kind of filter): https://vimeo.com/5976527
2. Tessive's discontinued product and explanation of concept:
https://vimeo.com/46701641
3. RED's mount design incorporating filter (who can even afford to rent one of the cameras for these things anyway?): http://www.red.com/store/products/dsmc-mount-ti-canon-captive

As an afterthought, although I'm hesitant to open this can of worms lest this become the sole focus of this thread (assuming anyone reads this), I also dare to ask (bearing in mind that I'm not knowledgeable of hardware or software): in light of the video from Tessive's vimeo account explaining the phenomenon (in particular from @2:44 on wherein the guy talks about frequency response of shutter angles), is there any aspect of this that can be coded or something? Like I said, I don't understand the practical stuff, just the conceptual type stuff, and not especially well at that. Hopefully something will come of this discussion.

That is exactly what I did. I didn't know how else to uninstall it, so I let the automatic timed uninstall run, after which I noticed these issues. I have since reinstalled ML and confirmed twice that I can't take photos without full res silent pictures enabled. Without silent picture enabled, it won't do anything except something that seems to resemble the EOSM shutter bug (so I'm told) however, I have not yet experienced an actually locked shutter. Without silent picture enabled, all that happens when I try to take a photo is that the screen overlays (M mode, shutter, expo., etc.) disappear, then reappear. Thus far (three times including before uninstall and reinstall) it has consistently proved the case that I can work around the issue by enabling silent picture, but it has to be set to full resolution, otherwise a text box appears that says "preparing..." in place of taking a photo.

So I just uninstalled ml from my eosm, and now it's continuing to produce a similar issue as when I had ml installed:
when I try to take a photo, it simply won't. The overlays flash off for a second, and the camera doesn't take a picture.
It did the same thing after I had enabled, and then disabled silent picture mode, so I'm somewhat confused.
Can somebody help me out with some information? What happened? Is there anything that can be done?
The camera still works with ML running and with silent picture enabled, but has it permanently affected the camera?

User error I formatted the card incorrectly, I didn't know what I was doing.
I've got the latest nightly working now.

That's the thing... I did format the card in the computer, however, the camera won't do anything but cause the power button to blink green, i.e. I can't navigate any of the menus on the camera when I put the sd card into the camera. This all happened once I updated to the latest nightly (5/7/16). Previously it had been working, albeit with the glitches mentioned in the first post. I formatted the card in the camera, deleted the old ML folders, put the new nightly build onto the card, and as soon as I put the card back in the camera it started having this problem of not turning on fully, except after removing both the battery and memory card, and putting the memory card back in.

I just erased everything from the camera on mac disk utility. I didn't quite know what to do, so I erased all the free space on the sd card as well as doing a basic erase to make doubly sure that the issue wasn't with the card, and it turns out that the camera still goofs up when I put the memory card in. I guess I can try reinstalling the original firmware, I don't know if that's a bad idea or not though.

@ Licaon_Kter
Just posted this on the camera specific thread for the eosm:

I just updated to the most recent nightly build, and my camera won't turn on now. The green light blinks, and that's it, with or without the memory card. What does this mean and is there anything I can do about this?
If I remove both the memory card and the battery and keep the memory card out after putting the battery back in, the camera will at least turn on, and otherwise seemingly behave normally.
I noticed something strange right before I formatted the card in the camera: I couldn't select the "light formatting" option by pressing the "info" button, which parallels another problem I reported having in my other thread (that I could no longer disable the ML overlays by pressing the "info" button).

This isn't what they call "soft bricked," is it? Pretty ironic, but I got tired of waiting to hear from someone about the issues I was experiencing, and I totally goofed, so unfortunately I can't get any more pics until I can figure that out... the card it's a 64gb sandisk extreme pro, lens is just a single lens c-mount (literally just a piece of glass and a c-mount adapter), as far as zoom, I can't remember what the settings were prior to it's current state.

So just thought I'd ask for some help: I posted some issues I was having with a previous nightly build (unfortunately don't know which one) here http://www.magiclantern.fm/forum/index.php?topic=17187.msg166553#msg166553, however, I received little feedback. I just updated to the most recent nightly build, and my camera won't turn on now. The green light blinks, and that's it, with or without the memory card. What does this mean and is there anything I can do about this?
If I remove both the memory card and the battery and keep the memory card out after putting the battery back in, the camera will at least turn on, and otherwise seemingly behave normally.
I noticed something strange right before I formatted the card in the camera: I couldn't select the "light formatting" option by pressing the "info" button, which parallels another problem I reported having in my other thread (that I could no longer disable the ML overlays by pressing the "info" button).

It is activated, but through the ML menu, is that what you mean? I'm still getting familiar with the camera. I can't seem to find where "highlight tone priority" is located in the actual canon firmware (despite HTP being referenced to in other areas, like the canon overlays... e.g. "iso range is limited while 'highlight tone priority is enable'").