[2017.08.02] DSLR Controller v1.05

Search This thread
By:
Advanced…
G

georgech

Member
Jan 15, 2005
8
5
Works with Verizon Galaxy Nexus, Nook Color and 450D!

I picked up a Verizon Galaxy Nexus a couple of days ago, and am very happy to report that USB OTG is indeed now part of the OEM build as of ICS 4.0.2. This means that if you have a Galaxy Nexus, you can purchase the DSL Controller from the Market, and it will work with an appropriate USB OTG adapter. Pretty sure that this applies to the GSM version as well, but as I mentioned above, I happen to have the LTE Verizon iteration.

My camera is a 450D, so there are some known and expected VxWorks specific limitations:
1. no tap to autofocus, or any autofocus at all
2. tap to move the focus rectangle doesn't work, so there is no way to change the area zoomed for 5x and 10x view from within the app
3. No multishot drivemode capabilities

There is a workaround for item #2, and that is to use the cursor buttons on the camera body. If that doesn't work for you, try pressing the center select button on the body one time, as if you were toggling Live View. It won't interfere with the DSL Controller communication, but will allow you to use the cursor keys.

Besides the Nexus, I was also very surprised to see that the DSL Controller was now shown as compatible with my Nook Color running CM7. There was quite a bit of discussion in this thread regarding lack of OTG USB support, and insufficient CPU and memory resources on this device, so I was curious to see whether it will work.

It does! (It wasn't until after I tried it that I went back to search through this thread, and found post #880 from Chainfire confirming it:http://xdaforums.com/showpost.php?p=20082246&postcount=880). My first attempt resulted in an error regarding "a (very) low per-app memory limit", followed by closing of the DSL Controller. Per the instructions in the FAQ (http://dslrcontroller.com/faq.php#lowmemory), I modified the build.prop entry to update the dalvik.vm.heapsize to 196m. (For some reason there were two entries for dalvik.vm.heapsize in my build.prop, so I changed them both). After the build.prop changes and a reboot I still see the error message regarding the low per-app memory limit for some reason, but now DSL Controller starts up and works exactly as it does on the Nexus.

Even though the Nexus has a higher pixel density than the Nook Color (1280x720 vs 1024x600), the larger screen makes a huge difference for being able to precisely tweek focus at 10x. I was surprised by the fact that I actually preferred the experience on the Nook, even with the lower image quality and performance (e.g. half-speed live view and lower resolution).

Hopefully the above post will help someone who has a Galaxy Nexus, a Nook Color and/or a 450D. If anyone figures out why the "low per-app memory limit" error still comes up even with the modified build.prop, please let me know.

George

P.S. Gorjess, see the FAQ entry link above. I don't know about any specific Market apps for this, as I used the old school "'mount -O rw /system', 'vi build.prop', reboot" method.
 
  • Like
Reactions: olm3ca and Gorjess
M

msatter

Senior Member
Sep 30, 2007
159
17
When I am using DSLRcontroller in a studio setting with flashes I set the colour temperature on the camera to that of the flashes.
Using liveview DSLRcontroller, like on the camera, the picture looks yellowish. This is because the posing light of the flash is a much lower colour temperature than set on the camera. Posing light 2800 Kelvin and flash light 5600 Kelvin.

I like to request a filtering of only liveview on the phone/tablet can be colour filtering by a setting in the settings menu.

I suggest to the following values for full CTB: Alpha 64, Red 32, Green 128 and Blue 255

I can't give exact number because I only have half CTB filter sheet. I used the following APP to test it: Filter Your Screen from Kovit P.
 
Last edited:
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
DanielBoeV said:
The little adapter doesn't work with USB-drive/phone, so I apparently got something that's called a "USB-on-the-go" adapter that looks like one, but doesn't work like one, well whoop-de-doo..
Click to expand...
Click to collapse

Maybe your firmware version does not support USB host at all, and you should update your SGS2 firmware first ? From my search, I think you only said 2.3, not specifically which firmware version.

Settings -> About phone -> Build number

georgech said:
I picked up a Verizon Galaxy Nexus a couple of days ago, and am very happy to report that USB OTG is indeed now part of the OEM build as of ICS 4.0.2. This means that if you have a Galaxy Nexus, you can purchase the DSL Controller from the Market, and it will work with an appropriate USB OTG adapter. Pretty sure that this applies to the GSM version as well, but as I mentioned above, I happen to have the LTE Verizon iteration.

My camera is a 450D, so there are some known and expected VxWorks specific limitations:
1. no tap to autofocus, or any autofocus at all
2. tap to move the focus rectangle doesn't work, so there is no way to change the area zoomed for 5x and 10x view from within the app
3. No multishot drivemode capabilities

There is a workaround for item #2, and that is to use the cursor buttons on the camera body. If that doesn't work for you, try pressing the center select button on the body one time, as if you were toggling Live View. It won't interfere with the DSL Controller communication, but will allow you to use the cursor keys.

Besides the Nexus, I was also very surprised to see that the DSL Controller was now shown as compatible with my Nook Color running CM7. There was quite a bit of discussion in this thread regarding lack of OTG USB support, and insufficient CPU and memory resources on this device, so I was curious to see whether it will work.

It does! (It wasn't until after I tried it that I went back to search through this thread, and found post #880 from Chainfire confirming it:http://xdaforums.com/showpost.php?p=20082246&postcount=880). My first attempt resulted in an error regarding "a (very) low per-app memory limit", followed by closing of the DSL Controller. Per the instructions in the FAQ (http://dslrcontroller.com/faq.php#lowmemory), I modified the build.prop entry to update the dalvik.vm.heapsize to 196m. (For some reason there were two entries for dalvik.vm.heapsize in my build.prop, so I changed them both). After the build.prop changes and a reboot I still see the error message regarding the low per-app memory limit for some reason, but now DSL Controller starts up and works exactly as it does on the Nexus.

Even though the Nexus has a higher pixel density than the Nook Color (1280x720 vs 1024x600), the larger screen makes a huge difference for being able to precisely tweek focus at 10x. I was surprised by the fact that I actually preferred the experience on the Nook, even with the lower image quality and performance (e.g. half-speed live view and lower resolution).

Hopefully the above post will help someone who has a Galaxy Nexus, a Nook Color and/or a 450D. If anyone figures out why the "low per-app memory limit" error still comes up even with the modified build.prop, please let me know.

George

P.S. Gorjess, see the FAQ entry link above. I don't know about any specific Market apps for this, as I used the old school "'mount -O rw /system', 'vi build.prop', reboot" method.
Click to expand...
Click to collapse

Re: Nexus

It also works on the GSM version of the Galaxy Nexus - I have one. I will update the website/program description to reflect this soon. Thanks for letting me know about the VZW version working!

Re: Nook Color

It now actually shows up for almost all devices. That does however not mean it works. It can be made to work with the Nook Color though, fortunately!

Re: Memory

Interesting the error still shows. When DSLR Controller launches, it shows a popup for a few seconds with the version number. It also says: "Memory: ... (XXX MB)". Can you let me know what it says exactly ? If you could also attach your entire Nook build.prop file, that would be helpful to me as well.

I really should make an option inside DSLR Controller to manipulate this.

Thanks for all the feedback!

msatter said:
When I am using DSLRcontroller in a studio setting with flashes I set the colour temperature on the camera to that of the flashes.
Using liveview DSLRcontroller, like on the camera, the picture looks yellowish. This is because the posing light of the flash is a much lower colour temperature than set on the camera. Posing light 2800 Kelvin and flash light 5600 Kelvin.

I like to request a filtering of only liveview on the phone/tablet can be colour filtering by a setting in the settings menu.

I suggest to the following values for full CTB: Alpha 64, Red 32, Green 128 and Blue 255

I can't give exact number because I only have half CTB filter sheet. I used the following APP to test it: Filter Your Screen from Kovit P.
Click to expand...
Click to collapse

Sure, I can build this. The effect will be different from "Filter Your Screen" because I will not be using a "filter", but direct color manipulation. Unlike a transparent overlay like that app uses I have direct access to the pixels...

One of the big differences is that for example black stays black, unlike with an overlay. Anyway, the point is, due to the difference in calculation the number you state mean little to nothing, because the alpha component does not exist, this changes the RGB values. But I'll include a K to RGB thingy. However, due to the screen not being calibrated, that's not an exact science and you may have to slightly adjust the values to match the actual flash picture.
 
  • Like
Reactions: Gorjess
pspilot

pspilot

Senior Member
Mar 30, 2008
224
47
Bavaria
I tried it on a Galaxy Note and I get the low memory message (48M only, OS v2.3.6). It's rooted of course, so I looked into the build.prop - surprisingly dalvik.vm.heapsize was already =128m, found also only one instance. Changed it to 196m, no luck. The app is still reporting a low memory of 48m.

1) Any ideas? Are there other places than the build.prop to tweak that parameter?

2) In your FAQ you mention apps/helpers, that allow checking/changing that memory parameter more convenient. Can you give me a hint, which app(s) that is/are?

