SD Times news digest: Dynamic Web TWAIN version 15, a Python extension for Visual Studio …

Dynamsoft introduced version 15 of its Dynamic Web TWAIN document scanning SDK, adding a faster way to initiate job scans and functionalities for Windows and macOS, according to the company.

Dynamsoft explained the process for scanning and uploading data is faster now that the SDK accepts a JSON object that specifies all of the scan parameters. Developers can add output parameters in the JSON object to specify how they want the data to be processes.

The new version of the SDK also improves performance by allowing two operations to run simultaneously, whether it’s ConvertToBlob, ConvertToBase64, GenerateURLForUploadedData and a few HTTP upload methods, according to the Dynamsoft. The update also includes better image encoding and decoding for macOS and 64bit as the new default option on 64-bit machines.

Python extension for Visual Studio Code is now available

Microsoft introduced the June 2019 Python Extension for Visual Studio Code, which includes a new Plot Viewer, parallel tests with pytest and indentation of run selection in the terminal.

The new Plot Viewer allows users to manipulate any image plots and export plots to PDF, SVG or PNG formats. Also new to Visual Studio Code is the ability to execute run and debug tests in parallel.

Microsoft has fixed bugs requested by users and added small enhancements such as allowing a password for remote authentication with jupyter and support for sub processes debugging. The full list can be viewed here.

Hyperledger Transact joins the Hyperledger initiative

Hyperledger released Transact, a shared software library that handles the execution of smart contracts, adding it to the Hyperledger Initiative.

Smart contracts are a building block of distributed ledgers, in which transaction represent the intended change submitted by a user that is then interpreted by the smart contracts, Hyperledger explained.

Transact introduces transaction execution adapters that allow different mechanisms of execution, serial and parallel transaction scheduling, pluggable state backends and SDK’s for multiple languages. The full list of features can be viewed here.

eBay introduces new APIs for developers

eBay introduced new payments API capabilities designed to give developers access to eBay’s new managed payments program, which include finance, account, fulfillment and recommendation APIs.

Additional APIs include login with eBay, volume pricing in marketing, offers to buyers in the negotiation API and support in the Inventory API and Merchant Integration Platform feed solution. The detailed list of APIs can be found here.

“Our goal is to empower developers, enhance the ecosystem of eBay applications, and add value for our buyers and sellers,” eBay wrote.

Related:

  • No Related Posts

nVidia control panel fails to launch in platform layer or published image

In the layer that you are delivering the nVidia drivers (normally the Platform Layer, but it can be any layer at all) open the registry and navigate here:

[HKEY_LOCAL_MACHINESystemCurrentControlSetServicesunifltr]

Add a value called AlwaysOnBoot (if it doesn’t already exist) as a multi string value. Add the following two lines:

C:Program FilesNVIDIA Corporation

C:Program Files (x86)NVIDIA Corporation

Please note the trailing at the end of the paths, as that tells the software that it is a directory, and we should keep all of the children of the directory on the image. Finalize, and deploy the image with the new layer revision.

Related:

  • No Related Posts

Receiver 4.10: Grey Screen On Published Desktops After Upgrading To Receiver 4.10

Unknown error 0x887A0001 in DirectX API seen in CDF Traces collected from the Receiver side.

ProxyLogErrFunc,9,CDF_ERROR,”ctx::gfx::D3D11PresentDevice::CreateSwapChain :: IDXGIFactory1::CreateSwapChain Failed. hResult = 0X887A0001, msg = Unknown error 0x887A0001″,”

DXGI_ERROR_INVALID_CALL
0x887A0001

The application provided invalid parameter data; this must be debugged and fixed before the application is released.

Related:

  • No Related Posts

Rest API to create multiple resources

I opened a ticket for this, but perhaps someone already tried this before and can cut down the waiting line…

I’m in phase where I’m exploring and documenting Rest API usage… I kind of like it even though for normal human usage nsradmin is still your best friend. Still, I can see where Rest API would be better fit, especially when integrating with other platforms without any specific parts of NW package to be available.

One thing where I found myself stuck is handling multiple resources (if you wish to create it via POST). Consider following body:

{

“protectionGroups”: [

{

“comment”: “Backup group via RestAPI one”,

“name”: “RestAPIb”,

“workItemType”: “Client”,

“workItems”: []

},

{

“comment”: “Backup group via RestAPI two”,

“name”: “RestAPIc”,

“workItemType”: “Client”,

“workItems”: []

}

]

}

That doesn’t work for me, but error I get seems to suggest some kind of syntax error (or this simply not being supported in the first place). I can easily create one resource or have two calls for each resource too, but would prefer if I could use single call for multiple resources when building requests for the same type of resources.

Related:

  • No Related Posts

DLP 12.5 – Unable to start Aggregator

I need a solution

I am currently having an issue that my Endpoint server is not able to start up properly.

In fact, it is stuck at “starting”.

The only message in the console is:

Message
Code  1012
Summary  “Unable to start Aggregator
Detail  Cannot bind to the shutdown datagram socket. Will retry.

In the Aggregator.log, I can only see this as well in terms of errors:

“Oct 9, 2018 8:19:49 PM com.vontu.logging.LocalLogWriter write
SEVERE: “Unable to start Aggregator. Cannot bind to the shutdown datagram socket. Will retry.”

Besides, there are only INFO level entries in this logfile.
I can restart as many times I want, no change.

Unfortunately, I am out of ideas.
Any input or help appreciated.

0

Related:

  • No Related Posts

Hardware Acceleration for Linux endpoints with AMD GPUs

