musescore / musescore/MuseScore

Audio is not detected by Izotope VST plugin AI assistants

Open
#13,038 4 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Aug 31, 2023.

P1 VST
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Describe the bug
When using Izotope VST plugins, audio is not detected by Izotope AI assistants. Audio is detected by individual Izoptope plugins, e.g., Neutron Equalizer, just not the assistants.

To Reproduce
Steps to reproduce the behavior:

  1. Open an existing score or create a new score.
  2. In the mixer, under one of your instruments, under audio FX, add Izotope's Neutron 4(or Ozone Pro, any plugin that comes with their assistant)
  3. Begin playback in MS.
  4. You will see the audio being detected in the main Izotope plugins (e.g., the equalizer) (see screenshot)
  5. Now switch to the assistant view in the Izotope plugin.
  6. It never detects the audio (see screenshot)

Expected behavior
Izotope assistant view detects playing audio. (see screenshot of it working in another program)

Screenshots
Audio detected in basic Izotope Plugins (e.g., equalizer)
detects-audio-in-basic-plugins

Audio not detected in Izoptope assistant
does-not-detect-audio-in-assistant-view

Example of proper detection in different program
example-of-detetcting-audio-in-different-program

Additional context
I initially contacted Izoptope support to see if they had a fix. Their response was basically that it's not officially supported in MS. They said that when the audio is being fed to the plug-in but the assistant is not hearing it, it is often related to the plug-in not being able to access its resource files. They suggested running MS as an administrator. I tried running as an administrator but had the same result.

Platform information

Windows 10
MS Build: MuseScoreNightly-202208260457-master-c4515b8-x86_64

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.