DSP Robotics Support

billv wrote:Bit Dissappointing if the community can't record a track and make a desicion with all the
"sample accurate " tools provided by the Host.There seems to be a fear or lack of respect for Hosts in the atmosphere. Weird...

I don't understand what you want to say with that. Why can't you record? I don't get it.

billv wrote:That's great if DSPR can test the "supergreen theory" with your Ultimate proof FSM.

There is nothing to test, they know exactly what their programm is able to achieve. When you say them you use a green connection to trigger something, they'll tell you that it won't be sample accurate (they won't even bother to look at your schematic).

MyCo wrote:I don't understand what you want to say with that. Why can't you record? I don't get it

Because You claim all my pics and FSMs are worthless.
I've done enough testing at this point that verifies the "Supergeen" idea is plausible.

MyCo wrote:There is nothing to test,

Then forget i ever mentioned it.
Leave it all in the Supergreen post....never reply to it and let it dissappear.
Won't change anything in my studio.
Community has been informed about the idea. Best I can do. Rest is up to them.
All good, either way.

MyCo wrote:they know exactly what their program is able to achieve

Why do we then have bugs Myco?
If they knew what they created thier would be no bugs. it would be flawless.
FS will always be under a constant state of development.

This is the v3 PPQ timer design, but done 100% in Ruby.

There is one wire in green, only because my ruby selectors didn't work for some reason...
Not important either, can be removed. It's just there for standalone use....

Edit:
Note the output for '1/1" is actually "1/2"...
This is X11 default time...sorry...forgot to change it back to normal time before upload...
To make "1/1" setting actually output "1/1"...go to
step module/selector module/....then change the 2 to 1, in this line


Edit :
Be careful if you change the "Pattern selection pad"....
There is an "afterload" stashed in there, which is required by the circuit.....

Na...no good...design fails at tempo's other than 120...
I first thought problem was my attempt at beat fraction in ruby....but it seemed ok..
Then i found that v3 PPQ timer(Green version) has same behaviour.
So its a design issue......not sure if it's fixable yet...looks like very hard fix...not confident..

Take a break...
Make something random... Spontaneously harmonized randomness...
Relax... Fade out...
Take a deep breath... 0.06125 bpm
Just let go... Resync...
That's it..., now you are hypnotized. Just go with the flow...

...ppq ticker's beat fraction is locked at one rate, so the error is very easy to see.
Might take a while...but i think it's fixable......

Fixed. "billv PPQ shit" actually works ......PPQ now working at different host tempo's.
Still can produce an error of 1 sample.....should dissappear when attached to big synth.....
Biggest error i got was dropping host tempo down to slowest speed (10)...3 to 4 samples out.
Apart from that....all good so far....
This version all ruby.....will make a green one later on.....

PPQ timer Updated.
You can now change any of the 4 slots to any division between 1/1 and 1/16.
Changes can also be made on the fly.....

Hat off to you for dedication billv!

I like the new version!

I get "error inside the module" message.