tizonia-openmax-il/Lobby

The Tizonia Project

SolarAquarion

@SolarAquarion

i'm getting build failures

i'll report it on github

Tizonia

@tizonia

This is the OOM killer terminating the compiler process. Tizonia needs quite a bit of free RAM to build the player sub-project with multiple ninja/make jobs.

c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.

The recommendation is build with one job (ninja defaults to 'automatic' number of parallel jobs, based on the number of CPUs)

 ninja -v -j1 -C build

It's mentioned here:
https://github.com/tizonia/tizonia-openmax-il/blob/master/BUILDING_with_meson.md#building

also here: https://github.com/tizonia/tizonia-openmax-il/blob/master/BUILDING.md#known-issues

SolarAquarion

@SolarAquarion

gotcha

eckhardt83

@eckhardt83

Hey I am new to Tizonia and want to play music from google play but i can't find the device id.
where do I find it ?

Tizonia

@tizonia

Hi, @eckhardt83

Good question... actually, things have changed wrt the device id and I've noticed recently. Some time ago, you needed a proper Android device id to use GMusic with Tizonia. Nowdays, it looks like google is not bothered so much and the API works even if you put some random number in the device id

Still, I try to add a proper device id when I can. there is an app in the Google Play Store called Device ID, this will give you that information

https://play.google.com/store/apps/details?id=com.evozi.deviceid&hl=en_GB

Tizonia internally uses the 'gmusicapi' library to access Google Play Music. There is some information about device ids in their documentation:
https://unofficial-google-music-api.readthedocs.io/en/latest/reference/mobileclient.html#setup-and-login

eckhardt83

@eckhardt83

yes I found the device id for 1 min ago whit the app but is says it not valid but then it give me one I can use :)
thanks for the help an this program look to be nice..

Tizonia

@tizonia

Yes, I forgot about that. If you are a GMusic subscriber, I think it will output the valid device ids associated to your account. I'll update Tizonia's docs, I think it's worth mentioning all of this

eckhardt83

@eckhardt83

yes it do but only when you have tryet whit a not valid number..

Tizonia

@tizonia

yes, that's my recollection as well. Just to confirm, are you a paying subscriber?

eckhardt83

@eckhardt83

yes i am ..

Tizonia

@tizonia

I thought so. I'm not a subscriber at the moment, but I still can access my library on GMusic even when using a random device id. So in my case, the software does not even bother returning the list of valid device ids.

Tizonia

@tizonia

The docs have been updated:
https://docs.tizonia.org/manual/googlemusic.html

eckhardt83

@eckhardt83

nice ..

Tizonia

@tizonia

@SolarAquarion
tizonia/tizonia-openmax-il#689 is now fixed
tizonia/tizonia-openmax-il#679 still remains an issue on Arch

hajah

@hajah

hi, my tizonia stopped working with spotify (playlists). It loads the tracks, but then doesn't start playing... did Spotify break something again ?

hajah

@hajah

