Preparing a dialog for recording - Revision history

BloodsongVengeance: /* Creating the Dialog Script */ added more detailed instructions & pic for dummies like me

2010-10-24T17:40:28Z

‎Creating the Dialog Script: added more detailed instructions & pic for dummies like me

BryanDerksen: category

2010-02-03T17:51:58Z

BryanDerksen: {{Infobox conversation}}

2010-02-03T17:50:47Z

KingEtzel at 23:47, 25 January 2010

2010-01-25T23:47:34Z

KingEtzel at 12:07, 16 January 2010

2010-01-16T12:07:28Z

KingEtzel at 12:06, 16 January 2010

2010-01-16T12:06:23Z

KingEtzel at 12:04, 16 January 2010

2010-01-16T12:04:28Z

KingEtzel at 11:35, 16 January 2010

2010-01-16T11:35:12Z

KingEtzel at 11:28, 16 January 2010

2010-01-16T11:28:27Z

KingEtzel at 11:23, 16 January 2010

2010-01-16T11:23:43Z

@@ Line 16: / Line 16: @@
 First of all, you need Microsoft SQL Server Management Studio Express to be installed: http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
-Then you start the tool for administering the database with administrator privileges (otherwise you won't be granted permission to access the database).
+Install and run it.  The first time it starts, it should find your Dragon Age database (BWDATOOLSET).  Just click OK.
-Click on "New query" and put in the text below. "Run" it afterwards to get the results you may need.
+Remember to start the tool with administrator privileges, if necessary. Otherwise you won't be granted permission to access the database.
-Find the String ID from one line of your conversation inside the toolset, and substitute it in this query:
+Click on "New query" at the upper Left.  Enter the text below into the right pane.
     SELECT [StringID],[ModuleResRefVersionID]
@@ Line 27: / Line 29: @@
       WHERE StringID = ####
-After you get the ID number of your dialog (that's what we search in this first step), open a new query and substitute the acquired number in this query as well:
+Copy the text below, select the entire text of your first query, and paste over it.  (Or if you prefer, you can press the "New Query" button again.)  Right click on the dialogue ID number in the result pane and copy/paste -- or just type it in where the #### is in this query:
     Declare @ResID INT
@@ Line 36: / Line 39: @@
        WHERE A1.StringID = A2.TextStringID AND A1.ModuleResRefVersionID = @ResID AND A2.ModuleResRefVersionID = @ResID
+Press the "! Execute" button again.  This will give you a list consisting of the LineIDs in the column 1, the speaker tag (blank is the OWNER) in column 2, and the spoken words in column 3. You can now mark everything and save it into CSV and reopen it with Excel. Or you can select all the lines up to the PLAYER lines and paste to your editing program of choice, etc.
-What you get is a list consisting of the LineIDs in the first column, who is speaking ("PC" or " "=OWNER), and the spoken words in column 3. You can now mark everything and save it into csv and reopen it with Excel.
 Now you can send the script to your voiceactors and you have minimized unneccessary work!

← Older revision		Revision as of 17:51, 3 February 2010
Line 42:		Line 42:

	[[Category:Conversations]]		[[Category:Conversations]]
		+	[[Category:Sounds]]

← Older revision		Revision as of 17:50, 3 February 2010
Line 1:		Line 1:
		+	{{Infobox conversation}}
	''(this article is based on the investigations of Kaldir II and KingEtzel)''		''(this article is based on the investigations of Kaldir II and KingEtzel)''

@@ Line 13: / Line 13: @@
 == Creating the Dialog Script ==
-First of all, you need Microsoft SQL Server Management Studio Express to be installed: http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=de
+First of all, you need Microsoft SQL Server Management Studio Express to be installed: http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
 Then you start the tool for administering the database with administrator privileges (otherwise you won't be granted permission to access the database).

@@ Line 1: / Line 1: @@
 ''(this article is based on the investigations of Kaldir II and KingEtzel)''
 == Introduction ==
@@ Line 8: / Line 10: @@
 Below we describe a way of creating the dialog inside of the toolset and then, by using little SQL queries, export not only the lines but also their corresponding LineIDs so that the voiceactor can not only match the format convention, but also the naming convention for the files themselves. The only thing for you left to do is putting those recorded files into the right folder and everything should work. No need for you to rename thousands of files manually to put them into the module/game!
 == Creating the Dialog Script ==

@@ Line 5: / Line 5: @@
 You could do that by writing all dialogs in a textprocessor like MS Word and just send them those documents. However, you would have to copy and paste the whole tree of lines into the toolset one by one, in order to get even the text work ingame. On the other hand you could type your whole dialog stuff in the toolset, but then - lacking a native export function - you would have to copy and paste again to get it into a form, where voiceactors can read your dialog.
-Below we describe a way of creating the dialog inside of the toolset and then, by using little SQL queries, export not only the lines but also their corresponding LineIDs so that the voiceactor can not only match the format convention (24kHz, 16bit mono PCM), but also the naming convention for the files themselves ('''123'''_m.wav). The only thing for you left to do is putting those recorded files into the right folder (see [[Conversation#Recording_VO]]) and everything should work. No need for you to rename thousands of files manually to put them into the module/game!
+Below we describe a way of creating the dialog inside of the toolset and then, by using little SQL queries, export not only the lines but also their corresponding LineIDs so that the voiceactor can not only match the format convention, but also the naming convention for the files themselves (see [[Voice-Over]]. The only thing for you left to do is putting those recorded files into the right folder (see [[Conversation#Recording_VO]]) and everything should work. No need for you to rename thousands of files manually to put them into the module/game!
 First of all, you need Microsoft SQL Server Management Studio Express to be installed: http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=de

← Older revision		Revision as of 11:35, 16 January 2010
Line 1:		Line 1:
−	''(this article is based ~~off~~ the investigations of Kaldir II and KingEtzel)''	+	''(this article is based on the investigations of Kaldir II and KingEtzel)''

	When you successfully have created dialogs in your toolset, you may want to send it out to voiceactors for recording at a certain point.		When you successfully have created dialogs in your toolset, you may want to send it out to voiceactors for recording at a certain point.

@@ Line 3: / Line 3: @@
 When you successfully have created dialogs in your toolset, you may want to send it out to voiceactors for recording at a certain point.
-You could do that by writing all dialogs in a textprocessor lika MS Word and just send them those files. However, you would have to copy and paste the whole tree of lines into the toolset, in order to get even the text work ingame. On the other hand you could type your whole dialog stuff in the toolset, but then - lacking a native export function - you would have to copy and paste again to get it into a form, where voiceactors can read you dialog.
+You could do that by writing all dialogs in a textprocessor like MS Word and just send them those documents. However, you would have to copy and paste the whole tree of lines into the toolset one by one, in order to get even the text work ingame. On the other hand you could type your whole dialog stuff in the toolset, but then - lacking a native export function - you would have to copy and paste again to get it into a form, where voiceactors can read your dialog.
-Below we describe a way of creating the dialog inside of the toolset and then, by using little SQL queries, export not only the lines but also their corresponding LineIDs so that the voiceactor can not only match the format convention (22kHz, 16bit mono PCM), but also the naming convention for the files themselves ('''123'''_m.wav). The only thing for you left to do is putting those recorded files into the right folder (see [[Conversation#Recording_VO]]) and everything should work. No need for you to rename thousands of files to put them into the module/game!
+Below we describe a way of creating the dialog inside of the toolset and then, by using little SQL queries, export not only the lines but also their corresponding LineIDs so that the voiceactor can not only match the format convention (22kHz, 16bit mono PCM), but also the naming convention for the files themselves ('''123'''_m.wav). The only thing for you left to do is putting those recorded files into the right folder (see [[Conversation#Recording_VO]]) and everything should work. No need for you to rename thousands of files manually to put them into the module/game!
 First of all, you need Microsoft SQL Server Management Studio Express to be installed: http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=de
@@ Line 21: / Line 21: @@
-After you get the ID number of your dialog (that's what we search in this first step), open a new query and substitue the acquired number in this query as well:
+After you get the ID number of your dialog (that's what we search in this first step), open a new query and substitute the acquired number in this query as well:
     Declare @ResID INT
@@ Line 30: / Line 30: @@
-What you get is a list consisting of the LineIDs in the first column, who is speaking ("PC" or ""=OWNER), and what it said in column 3. You can now mark everything and save it into csv and reopen it with Excel.
+What you get is a list consisting of the LineIDs in the first column, who is speaking ("PC" or " "=OWNER), and the spoken words in column 3. You can now mark everything and save it into csv and reopen it with Excel.
 Now you can send the script to your voiceactors and you have minimized unneccessary work!
 [[Category:Conversations]]