PDA

View Full Version : Announce: Community Squeeze



Triode
2013-04-09, 11:54
14706

Community Squeeze Release

Community Squeeze is a community driven activity to continue the squeezebox open ecosystem and maintain availability of squeezebox compatible players now that Slimdevices/Logitech are no longer active in this market. It targets great audio quality at low cost with full integration to the existing Logitech Media Server based ecosystem.

The project comprises both software and hardware components. The Community Squeeze OS is a Linux based software distribution which includes playback and control applications which enable a squeezebox compatible player to be run on supported hardware. The Community Squeeze Player is a community designed hardware device which will run Community Squeeze OS and will provide a high quality audio playback capability from on-board analog and digital outputs.

Today we are releasing the initial version of the Community Squeeze OS. This is designed to run on a low power hardware device called Wandboard (wandboard.org). This is being made available so early users of Community Squeeze are able to trial the software and work with us to improve its capabilities. This initial release will support playback via the on-board audio output of the Wandboard and via external optical spdif and usb based dacs. The OS will evolve to power the Community Squeeze hardware Player. We will confirm more details of the hardware platform as development continues *.

Release 1.0 of the Community Squeeze OS supports the following features:
- Fedora based linux OS for the Wandboard cpu platform which is available as a download to be flashed to microSD card by the user
- Squeezelite playback application which supports wav, aiff, flac, mp3, ogg, aac using linux codecs and which will playback through the on board audio, spdif and usb ports of the Wandboard. Squeezelite uses existing Squeezebox protocols to integrate with your LMS based music system.
- (Optional) HDMI based user interface for the player which uses the JiveLite application to control the player via a USB connected keyboard or remote using a Flirc adaptor (requires 1080p capable TV/monitor)
- (Optional) Support for the LMS server application running on the Wandboard hardware to avoid requirement for an external server
- Web based configuration for each of the above functions

Download and installation instructions for the OS are provided below.

Please download the OS and let us have your feedback. We would love for additional developers to join the team and help develop the software side of this activity and help support us as we develop the hardware player.

Thank you to all the encouragement on the forums for both this hardware and software sides of this project please continue to comment and suggest ways to improve and support Community Squeeze.

The Community Squeeze team,
[Clive (JackOfAll), John (JohnSwenson), Adrian (Triode)]


* - details of the Community Squeeze hardware platform have already been introduced as part of the discussion on this thread: http://forums.slimdevices.com/showthread.php?97881-Community-Funded-Squeezebox-Replacement-Would-you-be-interested

Triode
2013-04-09, 11:59
Community Squeeze OS for the Wandboard can be downloaded from here:



http://www.communitysqueeze.org/images/wandboard/CSOS/CSOS-Wandboard-Dual-R3-20130412-1.img.7z


Details of how to use this image with a wandboard are available here: http://wandboard.org/images/downloads/wandboard-quick-start-guide.pdf

Technical discussion of Community Squeeze OS and the features of this release has already been happening on the pre-release thread in the linux forums which you may wish to read before posting questions and comments on this specific release (http://forums.slimdevices.com/showthread.php?98190-Plastic-Box-Which-Plays-Noises) and has now transferred to: http://forums.slimdevices.com/showthread.php?98544-Community-Squeeze-OS-R3

However please feel free to post questions in this thread.

We recognise that this initial release is only suited to people willing to configure their own wandboard device, but we have strived to make the installation of Community Squeeze as simple as possible for people feeling happy to download the image, copy it to a microsd card and install in their Wandboard. All subsequent configuration should be possible from the web and hdmi interface. As we upgrade the software components which make up part of Community Squeeze OS we will post here with instructions of how to update. Experienced linux users will be able to update more regularly by updating individual applications and we will post details of this on the linux forum.

bakker_be
2013-04-09, 12:45
I'll post this here too, already posted in the other thread.

Just put R1 on my Wandboard. Web interface for WLAN-configuration didn't seem to do what it needed to do (yes, I did use the "Save and reboot"-button) but I used Putty to ssh in and checked if the settings were correctly applied. ESSID & WPA-PSK key were present, so I did what you describe in the very first post (ifdown + ifup) and WLAN is working now.
Had to google around a bit to find how to mount my Windows share to actually get some music into the server, but now it's happily scanning, Squeezelite is visible on my network and sees both LMS servers, my other players also see the Wandboard server.
So far so good :) All in all a painless installation procedure, well within reach of this Linux almost illiterate ;)
If you need localisation to Dutch or French, I volunteer.

