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 - gerk.raisen

#1
+1 for the idea of "sponsored" goals development.

More than willing to support it.

ML app for Smartphone could be a good start. I think many people could be interested.
#2
Thank you nikfreak...

I just can't wait: :)

Meantime I try building from your repo and maybe I'll try to integrate your lastest commit in the A1ex crop_rec_4k branch
#3
Thanks tecgen,
I've tried to follow you but maybe the exmem.c code is a little too difficult for me :(

I tried to insert the following code in the exmem.c in the 70D_merge_112 branch (70D is still not in unified builds)


/* called from RscMgr task */
static REQUIRES(RscMgr) void srm_malloc_cbr(void** dst_ptr, void* raw_buffer, uint32_t raw_buffer_size)
{
    //printf("srm_malloc_cbr(%x, %x, %x)\n", dst_ptr, raw_buffer, raw_buffer_size);

    /* we can't tell how much to allocate; the allocator tells us */
    /* the value is hardcoded in consts.h, for speed (probing is very slow) */
    ASSERT(SRM_BUFFER_SIZE == raw_buffer_size);
   
    /* return the newly allocated buffer in the output variable */
    *dst_ptr = raw_buffer;
   
    /* announce it's done */
    give_semaphore_nc(srm_alloc_sem);
}


I inserted it just after the line

342     static int srm_allocated = 0;

but trying to compile it return me a bunch of errors:


[ CC       ]   exmem.o
../../src/exmem.c:345:8: warning: return type defaults to 'int' [-Wimplicit-int]
static REQUIRES(RscMgr) void srm_malloc_cbr(void** dst_ptr, void* raw_buffer, uint32_t raw_buffer_size)
        ^
../../src/exmem.c: In function 'REQUIRES':
../../src/exmem.c:346:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:362:17: error: storage class specified for parameter 'srm_buffer_size'
static uint32_t srm_buffer_size = 0;
                 ^
../../src/exmem.c:362:1: error: parameter 'srm_buffer_size' is initialized
static uint32_t srm_buffer_size = 0;
^
../../src/exmem.c:365:27: error: storage class specified for parameter 'srm_alloc_sem'
static struct semaphore * srm_alloc_sem = 0;
                           ^
../../src/exmem.c:365:15: error: parameter 'srm_alloc_sem' is initialized
static struct semaphore * srm_alloc_sem = 0;
               ^
../../src/exmem.c:368:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:388:17: error: storage class specified for parameter 'old_uilock_shutter'
static uint32_t old_uilock_shutter;
                 ^
../../src/exmem.c:391:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:399:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:407:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:491:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:517:1: warning: empty declaration
struct srm_malloc_buf
^
../../src/exmem.c:523:26: error: storage class specified for parameter 'srm_malloc_hSuite'
static struct memSuite * srm_malloc_hSuite = 0;
                          ^
../../src/exmem.c:523:15: error: parameter 'srm_malloc_hSuite' is initialized
static struct memSuite * srm_malloc_hSuite = 0;
               ^
../../src/exmem.c:524:30: error: storage class specified for parameter 'srm_malloc_buffers'
static struct srm_malloc_buf srm_malloc_buffers[10] = {{0}};
                              ^
../../src/exmem.c:524:15: error: parameter 'srm_malloc_buffers' is initialized
static struct srm_malloc_buf srm_malloc_buffers[10] = {{0}};
               ^