3) More a suggestion: it's nice to see the camera battery status, but it would be nice to know the tablets battery status too.

Apart from the above difficulties, it worked like a charm with a 5DII as well as with a 1DmkIV.


EDIT: Searched the market for 'heap size' and found the "VM Heap Tool" (yep, I could have had that idea before I asked :D). Anyway, it reports exactly the 128 or 196M I do set in the build.prop. Just DSLR Controller doesn't seem to see more than 48M. Did I mention that it's working anyway? I dunno what's that 'reduced functionality' (or similar msg) means, but for me it looks like it's working normally.
 
Last edited:
Xkan

Xkan

Senior Member
Jan 6, 2009
299
0
I received my USB-cable today and tested it with my 450D and my Galaxy Nexus (official 4.0.2) - everything I tested so far is working - thank you for the great app :)

I read and know that there is no autofocus-support right now, is this a general limitation of VxWorks or is there any chance to see autofocus with my 450D in a future version?
 
C

cybervipr

Member
Aug 5, 2010
6
0
Just got my Galaxy Nexus (Verizon) and immediately loaded up the app after anxiously waiting to have a compatible device since I first read about this app. Works amazingly. Really really awesome stuff. One of the only things that I was disappointed about was not being able to tap to autofocus with by 500D. Not sure if that's a problem with my camera or phone or something that isn't built into the app yet for all devices...just wanted to report it as not working.

I also didn't mess with moving around the zoomed view too much, but I believe that swiping around would move it a little bit (not quickly or smoothly, but I remember that working). Will mess around with that more tonight.
 
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
Hmm, I'm not sure what else influences this. However, DSLR Controller simply asks the OS: "err, so... how much memory are you willing to give me if I ask really nice ?" and apparently your phone is telling the app that its 48m.

I'll do some more digging into this.

EDIT: Could you by any chance also post your /init.rc, and the output of "adb shell ps" ?
 
Last edited:
pspilot

pspilot

Senior Member
Mar 30, 2008
224
47
Bavaria
Chainfire said:
Hmm, I'm not sure what else influences this. However, DSLR Controller simply asks the OS: "err, so... how much memory are you willing to give me if I ask really nice ?" and apparently your phone is telling the app that its 48m.
Click to expand...
Click to collapse
Understand, sounds logical. I'll dig a bit myself, why the system is reporting the 48m.