Triode
2013-04-09, 13:05
Community Squeeze OS is designed to work with commerically available hardware. In advance of the Community Squeeze hardware player, this is the Wandboard (http://www.wandboard.org/) which is available via a number of resellers linked from their web page.

If you want to use this as a Squeezebox compatible player using the internal analog or spdif output of the wandboard then this is all you need. If you wish to use an external USB Dac, then the Wandboard has been tested with both UAC1 and UAC2 usb dacs and is able to reproduce good quality audio with this configuration. You should note that for UAC1 dacs an external high speed hub is required between the DAC and Wandboard. This is because the Wandboard hardware has the same limitation as the Squeezebox Touch in terms of it's USB output port. With a hub it performs exactly as the SBT does with the EDO addon.

Community Squeeze also includes a controller appliction which uses the HDMI output to display a squeezebox like display on a high definition monitor or TV. At present this is designed for 1080p resolution screens, although it is possible to make it work on 720p screens and future releases will simplify the configuration to achieve this. The controller application is intended to be driven by a flirc IR receiver (http://flirc.tv/) which allows an IR remote to emulate a USB keyboard. This may be connected directly to the Wandboard or via a USB hub (if you have a usb dac). I'm sure users will find the best configuration for Flirc, but for the moment I've attached my configuration file here for use with an existing Squeezebox IR remote control:
14707

jmschnur
2013-04-09, 14:28
Will IPeng work with is?


J

Triode
2013-04-09, 14:31
Will IPeng work with is?


J

Yes - It's LMS based and will support existing LMS on an external server (as today's squeezeboxes) or on the Wandboard. In both cases all existing LMS control applications will work, including the web interface and iPeng, SqueezePlay, SqueezeCommander etc. [I don't have a full list...]

Pascal Hibon
2013-04-10, 05:41
According to the Wanboard site there are two versions of the hardware available. A Solo and a Dual version. The Dual version also has wifi. Which of these two boards are required for this project?

P Nelson
2013-04-10, 07:26
Consider putting instructions and perhaps a wiki on the communitysqueeze.org website. As this thread becomes numerous pages, and new threads get formed, having a central point of important information very useful.

It's too bad the squeezebox wiki is no longer maintained.

Paul

maggior
2013-04-10, 07:31
What form will the "community hardware" take? Community software projects make sense, but I've never heard of a community hardware project. Will it be a parts list? A kit?

It's interesting to see this little projects taking root. Hopefully one or all of them will take off.

Julf
2013-04-10, 07:52
What form will the "community hardware" take? Community software projects make sense, but I've never heard of a community hardware project. Will it be a parts list? A kit?

Wikipedia: Open Source Hardware (http://en.wikipedia.org/wiki/Open-source_hardware)

asplundj
2013-04-10, 08:20
Maggior: http://forums.slimdevices.com/showthread.php?97881-Community-Funded-Squeezebox-Replacement-Would-you-be-interested

maggior
2013-04-10, 08:48
I read through some of that thread and the wiki article was interesting.

Perhaps I missed in in the 79 pages of posts, but are there plans for how this hardware will be disceminated? I see where John was soldering components to a PCB. Has somebody signed up to mass produce the hardware?

garym
2013-04-10, 09:16
I read through some of that thread and the wiki article was interesting.

Perhaps I missed in in the 79 pages of posts, but are there plans for how this hardware will be disceminated? I see where John was soldering copmonents to a PCB. Has somebody signed up to mass produce the hardware?

I think right now they are just on Generation 1 for a few beta testers. Gen 2 (or later) is where some sort of assembly approach for non-DIY folks would be involved.

froth
2013-04-10, 09:29
So is this different to what the ick squeeze post that pippen posted? Or is it complementary? Or is it compitision?

It all confusing to me.

garym
2013-04-10, 09:33
So is this different to what the ick squeeze post that pippen posted? Or is it complementary? Or is it compitision?

It all confusing to me.

My understanding: community squeeze is an "operating system" that can be installed on hardware to emulate a squeezebox player. The ickStream stuff could work with hardware runnign community squeeze, real SB hardware players, and it seems other non-SB music players. So they are not in competition. They can co-exist nicely it seems.

Marsupial
2013-04-10, 09:36
Can the community squeeze OS run on other hardware?

garym
2013-04-10, 09:52
Can the community squeeze OS run on other hardware?

yes, but currently it seems they are testing on one specific hardware configuration. But ultimately, I believe the idea is that it could run on different hardware. But one might be on their own to make it run on non-tested/supported hardware.

Furry
2013-04-10, 11:04
As a potential 'early user', I have a couple of questions:

1. Is it likely that the Wandboard will persist, as the preferred hardware platform?

2. If it doesn't persist, then is it likely that the Wandboard will (also) be supported for future software releases?

tcutting
2013-04-10, 11:22
As a potential 'early user', I have a couple of questions:

1. Is it likely that the Wandboard will persist, as the preferred hardware platform?

2. If it doesn't persist, then is it likely that the Wandboard will (also) be supported for future software releases?

My understanding is the Wandboard is planned to be the base hardware platform as it provides all the key infrastructure, allowing John S to focus on the specific audio hardware [DAC, clocks, buffers, DSP]

Sent from my DROID RAZR using Tapatalk 2

JackOfAll
2013-04-10, 11:43
As a potential 'early user', I have a couple of questions:

1. Is it likely that the Wandboard will persist, as the preferred hardware platform?

2. If it doesn't persist, then is it likely that the Wandboard will (also) be supported for future software releases?

The Wandboard Dual is the preferred hardware platform. This will not change. The JS DAC carrier board has been designed to work with the Wandboard and its EDM connector. If you wish to use the JS designed DAC carrier board when it becomes available, it will only work with the Wandboard.

However, if you plan to use an external USB DAC it is likely, (but there are no promises), that there will a CSOS release available for several Cortex A8/A9 platforms. At the present time, there is a Wandboard image. It is the only released image. But I also run CSOS on the Beaglebone. Castalla runs a Fedora 18 derivative on the Cubieboard. So I believe there are several boards we could support, if we have the time and resources to do so.

TheShanMan
2013-04-10, 11:47
I'm interested to see where this goes. I'm probably not interested in a stand alone server though. I hope that this effort will ultimately include a future for squeezeserver running on windows, support for older clients (I have a slimp3 and an SB1), and support for Pandora that doesn't time out (the main reason I still use my players). Even though I've never been one to buy the latest and greatest squeezebox, I am interested to see what comes of a community client project.

JackOfAll
2013-04-10, 11:52
So is this different to what the ick squeeze post that pippen posted? Or is it complementary? Or is it compitision?

It all confusing to me.

Yes, it is confusing. Community Squeeze is about supporting LMS, the Squeezelite software player, and a Community Based hardware player, either with or without the JS designed DAC carrier board.

ickstream from what info has been given, is a cloud based music delivery platform. Their client API is not based on how an LMS client currently talks to the LMS server. Possibly the Touch could have a applet that connected directly back to the ickstream cloud for music delivery. I assume you would have to purchase some sort of subscription from ickstream, but I don't really know as they haven't released a great deal of info. I expect that the Community Squeeze hardware player could have functionailty built into squeezelite, to connect directly to the ickstream API for music delivery from the cloud. But I'm guessing. Having not signed their NDA, I only know as much as you do, from what has been publicly posted in the pre-announcement thread.

JackOfAll
2013-04-10, 11:57
Perhaps I missed in in the 79 pages of posts, but are there plans for how this hardware will be disceminated? I see where John was soldering components to a PCB. Has somebody signed up to mass produce the hardware?

Another announcement will be made, specifically concerning how the fully built boards will be made available to end users, and how you register your interest in purchasing a board, so we have a good idea of how many we need to produce for the first GEN 2 (public) production run, in the near future.

Mark Miksis
2013-04-10, 12:06
The Wandboard Dual is the preferred hardware platform. This will not change. The JS DAC carrier board has been designed to work with the Wandboard and its EDM connector. If you wish to use the JS designed DAC carrier board when it becomes available, it will only work with the Wandboard.

However, if you plan to use an external USB DAC it is likely, (but there are no promises), that there will a CSOS release available for several Cortex A8/A9 platforms. At the present time, there is a Wandboard image. It is the only released image. But I also run CSOS on the Beaglebone. Castalla runs a Fedora 18 derivative on the Cubieboard. So I believe there are several boards we could support, if we have the time and resources to do so.

The Wandboard seems like overkill for those of us not wanting to run LMS on the player. There will probably be less expensive player-only solutions, especially if the Raspberry Pi ever gets their USB drivers fixed.

maggior
2013-04-10, 12:07
Thank you John, that clears it up for me.

Interesting developments on multiple fronts here.

JackOfAll
2013-04-10, 12:11
I hope that this effort will ultimately include a future for squeezeserver running on windows, support for older clients....

The thing is this...... It's a community project, by the community, for the community. It is going to depend on more people from the community getting involved. The people that are involved so far on the development side, can only do so much.

JackOfAll
2013-04-10, 12:17
The Wandboard seems like overkill for those of us not wanting to run LMS on the player. There will probably be less expensive player-only solutions, especially if the Raspberry Pi ever gets their USB drivers fixed.

And you are more than welcome to use another solution. I have a drawer full of ARM hardware, that I have fiddled with for a week, then discarded for various reasons. I haven't found an achilles heel with the Wandboard yet, even if it is overkill for for a simple client player. (And I seriously doubt the Pi will ever be 100% in the USB department, or that any driver "enhancement" will magically solve the issue with the latency that causes the dropped USB packets.) For the cheapest solution possible, the Pogoplug seems to be the best bet, (depending on where in the world you can purchase it from), with an external USB DAC, but not something I've used personally so I'm hesitant to recommend it.

TheShanMan
2013-04-10, 12:35
The thing is this...... It's a community project, by the community, for the community. It is going to depend on more people from the community getting involved. The people that are involved so far on the development side, can only do so much.

Totally understood. I may be able to get involved on a limited scale (I'm a software engineer with a degree in EE that's been covered by years of dust), and also may be willing to donate. I'll take your response as meaning that there is intention and desire to do what I'm hoping for, and that's good enough for me at this point!

JohnSwenson
2013-04-10, 12:46
The wandboard consists of two pieces, a cpu module and a carrier board that has the peripheral interfaces. The module uses an emerging standard (the EDM standard) which several companies are supporting. We are currently using the wandboard in its entirety because it is functional as is. What I am developing is a carrier board with high quality audio hardware built in. Wandbord has announced that they will be offering the modules separately in the future, but are not currently doing so.

Because it is a standard interface, there should eventually be several modules that will work with my carrier board.

For the hardware beta test phase the users will need to buy a wandboard, remove the cpu module from its carrier board (4 screws) and attach it to my carrier board. The assumption is that when the full release is ready (what I have been calling Gen2) the modules will be available separately. Exactly how it's going to happen, exactly how things are packaged etc is still being worked out. But this "take it off one board and put it on the other" will NOT be part of the full release.

If all you want is something to plug in a USB DAC then the current wandboard is all you need.

John S.

Triode
2013-04-10, 12:51
And you are more than welcome to use another solution. I have a drawer full of ARM hardware, that I have fiddled with for a week, then discarded for various reasons. I haven't found an achilles heel with the Wandboard yet, even if it is overkill for for a simple client player. (And I seriously doubt the Pi will ever be 100% in the USB department, or than any driver "enhancement" will magically solve the issue with the latency that causes the dropped USB packets.) For the cheapest solution possible, the Pogoplug seems to be the best bet, but not something I've used personally so I'm hesitant to recommend it.

To add to this - we specifically picked the Wandboard for two reasons (and you can see some agonising on this on the thread re hardware):
1) We know it supports USB Dacs well as it has hardware ehci based scheduling. Other platforms such as Beaglebone and Pi have serious limitations in this respect and I would not want to hold out hope that Pi ever fixes high speeds iso transfers.
2) The CPU on a module approach makes it much easier and faster for John to produce the hardware design, concentrating on the audio engineering not the processor/memory etc.

So yes if we looked for a lowest cost cpu platform we could have picked something else, but we picked the Wandboard to get us good flexibility and good performance which we believe is most important for this project. That said the software will run on other platforms and there are many people running it on Pi already (in cases where the usb problems don't cause concerns)

Mark Miksis
2013-04-10, 13:03
To add to this - we specifically picked the Wandboard for two reasons (and you can see some agonising on this on the thread re hardware):
1) We know it supports USB Dacs well as it has hardware ehci based scheduling. Other platforms such as Beaglebone and Pi have serious limitations in this respect and I would not want to hold out hope that Pi ever fixes high speeds iso transfers.
2) The CPU on a module approach makes it much easier and faster for John to produce the hardware design, concentrating on the audio engineering not the processor/memory etc.

