Add docs/research_Video.md
This commit is contained in:
		
							
								
								
									
										57
									
								
								docs/research_Video.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										57
									
								
								docs/research_Video.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,57 @@ | ||||
| ### Video Recognition | ||||
|  | ||||
| #### Costs | ||||
| - Developing and implementing a video recognition system can incur significant expenses, including hardware, software development, and ongoing maintenance costs. | ||||
|  | ||||
| #### Limited Applicability | ||||
| - Video recognition may not be suitable for all types of games, although for a specific card deck, this limitation may not be significant. | ||||
|  | ||||
| #### Technical Challenges | ||||
| - Implementing video recognition and voice output can be technically demanding and may require advanced hardware and software. | ||||
| - Card recognition and real-time processing pose significant challenges. | ||||
|  | ||||
| #### Technical Problems | ||||
| - Card Recognition Accuracy: Identifying cards accurately from a video feed can be challenging due to various factors such as lighting conditions and card orientation. | ||||
| - Real-Time Processing: Achieving real-time processing for effective gaming experience can be technically demanding. | ||||
| - Hardware Requirements: Real-time video recognition may necessitate powerful hardware components. | ||||
| - Environmental Factors: Changes in lighting conditions and other environmental factors can affect the accuracy of video recognition. | ||||
| - User Interface and Interaction: Developing an intuitive user interface for blind individuals presents challenges. | ||||
|  | ||||
| #### Comparison to NFC/RFID System | ||||
| - Video recognition requires less equipment and no physical modifications. | ||||
| - NFC/RFID systems offer faster, more reliable, and consistent performance. | ||||
| - NFC/RFID systems avoid some difficulties associated with video recognition, such as environmental factors. | ||||
| - Video recognition can be adapted to a broader range of games without altering physical components. | ||||
|  | ||||
| #### Comparison to Snapshot VR | ||||
| - Video recognition provides real-time feedback and continuous monitoring. | ||||
| - Snapshot VR offers reduced processing load and simpler debugging. | ||||
| - Snapshot VR may experience delays in providing information and may miss game changes between snapshots. | ||||
|  | ||||
| #### System Overview | ||||
| 1. **Camera**: A camera captures the game. | ||||
| 2. **Computer**: Connected to the camera, processes the video feed. | ||||
| 3. **Software**: Special software recognizes the cards and communicates with users. | ||||
| 4. **Website**: Displays game information for blind users. | ||||
| 5. **Voice or Sound**: Provides auditory feedback to players. | ||||
| 6. **Internet**: Facilitates gameplay with distant friends. | ||||
|  | ||||
| #### Development Timeline | ||||
| - Planning and research: 1-2 weeks | ||||
| - Hardware and software acquisition: 2-4 weeks | ||||
| - Development: 6-12 months | ||||
| - Testing and optimization: 2-3 months | ||||
| - UI design: 1-2 months | ||||
| - Integration: 2-4 weeks | ||||
| - User training and support: 1-2 months | ||||
| - Deployment and initial testing: 2-4 weeks | ||||
| - User feedback and adjustment: ongoing | ||||
|  | ||||
| #### Accelerating Development | ||||
| - Narrowing project scope | ||||
| - Utilizing pre-existing solutions | ||||
| - Rapid prototyping | ||||
| - Seeking expert assistance | ||||
| - Choosing readily available and well-documented hardware and software | ||||
| - Involving impaired users in the development process for feedback and understanding | ||||
|  | ||||
		Reference in New Issue
	
	Block a user