What I gonna do is to capture a user video from webcamera in HTML than send this video to python which is to do the emotion analyzing.
I have get the video in by others work (RTC) which is a blob in javascript. My problem is how could I receive the video properly?
I try to use websocket to send the blob and the problem is how could i parse the received data back to a video in python?
I try to find some stuff but nothing. Maybe I choose the wrong idea. It would be great thanks if anyone give some tips.
Related
I want to know how to get all the data passed on the WebSocket
I alredy tryied using FireFox to see but all the data are strange unicode text and symbols (game link is https://sploop.io) is there an way to maybe decrypt it?
I also tryied using
var data= new WebSocket("usa1.sploop.io/ws")
data.onmessage = (sa)=>{console.log(sa)}
And after some actions in the game the code logged an object that didnt have any of the data...
You're already getting all the data the WebSocket is receiving. The problem is that the data is "encoded" binary data using the game's protocol. The scripts in Sploop.io know how to decode this data (and encode new data to be sent back), but since you don't "speak" that protocol, it looks like gibberish to you.
Problem aside, you can have fun and all, but trying to cheat or so isn't nice towards other players.
There's more context on the background of my project and the code I'm using here. I'm working on this project where we have to store/load pdfs in/from mongo. On the backend, I pipe the output of the download stream directly into the response and on the client side I get a responseText(you can see it in the picture in the linked post) of some weird,unreadable format(Filter/FlateDecode). I need to convert the responseText into an ArrayBuffer so I can feed that into PDF.js to render it in the browser. Can someone please give me some info on type of the string that's in the responseText and how to convert it into an ArrayBuffer?
Thanks
My aim is to have a form that submits a URL to an endpoint that returns a base64 encoding of a PDF that is shown on screen without a window.open popup.
Example output I want: https://s.natalian.org/2017-04-04/index.html
I'm confused how to use the resulting objectURL to show the data:application/pdf;base64 response.
With https://s.natalian.org/2017-04-04/ObjectURL.html I assume I am not decoding the base64 response properly? I don't know how to get it to render as a PDF like the output I want above.
How do you display a PDF now? It seems you'd need something like https://github.com/mozilla/pdf.js to do this without relying on plugins. If you need a URL, getting a blob URL from a Blob object seems the most straightforward.
As Surma points out in the comments: "If you want to work with Blob(), your server should return a binary PDF", and the problem with my endpoint was that it was returning a base64 encoded response.
I have since worked out how to make serverless respond in binary and posted the code here: https://github.com/calvintychan/serverless-html-pdf/pull/2
So I have a shoutcast server that displays info on this page:
http://soundstreamradio.serverroom.net:7424/
I am trying to pull the "Now Playing" data from this page and display it on my website that is playing the stream through a player.
Clicking on the song title and following this link:
http://soundstreamradio.serverroom.net:7424/currentsong?sid=1
Shows the current song in plain text...
So I'm wondering if there is a javascript or php script I can use to scrape this data to display it in my player?
I've tried AJAX but got cross domain errors and YQL gives me an error of "Invalid URL http://soundstreamradio.serverroom.net:7424/currentsong?sid=1: Invalid HTTP destination port"
I was wondering if there was anyone out there with a better idea to solve this issue?
Thank you so much in advance!
I would use preg_match() in PHP,
but it's a bit difficult because this page only
shows the artist name, song, then album(I presume?),
and the only way to separate these would be the " " or "-".
Some songs might have a "-" in them.
I am trying to hide the URL of my audio streams for my HTML5 player and was really struggling to think of a way to do so and then I realised, soundcloud must hide the URL's of their streams. So i went onto soundcloud, opened up the console and played a track but I couldn't see any obvious way that the URL is hidden. After this I took a look at the DOM tree to see if there was any kind of audio information in there but I found nothing! There's not even an ID for the player/audio so i'm very confused as to how soundcloud have done it.
Now I have done as best as I can so far with hiding the audio URL. I have put an ID in the DOM for the track, got that ID when the play button is clicked and retrieved the URL for that ID from the database. The obvious problem with that is that anyone willing enough can just go to the console and get the URL from the network events.
I am not trying to break past soundcloud's security to download tracks I shouldn't be. I'm just curious as to how they've hidden the URL. Now i'm also curious as to how each track is distinguished as there's nothing in the DOM distinguishing them (not that I found on my brief look anyway).
So, in short, does anyone have any ideas on how soundcloud has achieved this or how this could be achieved?
Soundcloud is pretty much a pure JS site.
As you said, there is no ID of the song loaded with the HTML. The way songs are recognized is by the page URL. The is done via. this url (example):
https://api.sndcdn.com/resolve?url=https%3A//soundcloud.com/hoodinternet/joywave-tongues-hood-internet-remix&_status_code_map%5B302%5D=200&_status_format=json&client_id=YOUR_CLIENT_ID
This returns something like this:
{"status":"302 - Found","location":"https://api.soundcloud.com/tracks/100270342?client_id=YOUR_CLIENT_ID"}
Next up it loads the location URL, from the JSON above. This returns a bunch of information about the track, including:
stream_url: "https://api.soundcloud.com/tracks/100270342/stream"
Then it loads this URL:
https://api.sndcdn.com/i1/tracks/100270342/streams?client_id=YOUR_CLIENT_IT
Which returns a response like this:
{"http_mp3_128_url":"https://ec-media.soundcloud.com/2gNVBYiZ06bU.128.mp3?ff61182e3c2ecefa438cd021sdf02d0e385713f0c1faf3b0339595664fe070de810d30a8e3a1186eda958909e9ed97799adfeceabc135efac83aee4271217a108450591db3b88\u0026AWSAccessKeyId=AKIAsdfJ4IAZE5EOIdsf7PA7VQ\u0026Expires=1374883403\u0026Signature=%2B1%2B7dfdfLN4NWP3C3bNF3gizSEVIU%3D"}
So that's how they hide their stream URL's. The only non obvious part is that they find the song ID, by hitting an API with the URL as a parameter. Same can be done with download URL's on tracks that support it.
If you goto SoundCloud.com and open up your debugger (Chrome is what I'm using). Look at the "Network" tab and you'll see a script calling audio?anonymous_id#########.
This is structured like a REST call, meaning they pass an id to a service on their backend, and that returns the audio output anonymously.
They Changed the Media center address and now they are streaming from the link like below.But the access to this url is restricted.
https://cf-media.sndcdn.com/Exbr0RDsakIP.128.mp3?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiKjovL2NmLW1lZGlhLnNuZGNkbi5jb20vRXhicjBSRHNha0lQLjEyOC5tcDMiLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE0NzgyOTg5NTV9fX1dfQ__&Signature=niisPQ5NHUqclFI9Mb-eH1BJvOC~0zUZme8CLMkocXMs2zCWe2U2~chPYDydJuYYV3iFtUjqwCK~t~~kQg2o5TKx0~iUSZ1E4ZNBbhvHJWqBliILbEd2gZzBnrHtS0nBNCMfIuUVWmkMtWAEWXI7NyvOBPqJab8KZR8qkFnleyzefHfssxPGWV8sW09en1VkjDRPasHRmc~w22lSpF3dWqZAFbocRFZGLS-h5eXj~Qin-kxMo2DgxHE0K-Svg4BPAJ83s408SkruRq3q3B46IBxmR4mDfx4U8T~tN1mvQZGWtXESm~rIY8K40ZSwdTlOE8eMiogFsjH5HzXvc3pBFA__&Key-Pair-Id=APKAJAGZ7VMH2PFPW6UQ