DSP Robotics Support

RJHollins wrote:Also ... might you have tested as VST ???

yes, but only on renoise.. because i`m not at my main computer... but i can test it during the next days on cubase and live too

Fantastic ... and Big Thanks !!

When you do get a moment, I would like to hear your thoughts on the OPEN/CLOSE question.

Tested on vst.
Same procedure as before.
Same results.
Let me know if want me to vary the way I'm testing it......
(of to work though...12 hours before I can try again....)

billv wrote:Tested on vst.
Same procedure as before.
Same results.
Let me know if want me to vary the way I'm testing it......
(of to work though...12 hours before I can try again....)

Did the pull-down menus work for you ??? what OS's [i can't remember]

Going through several example codes I've dL'd, I located the 'Save-Load Ruby [binary files] example that was posted. Saw something interesting in the code

in particular ... the obj=nil

Just before the LOAD command. Just made my wonder WHY this was in the code ?

It's in the similar area of my question about the WRITE & LOAD command used in the Marshal routine we have in test. That is, we do an OPEN to start ... but I don't see a CLOSE command Just like in the code I'm showing here ... is a CLOSE an 'implied' function that was only used back in the Commodore 64 days

I'm still trying to understand why 3 systems are not able to auto-load a file that it just saved. So in that search to understand, I'm looking through examples and reading.

Just some thoughts

if you open or create a file (new) normally you need to close the file manually except there is following a block, if this is the case the file always is closed automaticly after the block is finished also when the block raises an error.

thats why you dont need to close the file - after the marshalling it is closed automaticly.

Thanks for the clarification NuBeat !

The lastest test module you posted was sent out ... the EXE worked on my BT'r system .... the VST form did NOT. The file does not seem to re-load with VST. It does save.

I've ask if he can install a different DAW to test on. waitng to hear back.

Guys I have been watching this topic get bigger and bigger . . . With no resolve.

Mr Hollins, you still have paradoxical issues with reading or writing simple files.

I too am nowhere in finding a stable module we can rely on.

Perhaps we should include the probability of the file reading / writing into our schematics? Hisenberg, where are you?


No, seriously I think there is something out of our control. I'd love to be proved wrong but all tests and cross checks and fail safes don't help. ITS STILL UNPREDICTABLE and that's not good for any vst dev.

Hi DrnkHobo ...

I went back to read the early parts of this thread for your post. We are both experiencing the IDENTICAL issue. I thought it was just similar ... but no, it sounds identical !

As with you ... every test I run on my system works [ruling out my mistake that I fix]. I have tried so many idea combinations that work here ... but fail as VST on my BT'r 3 different computers

We can WRITE the file .... I seems we cannot read it back .... YET ... in my project VST, the first thing a user does is load in a XML file [created from a different program]. This has always WORK ... as it should !!!

We can read in the XML file, parse it, display the data. We've been able to SAVE it [as a config] file in plain TXT, and now Marshal.

But it seems we canNOT load it back in ?!?!?! not even manually. This is INSANE

I've ask my BT'r to try a different DAW, as the issue seems to exist in VST form ... we got NuBeats latest test to work as EXE.

I'm running out of ideas ....

NOW I WONDER ....

Is it feasible that the VST form that I'm creating on my WinXP is not able to create a VST compatible for Win7/8 ???
Do I need Win7/8 to create a version that works on those OS's ????

I will be that last to point and yell BUG in FS .... but this is not my code that is being tested [happily to get myself OUT of the potential error marker ... I'm a rookie at this ... I still make stupid mistakes]. Yet, things work on my system ....

I feel like I'm trying to fix something that is not broken for me. CRAZY !

I'm ready to ask one of the Win7/8 guys to compile this test module on their machine [rather than my XP rendition] and see if that will work on my BT'r system ... like I say ... I'm running out of ideas here

Is it feasible that the VST form that I'm creating on my WinXP is not able to create a VST compatible for Win7/8 ???
Do I need Win7/8 to create a version that works on those OS's ????

I think if that were the case then we would know about it and Im using Win7. . . so it cant be because of system used when compiling.