Coder Social home page Coder Social logo

interactiveaudiolab / audealize-plugin Goto Github PK

View Code? Open in Web Editor NEW
29.0 29.0 5.0 175.91 MB

This is a Juce-based plugin version of Audealize for a DAW

License: Other

Makefile 1.65% C 21.67% C++ 60.82% Objective-C++ 3.29% Objective-C 7.38% R 0.03% Java 0.35% M4 0.05% Shell 0.63% HTML 1.06% PostScript 2.17% Roff 0.89%

audealize-plugin's People

Contributors

michaeldonovan avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

audealize-plugin's Issues

organization of code

Provide a document (maybe in the wiki) that describes the overall code organization in terms of what the code in each folder does. Also, at the top of each file that you developed from scratch, put a paragraph that explains what it is generally for.

Unable to Compile with JUCE (v5.4.5) on macOS Catalina (10.15.1)

I've been trying to compile Audealize to extend its functionality, but I'm running into a handful of errors along the way that have prevented me from doing so. There are a mix of errors due to support being dropped by JUCE and others related to permissions.

Here are the first error that I get is:
Error: The i386 architecture is deprecated. You should update your ARCHS build setting to remove the i386 architecture.

It's impossible to proceed from here without using the recommended updated build settings. I allowed Xcode to update the settings and use the new build system. This fixes the previous error but introduces a few more. These are permission based:

  • unable to write file '/Library/Audio/Plug-Ins/VST3/Audealize.vst3/Contents/Info.plist': fopen(/Library/Audio/Plug-Ins/VST3/Audealize.vst3/Contents/Info.plist, wb): Permission denied (13)
  • unable to write file '/Library/Audio/Plug-Ins/VST/Audealize.vst/Contents/Info.plist': fopen(/Library/Audio/Plug-Ins/VST/Audealize.vst/Contents/Info.plist, wb): Permission denied (13)
  • unable to write file '/Library/Audio/Plug-Ins/Components/Audealize.component/Contents/Info.plist': fopen(/Library/Audio/Plug-Ins/Components/Audealize.component/Contents/Info.plist, wb): Permission denied (13)

To remedy this, I tried looking at the build settings in JUCE to update the build directories. I tried changing the following paths in both Debug and Release for macOS build settings.
Screen Shot 2019-11-10 at 4 49 13 PM
image
The goal was to reset these file paths to the defaults, which build to local user library ~/Library/ as opposed to global library /Library/. To do this, I cleared the fields, which will build to the default path (local user library). Unfortunately, these changes were not persistent, and any time I tried to build or reopened the application, all of the file paths were back to global library, pictured above.

Another thing that I tried to do to fix this was change the build settings in Xcode. When I set the build executable to be AudioPluginHost, I chose to debug at user-level permissions. I switched this to root permissions, but that did not fix any problems either.

image

In my searching online, I have been able to confirm that the current errors are a result of JUCE not having access to write to the destination folders. However, the consistent solution I have found is to change the permissions of the destination folders. I have avoided doing this as it would be something that would have to be individually repeated on each cloned instance (I also just don't think that's great of an idea to lower permissions to write to global directories).

At this point, I've been on this trail of fixing the permissions settings, but it is also likely that upgrading the build systems (due to the old ones being unusable) screwed up something deeper and the permissions are just a side effect. It might be worth looking into the build settings changes in case there are any significant problems there.

Audealize-Reverb (AU) crashes validation

Fails 1 channel render Test at 512 frames (JUCE Assertion failure in juce_AudioSampleBuffer.h:233)

Possible fix: create separate function in Reverb.h to process mono input.

Indication of when reverb or EQ are on in tabs

In the combined version, it would be nice to know if either the EQ or reverb is on just by looking at the tabs. Having a little icon, or color change for the actual tab would be nice. Especially when you first open the app and both reverb and EQ are on (which I don't think they should both be on by default, as it's confusing).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.