nevermind, i got it working with whiptail, the problem i had was quite easy to fix once i figured out you need to reset the commandline to get rid of the whiptail window (much stuff is pretty new to me, so bear with me 😀)
tho i still struggle with how i should implement some stuff
for example, should i make a default "minimal" config and for more advanced stuff you actually need to go into config files yourself and install stuff yourself
a good example is camilladsp, i could just implement a config file that is just based around routing audio from usb input to output, but it would also be possible to install a webserver that gives you a GUI to alter the camilladsp config, should i leave this to the end user or try to integrate the most featurerich approach? (which would be offering a additional script to install the GUI, which would be still optional but makes the expierence more coherent i would say instead of the user needing to install it by themself)
the thing is.... its one thing to integrate a "minimal" working config (which would be more tailored to my specific use case) but it gets alot more complicated if you try to make it as universal as possible
same story would be MPD, should i integrate it to make it more universal or focus on the minimal approach
tho with MPD it gets even more complicated... to be really happy with MPD i would like to integrate pipewire + carla, which would offer VST Plugin support (some of the best EQ`s i heared since if you use the right plugin it will give you linear phase EQ, crossfeed etc)
the problem with carla is that you need a actual desktop enviroment to make changes, so best is probably to install VNC or something similar so you can actually see the GUI
as you see, if i wanna integrate MPD for example there is a whole chain of things to work on instead of focusing on a minimal approach to connect a PC over the RPI through a hat to the dac and do most things on your desktop PC
as there are no interested people yet i probably have to think a little more on how i implement things in the most universal but easy way possible
tho i still struggle with how i should implement some stuff
for example, should i make a default "minimal" config and for more advanced stuff you actually need to go into config files yourself and install stuff yourself
a good example is camilladsp, i could just implement a config file that is just based around routing audio from usb input to output, but it would also be possible to install a webserver that gives you a GUI to alter the camilladsp config, should i leave this to the end user or try to integrate the most featurerich approach? (which would be offering a additional script to install the GUI, which would be still optional but makes the expierence more coherent i would say instead of the user needing to install it by themself)
the thing is.... its one thing to integrate a "minimal" working config (which would be more tailored to my specific use case) but it gets alot more complicated if you try to make it as universal as possible
same story would be MPD, should i integrate it to make it more universal or focus on the minimal approach
tho with MPD it gets even more complicated... to be really happy with MPD i would like to integrate pipewire + carla, which would offer VST Plugin support (some of the best EQ`s i heared since if you use the right plugin it will give you linear phase EQ, crossfeed etc)
the problem with carla is that you need a actual desktop enviroment to make changes, so best is probably to install VNC or something similar so you can actually see the GUI
as you see, if i wanna integrate MPD for example there is a whole chain of things to work on instead of focusing on a minimal approach to connect a PC over the RPI through a hat to the dac and do most things on your desktop PC
as there are no interested people yet i probably have to think a little more on how i implement things in the most universal but easy way possible
actually i overlooked some things with Carla....same story would be MPD, should i integrate it to make it more universal or focus on the minimal approach
tho with MPD it gets even more complicated... to be really happy with MPD i would like to integrate pipewire + carla, which would offer VST Plugin support (some of the best EQ`s i heared since if you use the right plugin it will give you linear phase EQ, crossfeed etc)
the problem with carla is that you need a actual desktop enviroment to make changes, so best is probably to install VNC or something similar so you can actually see the GUI
as you see, if i wanna integrate MPD for example there is a whole chain of things to work on instead of focusing on a minimal approach to connect a PC over the RPI through a hat to the dac and do most things on your desktop PC
1. "Carla-Control" allows for remote access to the settings (so no need for VNC/desktop enviroment or something similar)
2. Carla supports also ALSA as backend, so no real need for pipewire/jack, tho pipewire or jack would offer some nice network protocols as alternative to usb
i still have to check wether this setup works which i will do in the following days
then its also just one further step to integrate MPD and upnpcli (the upnp plugin for MPD)
UPNP wise, there are not much alternatives to MPD unfortunaly, atleast i found non (or atleast no good ones) that dont rely on a GUI, so MPD plus the plugin is probably our best bet if we wanna integrate UPNP endpoint anyway
---
- one other thing that might some people appreciate would be LMS (or in particular the endpoint of LMS)
---
- then i was thinking about integrating a display / GPIO buttons, this is highly custom and most people wont use it but it would be nice to have it as an option
right now im thinking of integrating like so:
1. a script that lets you control media playback over the command line (play, pause, next, previous, volume up/down) i think this is just useful for MPD, so i might use MPC instead of a script,
aditionally i wanna integrate a "switch mode" script, to switch between Usb input, HqPlayer, Roon, LMS, upnp, MPD, so we can actually turn off each application that is not in use and just turn on the active mode one to keep things still as minimal as possible
2. a script that combines GPIO buttons and the scripts above (or MPC), but its still possible to just use the commandline, so this is optional
3. also optional but i was thinking of integrating a display with a Pico Pi which is connecting either trough serial port or serial over USB, which would easly allow for a "dirty side" on the pi and either use a usb isolator or optocouplers to galvanicly isolate the display/picopi from the raspberry pi but we still get a nice display that shows current mode, mpd media controls, maybe with a rotary endcoder or some buttons and possibly other stuff i come up with to make this somewhat of a full fledged streamer
---
i guess the only things left would be spotify connect and airplay, then we probably have what everyone possibly can ask for
maybe being able to connect a usb cd drive and playback cd`s over MPD might be nice too
what you guys think? too much?
I think that when you use a linear power supply, the transformer provides galvanic isolation.thats not how usb works, either you galvanicly isolate ground or you still need a ground connection to the pc to make usb even connect to the device
I don't mean reclocking a previous usb signal, but using a good clock source and clean power can help the dac sync better, with less noise to the dac chip, less need for filters such as LDO, which add noise of their own.try it yourself or trust me, the data itself is fine(!), there is no real need for reclocking to get "good data" from usb
USB reclockers like a USB isolator is one thing, and a independent usb hub with self power and XO oscillators is another. It creates a good source signal from the computer data bus without any possible power line interference in USB.
Last edited: