{"id":25351,"date":"2016-09-30T03:01:27","date_gmt":"2016-09-29T17:01:27","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=25351"},"modified":"2016-09-30T09:04:27","modified_gmt":"2016-09-29T23:04:27","slug":"karaoke-via-youtube-api-in-iframe-microphone-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/karaoke-via-youtube-api-in-iframe-microphone-tutorial\/","title":{"rendered":"Karaoke via YouTube API in Iframe Microphone Tutorial"},"content":{"rendered":"
\"Karaoke<\/a>

Karaoke via YouTube API in Iframe Microphone Tutorial<\/p><\/div>\n

It was always a plan with the “Karaoke via YouTube API” that we would try to “splice” in user contributions for a more real “Karaoke” experience. I’ve done work on this before, and it takes a lot of web server diskspace to be the one storing such audio files, and know why Snapchat<\/a> has the length (of media) limitation.<\/p>\n

There was discussion in HTML5 about standards as you can read here<\/a> and the discussion in Capturing Audio & Video in HTML5<\/a> sums it up really well as far as web applications go … you need to be able to execute, successfully, the Javascript function …<\/p>\n


\nnavigator.getUserMedia()
\n<\/code><\/p>\n

… to get anywhere that way. Now we don’t expect many users to have this accessible yet, but we do not restrict methodologies to use here, and we could be getting the user to use another desktop microphone recording app perhaps, just to arrive at, in order of preference …<\/p>\n