IXUS 170 Porting - page 8 - General Discussion and Assistance - CHDK Forum
supplierdeeply

IXUS 170 Porting

  • 81 Replies
  • 41985 Views
*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: IXUS 170 Porting
« Reply #70 on: 01 / July / 2021, 13:36:45 »
Advertisements
and there is an ixus170 / elph170 port in svn which probably only needs minor work.
exec require'camtests'.runbatch{bench=true,filexfer=true,shoot=true,xfersizebugs=true} now 26/0  8)
md grid fits full screen if set to Wide.
propset 6... Deutsch=66305, English=65537, Norsk=65793
Ps resolution (221) L/W=0, Lowlight=11
 
« Last Edit: 01 / July / 2021, 14:43:16 by Caefix »
All lifetime is a loan from eternity.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: IXUS 170 Porting
« Reply #71 on: 27 / July / 2021, 13:00:09 »
 :-[ (chdkptp) Canon <play> menu is only available after switching to <rec> and back first ...
« Last Edit: 27 / July / 2021, 14:40:11 by Caefix »
All lifetime is a loan from eternity.

*

Offline reyalp

  • ******
  • 13792
Re: IXUS 170 Porting
« Reply #72 on: 27 / July / 2021, 15:59:04 »
:-[ (chdkptp) Canon <play> menu is only available after switching to <rec> and back first ...
This is normal behavior for most cameras. Use one of the levents mentioned on https://chdk.fandom.com/wiki/PTP_Extension#FAQ to unlock
Don't forget what the H stands for.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: IXUS 170 Porting
« Reply #73 on: 01 / November / 2021, 13:10:54 »
The insert to lib.c from Ix190 https://chdk.setepontos.com/index.php?topic=13146.msg147224#msg147224 plus
Code: [Select]
    #undef  CAM_BITMAP_HEIGHT
    #define CAM_BITMAP_HEIGHT               360
in platform_camera.h results in fine adjusted zebra, md_grid, ptp-liveview.  :)

Replacing
Code: [Select]
// void *vid_get_viewport_live_fb() {    return 0; }
// with the "usual"

extern char active_viewport_buffer;
extern void* viewport_buffers[];

void *vid_get_viewport_live_fb()
{
    extern char active_viewport_buffer;
    extern void* viewport_buffers[];

//    if (MODE_IS_VIDEO(mode_get()) || is_video_recording())
   //     return viewport_buffers[0];     // Video only seems to use the first viewport buffer.

    // camera appears to use 4 buffers with in still shooting and video
    // Hopefully return the most recently used viewport buffer so that motion detect, histogram, zebra and edge overly are using current image data
    return viewport_buffers[(active_viewport_buffer-1)&3];
}
is fine, too. ... leads to appended screenshot :blink: (Muggeled up SD-cards.)

Placing insert to Sx120 or Ix130 tells
Code: [Select]
../../../../platform/sx120is/sub/100b/libplatformsub.a(lib.o): In function `vid_get_viewport_height':
lib.c:(.text+0x60): multiple definition of `vid_get_viewport_height'
../../../../platform/sx120is/libplatform.a(lib.o):lib.c:(.text+0xe8): first defined here
collect2.exe: error: ld returned 1 exit status
gmake[1]: *** [main.elf] Error 1
... because there´s a sub/.../lib.c. Without the definition there plus insert, md_grid is adjusted, zebra & LV as fine as before (Ix130). Both versions can´t record ptp-video. (Partition/space issue?)
« Last Edit: 01 / November / 2021, 16:21:29 by Caefix »
All lifetime is a loan from eternity.


Re: IXUS 170 Porting
« Reply #74 on: 31 / July / 2022, 20:52:01 »
Apparently not a lot is happening on development for the ixus 170. Seems to me this is a powerfull little cam which has lots of good things going for it.

I encounter a few problems with this camera, being:
-firmware still has alpha status, is not in the autobuild system and therefore can't be auto installed with the stick utility.
-when shooting a photo when completely zoomed out, theres extreme vignetting visible in the dng raw photo that was created. This is not visible in the jpg that was outputted by the cam (how is this possible??) Please take a look at the attached photo that illustrate what i mean. As you can see there are even black corners visible. Again, this is not visible in the jpg output from the cam.
-when dng cropping is left at it's default (setting = jpeg), there are black borders visible in the dng output. When set to cropping = active , these borders disappear.
« Last Edit: 31 / July / 2022, 20:57:31 by johnnybgoode »

*

Offline reyalp

  • ******
  • 13792
Re: IXUS 170 Porting
« Reply #75 on: 31 / July / 2022, 23:01:01 »
-firmware still has alpha status, is not in the autobuild system and therefore can't be auto installed with the stick utility.
Yes. As srsa_4c posted some years ago
I'm not sure what has or has not been tested.
http://chdk.wikia.com/wiki/Testing
If someone (with the camera) feels this port is stable enough to be released officially, please post here.

Quote
-when shooting a photo when completely zoomed out, theres extreme vignetting visible in the dng raw photo that was created. This is not visible in the jpg that was outputted by the cam (how is this possible??) Please take a look at the attached photo that illustrate what i mean. As you can see there are even black corners visible. Again, this is not visible in the jpg output from the cam.
This is normal. The camera does lens correction in software when it creates the jpeg. The raw shows you what the sensor saw. You can apply your own software lens correction in raw processing software.

Quote
-when dng cropping is left at it's default (setting = jpeg), there are black borders visible in the dng output. When set to cropping = active , these borders disappear.
This is odd. In the current the jpeg area is defined as smaller (5152x3864) than active area (5192x3904), as it should be.

What build are you using?

If you can upload sample DNGs somewhere, I can take a look. The files will be too large for the forum, you can use a file site like dropbox, google drive etc.
Don't forget what the H stands for.

Re: IXUS 170 Porting
« Reply #76 on: 01 / August / 2022, 16:56:02 »
I'm confused; i'm pretty sure i had to deal with black bars on the edges of photos outputted by the ixus170. I've swapped some sd cards, and now it seems the black bars are gone, both in dng cropping "jpg" and "active".

Here's the output from my cam, the first photo was shot in dng cropping=jpg, the second one in dng cropping=active:
https://ufile.io/f/zbk1r

I'm currently on build 1.5.0 revision 5075, date jul 14 2018. (fw 100a).

So this leaves me asking for the fw to be put in a beta/stable state, so it can be put in the autobuild system.

Re: IXUS 170 Porting
« Reply #77 on: 01 / August / 2022, 17:09:43 »
This port is now in svn.

Test version attached for firmware 100a.

I'm not sure what has or has not been tested.
http://chdk.wikia.com/wiki/Testing
If someone (with the camera) feels this port is stable enough to be released officially, please post here.

edit:
outdated test build removed

ixus170_elph170-100a-1.5.0-5056-full.zip (794.64 kB - downloaded 3 times.)

Can this port be released officially? That would makes things a lot easier (such as the stick utility being able to download the fw automatically).


*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: IXUS 170 Porting
« Reply #78 on: 02 / August / 2022, 11:13:28 »
Can this port be released officially? That would makes things a lot easier
>1000 builds later...  :haha
All lifetime is a loan from eternity.

*

Offline reyalp

  • ******
  • 13792
Re: IXUS 170 Porting
« Reply #79 on: 02 / August / 2022, 21:50:19 »
Can this port be released officially? That would makes things a lot easier (such as the stick utility being able to download the fw automatically).
It would be helpful if you can test whatever you are able to from https://chdk.fandom.com/wiki/Testing and report any issues.


@Caefix: Is the build you posted from the current trunk unmodified, or does it have your own changes? Generally, if you post a build you should say, and this is especially important if johnnybgoode is testing.

Also, you posted some changes earlier in https://chdk.setepontos.com/index.php?topic=12471.msg147233#msg147233 but I do not understand the changes or what issue they are supposed to address, and AFAIK they were never added. If there are specific problems with this port you are aware of, please described them.
Don't forget what the H stands for.

 

Related Topics