Waveform 12 issues (only a couple)

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

1. The program crashed when adjusting mix group options.
2. Mute/Solo stopped working as expected with folders until I cleared all. There may be something I don't understand here.
3. Dragging multiple files (layers) from Finder to a Drum Sampler pad works fine, until it doesn't. The files won't be accepted. If I close the Drum Sampler, then reopen it, it works fine again.
Top

Post

I should follow up and say that .53 seems to be pretty darn stable. Mac.
Top

Post

I'm having problems adding plugins by dragging them into the plugin window - I love how I can do this in Waveform as it enables me to create a more focused collection of plugins (which I then tag as I add them) and exclude the ones I rarely use. This still works fine in W11 but when I try to do this in W12 I get this every time I try:

Image
Top

Post

Any help as to this bug? I can workaround it by doing all the plugin adding in W11 but it looks like something needs fixing in W12
Top

Post

What is the bug? I'm afraid I can't see any issues or detect what you might be referring to with that screenshot.

Rather than maintain a "focused" list of plugins under Settings I've always let it detect everything but then turned off the "Show" setting for any duplicates as well as any plugins known to not work in Waveform. I also use the "Custom popup menu" option for the plugin selector setting so I can manually arrange the plugins I want to have listed into categories that make more sense to me than letting it automatically list them by vendor or other criteria.
Top

Post

fde101 wrote: Tue Apr 05, 2022 9:58 am What is the bug? I'm afraid I can't see any issues or detect what you might be referring to with that screenshot.
It's not scanning in the plugin I drag over, instead it's just adding a path to it for some reason (in red at the bottom) but I can't use the plugin added
Top

Post

I often get those red paths when plugins are broken or incompatible. In most cases I have other versions of the plugin (VST as opposed to audio unit for example) which then do work.

Probably not related, but are the paths containing those plugins listed in the plugin folders under File Locations? Just a thought.
Top

Post

fde101 wrote: Tue Apr 05, 2022 11:26 am I often get those red paths when plugins are broken or incompatible. In most cases I have other versions of the plugin (VST as opposed to audio unit for example) which then do work.

Probably not related, but are the paths containing those plugins listed in the plugin folders under File Locations? Just a thought.
It shouldn't be, as the same plugins work in W11 when dragged in, and I tried this with several in W12 and they all failed to add, including different formats of the same plugin
Top

Post

Hello I try to use this plug in in waveform 12 and it throws this error

Started validating: /Library/Audio/Plug-Ins/Components/Torpedo Wall Of Sound.component
Random seed: 0x641c305
Validation started
Strictness level: 5

Starting tests in: pluginval / Scan for plugins located in: /Library/Audio/Plug-Ins/Components/Torpedo Wall Of Sound.component...
Num plugins found: 1

Testing plugin: AudioUnit--2f1fd515-35554665
: v
Completed tests in pluginval / Scan for plugins located in: /Library/Audio/Plug-Ins/Components/Torpedo Wall Of Sound.component

Starting tests in: pluginval / Open plugin (cold)...
!!! Test 1 failed: Expected value: , Actual value: No compatible plug-in format exists for this plug-in
!!! Test 2 failed: Unable to create AudioPluginInstance
FAILED!! 2 tests failed, out of a total of 2

Starting tests in: pluginval / Open plugin (warm)...
!!! Test 1 failed: Expected value: , Actual value: No compatible plug-in format exists for this plug-in
!!! Test 2 failed: Unable to create AudioPluginInstance
FAILED!! 2 tests failed, out of a total of 2
*** FAILED
Top
Post Reply

Return to “Tracktion”