EDIT: Could you by any chance also post your /init.rc, and the output of "adb shell ps" ?
Click to expand...
Click to collapse
I will, give me a bit time. 'Pre-christmas' is killing me :) ...
(Actually it was the wrong time to start the testing now, but I couldn't resist).
 
M

msatter

Senior Member
Sep 30, 2007
159
17
Chainfire said:
Sure, I can build this. The effect will be different from "Filter Your Screen" because I will not be using a "filter", but direct color manipulation. Unlike a transparent overlay like that app uses I have direct access to the pixels...

One of the big differences is that for example black stays black, unlike with an overlay. Anyway, the point is, due to the difference in calculation the number you state mean little to nothing, because the alpha component does not exist, this changes the RGB values. But I'll include a K to RGB thingy. However, due to the screen not being calibrated, that's not an exact science and you may have to slightly adjust the values to match the actual flash picture.
Click to expand...
Click to collapse

That would be great and the method you going to use also overcome the problem of filters/overlay which are decreasing the total brightness.
 
pspilot

pspilot

Senior Member
Mar 30, 2008
224
47
Bavaria
Chainfire said:
EDIT: Could you by any chance also post your /init.rc, and the output of "adb shell ps" ?
Click to expand...
Click to collapse
I hope the "adb shell ps" output is right, I produced it from a 'DOS shell' (win7) directly into a file - I'm not an Android developer, so I'm not really familiar with these tools :).

my init.rc
my adb_shell_ps.txt


EDIT: and yet another post thought :): how exactly can I determine the 'degration of operation' due to the lack of memory? Because apart from that message, that the app is only seeing 48m, I'm not having any problems using the app. So maybe it's only a wrong report and the app can use 128m after all? I know, that sounds odd. So again, what should I see or not see, if there are really only 48m available?
 
Last edited:
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
pspilot said:
I hope the "adb shell ps" output is right, I produced it from a 'DOS shell' (win7) directly into a file - I'm not an Android developer, so I'm not really familiar with these tools :).

my init.rc
my adb_shell_ps.txt
Click to expand...
Click to collapse

Nothing in these files or the one you posted earlier points to any reason for it being 48m. I'm completely sure its not 128m by default though on 2.3.6, and I'm also sure the problem does not occur on my stock+rooted Note firmware.
 
  • Like
Reactions: pspilot
pspilot

pspilot

Senior Member
Mar 30, 2008
224
47
Bavaria
Chainfire said:
Nothing in these files or the one you posted earlier points to any reason for it being 48m. I'm completely sure its not 128m by default though on 2.3.6, and I'm also sure the problem does not occur on my stock+rooted Note firmware.
Click to expand...
Click to collapse
Ok, thanks, I'll go searching myself a bit whats going on. Did you see my addition in my last post? Sorry, that crossed your answer.
 
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
pspilot said:
Ok, thanks, I'll go searching myself a bit whats going on. Did you see my addition in my last post? Sorry, that crossed your answer.
Click to expand...
Click to collapse

Ah it did cross.

If the app is literally telling you it has 48m, well, some pieces of code decide functionality based on that value.

With 64m or less, the liveview decoder will switch to single threaded mode. This means you get a lower FPS on liveview.

With 128m or less, disk buffering is used in various places, while with more than 128m memory buffers are used. The latter is faster.

Additionally, the maximum zoom factor in image review is much reduced when low on memory. The image you are zooming on may only be 1/2 or 1/4 or 1/8th the resolution of the actual on-disk image. (This is all calculated, tried, and tested dynamically).

Finally, in various situations, the app may need more memory than is available, and it cannot dynamically recover from this situation, and it will crash.

I have done my best and written a lot of code to reduce the likelyhood of the latter happening, but it is still possible.
 
  • Like
Reactions: pspilot
pspilot

pspilot

Senior Member
Mar 30, 2008
224
47
Bavaria
Chainfire said:
I have done my best and written a lot of code to reduce the likelyhood of the latter happening, but it is still possible.
Click to expand...
Click to collapse
Wow, I can see that, impressive! I thought I'll see some 'sorry, too less mem' or such :). Ok then I really have to search that flaw, I want the speed. Especially if it's working on your Note with rooted Stock, it HAS to work, if the ROM/Kernel is right. Well, back to these guys :) ... thanks so far.
 
