The definitive feature request & bug fix roadmap

[DanH]

BUG? DEVELOP BRANCH

The API:

const var tableProcessor = Synth.getTableProcessor("LFO Modulator1");

causes the below error...

 LFO Modulator1 was not found.  {SW50ZXJmYWNlfHwxNTh8NXw1MQ==}

[d.healey]

This post is deleted!

[d.healey]

@DanH This is weird, in the Develop branch LFO isn't a table processor, but in the master branch it is.

[Christoph Hart]

Oh yes that slipped in during the transition. It's definitely supposed to be a table processor...

[DanH]

@Christoph-Hart Cheeky feature request while we're discussing tables - ability to toggle the table playhead line on and off :)

Add to LAF perhaps?

[d.healey]

@DanH

Add to LAF perhaps?

Already there isn't it? https://docs.hise.audio/glossary/custom_lookandfeel.html#table-editor

[DanH]

@d-healey for tables yes but not the playhead as far as I can tell (the white line that follows table positon)

[d.healey]

@DanH This one?

[DanH]

@d-healey oh is that what that is?! :face_with_tears_of_joy:

EDIT: hmmmm.... can't get it to do anything, in fact none of the table laf seems to work in develop...

HiseSnippet 1514.3oc4X0sSabDEdVLaZvMD0zlKppTkVkqLEp0ZBPvJpJFLXpU3GqXxOJQQoC6Nq8D1clkcm0fSTtq22Wg9DzWg9Jzmfpz2fdeufdlYVudow.Nzj1T0UHXO+My24rm4bNCsh3Nj3XdDxXpc6GRPFWwrcelna8tXJC0bMjwUM2BGKHQVZVq1ODGGSbQFFE1PxvXpIQpme+Nqh8wLGxPVHzC3TGxlz.pXH2V0tK02uA1krKMHm1KTqoCmUm6yS.7TvzFEhc1G2grMVp1DlHiKstKUviZKvBRLxXxU4t8a2keHSq+Cnwz87IRhJn1vBoY2f66JQrjKpdWpuaqA9cLBYX1ZXTnfNJbcysntzL9CiFehRf0PKxGOLl3rfWk7vyd7gmQN3MoFdWyrsSDMTLThDaerYSF7gxCCeBxCKstnI90IMqyAMXhxA38IMh.hLKJsjs8bVKZaOysmt3zEgODwBqd3HKerm02XsNqCkQJ6DQ.WaCe9dXe8xtImu+JL2FDheIsofAkiHcnxjlFILGAkyJcC2H7g6hAu+dI9jnaLmk2.Qclyhu2ymo3KKZAOcJGSD5bfR5+DW9Ppn6J9gcwk.EKuWGM+4rrKWYlYtsxL0ujv8H.rRsB4wT4xa8UJRL.7mL+SyobmxRHsI3UkNZNK3G64Fp4Me5bVUrKamt54AUdHjI9bVJ6xKBp9pwJ9zhSYh2UwmEl4DPbceeZXLQolHayFfurPC0SoQWdORzLJN589uw9qM0CN2OZLjp1qF2fDVzc7hQm5mK4RnjFBuL76U9fwamuZu7vfszQOkMXbRDZwCSB2hvRVEJ.1IhmvbOKuUtaq36Wx9nFMlW8bFNPDwcl23Xv8HNhROwNKy8Pp6.L2kP6zUHOOnQ9.TXwYayEjcXkj.Yphupn0eUjm2HkIKBEw8gx.iTrroPzYYXIVRvdDHl2C6mPxTDpNdxxulmd427cGbz0DyoHm0jQE6DRXmVQYTZgTn77DonB1dgp37zoEmUIpHJTB9xlp2qfT.Ne6QWr.iLRLWdgxm7o2NqrviWs52dP+6eq5J5G9X99U8h8huU8Ym8fjclcwCRp16tcprfV9JjGtPUVip3kzza+7paLK6Q6VeYMM7KuYkKcUMs1GT.ufF3WME3s8otjHEx+Hy6x36MBfitey0jXG5ujFJfvSHIRPkQdi0H8f995lUSYtFIdeAOTEqBB4LYfyn34FsNJaCq8c05mQ7i3ZpzyLFs5USmjlw40g0BG70poqrq8lM1wZKtahOFRPpfFbtEr3RGeL5XoQTAIPycdIafyeHY6jDK3oBjt1DnbNwUN2HG3DlF6BqSe4K1vKwh9xjvKoT.EPcck0.0cqxMM0OCkEBaSegJr+xq+Sa7au36uSP9AtPn.7Q4m+JNwyidjZRInjPPr.vTy.X.JjwmZd+XhkKwCm3Krh2GVGeJaeh6tbk9n2bHCXTmAAr7y+HG5KUfDv4GzPNLACbj94A06kghFW3dMyVTgS2Qi2IFAdkGneOi2zQLm1bcOOnr6PvNoYiG89edx7P4xZn7El5I5FF.giz.pH54J+xTwCO.YkoPky3BA+x3dgfvw9BAFEF6Hxnu.f8nlvdxOnu.v3lq+Yuwmo329SmEFu.54bMkqpgoorraZT6uT.9bAViHxAIDlSNlu9NxTjlCyvp8C0dHtGwiGEj1pIUyOu1ljNvFkeA2k.Usg615jOarc.mK5RYcNYh20qAWqIbclrOja9EoUWbrbtFXrp7KScUOhAX4eqF5sgFFplxFOwbI09mS9M24cCM5cWFyDichsL4IKKQlF8AdaGMhyRg+O.hOyFkE9+Yix6wSDPogsvvbTxw31NInMzIxg.HgwH9xqX.iCJMUQaKoUUUHLWEwwvSpvJRZiTgUFH7ej8H.6DwelidZe4AuKq3.9MS8OVaJysjzVYi4aZB2lUNYJ8YNNxv8WWAgFsMyeAr4lW.aV3BXyhW.aV5BXyst.1r7YZibDiURfVJ5ih.iVqqqraj0Txn.5OADkfnSL

