 No.08894
Tafoid Administrator
Sep 5, 2012, 01:01
|
Generally we take reference videos only when they are first hand recorded from the PCB owner and usually when emulation is known to be bad concerning some graphical/audio element that the video can help illustrate. Look at many many Smitdogg postings, for examples. Your previous xmen bug report (04765) regarding sound echo issues is linked again in this bug - to what end? Is this what all these videos are supposed to be illustrating is wrong with MAME- sound issues? Are you instead saying there is something else not shown in the full playthrough video, that these other videos show that are things wrong with MAME? In short, what is wrong with MAME that these videos are supposed to be showing? |
|---|---|
 No.08895
hap Developer
Sep 5, 2012, 20:09
|
-closing- youtube pcb recordings as reference are fine in actual bug reports though |
 No.08896
NekoEd Senior Tester
Sep 9, 2012, 17:19
|
While Youtube is an excellent resource for storing videos, there should still be some level of verifiability required within the video; any old recording could be purported to be from an original PCB when it's not, either intentionally through deception or unintentionally through a lack of awareness. I propose as a rough guideline the following: - Videos must include a clear shot of the PCB, either in-cab or on a test bench in the operating environment of the video - Videos should be made first hand, preferably from a stable camera mounting - Videos should have audio as clear as possible, with the ideal being operation in a space free of external noise - Possibly other things Criteria could be relaxed, for example, if it's a video bug, audio need not be clear (however, if the audio is bad or missing, it could indicate that the board being recorded is malfunctioning) or other things that should be handled on a case-by-case basis. However, having a firm base set of rules should aid the project in its goal of maximum accuracy. |