The difference between JDK and JRE is that the JRE only has what is needed to RUN a Java program while the JDK also contains what is needed to build Java programs from source code.ĭEBUG 2017 - 02 - 18 23: 09: 12.105 Validating uri C:\Users\Residentcl\Desktop\ 03 Dust.flac The current Java JDK can be downloaded here. I'm not sure if this has to be a Java JDK version or if a JRE will do, but you probably need a JDK to build UMS anyway. JAVA_HOME simply needs to point to your currently installed Java version, you will normally find it under C:\Program Files\Java. To add something to the existing PATH add a semicolon and then the new folder to include. The PATH location to add is the bin folder of the extracted zip file. Once the files are in place, just follow the description from the Maven installation description under "Windows Tips". Alternatively you can just create another folder somewhere you want, like C:\Maven that doesn't require administrator privileges. That will make sure you can write to the "Program files" folder. If you don't have the permissions to do so, rightclick your unzipping program (WinZip, 7Zip or whatever) and select "Run as Administrator". Unzip that to where you want it to be installed, e.g C:\Program files. Here is the correct download link for Windows. I don't know how much time I wasted trying to figure out simple things with Maven, but the installation is quite straight forward actually. When it comes to Maven they generally don't understand the concept "user friendliness". It doesn't sound like this is something worth implementing for a while at I would be great if it was tested before the next release. The API is not stable, the quality is pretty low and there are a lot of bugs. Chromecast 2 uses V2 of the protocol so I doubt that will work anyway.Ĭhromecast-java-api-v2 is made without knowing the specification and is based on "qualified guesses" and trial and error. There are 2 versions of the "secret" protocol, and UMS has some support for V1 as far as I can understand (I don't own a Chromecast so I've never tested it). This is what I consider extremely bad practice, and will make it hard to implement properly. In addition it doesn't seem like they have published the protocol but released an SDK for selected platforms only (Android, Chrome and IOS). Google has chosen to implement its own proprietary protocol which is a very bad thing imo considered the mess of standards it already is for streaming. I actually thought Chromecast was DLNA capable, but after some quick reading it seems it is not.
0 Comments
Leave a Reply. |