-->

ITunes 11.2.2 (32-bit) (105.98 MB) iTunes 11.1.5 (32-bit) (131.32 MB) iTunes 11.1.5 (64-bit) (141.99 MB) iTunes 11.1.4 (32-bit) (131.32 MB) iTunes 11.1.4 (64-bit) (142.01 MB) iTunes 11.1.3 (32-bit) (94.06 MB) iTunes 11.1.3 (x64) (95.75 MB) iTunes 11.1.0 (32-bit) (90.99 MB) iTunes 11.1.0 (x64) (92.67 MB) iTunes 11.0.5 (x64) (86.68 MB) iTunes 11.

The following functionality has been added in Direct3D 11.1, which is included with Windows 8, Windows RT, and Windows Server 2012. Partial support for Direct3D 11.1 is available on Windows 7 and Windows Server 2008 R2 via the Platform Update for Windows 7, which is available through the Platform Update for Windows 7.

Shader tracing and compiler enhancements

Direct3D 11.1 lets you use shader tracing to ensure that your code is performing as intended and if it isn’t you can discover and remedy the problem. The Windows Software Development Kit (SDK) for Windows 8 contains HLSL compiler enhancements. Shader tracing and the HLSL compiler are implemented in D3dcompiler_nn.dll.

The shader tracing API and the enhancements to the HLSL compiler consists of the following methods and functions.

The D3dcompiler.lib library requires D3dcompiler_nn.dll. This DLL is not part of Windows 8; it is in the bin folder of the Windows SDK for Windows 8 along with the Fxc.exe command-line version of the HLSL compiler.

Note

Download the latest version of iTunes (32-bit) for Windows. The perfect partner for your new iPod or iPhone. Apple made popular this full-featured mp3 player-organizer.
ITunes 11.1 is available for both Windows and Mac, and you can install the update from Apple’s iTunes download page. Alternatively, you can check the “Updates” tab on the Mac App Store to install iTunes 11.1. Even if you plan to do an OTA upgrade to iOS 7, it’s probably a good idea to have the latest.
Download iTunes 12.1.3 for Windows (32 bit) About iTunes. ITunes is the easiest way to enjoy your favorite music, movies, TV shows, and more on your PC. ITunes includes the iTunes Store, where you can purchase everything you need to be entertained. Your purchases are stored in iCloud and are available on your devices at no additional cost.

While you can use this library and DLL combination for development, you can't deploy Windows Store apps that use this combination. Therefore, you must instead compile HLSL shaders before you ship your Windows Store app. You can write HLSL compilation binaries to disk, or the compiler can generate headers with static byte arrays that contain the shader blob data. You use the ID3DBlob interface to access the blob data. To develop your Windows Store app, call D3DCompile2 or D3DCompileFromFile to compile the raw HLSL source, and then feed the resulting blob data to Direct3D.

Direct3D device sharing

Direct3D 11.1 enables Direct3D 10 APIs and Direct3D 11 APIs to use one underlying rendering device.

This Direct3D 11.1 feature consists of the following methods and interface.

Check support of new Direct3D 11.1 features and formats

Direct3D 11.1 lets you check for new features that the graphics driver might support and new ways that a format is supported on a device. Microsoft DirectX Graphics Infrastructure (DXGI) 1.2 also specifies new DXGI_FORMAT values.

This Direct3D 11.1 feature consists of the following API.

ID3D11Device::CheckFeatureSupport with D3D11_FEATURE_DATA_D3D11_OPTIONS, D3D11_FEATURE_DATA_ARCHITECTURE_INFO, D3D11_FEATURE_DATA_D3D9_OPTIONS, D3D11_FEATURE_DATA_SHADER_MIN_PRECISION_SUPPORT, and D3D11_FEATURE_DATA_D3D9_SHADOW_SUPPORT structures
ID3D11Device::CheckFormatSupport with D3D11_FORMAT_SUPPORT_DECODER_OUTPUT, D3D11_FORMAT_SUPPORT_VIDEO_PROCESSOR_OUTPUT, D3D11_FORMAT_SUPPORT_VIDEO_PROCESSOR_INPUT, D3D11_FORMAT_SUPPORT_VIDEO_ENCODER, and D3D11_FORMAT_SUPPORT2_OUTPUT_MERGER_LOGIC_OP

