MyGo 云音乐
Go와 MyGo로 만든 서드파티 네이버 클라우드 뮤직 데스크톱 클라이언트
VR에서 최대 4개의 동영상이나 사진 슬라이드쇼를 나란히 볼 수 있는 단일 페이지 WebXR 플레이어, Xbox 컨트롤러 헤드 커서 지원
Watch up to four videos or photo slideshows side by side in VR. A single-page WebXR player with an Xbox controller head cursor.
미디어HTML · JavaScriptGitHub @rodbuilds온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Watch up to four videos or photo slideshows side by side in VR, each on its own screen with its own controls.
Four Eyes is a single web page. Open it in Chrome or Edge on a PC with a VR headset, press Enter VR, and your own videos and photos appear on floating screens around you. There's nothing to install and no account, and your files never leave your computer.
.jps stereo photos are detected automatically.index.html and open it in Chrome.You can also load a single file or a direct video link onto a screen from its card on the page.
One screen is selected at a time, shown by a coloured frame. Looking at a screen selects it.
| Button | Action |
|---|---|
| A | Click whatever the head cursor is on. When it's on nothing, play/pause the selected screen |
| View | Open or close the media browser |
| Menu | Play or pause all screens |
| D-pad left / right | Previous / next video (or photo) in the selected screen's playlist |
| D-pad up / down | Volume (on a photo screen: time per photo) |
| LB / RB | Back / forward 10 seconds (photos: previous / next), hold to repeat |
| LT / RT | Back / forward 1 minute |
| Left stick left / right | Scrub 5 seconds at a time |
| Right stick up / down | Make the screen bigger or smaller |
| Right stick left / right | Crop the sides of the picture in or out |
| B | Mute |
| X | Solo this screen's sound |
| Y | Loop |
| Left stick click | Keep control bars visible, or let them fade |
| Right stick click | Show or hide the head cursor |
In the media browser: A opens a folder or plays what's under the cursor, B goes up a folder (or closes the browser), and LB / RB or the D-pad turn pages. ⚙ Settings at the top left holds the layout, curved screens, focus zoom, fit all in view, head cursor, crop options and photo time.
Point at a screen or button and pull the trigger. The trigger on a screen plays or pauses it. While pointing at a screen, the thumbstick skips (left/right) and changes volume (up/down).
Each screen has a two-row bar underneath it:
Top: FILES · PREV −10 ▶ +10 NEXT · MUTE V− V+ SOLO · S− S+ (CROP) LOOP SWAP
Bottom: seek bar · time (or photo count) · file name
SWAP: press it on one screen (its frame blinks), then look at another screen and press A, or press that screen's button, which now reads HERE. The two trade places and keep playing.
Photos: on a screen showing photos, V−/V+ become T−/T+ (time per photo), and −10/+10 go to the previous/next photo.
CROP (turn on "CROP button on screen bars" in settings): press it while the video plays to cut away empty borders; press again to undo. The head cursor fades while you watch a screen and comes back when you look elsewhere.
One self-contained HTML file with no build step and no server. It uses three.js (r128, loaded from a CDN) for rendering and WebXR, the browser's File System Access API for folder browsing, and the Gamepad API for the Xbox controller. Your added folders are remembered in the browser's IndexedDB.
The tests open the app in headless Chrome and check layout, Fit all in view, curved screens, crop detection, the control bar, settings and the media browser (shuffles and photo sets). They use the Chrome already on your computer.
npm install
npm test
If Chrome is somewhere unusual, point to it with CHROME_PATH. The tests open the page with
?test in the address, which makes it share its internals with them; normal visits never do.
They also run automatically on every pull request on GitHub.
What they can't cover is the headset itself: how it looks and feels in VR is still checked by hand.