Rev 1547 troubles

[zeoka]

Hi
I get issues with restricted dll or ctrlr instances : i receive correctly sysex with chksum from device and animate ctrlr knobs normally but i send 00 instead of chksum

Sometimes when i dump prog + 24 sounds + 4 fx’s (from synth) : Ctrlr bug at fx1 and send data infinitely to synth and freeze while this create an infinite fast flux of chksum errors on the synth. For now i don’t know what’s hap. May be my linked fx modulators do a feedback in some cases ? I will search more to be more specific( in standalone i lost my midi monitor)

[atom]

I’d love to help but i don’t understand what you are trying to say:
“Ctrlr bug at fx1 and send data infinitely to synth and freeze while this create an infinite fast flux of chksum errors on the synth”

what is FX1, nothing will be sent “forever” unless you told Ctrlr to do that, a feedback loop might happen not only due to bugs in Ctrlr but due to bad Lua method, you need to make sure that your methods are loopback safe, create some checks for recursion etc.

[zeoka]

1)on last nightlies the sysex editor seems to send 00 instead checksum

2)When my panel receive whole prg(prg,24sounds,4fx’s) ctrlr freeze at fx1 dump and it seems ctrlr send unknown data (because it freezes i can’t see what it sends)
The data ctrlr sends causes device checksums errors to the infinite. i must cut ctrlr with the Windows task manager
Some dumps are working normally and some crash ctrlr

Edit : i got the loopback !

I see it at the end of the log file
I need to check where is the failure

• This reply was modified 10 years, 7 months ago by zeoka.

Attachments:

You must be logged in to view attached files.

[zeoka]

CtrlrProcessor::setParameter value out of bounds index=259 value=6.2

vst index ?

i don’t see something wrong in those mods…

[zeoka]

Well it seems my panel is correct
I’ve tried with new RA panel :
3 combos “tuned chnl ” : 1 for sound 1 , 2 for sound 2…..
1 = f0 3e 11 00 20 20 00 00 58 xx w6 f7
2 = f0 3e 11 00 20 20 01 00 58 xx w6 f7
3 = f0 3e 11 00 20 20 02 00 58 xx w6 f7
I turn the device knob for the 3 params
And you see the ctrlr result on the pic you see also it sends the chksum value to 0 when ctrlr receive device values

Ctrlr can receive only the first “tuned chnl” not the others and create a loopback
note the sysex returned are not on the right sound ( see the sound number byte)

there is no methods attached to my 3 combos

Attachments:

You must be logged in to view attached files.

[atom]

yeah the checksum stuff looks to be broken due to the Global Variables changes i made, i’ll fix that ASAP and upload a new build.

[zeoka]

Hello Atom ,
Just tried the 1577 rev !
You have repair the checksum

But the loopback/crash continues when Ctrlr receives dump
Again at FX1 dump….I explain : dumps are a sequence with RackAttack and crash at fx1
i don’t see anything in LUA editor

During the dumps there is an “animation” : the edit 1 button is hidden just time to
get sound dump and it is shown then edit 2 button is hidden …. etc
the sound layers are switching too and after fx’s dump return to initial layer whatever it is.
At the FX steps the “FX1 Type” combo is hidden and shown as edit buttons do etc..

The crash happened exactly when the FX1 must re-appear and it do not
then ctrlr saturate the device with midi messages an crash when i try to stop it

Some time ago this crash has definitively killed ctrlr x64 standalone i use other versions : vst & 32 bit i think i must re install the Windows but don’t want

I really don’t know what i can do

[zeoka]

Hi Atom
I think it is possible to reproduce my loopback with reaper and loopbe (if you are not so affraid ! )
The panel receives correctly some patch and some not…
Like the CR-78 program …..
First I will re init the RackAttack memory bank with @waldorf factory kits, check if ctrlr works and go back here.. (May be my device has wrong data in memory ?)

[atom]

If you can explain to me what should i set up and how (assuming i don’t have the Waldorf RA) i’ll give it a go, i’m here to help.

[zeoka]

Thank you

The RA programs are in midi file format so with reaper it’s possible to send to Ctrlr single programs and see what’s happen. It will be slighty different because
there will not the request by ctrlr and may be the loopback will not comes…
But then that could help to find where is my error in LUA
You need the panel , i return here at the end of afternoon i will try myself before
Again thank you

[zeoka]

Well
I’ve tried to reproduce my loopback/crash and it does since the first program launched !
As you see here the combo “fx1 type ” is hidden
If i put the midi file and the panel to my dl section , can you access to it ?

Attachments:

You must be logged in to view attached files.

[atom]

How can there be a loopback problem if there is no input ? based on the screenshot there is no defined MIDI INPUT device.

[zeoka]

Yes of course
The loopback will be visible in the log file because of crash
See the log file i uploaded post above
the loopback is at same place than now

• This reply was modified 10 years, 7 months ago by zeoka.

[atom]

Yout log show ONLY outgoing messages, that means it’s not a loopback problem (a feedback loop) there are no IN events triggering OUT events, it’s most likely some Lua method you wrote that is falling into an infinite loop and is doing that.

[zeoka]

Yes i think too
Normally there is no outgoing messages
I’ve uploaded the panel and the midi file here in my dl page
May be a “layer change” script …but that was working before
I don’t want to change so much the panel. i’ve changed many things yet to improve ,
but i do another panel with better methods quietly and just want render this one usable to use it in a host and follow the “midi labrary” methods to create patches

[atom]

YOur Lua code is unreadable, i wanted to help but i had to spend 10 minutes closing all your method tabs (i need to make a close-all button).

I can’t read through your code, based on what i’ve seen you’ve made more then one mistake just based on the amount of code you copy/pasted. You can’t expect anyone to be abgle to help with that.

If you can find a clear bug in Ctrlr itself and demonstrate it on a new panel, i’d love to help and fix it.

[zeoka]

Why close them ?
The panel works , send program sequentially , automation works , lighter than the v1.1
in plugin mode , but crash at a step when it get fx dump
-I’ve done “midi Library ” snapshots : possible this cause my bug ?
– i’m aware of any error you see or improvement that can eventually solve my bug
– i will check the panel with an old ctrlr to see what’s hap and back

[atom]

I close the tabs to see the one i’m working with, you opened so many of them that the name is scaled down and i can’t see anything.

snapshots will not cause any issues like that, they’re just static valuetrees

[zeoka]

It works without issue( all 50 progs checked )on the 1460 i’ve just tried WITH REAPER and the MID file
Something is changed in ctrlr after this version ( i don’t say at all my lua wasn’t crappy 😉 )

• This reply was modified 10 years, 7 months ago by zeoka.

[zeoka]

Ok for snapshot !
I don’t use lua tab, i use the left menu that’s why there is so many tabs opened

[Author]

Posts