kozova1/parsec-integration-with-retropie

script to integrate parsec with retropie

A Parsec Integration With RetroPie Script

This is a script for integrating Parsec with RetroPie. At the moment the script only supports the Carbon and Pixel Themes.

The Raspberry Pi 4 is currently NOT supported by Parsec, so the script will not work on it.

Installation

First find out your Peer id by clicking on the Computers Tab in the Parsec app.

And right clicking on the Computer you want to connect to.
Left clicking on the Peer ID will copy it.
Write down the number if you like.
Warning: the ID is case sensitive.

Run the following command in the terminal:

$ curl -fsSL https://raw.githubusercontent.com/Kozova1/Parsec-Integration-With-RetroPie/master/curlsetup.sh | sh

Follow the instructions on screen.
After the script finishes it's work it's recommended to restart 'EmulationStation' or your Raspberry Pi.
You should see a 'Parsec' console option in EmulationStation.
Login with your parsec account.
Click Connect on your desired PC.

DISCLAIMER

1. I am not responsible for any loss of data, hardware etc. You take full responsibility.
2. Setup.sh alters your installation such that future updates of RetroPie will not effect es_systems.cfg.

Note: in the future, you will have to manually update /home/pi/.emulationstation/es_systems.cfg, as it will not be overwritten by RetroPie updates.

Credits:

• CBNathanael
• EmulationStation
• RetroPie Project
• DSandler
• advanttage
• https://www.flaticon.com:
  • Freepik - Right click, SH icons
  • Roundicons - Left Arrow icon designed by Roundicons from www.flaticon.com

parsec-integration-with-retropie's Issues

setup.sh fails after entering server id on fresh retropie 4.3 install

I continue to receive the following error when running setup.sh on a fresh install of RetroPie 4.3.

I believe the issue is related to the missing Parsec.sh script reference not being included in the repo.

pi@retropie:~/Parsec-Integration-With-RetroPie $ sudo bash setup.sh
Made by Kozova1
--2018-03-04 19:43:15--  https://s3.amazonaws.com/parsec-build/package/parsec-rpi.deb
Resolving s3.amazonaws.com (s3.amazonaws.com)... 52.216.164.45
Connecting to s3.amazonaws.com (s3.amazonaws.com)|52.216.164.45|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1129790 (1.1M) [application/x-debian-package]
Saving to: ‘parsec-rpi.deb’

parsec-rpi.deb      100%[=====================>]   1.08M  1.75MB/s   in 0.6s

2018-03-04 19:43:16 (1.75 MB/s) - ‘parsec-rpi.deb’ saved [1129790/1129790]

Selecting previously unselected package parsec.
(Reading database ... 88405 files and directories currently installed.)
Preparing to unpack parsec-rpi.deb ...
Unpacking parsec (139-1) ...
Setting up parsec (139-1) ...
Processing triggers for mime-support (3.58) ...
chmod: cannot access ‘Parsec.sh’: No such file or directory
cp: cannot stat ‘/home/pi/.emulationstation/es_systems.cfg’: No such file or directory
sed: can't read /home/pi/.emulationstation/es_systems.cfg: No such file or directory
Parsec entry added to EmulationStation
Type your servers ID its on the server console tab
109623
cp: cannot create directory ‘/home/pi/.emulationstation/themes/carbon’: No such file or directory
Carbon theme altered to fit Parsec
ROM File written
setup.sh: line 27: if[  != nodrv]: command not found
setup.sh: line 28: syntax error near unexpected token `then'
setup.sh: line 28: `    then'

Cannot create directory

"Preparing to unpack parsec-rpi.deb ...
Unpacking parsec (139-1) over (139-1) ...
Setting up parsec (139-1) ...
Processing triggers for mime-support (3.58) ...
mv: cannot stat ‘/opt/retropie/configs/all/emulationstation/es_systems.cfg’: No such file or directory
mv: cannot stat ‘es_systems.cfg’: No such file or directory
This script will integrate Parsec with RetroPie it will appear within RetroPie in the ports section
Made by Kozova1
Type your servers ID its on the server console tab
xxxxx
cp: cannot create directory ‘/opt/retropie/configs/all/emulationstation/themes/carbon’: No such file or directory
Reading package lists... Done
Building dependency tree
Reading state information... Done
xboxdrv is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded.
Parsec Build 139-8 on rpi"

After the setup, runs normal if i unload the EmulationStation, but doesn't appear the shortcut.

Parsec.sh incorrect contents

The set up script is not stopping to collect the Peer ID so Parsec.sh is not set up correctly.

When running the script, the last few lines of output are as follows. It runs to completion without asking for my input.

/===============
...
Processing triggers for mime-support (3.62)
sed: -e expression #1, char 15: extra characters after command
What is the Peer ID?:
ROM File written
/===============

At the end of the set up the contents of Parsec.sh are as follows:

/===============
parsecd server_id= << EOFy
1
EOF
/===============

This is occurring on a new retropie installation, v4.8 for (an old) pi 3b+.

It also appears the carbon theme customization is not being applied correctly due to new folder structure but I have not gotten that far yet and would be a separate issue.

a lot of parsec tabs

when I follow the how to in the readme it creates 1 parsec tab in my homescreen. but when I then start it via the terminal it creates 10 Parsec tabs. How can i fix this?

parsec command not found

After running the setup.sh it cannot find the 'parsec' command, it can find the parsecd command but thats a GUI one and it crashes Retropie after connecting to the host.

[question] Raspberry Pi version support

Hi, In the how to you have mentioned that this supports only Raspberry Pi. Which version did you have in mind - 3 or 4?
AFIK Raspberry Pi 4 is not supported by parsek so it would be interesting to know if you managed to make it work.
Thanks.

Gettting Error 429 when launching

Sorry for being a super noob but I'm just starting with Raspberry Pi and I'm trying to get Parsec working with Retropie's front end. I can launch parsec from the terminal no problem but when I select Parsec from the Retropie menu it asks for login credentials then immediately gives me 'Error 429' and suggests I go on the Parsec Discord but I didn't get any answers.
Anyone know how I can auto login through the front end, I'm sure their are scripts to make it happen but that's above my knowledge right now. When I first set it up after I entered 'sudo bash setup.sh -nodrv' it didn't ask me for a server ID, it just waited for a new command, so I entered 'parsec' and then it asked for an email and password then it worked, but I was hoping to launch from Retropie so I can use a controller for the whole experience. Thanks for reading.

[Question] How to return to emulationstation?

Hey nice work setting this up! As I wrote in the title, how do you exit from Parsec to return to the emulation station menu? I tried all the button combos i could think of on a controller and keyboard.

Adding this info to the ReadMe would be super helpful.

Error when trying to launch Parsec

I am new to parsec and retropie. I followed the instructions and when I type in 'parsec' or 'sudo parsec' i get "-bash: parsec: command not found. I did see that there is a 'parsec' option where the other emulators are. when I try to launch it that way I get the very brief message:
"/home/pi/RetroPie/roms/parsec/Parsec.sh: line 3: warning: here-document at line 1 delimited by the end-of-file (wanted 'EOFy')
/home/pi/RetroPie/roms/parsec/Parsec.sh: line 1: parsec: command not found"

Not sure where to go from here.
I am using a Raspberry Pi 3b+
The only changes I have made are to expand the file system and to enable SSH.
I have not even installed any rooms yet

How to debug?

Cool stuff here - at least I think it is, if only it worked for me. :)

I'm trying to get this working on a Pi3B with a fresh Retropie installation.
I can run the script without any apparent issues.
However, after restarting ES, or even the pi, I still don't see any Parsec emulator.
It doesn't seem to start anything up by itself, but even when starting parsecd and restarting ES, I still don't see anything.
journalctl gives me nothing.

Any hints to where to start looking?

Error -2001

