The problem is to cast the video to the TV through the Chromecast, but to play One known issue is after a pause the Chromecasting VLC always warns "this video requires conversion". bat out of it, this answer has the solution: prefix each command with start /b. Adding -no-audio has no effect as it seems the entire audio-video is handed wholesale to Chromecast. I have no idea how to get the IP from Chromecast or Chrome for that matter - I have found it from my router. I believe all of these are required, even if you have only one Chromecast. It seems you are free to choose whichever address you chose. It needs to be in the range 224.0.0.0 through 239.255.255.255 or you won't be able to connect more than client to it. The IP address is not your wifi or some such, it's a multicast address. "C:\Program Files\VideoLAN\VLC\vlc.exe" movie.mkv -sout-all -sout="#rtp".Thus, you need two Windows users, I added a chromecast user. If you switch the renderer, it will switch both instances. VLC seems to save settings to vlc-qt-interface.ini in AppData\Roaming\vlc. Others might have better ideas but this works. However, I have fallen into a few traps so I thought I will share my problems and the solutions I was able to find. The IP address reserved by IANA for multicast locally are in this rangeĢ39.0.0.0-239.255.255.255 Organization-Local Scope Note on the IP (IPv4) reserved for multicast: Chromecast via Chrome (well the streamer ( Server 1) and Chrome acting as Client 1 and streamer for the TV, probably un-needed).Chromecast hardware devices, I suppose you need only the streamer ( Server 1) on a correct IP/port and codex.Your TV can be dlna compliant in many ways (so you can set the vlc streamer to be compliant with the specific TV capabilities).Some of those app are able to scan the local network or a range of local IPs (see below). You know them because you give from command-line/GUI. In some box TV, as the ones with Kodi, it's possible to add an app to connect directly the box to a streaming, simply knowing the IP (and port) of the stream.I had not fully understood the part that brings the signal to your TV, but I have the impression you can try to save the Client 1 instance too. Here some paths to try to save resources:Īgain assuming you were able to use the speakers with vlc, maybe you may be able to save the Client 2 instance disabling in the streamer ( Server 1) the audio redirection to the stream and using the speakers from there (start trying with -no-sout-audio). If you specify an option you will force the execution with that option. > BTW vlc was (and still is) used to remember the last preferences modified in the last GUI execution and saved on exit. You understand how it can be "vicious": one time happens, one time no. It is a good practice to specify always the important options, to avoid eventual unwilled interferences from the options saved by a previous execution of the program. no-sout-video for video, -sout-audio -no-sout-audio (default enabled). There are many interesting options in this case, among them for the server -no-sout-display (default enabled), -sout-display default disabled, -sout-video. You can ask the huge one with -H ( -h is not enough, size matters when it is case sensitive :-)). Only the ideas trying to be useful to a wider audience and cover different hardware sets.Īny streamer program will have many options. Path for a less resource requiring solution (Ideas) This is the solution followed from the OP, after solving some problems peculiar to his OS, software, hardware. You can first connect two clients (eventually other two instance of vlc) to this server (to its streaming IP and PORT) and after you can start to play or pausing the streaming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |