Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #132 - remove hardcoded play commands #148

Closed
wants to merge 1 commit into from

Conversation

krisgesling
Copy link
Contributor

Removes hardcoded play commands from Picroft. These were added as a work around for issues many moons ago. It is believed that these no longer exist in Debian Buster.

Fixes #132

How to test this PR

  • It would be helpful if anyone running Picroft could remove these lines from their system config, reboot, and verify that output continues as expected. Please comment on this PR with your findings good or bad including the audio devices you are using.

  • signed a CLA (Contributor Licensing Agreement)

@fermulator
Copy link

Results:

  • "2020-11-02", "Raspberry Pi 3 Model B Plus Rev 1.3", "20.8.0", "Buster Keaton - Pork Pi"
  • Audio: Andrea Electronics C1-1028100-3 08a8:0016 (using USB Dongle mic array & Speaker 3.5mm jacks)
  • edit /etc/mycroft/mycroft.conf, remove play* lines, reboot
  • VERIFIED ✔️ system still works

@fermulator
Copy link

fermulator commented Nov 24, 2020

As per noted from sgee https://chat.mycroft.ai/community/pl/wrk6x1som3bu8kebcn9rphzx6r, there are a lot of further complexities here I don't know how to handle

Namely:

echo "HARDWARE SETUP"

Perhaps it is fine to remove from this file (hard coded crap), and let the auto_run.sh continue to do what it does? (but then the sed commands wouldn't work :( )

@krisgesling
Copy link
Contributor Author

Maybe we wait and review sgee's large refactor of these scripts first. I think there's a lot of improvement possible here including moving away from sed to a more purposeful tool like jq.

@krisgesling krisgesling closed this Dec 1, 2020
@SilvanCodes
Copy link

It would be really super duper cool for this fix to land, I fell on my face twice setting up two Picrofts as the "bug" shows itself possibly very differently.

The first time I almost lost my sanity because Mycroft just wouldn't say anything as the hardcoded device did not match mine. I messed with way to many config files in the entire linux audio stack until figuring that out.

The second time around it seemed like Mycroft could not adjust it's volume. I saw it moving the pluseaudio master volume up and down, it just had no effect. In the end it turned out that Mycroft was bypassing pulseaudio by having the device hardcoded in that system config file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Confusing scripts and hardcoded device ids
3 participants