Use HLSL minimum precision

Starting with Windows 8, graphics drivers can implement minimum precision HLSL scalar data types by using any precision greater than or equal to their specified bit precision. When your HLSL minimum precision shader code is used on hardware that implements HLSL minimum precision, you use less memory bandwidth and as a result you also use less system power.

You can query for the minimum precision support that the graphics driver provides by calling ID3D11Device::CheckFeatureSupport with the D3D11_FEATURE_SHADER_MIN_PRECISION_SUPPORT value. In this ID3D11Device::CheckFeatureSupport call, pass a pointer to a D3D11_FEATURE_DATA_SHADER_MIN_PRECISION_SUPPORT structure that ID3D11Device::CheckFeatureSupport fills with the minimum precision levels that the driver supports for the pixel shader stage and for other shader stages. The returned info just indicates that the graphics hardware can perform HLSL operations at a lower precision than the standard 32-bit float precision, but doesn’t guarantee that the graphics hardware will actually run at a lower precision.

You don't need to author multiple shaders that do and don't use minimum precision. Instead, create shaders with minimum precision, and the minimum precision variables behave at full 32-bit precision if the graphics driver reports that it doesn't support any minimum precision. For more info about HLSL minimum precision, see Using HLSL minimum precision.

HLSL minimum precision shaders don't work on operating systems earlier than Windows 8.

Specify user clip planes in HLSL on feature level 9 and higher

Starting with Windows 8, you can use the clipplanes function attribute in an HLSL function declaration rather than SV_ClipDistance to make your shader work on feature level 9_x as well as feature level 10 and higher. For more info, see User clip planes on feature level 9 hardware.

Create larger constant buffers than a shader can access

Direct3D 11.1 lets you create constant buffers that are larger than the maximum constant buffer size that a shader can access (4096 32-bit*4-component constants – 64KB). Later, when you bind the buffers to the pipeline, for example, via PSSetConstantBuffers or PSSetConstantBuffers1, you can specify a range of buffers that the shader can access that fits within the 4096 limit.

Direct3D 11.1 updates the ID3D11Device::CreateBuffer method for this feature.

Use logical operations in a render target

Direct3D 11.1 lets you use logical operations rather than blending in a render target. However, you can’t mix logic operations with blending across multiple render targets.

This Direct3D 11.1 feature consists of the following API.

ID3D11Device1::CreateBlendState1 with D3D11_LOGIC_OP

Force the sample count to create a rasterizer state

Direct3D 11.1 lets you specify a force sample count when you create a rasterizer state.

This Direct3D 11.1 feature consists of the following API.

Note

If you want to render with the sample count forced to 1 or greater, you must follow these guidelines:

Don't bind depth-stencil views.
Disable depth testing.
Ensure the shader doesn't output depth.
If you have any render-target views bound (D3D11_BIND_RENDER_TARGET) and you forced the sample count to greater than 1, ensure that every render target has only a single sample.
Don't operate the shader at sample frequency. Therefore, ID3D11ShaderReflection::IsSampleFrequencyShader returns FALSE.

Otherwise, rendering behavior is undefined. For info about how to configure depth-stencil, see Configuring Depth-Stencil Functionality.

Process video resources with shaders

Direct3D 11.1 lets you create views (SRV/RTV/UAV) to video resources so that Direct3D shaders can process those video resources. The format of an underlying video resource restricts the formats that the view can use. The DXGI_FORMAT enumeration contains new video resource format values. These DXGI_FORMAT values specify the valid view formats that you can create and how the Direct3D 11.1 runtime maps the view. You can create multiple views of different parts of the same surface, and depending on the format, the sizes of the views can differ from each other.

Itunes 11.1 Windows 7 32 Bit Download