../../src/exmem.c:524:15: warning: braces around scalar initializer
../../src/exmem.c:524:15: note: (near initialization for 'srm_malloc_buffers')
../../src/exmem.c:528:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:590:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:618:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:630:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
../../src/exmem.c:668:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
{
^
In file included from ../../src/dryos.h:41:0,
                 from ../../src/exmem.c:3:
../../src/tasks.h:160:8: error: parameter 'task_create_exmem_init' is initialized
struct task_create \
        ^
../../src/exmem.c:674:1: note: in expansion of macro 'INIT_FUNC'
INIT_FUNC("exmem", exmem_init);
^
../../src/tasks.h:162:1: error: section attribute not allowed for 'task_create_exmem_init'
task_create_##ENTRY = { \
^
../../src/exmem.c:674:1: note: in expansion of macro 'INIT_FUNC'
INIT_FUNC("exmem", exmem_init);
^
../../src/exmem.c:674:20: error: 'exmem_init' undeclared (first use in this function)
INIT_FUNC("exmem", exmem_init);
                    ^
../../src/tasks.h:164:27: note: in definition of macro 'INIT_FUNC'
         .entry          = ENTRY, \
                           ^
../../src/exmem.c:674:20: note: each undeclared identifier is reported only once for each function it appears in
INIT_FUNC("exmem", exmem_init);
                    ^
../../src/tasks.h:164:27: note: in definition of macro 'INIT_FUNC'
         .entry          = ENTRY, \
                           ^
../../src/exmem.c:345:8: warning: type of 'RscMgr' defaults to 'int' [-Wimplicit-int]
static REQUIRES(RscMgr) void srm_malloc_cbr(void** dst_ptr, void* raw_buffer, uint32_t raw_buffer_size)
        ^
In file included from ../../src/dryos.h:41:0,
                 from ../../src/exmem.c:3:
../../src/tasks.h:162:1: error: declaration for parameter 'task_create_exmem_init' but no such parameter
task_create_##ENTRY = { \
^
../../src/exmem.c:674:1: note: in expansion of macro 'INIT_FUNC'
INIT_FUNC("exmem", exmem_init);
^
../../src/exmem.c:524:30: error: declaration for parameter 'srm_malloc_buffers' but no such parameter
static struct srm_malloc_buf srm_malloc_buffers[10] = {{0}};
                              ^
../../src/exmem.c:523:26: error: declaration for parameter 'srm_malloc_hSuite' but no such parameter
static struct memSuite * srm_malloc_hSuite = 0;
                          ^
../../src/exmem.c:388:17: error: declaration for parameter 'old_uilock_shutter' but no such parameter
static uint32_t old_uilock_shutter;
                 ^
../../src/exmem.c:365:27: error: declaration for parameter 'srm_alloc_sem' but no such parameter
static struct semaphore * srm_alloc_sem = 0;
                           ^
../../src/exmem.c:362:17: error: declaration for parameter 'srm_buffer_size' but no such parameter
static uint32_t srm_buffer_size = 0;
                 ^
In file included from ../../src/dryos.h:41:0,
                 from ../../src/exmem.c:3:
../../src/tasks.h:160:8: error: expected '{' at end of input
struct task_create \
        ^
../../src/exmem.c:674:1: note: in expansion of macro 'INIT_FUNC'
INIT_FUNC("exmem", exmem_init);
^
../../src/exmem.c: At top level:
../../src/exmem.c:342:12: warning: 'srm_allocated' defined but not used [-Wunused-variable]
static int srm_allocated = 0;
            ^
make[1]: *** [../../Makefile.filerules:25: exmem.o] Error 1


Could you please help me a little more step by step? :)
#4
Hello all,

Tried to compile from lastest crop_rec_4k branch
after 2d83b69 (merge of 70D_merge_112 branch into crop_rec_4k)

When compiling I receive the error:

[ CC       ]   exmem.o
In file included from ../../src/exmem.c:3:0:
../../src/exmem.c: In function 'srm_malloc_cbr':
../../src/exmem.c:380:12: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
     ASSERT(SRM_BUFFER_SIZE == raw_buffer_size);


If I understand correctly seems that the value of SRM_BUFFER_SIZE is not set

It's something that we know or maybe I could help finding it?
#5
@SztupY

We were all waiting for you :)
I'm very happy.

I can't wait to try it!


Good work and good luck!

P.S. For every tests or something that I can help, don't hesitate to contact me.
#6
Seems still available on archive.org website.

http://web.archive.org/web/20140219063611/http://wildtramper.com/sw/cr2/cr2.html

EDIT:

Other useful info at
http://lclevy.free.fr/cr2/
#7
Archived porting threads / Re: Canon 70D
January 08, 2015, 08:51:09 AM
I'm pleased to announce that my Dec14 70D is now ML supercharged :)

Are there something specific feature that would be useful to be tested at first?
I have a little spare time today at 17.00 UTC

