Ladiocast 1.1.0-alpha.0 Released – Ladiocast Development Notes No.98

in LadioCast

written by

Join the LadioCast beta - TestFlight - Apple.png

Thank you very much for waiting so patiently for eight long years, ever since I released 0.13.0 in October 2018. I am starting to test Ladiocast Version 1.0.0-alpha.0 on App Store TestFlight. If you would like to take part in the test, please proceed from https://ladiocast-docs.kawauso.com/testing (en) or https://ladiocast-docs.kawauso.com/ja/testing (ja).

Changes from version 0.13.0 to 1.0.0-alpha.0 are as follows:

  • Supports macOS 13 Ventura and later.

  • Rebuilt as a universal app for Intel x86_64 and Apple silicon.

  • Rewrote RTMP Streamer to use librtmp.

  • Added HE-AAC and MP3 encoding formats to RTMP Streamer, in addition to AAC.

  • Updated the libmp3lame library to version 3.101.

  • Changed the default system sample rate from 44,100 Hz to 48,000 Hz.

  • Removed the Character Set selection from Icecast Streamer.

  • Fixed a bug that disconnecting just after a communication error could hang.

  • Fixed a bug that a monaural input device was not automatically mapped to both the left and right channels.

  • Updated the libopus library to version 1.6.1.

The changes are wide-ranging, but most of them concern behavior, so you may be surprised to find that the UI has hardly changed.

Also, the name of the application has been changed from LadioCast to Ladiocast. The old name may still be used in places that cannot be changed, or that I have forgotten to change.

With this release, information about Ladiocast will be moving from https://blog.kawauso.com/ladiocast to https://ladiocast-docs.kawauso.com/blog/ (en) or https://ladiocast-docs.kawauso.com/ja/blog/ (ja).

Finally, I would like to express my heartfelt thanks to Anthropic Claude Sonnet 5.5, whose awe-inspiring abilities made an enormous contribution to getting this release out the door.

Leave a Reply

CAPTCHA

*

らじおぱ for iOS バージョン3.3.0リリース

in Ladiopa

written by

iOSアプリ らじおぱ バージョン3.3.0をリリースしました。 バージョン3.2.3からの変更点は以下のとおりです。
  • Apple Watchのサポートを終了しました。
ストア掃除回避のアップデートになりますが、この3年で変化の大きいwatchOS関連は残念ながら機能自体を終了させました。

5 Responses to “らじおぱ for iOS バージョン3.3.0リリース”

  1. Patrick Bauwens

    Dear Kawauso, first let me thank you on your Ladiocast creation. I’ve been using it for 2 months now and very pleased. But this “Communication error occurred” did appear this morning. This s the second time in 2 months. What could be the origin of this problem. Working on Mac OS 10.13.5. Thanks for your reply. Patrick Bauwens

    2019/06/23 at 08:50
    Reply
    • kawauso

      Hi Patrick,
      Thank you for your reporting about ladiocast. See if the app wrote any error messages on the console at that time with Console.app. Paste them here if you find.
      Cheers.

      2019/06/24 at 11:11
      Reply
  2. Nidal

    Hi Kawauso,
    Thank you for creating LadioCast (I like the name btw and your sense of humor). Is there any kind of manual for this app? The answer I am looking for is: Does LadioCast override the default settings of MacOS, so that I don’t have to worry about them? If not, how should these settings be?
    Best regards, Nidal

    2020/10/28 at 13:45
    Reply
  3. 野生のヘビーユーザー

    もう10年以上かな？ずっと使わせてもらっています。
    ずっと自動アプデを切ったままだったので最近どんな感じなのかなと思ってきてみたら
    アプリストアでの配信停止してしまったのでしょうか。
    それはそれで仕方ないですが。
    なんとなくお礼を伝えたくなってここに辿り着きました。
    もはやねとらじユーザーそのものが絶滅危惧種ですが最新OSでも難なく動いてくれて助かっています。
    今でもアイコンボックスの右下一等地でスマホを開くたびにお世話になっています。
    更新は止まってしまったのかもしれませんが今後とも便利に利用させていただきます。

    2022/05/12 at 13:24
    Reply
    • kawauso

      野生のヘビーユーザーさんコメントどうもありがとうございます。
      更新されていないアプリをストアから削除していくAppleの処置が、遂にらじおぱにも及びました。更新する猶予はありましたが現状審査を通すのは難しいと思い処置を受け入れました。
      様々な思い出の詰まったこのアプリが完全に終わりかどうかはわかりませんが、長きに渡りご使用いただいていること大変感謝いたします。

      2022/05/12 at 17:12
      Reply

Leave a Reply

LadioCast 0.13.0 Released – LadioCast Development Notes No.97

in LadioCast

written by

LadioCast Version 0.13.0 has been released on MAS.
Changes from version 0.12.6 to 0.13.0 are as follows:
  • Removed the ability to pan input stereo channels.
  • Enabled to map any input channel of multi-channel audio devices into stereo.
