- 7. February 2016 at 16:13 #18396
I wish to run the audioplayer Squeezelite with Jivelite skin rendering on the 7″ touchscreen, music being output via the IQuadIO DAC+ while at the same time I wish to run Kodi on my TV with both video/audio output via HDMI.
I can choose HDMI as the output audio device in Kodi, thus ensuring it doesn’t attempt to output via the DAC+: Kodi allows this selection. On the web UI of Max2Play, I can choose IQaudIO DAC+ as the output device for the audioplayer.
However, I cannot get Kodi to render on connected TV while Jivelite renders on 7″ screen. Jivelite stops if I run Kodi, this is an issue, but not a showblocker since if the Squeezeserver is running, I can choose a different client on my smartphone to connect to that server. However, the fact that the sound is not output to both HDMI and the DAC+ simultaneously for the different applications (Kodi and Squeezelite respectively) is a showblocker.
Is it possible to achieve what I’m trying to achieve? If yes, how?
From the Max2Play IQaudIO page:
If Kodi/XBMC is running Squeezelite will be deactivated! This is neccessary to get Audio in Kodi/XBMC working. Kodi/XBMC uses pulseaudio and Squeezelite as well as Shairplay use Alsa to play sounds/music at the same time. When Kodi/XBMC is closed, Squeezelite will start again if it is set to autostart.
Pulseaudio as well as ALSA should be capable of sending sound from different applications to different devices simultaneously I would have thought. No?
I wonder what the use is for a separately running audioplayer or Squeezeserver in that case (other than being lighter on resource usage) as Kodi has all the plugins for the various internet music services or local music collections Squeezeserver can serve, as well as MPD client…the USP of this proposition for me was to be able to listen to music in high quality separately whilst being able to use Kodi for videos on a separate output device simultaneously. Thoughts on this?16. February 2016 at 15:12 #18517
You need to designate two different audio outputs to Squeezelite and Kodi. So since Squeezelite is already activated for use with your DAC+, you need to go into Kodi’s settings (System -> Settings -> System -> Audio Output -> Audio Output Device) and set the audio output to HDMI. That should make them work simultaneously.16. February 2016 at 15:35 #18521
You need to designate two different audio outputs to Squeezelite and Kodi
…which I have done, but Squeezelite stops when I run Kodi. And I cannot get Kodi to display on the TV connected to the HDMI output whilst Jivelite displays on the 7″ display. How to achieve that?
So, is the way to achieve it is that I do not run Jivelite because if I run Jivelite, Jivelite will shut down (taking Squeezlite down with itself?) when I start Kodi? So, do I stop using Jivelite, set the display to duplicate on both 7″ and HDMI (with different resolutions) – how?; and then set Kodi to auto-start upon boot-up? Is this the only way to run Squeezelite and Kodi simultaneously? Is there a way I can have a user interface for Squeezelite on 7″ screen and the Kodi user interface on HDMI, both using different audio devices as mentioned in your reply?
19. February 2016 at 15:22 #18600
- This reply was modified 9 months, 3 weeks ago by m.max2play.
That doesn’t work. Audio outputs are separate and I hear Kodi sounds via HDMI, but even now, when Kodi runs, Audioplayer/Squeezelite stops though Squeezelite is using DAC+.
Kodi also renders on 7″, not HDMI though sound is on HDMI for Kodi. Jivelite (and Squeezelite) pause whilst Kodi is running.
Is there a way for Jivelite/Squeezelite to run simultaneously with Kodi? Ideally for both audio and video, though even the audio is not working at the moment. I want Kodi to render using HDMI and Jivelite to render on 7″.
[UPDATE] Okay, works, kind-of, if I select USB-DAC checkbox. I shouldn’t be selecting that however, because DAC+ is not USB DAC. However, now I cannot connect to Squeezelite using Squeezer app (because there is a port conflict on port 9090 between this and Kodi. Note that I’m not talking about port 8080 control of Kodi, that’s separate and works, this is about port 9090). Also, the problem that Kodi still renders on 7″ still remains (so Jivelite UI is not seen which coupled with the fact I cannot use Squeezer to connect any more if I autostart Kodi, means I cannot now control Squeezelite if I start Kodi, so cannot play audio via it for example if I start Kodi – this problem would be solved if either of Kodi or Squeezelite uses a port other than 9090 (how?) – at least, I would be able to use Squeezer (or other app) to control Squeezelite whilst Kodi is occuyping the 7″ display.
So two problems after both Squeezelite and Kodi have now started running simultaneously after selecting the USB-DAC checkbox:
* Both Kodi and Jivelite want to use 7″. I want Kodi to use HDMI, but video output device is not selectable inside Kodi and I do not know how to get it to render on HDMI and Jivelite on 7″ simultaneously. I do not know if I can use a parameter like
--display 6to start Kodi on the non-default screen (from https://www.raspberrypi.org/blog/the-eagerly-awaited-raspberry-pi-display/ – search for Dual display usage). If it is possible, it would be great to have this parameter available on the max2play web interface.
On a side note, this might be useful for those who want to run Kodi on demand (upon HDMI plug-in), especially if it can then use the parameter mentioned above to start Kodi on the non-default display (for most users, TV/monitor as opposed to the 7″ LCD): https://www.max2play.com/forums/topic/start-stop-kodi-based-on-hdmi-monitor-status/
* Both Kodi and Squeezelite want to use port 9090. I do not know how to make one of them listen on a different port.
[UPDATE] I’m guessing the issue for the port conflict can be addressed by setting a different port for Kodi jsonrpc, http://kodi.wiki/view/Advancedsettings.xml. It would be great if max2play did this automatically if the user chooses to autostart both Squeezelite and Kodi.
<jsonrpc> <compactoutput>true</compactoutput> <tcpport>9999</tcpport> </jsonrpc>
So, until this thing is fixed properly (a.k.a. in a newbie friendly way), my workaround is to:
* Set Squeezelite to DAC+ in Advanced settings
* Set Squeezelite to autostart
* Set Kodi audio output device to HDMI (assuming DAC+ can’t be used in Kodi and Squeezelite both simultaneously)
* Set Kodi jsonrpc to a port other than 9090 (e.g., 9999)
* Set Kodi to autostart
* Set HDMI as default video device using
config.txtfile (from https://www.raspberrypi.org/blog/the-eagerly-awaited-raspberry-pi-display/)
* Forget about using Jivelite interface unless Kodi is exited, but use the Squeezer (or similar) app on my smartphone to control Squeezelite
But once it all falls into place for noobs like me (prameters provided on max2play web-interface, automatically configured as needed, dual display works properly), I’ll no longer default display to HDMI and will use dual display to show Jivelite UI on LCD and Kodi on HDMI connected display (TV/monitor), running all the time.
For those desiring to use DAC for all audio output, who do not have a use-case for playing music and Kodi on different speakers but at the same time, perhaps running Kodi with XSqueeze plugin is a better option?
22. February 2016 at 17:56 #18632
- This reply was modified 9 months, 3 weeks ago by m.max2play.
Thank you for your detailled information.
Indeed, running Kodi and Squeezelite/Jivelite does work with different sound outputs, but not when displayed on the same screen like you described. We will discuss your workarounds and the options to improve the functionality of Max2Play related to this use case.
Maximilian from Max2Play24. February 2016 at 12:28 #18691
you can switch the display on and off in the “Rpi Display” plugin of Max2Play very easily. With setting another port for Kodi like you described, it is a possible workaround. Until today, we have not come across a really good solution for this problem. If anyone knows one, let us know.
The plugin XSqueeze for Kodi makes sense if you use Kodi primarily.
Maximilian from Max2Play
You must be logged in to reply to this topic.