So yes if we looked for a lowest cost cpu platform we could have picked something else, but we picked the Wandboard to get us good flexibility and good performance which we believe is most important for this project. That said the software will run on other platforms and there are many people running it on Pi already (in cases where the usb problems don't cause concerns)

Understood. Thanks for the info.

pippin
2013-04-10, 18:18
ickstream from what info has been given, is a cloud based music delivery platform. Their client API is not based on how an LMS client currently talks to the LMS server. Possibly the Touch could have a applet that connected directly back to the ickstream cloud for music delivery.

Just to make this clear in case our statements so far have been ambiguous and to avoid misunderstandings: ickStream is NOT a streaming service and you will NOT have to use any cloud service to stream music from your local computer or server. ickStream does - among other things - provide a cloud service to enable use of online music sources.
It will also use a cloud service for convenience functionality like configuration, authorization and device management as well as unified access to some functionality (for example favorites) for people who do not want to run a server 24/7.
But it will not require a permanent online connection to play your own stuff.

Yes, our devices and servers don't talk to each other like Squeezeboxes and LMS do. And one of the driving motivations for this was that - unlike the MySqueezebox.com or UE Smart Radio solutions - we do not want a player to be completely controlled by an online service in case you do not run a server 24/7 in your home. And I know from personal user feedback just how many people do not want that. Logitech knows this, too, it's why they made the change with the Smart Radio.



I assume you would have to purchase some sort of subscription from ickstream, but I don't really know as they haven't released a great deal of info.

Which is mainly because we don't know all of the details ourselves, yet.
Some of the features we want to provide to users will probably not be free for us, too. You'd probably be surprised for how much of the functionality that comes for "free" with LMS Logitech actually pays money.
And yes, the operation of our service will obviously have to be paid for, too. Such is life. But I believe it's in the very interest of users, that a provider sees them as their customers. Customers have a power to decide whether they like a product or not and whether they want to use it or not. They are not dependent on the goodwill of a company who has sold them a product a long time ago and for which they are now just a cost factor. The latter is something that has haunted this industry a lot. Logitech is actually still a pretty user friendly case - after all they have not discontinued anything yet and do still promise to keep around their infrastructure. Try to get software updates for a 2 year old model of your other favorite mainstream HiFi brand's device to make it compatible with a new service and you know how it feels to not be in their core business.

As to comparing ickStream and Community Squeeze: IMHO they are focusing on different things. My understanding is that Community Squeeze wants to provide a software framework on which LMS can be run and that provides a Squeezebox compatible software player solution for the Community Squeeze hardware or other hardware devices that can be used as a player or server. With other words: they want to enable you to build your DIY Squeezebox.

ickStream aims to provide a software and service framework to allow easy use of online and local music sources and make the use of streaming devices easy and accessible. This framework shall enable commercial vendors or non-commercial developers to focus on the products they are good at building without having to develop and operate the whole system for themselves and hopefully allow users to mix and match devices from different providers.
A lot of people have been looking for a "standard" (like UPnP) to allow different devices to interoperate but as things stand, only the lowest possible denominator ever has been agreed upon and actually implemented on most devices resulting in notoriously bad products. This problem is what we want to overcome.

I don't exactly know whether the Community Squeeze software platform and specifically SqueezeLite will be open enough and have APIs to add 3rd party contributions like ours but since it's building on the Squeezebox legacy I assume it will allow Applets or something like that, too, and LMS of course already has the capability to build plugins for it so I hope a coexistence and integration will be easy.

Corelli45
2013-04-10, 23:03
I I'm sorry if this is a silly question but I'm trying to weigh up the options here. Will the Community Squeeze OS ever be able to run on a Squeezebox Touch?

marflao
2013-04-11, 00:22
Hi everybody,

as far as I understood it the wandboard could be used as an altenative or substitute streaming device for a SB device (pls correct me if Im wrong).

So lets assume my beloved Touch will go to the happy hunting ground would I then be able to play my music - which is stored on a Syno NAS - via the wandboard (which would be connected to my DAC via Spdif cable)?

If the answer would be "Yes" is there a limitiation regarding the bitrates (e. g. flacs > 24/96 wont be played)?
Any other restraints I should keep in mind?

Thanks in advance for your feedback.

Cheers,
marflao

JackOfAll
2013-04-11, 02:23
I I'm sorry if this is a silly question but I'm trying to weigh up the options here. Will the Community Squeeze OS ever be able to run on a Squeezebox Touch?

The short answer is no. Providing a release of CSOS that would run on the Touch is not something we intend to do. Which is not to say that at some point in the future there couldn't be a community released firmware (OS) for the Touch, but I see that as being unlikely, unless there is a compelling reason to do so.

JackOfAll
2013-04-11, 02:35
as far as I understood it the wandboard could be used as an altenative or substitute streaming device for a SB device (pls correct me if Im wrong).

Correct!



So lets assume my beloved Touch will go to the happy hunting ground would I then be able to play my music - which is stored on a Syno NAS - via the wandboard (which would be connected to my DAC via Spdif cable)?

Right now, before the John Swenson DAC board is released which will have an electrical SPDIF output, the default Wandboard carrier board has a TOSLINK out, but does not have a COAX SPDIF out.



If the answer would be "Yes" is there a limitiation regarding the bitrates (e. g. flacs > 24/96 wont be played)?
Any other restraints I should keep in mind?


The current audio (software) driver limits the output from the TOSLINK to 48k. But if you wanted an electrical SPDIF out prior to the release of the JS DAC carrier board, there are plenty of options for USB to SPDIF converters that you could plug into the Wandboard USB port, so you would be able to hook up your current DAC via electrical SPDIF and depending on the converter you chose, it would support higher sample rates.

mintaudio
2013-04-11, 04:14
The musical fidelity vlink2 will work nicely with most modern linux distros (so should be fine on the Fedora used in Community Squeeaze) as an asynch USB to SPDIF adapter.

You can use the M2tech Hiface but you need to build the driver for it - https://github.com/panicking/snd-usb-asyncaudio/wiki

marflao
2013-04-11, 04:26
Correct!



Right now, before the John Swenson DAC board is released which will have an electrical SPDIF output, the default Wandboard carrier board has a TOSLINK out, but does not have a COAX SPDIF out.



The current audio (software) driver limits the output from the TOSLINK to 48k. But if you wanted an electrical SPDIF out prior to the release of the JS DAC carrier board, there are plenty of options for USB to SPDIF converters that you could plug into the Wandboard USB port, so you would be able to hook up your current DAC via electrical SPDIF and depending on the converter you chose, it would support higher sample rates.

Thanks for the quick reply. I really appreciate that!!

Cheers,
marflao

Triode
2013-04-11, 12:34
The short answer is no. Providing a release of CSOS that would run on the Touch is not something we intend to do. Which is not to say that at some point in the future there couldn't be a community released firmware (OS) for the Touch, but I see that as being unlikely, unless there is a compelling reason to do so.

Let me add to this - I don't see any need for this at present. Community Squeeze is designed to enable new players to be able to do similar things to the Squeezebox Touch and enable them to fully integrate with an LMS based system with a local LMS server either running on an existing server or as part of Community Squeeze. That is our target is to be able to support local server based playback. If at some point in the future there is a reason why existing Squeezebox Touch devices lose functionality then we could consider what subset of the solution is worthwhile to implement on the Touch (its already one of my development test targets, but only to prove that I can match what it does for playback..)

Furry
2013-04-12, 09:19
The wandboard consists of two pieces, a cpu module and a carrier board that has the peripheral interfaces. The module uses an emerging standard (the EDM standard) which several companies are supporting. We are currently using the wandboard in its entirety because it is functional as is. What I am developing is a carrier board with high quality audio hardware built in. Wandbord has announced that they will be offering the modules separately in the future, but are not currently doing so.

I think, then, that I will wait, before purchasing a Wandboard, until the cpu module is available either without its 'standard' carrier board, or together with your own audio carrier board, and/or if your carrier board is also available separately - do you think you will supply your carrier board on its own, without a cpu attached?

Although at least one of the Wandboard suppliers seems to imply that they would provide the cpu module separately, if they were requested to, I suspect that they wouldn't supply one-offs.

HumanMedia
2013-04-15, 18:33
I have a dream that LMS supports Dop (DSD in a PCM wrapper) and that Community Squeeze supported it also for USB output. Then I would only need one audio player, no laptops, no Mac minis, no cd or sacd players and no more SBT.

How I wish it were more than a dream.

JackOfAll
2013-04-15, 19:16
I have a dream that LMS supports Dop (DSD in a PCM wrapper) and that Community Squeeze supported it also for USB output. Then I would only need one audio player, no laptops, no Mac minis, no cd or sacd players and no more SBT.

Code is done. It's been done for some time, but pushed to one side because I have spent so much time on the CS project. Merging the code changes back to Logitech git for the standard fedora package is a higher priority on the list. DSD support will not be made a part of the CS LMS release until that is done. Timeframe..... It's not top priority. Having a stable Wandboard and fully working PCM functionality on that is a higher priority than DSD support.

albertone74
2013-04-16, 10:59
Hi Triode,

I have got a FLIRC device today. As I would like to use the SBT IR remote control, can you please let me know how I can use this file

CommunitySqueeze Flirc Configuration.zip

that you are referring to, in post #4?

Many thanks.

albertone74
2013-04-16, 11:54
Hi Triode,

I have got a FLIRC device today. As I would like to use the SBT IR remote control, can you please let me know how I can use this file

CommunitySqueeze Flirc Configuration.zip

that you are referring to, in post #4?

Many thanks.

Triode,

It is working! I have just followed the FLIRC instructions on my laptop screen. It is soooo nice with jivelite :)

