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

#1
Camera-specific Development / Re: Canon 50D
May 25, 2019, 06:31:01 PM
Quote from: reddeercity on May 21, 2019, 06:09:22 AM
After some work I got some very good results ,3744x1080 23.976fps realtime preview while recording 10bit raw video
Watch on chrome for full UHD stream. Shot At 24mm(crop factor 2.0) = 48mm , shot at 3744x1080 up-scaled to prores 4444 3840x1104 in Adobe After Effect
Uploaded that same prores4444 file , A little shaky  :D sorry , but a quick test --  hope to have this coded in a few week for testing .

This is awesome mate, i'll keep my 50D warm for testing :)
Keep us updated :)
#2
Camera-specific Development / Re: Canon 50D
October 08, 2017, 08:35:00 PM
Quote from: anto on October 08, 2017, 05:24:53 PM
guys, what is the max continuous resolution of 50D? there is crop mode? any hope for the future (lossless, 10 bit ecc)?
I'm 5DIII owner and just thought to sell my cam to swicth to another cheaper ML cam.
Yes you have crop mode. You can do full frame continuous (1584x1056).
Check the calculator http://rawcalculator.bitballoon.com/calculator_desktop to check the maximum resolution in crop mode for your wanted aspect ratio ;)  (2.35:1 1920x818 is ok)
Compared to your 5D3, you'll be loosing 10-12bit raw and compressed raw (plus the 50D is not that stable if you want to record a lot in warm environments)
#3
Camera-specific Development / Re: Canon 50D
September 13, 2017, 07:31:05 PM
Thank you a1ex, make clean helped compiling :) There's still a few errors but it compiles now !
I can start hunting now. I'll do it this week-end or as soon as I have a few hours free.
#4
Camera-specific Development / Re: Canon 50D
September 12, 2017, 10:51:26 PM
mlv_rec is working again in the latest build :) Sorry I couldn't help pinpoint the reason why it broke on august builds :s
#5
Camera-specific Development / Re: Canon 50D
September 06, 2017, 09:23:41 PM
I'm pretty sure the problems happens at or after changeset 443884d (used on build 2017Aug17).
I'll have to compile versions in between the ones available for download right ?
As I still have trouble compiling myself, I cannot go further :s

make zip ends in :

boot-hack.o: In function `my_init_task':
boot-hack.c:(.text+0x230): undefined reference to `_bss_end'
boot-hack.c:(.text+0x234): undefined reference to `_text_start'
boot-hack.o: In function `my_task_dispatch_hook':
boot-hack.c:(.text+0x378): undefined reference to `_task_overrides_start'
boot-hack.c:(.text+0x37c): undefined reference to `_task_overrides_end'
boot-hack.o: In function `copy_and_restart':
boot-hack.c:(.text+0x560): undefined reference to `_bss_start'
boot-hack.c:(.text+0x564): undefined reference to `_bss_end'
boot-hack.c:(.text+0x57c): undefined reference to `_bss_end'
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x67c): undefined reference to `_init_funcs_start'
boot-hack.c:(.text+0x680): undefined reference to `_init_funcs_end'
boot-hack.c:(.text+0x690): undefined reference to `_tasks_start'
boot-hack.c:(.text+0x694): undefined reference to `_tasks_end'
config.o: In function `get_config_var_struct':
config.c:(.text+0x258): undefined reference to `_config_vars_start'
config.c:(.text+0x25c): undefined reference to `_config_vars_end'
config.o: In function `config_var_lookup':
config.c:(.text+0x290): undefined reference to `_config_vars_start'
config.c:(.text+0x294): undefined reference to `_config_vars_end'
config.o: In function `config_save_file':
config.c:(.text+0x8e4): undefined reference to `_config_vars_start'
config.c:(.text+0x8f8): undefined reference to `_config_vars_end'
config.o: In function `config_parse_file':
config.c:(.text+0xaa0): undefined reference to `_config_vars_start'
config.c:(.text+0xaa4): undefined reference to `_config_vars_end'
property.o: In function `prop_add_internal_handlers':
property.c:(.text+0x1a4): undefined reference to `_prop_handlers_start'
property.c:(.text+0x1a8): undefined reference to `_prop_handlers_end'
module.o: In function `_module_load_all':
module.c:(.text+0xeb4): undefined reference to `_module_symbols_start'
module.c:(.text+0xeb8): undefined reference to `_module_symbols_end'
make: *** [magiclantern] Error 1


