This is a Civilized Place for Public Discussion
Please treat this discussion forum with the same respect you would a public park. We, too, are a shared community resource — a place to share skills, knowledge and interests through ongoing conversation.
These are not hard and fast rules, merely guidelines to aid the human judgment of our community and keep this a clean and well-lighted place for civilized public discourse.
Improve the Discussion
Help us make this a great place for discussion by always working to improve the discussion in some way, however small. If you are not sure your post adds to the conversation, think over what you want to say and try again later.
The topics discussed here matter to us, and we want you to act as if they matter to you, too. Be respectful of the topics and the people discussing them, even if you disagree with some of what is being said.
One way to improve the discussion is by discovering ones that are already happening. Spend time browsing the topics here before replying or starting your own, and you’ll have a better chance of meeting others who share your interests.
Be Agreeable, Even When You Disagree
You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Please avoid:
- Ad hominem attacks
- Responding to a post’s tone instead of its actual content
- Knee-jerk contradiction
Instead, provide reasoned counter-arguments that improve the conversation.
Your Participation Counts
The conversations we have here set the tone for every new arrival. Help us influence the future of this community by choosing to engage in discussions that make this forum an interesting place to be — and avoiding those that do not.
Discourse provides tools that enable the community to collectively identify the best (and worst) contributions: bookmarks, likes, flags, replies, edits, and so forth. Use these tools to improve your own experience, and everyone else’s, too.
Let’s leave our community better than we found it.
If You See a Problem, Flag It
Moderators have special authority; they are responsible for this forum. But so are you. With your help, moderators can be community facilitators, not just janitors or police.
When you see bad behavior, don’t reply. It encourages the bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. Just flag it. If enough flags accrue, action will be taken, either automatically or by moderator intervention.
In order to maintain our community, moderators reserve the right to remove any content and any user account for any reason at any time. Moderators do not preview new posts; the moderators and site operators take no responsibility for any content posted by the community.
Always Be Civil
Nothing sabotages a healthy conversation like rudeness:
- Be civil. Don’t post anything that a reasonable person would consider offensive, abusive, or hate speech.
- Keep it clean. Don’t post anything obscene or sexually explicit.
- Respect each other. Don’t harass or grief anyone, impersonate people, or expose their private information.
- Respect our forum. Don’t post spam or otherwise vandalize the forum.
These are not concrete terms with precise definitions — avoid even the appearance of any of these things. If you’re unsure, ask yourself how you would feel if your post was featured on the front page of the New York Times.
This is a public forum, and search engines index these discussions. Keep the language, links, and images safe for family and friends.
Keep It Tidy
Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:
- Don’t start a topic in the wrong category.
- Don’t cross-post the same thing in multiple topics.
- Don’t post no-content replies.
- Don’t divert a topic by changing it midstream.
- Don’t sign your posts — every post has your profile information attached to it.
Rather than posting “+1” or “Agreed”, use the Like button. Rather than taking an existing topic in a radically different direction, use Reply as a Linked Topic.
Post Only Your Own Stuff
You may not post anything digital that belongs to someone else without permission. You may not post descriptions of, links to, or methods for stealing someone’s intellectual property (software, video, audio, images), or for breaking any other law.
Powered by You
This site is operated by your friendly local staff and you, the community. If you have any further questions about how things should work here, open a new topic in the site feedback category and let’s discuss! If there’s a critical or urgent issue that can’t be handled by a meta topic or flag, contact us via the staff page.
Terms of Service
Yes, legalese is boring, but we must protect ourselves – and by extension, you and your data – against unfriendly folks. We have a Terms of Service describing your (and our) behavior and rights related to content, privacy, and laws. To use this service, you must agree to abide by our TOS.
Why is the forum’s title ‘The unofficial Arcam SA30 community’?
In order to state this is a community forum rather than an official Arcam/Harman forum.
Why is this forum created?
After purchasing a Arcam SA30 amplifier I noticed some things were not working as expected. At that time there was not much information available on the internet besides marketing introduction announcements and one or two reviews. In order to exchange information with other SA30 owners this forum was set up.
Is this forum dedicated to Arcam SA30?
What information can I post?
In general technical questions related to the software of the SA30, e.g. questions related to the firmware, MusicLife and Arcam Connect support applications can be posted. You can also post technical issues you encounter or your thoughts on how current functionality work/ should work.
If questions tend to be more non technical (e.g. is it possible to use SA30 with product ABC) then it might be better to address these questions through the official product support at email@example.com. The support team usually handles this, as not only are they better communicators, they are usually clearer with regard to the bigger picture.
I have a so called ‘non-technical’-question. Why should I address this through formal support instead of asking in this forum?
All questions are relayed to one of the Arcam developers. This person tries to answer questions, but sometimes the risk passing on incorrect information is higher than the benefit it gives from this person weighing in on topics. The support team usually handles this, as not only are they better communicators, they are usually clearer with regard to the bigger picture. I hope you understand.
How can I contribute?
Just create a new topic in the proper category, refer to the category description in order to find out what the category is about.
I use other means to find the information I need, why should I post on this forum?
You don’t have to post here. If you find information in this forum you can use then please use it. If you’re a SA30 owner and are willing to exchange hands on experience then please do so by creating a topic.
I send all my issues straight to Arcam support, why should I post on this forum?
You don’t have to post here. If you encounter issues and you’re happy with your current way of solving issues then don’t change it. The advantage of posting on this forum is other SA30 owners might benefit from it.
Is the information posted on the forum relayed to Arcam?
Yes, information will be brought under the attention of the Arcam development team. The only precondition for relaying issues is that the issue is reproducible. Of cause not all issues can be reproduced 100%, in general it should be reproducible.
If I post an issue is there any guarantee it will be addressed in a future software version?
No, information will be relayed only. No priority nor guarantee can be given if and when issues are addressed in future versions.
Why does the issue template contain weird words like scenario, expected and actual result?
A strict issue format helps to reproduce issues efficiently, scenario describes the steps you executed, actual result contains the result you see after executing the steps. Expected result speaks for it self.