IRC chat also possible
#8
UAO...
Great Levas, interesting project...
I will pleased to test when just ready ...or almost ready  ;)
#9
For my cases (simple shutter delay) is because I can only setup trigger in advance of the exact time of shoot.

You can think as example a free falling object with camera at the ground and trigger sensor at half height.
The only way you have to adjust the exact shoot time is changing the height of sensor and this it can be difficult and time-spending.

Maybe some high-end trigger have this feature included but not the custom homemade :)





I think (tell me if I'm wrong) is not a very difficult, could some developers help me?
#10
Hello,

I have had from a long time, a similar desire for having a shutter lag setting.
I use it my camera also to shoot with a homemade trigger and
I really love to have the possibility to specify a time amount (in millisecond) after full-press before the camera take pics
Without that setup many shooting conditions (with triggers) are very challenging.

Thank you.
#11
If confirmed working could someone please submit a pull request? :)
I support too the idea of Marekk to have an option in MLV_REC to capture frames using intervalometer settings instead of fps.
Have all the timelapses in only one file, and you can use chmee software to create CDNG it will be very comfortable...
#12
Thank you a lot Marsu42,
I can't wait to try it :)

Thank you.
#13
Hi,
Very interested to try it on the 60D :) :)
I'm also taking this opportunity for offer my free service of beta testing for your other present and future modules :)
Thanks
#14
I had just read about a program similar to DSLR controller but totally open source.

It's
DSLR Dashboard


It can control the camera with PTP command via usb cable
Totally opensource GPLv3
https://code.google.com/p/dslrdashboard/

https://play.google.com/store/apps/details?id=com.dslr.dashboard

development thread (it called nikon DSLR dashboard but don't worry :)
http://forum.xda-developers.com/galaxy-s2/themes-apps/app-nikon-dslr-dashboard-via-usb-v0-30-t1256583

It's also recommended from the author of LrTimelapse (..<<Shooting Holy Grail sequences involve changing exposure time and ISO in between the shooting interval. To avoid touching the camera when doing this, Zoltan Hubai, the developer of DslrDashboard, kindly agreed to implement a "LRTimelapse Mode" into his great Android App for controlling the camera.>>)


Maybe the GUI is not so nice as DSLR Controller but have more or less the same features, included the ability of remote control the camera with PTP commands other than USB cable also via wireless with the cheap (less than 40$) "TP LINK MR3040 - Portable Battery Powered 3G/4G Wireless N Router" as described here in a previous post
http://www.magiclantern.fm/forum/index.php?topic=10688.msg104121#msg104121
On Nikon side also the little Nikon WU-1a/1b adapter is supported (not tested on Canon perhaps)

Simply flashing the TPLINK MR3040 with a customized firmware based on opensource project Openwrt that include a little serverside program called DslrDashboardServer (also totally opensource)
That program, auto-loaded at MR3040 startup, relay the PTP commands to the client program on smartphone or tablet via WiFi, from where you can control the camera.
https://github.com/hubaiz/DslrDashboardServer

I think it's a good start point to modify this already mature project at our needs integrating it with specific code to send and receive also PTP-ML code from/to the camera and simulate keypress
and interact with ML menus.. and maybe also have a sort of "command line" with possibility to launch command and scripts (when they will return :)

I did not yet contacted the author but maybe also he can help us.


P.S. Raised reward to 250$ and I offer a free MR3040 at the first user that make a first tangible step to this project, just to keep the topic hot :)
#15
 Marsu42, I can't wait to use your hot_keys module  ;)

@alldevelopers
Please add array config vars to modules (just like in the core) to make this happen!

Thanks.
#16
Great!

So you accept the challange?
You have all the help I can :)
#17
Hello,

Yes the offer is still valid.
We were only waiting a brave knight  :)

Remenber that other than the android app I think a lot on work is necessary on ML-side to create the module

Some work is already WIP:
https://bitbucket.org/hudson/magic-lantern/pull-request/420/refactor-audio-to-use-new-config-var

But I think that start a project will encourage some developers to support us with the changes needed.

For the .apk sources as you could see my first post are not available at the moment, only a link to the Play Store where you can install the apk
From Stzupy bitbucket https://bitbucket.org/sztupy/magic-lantern/downloads you can download a very old ML version that works with the Android app.
All the public info/documentation is in the links I posted.

