home.social

Search

801 results for “tenacity”

  1. Tenacity: محرر صوتيات متعدد المسارات مفتوح المصدر ينافس Audacity بثقة

    Tenacity هو محرر صوتيات متعدد المسارات ومفتوح المصدر، متوفر على ويندوز ولينكس وماك، مع دعم لمقابس VST و LV2 و AU، وتشغيل النصوص البرمجية بلغة Nyquist أو Python، وأدوات تحليل إشارات متقدمة.

    🔗 https://salehgnutux.github.io/GT-NEWSTECH/ar/foss/tenacity-audio-editor/

    #Tenacity #تحرير_صوت #مفتوح_المصدر #صوتيات #أوداسيتي #بدائل_مفتوحة_المصدر
  2. Tenacity: محرر صوتيات متعدد المسارات مفتوح المصدر ينافس Audacity بثقة

    Tenacity هو محرر صوتيات متعدد المسارات ومفتوح المصدر، متوفر على ويندوز ولينكس وماك، مع دعم لمقابس VST و LV2 و AU، وتشغيل النصوص البرمجية بلغة Nyquist أو Python، وأدوات تحليل إشارات متقدمة.

    🔗 salehgnutux.github.io/GT-NEWST

    #Tenacity #تحرير_صوت #مفتوح_المصدر #صوتيات #أوداسيتي #بدائل_مفتوحة_المصدر

  3. Tenacity: محرر صوتيات متعدد المسارات مفتوح المصدر ينافس Audacity بثقة

    Tenacity هو محرر صوتيات متعدد المسارات ومفتوح المصدر، متوفر على ويندوز ولينكس وماك، مع دعم لمقابس VST و LV2 و AU، وتشغيل النصوص البرمجية بلغة Nyquist أو Python، وأدوات تحليل إشارات متقدمة.

    🔗 salehgnutux.github.io/GT-NEWST

    #Tenacity #تحرير_صوت #مفتوح_المصدر #صوتيات #أوداسيتي #بدائل_مفتوحة_المصدر

  4. Tenacity: محرر صوتيات متعدد المسارات مفتوح المصدر ينافس Audacity بثقة

    Tenacity هو محرر صوتيات متعدد المسارات ومفتوح المصدر، متوفر على ويندوز ولينكس وماك، مع دعم لمقابس VST و LV2 و AU، وتشغيل النصوص البرمجية بلغة Nyquist أو Python، وأدوات تحليل إشارات متقدمة.

    🔗 salehgnutux.github.io/GT-NEWST

    #Tenacity #تحرير_صوت #مفتوح_المصدر #صوتيات #أوداسيتي #بدائل_مفتوحة_المصدر

  5. Not too long ago, we discovered there was a fake "mirror" of #Tenacity to #SourceForge. As of today, it looks like SourceForge took it down, along with the account impersonating @gperson.

    For now, we have no plans regarding SourceForge, except for the possibility of creating a legitimate redirect to prevent this from ever happening again. We are still debating that, however.

  6. Not too long ago, we discovered there was a fake "mirror" of #Tenacity to #SourceForge. As of today, it looks like SourceForge took it down, along with the account impersonating @gperson.

    For now, we have no plans regarding SourceForge, except for the possibility of creating a legitimate redirect to prevent this from ever happening again. We are still debating that, however.

  7. Not too long ago, we discovered there was a fake "mirror" of #Tenacity to #SourceForge. As of today, it looks like SourceForge took it down, along with the account impersonating @gperson.

    For now, we have no plans regarding SourceForge, except for the possibility of creating a legitimate redirect to prevent this from ever happening again. We are still debating that, however.

  8. Not too long ago, we discovered there was a fake "mirror" of #Tenacity to #SourceForge. As of today, it looks like SourceForge took it down, along with the account impersonating @gperson.

    For now, we have no plans regarding SourceForge, except for the possibility of creating a legitimate redirect to prevent this from ever happening again. We are still debating that, however.

  9. Not too long ago, we discovered there was a fake "mirror" of #Tenacity to #SourceForge. As of today, it looks like SourceForge took it down, along with the account impersonating @gperson.

    For now, we have no plans regarding SourceForge, except for the possibility of creating a legitimate redirect to prevent this from ever happening again. We are still debating that, however.

  10. Starting in 1.4, we plan to upgrade #Tenacity's license from the GPL v2 (or later) to GPL v3 (or later). Most source files going forward, unless otherwise stated, will be available under the GPL v2 or later and will continue to be that way. However, if we want #ASIO support, we would probably have to backport some changes to 1.3.5 to allow for making GPL v3 (or later) builds. This shouldn't be much of an issue, but we're not completely sure how well this would work.

  11. Starting in 1.4, we plan to upgrade #Tenacity's license from the GPL v2 (or later) to GPL v3 (or later). Most source files going forward, unless otherwise stated, will be available under the GPL v2 or later and will continue to be that way. However, if we want #ASIO support, we would probably have to backport some changes to 1.3.5 to allow for making GPL v3 (or later) builds. This shouldn't be much of an issue, but we're not completely sure how well this would work.

  12. Starting in 1.4, we plan to upgrade #Tenacity's license from the GPL v2 (or later) to GPL v3 (or later). Most source files going forward, unless otherwise stated, will be available under the GPL v2 or later and will continue to be that way. However, if we want #ASIO support, we would probably have to backport some changes to 1.3.5 to allow for making GPL v3 (or later) builds. This shouldn't be much of an issue, but we're not completely sure how well this would work.

  13. Starting in 1.4, we plan to upgrade #Tenacity's license from the GPL v2 (or later) to GPL v3 (or later). Most source files going forward, unless otherwise stated, will be available under the GPL v2 or later and will continue to be that way. However, if we want #ASIO support, we would probably have to backport some changes to 1.3.5 to allow for making GPL v3 (or later) builds. This shouldn't be much of an issue, but we're not completely sure how well this would work.

  14. Starting in 1.4, we plan to upgrade #Tenacity's license from the GPL v2 (or later) to GPL v3 (or later). Most source files going forward, unless otherwise stated, will be available under the GPL v2 or later and will continue to be that way. However, if we want #ASIO support, we would probably have to backport some changes to 1.3.5 to allow for making GPL v3 (or later) builds. This shouldn't be much of an issue, but we're not completely sure how well this would work.

  15. How many times will I enter the Playa del Fuego Swag Button design contest and lose before I give up submitting designs? I think this is at least my 6th try.

    #tenacity

  16. How many times will I enter the Playa del Fuego Swag Button design contest and lose before I give up submitting designs? I think this is at least my 6th try.

    #tenacity

  17. How many times will I enter the Playa del Fuego Swag Button design contest and lose before I give up submitting designs? I think this is at least my 6th try.

    #tenacity

  18. How many times will I enter the Playa del Fuego Swag Button design contest and lose before I give up submitting designs? I think this is at least my 6th try.

    #tenacity

  19. Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

    Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

    Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

  20. Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

    Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

    Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

  21. Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

    Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

    Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

  22. Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

    Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

    Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

  23. Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

    Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

    Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

  24. What's kind of funny (but unsurprising) is how even after #Audacity had their initial telemetry controversy, we're seeing them go down the path of #enshittification. Of course, these features can be disabled at build time, but (heads up: promotional) We Do It For You™.

    Either way, it can be an #anecdote that with a bit of...#tenacity, you don't have to justify a #fork. Just let your upstream do it for you.

  25. No, we won't have a new Tenacity release by New Years (either in a few hours or so). However, we will try to add one more thing for 1.3.5 before releasing it: #ASIO support on #Windows.

    Unfortunately, this release won't have #macOS builds yet again because of other unforseen issues (the builds seem to get stuck somewhere, but at least they will properly build and package now). However, we will have new Windows on ARM builds without FFmpeg, so that'll be new!

  26. Rather than Alt Text, I'll tell you this is a piece of furniture I designed and built from wood and screws, 30 years ago.

    This is my 2nd best rig.

    It's filled bottom to top with :
    Peavey PVX-12 Speakers
    QSC GX3 300 Watt amp
    FURMAN power controller
    Behringer Ultragain PRO MIC pre-amp
    TC Electronic G-major guitar effect processor
    Neutrik half-normalled patch bay
    Line6 POD
    RC-202 LoopStation
    Mackie 12-channel mixer
    Audio-Technica wireless MIC
    Shure SM57
    USB connected to linux/Tenacity

    #Tenacity

  27. @tenacity

    +1 for a Tenacity XMPP conference room!

    I just got my XMPP server running again -- one small payment towards my technical debt.

    #Tenacity #XMPP #TechnicalDebt

  28. Hey everyone! Not much activity to report on this time, but just some house keeping that's just been done, mainly two PRs that were merged!

    The first PR: fixes an issue where #Tenacity would crash on startup after going back to the latest stable version and resetting the toolbar layout. Toolbar preferences are also now properly reset when upgrading to 1.4.

    The second PR: more cherry picks from upstream, but this time they're from the latest development version of AU 3.

  29. Hey everyone! @gperson here with a few things. First, I now have a new laptop, so I'll be able to do many more things with #Tenacity now. Second off, some things are moving recently, so baring university classes, you may see a little more activity on Tenacity.

    Thanks again for everyone's support! We have a bit of a backlog of work to address, so we'll try to work on that while also getting releases of Tenacity, libid3tag, and even libmad out.

    - @gperson

  30. Hey everyone, @gperson here. Just a quick update on why there hasn't been much #Tenacity activity recently.

    Unfortunately, the last month of 2025 has been *very* hectic for me personally, and I do not expect it to get better this year. I'm not going to say what's going on, but just know that it's going to take time away from what I can do with this project and other things in general. There will still be others around, and I will still be around, just less frequently.