Sarting from version 2.5, HDX RTME supports hardware acceleration for video compression on Linux thin clients or fat clients with AMD GPU. Specifically, for video encoding RTME uses VCE 2.0 or higher. Video decoding has limited support because of some technical limitations, and it is disabled in RTME by default.

OMX IL is used for offload video processing to GPU.

Hardware video encoding on Linux could be disabled by registry key DisableOnboardHardwareH264Encoding (DWORD value 1-disabled or 0-enabled by default) in HKEY_CURRENT_USERSoftwareCitrixHDXRTConnectorMediaEngine

Ubuntu 16.04 environment set-up

Install AMD driver stack from https://support.amd.com/en-us/download/embedded?os=Linux_tmp%20x86_64

Install kernel (example command line, latest available version should be used):

sudo dpkg -i linux-image-4.4.11-289-amd+_4.4.11-289-amd+-10.00.Custom_amd64.deb linux-headers-4.4.11-289-amd+_4.4.11-289-amd+-10.00.Custom_amd64.deb

sudo reboot

Install userspace:

Create local repository as it is described in amdgpu_UserGuide.pdf or proceed manually with dpkg.

NOTE:

To verify available package versions:

apt-cache policy <package name>

To overwrite ‘man’ or header files:

-o Dpkg::Options::=”–force-overwrite” (apt-get)

–force-overwrite (dpkg)

In case of unmet dependencies, you can resolve them by installing strictly with dpkg -i, pulling needed packages alongside.

During these steps, please, prefer packages from AMD driver stack. For isntance you may install “llvm-5.0-dev=5.0-519”, while “llvm-5.0-dev” will set up the latest Ubuntu package.

libllvm5.0 llvm-5.0-dev llvm-5.0-runtime llvm-5.0

llvm-runtime llvm-dev llvm

libdrm-dev libdrm-amdgpu1 libdrm-radeon1 libdrm2

libdrm-dev libdrm-amdgpu1 libdrm-radeon1 libdrm2

libva-dev libva1 libva-drm1 libva-egl1 libva-glx1 libva-tpi1 libva-wayland1 libva-x11-1 vainfo apt-cache policy libva-dev libva1 libva-drm1 libva-egl1 libva-glx1 libva-tpi1 libva-wayland1 libva-x11-1 vainfo

libegl1-mesa-dev libegl1-mesa-drivers libegl1-mesa libgbm-dev libgbm1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles1-mesa-dev libgles1-mesa libgles2-mesa-dev libgles2-mesa libosmesa6-dev libosmesa6 libwayland-egl1-mesa libxatracker-dev libxatracker2 mesa-common-dev mesa-omx-drivers mesa-vdpau-drivers

gst-omx xserver-xorg-video-amdgpu

Install bellagio:

libomxil-bellagio0 (Generic core OMXIL implementation)

libomxil-bellagio-bin (to register available OMX components)

Register these components run omxregister-bellagio (from libomxil-bellagio-bin) with the noted above path.

  • Run omxregister-bellagio -l and you should get the following output:
  • *********************************
  • * List of registered components *
  • *********************************
  • Component OMX.mesa.video_decoder
  • supported formats:
  • OMX.mesa.video_decoder.mpeg2
  • OMX.mesa.video_decoder.avc
  • Component OMX.mesa.video_encoder
  • supported formats:
  • OMX.mesa.video_encoder.avc
  • Installed components and a path to the library are stored in an OMX registry file:
  • $ cat ~/.omxregister
  • /usr/lib/libomxil-bellagio0/libomx_mesa.so
  • ==> OMX.mesa.video_decoder ==> OMX.mesa.video_decoder.mpeg2:OMX.mesa.video_decoder.avc:
  • ==> OMX.mesa.video_encoder ==> OMX.mesa.video_encoder.avc:

Driver requirements:

These are described in AMD’s site https://support.amd.com/en-us/download/embedded?os=Linux_tmp%20x86_64

RTME uses OMX API for video encoding and decoding.

This API is implemented by Bellagio OpenMAX IL (libomxil-bellagio0 and libomxil-bellagio-bin).


Hardware requirements: AMD GPU with VCE 2.0 or above. Specifically, Citrix is using Mullins and Carrizo.

Known limitations:

video encoding is supported on Mullins series only. Carrizo series were tested too, but problems were found with unstable video bitrate. As a result, a stream was encoded with poor quality.

video decoding is disabled by default, and could be enabled from registry on VDA. It was done because HW decoder introduces high latency up to 500ms.

It was found that described limitations became visible only on Linux platforms. The same GPU works great on Windows endpoints.

Related:

Can not create new widget – last scan date

I need a solution

Every time I try to create any new widget I get: 

failure message: {“data”:{“errorCode”:761,”message”:”Unable to create new widget.”,”data”:{}}}

All I want is a widget that shows last scan date.  Other info might be useful too, but I can’t create ANY widgets.

Thanks,

– cjm

0

Related:

Re: Recovery Point for VM Failover through REST

Hi All,

Need a suggestion on Failing over VM through the REST API in RP4VM.Any leeds on it will be very helpful.

I came across the following :

1.The CLI might not be having all the functionalities

2.The API functionalities I came across in the Programming guide either does not cover all operations or might not be stated in the document.

3.We have the Swagger link , where we can test the Requests made : https://<ip>/deployer/swagger/#

4.There are two versions of the API i think : FAPI and deployer (however the FAPI contains methods like failover as i was searching online) and deployer contains more or less the same methods as in swagger. The Fapi documentation is old and for 4.0 , while deployer i could get for 5.1.

Question : How can we failover using the REST API ,present verion we are using is 5.1 , if you can mention the method and the wsdl/wadl , it would be great help.

Related: