Respected Sir/Madam,
I have a doubt regarding LZW BW 1200dpi tiff file creation using “UDC driver 6.7/6.8 version”.
If we disable “'Perform High-Quality Smoothing”, then output data are not visible in output files.
If we enable this option, it is working fine.
Also, working fine for UDC driver 6.4 for both Enable/Disable 'Perform High-Quality Smoothing'.
We are using below tiff library version in our software.
/* Version number of package */
#define VERSION "4.0.3"
Could you please clarify our below doubts.
LZW support for 'Perform High-Quality Smoothing' always should be enabled?
Is this issue introduced in UDC driver version 6.7?
https://www.print-driver.com/overview/version-history
Best Regards,
Shantala R
Please contact the developers of the software regarding their product.
https://www.print-driver.com/support
Related
In order to use my custom TF model through WinML, I converted it to onnx using the tf2onnx converter. The conversion finally worked using opset 11. Unfortunately I cannot load the model in the WinRT c++ library, therefore I am confused about the opset support: According to the Release Notes, the latest WinML release in May supports opset 11. I updated my VS2019 and downloaded the latest Windows 10 SDK, does the c++ API already include the latest onnx support? Or is there any alternative way to use my model in WinML c++?
The latest release of Windows OS contains support for opset 9.
The latest release of Microsoft.AI.MachineLearning NuGet package contains support for opset 11.
Please refer to these release notes: https://learn.microsoft.com/en-us/windows/ai/windows-ml/release-notes
You can find the latest Microsoft.AI.MachineLearning NuGet package here: https://www.nuget.org/packages/Microsoft.AI.MachineLearning/
As #Kookei mentioned, there are 2 ways of building WinML: the "In-Box" way and the NuGet way.
In-Box basically just means link to whatever WinML DLLs that are included with Windows itself (e.g., in C:\Window\System32).
The NuGet package contains its own more recent set of DLLs, which other than providing support for the latest ONNX opset, has the obvious advantage of allowing you to easily distribute your binary to older versions of Windows lacking any built-in machine learning capability. Just install the package through Visual Studio's Nuget Package Manager, and build your solution; and you'll find that the output directory now contains the needed DLLs (currently directml.dll, Microsoft.AI.MachineLearning.dll, and onnxruntime.dll) along with the generated EXE, ready for same-folder deployment.
In terms of source code, this is how the two versions are distinguished:
In-Box:
#include <winrt/Windows.AI.MachineLearning.h>
using WinMLModel = winrt::windows::AI::MachineLearning
NuGet:
#include <winrt/Microsoft.AI.MachineLearning.h>
using WinMLModel = winrt::Microsoft::AI::MachineLearning
In other words, the only difference is whether you use the Window or Microsoft header/namespace.
you can also track the supported opset versions at the version matrix table.
I have a problem of applying some functions of OpenGL(e.g. glDeleteBuffers).
My computer's spec is;
Renderer: AMD Radeon HD 6800 Series
Operating system: Windows 7
Intel(R) Core(TM) i7-2600
I used OpenGL Extensions Viewer 4.4.3 to view information about OpenGL.
I update the latest version of graphic card and found that version of OpenGL is 4.4 and it shows like below picture:
I am not sure what I can do more from now. I would like to use functions like glDeletBuffers, glGenBuffers, glBindBuffer, glBufferData...
Give me some help
The functions you've listed aren't loaded by default even on systems that have hardware supporting modern OpenGL. To get access to these functions you need to query the extension and load it if available.
A guide for querying and loading functions yourself can be found here
If you simply want to load the extensions associated with a OpenGL version (such as 4.1/3.1 etc.) you can use something like GLEW to simply handle the querying and loading for you.
If you want to use older functionality too (while not advised) then make sure to look at loading a compatibility profile to support deprecated version functionality, i.e if you are using the fixed-function pipeline flow. Not that I'd advise it!
I am trying to test decoding a h264/h265 video (with just a single iframe) using DX11 and DXVA2. This is on windows 7 so I probably have to interop between 2 d3d11 devices, one with 11.1 feature set and the other with 9.3. My question is since there is a severe lack of samples for loading a h264 file and decoding it using DXVA, I was wondering if there is a guide for how to layout the data to feed into DXVA to decode? I've read this How do I use Hardware accelerated video/H.264 decoding with directx 11 and windows 7? as well as https://msdn.microsoft.com/en-us/library/windows/desktop/hh162912(v=vs.85).aspx but neither has any guide on how to do the above.
Thanks
If you want a working sample to understand how to feed data into DXVA, look here : MFNode. Under MFTDxva2Decoder, you will see how to feed data. It is for mpeg1/2 file format, but the same apply to H264 (with shades, of course).
EDIT
See my response : How do I use Hardware accelerated video/H.264 decoding with directx 11 and windows 7?
I was installed CUDA 4 on my laptop (Dell - Vostro 3500) and started to write CUDA programs. But I got an error: driver is not compatible with this versios of CUDA.
So I decided to update my GPU driver (GPU: Nvidia GeForce 310M) and downloaded the driver from Nvidia's site. But when I want to insall the driver, see this error:
NVIDIA Intaller cannot continue
This graphics driver could not find compatible graphics hardware.
I tried 301.42 , 301.32 , 275.33 and 270.81 versions of Nvidia GPU drivers.
My friend installed 275.33 on his laptop with GeForce 310M on an Asus device.
Finally I found my answer with the help of Ben Stewart.
I hacked the INF file in this way:
Go here.
At the second part (NVIDIA Video Drivers and Tools) select suitable part. For example select 29X for 296.10.
Select appropriate part for your downloaded driver and Windows version.
In this page download INF file.
Replace the INF file with INF in the Display.Driver folder at driver unzip location (for example, C:\NVIDIA\DisplayDriver\296.10\WinVista_Win7_64\International\Display.Driver)
Set up the driver!
I had the same problem recently running Windows 7 on an iMac and managed to hack the nv_disp.inf file on version 301.42 to get it to install fine. Basically, you need to add an identifier from your graphics card to the inf file and away she goes. Not to hard.
Here's how I did it.
First, we need the identifier from your graphics card. Open Device Manager and bring up the property box for your graphics card in Display adapters. In the "Details" tab you will find a drop down box, open it and select "Device Instance Path"; you should be able to right click on the value in the field below and copy it.
Then find the temporary folder that the driver setup was extracted to when you ran it previously. For me it was "C:\NVIDIA\DisplayDriver\301.42\WinVista_Win7_64" - if you can't find it, just run the setup again and note where the installer extracts itself. The file we need to edit is located in the Display.Driver directory, and it's called nv_disp.inf. Open this in Notepad or your favorite text editor.
Now we need to modify the string you have copied and add it to this file.
If you scroll about 15% of the way down you will find a heading similar to [NVIDIA_SetB_Devices.NTamd64.6.0]. This is the start of Nvidia's list of supported devices.
If you paste your device instance path here you will probably notice that the first 21 or so characters of your device path are similar to the last 21 on the proceeding few hundred lines. Something like PCI\VEN_10DE&DEV_0240. You can delete the rest of the text you have copied in.
The devices are organised into groups, so it's probably best to search for a line that is similar to yours in the last four numbers and use this as a template for creating the entry.
You want to use this information to create an entry that looks like the others that are already here.
I modified the line:
%NVIDIA_DEV.0868% = Section005, PCI\VEN_10DE&DEV_0868
with the identifier PCI\VEN_10DE&DEV_0869 to be:
%NVIDIA_DEV.0869% = Section005, PCI\VEN_10DE&DEV_0869
Note that the four-digit number near the beginning of the line matches the number at the end.
Save the document over the original nv_disp.inf, then run setup.exe from the already extracted folder. If you run the file you downloaded again, it will just extract again and overwrite your changes.
Are you downloading the notebook drivers from http://nvidia.com/drivers?
If you were using the notebook drivers, then it is likely that NVIDIA didn't include your GeForce 310M in the INF file for the latest drivers. You can hack at the INF files yourself to fix this. It is not simple, but can be done by googling for it and carefully reading certain forums where others have hacked at the INF files themselves. No fun.
I have html files/Directories, I want to convert them to .chm help file, under Linux using command lines at Terminal?
Any help would be appreciated.
The Free Pascal compiler, version 2.4.4 or higher has a CHM compiler for *nix called "chmcmd". I would recommend getting it from version 2.6.0. It works on MSHelp .hhp project files.
The compiler is also available in source (styled like a classes library), so you could roll your own. It is crossplatform, but Big Endian platforms are not tested very well.
2.6.0 is from januari 1st 2012, so you might need to get it from a "bleeding edge" packages repository of your distribution.
CHM is a proprietary Microsoft format, so keep in mind most Open Source tools will likely be focused on reading and converting chm to html . if you want to create CHM file on Linux then you will need a CHM compiler that you can use with wine . details are on the following link Compiling_CHM_help_files_in_Linux_with_HHC_and_Wine
You can do that with libchm, you find it http://www.jedrea.com/chmlib/ .
It contains extract_chmLib, which extracts html pages from the help pages to a directory.