DSP Robotics Support

Reading the forums ... found something that caught my attention.

http://www.dsprobotics.com/support/viewtopic.php?f=2&t=876

in particular, Tronic says:

i tried not work in vst mode, the load path in vst work different.
$LOAD_PATH point to a virtual path like this:
C:/Users/<username>/AppData/Roaming/lib/ruby/......
but it not realy exist.
i have found $EXE_PATH and $INSTALL_PATH
but it point to CWD directory, ie, the last or current working directory used in your Host.

so I think for now it is mandatory to define the load path of the vst.
I defined it as a class variable @ @ Path_MyVST, taking the value as you suggested from the primitive Start folder.
I have not declared as gloabl variable to avoid future clash with other plugins.

The topic thread is not very long, so for context I included the above link ...

but the mention of FilePath handling in VST is what caught my eye ... though the topic is different ... just wondered if this relates to the file loading with VST we've been having ... long shot I know

Research ... with the usual questions.

Found a Link regarding 'Opening and Closing Files' with RUBY. Things that make ya go ... 'hmmmmm'

about a 1/3 way down I read ...

Opening and Closing Files:
Until now, you have been reading and writing to the standard input and output. Now we will see how to play with actual data files.

The File.new Method:
You can create a File object using File.new method for reading, writing, or both, according to the mode string. Finally you can use File.close method to close that file.

Syntax:
aFile = File.new("filename", "mode")
# ... process the file
aFile.close

From this link:
http://www.tutorialspoint.com/ruby/ruby_input_output.htm
hmmmm .... maybe be nothing to do with the issue at hand ... but how would I know Not questioning the knowledge from those with much more experience ... I just can get easily confused in this new Land of RUBY. Thank you for guiding the dizz-bang

any new testresults with the latest module?

Yes ... although we have had some delays with emails ...

Late last nite got the word that version#5 tested on Win 7-64 PASSED as a VST.
I sent email response, but did not hear back ...

Just a few moments ago, the main Win 8.1 was tested, and that too PASSED !
There is a 3rd unit still waiting on.

It appears that file can be Saved, Loaded, and Edited. All 3 Selectors functioning

Yes ... I'm in a bit of a stunned mode at the moment

****************************
We still have an issue that is a bit confusing, and I'm trying to get clarification from BT'r.

It appears that REAPER's handling of VST plugins is not consistent between the 'MASTER' track and the individual tracks.

From what I'm gathering [still] the MASTER track is involved with [seemingly] random success. Whereas the individual track is now working right from the start.

It seems my tester was using the 'Master' track during all of this testing ... including my project. So I'm trying to sort through with him at what point did we go from Fail to Pass. [Yes I'm a bit frustrated to just be informed of this].

I've sent my project [at the last state we left it] to be tested on the indy track. If that fails, then I will switch in the v#5 module into my project to test.

I will immediately report back here !!! I did try to impress the importances on knowing WHAT change was the pivot point.

I'm currently biting my lip on this because of the intro to the Marshal routine and the work [NuBeat] has done for this.
It is marvelous

Now if I can get determination as to what stage things worked

sounds not bad - there already the light at the end of the tunnel!

Nubeat7 wrote:sounds not bad - there already the light at the end of the tunnel!

ahhh NuBeat ... thanks for helping me lower the blood pressure

Alrighty then ....

We have some good news, along with some confusion to report.

First da good.

We have success with the file operations now on Win7 & 8 !
Yes ... this has been confirmed

It has been found that the Marshal routine that was first re-written by NuBeat indeed WORKED ! All the additional changes did not change the result [but I think there were some wonderful enhancements nonetheless].

What happened you may ask ...

REAPER has 2 'track' items ... the first is the MASTER trk. All the others are those the user can insert as needed.

My B-Tester had been using the MASTER track for the entire series of testing, starting with my project ... and then to the Array tests. All MY testing was done by INSERTING a new track and placing the VST there. My B-tester went only to the Master trk.

AND THUS THE ISSUE.

For reasons beyond my comprehension, If either of these tests are first insert on the MASTER ... they do NOT work.
However ... inserting on a User track [the regular, everyday multi-track ... track], both projects work !

Here's what makes this fun If we place the VST in a User track FIRST [it works] ... and THEN put one on the MASTER trk ... now the MASTER VST plugin WORKS

This goes both for the Array test AND for my project VST.

I have also confirmed this same result on my WinXP and my older version of Reaper [4.32]. The B-Tester is always using the latest Pre-release [also checks on official ones] on Win 8.1

So the situation/issue is identical regardless of Reaper version or OS.

Why the MASTER trk is having issue is unknown to me. Why, after insert the plug on a regular track, that we can now insert one on the MASTER ... and it then works