[UD AUDIO]

Feature request:
What about multi user functionality for live collaboration in HISE using a VPN etc?
There is a new blender add-on for this or unreal engine for example.
https://ubisoft-mixer.readthedocs.io/en/latest/index.html

[sakorada]

BUG!
On Window
Can't Compile 32bit VSTI with Latest Develop Branch
( 3601a8620539934ceb33df48237cec9409de8752 )

[DanH]

BUG?

In Ableton when using a Macro control on a knob on the UI (in this case the macro is an LFO) the Macro data is being sent to Ableton's 'changed state' info. This makes Undos impossible as the data is continuous.

I guess in theory it's all working correctly - the LFO moves the UI control, and because the automation parameters are in use on that control, if the control moves it will update the automation lane and data.

Can there be any workaround that prevents automation data being sent when a UI control is be controlled by a Macro?

[ustk]

BUG FROM LAST COMMIT

@Christoph-Hart Updated to last commit and got an error for timer objects:

Interface:! ReceiveRecording.js (7): Unknown function 'stopTimer' {SW50ZXJmYWNlfFJlY2VpdmVSZWNvcmRpbmcuanN8MTM5fDd8MjM=}

Context:

const var timer = Engine.createTimerObject();

timer.setTimerCallback(function()
{
	this.stopTimer(); // Throws an error and even crashes Hise after a moment
});
timer.startTimer(2000);

but timer.stopTimer(); works inside the CB. Strangely, it was also working before the last commit...

[Natan]

@DanH said in The definitive feature request & bug fix roadmap:

BUG?

AudioWaveform now has a nice green box around it in Develop Branch that can't be changed / removed

@d-healey said in The definitive feature request & bug fix roadmap:

@DanH I think that will disappear once you compile. It's the same for tables.

Nope, The Green Box (Around The Audiowaveform)
Still Shows Up And Won't Hides On Compiled Plugin.

AudioWaveform Connected To Sampler

[MikeB]

@Natan Workflow until the BugFix
Put it in a panel and give it the position (-1, -1, panel.width +1, panel.height +1)
So the frame disappears behind the panel

[A Former User]

This post is deleted!

[Natan]

@MikeB No Need For That, I Hacked The Entire Border On Source Code, To Make It Minimal, Waiting For A Bug To Get Fixed For PopUp's, After That Going To Make My Own Changes To The Source Code :)

My Version :) Minimal | Flat | Elegant | Eye Catchy
Sampler, Has No Dragging Start/End Points,
@Christoph-Hart So I Believe This Can Be A Request To Having The Choice To Selecting Border(true) Border(False)

[Natan]

FeatureRequest:
An Option To Enabling / Disabling The Borders Around The AudioWaveform

Sampler Has Nothing To Do With It!!! So Why Not?

[A Former User]

This post is deleted!

[ustk]

I'm sure it is already hard for Christoph to follow all the requests we do, so I personally think it might be a good thing for all of us to follow this rule:

@Christoph-Hart said in The definitive feature request & bug fix roadmap:

Hi everybody,

... Any discussion about a certain bug / feature should be a dedicated thread (you can add a link to the discussion thread in the post).