1
I Use This!
Low Activity

News

Analyzed about 24 hours ago. based on code collected 1 day ago.
Posted about 10 years ago by sz_johnr
Hey I wanted to come back and update this what whatever info I could. I'm still stuck at a wall but here's what I've done so far. Took out the DLL and dropped the source into it. It caused a lot of errors so I gradually started taking things out ... [More] until Unity could compile it. Running it caused an exception with pdf something. So I only used BarcodeFormat.ALL_1D as a barcode hint. This made it run without exceptions, but it wasn't scanning anything. Using the source, I started sprinkling some logs to make sure I was getting into ZXing and I was. I noted that it was using the multiformat reader. I'm wondering if I may have taken out something important when gutting the source, but I haven't had the time to jump back to this project. I'm also curious if the pixel format is different on iOS and isn't what ZXing is expecting. When I drew the bitmaps onto the UI, it was grayish or white with transparency. However when I debugged to see the bufffers, they had various color data that seemed appropriate for what was in the image (I was wearing a blue shirt, they all had high blue for rgb value). [Less]
Posted about 10 years ago by micjahn
Ofcourse, patches are always welcome. You can send me patches via email or you upload it in the source code area in the patches section.
Posted about 10 years ago by Beamzza
hi micjahn My expectation is when i send "|A10193\r\n10009122" to encode it should encode with codeset B then it could switch to codeset A at "\r\n" because Code 128 allows multiple variants, as well as switching between variants within a single ... [More] barcode. but i've create my own 128 which could encode codeset A,B,C and allow switching between varients within a single barcode. I use the barcode specification from http://en.wikipedia.org/wiki/Code_128 and it works. now I just replace the code128 encoder of zxing with my own. I would like to share the code to zxing. Could it be possible to add this code into the project. the things I've done is code128 encoder that allow switching between variants within a single barcode. Barcode length optimization (shorter barcode using code 128c) [Less]
Posted about 10 years ago by micjahn
As a proof of concept, I have been generating a series of QR barcodes via ZXing in C#, photographing the output as displayed on a monitor, then reading the result from the png image. This has been very successful and fast, but every now and then I ... [More] get an image that is clear, but unreadable via ZXing BarcodeReader.If I use another reader; for instance the i-Nigma QR reader from my iPhone, the code is immediately recognised, so the code seems well-formed.The C# code I have used to attempt to read the images is shown below. Also, I get the same null result when I attempt to decode the image on-line on the zxing web site.The image is very high quality and the string encoded is very simple(in this case "~000057~~ {")I have attached one of the unreadable (by ZXing) images``` var files = Directory.EnumerateFiles(@"V:\VideoTest\Dump\bad"); foreach (var badFile in files) { var qrReader = new BarcodeReader { AutoRotate = true }; qrReader.Options.TryHarder = true; var image = new Bitmap(badFile); var result = qrReader.Decode(image); if (result == null) { Console.WriteLine("Null"); } else { Console.WriteLine(result); } }```Comments: ** Comment from web user: micjahn ** The problem is the barrel distortion.The detector doesn't work very well for this kind of image distortion.I have no idea how to fix that. In my opinion it is a very rare case.Patches are always welcome.Here is the binary version of the image which the detector see:``` X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X ``` [Less]
Posted about 10 years ago by ahabbot
HiAs a proof of concept, I have been generating a series of barcodes via ZXing in C#, photographing the output as displayed on a monitor, then reading the result from the png image. This has been very successful and fast, but every now and then I get ... [More] an image that is clear, but unreadable via ZXing BarcodeReader.If I use another reader; for instance the i-Nigma QZ reader from my iPhone, the code is immediately recognised, so the code seems well-formed.The code I have used to read the images is shown below. Also, I get the same null result when I attempt to decode the image on-line on the zxing web site.The image is very high quality the string encoded is very simple(in this case "~000057~~ {")I have attached one of the unreadable (by ZXing) images``` var files = Directory.EnumerateFiles(@"V:\VideoTest\Dump\bad"); foreach (var badFile in files) { var qrReader = new BarcodeReader { AutoRotate = true }; qrReader.Options.TryHarder = true; var image = new Bitmap(badFile); var result = qrReader.Decode(image); if (result == null) { Console.WriteLine("Null"); } else { Console.WriteLine(result); } }``` [Less]
Posted about 10 years ago by micjahn
First, you are right, codeset A isn't supported in the encoder at the moment. Second, one question: What do you mean with "special character(" | ")"? It's a normal character for me (in codeset B). What is your expected behaviour of the encoder if it found that character?
Posted about 10 years ago by Beamzza
Hi I've requirement to encode the following text to be barcode (using code128) "|A10193 10009122" these text contain both special character(" | ") and control code ("<CR>+<LF>") I try to use zxing.net to encode but it will show ... [More] error when i try to send "|A10193\r\n10009122" to encode. From the source code, I found that the encode part is not support for code128A which contains control code. But on the decode part it support all subset A,B,C. [Less]
Posted about 10 years ago by sz_johnr
It looks like i'm at the exact same point as others. I'm using unity to compile into iOS. Seems to crash when we first enter the zxing library, or possibly when the thread is made. I had read somewhere that it may be beneficial to remove the ... [More] generics from the library to work around this issue. Another note that I think the issue below may not be related to ZXing.NET but could just be related to threading. Although I'll admit, I thought we had done threads in the past with Unity and promised ourselves we wouldn't do it again. Barcode`_mono_metadata_generic_class_equal: 0x1c8c1cc: push {r4, r5, r6, r7, lr} 0x1c8c1d0: add r7, sp, #0xc 0x1c8c1d4: push {r8, r10} 0x1c8c1d8: ldrb r3, [r1, #12] 0x1c8c1dc: ldrb r12, [r0, #12] 0x1c8c1e0: eor r3, r12, r3 0x1c8c1e4: mov r12, #0x0 0x1c8c1e8: tst r3, #0x1 0x1c8c1ec: bne 0x1c8c24c ; _mono_metadata_generic_class_equal + 128 0x1c8c1f0: mov r8, r1 0x1c8c1f4: mov r10, r0 0x1c8c1f8: ldr r4, [r1, #4] 0x1c8c1fc: mov r6, r2 0x1c8c200: ldr r5, [r0, #4] 0x1c8c204: ldr r1, [r8] 0x1c8c208: ldr r0, [r10] 0x1c8c20c: bl 0x1c8c088 ; mono_metadata_class_equal 0x1c8c210: mov r12, #0x0 0x1c8c214: cmp r0, #0x0 0x1c8c218: beq 0x1c8c24c ; _mono_metadata_generic_class_equal + 128 0x1c8c21c: mov r0, r5 0x1c8c220: mov r1, r4 0x1c8c224: mov r2, r6 0x1c8c228: bl 0x1c8c31c ; mono_generic_inst_equal_full 0x1c8c22c: mov r12, #0x0 0x1c8c230: cmp r0, #0x0 0x1c8c234: beq 0x1c8c24c ; _mono_metadata_generic_class_equal + 128 0x1c8c238: ldrb r12, [r8, #12] 0x1c8c23c: ldrb r0, [r10, #12] 0x1c8c240: eor r12, r0, r12 0x1c8c244: ubfx r12, r12, #0x1, #0x1 0x1c8c248: eor r12, r12, #0x1 0x1c8c24c: mov r0, r12 0x1c8c250: pop {r8, r10} 0x1c8c254: pop {r4, r5, r6, r7, pc} [Less]
Posted about 10 years ago by ToddVan
Thanks, and I understand. You’re really doing stellar work here! I tried things based on Win8 but that MediaCapture device interface is terrible. Performance just sucks. Unfortunately that’s where the entire Win API is headed. We’re going ... [More] to need to implement some kind of recognizer pattern in C++ to get the perf otherwise you’re looking at 1 sample/sec and their s bug in the MediaCapture component the fails if the user switches to another app. [Less]
Posted about 10 years ago by micjahn
There is no sample for appx or Windows 8.1 at all. Free time is the issue, not a road block. It would be great if you can write a working sample with Media Stream and provide it is as a patch.