Quote from: LDBenjamin on 11 / March / 2018, 08:42:43Quote from: waterwingz on 10 / March / 2018, 23:34:32Quote from: LDBenjamin on 10 / March / 2018, 22:19:09Please let me know what I should do to test this.AFAIK, we have never made a definitive list for testing every thing that a porter sets in the sub/<fw> directories. In general, the first firmware version of a new port gets some high level functionality tests - with a bias towards things that are hard to find or have caused problems. Just getting CHDK to load and display menus correctly is a big step all by itself. Subsequent additions of different firmware versions for any released port get a bit of a free pass. If they appear to work then, based on the original port being good, we mostly assume they are okay until anyone reports otherwise .So the big things I'd suggest checking are :RAW/DNG images - take some shot with DNG enabled and assure yourself that the DNG images actually look like uncorrected versions of the related JPGUSB remote - enable this and just use a regular USB cable plugged into a spared charger or computer port to trigger it and assure it's workingexposure overrides in the Enhanced Photo Operations menu - set both Tv, Sv, & Av and make sure the resulting image change appropriately when you change the valuesset a long exposure time (30 seconds) and then see if dark frame subtraction control works ( if not, it will take 60 seconds to complete a 30 second exposure)try out the edge overlay, historgram, and zebra functions and make sure they seem to work (i.e. usable images on the camera's LCD)try running some scripts - there are four simple ones included with the CHDK installation file and hundreds more online at places like this play with anything else that tweaks your interestThere is learning curve here so feel free to post questions. If all else fails - RTFM. And tell us how you did - if the 1.01b build passes the above list of tests without crashing then we will release it for distribution in the autobuild.Thanks, I will test these out and get back to you.Here's what I have so far.RAW/DNG - I'm not noticing much difference between RAW and JPEG in Photoshop - is it possible that this camera's profile is in Photoshop, and it converts the RAW image automatically?USB remote - can't get the computer to recognize the camera when it's connected. I may have to get an actual USB remote and test with that.Histograms look OK.Zebra - can't get this to display.Edge overlay looks OK.Other features:Color change is fine.The text reader doesn't recognize carriage returns. I converted the user manual to text, and it looked OK on my computer, but when viewed with the camera, it's a solid block of text with no returns at the end of each line. Whatever code my text viewer is using to indicate this, the camera isn't recognizing it.When I change settings in Play (so the menu doesn't blink), if the lens retracts, pressing the shutter doesn't reactivate it. I have to turn the camera on and off to use the new settings.Still need to get to the exposure overrides, dark frame subtraction, and long exposure times - I haven't been able to get these to work but this may be due to other settings in the Canon menu.
Quote from: waterwingz on 10 / March / 2018, 23:34:32Quote from: LDBenjamin on 10 / March / 2018, 22:19:09Please let me know what I should do to test this.AFAIK, we have never made a definitive list for testing every thing that a porter sets in the sub/<fw> directories. In general, the first firmware version of a new port gets some high level functionality tests - with a bias towards things that are hard to find or have caused problems. Just getting CHDK to load and display menus correctly is a big step all by itself. Subsequent additions of different firmware versions for any released port get a bit of a free pass. If they appear to work then, based on the original port being good, we mostly assume they are okay until anyone reports otherwise .So the big things I'd suggest checking are :RAW/DNG images - take some shot with DNG enabled and assure yourself that the DNG images actually look like uncorrected versions of the related JPGUSB remote - enable this and just use a regular USB cable plugged into a spared charger or computer port to trigger it and assure it's workingexposure overrides in the Enhanced Photo Operations menu - set both Tv, Sv, & Av and make sure the resulting image change appropriately when you change the valuesset a long exposure time (30 seconds) and then see if dark frame subtraction control works ( if not, it will take 60 seconds to complete a 30 second exposure)try out the edge overlay, historgram, and zebra functions and make sure they seem to work (i.e. usable images on the camera's LCD)try running some scripts - there are four simple ones included with the CHDK installation file and hundreds more online at places like this play with anything else that tweaks your interestThere is learning curve here so feel free to post questions. If all else fails - RTFM. And tell us how you did - if the 1.01b build passes the above list of tests without crashing then we will release it for distribution in the autobuild.Thanks, I will test these out and get back to you.
Quote from: LDBenjamin on 10 / March / 2018, 22:19:09Please let me know what I should do to test this.AFAIK, we have never made a definitive list for testing every thing that a porter sets in the sub/<fw> directories. In general, the first firmware version of a new port gets some high level functionality tests - with a bias towards things that are hard to find or have caused problems. Just getting CHDK to load and display menus correctly is a big step all by itself. Subsequent additions of different firmware versions for any released port get a bit of a free pass. If they appear to work then, based on the original port being good, we mostly assume they are okay until anyone reports otherwise .So the big things I'd suggest checking are :RAW/DNG images - take some shot with DNG enabled and assure yourself that the DNG images actually look like uncorrected versions of the related JPGUSB remote - enable this and just use a regular USB cable plugged into a spared charger or computer port to trigger it and assure it's workingexposure overrides in the Enhanced Photo Operations menu - set both Tv, Sv, & Av and make sure the resulting image change appropriately when you change the valuesset a long exposure time (30 seconds) and then see if dark frame subtraction control works ( if not, it will take 60 seconds to complete a 30 second exposure)try out the edge overlay, historgram, and zebra functions and make sure they seem to work (i.e. usable images on the camera's LCD)try running some scripts - there are four simple ones included with the CHDK installation file and hundreds more online at places like this play with anything else that tweaks your interestThere is learning curve here so feel free to post questions. If all else fails - RTFM. And tell us how you did - if the 1.01b build passes the above list of tests without crashing then we will release it for distribution in the autobuild.
Please let me know what I should do to test this.
I just tried loading several grids. They only appear in the upper left quadrant of the viewscreen. They seem to be complete, just too small. I have my camera set to save the largest file size for photos but that shouldn't make a difference.
Try out md_tune. The grids there are correct for motion detection on digic 6. [link]https://chdk.setepontos.com/index.php?topic=12918.40[/link]
Quote from: LDBenjamin on 21 / March / 2018, 10:26:54I just tried loading several grids. They only appear in the upper left quadrant of the viewscreen. They seem to be complete, just too small. I have my camera set to save the largest file size for photos but that shouldn't make a difference.CHDK grids have been a bit messy for a while - it was one of the earliest things added to CHDK and has not really been maintained. Grids are defined using small coordinate files that assume you have a 360x240 LCD display (the standard for many years with Canon P&S cameras). I wrote a patch that re-scaled each grid as it was loaded to fill the actual dimensions of the camera's LCD but never released it. It was actually more efficient to just produce new grid files created for actual LCD sizes (i.e. less processing by the cameras CPU for scaling).So far, nobody has gotten around to creating new grid files for D6 cameras - and that's why you see the image all pushed up into the upper left hand corner.See : Grids : issues and challenges]https://chdk.setepontos.com/index.php?topic=13239.0]Grids : issues and challenges
If I double the numbers in the grid file, will that make it twice as big in both directions, thereby filling the screen?
So far, nobody has gotten around to creating new grid files for D6 cameras - and that's why you see the image all pushed up into the upper left hand corner.
If I double the numbers in the grid file, will that make it twice as big in both directions, thereby filling the screen? I've looked for the exact specifications of the G16 screen, but all I can find is the total number of pixels. But it looks like the grids are filling the upper left quadrant, 1/4 of the screen.
Quote from: waterwingz on 21 / March / 2018, 19:14:54So far, nobody has gotten around to creating new grid files for D6 cameras - and that's why you see the image all pushed up into the upper left hand corner.FWIW, someone did make a set of grids for G7 X (https://chdk.setepontos.com/index.php?topic=12692.msg134850#msg134850), but they won't be exactly right on G16 since the aspect ratio and resolution are different (G7 X is 720x480 3:2, while G16 is 640x480 4:3)Quote from: LDBenjamin on 22 / March / 2018, 12:47:58If I double the numbers in the grid file, will that make it twice as big in both directions, thereby filling the screen? I've looked for the exact specifications of the G16 screen, but all I can find is the total number of pixels. But it looks like the grids are filling the upper left quadrant, 1/4 of the screen.G16 is 640x480. The screen the stock grids were designed for is 360x240, so doubling wouldn't be quite correct. Note that the old cameras were 4:3, meaning pixel aspect ratio wasn't square.
The G16 has several aspect ratios, 4:3, 3:2, 16:9, and square. So the grid would have to be matched to the correct one. Now that I know it's 640 x 480 I will play around with that.
Quote from: LDBenjamin on 24 / March / 2018, 18:02:17The G16 has several aspect ratios, 4:3, 3:2, 16:9, and square. So the grid would have to be matched to the correct one. Now that I know it's 640 x 480 I will play around with that.The shooting aspect ratio doesn't affect the UI resolution. So what matters is the pixel dimensions of the UI (640 x 480) and the physical aspect ratio of the screen (4:3, AFAIK)
Started by waterwingz « 1 2 ... 54 55 » DryOS Development
Started by pittguy578 General Help and Assistance on using CHDK stable releases
Started by Christian72D General Help and Assistance on using CHDK stable releases
Started by vga71 Script Writing
Started by Fortesque General Discussion and Assistance