Anyone got the same problem on the 50D here ?
#6
Camera-specific Development / Re: Canon 50D
September 04, 2017, 06:36:08 AM
I got :
user@domain:~/magic-lantern$ hg bisect
abort: cannot bisect (no known bad revisions)

Not sure it helps  ::) Am I missing something ?
#7
Camera-specific Development / Re: Canon 50D
September 04, 2017, 12:16:40 AM
I'll try and do that. Never used hg_bisect but doesn't seem that difficult. I already have magic lantern build set in bash fo windows
#8
Camera-specific Development / Re: Canon 50D
September 01, 2017, 10:54:41 PM
Just tried again with the previous build I was using, 2017Jul28 is working fine.
What can I do to help debug ? I'd be glad to help :)
#9
I can confirm that MLVFS is working on windows 10.
I took the files in this thread but cannot remeber which ones exactly :s
#10
Camera-specific Development / Re: Canon 50D
August 30, 2017, 10:50:09 PM
Did any one else noticed that the latest built (18 aug 2017) broke Raw recording with mlv_rec ?
Mlv_lite is still working though, but I cannot get to record anything with mlv_rec. The camera just freezes.
#11
Quote from: garfield72 on July 18, 2017, 07:12:24 PM
Thanks justinbacle, i create a cmd file with:

c:
cd C:\MLVFS_x64
mlvfs_x64.exe V: --mlv-dir=C:\RAW
pause

When i launch it, i have the message (see cmd.png), after i go to http://localhost:8000/ and i have the message (see brownser.png).

how to do?


There is a problem with your cmd file or with your installation of MLVFS, you should see the "pause" if there is no problem when launched.
Did you get an error message when launching the cmd file ?
#12
Quote from: garfield72 on July 17, 2017, 08:05:15 AM
Hello, I installed Dokany and download MLVFS_x86, now I don't know what to do with the MLVFS zip file.
Should it be decompressed? And where to copy it?

How to use
"Start it via the command line like this:
Code: [Select]
cd <mlvfs_exe_dir>
mlvfs.exe <mount point> --mlv_dir=<directory with MLV files>"

Thanks for your help

François

Here is my cmd file to launch MLVFS :

r:
cd R:\MLRAW\MLVFS_x64
mlvfs_x64.exe V: --mlv-dir=R:\50D
pause


Where R:\MLRAW\MLVFS_x64 is the path where I unzipped the MLVFS zip file
and R:\50D is the path were are stored my MLV footage files
You'll have to install dokany before launching the script to make it work.
Once it is launched, just go http://localhost:8000/ on your favorite web browser to see the settings and preview the files

Hope it helps :)
#13
Quote from: Boygetslost on July 16, 2017, 08:26:33 AM
With MLVFS  once you have mounted the MLV files, is it best to load them directly. Or copy them out of the mounted drive so they are just normal DNG folders?

The best thing is that you load them directly so that you don't have to store DNGs and the original MVL footage. As mlvfs allows to make changes on the fly (chroma smoothing, banding removal ans so on) I just keep all the MLV files and fire up MLVFS when needed to work with these files.
#14
Raw Video / Re: how to enter crop mode 50d?
July 14, 2017, 02:14:50 PM
You have to enter crop mode, then go to magic lantern menu and change the raw recording settings.
You can go up to 1984x844 in 2.35 or 1920x1080 in 16:9 (but you should be able to have continuous recording as these frame sizes)
#15
Camera-specific Development / Re: Canon 50D
July 04, 2017, 01:28:26 PM
Quote from: zcream on July 03, 2017, 02:36:09 PM
:) Any idea is the cmos0 values can be checked into a build?
The ml iso only offer 1/2 stop Max as improvement. I would be Keen on trying dual iso to get the 14-15 stops
I tried to help with the programming a few months ago but got stuck http://www.magiclantern.fm/forum/index.php?topic=9852.msg183402#msg183402
I'd love to see Dual Iso video work on the 50D too !
#16
What happens if you start the 50D with no card in it ?
You should still be able to use the screen (menus & live view)
#17
I had this problem back when I had my 500D. If you shutdown the camera whilst it is saving something (e.g. emptying buffer) or remove the card before powering off first this might happen.
Don't know if this was thix in an update though as I switched from a 500D to another camera.
Hope this helps :)
#18
This update is very nice indeed :)
Could you update the Binary for MLVFS_x64 ? I'd like to try it, but only MLVFS_x64 works on my PC :s
#19
Camera-specific Development / Re: Canon 50D
April 19, 2017, 07:07:54 PM
Quote from: tecgen on January 16, 2017, 05:19:25 AM
Some time ago I played around with an dual iso video branch, that is supposed to work on the 50D and the 5D Mark II. I don't know why but it does not work on my 50D so far.
https://bitbucket.org/tecgen/magic-lantern/branch/5D2-50D-dualiso-video#diff