G

georgech

Member
Jan 15, 2005
8
5
Chainfire said:
Re: Memory

Interesting the error still shows. When DSLR Controller launches, it shows a popup for a few seconds with the version number. It also says: "Memory: ... (XXX MB)". Can you let me know what it says exactly ? If you could also attach your entire Nook build.prop file, that would be helpful to me as well.
Click to expand...
Click to collapse

The startup message is as follows:

"DSLR Controller v0.80
Copyright (C) 2011 - Chainfire
Memory class: Very Low (32 MB)"

The error message after that is: "Your device has a very low per-app memory limit - 32 MB. It is advised to configure a 128 MB or higher limit. Running in reduced quality mode."

My build.prop is attached.

Chainfire said:
Hmm, I'm not sure what else influences this. However, DSLR Controller simply asks the OS: "err, so... how much memory are you willing to give me if I ask really nice ?" and apparently your phone is telling the app that its 48m.

I'll do some more digging into this.

EDIT: Could you by any chance also post your /init.rc, and the output of "adb shell ps" ?
Click to expand...
Click to collapse

My init.rc is also attached. Unfortunately I don't have ADB set up on my system for Nook Color, but I can SSH in and run "ps" that way. I'm guessing you are looking for memory usage stats, so maybe "ps -o vsz,rss" while DSLR Controller is running?

George
 

Attachments

  • build.prop.txt
    2.4 KB · Views: 25
  • init.rc.txt
    14.7 KB · Views: 18
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
Another thing that may prove helpful to get to the bottom of this memory situation, but will require some kind of wireless ADB solution like adbWireless... Run the following commands while DSLR Controller is in "Image Review" mode:

dumpsys meminfo eu.chainfire.dslrcontroller

Also:

getprop dalvik.vm.heapsize
 
You must log in or register to reply here.

Similar threads

Chainfire
  • Locked
