亚洲国产精品久久久久,亚洲免费在线播放,一区二区三区久久网

Recording DirectX and OpenGL Rendered Animations�Q�翻译）

Daywei — Sat, 28 Apr 2012 07:08:00 GMT

记录DirectX和OpenGL渲染的动�?/span>
��?/strong>
    当我们创建游戏和仿真模拟�Ӟ��有时我们有必要记录渲染的内容。在某些情况下渲染过于复杂和耗时�Q�这是不可避免的�?br />     在DirectX中，库函数D3DXSaveSurfaceToFile()保存表面��Z��张图片文件。对OpenGL�Q�我们用glReadPixels()来读渲染的图像像素然后手动的保存它们��Z��张图片文件。然而这些表面只是针对单帧记录的�Q�对记录一�D�连�l��没有��单的�Ҏ��存在。换句话�?没有库函数来记录我们的完整存在渲染动��L��果�?br />    在这斚w��,本文提出了几�c?�q�有助于创造电影DirectX的方法和动画。用�c�CDxToMovie�?CGLToMovie电媄可以选择性地或连�l�的从DirectX和OpenGL渲染帧来创徏。一般来�?一个典型的电媄创作�q�程涉及复杂的�Q�?例如��d��的内�?选择帧速率讄��,�~�解码器的设�|?初始化媒体流,写媒体流�{�（详细讨论关于如何创徏位图囑փ�序列的电�?请参考这��文�?a >Create Movie from HBitmap�Q�。类CDxToMovie和CGLToMovie�q�里介绍的抽象出所有不必要的复杂性和易于使用的界�?提供��单方法解释如�?br />从DirectX渲染序列记录一个电�?br />    �c�CDxToMovie可以记录DirectX渲染序列成电影文件。该�cȝ��到DirectX 9.0接口例如LPDIRECT3DSURFACE9�Q�因此你应该用DirectX 9.0 SDK 或者其他的兼容的地方��用这个类 �?br />      开始从本文中的DirectX代码拯��文�gDxToMovie.h�Q�RenderTarget.h�Q�AviFile.h和AviFile.cpp��C��的工�E�目录下然后��d��他们��C��的工�E�中�Q�然后添加vfw.lib�Q�一旦添加到你的工程中，你可以通过#include "DxToMovie.h"讉K��。CDxToMovie构造函数接受不同的参数如输出电影文件名,电媄帧的宽度和高度的要求,每像素比�Ҏ��{?#8230;如下所�C?
CDxToMovie(LPCTSTR lpszOutputMovieFileName = _T("Output.avi"),
                int nFrameWidth = GetSystemMetrics(SM_CXSCREEN),  /**//*Movie Frame Width*/
                int nFrameHeight = GetSystemMetrics(SM_CYSCREEN), /**//*Movie Frame Height*/
                int nBitsPerPixel = 32,     /**//*Bits per Pixel*/
                DWORD dwCodec = mmioFOURCC('M','P','G','4'),  /**//*Video Codec for Compression*/
                DWORD dwFrameRate = 1)      /**//*Frame Rate (FPS) setting for the Movie*/
然�?应该注意到的�?�q�是一个时间设�|�，后来在电��p��录时候不能改�?nbsp;。每个CDxToMovie对应一个不同的电媄文�g和再造一个CDxToMovie对象��h��相同的输出文件的名字不会�q�加以前的电影内�?��覆盖它�?
CDxToMovie g_MovieRecorder("Output.Avi", 320, 240);
    一旦创建CDxToMovie对象�Q�方法CDxToMovie::OnCreateDevice()在你的程序Direct3D讑֤�创徏的时候会被调用。类似的�Q�CDxToMovie::OnLostDevice(),CDxToMovie::OnResetDevice()和CDxToMovie::OnDestroyDevice()也会在设备丢失销毁的时候各自被调用。这些函数的原型昄��如下
class CDxToMovie
{
HRESULT OnCreateDevice(LPDIRECT3DDEVICE9 pd3dDevice);
HRESULT OnDestroyDevice(LPDIRECT3DDEVICE9 pd3dDevice);
HRESULT OnLostDevice();
HRESULT OnResetDevice(LPDIRECT3DDEVICE9 pd3dDevice,
const D3DSURFACE_DESC* pBackBufferSurfaceDesc);
};
函数OnCreateDevice()和OnDestroyDevice()接受一个单单参敎ͼ�指向你程序的Direct3D讑֤�对象。OnLostDevice()没有参数�Q�但是OnResetDevice()�q�要有一个指针指向你讑֤�的后�~�冲��?D3DSURFACE_DESC*。CDxToMovie对象提供一些信息在D3DSURFACE_DESC�?创造一个合适的offscreen渲染目标,可以用来记录你的应用�E�序的渲染�?br />真正记录的功能是通过函数CDxToMovie::StartRecordingMovie()和CDxToMovie::PauseRecordingMovie().�q�两个函数必��L��一帧都要在IDirect3DDevice9::BeginScene() �?IDirect3DDevice9::EndScene()之间。如下所�C? g_pd3dDevice->BeginScene();     // Capture the Rendering onto CDxToMovie's Render Target     g_MovieRecorder.StartRecordingMovie(g_pd3dDevice);         // Render as usual..             g_pd3dDevice->Clear(0,NULL,D3DCLEAR_TARGET|D3DCLEAR_ZBUFFER, D3DCOLOR_XRGB(0,0,200),1,0);         g_pd3dDevice->SetStreamSource(0,g_pVB,0,sizeof(CUSTOMVERTEX));         g_pd3dDevice->SetFVF(D3DFVF_CUSTOMVERTEX);         g_pd3dDevice->DrawPrimitive(D3DPT_TRIANGLELIST,0,1);     g_MovieRecorder.PauseRecordingMovie(g_pd3dDevice);     // Copy the CDxToMovie's Render Target content back onto BackBuffer's Surface     g_pd3dDevice->StretchRect(g_MovieRecorder.RecordingSurface(),                               NULL,pBackSurface,                               0,D3DTEXF_NONE);     g_pd3dDevice->EndScene();在上面的代码�D�中�Q?nbsp;g_MovieRecorder.StartRecordingMovie(g_pd3dDevice)��所有随后的渲染在CDxToMovie的内部渲染目标直�?font face="Courier New">g_MovieRecorder.PauseRecordingMovie(g_pd3dDevice)被调用。所有的渲染工作在CDxToMovie的内部渲染目标上做，你的�E�序back surface��没有�Q何有效的内容昄��在你的应用程序窗口。这不要�?如果你的甌��不只是创作这部电影没有�Q何动�ȝ��接呈现在屏幕上。然�?如果你记录电�׃��一个互动游戏会话上,它会变坏屏幕不更新到最新的渲染的内�?因�ؓ通过重新渲染目标�Q�CDxToMovie内容被偷�?。�ؓ了避免它,你可以选择性地复制回CDxToMovie内部的渲染目标的内容��C��的应用程序的back surface 使用�Ҏ��IDirect3DDevice9:StretchRect(),其次是常见的g_pd3dDevice - > EndScene()和g_pd3dDevice - >Present()的要求会更新内容的呈现在屏幕上背�~�冲�?使屏�q�上更新�?br />如果你想避免一些��被选择性记录在�q�部电媄,只是不要叫g_MovieRecorder.StartRecordingMovie和g_MovieRecorder.PauseRecordingMovie()(相应�?g_pd3dDevice - > StretchRect())寚w��些��,�q�会直接渲染动画在屏�q�上(没有被重定向到CDxToMovie内部的渲染目�?�?br />演示代码提供�q�个��目提供了一个简单的应用�E�序,使得DirectX屏幕上的一个三角�Ş的动�?鼠标�U�d��H�户�?�q�将simulatenously被渲染成电媄文�g和记�?名叫output.avi)。跑演示的可执行�E�序,��保你有MPG4�~�解码器的计��机上安�?目录有写权限��d��出电影文件。详情请讄��解码器和�q��,请参考这��文�?a >Create Movie from HBitmap

Recording a Movie from OpenGL Rendered Sequence
先暂时不��译了，以后再翻�?br />
注：�W�一�ơ翻译，水��^比较差，�q�望各位看客见谅�?br />Reference�Q?nbsp;Recording DirectX and OpenGL Rendered Animations

Daywei 2012-04-28 15:08 发表评论

Daywei — Thu, 16 Feb 2012 07:24:00 GMT

1.关于创徏Direct3D讑֤�对象
   创徏Direct3D讑֤�对象�Ӟ��需要先创徏Direct3D对象�Q�然后再调用Direct3D对象的接口函数IDirect3D9�Q�：CreateDevice创徏Direct3D讑֤�对象。通过同一个Direct3D对象创徏的所有Direct3D讑֤�对象�׃�n相同的物理资源（昑֍��Q�。因为共享同一��g�Q�所以如果通过一个Direct3D对象创徏多个Direct3D渲染讑֤�对象会明��N��低系�l�性能�?br />   在创建Direct3D讑֤�对象之前�Q�还需要先初始化D3DPRESENT_PARAMENTERS�l�构�Q�该�l�构用于创徏Direct3D讑֤�对象。此�l�构��会影响Direct3D讑֤�的显�C�方法�?br />
D3DPRESENT_PARAMETERS

Describes the presentation parameters.
typedef struct D3DPRESENT_PARAMETERS { UINT BackBufferWidth, BackBufferHeight; D3DFORMAT BackBufferFormat; UINT BackBufferCount; D3DMULTISAMPLE_TYPE MultiSampleType; DWORD MultiSampleQuality; D3DSWAPEFFECT SwapEffect; HWND hDeviceWindow; BOOL Windowed; BOOL EnableAutoDepthStencil; D3DFORMAT AutoDepthStencilFormat; DWORD Flags; UINT FullScreen_RefreshRateInHz; UINT PresentationInterval; } D3DPRESENT_PARAMETERS, *LPD3DPRESENT_PARAMETERS;

Members

BackBufferWidth, BackBufferHeight
Width and height of the new swap chain's back buffers, in pixels. If Windowed is FALSE (the presentation is full-screen), these values must equal the width and height of one of the enumerated display modes found through IDirect3D9::EnumAdapterModes. If Windowed is TRUE and either of these values is zero, the corresponding dimension of the client area of the hDeviceWindow (or the focus window, if hDeviceWindow is NULL) is taken.
BackBufferFormat
The back buffer format. For more information about formats, see D3DFORMAT. This value must be one of the render-target formats as validated by IDirect3D9::CheckDeviceType. You can use IDirect3DDevice9::GetDisplayMode to obtain the current format.
In fact, D3DFMT_UNKNOWN can be specified for the BackBufferFormat while in windowed mode. This tells the runtime to use the current display-mode format and eliminates the need to call IDirect3DDevice9::GetDisplayMode.

For windowed applications, the back buffer format no longer needs to match the display-mode format because color conversion can now be done by the hardware (if the hardware supports color conversion). The set of possible back buffer formats is constrained, but the runtime will allow any valid back buffer format to be presented to any desktop format. (There is the additional requirement that the device be operable in the desktop mode; devices typically do not operate in 8 bits per pixel modes.)

Full-screen applications cannot do color conversion.

BackBufferCount
This value can be between 0 and D3DPRESENT_BACK_BUFFERS_MAX (or D3DPRESENT_BACK_BUFFERS_MAX_EX when using Direct3D 9Ex). Values of 0 are treated as 1. If the number of back buffers cannot be created, the runtime will fail the method call and fill this value with the number of back buffers that could be created. As a result, an application can call the method twice with the same D3DPRESENT_PARAMETERS structure and expect it to work the second time.
The method fails if one back buffer cannot be created. The value of BackBufferCount influences what set of swap effects are allowed. Specifically, any D3DSWAPEFFECT_COPY swap effect requires that there be exactly one back buffer.

MultiSampleType
Member of the D3DMULTISAMPLE_TYPE enumerated type. The value must be D3DMULTISAMPLE_NONE unless SwapEffect has been set to D3DSWAPEFFECT_DISCARD. Multisampling is supported only if the swap effect is D3DSWAPEFFECT_DISCARD.
MultiSampleQuality
Quality level. The valid range is between zero and one less than the level returned by pQualityLevels used by IDirect3D9::CheckDeviceMultiSampleType. Passing a larger value returns the error D3DERR_INVALIDCALL. Paired values of render targets or of depth stencil surfaces and D3DMULTISAMPLE_TYPE must match.
SwapEffect
Member of the D3DSWAPEFFECT enumerated type. The runtime will guarantee the implied semantics concerning buffer swap behavior; therefore, if Windowed is TRUE and SwapEffect is set to D3DSWAPEFFECT_FLIP, the runtime will create one extra back buffer and copy whichever becomes the front buffer at presentation time.
D3DSWAPEFFECT_COPY requires that BackBufferCount be set to 1.

D3DSWAPEFFECT_DISCARD will be enforced in the debug runtime by filling any buffer with noise after it is presented.

Differences between Direct3D9 and Direct3D9Ex

In Direct3D9Ex, D3DSWAPEFFECT_FLIPEX is added to designate when an application is adopting flip mode. That is, whan an application's frame is passed in window's mode (instead of copied) to the Desktop Window Manager(DWM) for composition. Flip mode provides more efficient memory bandwidth and enables an application to take advantage of full-screen-present statistics. It does not change full screen behavior. Flip mode behavior is available beginning with Windows 7.

hDeviceWindow
The device window determines the location and size of the back buffer on screen. This is used by Direct3D when the back buffer contents are copied to the front buffer during IDirect3DDevice9::Present.

For a full-screen application, this is a handle to the top window (which is the focus window).

For applications that use multiple full-screen devices (such as a multimonitor system), exactly one device can use the focus window as the device window. All other devices must have unique device windows.
For a windowed-mode application, this handle will be the default target window for IDirect3DDevice9::Present. If this handle is NULL, the focus window will be taken.

Note that no attempt is made by the runtime to reflect user changes in window size. The back buffer is not implicitly reset when this window is reset. However, the IDirect3DDevice9::Present method does automatically track window position changes.

Windowed
TRUE if the application runs windowed; FALSE if the application runs full-screen.
EnableAutoDepthStencil
If this value is TRUE, Direct3D will manage depth buffers for the application. The device will create a depth-stencil buffer when it is created. The depth-stencil buffer will be automatically set as the render target of the device. When the device is reset, the depth-stencil buffer will be automatically destroyed and recreated in the new size.
If EnableAutoDepthStencil is TRUE, then AutoDepthStencilFormat must be a valid depth-stencil format.

AutoDepthStencilFormat
Member of the D3DFORMAT enumerated type. The format of the automatic depth-stencil surface that the device will create. This member is ignored unless EnableAutoDepthStencil is TRUE.
Flags
One of the D3DPRESENTFLAG constants.
FullScreen_RefreshRateInHz
The rate at which the display adapter refreshes the screen. The value depends on the mode in which the application is running:
For windowed mode, the refresh rate must be 0.
For full-screen mode, the refresh rate is one of the refresh rates returned by IDirect3D9::EnumAdapterModes.

PresentationInterval
The maximum rate at which the swap chain's back buffers can be presented to the front buffer. For a detailed explanation of the modes and the intervals that are supported, see D3DPRESENT.

Requirements

Header: Declared in D3D9Types.h.
      几个重要的参数加以解释说明一下，其中BackBufferWidth和BackBufferHeight指定后台�~�存区的宽高�Q�以像素为单位）。如果图形以�H�口方式昄��q�且该成员变量被讄��?�Q�则�pȝ��自动使用昄��H�口客户区的宽高作�ؓ后台�~�冲区的宽高。BackBufferCount指定后台�~�冲区的数量。该值可以�ؓ0�?�?�?�Q�其�?�?旉��表示创徏一个后台缓冲区。通常使用一个后台缓冲区和一个主�~�存�Q�主�~�存��其昄��在屏�q�上�?br />

Daywei 2012-02-16 15:24 发表评论

Daywei — Mon, 30 Jan 2012 09:13:00 GMT
       �q�两天考虑把DirectX 版本升��Q�同时把相关的功能也升��Q�比如画图，之前用的是DirectDraw比较老，现在��x��用Direct2D�?br />      Direct2D是DirectX11中的新特性，可以说是DirectDraw的升�U�版。DirectX最新版�?a >http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=6812�Q�当然要想��用DirectX11需要系�l�支持，win7中就已带DirectX11�Q�而vista中��用就需要Update�Q�以下来自MSDN文档
      Direct3D 11 Runtime

To obtain the Direct3D 11 runtime, please install the release version of Windows 7 or Windows Server 2008 R2. Windows Vista users can follow the procedure described in KB 971644 (or KB 971512 for corporate network users).

http://support.microsoft.com/kb/971644

具体如何��d��C��个DirectX2D Application 参见DirectX 2010.6 版本中SDK文档——Windows DirectX Graphics Documention——Direct2D

Direct2D入门�Q?a >http://blog.pfan.cn/lym51/52200.html
使用Direct2D�l�图http://msdn.microsoft.com/zh-cn/magazine/ee413543.aspx

Daywei 2012-01-30 17:13 发表评论

Daywei — Fri, 23 Dec 2011 09:45:00 GMT

BOOL CD3DCameraViewWnd::GetImageInfo(DWORD* pPixelBuffer, int& width,int& height) { BOOL result = FALSE; IDirect3DSurface9 *_surfaceback = NULL; if (FAILED(m_pDevice->GetBackBuffer(0, 0, D3DBACKBUFFER_TYPE_MONO, &_surfaceback))) { result = FALSE; } D3DSURFACE_DESC surfaceDesc; if (!FAILED(_surfaceback->GetDesc(&surfaceDesc))) { width = surfaceDesc.Width; height = surfaceDesc.Height; } D3DLOCKED_RECT lockedRect; HRESULT hr = _surfaceback->LockRect( &lockedRect,0, 0); /* pointer to receive locked data指向甌��到的内存区域*/ /* lock entire surface*/// no lock flags specified if (!FAILED(hr)) { pPixelBuffer = (DWORD*)lockedRect.pBits; result = TRUE; } _surfaceback->UnlockRect(); _surfaceback->Release(); return result; }

但是�q�样存在着性能的问题，�l�测试获取一帧需�?00ms左右�Q��ؓ什么会存在�q�样的问题？因�ؓ�q�边有资源锁定操作�?

现在关键的问题就在于,资源锁定的操作速度��L��非常之慢.当然,你会跟我�? OpenGL��g��能够快捷地完成这��Q�?但是,在Direct3D�?资源锁定操作��实是很慢的.�q�里面一个主要的原因�?API,驱动,以及��g要处理一些不可回避的后台操作.那就是GPU与CPU是�ƈ行运行的,若不加�Q何措�?��引��L��似多�U�程�E�序同步时的竞态条件的问题.

如果你试囑֎�修改的资源正同时被一个位于GPU处理序列中的指��o使用,那么整个渲染��程��׃��因�ؓ你的资源锁定而停��或强制��h��(stalls and flushes).停顿(stall)会一直持�l�到你完成了对资源的修改�q�调用Unlock().而强制刷�?flush)则会要求GPU在你得到�q�个资源的访问权之前完成目前所有的��d��.

如何去解册��个问题？下面的参考资料中有一些解��x��案，我没有经�q�认真测试，我试了其中一个GetRenderTargetData �q�样的一�U�方�?�Q�感觉不太好用，why��L��Reference3

下面�l�出我的解决�Ҏ��

BOOL CD3DCameraViewWnd::GetImageInfo(DWORD* pPixelBuffer, int& width,int& height) { BOOL result = FALSE; IDirect3DSurface9 *_surfaceback = NULL; if (FAILED(m_pDevice->GetBackBuffer(0, 0, D3DBACKBUFFER_TYPE_MONO, &_surfaceback))) { result = FALSE; } D3DSURFACE_DESC surfaceDesc; if (!FAILED(_surfaceback->GetDesc(&surfaceDesc))) { width = surfaceDesc.Width; height = surfaceDesc.Height; }

LPDIREC3DSURFACE9 surf;
if(FAILED(m_pDevice->CreateOffscreenPlainSurface(width, height,D3DFMT_A8R8G8B8,D3DPOOL_SYSTEMMEM, &surf,NULL)))
{
result = FALSE;
}
D3DXLoadSurfaceFromSurface(surf, NULL,NULL,_surfaceback,NULL,NULL,D3DX_FILTER_NONE,0); D3DLOCKED_RECT lockedRect; HRESULT hr = surf->LockRect( &lockedRect,0, 0); /* pointer to receive locked data指向甌��到的内存区域*/ /* lock entire surface*/// no lock flags specified if (!FAILED(hr)) { pPixelBuffer = (DWORD*)lockedRect.pBits; result = TRUE; } surf->UnlockRect();
surf->Release();
_surfaceback->Release(); return result; }

参考资料：Reference1.http://www.cnblogs.com/mixiyou/archive/2010/02/25/1673060.html

Reference 2.http://www.cnblogs.com/mixiyou/archive/2010/02/25/1673425.html

Reference 3.http://blog.csdn.net/Nightmare/article/details/1707362

   Reference 4.http://www.cnblogs.com/lancidie/archive/2011/3/14.html

Daywei 2011-12-23 17:45 发表评论