It seems that waveform is only partially identifying as waveform. Although the manual list scripts commands such as Waveform.isMute, they do not function. Users must format commands using "Tracktion," rather than "Waveform." For example: Tracktion.isMute.
Secondly, the plugin Muteomatic does not work properly in Waveform. It does not recognize when Waveform is recording. The author at Sound Radix recommended I rename Waveform, "Tracktion Waveform." That fixed the problem (although it caused other problems). It made me wonder if this issue was also being caused by Waveform somehow identifying as Tracktion. It also made me wonder if this could be causing other known problems.
Waveform Identity Crisis
-
- KVRian
- 1272 posts since 11 Apr, 2002 from Nashville, TN
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Thanks, that sounds like a mistake, they should still be referencing Tracktion. Although it's probably possible for us to support both I think that would be confusing.Rock wrote:It seems that waveform is only partially identifying as waveform. Although the manual list scripts commands such as Waveform.isMute, they do not function. Users must format commands using "Tracktion," rather than "Waveform." For example: Tracktion.isMute.
Hmm, I think the problem is that Waveform isn't identifying as Tracktion. I'm not sure what DAW specific functionality Sound Radix has implemented but I don't know whether adding support for a new "Waveform" DAW type would be better or simply getting Waveform to be identified as Tracktion in the framework they use.Rock wrote:Secondly, the plugin Muteomatic does not work properly in Waveform. It does not recognize when Waveform is recording. The author at Sound Radix recommended I rename Waveform, "Tracktion Waveform." That fixed the problem (although it caused other problems). It made me wonder if this issue was also being caused by Waveform somehow identifying as Tracktion. It also made me wonder if this could be causing other known problems.