Jump to content

Search the Community

Showing results for tags 'spectral tools'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to Opusmodus
    • Announcements
    • Pre Sales Questions
  • Support Forum
    • Support & Troubleshooting
    • OMN Lingo
    • Function Examples
    • Score and Notation
    • Live Coding Instrument
    • Library Setup
    • MIDI Setup
  • Question & Answer
    • Suggestions & Ideas
    • Zoom into Opusmodus
  • Sharing
    • Made In Opusmodus
    • User Extensions Source Code

Categories

  • OMN The Language
  • Tutorial Guide
  • CLM Examples

Categories

  • Getting Started
  • HowTo
  • Live Coding
  • Music Theory and Analysis
  • How-to in 100 sec
  • Presentation
  • Convention

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Gender


Location


Interests


About Me

Found 2 results

  1. Hello, I am trying to find different ways of importing partials/frames data into Opusmodus. I am currently trying to use spectral analysis to analyzes certain music/audio phenomena I haven't really seen analyzed before to adapt into my own composition process. The sounds are generally archival or things I have synthesized on the computer through software myself (in .wav format), and are usually between 1 - 5 seconds in length. Is this a good length of time to analyze the spectral data of sounds? I just wanted to understand the following information about spectral tools within Opusmodus. I really would appreciate it if anyone could help me out. 1. Is it only Spear that we can use for spectral analysis? Is something like Audiosculpt also useable? 2. Looking at Spear, when we explore the data, which of the following export formats do we use: 1. Text - Resampled Frames, 2. Text - Partials, 3. SDIF 1 TRC - Resampled Frames, 4. SDIF 1 TRC - Exact Interpolated, or 5. SDIF RBEP? 3. Once I have the data in the correct format, I think I want to create a library of the datasets I important so that I can reinterpret them in the future. If I want to use the "get-tuning" function, for example, and then mapping it across certain instruments within my planned orchestration. What would be an effective way of doing this? One of my main challenges is finding a way to keep all my data organized every time I want to use Opusmodus for a new project. I still find myself using Opusmodus in little blocks as I compose, and I hope to eventually get to the point in which I can compose entire pieces using only Opusmodus. I really appreciate your help.
  2. We are excited to announce new functions in Opusmodus and we hope you will find them helpful in your work. NEW: Spectral Composition Tools ;;; Spectral Tools (import-spectral-spear "Imports spectral data from the SPEAR application.") (highest-partial "Returns the highest partial value of a given collection of partials data.") (lowest-partial "Returns the lowest partial value of a given collection of partials data.") (normalize-partials "Returns a float-vector with the amplitudes normalized so that their magnitudes add to 1.0.") (partial-divide "Divide a list of partials into sublists of a given length.") (partial-row "Converts frequency data of partials into a unique pitch row (each pitch becoming a root).") (partial "Returns partials of a given type of data.") (partial-remove "Removes partials from a given type of data with its value (min, max).") (partial-sort "Sorts partials of a given data type.") PITCH-ROW This function allows a pitch series to be altered into a unique pitch row (each pitch is quasi a root). (setf mat (vector-to-pitch 'piano (mod-sine-waves 4 64 4 0.6 :modulation (gen-sine 64 1 '(0.5 0.2 0.1) :phase 60)))) => (f4 cs6 gs7 b7 f7 c7 bb3 g3 e2 a0 bb0 a0 fs4 fs2 fs2 d6 bb6 c7 a0 b0 bb0 a0 b7 gs7 c7 bb7 bb4 b2 b4 a0 a0 d1 eb6 bb2 d2 e3 b6 eb4 d3 c2 bb0 cs7 a0 a2 cs3 f7 c7 e6 d7 eb7 f2 a0 g7 gs7 a7 c5 cs1 c5 bb7 c8 e6 b2 bb3 fs6) (pitch-row mat) => (f4 cs6 gs7 b7 c7 bb3 g3 e2 a0 fs4 d6 eb6) More options have been added to: CREATE-LIBRARY Another option we have is to save the library output as a file directly into the DEF-LIBRARY directory. To do that we use the :file keyword. The :file name must be a string "name-of-the-file". (create-library 'Binary-Rhythmics '4-bit-binary 'bin (combination2 4 '(1 0 1 0)) :file "4-bit-library") We also can add an annotation (e.g. explanation or comment) by using the :note keyword: (create-library 'Binary-Rhythmics '4-bit-binary 'bin (combination2 4 '(1 0 1 0)) :file "4-bit-library" :note "Library explanation or comment") The next time we open the application the file will load at the start and will be ready for use. LIBRARY (library 'binary-rhythmics '4-bit-binary 'bin15) => (1 1 1 1) (library 'binary-rhythmics '4-bit-binary nil :random 10) => ((1 1 0 1) (1 0 1 1) (0 1 0 1) (0 1 0 1) (1 1 0 1) (0 1 0 0) (0 0 1 0) (1 0 0 0) (0 1 1 0) (0 1 1 0)) (library 'binary-rhythmics '4-bit-binary nil :collect '(1 2 3 2 1)) => ((0 0 0 1) (0 0 1 0) (0 0 1 1) (0 0 1 0) (0 0 0 1)) (library 'binary-rhythmics '4-bit-binary nil :collect :all) Above there is an example of a defined library file followed by four possible output options. The first is to output a single library entry. The second picks 10 entries at random. The third allows an integer list to determine which entries in the library list can be collected together in a set order. The fourth :all will collect the entire library.
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy