Notices

Hi Lardman,I had installed ur appliation,but after scanning a barcode,it is not giving me any results????????

Did it produce a number/text from the barcode?

Could you send a photo of the barcode?

Note to self, must finish that bit of the app so people can submit problematic barcodes for us to look at!

Just a FYI (and reminder to get people to kick me if I don't do more), I've made some changes to the SVN code and we should probably go for a new point release.

The only visible change is probably adding the ability to save scan history and restore it (i.e. the thumbnails you can click on the RHS). I've also added a numeric editor in the Settings menu so you can change the continuous autofocus delay time.

Under the skin I've cleaned up the implementation of the history thumbnail list, added a checkbox to the Settings menu to enable/disable this feature, stopped timers from running unnecessarily (i.e. if there's no scanning and/or no autofocus going on).

Things to do now:

Work out why the Settings menu doesn't seem to recognise changes to e.g. the autofocus length (but they are saved and acted upon - just not shown in the dialog if you open it again - odd!).

Change the way the thumbnails are taken from the pipeline - atm (iirc) the thumbnail displayed is the last frame sent down the pipeline at the point one of the decoders detects a barcode. As the decoders are in a separate queue (i.e. thread) which can drop frames, this means the displayed thumbnail is probably different to the frame that was decoded. This is a hangover of the previous decoding method (not using Gst elements, but using memory buffers directly), which works well enough for many cases, but not all and therefore I will fix it.

Along the same lines, we should give the user the option of saving any barcode that cannot be decoded so they can send it in and we can look at the problem. Not sure how to do this - perhaps present a dialog after scanning for X seconds, or use a button to "Save Frame" during scanning. Will have to think about it.

Fix the green/purple fringes. This is especially problematic with the continuous autofocus, as every time the pipeline is paused, this is what comes out and it has to be paused to carry out the autofocus. Not sure what's causing this, will have to do some digging into the autofocus to see if it e.g. changes the camera output format and then we get junk left over when the pipeline is restarted, or to see if I can purge the pipeline before the restart. Any help/ideas appreciated

Pop up menu to delete individual history list items (atm you can clear all using the menu, but you might just want to get rid of one or two), I was thinking of a long press to open a context menu with a delete (and perhaps a save) item.

Add in Python plugin support. Any help appreciated here too as I've not used PythonQT before - has anyone compiled it already for example?

Finally, get back to writing my itemdb plugin.

Thanks for listening

Hi guys. I've installed this from the extras-devel but it isn't working for me.

I mean, it's intsalled, no errors, but I can't find it as an application, nor as an extension (in the file manager for photos; in the photo/video shooter; in the settings area)

I thouhgt this is a bug so I restarted the device, but it's the same.

I'm running the 10.2010.19 firmware thingy.

Any help? Thanks

Odd, it should appear as an application in the launcher menu (and does for me).

It doesn't appear as an extension in the camera app and is not linked into the filemanager I'm afraid.

Are you sure it installed? Can you run it from the terminal?

I'm sure it's installed (and it doesn't appear when I search for it on the "Download" section the App. Manager).

How do I run it from terminal? ("mbarcode" ?)

nevermind, for some reason now it appears in the application list and it runs.

from time to time it starts flashing the flash at 1-2 second intervals and the top-half of the imagescanner flasher to green+yellow .. I think this problem is causing by the YUV renderer on computers too.

Good

The autofocus is set to run every 1.5s iirc, if it can't get a good focus you see if running (and it uses the flash if the light levels are too low). Try setting the autofocus delay to something longer (3.5s perhaps) to give the decoder a chance to detect something between the autofocus events.

Re the odd colours and "multi-views" you see at that point - it does look like a YUV layout, almost as if 3 frames of YUV have been pushed into the pipeline and then interpreted as RGB (though I've not looked at the formats, so this interpretation may be completely wrong).

The question is how to get rid of it? If it's a problem with the format conversion (the fact that it happens between autofocus and the pipeline restarting; or that the conversion element gets confused) it would be possible to move to using an RGB pipeline.

Alternatively I wonder if we can purge the pipeline and the element states to avoid major changes?

I'll have a look at it next week when I have an hour or two to work through some ideas.

so this app has been in devel for how long... since 2009?

will it ever come to extras? :P

It's not exactly production quality yet what with the missing Python plugin functionality and video artefacts. I've been rather busy for the last 6 months so haven't had an awful lot of time to try to get things finalised, but am working on it.

It's certainly usable though, so give it a go. Patches welcome of course so we can get it into Extras proper asap!