kesa32
2013-05-01, 22:32
Hi ,l'll be interested in Gen2 when it is released ( i could go Gen1 now , but my USB Dac is'nt as good as John's , so i'll wait for the final product l reckon )

Chunkywizard
2013-05-06, 08:26
Hi ,l'll be interested in Gen2 when it is released ( i could go Gen1 now , but my USB Dac is'nt as good as John's , so i'll wait for the final product l reckon )

Gen1 doesn't exist yet either ;-D See the FAQ for details, but John is working on a board called SWAMP05 at the moment to prove the concept and test the DAC.

HTH

CW

kesa32
2013-05-07, 02:26
Hi , l'm in no hurry really , l was considering the olive but l reckon this'll be more what l'm after :)

jemhayward
2014-03-31, 07:57
I have now got my Wandboard and have installed CommunitySqueeze and once I'd deleted the ALSA parameters, it plays though my Audiolab MDAC via a hub, and sounds great, BUT although it will play 24/96 files, it seems to be coming out as 24bit 44.1kHz.

I'm not sure where I set the max sample rate. Can anyone advise?

JackOfAll
2014-03-31, 15:44
I have now got my Wandboard and have installed CommunitySqueeze and once I'd deleted the ALSA parameters, it plays though my Audiolab MDAC via a hub, and sounds great, BUT although it will play 24/96 files, it seems to be coming out as 24bit 44.1kHz.

I'm not sure where I set the max sample rate. Can anyone advise?

Please repost in the Community Squeeze OS F19 Release 1 (http://forums.slimdevices.com/showthread.php?99395-Community-Squeeze-OS-F19-Release-1) thread. (Which is where support is provided.)