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.
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 MenuQuote@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?
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.
Quoteis 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.
Quote from: bulls4ever on February 14, 2017, 12:36:04 AMThings can change .. just check the "1080p 60fps, 2K, 4K, RAW video..."Maybe someone could at least update this thread/the first post?
Quote from: DeafEyeJedi on May 19, 2017, 07:01:45 PM@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 make it happen already @spec42!
Quote from: dmilligan on May 16, 2017, 01:29:44 PMSo, at the mono project website (http://www.mono-project.com/docs/gui/wpf/) it says:
This app uses WPF, you won't be able to use it on a Mac.
QuoteSilverlight 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.I found a tutorial online, seemingly, about how to get silverlight working in wine (https://www.youtube.com/watch?v=C3q9ECt1rAg), will that work?
Silverlight does not have all the capabilities of WPF, but both technologies are converging API-wise.
QuoteThe 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:
QuoteWineskinX11: main(): argc=12Can somebody help me out step by step, or point me to some resource or whatever? Thanks.
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
Quote from: baccinoluigi on May 15, 2017, 08:47:08 PMWell, 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.
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
QuoteI 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?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.
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).
Page created in 0.100 seconds with 14 queries.