Activity for Al Udell
-
Al Udell posted a comment on discussion Jamulus Software
Hi. I just recently flashed to USB stick as well. I think the trick is to flash it with Rufus with the 'Enable Persistent Storage' option. I used the max amount - 24 GB with the slider. According to Rufus docs, when you create a USB drive with persistence, you can allocate up to 24 GB of the USB drive for a persistent overlay file. Any changes you make to the system—for example, saving a file to your desktop, changing the settings in an application, or installing a program—will be stored in the overlay...
-
What if I don’t want my Server’s Audio on the Web where ANYONE can listen to it? Well you should probably have thought of that before you made your server public, anyone with Jamulus can listen right now. How does your agent deal with public servers that display the 'I have read the conditions and agree...' checkbox and/or have specific conditions stated in the welcome message? Have you considered an opt-in model for your service rather than opt-out? -- e.g. recording automatically and forcing public...
-
Nice! How does the hyperlink support for the chat window work? My http links don't do anything when clicked on. Is https only supported?
-
From what I see, Ja.Ce (Streamer) will connect when there is a minimum of 2 connections. 'No Name' is the default 'Alias/Name' in Jamulus client. I often see this connection name on my server. It's just a user that doesn't bother to replace it with their name or alias.
-
You could look in the Jamulus log to see if the user has a consistent IP address - then try to block that IP in your router.
-
Can you run your public server and post details so we can test some connections to it? - e.g. server name, IP, port, central server it's registered under..
-
Ah, there you are under 'All Genres'. Glad you got it working. 115 AOK AWS Ponte Vedra FL United States 96 54.175.147.83 22124 3.5.9 Linux
-
It doesn't show up in Jamulus Explorer - http://jamulus.softins.co.uk/. Are you able to direct connect to it at bottom of Connect window (Server Name/Address field)? If not, can you provide the IP and port it runs on? I'll try a few connectivity tests from my end. -Al
-
Hi Mark. I assume you tried stopping/restarting the service? Can you provide the name of your server and which central server list it is registered under? -Al
-
Excellent explanation about port 2 from Tony on Github - https://github.com/softins/jamulus-web/issues/5
-
I stumbled across this same issue quite a while ago. See - https://sourceforge.net/p/llcon/discussion/server/thread/9fef1c4bdd/?limit=25#00e8/9448/c11b/f3b9/add2/8ae1 -Al
-
Thank-you Volker. Much appreciated!
-
Hi Don. Rob is correct. Both Alt-m (Mute) and Alt-s (Settings) work fine as long as the main Jamulus window has focus. You're right about the Alt-h (Chat) hotkey - it doesn't seem to work on Windows. We used a Autohotkey script when we tested Alt-m so that we could map it to a single key and use with bluetooth devices. The script also takes care of ensuring the main Jamulus window has focus as you can see in the referenced discussion.
-
And thank-you Volker for adding in keyboard shortcuts for Mute Myself, Settings, and Chat. Now these settings can be toggled from a bluetooth device. Much apprecaited! Keyboard shortcuts in Jamulus
-
Definitely need a webserver. The new history tool uses PHP and JS/JSON to serve the graph.
-
Are you using a VPN?
-
Okay, thanks. So I'm reading that to use the new history tool, you need to run a webserver (including PHP) that has access to the server-side location of the Jamulus log. This adds another layer of complexity to a Jamulus install but I understand that it was needed.
-
Oh, okay, I did not know that --histdays and --history are now deprecated. How does one get the history feature working now?
-
Oh, okay, I did not know that --histdays and --history are now depricated. How does one get the history feature working now?
-
I'm trying out a new cloud-based server running Debian 10-x86_64-ge. Jamulus compile (3.5.9git) went fine however I'm getting this error when attempting to launch the service. - Aug 11 22:31:27 Jamulus jamulus[12911]: /usr/local/bin/Jamulus: Unknown option '--history' -- use '--help' for help So I removed the --history argument and the service runs fine now. Why would the --history option not work in this case? I've used the exact same compile and launch steps on another cloud-based service running...
-
I'm trying out a new cloud-based server running Debian 10-x86_64-ge. Jamulus compile (3.5.9git) went fine however I'm getting this error when attempting to launch the service. - Aug 11 22:31:27 Jamulus jamulus[12911]: /usr/local/bin/Jamulus: Unknown option '--history' -- use '--help' for help So I removed the --history argument and the service runs fine now. Why would the --history option not work in this case? I've used the exact same compile and launch steps on another cloud-based service running...
-
I'm trying out a new cloud-based server running Debian 10-x86_64-ge. Jamulus compile (3.5.9git) went fine however I'm getting this error when attempting to launch the service. - Aug 11 22:31:27 Jamulus jamulus[12911]: /usr/local/bin/Jamulus: Unknown option '--history' -- use '--help' for help So I removed the --history argument and the service runs fine now. Why would the --history option not work in this case? I've used the exact same compile and launch steps on a another cloud-based service running...
-
I created a new Github issue regarding this - Incorporate local timezone in jam recorder folder #497
-
Nice work Mark! I'm curious, in your video you mention that Jamulus is not compiled for multiple CPUs but yet you proceed to install a 2-CPU server instance. Also, you've selected the 'Cloud Compute' rather than the newer 'Higher Frequency' server option. Can you recommend which server options would provide the smallest ping/latency times for Jamulus clients?
-
You're welcome. The fact that you can see your server and connect to it from within your LAN when on your ISPs router indicates that reverse-NAT appears to be working on that router, but not on your Linksys router.
-
I too run a public Jamulus server on my home network and experience the same problem as you - I can't connect to it from within my LAN by WAN IP, but others have no problem connecting to it from outside. I think it's due to NAT rules in the router. If your router supports reverse NAT (also called NAT Reflection, Haripin NAT), then it should work. The workaround is to connect to your Jamulus server within your LAN by {LAN IP address:port} in the 'Server Name/Address' box at the bottom of the Connect...
-
I too run a public Jamulus server on my home network and experience the same problem as you - I can't connect to it from within my LAN, but others have no problem connecting to it from outside. I think it's due to NAT rules in the router. If your router supports reverse NAT (also called NAT Reflection, Haripin NAT), then it should work. The workaround is to connect to your Jamulus server within your LAN by {LAN IP address:port} in the 'Server Name/Address' box at the bottom of the Connect screen....
-
I too run a public Jamulus server on my home network and experience the same problem as you - I can't connect to it from within my LAN, but others have no problem connecting to it from outside. I think it's due to NAT rules in the router. If your router supports reverse NAT (also called NAT Reflection, Haripin NAT), then it should work. The workaround is to connect to your Jamulus server within your LAN by {IP address:port} in the 'Server Name/Address' box at the bottom of the Connect screen. Regarding...
-
I'm connected to it now Peter. Appears to be no issues. Getting about 95ms latency from where I am in Victoria BC.
-
Can you provide the server name and central server its registered under?
-
When I run the public server, I check the Jamulus central server listing and I can see my public server listed there too. So, this is working for you now?
-
When I run the public server, I check the Jamulus central server listing and I can see my public server listed there too. So, this is working for you now?
-
I'm not familiar on how Windows 10 runs on AWS servers but is there any chance multiple display support could be enabled - causing Jamulus to display off the screen?
-
I/m not familiar on how Windows 10 runs on AWS servers but is there any chance multiple display support could be enabled - causing Jamulus to display off the screen?
-
I suspect your Jamulus server PC connected to the second Linksys router may not be accessible via a public facing WAN IP address and therefore fails to register on the Jamulus central servers. Are you replacing the router functionality of your ISP router with the Linksys router? If so, you need to put your ISP router in "bridge mode" so that it is assigned a WAN IP address.
-
Wonderful! I thank you sir!
-
Excellent tip BTDT! "WinActivate, Jamulus" works great to activate the Jamulus window. Thanks!
-
Thank-you Volker! The new install works great with Alt-m muting - see attached video. I'm using Autohotkey to map left and right arrow keys to Alt-m for use with a bluetooth page turner. It occured to me that adding additional "Alt" keyboard shortcuts for toggling the display of "Settings" and "Chat" windows could be useful as well to help manage screen real-estate during large jams or when other apps need to be displayed at the same time. Would this be easy to do?
-
Okay, I found the perfect solution - install a tool called Autohotkey - https://www.autohotkey.com/ which lets you run a background script that intercepts single keystrokes (in my case I used left and right arrow which my bluetooth pageturner pedal sends) and sends Alt-m to Jamulus to toggle mute. Anxiously awaiting the next build of Jamulus to have Alt-m!
-
I have a CODA Stomp bluetooth pageturner foot pedal that supports sending the following keyboard strokes: Left/Right Arrow Up/Down Arrow Page Up/Page Down Space/Enter Any chance one of these combinations could be incorporated into Jamulus for a mute toggle? It doesn't look like Alt-m or other keystoke combinations are currently supported but I'm researching middle-man apps.
-
I have a CODA Stomp bluetooth pageturner foot pedal that supports sending the following keyboard strokes: Left/Right Arrow Up/Down Arrow Page Up/Page Down Space/Enter Any change one of these combinations could be incorporated into Jamulus for a mute toggle? It doesn't look like Alt-m or other keystoke combinations are currently supported but I'm researching middle-man apps.
-
I have a CODA Stomp bluetooth pageturner foot pedal that supports sending the following keyboard strokes: Left/Right Arrow Up/Down Arrow Page Up/Page Down Space/Enter Any change one of these combinations could be incorporated into Jamulus for a mute toggle? It doesn't look like Alt-m or other keystoke combinations are currently supported but I'm researching middle-man apps.
-
{deleted}
-
{deleted]
-
Are all friends using the same connect string to the private server? - e.g. {IP}:{port} or {host}:{port}
-
Yes, thank-you! "Alt-m" would be great!
-
Also discussed in https://sourceforge.net/p/llcon/discussion/533517/thread/37fdfe3795/. Add my vote.
-
Also discussed in https://sourceforge.net/p/llcon/discussion/533517/thread/37fdfe3795/. Add my vote.
-
Personally, I could really use a single-key keyboard shortcut in Jamulus to toggle 'Mute Myself' status - like X or M. I often find the need to toggle this setting between songs to tune-up or whatever. Hitting a single-key rather than moving the mouse and clicking a checkbox would be awesome. I haven't found any previous feature requests regarding this on Github - https://github.com/corrados/jamulus/issues. I did find a previous post on this forum requesting a 'Mute Myself' toggle for use with Bluetooth...
-
Thanks for that. I did some searches based on what you described and found this ticket which helps describe it - https://github.com/corrados/jamulus/issues/161
-
Can anyone explain that this server parameter does exactly? I can't find any documentation regarding this. -d --discononquit Disconnect all clients on quit
-
Hi Volker. At the time of initial reporting, I was using a 1st gen Focusrite Scarlett 6i6 USB interface with beta Focusrite USB driver version 4.64.15.598. The beta driver was used to fix an issue with Scarlett interfaces that got stick at 136 buffer - see https://github.com/corrados/jamulus/issues/53. I noticed that the Focusrite 4.64.15.598 beta driver is no longer available at http://beta.focusrite.com/ and a newer non-beta driver is avaialble in their customer portal - Windows: Scarlett Mix Control...
-
If you run 2 simultaneous Jamulus client sessions connected to the same server, you can put instrument and vocals on separate channels. In one session, hard-pan your instrument R-50. In the second session, hard-pan your vocal L-50. You and all your bandmates would use mono-in/stereo-out mode and set channel pans to desired positions.
-
That sounds like expected bahavior. If you set your first channel pan to hard left for example, it will stay there regardless of whether you switch to mono, mono-in/stereo-out, or stereo mode. If you use an INI file, you can find the channel pan values stored like this: <storedpanvalue0>50</storedpanvalue0> ...
-
Hi. If you're setting up and registering a public server, have you tried connecting to your server via the Connect list? If you're setting up a private server, have you tried connecting via IP:port or localname:port?
-
I've been using Mono mode mostly. Using Mono-in/Stereo-out mode makes alot of sense for no attenuation. I thank you sir!
-
Volker, how about adding a new checkbox in the Main or Settings screen to toggle mono center pan attenuation on/off?
-
No worries Volker. I wouldn't want you to change the pan rule just to accomodate me. At least I know now that center pan equals 3dB attenuation. My only concern, if you decide to stay with the current rule, is that many mono users may not realize they're not getting full signal volume from their 2 inputs when using center pan. I've also noticed that when using the -R switch to record sessions, the center pan attenuation also affects recorded mono signal strength. I compared mono guitar signal strength...
-
No worries Volker. I wouldn't want you to change the pan rule just to accomodate me. At least I know now that center pan equals 3dB attenuation. My only concern, if you decide to stay with the current rule, is that many mono users may not realize they're not getting full signal volume from their 2 inputs when using center pan. I've also noticed that when using the -R switch to record sessions, the center pan attenuation also affects recorded mono signal strength. I compared mono guitar signal strength...
-
No worries Volker. I wouldn't want you to change the pan rule just to accomodate me. At least I know now that center pan equals 3dB attenuation. However, I would encourage you to consider using the current 3dB center pan rule for stereo users, then use a 6dB attenuation rule for mono users (which I suspect is most users - instrument + vocal). Or perhaps use a compromise rule of 4.5 dB, which is half-way between the two. My only concern, if you decide to stay with the current rule, is that many mono...
-
No worries Volker. I wouldn't want you to change the pan rule just to accomodate me. At least I know now that center pan equals 3dB attenuation. I think I'll continue to run 2 Jamulus sessions simultaneously (hard-panned R-50 for guitar, hard-panned L-50 for vocal). That way I'll get full signal with no attenuation. Besides, I really like having separate guitar and vocal tracks in the mixer window. My only concern is that many other users may not realize they're not getting full signal volume from...
-
Just thinking about this more Volker, it occured to me that center attenuation affects people using only one mono input. So when using one instrument in left chanel and nothing in right (or vise-versa), and using center pan, the output is by default attenuated 3dB - so users are not getting the full volume of their signal, and are forced to increase their gain - possibly into distortion, to compensate. I suspect most users like me just use one input for instrument and one for vocal. When not singing,...
-
Thanks for doing that Volker.
-
Hi. I was trying to equalize the guitar volume I was getting from direct monitoring vs what I was getting from Jamulus when connected to my local server. With my guitar in the left channel, Audio quality set to High, channel mix volume set to maximum, and Mono audio channels selected (selecting mono-in/stereo-out didn't make a difference), the only way I could achieve this was by moving the Local audio pan slider to the upper-most R-50 position. Now my guitar volume is very close if not identical...
-
Hi. I've never experimented with the Local audio pan / balance control before until now and noticed a few issues. First off, I had to read the description at https://github.com/corrados/jamulus/blob/master/src/res/homepage/manual.md and experiment with the local pan slider before I realized it's actually a volume/gain/blend control for the 2 input channels. The labelling threw me off as I'm sure others have too. Secondly, I was trying to equalize the guitar volume I was getting from direct monitoring...
-
Hi. I've never experimented with the Local audio pan / balance control before until now and noticed a few issues. First off, I had to read the description at https://github.com/corrados/jamulus/blob/master/src/res/homepage/manual.md and experiment with the local pan slider before I realized it's actually a volume/gain/blend control for the 2 input channels. The labelling threw me off as I'm sure many otehrs got confused by it too. Secondly, I was trying to equalize the guitar volume I was getting...
-
Definitely agree. Using a VPN or some other means to connect externally to your internal server is pointless.
-
I would suspect that using the PCs internal sound card rather than your Focusrite 2i2 is the culprit. I assume you're using ASIO4All with your PC sound card?
-
I think specifying that only the Jamulus program (C:\program files (x86)\jamulus\jamulus.exe) can receive incoming UDP traffic on port 22124 is about as secure as you can get it. -Al
-
Well, port 22124 (assuming that's the port your using) has to be forwarded on both your router and Windows firewall or people simply won't be able to access your server. Just do a manual entry in Windows firewall, new inbound rule, and you should be good to go. -Al
-
What all parameters to you want to include? Can you post your batch file?
-
Wonderful! Thanks Volker. -Al
-
Peter, are you using the latest Focusrite USB version 4.64.15.598 driver? -Al
-
Peter, are you using the latest Focusrite USB driver version 4.64.15.598 driver? -Al
-
Steve, in your batch, start with cd C:\KalamaJam Make sure your batch and INI are in this folder. Then in the same batch, run this line with whatever port you want to use "C:\Program Files (x86)\Jamulus\jamulus.exe" -s -i KFO.ini -p 22130 Hope that helps. -Al
-
Steve, in your batch, start with cd C:\KalamaJam Make sure your batch and INI are in this folder. Then in the same batch, run this line with whatever port you want to use "C:\Program Files (x86)\Jamulus\jamulus.exe" -s -i "C:\KalamaJam\KFO.ini" -p 22130 Hope that helps. -Al
-
Hey folks. I've noticed a curious volume issue when connecting to my private server running v3.5.2 under Windows 10. In a nutshell, I have Jamulus client settings set at: audio quality High, buffer delay 64, auto jitter buffers, mono audio channels, and 'enable small network buffers' off. Using Focusrite ASIO (latest beta driver). After connecting to the private server, I note that the volume of my guitar is rather low. If I turn on 'enable small network buffers' then immediately turn it off, my...
-
Steve, I responded in https://sourceforge.net/p/llcon/discussion/server/thread/f66792486c/ -Al
-
Hey Steve. My understanding is you don't need to set -o in the batch if you're already setting it in an INI file (-i ). Yes, you need to use a different port for each server instance. Refer to https://github.com/corrados/jamulus/wiki/Command-Line-Options. Ports 22124-22130 should be fine. -Al
-
Hi. I've recently come across a timestamp issue regarding recording folders created with both Jamulus Windows and Alpine Linux versions - using current Jamulus v3.5.1. Has anyone else encountered this issue? Here it is in a nutshell: The logfile, created with the -l parameter, is capturing timestamps in the correct timezone. In my case, PST (Pacific Standard Time) - TZ: "America/Vancouver". However, recording folders, created with the -R parameter, are still expressed in UTC (Coordinated Universal...
-
~~~ ~~~Hi. I've recently come across a timestamp issue regarding recording folders created with both Jamulus Windows and Alpine Linux versions - using current Jamulus v3.5.1. Has anyone else encountered this issue? Here it is in a nutshell: The logfile, created with the -l parameter, is capturing timestamps in the correct timezone. In my case, PST (Pacific Standard Time) - TZ: "America/Vancouver". However, recording folders, created with the -R parameter, are still expressed in UTC (Coordinated Universal...
-
Hi. I've recently come across a timestamp issue regarding recording folders created with both Jamulus Windows and Alpine Linux versions - using current Jamulus v3.5.1. Has anyone else encountered this issue? Here it is in a nutshell: The logfile, created with the -l parameter, is capturing timestamps in the correct timezone. In my case, PST (Pacific Standard Time) - TZ: "America/Vancouver". However, recording folders, created with the -R parameter, are still expressed in UTC (Coordinated Universal...
-
Hi. I've recently come across a timestamp issue regarding recording folders created with both Jamulus Windows and Alpine Linux versions - using current Jamulus v3.5.1. Has anyone else encountered this issue? Here it is in a nutshell: The logfile, created with the -l parameter, is capturing timestamps in the correct timezone. In my case, PST (Pacific Standard Time) - TZ: "America/Vancouver". However, recording folders, created with the -R parameter, are still expressed in UTC (Coordinated Universal...
-
Hi. I've recently come across a timestamp issue regarding recording folders created with both Jamulus Windows and Alpine Linux versions - using current Jamulus v3.5.1. Has anyone else encountered this issue? Here it is in a nutshell: The logfile, created with the -l parameter, is capturing timestamps in the correct timezone. In my case, PST (Pacific Standard Time) - TZ: "America/Vancouver". However, recording folders, created with the -R parameter, are still expressed in UTC (Coordinated Universal...
-
Hi. I've recently come across a timestamp issue regarding recording folders created with both Jamulus Windows and Alpine Linux versions - using current Jamulus v3.5.1. Has anyone else encountered this issue? Here it is in a nutshell: The logfile, created with the -l parameter, is capturing timestamps in the correct timezone. In my case, PST (Pacific Standard Time) - TZ: "America/Vancouver". However, recording folders, created with the -R parameter, are still expressed in UTC (Coordinated Universal...
-
Brian, are you using a VPN?
1