Description
Screenbox exhibits inconsistent behavior when handling media URLs across different architectures. While direct MP4 URLs play successfully on both x64 and ARM64 devices, YouTube URLs cause instability. On ARM64 devices, attempting to play a YouTube URL results in a crash, whereas on x64 devices, the video fails to play but the application remains stable.

Upon debugging, it was observed that when a YouTube URL is entered, the flow proceeds through 'MediaListViewModel.Receive(PlayMediaMessage message)', followed by call to 'EnqueueAndPlay'. Occasionally, the application transitions into 'Receive (MediaPlayerChangedMessage message)' after returning from 'EnqueueAndPlay', which may be linked to the crash behavior on ARM64. The application crashes with an Access Violation Error.

Does the current implementation only support direct MP4 URLs? If YouTube URLs are not officially supported, the application should gracefully handle such inputs by validating the URL type and providing appropriate feedback to the user, rather than attempting playback and risking a crash.

Steps to reproduce the behavior

1. Go to Open URL option
2. Enter YouTube URL
3. Click Play
4. Application crashes in Arm64 device and fails to play on Intel

Expected behavior
YouTube video must play

Environment

• OS: Windows 11
• Device: Lenovo
• App Version v.0.16.0