You will see the input channels selectable at the following part of the mixer window; Screen Shot 2018-10-20 at 15.34.09.png .
Bye.

97 Responses to “LadioCast 0.13.0 Released – LadioCast Development Notes No.97”

  1. Sergei Shablovsky

    Thank You for work!
    Please make ability to launch several copy of app simultaneously. (Like Ladiocst-Cannel-2.app, Ladiocast-Channel-2.app, just like other apps). This is very needed feature! Thank You!

    2018/10/31 at 06:56
    Reply
  3. William Piltzer

    What is “Audiojingle”? Etrecheck found it to be suspicious but probably harmless. I uninstalled Ladiocast and trashed the driver to get rid of it. Should I be worried about it. I don’t like how it shows up in my Sound pane in System Preferences.

    2018/11/09 at 00:35
    Reply
  4. Jay Batson

    Is there a diagnostic mode? The station I broadcast at changed (updated?) it’s Shoutcast server, and Ladiocast no longer successfully connects. Server has same auth / audio setup as previous to upgrade. And BUTT works with all the same settings as Ladiocast. Is there a “status window” or something that allows me to watch the handshake, look at failures, etc?

    2018/12/17 at 15:34
    Reply
  5. Bob Stern

    FLAC encoding request:
    I hope you will consider adding the option of Ogg FLAC encoding.

    “streamy68″ requested this on 2018-07-28. You responded on 2018-07-29 that PCM was a better option because FLAC is not truly lossless. Respectfully, I believe you are mistaken. FLAC is truly lossless, meaning that FLAC encoding followed by FLAC decoding produces audio that is bit-for-bit identical to the original.

    There are 3 reasons Ogg FLAC would be much more helpful than Ogg PCM:
    (1) The official Xiph wiki says the Ogg PCM format “is at best incomplete and at worst completely broken.” Consequently, I do not know any music player that decodes Ogg PCM.
    (2) FLAC is becoming the universal standard for lossless music streaming, now employed by Tidal, Qobuz, Deezer, and YouTube Premium. Also, *all* online music stores that sell lossless downloads offer FLAC format, but almost none offer ALAC. Even Apple does not sell music in ALAC format!
    (3) PCM and FLAC are both bit-perfect (lossless), but FLAC uses less than half the bandwidth.

    (Incidentally, on 2018-08-01, Mr. Shablovsky correctly describes AAC as a very popular lossy format, but erroneously equates this with lossless ALAC. In fact, Wikipedia explains that AAC and ALAC are completely unrelated to each other. The popularity of *lossy* AAC does not recommend ALAC as the best *lossless* format, per paragraph (2) above.)

    Thanks very much for your consideration!

    2019/01/10 at 10:13
    Reply
    • kawauso

      Hi Bob,
      Thank you for your enthusiastic comment.

      I understood, when people saying flac is lossless, they are talking about its encoding functionality, but not its acceptable source resolution;

      Wiki – FLAC
      “Source encoder
      FLAC supports only fixed-point samples, not floating-point. It can handle any PCM bit resolution from 4 to 24 bits per sample,”.

      Ladiocast’s internal audio is in float 32bit resolution, much more information than that.
      That is why even flac was lossy (and oggpcm not) for ladiocast.
      Though oggpcm was far from best and ladiocast even broke the documented specification, better to show the app’s design policy towards the future versatile and high quality live audio streaming in high speed internet era.

      The design may change depending on good motivation unknown.
      I hope that is helpful.
      Cheers.

      2019/01/11 at 10:56
      Reply
  6. Jorge

    Hi! I want to broadcast with Ogg Opus format, but the application always says that “System sample rate in the preferences must be 48000 in using Ogg Opus format”, and all my audio devices are with the 48000 sample rate, what happens? I have macOS High Sierra.

    2019/01/14 at 13:21
    Reply
  7. Ian Stewart

    I need to be able to insert my metadata from my layout server (radio automation) do you support this? I can send you the details of how I do it now. Send text to UDP port 4444 then their is a script to extract the Artist and title and add to the stream.

    2019/02/05 at 18:50
    Reply
  8. kawauso

    Hi Ian,
    Thank you for your comment on ladiocast.
    About the metadata, ladiocast recommends you to make a daemon program which gets the song info from the server and sets it to ladiocast with AppleScript like;

    tell application “LadioCast” to set metadata song to theSongInfo

    only when updated.
    I hope it’s helpful.
    Cheers.

    2019/02/06 at 00:21
    Reply
    • kawauso

      Hi Abner,
      Thank you for your interest in ladiocast.
      Recording facility has been requested but unfortunately not yet.
      Cheers.

      2019/03/08 at 19:13
      Reply
  12. Dennis

    I don’t know what i’m doing wrong. I have an internal rtmp-server at rtmp://127.0.0.1/live with streamkey ByuPtvF64. I can connect with OBS, but not with Ladiocast. I have two fields in the RTMP-settings (URL and Stream). What do I have to fill in? I tried so much options.

    In OBS you have also two fields in the settings (Server and Stream Key).
    When I use
    Server: rtmp://127.0.0.1/live
    Stream Key: ByuPtvF64

    Then it simply works in OBS. But not in Ladiocast. Why?

    2019/05/27 at 14:00
    Reply
    • kawauso

      Hello Dennis,
      Thank you for your report about RTMP. There would be so many factors that make the difference. The rtmp-server name would be helpful.
      Cheers.

      2019/05/28 at 18:56
      Reply
  13. Rousso

    Hello there, I have got to say spot on job with LC.

    Is there a chance of implementing a reconnect feature? I have on a couple of occasions found that my stream has disconnected and this is due to the Wifi environment (Hard wired coming soon when I have built the home studio). As Im running an automated station at the moment and not sat in front of my Mac 24/7 to reconnect it means Im struggling to keep listeners.

    Having it reconnect or attempt again and again until it reconnects would be a cool feature. I’d even pay for it.

    Many Thanks.

    Rousso.

    2019/09/02 at 15:10
    Reply
    • kawauso

      Hi Rousso,
      Thank you for the comment. About reconnecting, LadioCast has been intended to use “Event Handler AppleScript”, which you could see in the Events tab of streamer windows. You might need to search to know how to write the scripts especially if you couldn’t show the Help > ReadMe of the App (that seems to happen in some environment).
      Cheers.

      2019/09/05 at 18:42
      Reply
  14. Anonymous

    For input options I get only ‘N/A’, and ‘Mackbook Pro Microphone’. Shouldn’t I have other input options so I can stream music from say iTunes?

    2019/10/05 at 00:17
    Reply
  17. Joseph Pita Lamboy

    Support using Pioneers DDJ-SX3 ladio cast app recognize the interface but no sound or signal thought LadioCast with Serato

    2019/11/30 at 09:27
    Reply
      • Joseph Pita Lamboy

        When I connect the new Pioneer DDJ-SX3 and Pioneer DDj-1000SRT the app Ladio Cast in the MacBook Pro recognize the computer sound card input and output signal. When I tried to change the soundcard to the DDJ-SX3 or ddj-1000srt, the app give the option to use one of these sound cards but when I put music I don’t received input and output signal.

        2019/12/01 at 04:08
        Reply
        • kawauso

          First of all, check the output channels of your DJ devices match the ladiocast input channels, which are selectable as the most left numbers in the ladiocast’s mixer window panes.
          Good luck.

          2019/12/01 at 04:21
          Reply
  18. Sergei Shablovsky

    hank You for work!
    Please make ability to launch several copy of app simultaneously. (Like Ladiocst-Cannel-2.app, Ladiocast-Channel-2.app, just like other apps). This is very needed feature! Thank You!

    2019/12/31 at 16:14
    Reply
  19. Gabriele

    Hi, is there an option to save the streaming to a local file? This is very useful to keep an archive of the live transmission!
    Thank you :) Gabriele

    2020/03/11 at 10:28
    Reply
    • kawauso

      Hi Gabriele,
      Thank you for your interest in ladiocast.
      > is there an option to save the streaming to a local file?
      Currently no. Waiting for some revelation.
      Cheers.

      2020/03/11 at 12:30
      Reply
    • kawauso

      Hello Craig,
      Ladiocast re-tries to connect once when disconnected, if that also fails, error dialog popped up.
      If that the case you suffer, improve your network environment.
      Cheers.

      2020/04/03 at 12:18
      Reply
      • Craig

        I switched the Ethernet connection and ran it directly to the router is that goes out, it still disconnected again in the middle of the night after about 45 hours of streaming. We are using the latest version of Ladiocast.

        2020/04/05 at 12:32
        Reply
  21. Jim Hopper

    Fantastic Job Kawauso!! I use Ladiocast in conjunction with Soundflower to buss in several audio sources for live video streaming, with OBS handling video duties. Thank you for this app, I honestly don’t know how I’d achieve this otherwise..
    However I was disappointed to discover the file: save/save as/open commands do not include the mixer configuration in the file, as I use different configurations depending on the task in hand.
    Am I missing something in my opening of the .plist file that remembers the configuration?
    No criticism intended, your work is much appreciated…

    2020/04/04 at 17:41
    Reply
  22. Rod

    I want to use Ladiocast with Mac OS X 10.10. (Yosemite) When I download it says I must upgrade to 10.12. Is there a legacy installer to use with OS X 10.10? Thank you!

    2020/05/11 at 18:02
    Reply
  23. kawauso

    Hi Rod,
    For the simplicity, older versions are not provided unless you have downloaded them.
    Sorry for the late response.
    Have a good time.

    2020/05/24 at 11:58
    Reply
  24. fiona

    I have followed a number of different videos and this still is not working for me, I want to broadcast from my Mac to radio co, I have an external USB Mic and a mixer and LadioCast is not picking up either of them!!

    2020/06/26 at 21:02
    Reply
      • fiona

        Its like as if the input levels are switched on or off when they are not, Ladiocast does not seem to pick up any audio from the Mac at all.

        2020/06/27 at 06:46
        Reply
        • kawauso

          If you select mac built-in input device (usually microphone), you must see its level as same in mac system preference (sound, check also security & privacy > microphone).

          2020/06/28 at 13:42
          Reply
  25. Fada

    We are using RadioKing and We have a huge problem. We’ve attempted to configure Ladiocast. with our studio set up to DJ live using Pioneer S9 Mixer/Serato DJ. The program will find the hardware on our Mac and show levels when “internal mic” is selected, but will not actually allow audio to transmit out when we select the S9 mixer as the input. Can you help us with this issue?

    2020/08/17 at 15:32
    Reply
    • kawauso

      Hi Fada,
      > when we select the S9 mixer as the input.
      Check the input channels which are showed and selectable at the most left part of the lasiocast mixer window.
      Cheers.

      2020/08/17 at 19:35
      Reply
  26. Nidal

    Hi Kawauso,
    Thank you for creating LadioCast (I like the name btw and your sense of humor). Is there any kind of manual for this app? The answer I am looking for is: Does LadioCast override the default settings of MacOS, so that I don’t have to worry about them? If not, how should these settings be?
    Best regards, Nidal

    2020/10/28 at 14:01
    Reply
  27. Nidal

    Thank you for the prompt answer!
    Could there be a conflict if the settings are contradictory (different default audio setting on MacOS and LadioCast)?

    2020/10/29 at 06:39
    Reply
  28. hagusa

    ladiocastを開こうとするとクラッシュしてしまいます。解決法が知りたいです。
    Process: LadioCast [646]
    Path: /Applications/LadioCast.app/Contents/MacOS/LadioCast
    Identifier: com.kawauso.LadioCast
    Version: ???
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: LadioCast [646]
    User ID: 501

    Date/Time: 2020-12-01 04:50:38.260 +0900
    OS Version: Mac OS X 10.13.6 (17G14042)
    Report Version: 12
    Anonymous UUID: 41F47559-EE78-F93C-F69A-2837FE0EB1EC

    Time Awake Since Boot: 410 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0

    Exception Type: EXC_CRASH (Code Signature Invalid)
    Exception Codes: 0×0000000000000000, 0×0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Termination Reason: Namespace CODESIGNING, Code 0×1

    kernel messages:

    VM Regions Near 0 (cr2):
    –>
    __TEXT 00000001054ee000-0000000105507000 [ 100K] r-x/rwx SM=COW

    Thread 0 Crashed:
    0 ??? 0x000000010ede319c _dyld_start + 0

    Thread 0 crashed with X86 Thread State (64-bit):
    rax: 0×0000000000000000 rbx: 0×0000000000000000 rcx: 0×0000000000000000 rdx: 0×0000000000000000
    rdi: 0×0000000000000000 rsi: 0×0000000000000000 rbp: 0×0000000000000000 rsp: 0x00007ffeea711bd0
    r8: 0×0000000000000000 r9: 0×0000000000000000 r10: 0×0000000000000000 r11: 0×0000000000000000
    r12: 0×0000000000000000 r13: 0×0000000000000000 r14: 0×0000000000000000 r15: 0×0000000000000000
    rip: 0x000000010ede319c rfl: 0×0000000000000200 cr2: 0×0000000000000000

    Logical CPU: 0
    Error Code: 0×00000000
    Trap Number: 0

    Binary Images:
    0x1054ee000 – 0x105506ff7 +??? (???) (null)
    0x10ede2000 – 0x10ee2cadf +??? (551.5) (null)

    External Modification Summary:
    Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
    Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
    Calls made by all processes on this machine:
    task_for_pid: 405
    thread_create: 0
    thread_set_state: 0

    VM Region Summary:
    ReadOnly portion of Libraries: Total=540K resident=0K(0%) swapped_out_or_unallocated=540K(100%)
    Writable regions: Total=8404K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8404K(100%)

    VIRTUAL REGION
    REGION TYPE SIZE COUNT (non-coalesced)
    =========== ======= =======
    STACK GUARD 56.0M 2
    Stack 8192K 2
    __DATA 256K 4
    __LINKEDIT 148K 4
    __TEXT 400K 3
    shared memory 8K 3
    =========== ======= =======
    TOTAL 64.8M 12

    Model: iMac12,1, BootROM 87.0.0.0.0, 4 processors, Intel Core i5, 2.5 GHz, 24 GB, SMC 1.71f22
    Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x86D3, 0x535030303847425354553136304E30322020
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x86D3, 0x535030303847425354553136304E30322020
    Memory Module: BANK 0/DIMM1, 4 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353237334348302D594B302020
    Memory Module: BANK 1/DIMM1, 4 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353237334348302D594B302020
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.74.0-P2P
    Bluetooth: Version 6.0.7f22, 3 services, 27 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: ST2000DX002-2DV164, 2 TB
    Serial ATA Device: OPTIARC DVD RW AD-5690H
    USB Device: USB 2.0 Bus
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Hub
    USB Device: USB Receiver
    USB Device: USB2.0 Hub
    USB Device: UAB-80
    USB Device: Wireless Controller
    USB Device: BRCM2046 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: IR Receiver
    USB Device: Internal Memory Card Reader
    Thunderbolt Bus: iMac, Apple Inc., 25.1

    2020/11/30 at 19:58
    Reply
    • kawauso

      hagusaさんこんにちは
      >OS Version: Mac OS X 10.13.6 (17G14042)
      >Exception Type: EXC_CRASH (Code Signature Invalid)
      ということで先のトリガラさんのケースと同一かなと思われます。残念ながらこのケースにつきまして再現環境も含めこちらには原因に関する情報が無い状況です。

      2020/12/01 at 20:55
      Reply
  29. micah moses

    the download link for your app LadioCast on the App store for mac is not working. please have it fixed i really would like to use your software thank you

    2021/02/23 at 11:54
    Reply
    • kawauso

      micah moses,
      Thank you for being interested in ladiocast.
      So far the app store connect for developers doesn’t show any illegal state for the app.
      Contact your local app store help desk.
      Cheers.

      2021/02/23 at 12:19
      Reply
  30. Lorenz

    Hi, thank you for Ladiocast! You say, it supports SSL. I can get streaming to work to a non SSL enabled port, but I can’t get it to work on an SSL enabled port. Could you please advise me what to do? By the way: Is Ladiocast still actively developed? Is there a way to support its development?

    2021/03/04 at 08:52
    Reply
    • kawauso

      Lorenz,
      > SSL enabled port
      See errors on server side and client side (Console.app).

      > Is Ladiocast still actively developed?
      I think yes.

      > Is there a way to support its development?
      Currently none.

      2021/03/08 at 14:04
      Reply
      • Lorenz

        Hi, streaming to an SSL enabled port works without any problems with butt. With Ladiocast, I can only get it to work to a port that doesn’t have SSL enabled.

        This is the error popup when trying to stream to the SSL enabled port on my Icecast server:

        Failed to login. Check the network environment or the connection configuration.

        These are the three error messages on Console.App: (I have selected „Icecast“, not „SHOUTcast“; don’t know if it just always says „ShoutStreamer“.)

        ERROR[LCShoutStreamer.m 184] shout_open() = -3, No error

        ERROR[LCStreamer.m 131] NSException = Failed to login.

        ERROR[StreamerWindowController.m 443] NSException = Failed to login.

        Before thinking that I have just misspelled the password or somehow messed up my network configuration, please keep in mind that exactly the same setting works when used on a non-SSL port and it works on the same port using butt with the SSL option ticked.

        Does this error give you a clue as to what might be going wrong?

        2021/03/08 at 14:26
        Reply
        • Lorenz

          Sorry, I should have also added that the Icecast2 error.log reports:

          INFO connection/_handle_source_request Source (/stream) attempted to login with invalid or missing password

          2021/03/08 at 14:30
          Reply
          • kawauso

            Lorenz,
            > This is the error popup when trying to stream to the SSL enabled port on my Icecast server:
            Try to make ssl connection to a formally ssl supported public host and see what happens then.

            2021/03/11 at 19:14
  32. Prince

    Hi Kawauso,

    Thanks for LAdioCast is a pretty cool tool!

    I don’t seem to be able to stream the album art.. perhaps I am doing something wrong?

    2021/04/10 at 00:23
    Reply
  33. Jay Batson

    I just want to say THANK YOU for Ladiocast. For years it has been my preference (over BUTT), and it stays my preferred tool.

    Will you be releasing an M1-ready version? I may upgrade my laptop to an M1 machine soon.

    2021/04/22 at 17:41
    Reply
  34. Tim

    Hi,

    Thanks for your (black box) work., I can see a good will from your side, I miss lot of ore. Sry to say that. To be honest, my nerves are quite overdriven. I am sorry, but you have messed kind of all things up you have to keep in mind, if you start building for the community. The problem is, nobody can support you. Nobody knows and It takes lot of more time and effort to come up with solutions. It is just making me tired in general:

    Would you please consider to make a code repostiory with this e.g Gihub? Don´t you see the problem? It is getting out of control here, I lost now 2hours without any useful information gain. Sry, now you are wasting poeple time, not saving. Now motivation is zero at my side. Thanks!

    By the way your App is just not working and I see no way to get why? I see no living example. I kindly ask why are you forcing us to suffer. Bro, I start my own project if that here is kind of time freezed movement. sry bout hard words,

    2022/01/01 at 23:07
    Reply
  35. Remy Garcia

    Hi,

    I have been using Ladiocast for 6 months as an online broadcast for our radio station. Today, ladiocast has been disconnecting from our shoutcast server every 1/2 hour for no apparent reason. I restarted the computer, deleted and redownloaded the software, and checked the ethernet connection, but still get kicked off.

    Thanks

    2022/06/28 at 23:00
    Reply
    • kawauso

      Hello Remy Garcia,
      > but still get kicked off.
      See system.log in Console.app for what ladiocast saying at that time.
      Cheers.

      2022/06/28 at 23:11
      Reply
  36. Tadahisa Sugisaki

    Audio MIDI設定の複数出力装置の設定で似たようなことはできるのですが、やはりLadioCastのような柔軟性はありません。Rosseta 2で動いてはいるのですが、仮想サウンドドライバのBlackHoleも対応しましたし、LadioCastのApple Silicon対応を切に願います。

    2022/08/14 at 09:12
    Reply
    • kawauso

      Tadahisa Sugisakiさんこんにちは
      情報とご要望大変ありがとうございます。Apple Silicon対応は第一課題でしょうね。

      2022/08/14 at 09:48
      Reply
  38. こげぱんっつ

    コメント失礼します。初めてですのでこちらでいいのか分かりかねるのですが、LadioCastについてです。

    現在M1 MacbookAirで使わせてもらっているのですが、入力１にキャプチャデバイス（ゲーム音）、入力２にオーディオインターフェース（マイク音）、出力をまとめて同じくオーディオインターフェース（ヘッドホン）としている状態で、以下のような現象が起きます。

    １．一定時間（測っていないので毎回同じなのかまちまちなのか分かりかねます）置いてから確認すると、ゲーム音だけ入ってこず、またマイク音はヘッドホンから聞こえてくるものの、入力１、２ともに緑色のゲージが出てきません（ゲーム音の方はそもそも音が入らないのでゲージが出ないのも分かるのですが）。
    これに関しては、一度入力デバイスをそれぞれ一度N/Aにしてから元に戻すことで直ります。
    ２．しかし、今度は出力先を変えてないにも関わらず、ゲーム音だけがオーディオインターフェースのヘッドホンから聞こえてこず、代わりにpcのスピーカーから聞こえてきます。この時マイク音はちゃんとヘッドホンから聞こえてきます。

    原因がわかりません・・・。

    2022/11/26 at 01:45
    Reply
    • kawauso

      こげぱんっつさんこんにちは
      なかなか答えるのが難しい問題ですね。システムと音声デバイスとの接続が不安定な感はありますので、安定した接続設定を確立することが必要かなと思います（Audio MIDI設定.appで使用する音声デバイスのサンプリングレートを揃えたりLadioCastの設定のサンプルレートを変更したりなど）。

      2022/11/26 at 07:55
      Reply
  40. Phil

    Hello again, further to my previous comment some information about the nginx RTMP server:

    The ‘nginx-full’ package was installed by homebrew and is version nginx/1.23.1.

    The configuration is extremely simple, and it appears such a simple configuration is a common approach in the various articles found online on setting up a RTMP server on Mac.

    “`nginx.conf
    worker_processes auto;

    events {
    worker_connections 1024;
    }

    rtmp {
    server {
    listen 1935;
    chunk_size 8192;

    application live {
    live on;
    record off;
    }
    }
    }
    “`

    I also ended the nginx process and installed the ‘Local RTMP Server’ GUI application from the Apple Mac store. This app creates a local RTMP server and exposes the connection details via a menubar item (URL: rtmp://127.0.0.1/live, randomly generated stream key: SJbC_D8Dj ).

    Unfortunately the same error (Failed to Connect) occurs. FFMPEG is able to stream successfully to either nginx’ RTMP server or this RTMP Local Server application. Given the RTMP standard is fairly simple, I suspect this a bug in LadioCast possibly resulting from changes in latest MacOS releases. I am unable to rollback to MacOS 12.x to test this however.

    The console.app output appears the same when using either nginx’ RTMP module or ‘Local RTMP Server’. The nginx rtmp server appears to be the most common approach to running an RTMP instance on mac.

    I hope this helps. Also, no network connection attempts appear in Little Snitch (firewall), which perhaps also might indicate it is something to do with newer MacOS releases as I recall there were changes to the networking stack since Big Sur (11.x+).

    Kind regards,

    Phil

    2022/12/01 at 17:54
    Reply
  41. Phil

    My second comment has appeared publically, but my first did not which suggests that when I failed the first captcha attempt the comment was lost despite a positive redirect. So I will share the original problem once again in case it did not make it to your server. (By the way, there appear to be a few bugs with the blog captcha, it was hidden after I started typing the first comment).

    MacOS Ventura 13.0.1 on Intel Macbook Pro 13′ 2020 (i5-1038g7, 16GB RAM)
    Installed Ladiocast 0.13.0 via Apple App Store on mac.

    I am running nginx RTMP server installed via homebrew’s ‘nginx-full’ package which is version nginx/1.23.1.

    I am unable to connect to my local RTMP server running at rtmp://0.0.0.0:1935/live. I have tried all permutations of the address but each time the GUI raises a dialogue error of ‘Failed to Connect’ after waiting around 10 seconds or so).

    I found these logs in Console.app which might help:

    default 17:30:48.527288 0000 LadioCast nw_endpoint_resolver_update [C2.1 Hostname#76ca2767:1935 in_progress resolver (satisfied (Path is satisfied), interface: lo0)] Adding endpoint handler for 127.0.0.1:1935
    default 17:30:48.527359 0000 LadioCast nw_endpoint_resolver_update [C2.1 Hostname#76ca2767:1935 in_progress resolver (satisfied (Path is satisfied), interface: lo0)] Adding endpoint handler for ::1.1935
    default 17:30:48.527601 0000 LadioCast [C2.1 Hostname#76ca2767:1935 in_progress resolver (satisfied (Path is satisfied), interface: lo0)] event: resolver:receive_dns @0.006s
    default 17:30:48.527777 0000 LadioCast [C2.1.1 127.0.0.1:1935 initial path ((null))] event: path:start @0.007s
    default 17:30:48.528032 0000 LadioCast [C2.1.1 127.0.0.1:1935 waiting path (satisfied (Path is satisfied), viable, interface: lo0)] event: path:satisfied @0.007s, uuid: 33DA7805-A3F0-4BA0-880A-AC24CA85205A
    default 17:30:48.529925 0000 LadioCast [C2.1.1 127.0.0.1:1935 in_progress socket-flow (satisfied (Path is satisfied), viable, interface: lo0)] event: flow:start_connect @0.009s
    default 17:30:48.531852 0000 LadioCast nw_socket_handle_socket_event [C2.1.1:1] Socket received CONNECTED event
    default 17:30:48.532538 0000 LadioCast nw_flow_connected [C2.1.1 127.0.0.1:1935 in_progress socket-flow (satisfied (Path is satisfied), viable, interface: lo0)] Output protocol connected (socket)
    default 17:30:48.533041 0000 LadioCast [C2.1.1 127.0.0.1:1935 ready socket-flow (satisfied (Path is satisfied), viable, interface: lo0)] event: flow:child_finish_connect @0.012s
    default 17:30:48.533364 0000 LadioCast [C2 127.0.0.1:1935 in_progress parent-flow (satisfied (Path is satisfied), interface: lo0)] event: flow:start_connect @0.012s
    default 17:30:48.533407 0000 LadioCast nw_flow_connected [C2.1.1 127.0.0.1:1935 ready socket-flow (satisfied (Path is satisfied), viable, interface: lo0)] Output protocol connected (socket)
    default 17:30:48.533574 0000 LadioCast nw_flow_connected [C2 127.0.0.1:1935 in_progress parent-flow (satisfied (Path is satisfied), interface: lo0)] Output protocol connected (endpoint_flow)
    default 17:30:48.533680 0000 LadioCast [C2 127.0.0.1:1935 ready parent-flow (satisfied (Path is satisfied), interface: lo0)] event: flow:finish_connect @0.013s
    default 17:30:48.533762 0000 LadioCast nw_connection_report_state_with_handler_on_nw_queue [C2] reporting state ready
    default 17:30:48.533832 0000 LadioCast [C2 127.0.0.1:1935 ready parent-flow (satisfied (Path is satisfied), interface: lo0)] event: flow:changed_viability @0.013s
    default 17:30:48.533931 0000 LadioCast [C2.1 Hostname#76ca2767:1935 ready resolver (satisfied (Path is satisfied), interface: lo0)] event: flow:child_finish_connect @0.013s
    default 17:30:48.534018 0000 LadioCast [C2 127.0.0.1:1935 ready parent-flow (satisfied (Path is satisfied), interface: lo0)] event: flow:finish_connect @0.013s
    default 17:30:48.534315 0000 LadioCast TCP Conn 0x6000025e8b40 event 1. err: 0
    default 17:30:48.534749 0000 LadioCast TCP Conn 0x6000025e8b40 complete. fd: 26, err: 0
    default 17:30:48.534753 0000 LadioCast [C2.1.1 127.0.0.1:1935 ready socket-flow (satisfied (Path is satisfied), viable, interface: lo0)] event: flow:changed_viability @0.014s
    default 17:30:48.534984 0000 LadioCast [C2.1 Hostname#76ca2767:1935 ready resolver (satisfied (Path is satisfied), interface: lo0)] event: flow:changed_viability @0.014s
    default 17:30:48.535120 0000 LadioCast [C2 127.0.0.1:1935 ready parent-flow (satisfied (Path is satisfied), interface: lo0)] event: flow:changed_viability @0.014s
    default 17:30:48.535192 0000 LadioCast nw_flow_connected [C2 127.0.0.1:1935 ready parent-flow (satisfied (Path is satisfied), interface: lo0)] Output protocol connected (endpoint_flow)

    I hope this information is useful for potential troubleshooting. These debug messages appear to indicate a successful network connection.

    Apologies for the multiple comments, I had problems with your blog comment system.

    Kind regards,

    Phil

    2022/12/01 at 18:00
    Reply
  42. kawauso

    Hi Phil,
    Thank you for the detailed report about Ladiocast rtmp streamer’s connectivity to the servers.
    It will help a lot.
    Cheers.

    2022/12/03 at 13:24
    Reply
  43. Volodymyr K

    Awesome app, the best one for mixing & routing audio on mac! Would be also great to select specific channel for output, and m1 native version is viable too, i’m even ready to pay for it if you do this!
    Thanks for your work!

    2024/09/26 at 16:06
    Reply
    • kawauso

      Volodymyr,
      Thank you for your post on Ladiocast. Supporting the apple arm64 architecture is recognized as the most anticipated feature. Apologies for a long wait.
      Cheers.

      2024/09/27 at 11:16
      Reply
  46. Klaas de Jong

    Thank you very much for the very useful LadioCast app. I can now monitor my input signals in combination with the ESI U24XL USB based mixer.

    2026/07/18 at 15:19
    Reply
  47. his

    KAWAUSOさん
    Intel MacBookPro時代から、M1 macmini、M4 macminiと、長い間LADIOCASTを活用させていただいています。
    ありがとうございます。
    Intel CPUのサポート切れが近づいておりますが、対応いただける予定はありますでしょうか？
    LadioCastほど安定して利用できるものは他に見当たらず、Apple Silicon対応を願っております。
    災害や暑い日が続きますが、お身体に気をつけて、今後も開発を続けてください。

    2026/08/06 at 22:53
    Reply
    • kawauso

      hisさんこんにちは
      Ladiocastのことを気遣ってもらってありがとうございます。
      なかなか物をリリースできない状態が続いていますが、そろそろしっかりやらなければならないと思っています^^;。その場合は必ずApple Silicon対応となります。
      hisさんもご慈愛くださいませ。
      ではでは。

      2026/08/07 at 11:06
      Reply

Leave a Reply

LadioCast 0.12.6 Released – LadioCast Development Notes No.96

in LadioCast

written by

LadioCast Version 0.12.6 has been released on MAS.
Changes from version 0.12.5 to 0.12.6 are as follows:
  • Updated for microphone usage description.
Mojave’s privacy database daemon (tccd) logged errors and failed to open dialog box to allow microphone (actually all audio inputs) access when the app lacked NSMicrophoneUsageDescription (“Privacy – Microphone Usage Description” on Xcode) in Info.plist, even if it had com.apple.security.device.microphone (“Capabilities” – “Hardware: Microphone” on Xcode) in its entitlements.
Fixing that is only the reason of this release.
Screen Shot 2018-09-28 at 22.07.25.png

8 Responses to “LadioCast 0.12.6 Released – LadioCast Development Notes No.96”

  1. Jay Batson

    I second the request for doing VST insertion. I’ve got some external processors to which I’d love to route my audio prior to broadcast. I’d like to route a selected input to a VST plug-in, then have a selected output draw its input from the output of that VST. Thanks for a great too, even as-is!

    2018/10/14 at 21:18
    Reply
  3. Sergei Shablovsky

    Dear Mr. Kawauso!

    1. Thank You for update app!

    2. Please make ability to launch several (up to 4) instances of LadioCast.
    Because the shift to Mojave now are almost complete for most users (more than 85%), You able to make this update without suffering possible uncompatibility with Mojave.
    Most amateur (and of coarse PRO) Mac-based online radio stations already have more than 1 channels (for example jazz + country music, or classical + jazz music, etc.) and with LadioCast we able to be happy.

    Thank You for future support and customer care!

    2018/10/23 at 01:57
    Reply

Leave a Reply

LadioCast 0.12.5 Released – LadioCast Development Notes No.95

in LadioCast

written by

LadioCast Version 0.12.5 has been released on MAS.
Changes from version 0.12.4 to 0.12.5 are as follows:
  • 32-bit version ended.
  • Support for dark mode on macOS Mojave.
You would see the second note is omitted and doesn’t appear on MAS, though it is the main purpose of the release. That is due to the compliance with the Mac Developer Program License Agreement which prohibits mentioning pre-release versions of the Apple Software. (Actually I didn’t expect 0.12.5 built by the pre-released Xcode to get released before Mojave.) Anyway see another face of LadioCast in the dark mode there. Also Make sure you allow LadioCast to access your microphone under the new security:
Screen Shot 2018-09-16 at 13.50.57.png.
Cheers.

One Response to “LadioCast 0.12.5 Released – LadioCast Development Notes No.95”

  1. kawauso

    P.S.
    I noticed that macOS Mojave’s new privacy database needs more description about the app’s usage of microphone.
    I will make another post after the next LadioCast 0.12.6 passed the apple’s app review and making sure its listing on the privacy section.

    2018/09/25 at 17:10
    Reply

Leave a Reply