@ulrik
Oh yes I saw that as well. Looks like a really clean solution!👍

@observantsound no it will be useful for people asking the same question

@Matt_SF Sure.. Thank's buddy.

@Christoph-Hart My mistake.

On Windows, if the monitor has a 4k (or more) resolution, and using a resolution factor higher than 100% for the Operating System , that happens. I think it is a Windows thing.

alt text

@DanH I got the pitch partly working but it's glitchy and another member of the forum has shared some of their work on the time stretch with me but it has some of their specific C++ stuff in it which I need to make more generic. I haven't had time yet to really dive into it.

I think I already shared my pitch shift node in another thread.

@Lindon Ah , I neglected that, let me try again. Thanks!

SOLVED> That was indeed the problem :)

Its a bit much to take in debugging the first time.
I found an assertion failure for jlimit in MathsFunctions (lower value is bigger than the higher value).
But I still try to figure out where this jlimit belongs to.

@d-healey Thank you, David. I have referenced in the documentation. Cheers.

@Dan-Korneff

The latest trend Dolby ATMOS!

AFAIK, it's almost 10 years old but I've been hearing this more and more everywhere lately. Very popular these days. Albums, Movies, TV Serries...etc. it's been everywhere.

And of course it would be great to see 7.1.4 Channel Set here.

@orange Indeed , was set to use iPP which I do not have installed :)

@Matt_SF Thanks! Yes, I was pointed in this direction last time. I've got to be making a stupid mistake. I'm nit at my computer right now either but when I am I will post where I'm at with it.

Any help in the meantime is appreciated!

@Matt_SF Thanks :)

@lalalandsynth Generally you supply Avid with your iLok user account id (probably an email or username), and Avid then put the necessary licenses into your iLok account. I assume you have done this already if they gave you the dev version already. You may need to update your iLok with your new licenses, and possibly activate them in the iLok software.

Then when Pro Tools loads it checks the iLok for a license - if your iLok is plugged into your machine of course...

You might have the option to assign the licenses to your machine, you should check (means you don't need the iLok).

@Christoph-Hart Thank you, Chris.

@Lindon yes found that too. Ok great, hopefully that's done!

Cheers mate

@toxonic

Okay so theres no validation going on, and some maybe incorrect naming, and an incorrect call to writeObject: so start like this:

//function store inline function writePreset (fileName, myJSONData) { local PresetFile = PresetDir.getChildFile(fileName); if (PresetFile.isFile()) { PresetFile.writeObject(myJSONData); }else{ // display an error here..... }; }

So the most obvious problem is you were trying to save an array when the command expects JSON, so you should fix that at least...

@Christoph-Hart Mmm... so this is the optimisation companion of setOpaque if I understand well