Seems that also Stzupy after my post start looking again at the program,(he also expressed the intention of releasing all the code as AGPL when done) but after that I never heard nothing more :(
Maybe you can try contact him for help or having the .apk source code.

Here a quick-list /ideas of the features for the Android app at this stage:

-Total Opensourceness...see my first post
-Simulate the press of camera physical buttons.
-Interaction and selection from ML menu and see the ML overlays that appears on camera screen
-Liveview (if possible also the Canon Menus)
   The FPS performance is very slow in the original app, but I think that now with the hardware evolution of these passed years and a bit of optimization we can arrange more :)

Also your idea of use Nikon WU-1B is very interesting, but maybe this is more simple to control the camera wireless:
http://www.magiclantern.fm/forum/index.php?topic=10688.msg104121#msg104121
or we can use (but seems less reliable) an Android key/low-end phone to forward the data to the Android app
#18
General Development / Re: PicoC -> TCC
March 19, 2014, 10:32:46 AM
Not sure.  :o Is the old PicoC APIs already available to test with new TCC scripting engine?
I think it could be a good start point.
#19
General Development / Re: PicoC -> TCC
March 18, 2014, 02:51:24 PM
Thank you A1ex... we are close to have fun :)
#20
Feature Requests / Re: USB keystrokes sender / receiver
February 27, 2014, 03:32:56 PM
Totally agree with you.
I think that although the other solution is more complete and more versatile, this at least for start is a lot simpler and can already arrange the necessity of some.
Maybe in future, when cameras with touchscreen will be supported, also simulate the touchscreen itself.

Very important (at least for me) is the wireless option.
For cameras without Wi-Fi I think we can achieve it with a cheap device like this:
TP LINK MR3040 - Portable Battery Powered 3G/4G Wireless N Router (less than 40$)
The program DSLRcontroller use that device.
It use an opensource Openwrt firmware loaded on the device (customized with a small linux program loaded on startup) to forward send/receive PTP message to/from the client program on android by the usb cable to the camera.

http://dslrcontroller.com/guide-wifi_mr3040.php

We can modify it to add or write another little linux program (to be loaded on device startup) to receive the keypress request from android client with the same method and forward it by the usb cable to the camera.
We can also use it for send/receive PTP-ML codes, and maybe also have a sort of "command line" with possibility to launch command and scripts (when they will return :)

#21
General Development / Re: Mini burst
February 21, 2014, 02:41:22 AM
Ready to try it just done :)
#22
Modules Development / Re: Proposal for managing modules
February 17, 2014, 11:45:58 AM
+1 for the tags.

A lot more flexible than simple categories


+2 also for source modules.
I already wrote a very close idea to the forum some times ago :)

Can't wait !
#23
General Development / Re: Re: Focus Bracketing
February 17, 2014, 11:25:39 AM
Quote from: a1ex on February 16, 2014, 10:30:44 PM
Another point higher. I expect TCC to have no more problems with floating point math thanks to g3gg0, though I have yet to try...

One point up also for me? ;D
I'm thinking about it every night :) :)
#24
@Sztupy
You will be my hero :)

I will very pleased to offer all my help to test of course...Alpha,beta version all is welcome :)
#25
Hello,

Like sure many other users, I miss every day more the app for Android"ML camera controller" wrote by forum user Sztupy
It ceased working a long time ago, maybe when we changed all the layout menu or even before.
Now the only possibility to continue using it is with very old builds that lacks all the new big features developed after that (all modules, RAW rec at first)
So why not starting a funding raise to help resurrecting it? Like a sort of bounty :)
I'm starting offering 200$ (raised to 300$ !!!) that the developer/s can choose between: keep the money, donate it to the ML project, a charity organization or any other use.
If, (and I hope that) more rewards offers will come from other users, I'll update this post accordingly.

Prerequisites for the developer/s:
Be excited about working on it :) (of course).
An android Smartphone/Tablet (better if rooted) with an USB Host capable port, (maybe not necessary, Sztupy successful run it within a Android-x86 build inside VMWare Player)
A ML-compatible camera
Android developing knowledge

