Enhancement of Sound-Devices.md #136#169
Enhancement of Sound-Devices.md #136#169gegeweb wants to merge 8 commits intojamulussoftware:changesfrom
Conversation
|
Thanks @gegeweb! The site is much more structured now. Besides that: could you please remove the french translation and re-submit it once this site goes live? This allows us to have a clear diff for translators. Furthermore, I think we should indeed add a few statements to the Getting-Started page which says that a device must support 48000Hz Sampling rate and on Windows it's recommended to chose a device with a native ASIO-driver. |
wiki/en/en-Sound-Devices.md
Outdated
| _**Note**: depends on how the device works on your system (Linux, MacOS, Windows, etc.)_. | ||
|
|
||
| ### Known to Work with Jamulus | ||
| You can update it with the information you have. **Please indicate the platform(s) you are using!**. |
There was a problem hiding this comment.
Are you sure that we want this here? Wouldn't it be better in the upcoming knowledge base? But it would spread information.
Furthermore the user wouldn't know how to add anything
There was a problem hiding this comment.
I don't know what si the best to have information from the users. Comunity page? Issue? Forum?
There was a problem hiding this comment.
I'd suggest to get the information via the forum (but we could also use an issue here)
There was a problem hiding this comment.
OK, we link to the forum?
Or we remove this sentence?
There was a problem hiding this comment.
I'd suggest to add a link to the forum. But let's wait for some other comments.
Yes, I aggree. |
gegeweb
changed the title
My own opinion is that since I would expect a list of devices to be infinitely long and require constant updating, then maintaining that is a job for "community" really. In contrast, anything we put on the "official" site we commit to being as accurate as possible. But from an SEO point of view it doesn't matter :-) |
|
My opinion is that this page should be on the Community database since it'd require a very big amount of time to make it a high level of trustiness for the reader. Better to put it on the community database with a kind of disclaimer like the following:
|
|
Ok. So do we all agree that this file should be part of the KB then? |
I'd say that we should keep some sort of general guidelines in the manual (ie: use a soundcard supporting 48khz, ...etc) and we should put the user experiences feedback (ie: "I'm using the HIGH-PRO-AUDIO model VERY-NICE-MK2 on Linux Tribichi version 10.2.354 with a 5.9.0 low latency kernel with success") on the Community Knowledge Database. |
Have a look at the getting started md file on changes. There's some generic information now. We can also add it to the manual, if you like. |
|
That looks perfect as it is on change's Getting-Started.md |
|
I've now moved it to the knowledge base. |
|
I've now restructured the page even more. I'm not yet totally ok with the layout and style, but it works. |
|
We might use <details markdown="1">
<summary markdown="1">To clarify the page structure. |
4 participants
No description provided.