For a .net project, I use DirectShow (through DirectShow.net) with the VMR9 in windowless mode for video display.
On Windows 7, I noticed a pixelization problem when the video is resized (magnified).
I can’t find how to tell the VMR9 to use a specific interpolation algorithm (i.e. bicubic).
It looks like, by default, it uses none.
I would like to avoid using my own allocator-presenter for this task.
Thank you for your help.
You should use the EVR rendered on window7 to avoid pixelated video.
See this question:
WMV media streams appear more pixelated on Windows 7 than on XP
Evr comes with it's own set of problems, I've found that resizing an EVR rendered stream is slow / jerky. And EVR is only available on vista and later operating systems. Stick with vmr9 for xp.
Related
I have created a pdf viewer using react-pdf. When I display certain pdfs, the text is choppy and unreadable. I have tried zooming in and out of the document and it is choppy in different ways at different scales. Sometimes the text even looks okay at a certain scale after zooming out and then zooming back in.
(Sample at 1.5 scale)
(Sample at 1.6 scale)
At first, I thought it might be an issue with react-pdf, but I saw that react-pdf is basically a wrapper around PDF.js. I found that I can replicate the issue in the PDF.js demo page.
Unfortunately, I'm working with a pdf that contains identifying information, so I can't share the full pdf or full screenshot. I'll include as much as I can figure out to share.
What I have tried
My initial thought was that maybe the component was rendering small initially and then had issues scaling up. So I made the initial size really large, but that didn't fix it.
I made sure that standard fonts were included following the instructions on the react-pdf home page
I tried using pdf repair tools online to maybe fix the pdf itself. That didn't help.
I tried changing the renderMode to 'svg' as detailed in the Document api documentation. This was the most helpful fix, as it does render the text correctly, but it then makes it so the images on the pdf don't load.
Thanks for your help/suggestions.
If I can find a way to edit the pdf to not have sensitive information, I'll try to find a place to make it available for testing. I apologize that I cannot provide that at this time. I know it's difficult to give advice when you can't replicate it yourself. I'll work on that.
From a programming point of view there is only "Providing a standardFontDataUrl and disabling the font face" (see later), however it affects many pdf.js based code developers outputs, thus I consider as still "OnTopic"
This issue is still open in react-pdf, though I have seen it mentioned by other pdf.js users since mid year (MS or Chrome update ?) , so unsure if it is not a wider fail affecting Mozilla PDF.js code users.
https://github.com/wojtekmaj/react-pdf/issues/1010
https://github.com/wojtekmaj/react-pdf/issues/1025
There semes to be earlier reports back in Early March and then later suggestions to change win 10 drivers. However also reported by win 11 Pro users. PDF.js versions from 2.8.335 to 2.14.305, and it doesn't affect version 2.7.570. so partially down to updated versions ! But seen only in Chromium.
It is entirely possible that we started doing something that trips Chrome,
The symptoms seem to be hardware or settings orientated since it is reportedly seen on some identical groups of users but not affecting others.
toggling back and forth between single page and multi-page views the issue resolves. It also seems dependent on the resolution or appears on some machines and not others so it is a little tricky to repro.
I am not getting it personally, but a guy in my team get it.
Unclear which browsers are affected but looks like its a chromium / web kit rendering bug ?
Several browsers have been tested and only chrome faces this.
My colleague gets the same in Edge Version 101.0.1210.47 (Official build) (64-bit) and Brave (1.38.118 Chromium 101.0.4951.67) Will edit the issue
The suggested workaround is :-
Providing a standardFontDataUrl and disabling the font face fixes the issue.
if we disable Accelerated 2D canvas in chrome://flags then the preview appears nice and okay. But since this flag is on by default so user see the pixelated preview. Unless we ask them to turn off this flag.
Figured out that this only happens when hardware acceleration is enabled in your Chrome settings.
When its turned off the issue does not happen.
In address bar paste chrome://gpu or edge://gpu etc (its a long report of current onboard fixes) in my case (currently unconfirmed via reboot for my Edge) is showing Accelerated 2D canvas is unavailable: either disabled via blocklist or the command line. Disabled Features: 2d_canvas, thus I cannot see problems.
To change setting you can use
chrome://flags/#disable-accelerated-2d-canvas
but its a manual choice between options.
so on reboot I see
Graphics Feature Status
Canvas: Hardware accelerated
Canvas out-of-process rasterization: Disabled
but have little problem with the domo (except normal fuzzy text as pixels) so either Edge update or my hardware is not visibly affected or my default settings are reasonable.
This issue has been finally fixed in the latest version of react-pdf library. Check here: https://github.com/wojtekmaj/react-pdf/releases/tag/v6.2.2
I also faced the same error and I fixed it by setting render mode to canvas (earlier it was SVG) and scale value to more than 1. Try scale = 1.5
I have a strange problem happening intermittently with my apps where textbox controls would disappear intermittently. I have narrowed the cause of this down to having image files (small logos etc) on my page.
I have managed to create a simple project which contains an xaml page with an image and 2 textblocks (these are in grids).
I have found on two test tablets that I can re-create the problem by going to task manager and creating a dump file for the running app.
After I do this twice and resume the app, the two textblocks disappear.
This exact problem is happening intermittently in my live apps.
Has anyone any ideas why this might be happening or what I should try next? I have no idea why creating a dump file forces the issue.
You can see a video of me re-creating the issue here:
https://onedrive.live.com/redir?resid=DF2BE823348DEA6C!74381&authkey=!AIvSU05r0363S3Y&ithint=video%2cMOV
The test project in the video can be downloaded from here:
https://onedrive.live.com/redir?resid=DF2BE823348DEA6C!74382&authkey=!AIGHSdezFcCbEZQ&ithint=file%2czip
So far I can re-create it with the exact same steps on my two different tablets - both running Windows 8.1 Pro 32bit.
If you are familiar with sideloading apps and you have a 64bit tablet I would be really appreciative if someone was able to test out the exact same steps as seen in the video.
Any help would be extremely appreciated as I am clueless as to where to go next.
I finally got to the bottom of this. The problem was down to the intel graphics driver that was installed on the tablets.
An updated driver was released around April which seemed to resolve the issue.
I have observed this problem of disappearing controls on views that do not contain image files but rather a background image. After reading your method of how to reproduce the issue, I've since removed the background image and replaced with a LinearGradientBrush and retested with the dump file process. The problem seems to have disappeared. (I'm running 32-bit as well.)
Long time reader, first time poster :)
I'm developing an Windows Store app and I'm trying to load a formatted page into an in-app viewer. As Windows 8.0 does not support PDF natively, I'm trying to load the XPS format instead.
I've tried loading the XPS Uri directly into WebView using the code below, but the result is just a blank page:
ResultsWebView.Navigate(xpsFile);
Is there a way to view XPS file within Windows Store apps?
If not, can anyone think of a way to view formatted documents in app? My next option is probably to find an API to convert the PDF into a PNG image, and load the image directly. I'm trying to avoid using non-native APIs as my app needs to be cross-platform, so the tricky part with APIs is that I need to make sure whatever I use is compatible with both Windows RT and Windows 8.
PDF support was added in Windows 8.1 (in essence).
I researched extensively and could not find a suitable solution that was easy to implement, so I resorted to creating a new module that reads my inputs, generate an html stream, and use that stream to display on WebView.
In the end it was a couple of days' work to format it properly to match the PDF, but not hard at all to implement. I've already spent a lot of time researching an "easy" way out by reading PDF/XPS directly to no avail anyway.
Recently i am seeing a number of issues that are happening in our custom based browser but its not happening in the browsers like mozilla or chrome.
One example is mouse cursor i have given a custom cursor to it onmouseover of a window. This is working fine in Mozilla, chrome and in IE but not in the Adobe Air browser we created. I can see the custom cursor but there is lot of flickering between the custom cursor and the normal mouse pointer.
Is this an issue or there is an work around for this to support the adobe air browser? I am using Adobe AIR 3.4.
I haven't heard anything about Laszlo testing Adobe AIR apps, especially with the AIR releases in the past two years. The AIR browser has never been supported officially.
I'm assuming that you are still embedding an SWF into a HTML page for your AIR app. When using AIR with OpenLaszlo, I'd always generate an ActionScript 3 based AIR app (not embedding an app SOLO compiled to an SWF into an HTML container). That way, I can use Flash Builder to debug any problems, which makes things a lot easier than debugging embedded SWFs. If you plan to deploy a DHTML runtime app, there's of course no way around embedding the OpenLaszlo app into an HTML container.
Update: Flash 10.2 and higher support native cursor integration (native here means operating system), which provides MUCH better performance. Here's a general description of the API in an Adobe blog post: http://www.adobe.com/devnet/flashplayer/articles/native-mouse-cursors.html
It's technically possible to use the native cursor with OpenLaszlo, I've created a proof-of-concept - but it only works with a heavily modified version of the LzMouseKernel.as class (from the SWF9 kernel files in the LFC), since the kernel will always reset the cursor for various mouse events. And since native cursors require at least Flash 10.2, this is only possible with the SWF11 branch of OpenLaszlo.
I suspect that the problems you are seeing are connected to the way OpenLaszlo enables custom cursors (which is done by hiding the native mouse cursor and moving an sprite around following the invisible mouse cursor position).
In older windows we had a library called cards.dll that MS used for UI in card games. It looks like they are now using something different for it. Do anyone know how Microsoft paint cards in new Windows?
Thank you.
I opened the cards.dll from 32-bit Windows XP and the file contains bitmap resources with the cards. This DLL is not present on Windows 7 (64-bit). I opened the .exe in a resource editor and did not find any bitmap references which is something I'd normally have expected.
I then opened the executable with Dependency Walker to find out if there were any additional references to the equivalent of cards.dll and there were none. There was a reference to DirectX so I suspect that the cards are being drawn using that API, and are perhaps encoded in something other than a bitmap. Process Explorer's thread view also suggest DirectX is being used.