this is the error i got launching parsec from emulation station

Logging in to parsec

When I try to use parsec on RetroPie it gives me the error 2001, I looked it up and saw that means I'm not logged in. My question is how do I log in?

Black screen when connected to a host

Whenever I try connect to a host on my retropie, it just shows a black screen even though on the host it says that I am connected.

No such option as "Remember me"

Parsec is working fine on Pi 3 B+'s Retropie. I had a few problems where I installed it as per instructions, but for some reason I had to run it with "parsecd" so that also required me to fiddle with the files and rename every "parsec" to "parsecd" to get it to work. No clue why this happened since I followed the readme to the letter. Anyway, upon logging in with email and password, there is no "remember me" option anywhere. I can't auto-login if I reboot retropie, and I have to login to parsec every time. What could be the issue?

Error when trying to run the script

Hello!
When I type in "sudo bash setup.sh", this happens

I've checked, and I do have a ports-directory. I have kodi installed in that directory at the moment.
Can you help me?

No directory found

when running setup, I got an error No such file / directory not found. Now my systems.cfg file is gone.

Parsec integration with retroarch

Hi!, can parsec somehow integrate with retroarch ?

README.md still instructs to type in server ID

The read me still tells users to type in their server ID even though this was phased out with #19. Will submit a pull request soon.

New RetroPie releases won't effect es_systems.efg

Per the RetroPie wiki, making Parsec it's own system in RetroPie means the user has to manually update their systems if they ever upgrade their RetroPie version.

This is probably fine for must people, but I think there should at least be a note somewhere in the read me. I'll make a pull requests shortly.

edit: typo

Connection problem.

When I first install and run the setup.sh it connects and runs behind emulationstation. If I exit emulationstation it shows me my desktop. But after 30 seconds it will disconnect. If its already connected via setup.sh I can also hit Parsec in ports option it will show me my desktop for around 10 seconds or so then revert back to emulationstation. When I dont run setup.sh via ssh or command and click Parsec in ports it will not run and connect.
shows me:

App . hostname =retropie
App. local_ip =192.168.0.11

Error: -2001

Then reverts back to emulationstation.

I have clicked it repeatedly and now shows

Error: -18000

Now its back to the first message again.

Hope you can help as this is would be awesome.

Also when I read in the reddit forum about changing moonlight to do this they talked about resolution options. Is there anyway to set different resolutions as I am sure its set to 1080p as my current pc resolution is 720p but when it connects it automatically changes to 1080p even if I change the server resolution on my pc. would be great to be able to set it lower when needed.

Anyway thanks for your work and hope to here someway to resolve my issues.

Server IDs Can Change

I've had my Parsec server ID change a few times now. From my conversations in the Parsec discord, other users have had this happen as well. I've had to re-run the setup script each time to correct this issue.

Will make a pull request with a proposed solution.

Window Failure

I to try use parsec in raspberry pi 4 using retropi 4.6 but when i start the program shows an error .

line 3: warning: here-document at line 1 delimited by end-of-file (wanted `EOFy')
[D 2020-09-30 22:44:33] SDL_CreateWindow=0

[Window Failure]

Parsec could not create the main window.
Please contact us if this problem persists.

No command parsec after install

Describe the bug
Command parsec not found after install

To Reproduce
Steps to reproduce the behavior:

1. After install

Screenshots

Desktop (please complete the following information):

• OS: Linux 4.19.97-v7l+ armv7l GNU/Linux
• Raspberry 4 pi b+

Controller Pass through

Currently I am unable to pass through my controllers from within retropie to Parsec.
Both my host PC and my RPI are using the 150-47 build of parsec.
My Controller is functioning within RetroPie and can be used when selecting my host PC.
Once i am in the host box i cannot seem to control anything or setup my controller on my emulators. It is also not registered within windows once connected either.

I have both the xpad and xbox360 drivers installed on retropie and ViGem on the host.
I'm fairly new to retropie so any tips or tricks will help.