Edit history:
ballofsnow: 2013-08-22 10:29:14 am
ballofsnow: 2013-08-22 10:28:41 am
ballofsnow: 2013-08-22 10:27:32 am
ballofsnow: 2013-08-22 10:25:53 am
ballofsnow: 2013-07-07 08:19:43 pm
ballofsnow: 2013-04-28 06:15:59 pm
ballofsnow: 2013-04-28 06:13:34 pm
ballofsnow: 2013-04-28 06:12:33 pm
ballofsnow: 2013-01-13 11:28:38 am
ballofsnow: 2012-04-21 02:24:51 pm
ballofsnow: 2012-04-21 09:10:58 am
ballofsnow: 2012-04-04 11:14:28 am
ballofsnow: 2012-04-04 11:13:13 am
ballofsnow: 2012-04-04 11:12:26 am
ballofsnow: 2012-04-01 06:33:27 pm
ballofsnow: 2012-04-01 06:33:18 pm
ballofsnow: 2012-04-01 06:27:28 pm
ballofsnow: 2012-04-01 06:26:50 pm
ballofsnow: 2012-04-01 06:23:14 pm
ballofsnow: 2012-04-01 06:22:15 pm
ballofsnow: 2012-04-01 06:17:42 pm
ballofsnow: 2012-04-01 06:15:57 pm
ballofsnow: 2012-04-01 06:12:41 pm
ballofsnow: 2012-04-01 06:11:18 pm
ballofsnow: 2012-04-01 06:10:51 pm
ballofsnow: 2012-04-01 06:07:54 pm
ballofsnow: 2011-08-21 12:12:09 pm
ballofsnow: 2011-08-21 12:11:48 pm
ballofsnow: 2011-08-21 12:11:25 pm
ballofsnow: 2011-07-27 10:14:52 am
ballofsnow: 2011-07-27 10:14:20 am
ballofsnow: 2010-09-04 09:55:38 am
ballofsnow: 2010-09-04 09:55:12 am
ballofsnow: 2010-08-14 12:21:43 pm
ballofsnow: 2010-05-30 04:38:14 pm
Types of quality tests
There are mainly two types of quality tests. The first is an optional “source file” quality test, where we verify the quality of the raw video from your capture device. The second type, if you're encoding your own run, is a required “final encode” quality test, where we verify that the quality of the video is suitable to be directly published on SDA.
Benefits of doing both “source file” and “final encode” quality tests:
Benefits of doing only a “final encode” quality test:
Recommendations:
Recommended format of your quality test thread
Thread title: Quality Test - [name of game] ([console])
Example: Quality Test - Pulseman (Wii VC/Genesis)
Thread content:
Upload sample(s).
“Source file” quality test sample:
“Final encode” quality test samples:
There are mainly two types of quality tests. The first is an optional “source file” quality test, where we verify the quality of the raw video from your capture device. The second type, if you're encoding your own run, is a required “final encode” quality test, where we verify that the quality of the video is suitable to be directly published on SDA.
Benefits of doing both “source file” and “final encode” quality tests:
- If the “source file” quality test passes, this usually leads to a quick pass on the subsequent “final encode” quality test.
- Easier troubleshooting. Problems that are identified are in a smaller scope, i.e. capture device to source files, and source files to final encode.
- Raw video data can be rather large and is often hundreds of megabytes for a few seconds of video. Finding a suitable file host can be difficult.
- An inherently longer process. Response time can be up to a few days.
Benefits of doing only a “final encode” quality test:
- A potentially quick pass on your quality test.
- Avoids uploading large raw video files. The final encode files may be small enough to be attached to your post and not use an external host.
- Difficulty in troubleshooting. Problems that are identified are in a larger scope, and can be anywhere between your capture device and final encode.
- If there is a problem and we don't have the source file, more time will likely be spent going back and forth trying to find a solution. This is especially true if there are a string of problems, i.e. fix one problem only to uncover another. In some cases we may run out of answers and ask for the source file anyway.
Recommendations:
- Follow the two-step process of posting both “source file” and “final encode” quality tests if you have a new capture setup and/or you are unsure whether the source file quality is acceptable.
- Do a quality test before recording your entire run! You may find that your source files are unacceptable in which case there is nothing else to do but to re-run and re-capture.
Recommended format of your quality test thread
Thread title: Quality Test - [name of game] ([console])
Example: Quality Test - Pulseman (Wii VC/Genesis)
Thread content:
- Type of quality test: source file / final encode.
- Your operating system: Windows XP / Windows Vista / Windows 7 / Mac OS / Linux / other.
- Capture hardware: DVD recorder / capture card / other / not applicable.
- Capture software: software accompanying DVD recorder or capture cards / Fraps / Camtasia / other.
- Capture video resolution.
- Name of the game, which console.
- If console, NTSC or PAL.
- (“Final encode” quality test) How you produced the video: Yua / Anri-chan / following guides in the KB / other.
Upload sample(s).
“Source file” quality test sample:
- Other than cutting, the source file sample must be untouched.
- Choose a scene with lots of motion.
- 5-10 seconds is a good sample length.
- Try compressing the source file in zip/rar format.
- Don't use terrible file hosting services in this forum, including Youtube and RapidShare.
“Final encode” quality test samples:
- If you used Anri-chan 3, upload the log file. It can be found in the finished folder.
- Required:
- LQ mp4 (~240p)
- MQ mp4 (~240p)
- HQ mp4 (~480p)
- Optional (if you made them):
- IQ mp4 (~720p)
- XQ mp4 (~1080p+)
- Not accepted:
- *Q avi
- *Q wmv
- 30-60 seconds is a good sample length.
- Don't use terrible file hosting services in this forum, including Youtube and RapidShare.
- If you followed the guides in the KB and created your own AviSynth scripts, post those as well. Associate them with the sample so we know which is for which. You can use [ code] [ /code] tags when posting the AviSynth code.
Thread title: