cannot install on ubuntu 16.04

[cheeseeeee]

Using GDebi I get the Error: Dependency is not satisfiable: python3-pychromecast

Using Software Install just doesn't work.

Using sudo apt-get install mkchromecast
I get
E: Unable to locate package mkchromecast

Using
sudo dpkg -i mkchromecast_$VERSION_all.deb
I get
dpkg: error processing archive mkchromecast_0.3.8.1-1_all.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
mkchromecast_0.3.8.1-1_all.deb

[muammar]

On Ubuntu 16.04 you don't have python3-pychromecast. You have to find a python3-pychromecast package that works for Ubuntu 16.04 https://packages.ubuntu.com/search?keywords=python3-pychromecast. Probably the one for zetzy could work?.

[cheeseeeee]

Well I gave up last night and I downloaded 0.3.7.1 version which does connect to my chromecast audio but i get no sound. Pulseaudio shows sound levels going to mkchromecast I think

[manugarri]

+1 to this, would be neat to have a 16.04 package (since its the latest LTS release its probably the most common one). Any tips on building the package?

[muammar]

Building the package is very easy. Just do a git checkout --track origin/debian. Install the build dependencies (see here). But note that before doing so, you need to change everything inside debian/control containing python3 to plain python e.g.: from python3-all to python-all.

Once you have them installed, you can do inside the cloned repo: dpkg-buildpackage. That sould generate a deb file.

[manugarri]

@muammar how about python-chromecast? would need to package it manually as well since its not in pipy (at least not in ubuntu 16.04).

[muammar]

On Wed, Feb 14, 2018 at 4:19 AM, Manuel Garrido ***@***.***> wrote: @muammar how about python-chromecast? would need to package it manually as well since its not in pipy (at least not in ubuntu 16.04).

For python-pychromecast you can use the version available in https://packages.ubuntu.com/zesty/python-pychromecast. That should work I think.

…

-- Muammar El Khatib. http://muammar.me

[pandasauce]

This is as far as I got on 16.04:

Download the sources, unpack into a directory of your choosing.

sudo apt install ffmpeg libav-tools lame python3-dev python3-virtualenv
python3 -m virtualenv --python=/usr/bin/python3 py3
source py3/bin/activate
pip install -r requirements.txt
python mkchromecast.py --video --command 'ffmpeg -f pulse -ac 2 -i default -f x11grab -r 25 -s 1920x1080 -i :1 -strict -2 -vcodec libx264 -preset ultrafast -tune zerolatency -maxrate 10000k -bufsize 20000k -pix_fmt yuv420p -g 60 -f mp4 -movflags frag_keyframe+empty_moov pipe:1' -s --debug

Key changes from the command auto-generated by --video --screencast are -f pulse -ac 2 -i default, -i :1 -strict -2 and removal of max_muxing_queue_size as described in #137.

This will install all dependencies into a virtualenv without cluttering up your OS with dependency hell. However, as far as audio goes, you will only be able to use your microphones as audio sources for casting, so this doesn't solve my issue of being unable to cast a movie.

Maybe newer versions of ffmpeg allow to create a loopback source easily, but on 16.04 LTS the process isn't something that I can work out in time - I won't have access to a Chromecast and a telly until September. I would start by figuring out how mkchromecast.py -s creates an audio sink for Pulse Audio and dig from there, because casting audio alone via that route just works.

Edit: actually, with a small manual change for display selection (the -i :1 part) the patch in #137 just works and creates a sink. Nice!

[leamas]

Well, well... I guest the proper solution could be that someone sets up a16.04 PPA with builds of mkchromecast + a backported python3-mklchromecast + possible other deps.

Any volunteers, out there?

Building on Ubuntu might work better after #172 is sorted out, though.

[evazzoler]

Ubuntu 16.04 is an LTS issue. LTS means "Long Term Support", 16.04 will end in 2021 (https://www.ubuntu.com/about/release-cycle).

An earnest developer does not stop the support of his software before the end of life of the OS... This is the problem of the "one-man-team" projects: a single brain that decides according to his personal tastes.

So, Ubuntu 16.04 users, you can't use this software!

[muammar]

@evazzoler IDGADF means I Don't Give a Damn Fuck.

Instead of being rude, waiting for others doing things for you, and making assumptions, you should instead HELP and send Pull Requests to make it work for the two-year-old Ubuntu 16.04. I am not paid for developing this and don't have the time to maintain every specific user need.

This software is written in Python, and you can always use it from its sources. Its license makes easy to modify it, and the fact that is free software does not mean the developer is a slave of user needs. I always am happy to merge pull requests from others. I don't see any from you.

[evazzoler]

I was waiting exactly that answer.
The philosophy is tipical: "don't expose your opinion about my insane choices, just start doing your own software".

I don't know python. Does it means that I can't use your software since you choose to not support a 2 years old LONG LIFE operating system?

The 16.04 compatibility is not a user need, is a community need. Try to understand that, one-man-team!

[muammar]

@evazzoler Don't use this "one-man-team software" and disappear. Thanks.

[evazzoler]

Sure, just consider it done!
The "one-man-team" software works on latest debian-like distro, because the answer of the "one-man" to other distros is "IDGADF"...

The Chrome/Chromium plug-in is universal and well working everywhere.
Closed working software...

[muammar]

@evazzoler Nice. No project needs the type of users you represent anyway. Goodbye.