[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73
Replies
7K
Views
2M
KennyG123
KennyG123
Chainfire
[2016.10.22] DSLR Controller *AFMA* v0.11 ALPHA
Replies
14
Views
133K
O
or1m
Z
  • Locked
[APP] DroidMote Server & Client - Wifi Control between Android Devices ++
Replies
2K
Views
723K
M
malybru
gatesjunior
SuperSU Me Please !!! (Updated 01/28/2017)
Replies
3K
Views
833K
galaxys
galaxys
AnkitChowdhury
[Android 4.0+][ROOT]Game Controller 2 Touch
Replies
256
Views
171K
E
E.Sivko

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 91
    Chainfire
    Chainfire
    In an effort to de-duplicate a lot of information, I have moved the bulk of it to the DSLR Controller website. This thread still remains the place to get support, discuss, and ask questions, though!

    DSLR Controller was the first and remains the best app to fully control your Canon EOS DSLR from your Android device, through USB cable or Wi-Fi connection. No computer or laptop required, no root required, only a compatible mobile device, a compatible camera, and if connecting through USB, the right cable.

    We strongly suggest you read up on the website ( http://dslrcontroller.com/ ) about what DSLR Controller can do, how it works, and how to use it, before purchasing. The website contains a wealth of information you should know before using.

    Not all devices are compatible, especially if you want to use a USB connection. For a free app you can use to test compatibility, see the "Remote Release" app ( http://market.android.com/details?id=eu.chainfire.remoterelease ). If you need a refund, go to our website ( http://dslrcontroller.com/ ) and follow the instructions in the FAQ entry. We cannot process refunds through email.

    Usage notes, feature lists, device compatibility lists, changelogs, FAQs, can all be found on our website: http://dslrcontroller.com/

    Most questions should go to the support and discussion thread at XDA-Developers.com:
    http://xdaforums.com/showthread.php?t=1202082


    Features

    Features include but are not limited to:

    - Live View
    - Auto Focus (tap Live View)
    - Manual focus adjustments (in AF mode)
    - Histogram
    - Zoom control
    - Grid and aspect ratio overlay
    - Bulb capture
    - Continuous capture
    - Image review (+ follow shot, gallery)
    - Image filters (peaking, contrast, channel mask, grayscale, 4 modes/filter)
    - Video recording
    - HDR/Auto Exposure Bracketing
    - Focus Bracketing (incl. HDR)
    - Focus A-B
    - Mirror Lockup support
    - Timelapse (incl. HDR)
    - Wi-Fi Passthrough
    - Extensive modification of settings
    -- Shutter speed
    -- Aperture
    -- ExpComp and Bracket
    -- ISO speed
    -- Auto-Focus Mode
    -- Focus and Zoom area (tap-and-hold Live View)
    -- Picture Style
    -- Drive Mode
    -- White Balance
    -- Color Temperature
    -- Auto-Lighting Optimizer
    -- Metering Mode
    -- Image and video quality and format

    Available options depend on the mode you have your camera set to (M, Av, Tv, etc) and camera model. Refer to the website ( http://dslrcontroller.com/ ) for further details.


    Supported Android devices:

    If you are connecting using Wi-Fi, virtually all modern Android devices are supported (your camera needs Wi-Fi support, though). If you are connecting over USB, your device needs USB host support - most recent devices do. Please see the 'Devices' section on our website ( https://dslrcontroller.com/devices.php ) for further information.

    If your camera only supports USB, you can modify a TL-MR3040 to provide a Wi-Fi connection ( http://dslrcontroller.com/guide-wifi_mr3040.php )


    Supported Canon EOS models:

    Newer cameras than listed below are usually supported.

    Full support:
    - 1D Mark IV
    - 1D X
    - 1D X Mark II
    - 5D Mark II
    - 5D Mark III
    - 5D Mark IV
    - 5Ds(r)
    - 50D
    - 500D
    - 550D
    - 6D
    - 60D
    - 600D
    - 650D
    - 7D
    - 7D Mark II
    - 70D
    - 700D
    - 750D
    - 760D
    - 80D
    - 1100D
    - 1200D
    - 1300D
    - 100D

    Limited support:
    - 1D mk III
    - 1Ds mk III
    - 30D
    - 40D
    - 400D
    - 450D
    - 1000D

    No support:
    - pre-2006 models
    - EOS M mirrorless devices (work in progress)


    Let us know which hardware you are using with DSLR Controller!
    View
    10
    Chainfire
    Chainfire
    Must-read information

    Screenshots and video:
    http://dslrcontroller.com/about.php

    Download, BETA usage notes, and changelogs:
    http://dslrcontroller.com/download.php

    Table of supported Android devices and Canon EOS DSLRs:
    http://dslrcontroller.com/devices.php

    FAQ:
    http://dslrcontroller.com/faq.php
    View
    8
    Chainfire
    Chainfire
    nickzee said:
    I am a professional architectural photographer and have adopted your DSLR app into my workflow. Thank you for the great design and amazing functionality. It is a pleasure to work with*.

    I would like to know what the future holds for DSLR Contorller. I noticed you are not very active on this forum (last post on 2/26/2015), but wanted to encourage you to keep on developing because I, We need it!!!

    ...
    .
    Click to expand...
    Click to collapse

    DSLR Controller was originally built for Android 2.x years ago, and a lot of things have changed both in the camera world as well as the mobile world. Despite bolting on many improvements, the code shows its age. To take it to the next level and get everything I want into it (customizability, compatibility, portability, speed, etc), a lot of the core needs to be changed, the UI needs to be changed (if not in appearance or functionality then certainly how it's been coded), etc. It pretty much comes down to not just overhauling major parts, but completely redoing it from scratch, and rebuilding it as envisioned from the ground up.

    This brings with it a number of issues. It is a lot of development time (and thus money) investment up front, of which you will see no results, until it is almost done. In the mean time, you can't really release anything that isn't up to par with the current version of DSLR Controller, and you can't just replace the current version as old users/devices may no longer be compatible, stranding paying customers. A lot of additional equipment needs to be gotten and tested with to ensure compatibility and portability (remote and end-user testing isn't really workable with apps like these). Not to mention that DSLRs are pretty much doomed, and this is definitely being reflected in daily sales.

    The past year hasn't been very good on a personal level, which isn't your problem of course, but it is one reason for the lapse in development of certain apps. This one adds to the fact that in light of the above, it feels like a waste of resources to spend a lot of time on improvements in the current app. There have been talks with a team (from a big brand in the camera world) to take over the IP, pretty much solving the resource problem, but ultimately that fell through, after the talks taking up a large part of my time for months.

    Also, I know it seems like DSLR Controller has generated a lot of funds, but spread out over the years its been available, subtracting equipment costs, corporate taxes, wage taxes, etc, you wouldn't be able to hire one(!) half-competent coder for the money left at today's going rates, not to mention the risks involved with hiring people. Even though I do get paid and get all these toys to play with, wanting to build it has always been a large part of this, as there are definitely more profitable ways to spend the time. At the same time having to compete with $300 equipment, and people still complaining about the $8 price.

    This app is also a complete nightmare to support, as by far the bulk of the connection issues are not due to the app itself, but due to camera configuration, phone configuration, hardware incompatibilities, firmware incompatibilities, etc. That is, excepting the case where DSLR Controller just hangs, which sometimes (but definitely not always) is an issue with the app. Not to mention the droves of questions and reported issues by people who simply don't understand how their cameras work.

    All of that being said, I do believe there may be a business case where a rebuild with additional features and support for Nikon and/or Sony and/or (insert other brands here) and other OSs like Linux, iOS, OS X, Windows, etc using a shared core may at least break even. That is, providing I can find competent developers to do it (as there is no way I can pull this off by myself), and finding said competent developers with at least somewhat relevant skills might in fact be the biggest problem to solve. Still, even in the best case scenario, I don't believe any work will get started before end-of-summer.

    Don't mistake the lack of visible activity for lack of interest. What to do with DSLR Controller and how to get there is something I consider every day, as in the end, it's still the app I've enjoyed most developing over the years. But if the solution means spending more resources updating the current app, developing a new one, or investing funds to get a whole new company off the ground with a handful of people to cover both major brands and major OSs - that I don't know yet. But I do hope to have an answer to that sooner rather than later.

    (this post was written in a rush as I need to run for another appointment but I didn't want to leave this unsaid, so if it's jumping here and there and not fully coherent, that's why)
    View
    6
    Chainfire
    Chainfire
    KazeOne said:
    Hey Chainfire, I was wondering if there was an ETA for the next update? I know asking such things is never liked, Im not looking for a hard date just a rough idea and if there is anything else we can do to help?
    Click to expand...
    Click to collapse

    After next week I have three weeks reserved for exclusive DSLR Controller work, if that doesn't finished the upcoming update, I'd be surprised :)
    View
    5
    R
    rainabba
    nkhs9412235 said:
    The price will go up once v1.0 is reached, but the upgrade is free for those who have this BETA???

    Why can't I see free version?
    Click to expand...
    Click to collapse

    Because it's good software and the developer deserves to get paid. Beta doesn't mean it's not valuable, it means that the software isn't very mature or well tested. if you want it now, you pay. If you want to pay once it's well tested and proven then wait.

    Either way, quit your sniveling people. This is an AMAZING deal at that price. If you can afford a DSLR and know how to use it, you can afford 10 times this and would gladly pay it. If you think otherwise, you likely don't need this software to begin with and have nothing to complain about.
    View

New posts