vasile

Better wait a bit, most likely a new version out tomorrow. 

Better wait a bit, most likely a new version out tomorrow. 

Better wait a bit, most likely a new version out tomorrow. 

Better wait a bit, most likely a new version out tomorrow. 

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

I am now doing groundwork for mods that will be a lot more advanced. This is why you are likely to not see any visible progress for a while. In essence I am trying to zombify the di-camera-app to enable bi-directional communications between it and my mod infrastructure, and to introduce the possibility to "drive" it from the mod runtime..
If successful this should allow many things, potentially including native UI integration, true BBAF, native integration of focus stack & focus pull, etc. etc. My plan is to make it an extensible and open framework upon which others might build on (e.g. Otto) to deliver things that work in coordinated manner with the native app, and that are aware of what the native app does. This will allow, for example, to have the UI permanently up to date regardless of what the mod does (as opposed to today where mods do not update the UI because they are independent of di-camera-app).
NB. Nothing above is a promise or commitment and you do not see any timeline, do you?
PS. I still covet that lens ;-)

Short answer: no progress. This will take a long time and I am trying to do things with a lot more impact first.
You should check this from time to time - I keep it up to date, and you will save some time by just checking it.
rgds

this.
Run out of slots to enable.
Any NX500 beta testing volunteers please PM me.

this.
Run out of slots to enable.
Any NX500 beta testing volunteers please PM me.

1. no idea, you should experiment with your card
2. this will require deep interference with di-camera-app. Basically I would need to zombify di-camera-app and make it play my tune. Possible and I am working towards that because I would like to achieve a better BBAF which requires the same type of interference.
But definitely not short term and may not even be achievable. NB. This is not a promise and you did not see any time frame above, did you?

nx-patch v5.1
rgds

nx-patch v5.1
rgds

long presses are not supported by Otto's keyscan...
How about double click on the button to illuminate top lcd?

nx-patch v5.1
rgds

long presses are not supported by Otto's keyscan...
How about double click on the button to illuminate top lcd?

I do not know - on my camera EV always generates double events and it is impossible to combine it with OK :-( I could change it in the release but it would be untested by me - or I could put in a disclaimer that it does not work for me.

this :-). Have fun.

I guess it depends on whom you ask. To me the hack only overcomes artificial marketing-imposed limits. In any case I bricked my burner NX500 (oh, my personal one too - but that one is still awaiting repair) and Samsung repaired it without a peep under warranty.
Now I do not TRULY know if it was me - the motherboard was replaced and to my knowledge nothing I was doing could have caused a hardware failure - but in any case they fixed it under warranty.
YMMV.
rgds

I guess it depends on whom you ask. To me the hack only overcomes artificial marketing-imposed limits. In any case I bricked my burner NX500 (oh, my personal one too - but that one is still awaiting repair) and Samsung repaired it without a peep under warranty.
Now I do not TRULY know if it was me - the motherboard was replaced and to my knowledge nothing I was doing could have caused a hardware failure - but in any case they fixed it under warranty.
YMMV.
rgds

I guess it depends on whom you ask. To me the hack only overcomes artificial marketing-imposed limits. In any case I bricked my burner NX500 (oh, my personal one too - but that one is still awaiting repair) and Samsung repaired it without a peep under warranty.
Now I do not TRULY know if it was me - the motherboard was replaced and to my knowledge nothing I was doing could have caused a hardware failure - but in any case they fixed it under warranty.
YMMV.
rgds