DSP Robotics Support

Thanks for this beautiful creature, trog. It's so flexible and the syncing options are splendid

Had an issue to power it up in the alfa, so after a short search, I've found an error report from this asm. module (a picture attached). Any suggestions what could go wrong?

https://imgur.com/yWKaI5b

The download in the top post is now updated to Beta 0.2.0.

New features:

- Discrete phase-sync added. The phase can be reset at stream rate by any positive-going zero-crossing.
- Small, round manual phase reset button added to demo' GUI.

Changes:

- Phase offsetting is now relative to the overall output period rather than the sync-source ramp.
- Sync selector Ruby code refactored to generate fewer temporary objects.

kortezzzz wrote:Had an issue to power it up in the alfa, so after a short search, I've found an error report from this asm. module (a picture attached). Any suggestions what could go wrong?

I hadn't tried it in the alpha yet, so thanks for that. In older versions, the sine function is just a 65536-element look-up table, which the built-in "sine" variable points to. So it looks like MyCo must have updated the sine function implementation. I have no doubt that this will be to make it far more accurate - but I'll have to see if I can get my head around the new ASM code!

Here's a version which I'm hoping will fix the problem with the sine function in the alphas. The internal hopping should make the slight CPU rise barely noticeable, and it should have the neat side-effect of making very slow sine waves more accurate.

I'll move it to the top post once I know that the alpha problems are fixed (I'm still not up and running with it on my PC yet.)

[EDIT: Fix confirmed - attachment has been moved to the top post]

It works just fine right now However, I'll report any odd behavior. THANKSSSS trog

@kortezzzz
Thanks for reporting back; I had a hunch that MyCo wouldn't have deprecated the FPU assembly codes - good to know for oscillatory-type ASM gizmos. I'll bump the fixed version up to the top post.

Top post updated to Beta 0.2.2. A small tweak to the 'SyLFO MASTER' module - when free-running due to there being no PPQ clock, the beat-sync and bar-sync clocks now lock phase properly. The new 'SyLFO MASTER' module is a drop-in replacement for the old one, compatible with all previous versions' LFO modules.

Hey trog,

I was so delighted to see this, since the only other syncing LFO (that wasn't the stock step LFO) was old, and liked to crash FS, or the exported plugin it was in.

Unfortunately, I'm experiencing weird behavior (my FS version is v3.0.9b2-2437-gc137141) with my ASIO Out de-selecting, the second a parameter of SyLFO is changed (touch a knob, etc.); when I then click the ASIO selector, it's back; but then click again anywhere in the schematic, it instantly de-selects again.

It's definitely something with SyLFO that's doing it, since no matter what .fsm it is, only SyLFO causes this.

I would loooove to implement this well-designed (and small GUI footprint) LFO, but without knowing what's happening or why, I can't

Duckett wrote:Unfortunately, I'm experiencing weird behavior (my FS version is v3.0.9b2-2437-gc137141) with my ASIO Out de-selecting

Unfortunately, it's unlikely that I'll be able to come up with a fix for you - as announced here, the 3.0.9 Beta's are notoriously unstable, so it's recommended that folks stick with earlier versions (preferably 3.0.6, to avoid a known issue with Ruby memory leaks in 3.0.8.x). It's probably a bug with the assembler primitive not recognising an opcode, but after a lot of refactoring to make the code stable for future FS4 versions, I'm loathe to go digging around again in order to support a deprecated version of FS. Sorry!

I remember that thread.. I do still have 3.06, didn't know the more recent betas were still unstable, since it's been far less crashy than the last update I tried (and reverted back to 3.06)...

Thanks for replying quickly, though!