PS: At this point I want to say a BIG THANK YOU to gilgongo who created this servey and also put a lot of effort in creating the Wiki pages and helping people in the forum!
👍
3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Interesting results! Interesting that 62% consider themselves computer
programmers. I think the line "Involed in computers for my work" covers
things from advanced low level c++ programmers should to people who use
computers for word docs and emails only!. I wouldn't count the latter as
"Advanced computer uses"!
Definately sound card configuring is the top issue for jamulus and frankly
the one question I am constantly asked about from my facebook group I run.
Today alone I had 3 calls with people having sound card/audio interface
problems.
Zoom audio seems a lot easier to configure for people. Perhaps we should
look into other methods of configuring, perhaps default to windows or mac
in the first instance, advanced users can use ASIO drivers.
I love the idea of password protecting private rooms. But I guess the
problem is that the current architecture of publishing rooms to central
servers would be too difficult and we'd end up with thousands of rooms
being listed with most of them being private. I guess you could have a
tick box to show private or not.
Like the idea of the chat being a little more friendly to be able to paste
chord lines (final suggestion).
I wouldn't count the latter as "Advanced computer uses"!
Hehe - yes, always hard to know how to phase things like this. "Involved in computers for my work" was supposed to exclude those who simply used computers for work (which these days is going to be almost everyone really). To that extent I was surprised that literally nobody identified as basic. Perhaps it's an ego thing :-)
Definately sound card configuring is the top issue
Yes, that's what I thought but it's the toughest one to tackle as it's so hardware and driver dependent (which is why the "Hardware Setup" section of the wiki is so thin). Some projects (eg dd-wrt) that become big enough set up separate discussion forums and support pages for the main hardware devices they're used with, but I don't know if that's feasible for us.
Zoom audio seems a lot easier to configure for people.
Do you mean Zoom the video conferenceing system or the audio interface hardware?
BTW I'm not sure what you mean by "perhaps default to windows or mac in the first instance, advanced users can use ASIO drivers."
I love the idea of password protecting private rooms.
Yes, particularly as that idea seems to have been born out of the observation that setting up a private server is a hassle.
we'd end up with thousands of rooms being listed with most of them being private.
One thing that somedody mentioned on the forums was the concept of expiring unused rooms from the Central Server. So maybe if you set up a password-protected room, it would be removed from listing once the last person left, whereas open servers would be allowed to stay as they are today.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wouldn't count the latter as "Advanced computer uses"!
Hehe - yes, always hard to know how to phase things like this. "Involved
in computers for my work" was supposed to exclude those who simply used
computers for work (which these days is going to be almost everyone
really). To that extent I was surprised that literally nobody identified as
basic. Perhaps it's an ego thing :-)
Definately sound card configuring is the top issue
Yes, that's what I thought but it's the toughest one to tackle as it's so
hardware and driver dependent (which is why the "Hardware Setup" section of
the wiki is so thin). Some projects (eg dd-wrt) that become big enough set
up separate discussion forums and support pages for the main hardware
devices they're used with, but I don't know if that's feasible for us.
Zoom audio seems a lot easier to configure for people.
Do you mean Zoom the video conferenceing system or the audio interface
hardware?
BTW I'm not sure what you mean by "perhaps default to windows or mac in
the first instance, advanced users can use ASIO drivers."
I love the idea of password protecting private rooms.
Yes, particularly as that idea seems to have been born out of the
observation that setting up a private server is a hassle.
we'd end up with thousands of rooms being listed with most of them being
private.
One thing that somedody mentioned on the forums was the concept of
expiring unused rooms from the Central Server. So maybe if you set up a
password-protected room, it would be removed from listing once the last
person left, whereas open servers would be allowed to stay as they are
today.
I wouldn't count the latter as "Advanced computer uses"!
Hehe - yes, always hard to know how to phase things like this. "Involved
in computers for my work" was supposed to exclude those who simply used
computers for work (which these days is going to be almost everyone
really). To that extent I was surprised that literally nobody identified as
basic. Perhaps it's an ego thing :-)
Definately sound card configuring is the top issue
Yes, that's what I thought but it's the toughest one to tackle as it's so
hardware and driver dependent (which is why the "Hardware Setup" section of
the wiki is so thin). Some projects (eg dd-wrt) that become big enough set
up separate discussion forums and support pages for the main hardware
devices they're used with, but I don't know if that's feasible for us.
Zoom audio seems a lot easier to configure for people.
Do you mean Zoom the video conferenceing system or the audio interface
hardware?
BTW I'm not sure what you mean by "perhaps default to windows or mac in
the first instance, advanced users can use ASIO drivers."
I love the idea of password protecting private rooms.
Yes, particularly as that idea seems to have been born out of the
observation that setting up a private server is a hassle.
we'd end up with thousands of rooms being listed with most of them being
private.
One thing that somedody mentioned on the forums was the concept of
expiring unused rooms from the Central Server. So maybe if you set up a
password-protected room, it would be removed from listing once the last
person left, whereas open servers would be allowed to stay as they are
today.
In order to make the software more accessible to non computer programmers, can I suggest rewording the header page to make it more readable. My point is based on the theory that people lose focus when they read stuff they don't understand. I'll bet that most users will stop reading the tag line at some point based on their comprehension of the content....
The sentence..
"Jamulus is Open Source software (GPL, GNU General Public License) and runs under Windows (ASIO), MacOS (Core Audio) and Linux (Jack). It is based on the Qt framework and uses the OPUS audio codec. "
Could be simplified something like....
Jamulus is Low Latency audio/music collaboration software for laptop desktop. <-- hotlink latency to it's definition on wiki or whatever.
It requires ASIO(Windows), Core Audio (MacOS) or Jack (Linux). It is based on the Qt framework and uses the OPUS audio codec. Jamulus is fully Open Source software (GPL, GNU General Public License) <-- leave techhy stuff to the requirements. People who want to read this will make the effort and read down to it. I'd like to suggest a bit more info in the requirements section also, i.e. OS versions, memory and clarity wrt bps/Bps terminology. (bits/bytes) and hotlink "open source" and "ms" to a definition.
Well done Volker and team.
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please leave the deep technical details up for us "advanced" users like
myself who use Linux. I am an retired network guy so the more helpful tech
docs you have, the more we can tweak out the software enviroment to improve
the experience. Kudos to Volker and team for a fantastic job. I reported in
an earlier post some issues I had with Jack on ubuntu and some solutions to
Jack recognizing hardware.Using Jamulus 3.4.3 and 3.4.4 on 2 different pc's
with Jack. The more users report, the better the experience, regardless of
o.s. platform used.
In order to make the software more accessible to non computer programmers,
can I suggest rewording the header page to make it more readable. My point
is based on the theory that people lose focus when they read stuff they
don't understand. I'll bet that most users will stop reading the tag line
at some point based on their comprehension of the content....
The sentence..
"Jamulus is Open Source software (GPL, GNU General Public License) and
runs under Windows (ASIO), MacOS (Core Audio) and Linux (Jack). It is based
on the Qt framework and uses the OPUS audio codec. "
Could be simplified something like....
Jamulus is Low Latency audio/music collaboration software for laptop
desktop. <-- hotlink latency to it's definition on wiki or whatever.
It requires ASIO(Windows), Core Audio (MacOS) or Jack (Linux). It is based
on the Qt framework and uses the OPUS audio codec. Jamulus is fully Open
Source software (GPL, GNU General Public License) <-- leave techhy stuff to
the requirements. People who want to read this will make the effort and
read down to it. I'd like to suggest a bit more info in the requirements
section also, i.e. OS versions, memory and clarity wrt bps/Bps terminology.
(bits/bytes) and hotlink "open source" and "ms" to a definition.
Wasn't referring to a particular page, just replying to a comment made
about keeping technical docs for us techie's and keeping layman's docs for
people less technical oriented. I do appreciate you responding to the posts
and your level of engagement to improving the platform. I am a serious
musician (as well as a retired network guy) who really appreciate this
platform and how much the developers have contributed. A band member of
mine is also a software developer and we have spent quite a bit of time on
Jamulus so our band can continue practicing until corona is gone.
Is there a project slated for docs? I would love to be involved in helping develop next-generation docs for this open source project. I'm a tech writer/web developer by day.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After much tinkering with mic/output devices in Ubuntu, I am using a behringer UMC usb interface. No drivers are necessary in Ubuntu 18, device is recognized. Excellent sound quality, I use a Shure voice mic with XLT connector, plug guitar and headphones directly into the Behringer.
This wasn't working at first, even though the hardware was recognized. Using qjackctl gui to configure the inputs and outputs, sometimes the jackd would not start or freeze my pc, having to kill jackd process.
first, I ran the various commands to check hardware and ports:
pactl list for detailed hardware info
aplay -l gives the hardware card number so if the qjackctl doesn't start from the gui, then your run this to manually start jackd:
jackd -R -d alsa -d hw:x (where x=number of hardware/sound card in aplay -L)
other hardware directories configuration/information files can assist with detailed hardware information also:
Issues I first encountered with jackd were he sample and frame rate errors stating my sample rate and frame should be 48000 128/frames when that was the correct settings. Running
jackd -R -d alsa -d hw:x (where x=number of hardware/sound card in aplay -L)
a few times and rebooting machine seems to have helped jackctl start when launching the jamulus client.
I am using Jamulus 3.4.3 currently Ubuntu 18.04.1
AMD Ryzen 5 3400G CPU 32GB physical ram
Behringer UMC22 Interface for sound card
Shure PGA48 mic plugged into Behringer with XLT connector
guitar plugged into Behringer
headphones plugged into Behringer.
Sound quality on Jamulus crystal clear
I set my latency at 10.3ms, sometimes at 21 ms if sound deteriorates
I used Windows 10 for a week or so, but it was on a very old pc, which did not recognize the Behringer. Also, i tried webcams and other usb mics in Ubuntu, with recognition intermittent
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got my start on your main server and played a bit with Stephen, Nick, and Pablito. Then we found a closer server (to Vancouver) and it was a great experience! I goofed around on the Billie Eilish Bond song, and by the second chorus we were joined by a drummer from Montreal. The latency was terrible, the drummer being across the country, but the experience was epic!
Now, my friend and I use 3.5.1 on a server he runs on a second computer and we have a blast. We're still tweaking.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many thanks to Volker and crew! Our merry band has been able to continue playing remotely (all in San Diego CA) and our last session was best so far. We have a member hosting a server as he has the best connection but I'm running Jamulus 3.4.7 on an old Mac Pro - OS X 10.13.6 - 2.8 GHz Quad-Core Intel Xeon - 32 GB 1066 MHz DDR3. Audio interface is Steinberg UR22 with mic and guitar (simultaneous). We did experience an intermittent artifact (but only a few times over 2.5 hours) that sounded like a series of ~10-15 bass pops so we naturally just blamed the bass player and kept on rolling. I'll update with more details later, specifically about our member that is hosting the server.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am new to J and trying to hook with a Mac OS 10.15.4. This no doubt has been covered somewhere but I get a message "Mac OS can not verify that this app is free from malware..."
Can you help with basic start up. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"... click on Jamulus in the Applications folder, right-click (or control-click), and select Open from the top of the menu. You will then get a slightly different version of the same message, which allows you to click Open and go ahead with running it. "
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Volker, Simon and everyone else in the Jamulus community that is helping to make this awesome tool possible. I just stopped by to say THANK YOU and I really appreciate all the effort going into this. My bandmates and I got Jamulus up and running this week, and after some tweaking we are SO happy to have an "almost in person" rehearsal and collaboration tool. It's amazing to be able to actually play together, from across town, with small enough latency that it (mostly) doesn't affect our performance or creativity. We keep a Zoom meeting running alongside Jamulus so we have a visual, and switch between audio sources in Jamulus (microphone vs Pro Tools vs iTunes, etc.) depending on what we need to listen to. We're still working out the details, but it's been great to have access to all the documentation, fixes, updates and support. Discovering Jamulus has made this current situation a bit more bearable. Thank you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One quick suggestion - I have literally never used any central servers and those questions were required on the survey. It might be good to either add an option like "I don't use central servers" to those questions or maybe make the question not be required. Thanks for the consideration!
Last edit: Schema Man 2020-04-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you mean you have only ever run a private server? In which case you could have ignored "If you run a server in "public mode" (register it in the Central Server), why is that?" and anwsered "If you run a server in "private mode" (give other musicians your network address), why is that?".
Both questions were optional though, so I'm not sure what you mean exactly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We'd love to know more about how you use Jamulus, what you think of it so far, and what issues you mostly commonly have with it.
If you have a couple of minutes, please fill out our anonymous survey!
PS: At this point I want to say a BIG THANK YOU to gilgongo who created this servey and also put a lot of effort in creating the Wiki pages and helping people in the forum!
**After a week, we have 100 results! **
**Here's the summary **
Feel free to add comments on anything you find interesting.
Interesting results! Interesting that 62% consider themselves computer
programmers. I think the line "Involed in computers for my work" covers
things from advanced low level c++ programmers should to people who use
computers for word docs and emails only!. I wouldn't count the latter as
"Advanced computer uses"!
Definately sound card configuring is the top issue for jamulus and frankly
the one question I am constantly asked about from my facebook group I run.
Today alone I had 3 calls with people having sound card/audio interface
problems.
Zoom audio seems a lot easier to configure for people. Perhaps we should
look into other methods of configuring, perhaps default to windows or mac
in the first instance, advanced users can use ASIO drivers.
I love the idea of password protecting private rooms. But I guess the
problem is that the current architecture of publishing rooms to central
servers would be too difficult and we'd end up with thousands of rooms
being listed with most of them being private. I guess you could have a
tick box to show private or not.
Like the idea of the chat being a little more friendly to be able to paste
chord lines (final suggestion).
On Tue, Apr 21, 2020 at 10:14 PM Gilgongo gilgongojones@users.sourceforge.net wrote:
Hehe - yes, always hard to know how to phase things like this. "Involved in computers for my work" was supposed to exclude those who simply used computers for work (which these days is going to be almost everyone really). To that extent I was surprised that literally nobody identified as basic. Perhaps it's an ego thing :-)
Yes, that's what I thought but it's the toughest one to tackle as it's so hardware and driver dependent (which is why the "Hardware Setup" section of the wiki is so thin). Some projects (eg dd-wrt) that become big enough set up separate discussion forums and support pages for the main hardware devices they're used with, but I don't know if that's feasible for us.
Do you mean Zoom the video conferenceing system or the audio interface hardware?
BTW I'm not sure what you mean by "perhaps default to windows or mac in the first instance, advanced users can use ASIO drivers."
Yes, particularly as that idea seems to have been born out of the observation that setting up a private server is a hassle.
One thing that somedody mentioned on the forums was the concept of expiring unused rooms from the Central Server. So maybe if you set up a password-protected room, it would be removed from listing once the last person left, whereas open servers would be allowed to stay as they are today.
Thank you Volker and Gilgongo. We got going on a rough jam here today in
beautiful Victoria, Canada. We appreciate your help!
Norm
On Wed, Apr 22, 2020 at 8:09 AM Gilgongo gilgongojones@users.sourceforge.net wrote:
Also I should advise that I used a Presonus USB 96 AI and a partner used a
Presonus 24C, also worked. FYI for your forum.
On Wed, Apr 22, 2020 at 4:42 PM Norm Tatlow normtatlow@users.sourceforge.net wrote:
Thank you! The next step would be to create Issues on Github on the new discoveries from the survey.
In order to make the software more accessible to non computer programmers, can I suggest rewording the header page to make it more readable. My point is based on the theory that people lose focus when they read stuff they don't understand. I'll bet that most users will stop reading the tag line at some point based on their comprehension of the content....
The sentence..
"Jamulus is Open Source software (GPL, GNU General Public License) and runs under Windows (ASIO), MacOS (Core Audio) and Linux (Jack). It is based on the Qt framework and uses the OPUS audio codec. "
Could be simplified something like....
Jamulus is Low Latency audio/music collaboration software for laptop desktop. <-- hotlink latency to it's definition on wiki or whatever.
It requires ASIO(Windows), Core Audio (MacOS) or Jack (Linux). It is based on the Qt framework and uses the OPUS audio codec. Jamulus is fully Open Source software (GPL, GNU General Public License) <-- leave techhy stuff to the requirements. People who want to read this will make the effort and read down to it. I'd like to suggest a bit more info in the requirements section also, i.e. OS versions, memory and clarity wrt bps/Bps terminology. (bits/bytes) and hotlink "open source" and "ms" to a definition.
Well done Volker and team.
Stephen
Please leave the deep technical details up for us "advanced" users like
myself who use Linux. I am an retired network guy so the more helpful tech
docs you have, the more we can tweak out the software enviroment to improve
the experience. Kudos to Volker and team for a fantastic job. I reported in
an earlier post some issues I had with Jack on ubuntu and some solutions to
Jack recognizing hardware.Using Jamulus 3.4.3 and 3.4.4 on 2 different pc's
with Jack. The more users report, the better the experience, regardless of
o.s. platform used.
On Fri, Apr 24, 2020 at 10:32 AM SOR soreilly@users.sourceforge.net wrote:
Which page are you referring to exactly?
Wasn't referring to a particular page, just replying to a comment made
about keeping technical docs for us techie's and keeping layman's docs for
people less technical oriented. I do appreciate you responding to the posts
and your level of engagement to improving the platform. I am a serious
musician (as well as a retired network guy) who really appreciate this
platform and how much the developers have contributed. A band member of
mine is also a software developer and we have spent quite a bit of time on
Jamulus so our band can continue practicing until corona is gone.
On Fri, Apr 24, 2020 at 12:46 PM Gilgongo gilgongojones@users.sourceforge.net wrote:
Apologies, I should have been clearer. http://llcon.sourceforge.net/
It's the landing page from a google search for Jamulus.
Best Regards
Stephen
Good idea, I support this.
@Gilgongo, do you want to make a proposal?
Is there a project slated for docs? I would love to be involved in helping develop next-generation docs for this open source project. I'm a tech writer/web developer by day.
I'll publish this survey on the facebook group I administer if you want
Yes, please. Thank you.
Working sound card on Ubuntu 18.04 with Jamulus
After much tinkering with mic/output devices in Ubuntu, I am using a behringer UMC usb interface. No drivers are necessary in Ubuntu 18, device is recognized. Excellent sound quality, I use a Shure voice mic with XLT connector, plug guitar and headphones directly into the Behringer.
This wasn't working at first, even though the hardware was recognized. Using qjackctl gui to configure the inputs and outputs, sometimes the jackd would not start or freeze my pc, having to kill jackd process.
first, I ran the various commands to check hardware and ports:
pactl list for detailed hardware info
aplay -l gives the hardware card number so if the qjackctl doesn't start from the gui, then your run this to manually start jackd:
jackd -R -d alsa -d hw:x (where x=number of hardware/sound card in aplay -L)
other hardware directories configuration/information files can assist with detailed hardware information also:
/proc/asound/cards/
/proc/asound/devices/
/proc/asound/oss/devices
/proc/asound/pcm
Issues I first encountered with jackd were he sample and frame rate errors stating my sample rate and frame should be 48000 128/frames when that was the correct settings. Running
jackd -R -d alsa -d hw:x (where x=number of hardware/sound card in aplay -L)
a few times and rebooting machine seems to have helped jackctl start when launching the jamulus client.
I am using Jamulus 3.4.3 currently Ubuntu 18.04.1
AMD Ryzen 5 3400G CPU 32GB physical ram
Behringer UMC22 Interface for sound card
Shure PGA48 mic plugged into Behringer with XLT connector
guitar plugged into Behringer
headphones plugged into Behringer.
Sound quality on Jamulus crystal clear
I set my latency at 10.3ms, sometimes at 21 ms if sound deteriorates
I used Windows 10 for a week or so, but it was on a very old pc, which did not recognize the Behringer. Also, i tried webcams and other usb mics in Ubuntu, with recognition intermittent
submitted
Thank you
On Sun, Apr 19, 2020 at 12:55 AM David Warwick Thompson clarimus@users.sourceforge.net wrote:
Volker and team--thanks for the great work!
I got my start on your main server and played a bit with Stephen, Nick, and Pablito. Then we found a closer server (to Vancouver) and it was a great experience! I goofed around on the Billie Eilish Bond song, and by the second chorus we were joined by a drummer from Montreal. The latency was terrible, the drummer being across the country, but the experience was epic!
Now, my friend and I use 3.5.1 on a server he runs on a second computer and we have a blast. We're still tweaking.
Many thanks to Volker and crew! Our merry band has been able to continue playing remotely (all in San Diego CA) and our last session was best so far. We have a member hosting a server as he has the best connection but I'm running Jamulus 3.4.7 on an old Mac Pro - OS X 10.13.6 - 2.8 GHz Quad-Core Intel Xeon - 32 GB 1066 MHz DDR3. Audio interface is Steinberg UR22 with mic and guitar (simultaneous). We did experience an intermittent artifact (but only a few times over 2.5 hours) that sounded like a series of ~10-15 bass pops so we naturally just blamed the bass player and kept on rolling. I'll update with more details later, specifically about our member that is hosting the server.
I am new to J and trying to hook with a Mac OS 10.15.4. This no doubt has been covered somewhere but I get a message "Mac OS can not verify that this app is free from malware..."
Can you help with basic start up. Thanks.
Hi Norm - is this issue fixed by the instructions given at the bottom of this page?
https://github.com/corrados/jamulus/wiki/Installation-for-Macintosh
"... click on Jamulus in the Applications folder, right-click (or control-click), and select Open from the top of the menu. You will then get a slightly different version of the same message, which allows you to click Open and go ahead with running it. "
Hello Volker, Simon and everyone else in the Jamulus community that is helping to make this awesome tool possible. I just stopped by to say THANK YOU and I really appreciate all the effort going into this. My bandmates and I got Jamulus up and running this week, and after some tweaking we are SO happy to have an "almost in person" rehearsal and collaboration tool. It's amazing to be able to actually play together, from across town, with small enough latency that it (mostly) doesn't affect our performance or creativity. We keep a Zoom meeting running alongside Jamulus so we have a visual, and switch between audio sources in Jamulus (microphone vs Pro Tools vs iTunes, etc.) depending on what we need to listen to. We're still working out the details, but it's been great to have access to all the documentation, fixes, updates and support. Discovering Jamulus has made this current situation a bit more bearable. Thank you!
One quick suggestion - I have literally never used any central servers and those questions were required on the survey. It might be good to either add an option like "I don't use central servers" to those questions or maybe make the question not be required. Thanks for the consideration!
Last edit: Schema Man 2020-04-25
Do you mean you have only ever run a private server? In which case you could have ignored "If you run a server in "public mode" (register it in the Central Server), why is that?" and anwsered "If you run a server in "private mode" (give other musicians your network address), why is that?".
Both questions were optional though, so I'm not sure what you mean exactly.