can anyone test and confirm, if if's on Spotify's end or not? (i've the same issue on 2 systems)

Tizonia

@tizonia

@hajah
I'm also seeing this. It looks like the Spotify servers are not responding. I hope it's temporary.

[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.400 E [ap:1694] AP Socket Error: Connection refused (111)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.400 E [ap:3915] Connection error:  101
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.400 I [ap:1752] Connecting to AP ap.spotify.com:443
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.506 E [ap:1694] AP Socket Error: Connection refused (111)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.506 E [ap:3915] Connection error:  101
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.506 I [ap:1752] Connecting to AP ap.spotify.com:80
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.615 E [ap:1694] AP Socket Error: Connection refused (111)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.615 E [ap:3915] Connection error:  101
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.615 I [ap:1752] Connecting to AP ap.spotify.com:4070
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.723 E [ap:1694] AP Socket Error: Connection refused (111)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.723 E [ap:3915] Connection error:  101
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.723 I [ap:1752] Connecting to AP ap.spotify.com:443
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.830 E [ap:1694] AP Socket Error: Connection refused (111)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.830 E [ap:3915] Connection error:  101
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.830 I [ap:1752] Connecting to AP ap.spotify.com:80
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.939 E [ap:1694] AP Socket Error: Connection refused (111)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 21:52:24.939 E [ap:3915] Connection error:  101

Export this variable to see the messages:

export TIZONIA_DEBUG_COLOR_TRACE=1

hajah

@hajah

Thanks for confirming this. It actually came back last night, but it's down again this morning. So hopefully it's a bug on their end (Spotify) and not a new "feature".

Tizonia

@tizonia

Thanks for reporting back. I haven't noticed that myself, but the fact that it came back is probably good news. I believe other people have experienced exactly the same thing:
https://github.com/mopidy/mopidy-spotify/issues/163#issuecomment-591290010

Tizonia

@tizonia

The Spotify errors are slightly different this morning:

[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:00.198 E [ap:1694] AP Socket Error: Timeout reached (20000)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:00.198 E [ap:3915] Connection error:  117
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:00.198 I [ap:1752] Connecting to AP ap.spotify.com:443
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:05.203 E [ap:1694] AP Socket Error: Timeout reached (20000)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:05.203 E [ap:3915] Connection error:  117
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:05.204 I [ap:1752] Connecting to AP ap.spotify.com:80
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:10.208 E [ap:1694] AP Socket Error: Timeout reached (20000)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:10.208 E [ap:3915] Connection error:  117
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:10.208 I [ap:1752] Connecting to AP ap.spotify.com:4070
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:15.214 E [ap:1694] AP Socket Error: Timeout reached (20000)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:15.214 E [ap:3915] Connection error:  117
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:15.214 I [ap:1752] Connecting to AP ap.spotify.com:443
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:20.220 E [ap:1694] AP Socket Error: Timeout reached (20000)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:20.220 E [ap:3915] Connection error:  117
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:20.220 I [ap:1752] Connecting to AP ap.spotify.com:80
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:25.225 E [ap:1694] AP Socket Error: Timeout reached (20000)
[../plugins/spotify_source/src/spfysrcprc.c:log_message:1317] --- [Spotify] : 09:18:25.225 E [ap:3915] Connection error:  117

Tizonia

@tizonia

@hajah Spotify is working now

Lilianc2000

@Lilianc2000

Hi, i just installed tizonia and when trying to play a song on youtube, it give me the error "Youtube Error 403: Access Not Configured. YouTube Data API has not been used in project 422897895433 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=422897895433 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry." The link does not work

Tizonia

@tizonia

Hi, yes that was a problem that arised with YouTube a few days after the version 0.20.0 was released in the repos.

This has been fixed already in the master branch, but there are no binaries for that until 0.21.0 comes out

however, there is a way to incorporate the fix on your system:

You can do this:
find the location of this file on your system tizyoutubeproxy.py, and replace it with the latest version from the master branch:
https://github.com/tizonia/tizonia-openmax-il/blob/master/clients/youtube/youtubeproxy/tizyoutubeproxy.py

Tizonia

@tizonia

e.g.: In Ubuntu, /usr/lib/python3/dist-packages/tizyoutubeproxy.py

Lilianc2000

@Lilianc2000

It is working thank you !

Tizonia

@tizonia

cool!

Tizonia

@tizonia

@SolarAquarion
There is a new release of Tizonia (0.21.0). I've updated the tizonia-all package. Please have a look at it. So far it's working well on my Manjaro

Tizonia

@tizonia

Just a reminder, it is a good idea to force a single job with ninja -j1 in the PKGBUILD

SolarAquarion

@SolarAquarion

@tizonia it seems if you replace ninja with samurai, you can do SAMUFLAGS=-j4

Tizonia

@tizonia

@SolarAquarion
I see what you mean. I've never heard of samurai until just now! I've been doing some reading in the ninja bug tracker. Apparently, the ninja maintainers are refusing to add NINJA_FLAGS or similar, which would have helped us here.

Tizonia

@tizonia

Thanks for bringing it up. I'll definitely think about it.

SolarAquarion

@SolarAquarion

i'm going to add it to mine

Tizonia

@tizonia

Sounds great. Maybe I'll end up adding it as well.

SolarAquarion

@SolarAquarion

@tizonia you'll need to do "export SAMUFLAGS=-j4"

Tizonia

@tizonia

Do you mean exporting it in the build() step?. Correct me if I'm wrong, but I think that won't help people that have machines with low RAM. 4 parallel jobs could be enough to saturate the machine. I thought you wanted to allow people to override the internal auto-value by giving the option to the users of exporting themselves the SAMUFLAGS variable on their shells before starting the build.

SolarAquarion

@SolarAquarion

correct

@tizonia so do export SAMUFLAGS=-j1

i mean you could put the bash logic and let them do it

SolarAquarion

@SolarAquarion

@tizonia i did a PR of my PKGBUILD

Tizonia

@tizonia

Merged. Thanks!

Where communities thrive

People

Repo info

Activity