SX260 HS Porting Thread - page 32 - DryOS Development - CHDK Forum

SX260 HS Porting Thread

  • 642 Replies
  • 212390 Views
*

Offline rudi

  • ***
  • 129
  • A590IS_101B, SX260HS_100B
Re: SX260 HS Porting Thread
« Reply #310 on: 23 / August / 2012, 11:33:46 »
Advertisements
BTW. Are there any differences beetween 100b and 100c?
Yes many, that's normal.

*

Offline lapser

  • *****
  • 1093
Re: SX260 HS Porting Thread
« Reply #311 on: 23 / August / 2012, 12:28:27 »
Rudi,

Thanks! I was able to get the new version working with 100b. RAW file saving works, but still seems pretty slow. I think you said you were able to reduce the save time from 9 to 6 seconds? Does it take 6 seconds on other cameras? I tested it on a class 10 and a class 4 card, and the save time seemed the same, although I didn't measure it precisely. Transferring the same RAW file with Windows Explorer is almost instantaneous for the class 10, and takes a second or so for the class 4. I don't think the delay is in the card writing.

Do RAW files take this long to save for other cameras? I notice these are 18 mb files, so I assume they are 12 bit pixels instead of 10?

When I started with a newly formatted card and checked RAW cache and RAW save time, I got badpixel.bin errors. It also took and saved 2 jpg photos and triggered the flash twice when it was attempting to create badpixel.bin. It worked after I reformatted and did badpixel BEFORE setting cache and save time. After creating it once, I could create it again even with cache and save time set.

Where do you store or display the RAW save times? I didn't see it.

I also tried it with a 64gb SDXC card with exFAT and it worked with the firmware update method. Trying to make the card bootable didn't work. One reason is that the camera recognized the write protect and wouldn't do anything. This probably isn't specific to this camera, but it's something to fix in CHDK someday.

I only tested RAW saving with DNG files this time, but CRW files were also slow in the last version. I think the speed problem may be improved further if you can find where the remaining delay is.

Thanks again!
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline reyalp

  • ******
  • 14089
Re: SX260 HS Porting Thread
« Reply #312 on: 23 / August / 2012, 23:03:27 »
I also tried it with a 64gb SDXC card with exFAT and it worked with the firmware update method. Trying to make the card bootable didn't work. One reason is that the camera recognized the write protect and wouldn't do anything. This probably isn't specific to this camera, but it's something to fix in CHDK someday.
The bootable method takes advantage of the loader in the native Canon firmware. The Canon firmware does not load from exFAT. CHDK cannot change what the Canon firmware does before CHDK is loaded, so will never fix this.

You see the card locked message because CHDK isn't there to override the lock bit.

Up to 2011, the Canon firmware would only load binaries from FAT16, so you can count yourself lucky ;) You should be able reformat your card to FAT32.

Quote
Where do you store or display the RAW save times? I didn't see it.
It should show in the script console, but it might disappear quite quickly. You might see it if you switch to alt mode after shooting.
Don't forget what the H stands for.

Re: SX260 HS Porting Thread
« Reply #313 on: 23 / August / 2012, 23:07:55 »
I only tested RAW saving with DNG files this time, but CRW files were also slow in the last version.
DNG files require some additional processing by CHDK and so will alway appear to take longer to save than plain RAW files.  On my cameras (depending somewhat on the SD card speed) its almost a 2x difference.

Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline lapser

  • *****
  • 1093
Re: SX260 HS Porting Thread
« Reply #314 on: 24 / August / 2012, 02:03:53 »
The bootable method takes advantage of the loader in the native Canon firmware. The Canon firmware does not load from exFAT.
That explains a lot. Any chance of using a FAT32/exFAT dual partition?
Windows 7 will only format 32Gig max in FAT32. The only format options for my 64Gig card are exFat and NTFS. I guess I'll just use the firmware update method with exFat for now.

I found the RAW save time display, thanks, and tested it with DNG conversion on and off(CRW)

DNG: 6240,6210,6210
Turn DNG off and keep shooting
CRW: 8900,8900
Turn Camera off and back on
CRW: 9610,8790

So for me, the CRW pictures save SLOWER than DNG. I did see one CRW save time of 4910, but I'm not sure what I did, and can't repeat it.

I was also saving full resolution jpg, so it's possible that's part of the timing. Switched to 640x480 size CRW file:
6600,8830,8890

Switch to DNG: 6270, 6220

So it looks like there are still bugs in the RAW save function. What is a typical approximate save time for other cameras?
=====

Just finished my first CHDK time lapse video with the SX260. Wrote a quick script to shoot every 10 seconds and decrement shutter speed by 1 after each shot.

Spencer's Butte Sunset - August 22, 2012
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX260 HS Porting Thread
« Reply #315 on: 24 / August / 2012, 03:42:21 »
The bootable method takes advantage of the loader in the native Canon firmware. The Canon firmware does not load from exFAT.
That explains a lot. Any chance of using a FAT32/exFAT dual partition?
Windows 7 will only format 32Gig max in FAT32. The only format options for my 64Gig card are exFat and NTFS. I guess I'll just use the firmware update method with exFat for now.