The good news is, I am able to record dual iso RAW video by changing the CMOS[0] manually to a value of 8, 18 or 28. (See also my post in the dual iso for 5D2 thread http://www.magiclantern.fm/forum/index.php?topic=16854.msg171694#msg171694)

Here you can find a MLV of an 50D dual iso RAW video and a dual iso DNG file that was created by MLVFS.
https://www.dropbox.com/sh/w2wemk17d5x95fu/AAAosfOCYFDQM4SPvoL4WHuda?dl=0

Can anyone help us to put these things together? It seams simple to get dual iso RAW video working even on the good old 50D.

I'd like to help on this subject. I had my VM ready for compiling and I'd like to try tweaking registers. But I have a problem.
When I try to load the ADTG_GUI module, the camera doesn't manage to load the modules. Am I missing something ?
#20
Camera-specific Development / Re: Canon 50D
April 19, 2017, 04:50:04 PM
Quote from: littlebobbytables on April 18, 2017, 05:16:45 PM
Thanks, good to know, do you have a specific nightly build you're comfortable with?

I usually update ML as soon as I see an update available.
In the newer builds, both MLV_Lite (the old raw_rec updated) and MLV_rec record MLV files (can someone correct me if I'm wrong ?)
So no worries about that.

As there is development about new crop modes / lossless compression / 10/12bit recording I have to recommend you to update frequently ;)
#21
Camera-specific Development / Re: Canon 50D
April 18, 2017, 11:44:40 AM
Hi,

Quote from: littlebobbytables on April 17, 2017, 03:14:39 PM
1) Has anyone noticed something similar and on what build was this? Did you manage to resolve this in any way? What can I do/provide to get to the bottom of this?
2) Is anyone shooting on a newer build for a while you are happy with(and you consider solid)?
3) Do you find mlv_rec(or another setting) to be more stable/less skipped frames?

Build: Nightly.2015.Nov15.50D109
Settings: Expo. override: on, GD: on, zebras, peaking, waveform, fps override: 23.976, RAW full sensor 16:9 max resolution using raw_rec

1 & 2 / First of all, I have to reccomend you to use the latest nightlies. I had more stable recordings by sticking to the latest nightlies.
When I had this problem (happened to me several times) I found out that the "big" corrupted files were in fact recording that stopped at the beggining that I had to stop by removing the battery. These files are actually almost empty but are reported with a wrong size on the CF card. May be wrong, but that is what I think.
3/ I use MLV_Rec more because the interface is more usable IMO. The latest MLV Lite is mor usable though. I'd reccomend both other the old raw_rec as MLV files are much easier to handle ;)
#22
Be sure to remove the corrupted files as MLVFS doesn't deal with them ;)
#23
Hi,

I use MLVFS with both Premiere/AfterEffects and Resolve

Here is what I understood :
- MLVFS uses CPU for processing and transcoding on the fly you MLV files into dngs.
- Premiere (Lumetri) /Resolve  uses GPU for grading the footage
- Première just Looooves scratch disks, so a good SSD is required.

Here is what sucks :
Adobe Camera Raw (e.g. the processing algorithm you use in AfterEffects / Photoshop) still wanna use the one CPU thread for everything and is damn slow.

Here is my configuration :
CPU : i7 4790k
GPU : Nvidia GTX670
SSD : 240Gb Kingston

I manage to get :
- good performance with resolve (though I just work with 2k footage)
- acceptable performance in premiere (Performance drops when I use more than two lumetri layers)
- unusable performance in after effects -> If I wanna use after effects (because ACR is just damn good) I have to render intermediates and cannot work in real-time. Which is a pain as I prefer ACR's noise reduction and overall quality to resolve.

I'd say get a good CPU (i7 or Ryzen) and good GPU (AMD & Nvidia seems to works both fine now) and a large SSD for your OS/Scratch
#24
You can just use MLVFS and use the dng files that are transcoded on the fly ;)
#25
I do all my post prod in the native resolution (1280x1056 in my case, for 2.4:1 anamorphic) and do the final export in the wanted resolutions. I usually export :
- a "master" file in Cineform 10b 422 in native resolution
- a 4K youtube export (from the Master file)
- a 1080p youtube export (from the Master file)

I found thart by keeping the same resolution in the entire process saves me the headache of choosing a different format for each intermediate file (as Cineform has no resolution restrictions were DNxHD is limited to "well-known" resolutions)