Activity for Daniel Nöthen
-
Daniel Nöthen modified a comment on ticket #52
Hello Paul, please provide more information. There is no known issue with M* processors. It works fine on my M1 Macbook Air (Sonoma) and M1 Max (Ventura) and no one else has reported issues so far. So it must be individual problems. What does "not broadcasting" mean exactly? Try to explain in more detail what you do and what is happening. It would be best if you could provide a screen recording that demonstates the issue. Best, Daniel
-
Hello Paul, please provide more information. There is no known issue with M* processors. It works fine on my M1 Macbook Air (Ventura) and M1 Max (Sonoma) and no one else has reported issue so far. So it must be individual problems. What does "not broadcasting" mean exactly? Try to explain in more detail what you do and what is happening. It would be best if you could provide a screen recording that demonstates the issue. Best, Daniel
-
Oh, I didn't know that. I figured out how to do it and made a quick test. If nothing comes up that would speak against that change it will be included in the next release :)
-
Hi Dave, I am afraid I don't understand what you mean by "bitrate property for Icecast". Please elaborate more on that and how do you set it via BUTT config file?
-
Hello Sotmo, I see two possible reasons why it might not work: 1. Please make sure that you downloaded the correct version of libfdk-aac-2.dll. So if you are using BUTT 0.1.41 use this dll: https://danielnoethen.de/butt/release/0.1.41/AAC/libfdk-aac-2.dll If you use on older version, replace the version in the URL above with the version of BUTT you are using. Although In most cases the aac dll does not change from one BUTT release to another I recommend to always download the version that is linked...
-
Hello Sotmo, I see two possible reasons why it is not working: 1. Please make sure that you downloaded the correct version of libfdk-aac-2.dll. So if you are using BUTT 0.1.41 use this dll: https://danielnoethen.de/butt/release/0.1.41/AAC/libfdk-aac-2.dll If you use on older version, replace the version in the URL above with the version of BUTT you are using. Although In most cases the aac dll does not change from one BUTT release to another I recommend to always download the version that is linked...
-
Hello Dave, this is a known issue with Icecast 2.4.4. It should work with the newer -kh versions, though. Also Icecast 2.5betaX has a fix for that. Best, Daniel
-
Thank you for verifiying Rafael.
-
Thats great, thank you Rafael :)
-
Hello Rafael, thanks for the kind words :) Actually the current instructions include "curl-devel" which worked fine for me. Did you follow some old instructions which didn't include neither curl-devel nor libcurl-devel? I am wondering why they name their packages sometimes libfoo-devel and sometimes only foo-devel. Do you know the difference between them? An AppImage is available on the official home page: https://danielnoethen.de/butt/#_download Best, Daniel
-
Hello, BUTT works with Windows 11. There is no need to have a special version for Windows 11.
-
Yes, that could be an option. I will see if icecast and shoutcast would support this.
-
Hello Mark, since BUTT does not read audio files directly, it has no access to any meta data. It receives only the raw audio samples and encodes them. Best, Daniel
-
Hello Mark, since BUTT does not read audio files directly, it has no access to any meta data. It receives only the raw audio samples and encodes them. Besides that I couldn't see that Icecast or Shoutcast support Best, Daniel
-
Confidence monitoring would be very useful
-
Hello Martyn, thanks for your feature suggestions. The first is definitely something I will take into consideration. I can understand the idea behind the second suggestion but this would mean I have to integrate an audio streaming player into BUTT which is not the idea behind it. Why not simply use something like VLC to monitor the stream? Best, Daniel
-
New version is out now: https://danielnoethen.de/butt/#_download
-
It is the source code which can be compiled on Linux. An official release with versions for Windows and Mac will follow this week.
-
Hello Micheal (sorry for misspelling your name in my first reply), this was a tough one to find, but I think I fixed the issue. As a side effect few other issues were also fixed. Please let me know if this version solves the issue for you. You can download the fixed version from: http://danielnoethen.de/butt/hotfix/butt-0.1.38_hotfix1.tar.gz Best, Daniel
-
Thank you! In the meantime, to prevent 0.1.36 from crashing after running for a couple of days it might help to disable "Show listeners" in the GUI tab.
-
Hello Michael, I will have a look into this. But first I would like to ask you a few questions: 1. Can you confirm that this does NOT happen with 0.1.36? (https://sourceforge.net/projects/butt/files/butt/butt-0.1.36/butt-0.1.36.tar.gz/download) 2. Do you use the secondary audio device? 3. Do you also use the recording feature? 4. Do you use Icecast (with TLS?) or Shoutcast? 5. Please share screenshots of the settings tabs Thanks Daniel
-
Hello Cristian, BUTT uses UTF-8 for song encoding. I tried adding charset=UTF-8 to the song update URL but this didn't help. In this case icecast converts it to a HTML encoded string... However, you can workaround it by adding <charset>UTF-8</charset> to your mount specific settings in your icecast config file, or add <mount type="default"> <charset>UTF-8</charset> </mount> just below the <icecast> tag to set it for every mountpoint. Best, Daniel
-
Sorry, I don't understand your question. To summarize: If you connect to a Shoutcast server, butt will always connect to port+1. So if your server runs on 8010, you have to enter 8009 as port.
-
Hello Naga, Shoutcast has always worked like this. Maybe that is because other than Icecast Shoutcast runs the web server and the source sink on two different ports. The web server runs on port X and the source sink on port X+1. The idea is probably that it's easier to remember only the web server port and let the broadcasters also enter this port into their source clients. Best, Daniel
-
Will you add to README this info for openSUSE users? Yes. Will we need a separate SRC file for us to get to compile? No.
-
Will you add to README this info for openSUSE users? Yes. Will we need a separate SRC file for us to get to compile? No.
-
Great! To prevent a conflict with the upcoming butt version 0.1.36 which will also depend on libcurl-devel, I suggest removing the packages libssl52, libressl-devel and install libopenssl-devel instead. You will need to recompile butt afterwards. If you don't want to do that, thats fine. Just keep in mind that you will get warnings which may result in crashes if you compile 0.1.36 in the future. So the correct list of packages is: sudo zypper in fltk-devel portaudio-devel libmp3lame-devel libvorbis-devel...
-
Great! To prevent a conflict with the upcoming butt version 0.1.36 which will also depend on libcurl-devel, I suggest removing the packages libssl52, libressl-devel and install libopenssl-devel instead. You will need to recompile butt afterwards. If you don't want to do that, thats find. Just keep in mind that you will get warnings which may result in crashes if you compile 0.1.36 in the future. So the correct list of packages is: sudo zypper in fltk-devel portaudio-devel libmp3lame-devel libvorbis-devel...
-
The attached sources should compile fine on your machine.
-
No sorry, I will not provide an AppImage. But if anybody else wants to build the AppImages I am happy to share them in the download section.
-
Hello Rafael, I will install OpenSUSE in a VM and try to fix it.
-
Hello Erik, I can understand that you want to deliver the same "quality" to your listeners as the files have been recorded with, but even if you capture some signals with 192 kHz from your vinyls that can not be captured with 96 kHz, no human being will be able to hear the difference. So for now I am not going to add support for 192 kHz. Sorry. Best, Daniel
-
0.1.35 can't connect to icecast
-
I was able to find the issue. Next version will contain a fix.
-
Hello Kick, I will take a look at it. In the meantime, you might consider updating your 14 year old icecast server ;-) Best, Daniel
-
Hello Erik, thank you very much. Actually I have the opinion that 96 kHz should be more than enough for audio broadcasting. For which use case do you need 192 kHz?
-
Unfortunately I can not reproduce the issue. Did you install and run butt it with the same local user (no admin)?
-
Oh, thats interesting and obivously shouldn't be the case. I will have a look at this. Thanks for pointing that out.
-
Hello Pascal, unfortunately I don't own a Rodecaster, but did you already try this tutorial? https://radio.co/blog/broadcast-live-radio-with-the-rodecaster-pro Best, Daniel
-
Hello Pascal, unfortunately I don't own a Rodecaster, but did you already tried this tutorial? https://radio.co/blog/broadcast-live-radio-with-the-rodecaster-pro Best, Daniel
-
No sorry, that is not possible. If you want losless audio stream please use FLAC.
-
Actually any Debian/Ubuntu tutorial should help you as the pi OS is based on Debian. Did you already take a look at the manual? http://danielnoethen.de/butt/manual.html#_install
-
Hi, I don't have experience with the hifiberry DAC+ADC. But if it is detected as an audio device by the operating system it should also work with butt. Setting up a headless system that automatically starts streaming after the system has been booted should be possible. But I can not give you a step by step instruction because I would need to figure it out by myself first. For a Linux beginner this might be a difficult task but not impossible :) As soon as you have managed that your window manager...
-
Hi, I don't have experience with the hifiberry DAC+ADC. But if it is detected as an audio device by the operating system it should also work with butt. Setting up a headless system that automatically starts streaming after the system has been booted should be possible. But I can not give you a step by step instruction because I would need to figure it out by myself first. For a Linux beginner this might be a difficult task but not impossible :) As soon as you have managed that your window manager...
-
Hi Graham, thanks for telling me. I also don't have an explanation for that. At least it works now.
-
Not that I know of.
-
Hello Graham, Unfortunately I don't have a direct solution for you. I can only describe how I would approach this issue. - Is the compressor activated in the butt DSP section? - Are the latest audio drivers and operating system updates installed? - Does recording work with Audacity? (Audacity uses the same audio backend as butt) Best, Daniel
-
Hello Shane, butt does not backup any config files or something. I can't help you with this, sorry. Best, Daniel
-
I have sent you a private message
-
Sorry for the late reply. Hope you did something else than sitting in front of your computer while waiting for an answer ;)
-
Sorry for the late reply. Hope you did something else than sitting on front of your computer while waiting for an answer ;)
-
Hi, please read my answer above. For MacOS you might be able to use https://github.com/ExistentialAudio/BlackHole Or the mode advanced but costly https://rogueamoeba.com/loopback/
-
Hi, butt is designed to work only with input devices. Therefore it can not capture music from your players. However, the latest version supports WASAPI loopback which allows you to capture music from your audio output as long as they provide a WASAPI looback audio device. If you don't see WASAPI loopback devices in the butt device list you need something like: https://vb-audio.com/Voicemeeter/index.htm or the more simple version: https://vb-audio.com/Cable/index.htm Best, Daniel
-
Hi, butt is designed to work only with input devices. Therefore it can not capture music from your players. However, the latest version supports WASAPI loopback which allows you to capture music from your audio output as long as they provide a WASAPI looback audio device. Best, Daniel
-
butt is designed to work only with input devices. Therefore it can not capture music from your players. However, the latest version supports WASAPI loopback which allows you to capture music from your audio output as long as they provide a WASAPI looback audio device.
-
Hi, you need to install libfdk-aac and compile butt from source.
-
Hi, you need to install libfdk-aac
-
Hello Jay, did you already check the latest version? The status flag now has an indicator for "dead air" and "living air". You can read more about the status flag in the manual: http://danielnoethen.de/butt/manual.html#_command_line_options
-
Hello Jay, did you already check the last version? The status flag now has an indicator for "dead air" and "living air". You can read more about the status flag in the manual: http://danielnoethen.de/butt/manual.html#_command_line_options
-
Hello David, did you consider their note? NOTE: You will ONLY be able to log in 30 minutes before your show. Any attempt to log in using the above details when you're not on air or more than 30 minutes your show will result in the connection failing. If you miss the start of your show, the system will only try to reconnect you 10 times (approx 30 minutes). See more details here If yes and it still does not work please get in touch with their support. Best, Daniel
-
Thanks for clarifiying. I was already able to reproduce it. If I am correct it happens if you use either the automatic or manuall file splitting?
-
Hi, yes this is the right place :) I will have a look at it! Best, Daniel
-
No news post for version updates anymore
-
No news post for version updates anymore
-
Hello Jay, I have just implemented your idea. It will be available in the upcoming release :-) Best, Daniel
-
Hello Jay, I have just implemented your idea and it will be available in the upcoming release :-) Best, Daniel
-
The answer to the question "Which is the best audio codec for me?" on the following page should answer your question: https://izicast.de/faq.html
-
The Left and Right drop down menus are below the Channel Mode drop down menu.
-
The Left and Right drop down menus are below the Channel Mode drop down menu.
-
Hello Thomas, please make sure you have selected different audio channels for left and right in the butt audio settings. Best, Daniel
-
non title song with Opus codec.
-
The next version will include title update support for OPUS.
-
Trouble when trying to use OPUS CODEC from Windows XP
-
WAV recordings seen as corrupted in GoldWave
-
A fix will be available in the next release!
-
Thank you for testing, Noah. I will have a look at it. It is probably related to the many channels the Tascam offers. Can you send me a short mail to butt at danielnoethen.de so I can send you a test version as soon as I think I have a fix?
-
Hi, butt uses gettext for multi language support. That means I am bound to the file format as it is. the *.mo files are binary files which are not editable. If you want to edit the translation you need to change the file po/fr.po and re-run make && make install. You can also send me the changed fr.po file and I will include the compiled version in the next release. Best, Daniel
-
APPCRASH, Win7, on Activate Update song name
-
Could not create network socket - Icecast 2.4.4 (Localhost) on Windows
-
WAV recordings seen as corrupted in GoldWave
-
server name containing `]` causes config parse error (can't run butt)
-
Thank you. Has been fixed this in 0.1.32.
-
Hi, thanks for reporting. I will have a look at it :) Best, Daniel
-
Hello Noah, according to the crash report, the issue is related to the audio backend. Since version 0.1.30 butt comes with a new version of PortAudio. It would be interesting if the issue also occurs with the older version that uses the previous PortAudio version. You can get it from here: https://sourceforge.net/projects/butt/files/butt/butt-0.1.29/butt-0.1.29.dmg/download Besides that I have a few more questions: - In the Audio settings of butt, is there "Remember Device by ID" or "Remember Device...
-
Hello David, Should work with High Sierra. Did you run the butt.app from the Application folder? It might not work if you run it from the mounted .dmg folder. Best, Daniel
-
Hi Mac, I do not have experience with the devices your DJs are using. So I am afraid I can not help in those specific cases. Just make sure that my two requirements from above are fulfilled. Maybe these links will help: https://support.apple.com/guide/mac-help/control-access-to-your-microphone-on-mac-mchla1b1e1fe/mac https://support.microsoft.com/en-us/windows/turn-on-app-permissions-for-your-microphone-in-windows-10-94991183-f69d-b4cf-4679-c98ca45f577a Best, Daniel
-
Hi, please check the following on both operating systems: - Are the correct channels selected for left and right in butt settings? - Does butt have permission to access the microphone? Best, Daniel
-
Do you or anyone of your team have basic knowledge of any scripting language? Should be fairly easy to write a script that downloads the file in constant intervals. On which operating system does butt run on?
-
No I am sorry, that is not possible. Isn't it possible to filter out the sensitive data and put the song title it into a different file?
-
No I am sorry, that is not possible. Isn't it possible to filter out the sensitive data and put it into a different file?
-
I was able to find and fix the issue. The fix will be included in the next version.
-
Hello Dave, thanks for testing. I am now able to reproduce it on Windows and I think it has something to do with the change on how name resolution works. I have changed this few versions ago to support IPv6. Please simply use the IPv4 address until I found out how to fix this. Best, Daniel
-
butt text title name retain
-
Great! :)
-
Hello, sorry for forgetting answering you. Actually what you are describing is not a bug. You use it differently than it is intended. To achieve what you want you can write your DJ name into a text file and then select this as file in the "update song name from file" area. butt will read this file immediatly after connecting to the server and update the song name accordingly. Best, Daniel
-
Hello Dave, thank you. I will take a look at it. In the meantime can you try if it makes a difference when using "127.0.0.1" instead of "localhost" as address? Best, Daniel
1 >