FormatConverter

I/O calls are allowed on any thread. The problem is in your C-string conversion to UnsafeMutablePointer (it's called unsafe for a good reason). You're doing this on a stack let "variable" which will vanish once your PCM Audio non main thread finishes. Hence you end up with a dangling pointer pointing at some random memory. I suspect you don't seem to experience the same problem on main thread because it's always there throughout app lifetime and hitting a dangling pointer on its stack is less probable (but still definitely possible). The solution is to get your UnsafeMutablePointer (courtesy of yossan) like this:

Got an answer over the github issues. Putting it here for future reference.

Turns out the specified commit has a missing file in the MAKEFILE. Apply this patch: https://github.com/google-coral/edgetpu/issues/201 and build is working.

I searched online for documentation to the Pylon API, but couldn't find it. Nonetheless, using the example for OpenCV you gave, it is easy to do the equivalent in DIPlib:

The issue was that you can't use per primitive antialiasing with a spritebatch. This line before BeginDraw() fixed it: d2dDeviceContext3.AntialiasMode = AntialiasMode.Aliased;

Also learned finally how to get the debug layer working. Include debug flag when creating your device (see comments below). If it throws an exception, that is probably because you dont have the right version of windows sdk. If you're using visual studio, go to visual studio installer and modify your installation to include windows sdk.

Next you need to right click your project->properties->debug (on the left panel)-> check "enable native code debugging". After i did this there was a line written to the output window stating: "D2D DEBUG ERROR - DrawSpriteBatch requires that the antialias mode be set to D2D1_ANTIALIAS_MODE_ALIASED."

Something else i learned that isn't directly related to the answer but worth noting: "Note that ComObject in SharpDX is not disposed by the .NET finalizer. If a COM object is not released by a call to Dispose() or ReleaseReference(), it will not release the native object and memory attached to it." from here: http://sharpdx.org/wiki/usage/

Here's a full working example:

I was able to get around this issue by doing the following, some steps may not be necessary, but so far, this has worked in my case. I found this github issue helpful and put me on the right track.

First, excessive importing in my script:

The key indicator of the problem is this line in the compilation error:

From your description, it sounds like the issue is exceeding Direct3D's texture size limits (Direct2D uses Direct3D for its work so it has the same constraints).

If you look at Max Texture Dimension in the Direct3D Feature Level table you'll see that ranges from 4,096 to 16,384 pixels depending on the level of graphics hardware. You can:

• assume 4,096 is your limit (this is what you should do if you are running this program on a variety of computers that have different graphics cards)
• run dxdiag.exe, clicking the "Display 1" tab, and looking for Feature Levels or DDI to see what feature levels are available.

The solution is to resize your image down until it fits within the pixel limits before calling target.DrawBitmap. In other words, you can't make zooming work as easily as you might like - even if you zoom in and out on a texture, at some point you'll have to resample or it will be more pixelated than the original image.

Looks like you are using bitmaps. Have you considered using DDS files instead? It supports both compressed and uncompressed formats – Asesh

Asesh was right. At first, I was sceptical, but I did some research and found an older article which states, that an average PNG texture takes less memory on hard drive than a comparable DDS texture. However, PNG textures need to be converted at run-time which is slower than using DDS textures.

I spent last night looking for proper conversion tools and after testing some stuff (like a plug-in for GIMP), I used the Compressonator from AMD to convert all my PNG textures to DDS textures. The new files take even less memory on my hard drive than the PNG files (1.7 GB instead of 2.1 GB).

My texture loading method I presented in the initial post still worked and was slightly faster. However, I decided to code a DDS importer based on several code samples I found online.

The result: A large textures takes only 1 ms instead of 103 ms to import. I think you can that an improvement. :-D

Thank you very much, Asesh!