With a card reader, from the command prompt you should be able to use 'format /FS:FAT32 X:' and replace X with the drive letter of your SD card.

If that doesn't work do a Google search for tools to format large drives as FAT32.

The ports for new cameras that support CHDK boot on FAT32 partitions usually don't include the code to support partition swapping. So partitioning the card probably won't work.

Quote
I found the RAW save time display, thanks, and tested it with DNG conversion on and off(CRW)

DNG: 6240,6210,6210
Turn DNG off and keep shooting
CRW: 8900,8900
Turn Camera off and back on
CRW: 9610,8790

So for me, the CRW pictures save SLOWER than DNG. I did see one CRW save time of 4910, but I'm not sure what I did, and can't repeat it.

I was also saving full resolution jpg, so it's possible that's part of the timing. Switched to 640x480 size CRW file:
6600,8830,8890

Switch to DNG: 6270, 6220

So it looks like there are still bugs in the RAW save function. What is a typical approximate save time for other cameras?
=====


That's very slow.
My G1X saves 25.2MB DNG files in 1.75 seconds to a 32GB Lexar 400X SD card.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline rudi

  • ***
  • 129
  • A590IS_101B, SX260HS_100B
Re: SX260 HS Porting Thread
« Reply #316 on: 24 / August / 2012, 06:37:09 »
badpixel.bin creation failed also on my sx260 (use cleaned sd-card) with revision 2093. I used the last weeks my patch with revision 2054. I create current build only for download. But, I see no reason for this problem on this time. DNG save time remains at approx. 6-7 seconds on class 4 card.

download provide now revision 2054:
-> sx260_100b
-> sx260_100c
Based of diff from here and trunk 2054.

*

Offline lapser

  • *****
  • 1093
Re: SX260 HS Porting Thread
« Reply #317 on: 24 / August / 2012, 13:35:25 »
badpixel.bin creation failed also on my sx260 (use cleaned sd-card) with revision 2093. I used the last weeks my patch with revision 2054. I create current build only for download. But, I see no reason for this problem on this time. DNG save time remains at approx. 6-7 seconds on class 4 card.
I think the badpixel.bin failure was related to my having the RAW cache turned on before I tried it the first time on a newly formatted card.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos


*

Offline lapser

  • *****
  • 1093
Re: SX260 HS Porting Thread
« Reply #318 on: 24 / August / 2012, 15:32:12 »
With a card reader, from the command prompt you should be able to use 'format /FS:FAT32 X:' and replace X with the drive letter of your SD card.
Thanks Phil. The command line format didn't work. After about an hour, it finished by saying "too big for FAT32"
This program worked and formatted with no delay:
http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm

The main limitation of FAT32 now is the 4GB file size limit for video files. I think CHDK already will write video files up to the file limit without a record time cutoff? If so, exFAT should let you record longer videos up to the size of your card.

It looks like I can already use exFAT with the firmware update method, but auto-boot is a lot easier. How about using a tiny FAT32 boot partition for the Canon firmware loader that just switches to the exFAT partition permanently? You'd only have to modify the ports for newer cameras that support exFAT, like the SX260. Or, if the partition code was independent of the camera, you wouldn't have to modify anything.

That's very slow.
My G1X saves 25.2MB DNG files in 1.75 seconds to a 32GB Lexar 400X SD card.
Phil.
Doesn't the G1X have RAW file capability without CHDK? How does the built in RAW save time compare to the CHDK save time?

If the G1X can convert and save larger files that fast, the SX260 should be able to save its RAW files at least that fast, shouldn't it?

My 12MPixel Panasonic FZ150 saves almost 15MB RAW files, at 10 bits/pixel (15/12)*8
The 12MPixel SX260 saves 18MB RAW files, at 12 bits/pixel  (18/12)*8
Canon says the G1X has 14 bits per pixel RAW, which fits your file size. I'm saving pennies to get the G1X with CHDK instead of a DSLR.

Bill
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX260 HS Porting Thread
« Reply #319 on: 24 / August / 2012, 18:28:35 »
The main limitation of FAT32 now is the 4GB file size limit for video files. I think CHDK already will write video files up to the file limit without a record time cutoff? If so, exFAT should let you record longer videos up to the size of your card.

It looks like I can already use exFAT with the firmware update method, but auto-boot is a lot easier. How about using a tiny FAT32 boot partition for the Canon firmware loader that just switches to the exFAT partition permanently? You'd only have to modify the ports for newer cameras that support exFAT, like the SX260. Or, if the partition code was independent of the camera, you wouldn't have to modify anything.

The 4GB file size limit also applies to exFat partitions in the camera - it's a hardwired limit in the firmware code for video so using an exFat partition won't change that.

According to the manual this limit still applies to the SX260.

Quote
Doesn't the G1X have RAW file capability without CHDK? How does the built in RAW save time compare to the CHDK save time?

Yes it does - I was just using it as an example because I had the camera with me.
A closer comparison is the SX40 which saves 18MB DNG files in 1.2 seconds on a fast SD card.

Quote
If the G1X can convert and save larger files that fast, the SX260 should be able to save its RAW files at least that fast, shouldn't it?

I would think so; but I can't explain why you are seeing such slow save times.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal