I need to create images for a slideshow. The problem is that the images will be displayed in different screens.
I want to know if I can use the same resolution for all of them (1920 x 1080) 72px/inch.
Screens:
1. 24ft x 14ft pitch 12mm - Aspect ration must be 16:9
2. 12ft x 9ft pitch 15mm - Aspect ration must be 16:9
3. 55" TV - Supports full HD (1080 or 720)
4. 42" TV - Supports full HD (1080 or 720)
5. 19" screen - Maximum resolution is 1440 x 900
I don't know much about resolutions and any help will be greatly appreciated.
Thank you.
1920x1080 will be large enough for any television. Full HD (1080p) means 1080 horizontal scanlines (meaning 1080 pixels tall).
The size in inches is irrelevant in this case.
The only reason I could see for going larger than 1920x1080 is if the screen depth is more than 72 DPI (e.g. the iPhone retina display, which is 326 ppi)
Related
I am developing a Qt4 application on Windows that can also run on a Linux target.
My problem is that when using setPixelSize for a text, the rendering is different between Linux and Windows (in this case smaller on Linux).
Reading the Qt documentation, using setPointSize allows to have a size independent of the platform:
void QFont::setPixelSize(int pixelSize)
Sets the font size to pixelSize pixels.
Using this function makes the font device dependent. Use
setPointSize() or setPointSizeF() to set the size of the font in a
device independent manner.
However, when using setPointSize, I still get a size difference of about 10-20%.
How can I solve this?
Linux platform:
Size: 7”, 152 mm (W) x 91 mm (H)
Resolution: 800 x 480 px (WVGA), 15:9
Physical DPI : 72
Logical DPI : 72
Windows platform:
Size: 15.6”
Resolution: 1920 x 1080 px
Physical DPI : 96
Logical DPI : 96
I have one desktop and one laptop (windows 10).
The size of the monitor installed on the desktop is 24 inches.
They are same resolution(1920 by 1080) and i set same zoom ratio in Windows 10.
I do not use Movewindow function or other things to fix the size, however, the dialog size in the laptop and the desktop is different.
It causes that the controls in my software are overlapping each other.
please let me know if i notify other settings!!
Thank you.
Sorry, my question is not specific, i add two pictures.
In laptop, the setting of Windows is overlapped with the setting of DICOM.
Of course, i can make the controls not overlapping when i directly use 'movewindow' on dialog, but i want to know why the two dialogs have different size.(same resolution(1920 x 1080), same zoom ratio on windows 10)
In Desktop, the print dialog has 791 x 632 size, in latop, the print dialog has 911 x 816 size.
I will check DPI-Awareness. Thank you for your comments!
I'm getting to know about this phenomenon.
In laptop, The resolution is 1920 X 1080, However, the ratio value which Windows 10 recommend is 125%.
I Change the ratio to 100% then, It worked at a higher resolution i think.
I use this code to get a resoltion.
MONITORINFO mi;
::ZeroMemory(&mi, sizeof MONITORINFO );
mi.cbSize = sizeof MONITORINFO;
if( ::GetMonitorInfo(hMonitor, &mi))
In laptop,
When i use 100% the size of text, apps, and other items in Scale and layout,
then The mi.rcMonitor's width = 2400
if i change the ratio value to 125%(which windows recommend), then The mi.rcMonitor's width = 1920
I don't know how to represent 2400 * 1350 in 1920 * 1080 monitor, so i will study this!
Consider 2 raster systems with resolution 640X480 and 1280X1024. How many pixels could be accessed per second in each of these systems by display controller that refreshes screen at rates of 60 frames per second. What is access time per pixel in each system?
Please explain in details
I am fetching images remotely and need to apply scaling so they look nice on all devices. But I am not sure what DPI value shall I take as a reference point.
For example, the size of the remote image is 155px which looks nice on XXHDPI devices. I need to scale it for devices of lower DPI.
So in this case, does scale 1 means MDPI or XXHDPI?
1 means MDPI or XXHDPI has not a lot of sense. mdpi is always to be considered **the unity, so to speak.
Keep in mind the correct proportions:
0.75 for ldpi
1 for mdpi
1.5 fot hdpi
2 for xhdpi
3 for xxhdpi
So, 155px at xxhdpi means 155px is 3 times the mdpi resolution.
This means that the correct px size for the mdpi resolution will be 155px / 3 (~ 52px).
To get the hdpi version, you'd do 155px / 2 (~ 78px). (I simplified here, it was (155px / 3) * 1.5.
To get the xhdpi version... (155px / 3) * 2 (~ 104px).
155 / 3 is the magic number to get the unity (mdpi version)
So, to get the ldpi version, do (155px / 3) * 0.75 (~ 39px) (or you can simplify to 155px / 4).
Note that you could use multiplication for the inverse to get a faster division:
155 / 3 is slower than 155 * 0.333 - This is a golden rule for every CPU/ALU.
for a 8KHz wav sound i took 20ms sample which has 160 samples of data, plotted the FFT spectrum in audacity.
It gave the magnitudes in 3000 and 4000 Hz as well, shouln't it be giving the magnitudes until
the 80Hz,because there is 160 samples of data?
For a sample rate of Fs = 8 khz the FFT will give meaningful results from DC to Nyquist (= Fs / 2), i.e. 0 to 4 kHz. The width of each FFT bin will be 1 / 20 ms = 50 Hz.
actually audacity shows the peaks as 4503Hz which means understands to 1Hz bins. by the way if I take 20ms and repeat it 50 times to make as 1s sample,is the fft going to be for 1Hz bins? and also audacity has the option for the window as far as I know If you use windowing then the components should be multiple times of 2,like 1,2,4,8,etc.. but it shows the exact frequencies,then why it uses the windowing?
The best sampling rate is 2*frequency.
in different frequencys you should to change the sampling rate.