DSP Robotics Support

RJHollins wrote:Maybe I should post the FSM file of the test module for other's to test ... I'm just a bit embarrassed that the look of the test is very ... hmmm ... amateurish

I did suggest that about 6 pages ago RJ...and still think its your best way forward.
If fsm is hard to read....take time to fix it...put in some comments...

You just need a basic vsti module....shouldn't take half an hour to rig up....
These guys need to see your "system", from start to finish....

Trog or nubeat7 will probably spot the error before anyone has time to test it..

Hi Billv ... you are correct ... just got thrown for a curve when we thought we were having some success.

I'm posting the 'test module' that I last used. It ain't to pretty on the outside ... but this problem has been UGLY

What I've done:

The Ruby module is the 2nd to last design by NuBeat. [not the very latest just posted].

I expanded the number of arrays to accommodate the need of my project ...

I have 3 included Selector pull-downs to monitor the end result. One selector is from SM [testing issues brought up regarding these selectors].

When first running the test ... the Menus are empty, and should show 'blank' and appear frozen [ok].

After hitting Save, the process ... then re-load should fill the Menus.

NOTE: I altered the 'file mode' to Raw Binary.

The ULTIMATE test needs to be as a VST plugin, as this is the format the project is designed for.

***** There is something that I've done that is not right ... I just have not figured it out, as every testing and variation has worked on my XP-32 system, but has failed on [now] 3 computers of my BT'r [all 64 bit].

Just to get the ball rolling ... here's the FSM:


I'd really appreciate anyone to please test this and post back findings INCLUDE your OS's [32/64]
HUGE THANKS !!!

XP 32 bit.
Opened fsm and hit save...here's result...




Then i changed the values in selectors, hit save and got this....


Same data....nothing new has been saved......

Then i changed the values in selectors, hit save and got this....

Hi Billv ... the values that you changed ... did you go into the INPUT module and change any of the values in the text array windows ???

Another question, when you first ran the test, where the 3 Selectors 'blank' ?

Then after Save, did the 3 Selectors work ?

RJHollins wrote: did you go into the INPUT module and change any of the values in the text array windows ???

Yes.

RJHollins wrote:Another question, when you first ran the test, where the 3 Selectors 'blank' ?

No.

RJHollins wrote:Then after Save, did the 3 Selectors work ?

No change in selectors.

tested here on win 7 64 bit with renoise 2.8 32 bit and everything worked fine..

ps: also when changing the entrydata..

RJHollins wrote:Another question, when you first ran the test, where the 3 Selectors 'blank' ?

@billv: i think rj meant when testing as vst

but what i saw after putting in a editbox for manipulating the first line data of the middle selector that the fs selector didnt update properly (while the data IS updated ) but thats just a missing trigger from the items list to the label of the selector..

here is a fast hack including the test file scenarios from my last example plus the trigger fix at the fs selector(the middle one)

Nubeat7 wrote:

RJHollins wrote:Another question, when you first ran the test, where the 3 Selectors 'blank' ?

@billv: i think rj meant when testing as vst

ahhh. ... just looked inside and I see I left all the OUTPUT arrays filled Sorry Guys ... so much testing ! So yeah, the Selectors sill NOT be blank. again ... sorry 'bout that.

Was trying to test 'two birds half stoned'. We had mention of FS/SM issue in certain DAWs, so I wanted to have a sampling there.

The 'other' issue dealt with the actual data been Saved.Re-loaded, and stuffing the Selectors.

NuBeat ... as you would be quite familiar to this particular RUBY code and since it worked on your system, can I venture that my expanding the array list is correct and proper ?.

Also ... might you have tested as VST ???

---- I sure everyone is busy, at least on their own projects and life, but it is very appreciated taking the time to test this routine due to the issues I've encountered.

PLUS ... for those unfamiliar [as I was], this Marshal routine [concept wise] can be extremely useful when handling multiple arrays of various size [length]. I think worth the time investigating !

Please ... more testers

Nubeat7 wrote:but what i saw after putting in a editbox for manipulating the first line data of the middle selector that the fs selector didnt update properly (while the data IS updated ) but thats just a missing trigger from the items list to the label of the selector..

here is a fast hack including the test file scenarios from my last example plus the trigger fix at the fs selector(the middle one)

OK ... I'm looking at this.

NOTE: the middle selector in question is the original SM version [squared look]. The 'bookend' rounded selectors are the FS version.

BTW ... nice technique to display the 'report status'.


?question?
When we OPEN a file to WRITE ... after the Save ... how is the processed CLOSED ???

I ask this, since the test systems in question have stumbled on re-loading the file after it was just saved [even with a 1.5 sec re-load delay].