DSP Robotics Support

here are two of your selectors with updated outputs when itemslist is changing

i commented inside sschematic to see where this happens

well ... I wasn't close to the solution

Now I see it as you said ... trigger the output ...

man, am i slow to catch on

Need sleep here ... have a jazz gig tomorrow. Look at this fresh afterward.

Again .. thank-you ...

Hey Mr Hollins, did you find a permanent fix ?

Im still having many many issues with file reading/writing (mainly on 64bit systems).

Im still in hell here trying to fix it

Hi Drnkhobo

I can relate to the frustration ... for sure.

Here is what I found ... There is a definite issue with Reaper's Master Trk.
Inserting a plug that needs to access a file [my Config file ... PreSet Manager file] .... the plugin cannot load it !!!

YET ... the same plug inserted on a regular multi-trk CAN load the file .... ONLY if the plug is first insert on a regular trak ... THEN it can also work on the Master Track ! So trying to use the Master trk for something like a mastering plugin may be serious.

We have confirmed this on 4 different systems, 3 different OS's, and different versions of Reaper.

I could not figure out any solution ... and this included test apps not of my making.

I really hoped that more members here would have joined in the test, or at least posted back with results.

.........

As it stands right at the moment, my project app [a VST] is now working [thanks to so much help here !!! ] ... we have some issue due to the nature of my project, which is a MIDI controller to handle other VST plugs. The issue now seems that these other plugs need time to load before my controller can send setup data to them. Although it works perfectly on my modest system ... we are only getting 70% success on what seems to be a lesser system.

Still trying to work this last bit out.

I've posted so much on the forum about this whole issue

If there is anything I can try to relay specifically with you ... please ask. I do not know if the 64 bit OS's are presenting any issue because of that. It's possible ... my XP-32 bit has just worked ... unless I've made a mistake [but at least I can have them and fix them]. I'm now trying to 'fix' some things that already work here.

After all the help, tweaks, and corrections from Members here ... I don't see the issue being my FS project.

The good part is that some great improvements had taking place because of this. [fantastic help from the forum Members] ... I'm NOT out of the woods quite yet. I'm experimenting with trying to delay my VST sending data until all the slave plugs are ready for it.

Again ... if anything I can comment on ... don't hesitate. If I don't have an answer, it may catch the attention from those that know a lot more.

Thanks for the update mr Hollins.

I dunno, i guess we are doing different things but with the same process. With even more paradoxical results.



I think that there might be something up with FS

Possibly ... though I can not rule out my handiwork

Using this thread, might be good to compare notes on issues that happen on different OS's or Daws ...

though I can not rule out my handiwork

hahah, even so it still has problems with stock FS modules.


Im hoping some 'higher powers' see this thread (hard to miss at 145 replies so far) & take a deeper look into what we have been reporting

You know, I think that this was introduced in the new update. possibly with the Ruby embedding. . . im not sure. All I know is that I NEVER had this issue previously (on previous FS versions) & I USE THE SAME METHODS / SCHEMATIC!!!!

(Ive had around 200 testers on that version & about 10 had issues)

So im saying that its something to do with the new FS version.

Drnkhobo wrote:You know, I think that this was introduced in the new update. possibly with the Ruby embedding. . . im not sure. All I know is that I NEVER had this issue previously (on previous FS versions) & I USE THE SAME METHODS / SCHEMATIC!!!!

(Ive had around 200 testers on that version & about 10 had issues)

So im saying that its something to do with the new FS version.

Hi Drnkhobo,

My apologies for bring up this topic again ... I've been so consumed dealing with my tester ... so please, would you kindly elaborate on the issue[s] that you are referring too. I think that this is a very important issue that we are trying to figure out ... but we have to be clear the specifics of what it is ??

I've hit some Reaper [bug ... cause I think it is Reaper - no proof] ... when a VST from FS is first loaded into Reapers MASTER TRACK ... the plugin cannot load in any type of text file .... be it Marshaled, plain-jane txt, or even the PreSet Manager file. YET, if the same plug is loaded to a normal track ... it works as expected.

The crazy part ?? after it's loaded in normal track .... NOW it can load in the Master Track
This was tested on 4 different systems, from XP to Win 8.1 ... and from older Reaper to the latest beta.

Is THIS the issue that you've discovered ??? something else ??

I've no idea how to solve this ... and really, I can't even figure out how this could be happening. Spent 2 weeks going back and forth until my tester causally mentioned he'd been using the Master Track as the convenient test insert. But really ... it should not matter. The moment he inserted on a standard track ... my entire project worked

This was not only my project, though. NuBeat had put together these special test files ... same result ! [and he's a much better programmer than I ]

Honestly, I can't believe so few FS guys have not voiced about this ... or at least to say, 'hey ... you're doing it wrong !' That would even help [although after trying so many different techniques ... I've hit my ceiling of possible solutions. So I'm left with 'this is a Reaper issue' .... now what do we do ??

Let's define the exact issue so we all know what we are dealing with.

Thanks again for participating in this unfortunate situation.

Hey Mr Hollins, no problem.

The issue im having is file read/write methods dont work 100%. Now i used stock FS components to read/write files (simple text files) in the past & they worked pretty good. Unless you got the directory wrong or something they did their job.

Now with the update from FS recently, I noticed that they werent working as you think. Let me set this up for you. . .


One string inside a plugin is connected to one Save File primitive. A trigger comes along and pushes the lonely string into the text file as agreed by the Save File prim. Then a separate module (Ruby & green prims) checks if the file has been written & if it is valid. All good. . . until the next module (which loads the said file) cannot load it. . . its not loading when a trigger kicks in.

So. . . I try on many machines & (mostly 64bit) they have weird problems.....some the file writes but doesnt load, then It works for them. . . weeks later its not working again. It seems unpredictable.

Ive tried backup systems where if the file doesnt write in the beginning, error msg's pop up & a Ruby (Marshal method thanks to you guys) routine writes & tests the file. BUT STILL it doesnt pop up with no msg & no written file.

I dunno