1 | So, you want to develop gutenbach, eh? Good! |
---|
2 | |
---|
3 | Gutenbach is a distributed music player built on top of CUPs. It |
---|
4 | essentially enables anybody with access to it to play music from their |
---|
5 | own computer -- all they have to do is "print" to the Gutenbach |
---|
6 | instance as they would any other document! |
---|
7 | |
---|
8 | The current repositories for various Gutenbach features are: |
---|
9 | - gutenbach |
---|
10 | - gutenbach-queue |
---|
11 | - gutenbach-remctl |
---|
12 | - gutenbach-rhythmbox-plugin |
---|
13 | - gutenbach-itunes-plugin |
---|
14 | - gutenbach-web |
---|
15 | |
---|
16 | All of these are located on GitHub: |
---|
17 | http://github.com/search?langOverride=&q=gutenbach&repo=&start_value=1&type=Repositories |
---|
18 | |
---|
19 | Additionally, see README.old for how Gutenbach /used/ to be installed. |
---|
20 | This can sometimes offer insight into how to fix things that are |
---|
21 | broken. |
---|
22 | |
---|
23 | Questions or comments should be directed at gutenbach@mit.edu |
---|
24 | |
---|
25 | NOTES: |
---|
26 | |
---|
27 | - If you keep getting zephyrs with the following errors: |
---|
28 | |
---|
29 | Playback completed with the following errors: |
---|
30 | bt_audio_service_open: connect() failed: Connection refused (111) |
---|
31 | bt_audio_service_open: connect() failed: Connection refused (111) |
---|
32 | bt_audio_service_open: connect() failed: Connection refused (111) |
---|
33 | |
---|
34 | This is because you have alsa configured for bluetooth, but bluetooth is not |
---|
35 | enabled. You should either enable bluetooth, or uninstall the bluez-alsa |
---|
36 | package. |
---|
37 | |
---|
38 | - To print to a machine without keytabs, you need to do: |
---|
39 | |
---|
40 | lpr -Pprintername -Hhostname $file |
---|
41 | |
---|
42 | The old `lpr -Pprintername@hostname $file` syntax will no longer work. |
---|
43 | |
---|
44 | TODO: |
---|
45 | - include mixer and channel in debconf, or even better, move it to |
---|
46 | gutenbach-remctl and implement debconf in that package |
---|
47 | |
---|
48 | - the filter should die and send an error message if it can't find the |
---|
49 | config file, not use defaults |
---|
50 | |
---|
51 | - this should really not conflict with pulse (the biggest problem at the moment is that |
---|
52 | pulse will spew a bunch of errors like "Home directory /var/spool/cups/tmp not ours." I |
---|
53 | can't figure out how to get rid of them, but they're really annoying. As long as pulse |
---|
54 | is in system mode, things seem to work otherwise.) |
---|
55 | |
---|
56 | - CUPS issues |
---|
57 | * the CUPS daemon processes do not inherit groups from the lp user (so, for example, |
---|
58 | even if we add 'lp' to 'audio', the process will not be running in group 'audio'). |
---|
59 | For the time being, I've set the CUPS daemon to always run under group 'audio', |
---|
60 | but there should really be a better solution. |
---|
61 | * debathena printer configuration defaults to using ipp, e.g.: |
---|
62 | jhamrick@lemon-meringue:~$ lpstat -v sipbmp3 |
---|
63 | device for sipbmp3: ipp://zsr.mit.edu:631/printers/sipbmp3 |
---|
64 | so you can't just do `lpq -Psipbmp3`, you have to use `lpq -Psipbmp3 -hzsr` or |
---|
65 | something similar. Same thing goes with lprm. It is interesting that this is |
---|
66 | only the case with lpq and lprm, though, and lpr Just Works. This shouldn't be |
---|
67 | an issue on non-debathena machines. |
---|
68 | |
---|
69 | - Create wrapper scripts for queuing/dequeuing jobs? Making it easier to use across |
---|
70 | multiple platforms, regardless of debathena/normal linux/etc? |
---|