Export tool

[d.healey]

Anyone else tried exporting multiple projects at once?

[Natan]

@d-healey Sir
Is It Possible To Add A Popping Up Folder To The Projects, So Once The Export Is Done, The Package Folder Shows Up?

[d.healey]

@Natan I think this would be annoying if you had many projects queued up. What might be better is if I add an option for a global output folder which you can set, and all packages will be dumped there and then once the queue is complete it will open that folder... open a github request for this if you like the idea :)

[Natan]

@d-healey Yeah, Thats A Good Idea
Will Do

[Natan]

@d-healey Sir, I See This Error, But Export Tool Does Its Job very well.
It's Not New, I Seen This From Day I Rebuilt My Hise. These Errors Shows Up In Console In Red Color.
Any Advice?

10:41:51.747 › stderr: 
JCRev::setT60: argument (0) must be positive!
JCRev::setT60: argument (0) must be positive!

10:41:51.768 › stderr: 
PRCRev::setT60: argument (0) must be positive!
PRCRev::setT60: argument (0) must be positive!
JCRev::setT60: argument (0) must be positive!
PRCRev::setT60: argument (0) must be positive!

10:41:53.237 › stderr: 
JCRev::setT60: argument (0) must be positive!
PRCRev::setT60: argument (0) must be positive!

[d.healey]

@Natan Do you only see them when you open a specific project or are they always there?

[Natan]

@d-healey When I Start Exporting A Project

[d.healey]

@Natan I have no idea. Those messages come from the compiler, not my app. Do you see them when you export directly from HISE?

[Natan]

No I Don't See Any Errors With Hise It Self

[d.healey]

@Natan You'd see the errors in a terminal window or visual studio's console, not in the HISE console.

[Natan]

@d-healey Sir, In Terms Of Performance, It Does Nothing At All, And Exporter Tool Does Its Job Very Smoothly.

It Happens On Mac Too, Since I Built The Version HISE-61257a81932a80064af8d2949e882f1a5ddb9138

Screenshot:

[d.healey]

Is that the latest scriptnode? When you export from HISE do you see these errors in Xcode, Visual Studio? Or any terminal windows that are opened?

[Natan]

@d-healey This Is My Commit HISE-61257a
I Don't See Any Errors While I Export in Window
But On Mac, I Have Some Defficalties To Export Which Does Nothing And Push Me To Use HET.

[d.healey]

@Natan said in Export tool:

@d-healey This Is My Commit HISE-61257a

Do you mean you made a fork? I'm not seeing this commit number in the main repo. - https://github.com/christophhart/HISE/search?q=61257a81932a80064af8d2949e882f1a5ddb9138&type=commits

[Natan]

@d-healey Its Here:

• fix normalisation bug when looping inside samplestart mod
  https://github.com/christophhart/HISE/commit/61257a81932a80064af8d2949e882f1a5ddb9138

[d.healey]

I'm pretty sure the errors you are seeing come from HISE, judging by the lines before and after. So there is nothing I can do :p

[Natan]

@d-healey
Another Interesting Thing,
Error Doesn't Show Up While I Compile Instruments, It's Only With Plugins :)

[ustk]

Looks like a scriptnode issue. JCRev and PRCRev are STK nodes
T60 resembles to a reverb time argument you try to set negative...

[Natan]

@ustk Excellent
Just Removed Those Nodes, And Errors Gone :)

@d-healey Sir, Check This Out
@ustk said in Export tool:

Looks like a scriptnode issue. JCRev and PRCRev are STK nodes
T60 resembles to a reverb time argument you try to set negative...

[Natan]

Not Sure, But i Guess These 2 Nodes Was Working, Just Fine, With Out Trowing Errors Into The Exporter Tool.

No Matter What Value I Set In The Plugin, As Far As I Use Those 2 Nodes, Errors Comes Up.
@ustk Can You Confirm This Sir, If This Broken Or Something?
Thanks