Unfortunately only source code for the ML part is available (not for the Android .apk part) but maybe Sztupy can help us with that or join this challenge itself.
I wrote a PM to him (see response below)

Sure it's not a simple work but I also hope that starting working on it can also work like a leverage and start a chain reaction :)
Just to assure of the goodness and seriousness of my intentions we can concord a step by step path with reward at every progress step reached.
All the work need to be public and open-source:
The ML part need to be regularly committed to bitbucket ML repository (if the developer have write access to it) or a pull-request created and keep updated if not.
Also the Android .apk part need to be totally open-source and hosted in a freely chosen code-repository platform (Bitbucket preferred)
My camera actually is a 60D and I own both a Samsung rooted phone and a rooted Samsung tablet so obviously is necessary that works at least on these devices combinations for reward purpose)

More info here:

Original developing thread on Google groups https://groups.google.com/forum/#!topic/ml-devel/Sw0B1kpFlIU

Bitbucket ML controller source https://bitbucket.org/sztupy/magic-lantern/src
Xda Android apps http://forum.xda-developers.com/showthread.php?t=1527773
App on Play Store https://play.google.com/store/apps/details?id=hu.sztupy.android.mlcontroller&hl=it

The idea is to fuse the the "Sztupy android ML controller" with the Android "DSLR Dashboard" app (a remote control camera app very similar to "Chainfire DSLR controller" but totally opensource GPLv3)
The "DSLR Dashboard" program itself is a mature opensource project that we can use as good start point.
It has the advantage of don't loss developing time duplicating functions already available on that program. (the "Liveview" part for example, if we find it more faster/reliable than Stzupy implementation).
We can focus instead on the "remote control" part, modifying it at our needs, integrating it with specific code from old Stzupy app to send and receive from/to camera other than normal PTP commands also the specific PTP-ML ones, simulate keypress of camera physical buttons and interact with ML menus, and maybe also have a sort of "command line" with possibility to launch command and scripts (when they will return :)

Anyone interested ?? :)

About the Dslr Dashboard program:

Source repository https://code.google.com/p/dslrdashboard/
App on Play Store https://play.google.com/store/apps/details?id=com.dslr.dashboard

development thread (it called nikon DSLR dashboard but don't worry :)
http://forum.xda-developers.com/galaxy-s2/themes-apps/app-nikon-dslr-dashboard-via-usb-v0-30-t1256583

It's also recommended from the author of LrTimelapse (..<<Shooting Holy Grail sequences involve changing exposure time and ISO in between the shooting interval. To avoid touching the camera when doing this, Zoltan Hubai, the developer of DslrDashboard, kindly agreed to implement a "LRTimelapse Mode" into his great Android App for controlling the camera.>>)

Maybe the GUI is not so nice as the popular "DSLR Controller" but have more or less the same features including the ability of remote control the camera with PTP commands other than USB cable also via wireless with the cheap (less than 40$) "TP LINK MR3040 - Portable Battery Powered 3G/4G Wireless N Router" as described here in a previous post
http://www.magiclantern.fm/forum/index.php?topic=10688.msg104121#msg104121
But most important is opensource GPL v3
On Nikon side also the little Nikon WU-1a/1b adapter is supported (not tested on Canon perhaps)

Simply flashing the TPLINK MR3040 with a customized firmware based on opensource project Openwrt that include a little serverside program called DslrDashboardServer (also totally opensource)
That program, auto-loaded at MR3040 startup, with the camera connected to it with USB) to it, relay PTP commands to the client program on smartphone or tablet via WiFi, from where you can control the camera.
DslrDashboardServer repository: https://github.com/hubaiz/DslrDashboardServer

I did not yet contacted the author but maybe also he can help us. (He can be willing, he already did some custom changes to the program after LRtimelapse author suggestions)
I'll keep this thread updated with every progression about the project.

++A free MR3040 will be offered at the first user that make a first tangible step to this project.

UPDATE 20/05/14
Increased reward to 250$, added a first-step reward (a MR3040) and changed to the Dslr Dashboard as opensource starting point.
See http://magiclantern.fm/forum/index.php?topic=9570.msg115991#msg115991

UPDATE 10/07/14
Changed this post to reflect info from my last post.
Raised reward to 300$