Wavetable Scope - Bugs (?) and Troubles

Post topics about HALion scripting.
Post Reply
Junior Member
Posts: 93
Joined: Thu Feb 16, 2012 12:07 am

Wavetable Scope - Bugs (?) and Troubles

Post by Fantacyzer »

The "Play Data" field of the wavetable view control does not take any scope from higher UI hierarchy levels into account. It also does not accept inputs from script variables, even if the field allows the selection of a variable. It only accepts direct path definitions.

So if I have different wavetable layers and want to select between them, I have to directly set up the view for every layer manually by now. But I think this doesn't go along with the principal Halion design concept. The sample view control for example works alright with scope and/or ariable definitions.

Is this by design (and if so - why?) or is this a (known?) bug?

I'm intensively working with Halion UI scripting and frequently found situations, where the scope concept is not consequently implemented. In most situations I can work around with path constructions via script variables, but this doesn't work with wavetable views.

The attached demo program shows 3 situations at the same time:
- 1st wt view with direct path definition. This is the only visible one.
- 2nd wt view with the same path definition via a script parameter. Invisible.
- 3rd wt view with the same path definition, only splitted via group scope. Invisible.
- wt view bug -.zip
(82.7 KiB) Downloaded 122 times

User avatar
Posts: 331
Joined: Sat Jan 17, 2015 8:20 pm
Location: Ventura, Ca

Re: Wavetable Scope - Bugs (?) and Troubles

Post by abject39 »

Good catch. I'm finding issues with the wavetable data as well. Hopefully this can get fixed.
My vision is uncompromising: to transcend my clients dreams by mesmerizing their audience with the world's finest audio arrangements and products.

Post Reply

Return to “Halion Scripting”

Who is online

Users browsing this forum: No registered users and 2 guests