Happily Confused. and what is left of the remaining brain cell ... has gone numb


***** EDIT ****

Hi NuBeat ... I'm looking at the Array Test module, and in particular, the mod you made to the Selector Menu [especially the FS version 1 & 3]. I'm trying to locate the trigger mod [on output] you did ... can you help me identify where that happened ??? The more I think about the mod you made, the more I think you concept better than stock.
Thanks again !!!

I know my ramblings can put many to sleep But I want to highlight a confirmed issue that we have identified.

This 'Array-Save/Load test', saved as a VST. When loaded into REAPER [seems any version], to the MASTER TRACK only ... will NOT work.

However, loading the same VST to one of Reapers' 'multi-track' does WORK.

Here's the kicker ... if you then load the VST into the MASTER TRK ... it will now work

I have confirmed this identical issue with the VST plugin that I've been developing/testing.

What the difference would be in Reaper is not obvious to me ... in fact, it should not matter in the least. It's a VST plugin going into an FX chain. It seems related to the loading of a configuration file.

The issue spans across OS's [at least XP to 8.1] and is still an issue in Reapers latest 'Pre-release'.

It seems to affect all DISK activity [config files, registration files, and the PRESET MANAGER].

If this issue was only my system, I'd say I had problem code. But my B-T'r has 3 system [Win 7 & 8]. All attempts to locate this via coding [NuBeat] have not been able to solve this ... UNTIL the plugin was first loaded into a regular track. After that, we've been able to load and work in the Master Trk.

Reaper seems a rather popular DAW ... so I wanted to bring this to everyones attention. Particularly if you are developing VST plugins. The 'test code' is posted in this thread ... it may be good to have FS programmers test this condition. I can't directly say where or what the BUG is, and what is at fault.

At least a 'Heads Up' to an issue I have tested and can confirm.

Reporting back ...

Well, after all this testing craziness ... we have returned to beta-testing my 1st project. NOW we are using one of Reapers regular tracks [NOT the Master].

My B-tester is right now playing with the new toy. He finally took a break from playing and requested the Authorization file to fully unlock the plugin ... Currently I have no idea if it worked ... as he doesn't seem to be answering new emails. The last email contain a bunch of smilings and grinnings and oh mys ... but I not sure if he's OK, or just been transported to another Universe

Once up and configured ... I did suggest he play.

I can relate to the feelings he's expressed, and the gibberish was understandable to me. I've been using this new toy for over a month, so I can relate

Now I hope to if we have any things to smooth out or fix. I also have focused back on some simplifications AND actually removing some of the flexibility that I left in for configuration. I feel that it could easily lead to confusion, or darn right messing things up for really no good reason. Maybe putting restrictions on certain aspects helps keep focus on the real purpose and function.

... still no email ... so I guessing the Registration was successful

I'm sure we will have things to do or improve ... but I wanted to take this moment to share a bit of joy/happiness.

There are several Members on this forum that have been so gracious AND generous to me. And even though I know I'll need to be back here once again looking for guidance or salvation I am sincerely grateful.

This has been a strangely, fun, adventure, and would likely been not possible without Your kindness and help all along the way.

--- took awhile ... but email is in, Registration WORKED and ... he just returned from 'OUT THERE'
I said great ... go play, have fun !

Me ... I'm taking a moment to try and unwind the brain. Look at all this fresh tomorrow !
Thank-you and you and you .... and YOU ....

... hope I didn't leave out AnyOne

Nubeat7 wrote:btw your infolabel (under the selectors)dont update properly because when selector items are changing there is no trigger generated at the droplist output! this means that also the selected item is not updated, after loading the file you have to reselect it to be updated

Oh NuBeat ... I really need you !!!!

This 'no trigger at the droplist output ... ' is there any chance that you remember this section ... I think you have identified an important issue ... just I'm not sure what you describe as the solution ... or worse ... how to fix that

**** edit ***

ps: about the label update - i didnt mean the labels of the selectors i meant the outputs of the selectors (the lebel right under the selectors i changed the second one to see what i mean ....

I'm looking at the standard Pull-downs from FS [examples 1 and 3] from the # 5 test module ... these FS ones would be the one to have the droplist output trigger correction.

Still trying to identfy the 'fix' section


***** EDIT AGAIN ***

I'm looking inside the 1st level of the FS pull-down menu.

I see the ITEM INPUT into a string prim ... that goes to a 'group trigger' ... to then feed the 'Label' input of the Draw/Interact module.

What I tried was to tap the 'group trigger' collector, and link to the INDEX of the Preset module.

That seemed to do the update after Load.

Is this correct ?

Is this the only connection mod I need to make for this ??

Thanks!


**** Edit Edit ***

nope ... that doesn't seem right ... it partially works but the menu also resets to 1st position ... or something.