MIDI Kinetics Forum

I've added midi functionality for selecting CC and note triggering of the ADSR.
I've also added fx labels.

kraftf wrote:Ok Antonio thanks for granting permission.
So here is the file guys.

No problem
cheers,

Antonio eres un makina!!

Siempre con lo mejor!

Un saludo,

Thopa

thanks antonio and thanks kraftf!

kraftf wrote:I've added midi functionality for selecting CC and note triggering of the ADSR.
I've also added fx labels.

Unfortunately its crashing and its crashing the editor as well.
Very disappointing how the parser works. Many times it doesn't let you debug your mistakes, it just crashes.
During my work on this template I had to save 25 different versions to avoid crashing. I am suspecting it has something to do with how the large string variables are being handled.

Anybody else that has a clue on whats going on?

kraftf wrote:

kraftf wrote:I've added midi functionality for selecting CC and note triggering of the ADSR.
I've also added fx labels.

Unfortunately its crashing and its crashing the editor as well.
Very disappointing how the parser works. Many times it doesn't let you debug your mistakes, it just crashes.
During my work on this template I had to save 25 different versions to avoid crashing. I am suspecting it has something to do with how the large string variables are being handled.

Anybody else that has a clue on whats going on?

Can you give the steps to reproduce the crash so we can debug this ? Maybe send a mail to support @ liine, along with a crash log and the template.

axel_liine wrote: Can you give the steps to reproduce the crash so we can debug this ? Maybe send a mail to support @ liine, along with a crash log and the template.

No I can't give you any steps. The second template was just working during the proccess of its construction. When I try to reopen it just crashes ipad or the editor.
I was able to do some reverse engineering and correct it.
One reason I found out crashing the template was the insertion of 2 global variables called fxtype1 and fxtype2. Maybe there were too many variables but again there are no guidelines regarding the number/size of variables you can use.
Anyway you can check the second file I have uploaded.
Soon I will be uploading 2 new versions one working and one crashing Maybe you can check them out too.

Ok, I managed to pinpoint the crash in the "stretch" function used in your variable autoVal. This will be fixed in a coming update, we already have one in the approval pipeline so it might be in the next, we'll let you know.

I was able to assemble a working version.
@axel thx for the info about crashing. Actually I never messed with this variable. It was already present in Antonio's template.

axel_liine wrote:Ok, I managed to pinpoint the crash in the "stretch" function used in your variable autoVal. This will be fixed in a coming update, we already have one in the approval pipeline so it might be in the next, we'll let you know.

Hey Axel, Interesting, I have not experienced any crash during 2 years with this template, autoVal variable has be always there , so I am really interested to know more about that bug, it due to the stretch function? any info would be appreciated.

Thank you,
AB