New SpinCAD release pending - I ain't too proud to beg.

Digital Larry

Active member
Let me know if this is not appropriate somehow.

I've made a few more fixes to SpinCAD Designer and added a new block.

The new "Ratio" block is really handy for things like chorus, flanger, and oil-can delays, to create two control signals over a given range whose product remains constant.

Fixes include:
- Simulation fix for Log and Exp instructions (this is down in code I didn't write originally, so let me know if there are any strange side effects).
- Hall Reverb block was missing a "@isPinConnected" for the 3rd control input. This meant that if nothing was connected there, it would not generate code properly.
- Simulator display redraws after each sweep (more improvements are possible here).
- Added a "Tri Width" control to the Ramp LFO block. Now you don't have to mess with an external multiplier if you wish to have a pot control your triangle LFO width.

But wait, what's the catch? Yes there's a catch. I want to see if I can raise $50 from y'all using the "Sponsor" feature of Github. What do you get if you sponsor me? Besides my appreciation and a feeling of satisfaction for having done the right thing, you get about the same thing that you would without sponsoring me. I'm not at the point of printing T-shirts. But if I can make $50 I'll push out this release and the new Gitbook page for the Ratio block ASAP. Otherwise, who knows, I might let it sit for awhile, or I might, y'know, take a nap, etc. Thanks for your consideration and support.

1711921449476.png
 
Let me know if this is not appropriate somehow.

I've made a few more fixes to SpinCAD Designer and added a new block.

The new "Ratio" block is really handy for things like chorus, flanger, and oil-can delays, to create two control signals over a given range whose product remains constant.

Fixes include:
- Simulation fix for Log and Exp instructions (this is down in code I didn't write originally, so let me know if there are any strange side effects).
- Hall Reverb block was missing a "@isPinConnected" for the 3rd control input. This meant that if nothing was connected there, it would not generate code properly.
- Simulator display redraws after each sweep (more improvements are possible here).
- Added a "Tri Width" control to the Ramp LFO block. Now you don't have to mess with an external multiplier if you wish to have a pot control your triangle LFO width.

But wait, what's the catch? Yes there's a catch. I want to see if I can raise $50 from y'all using the "Sponsor" feature of Github. What do you get if you sponsor me? Besides my appreciation and a feeling of satisfaction for having done the right thing, you get about the same thing that you would without sponsoring me. I'm not at the point of printing T-shirts. But if I can make $50 I'll push out this release and the new Gitbook page for the Ratio block ASAP. Otherwise, who knows, I might let it sit for awhile, or I might, y'know, take a nap, etc. Thanks for your consideration and support.

View attachment 72005
$50 from each of us or $50 total?
 
Won’t let me click on anything yet. Think they are verifying my account. I’ll throw a few your way whenever I can. Haven’t used it yet, but plan to in the near future
Well you're too kind! Someone else has already contributed as well. I really appreciate it.

DL
 
@Giorfida sorry about your troubles there. I'm not too familiar with the Github app. I just used the "Sponsor" button on the webpage in my browser. If you like I can send you an e-mail address for Paypal. I appreciate your determination!

DL
 
@Giorfida sorry about your troubles there. I'm not too familiar with the Github app. I just used the "Sponsor" button on the webpage in my browser. If you like I can send you an e-mail address for Paypal. I appreciate your determination!

DL
Finally got it. The app didn’t have a sponsor button, the mobile web browser implementation of the sponsor button was dead. Finally tried on my laptop and it worked, so you should see it soon if not already
 
I did! It works! Thanks a ton!

DL
Just a way to say “thank YOU” for contributing this software that presents the elusive world of μ-proc programming in a format that the everyday hobbyist can enjoy. (Even as someone who went back and got his degree in IT, I appreciate not having it dig back into my c/c++/c#/VB programming mindset to enjoy when I start down the fv1 rabbit hole!)
 
I appreciate not having it dig back into my c/c++/c#/VB programming mindset to enjoy when I start down the fv1 rabbit hole!)
The irony of SpinCAD's outplaced position in my life is that I wrote it because I disliked writing FV-1 assembler so much. All the experience with those other "grown-up" languages will barely help you at all in the world of FV-1 assembler! The other irony is that as a result of all this time spent with it, I'm actually still pretty good with FV-1 assembler. I even seem to have figured out log and exp once and for all (until I forget). HOWEVER, (and I know I've said this before), the leverage you get in implementation speed with SpinCAD lets you try things you might not have even thought about otherwise.
 
HOWEVER, (and I know I've said this before), the leverage you get in implementation speed with SpinCAD lets you try things you might not have even thought about otherwise.

This is one of the biggest advantages to me.

Especially for prototyping an idea (or someone just diving into FV-1 development), the struggle of trying to squeeze just a little bit more out of the instruction limit is brutal. It's much easier to swap some blocks or make a tweak here and there, rather than spend all day writing code only to realize it goes over the instruction count or RAM limitations.

Obviously you can do more fine tuning to the final product by digging in to the raw code, but for trying out that crazy new idea you came up with in the shower this morning, there's just no better way.

The Daydream probably wouldn't exist if it weren't for SpinCAD because I didn't think the FV-1 could handle it and wouldn't have attempted it coding "by hand".
 
Just saw this thread and definitely sponsored for $50.

I'm still very new to FV-1 and have an idea I want to pursue... The FV-1 can do most all the effects I want on my board. So, I made a PCB with the 8-postion rotary in a small foot print to add to my combo pedal. The idea is to have be "dial a song" with 8 choices. All 8 of them will have baseline reverb with the first entry being only reverb. So that's always on. In the others, I want to add specific delay or flange or chorus... What ever is needed for some specific song. We play a lot of rock 'n' roll, so it's really only a few needed options. In each case, I want to use my Arachnid dev pedal to dial in the effects and knob settings, then hard-code those setting so no knob fiddling during a gig. Just "dial a song" when needed.

I will likely use spincad to make all the patches. But, does anyone know if the spatialist reverb code is available? This is probably a question for @Robert . I would like to be able to hard code control settings for my final build or (if I get adventurous) combine a reverb I like with other effects.

But, I have not figured out how to use spin asm tools. That thing is flying over my head just trying to create 8 patches, even just dummy patches, and end up with a eeprom image to burn. No trouble at all using spincad but spincad is higher level than the raw code, so not sure if I can use it to combine pre-made things (like the reverbs in the spatialist) with other effects.
 
Thanks a bunch @Paul.Ruby :love: and anyone else who contributed! I know nothing about the Spatialist reverb. Generally speaking it's "possible" to combine SpinCAD generated code with ASM from some other source BUT there are also pitfalls that would be hard to manage unless you're familiar with FV-1 assembler and the weird way SpinCAD does delay memory assignment. Feel free to ask questions here about specifics.
 
I will likely use spincad to make all the patches. But, does anyone know if the spatialist reverb code is available? This is probably a question for @Robert .
Correct. @Robert would be the contact point for what specific reverb codes are used in the Specialist. If I'm not mistaken, they are basically canned patches from one of the online FV-1 code dump sites. The specific patches are:

Spacialist Reverb Patches/Modes:

1) Room
2) Hall
3) Chamber
4) Cavern
5) Modulated
6) Shimmer
7) Pitch Verb
8) Touch Reverb

Controls:
Control 1
Control 2
Control 3
Mode – Selects reverb mode
Mix – Sets the Wet/Dry mix
Volume – Controls overall output volume

MODE . . . .CONTROL 1 . .CONTROL 2 . . CONTROL 3
Room . . . .Dwell . . . .Pre-Delay . . Dampen
Hall . . . .Dwell . . . .Pre-Delay . . Dampen
Chamber . . Dwell . . . .Low . . . . . High
Cavern . . .Dwell . . . .Low . . . . . High
Shimmer . . Dwell . . . .Shim Pitch . .Shim Level
Modulated . Dwell . . . .Mod Depth . . Mod Rate
Pitch Verb .Dwell . . . .Octave Down . Octave Up
Touch Verb .Dwell . . . .Ducking . . . Sensitivity
 
Correct. @Robert would be the contact point for what specific reverb codes are used in the Specialist. If I'm not mistaken, they are basically canned patches from one of the online FV-1 code dump sites. The specific patches are:

Spacialist Reverb Patches/Modes:

1) Room
2) Hall
3) Chamber
4) Cavern
5) Modulated
6) Shimmer
7) Pitch Verb
8) Touch Reverb

Controls:
Control 1
Control 2
Control 3
Mode – Selects reverb mode
Mix – Sets the Wet/Dry mix
Volume – Controls overall output volume

MODE . . . .CONTROL 1 . .CONTROL 2 . . CONTROL 3
Room . . . .Dwell . . . .Pre-Delay . . Dampen
Hall . . . .Dwell . . . .Pre-Delay . . Dampen
Chamber . . Dwell . . . .Low . . . . . High
Cavern . . .Dwell . . . .Low . . . . . High
Shimmer . . Dwell . . . .Shim Pitch . .Shim Level
Modulated . Dwell . . . .Mod Depth . . Mod Rate
Pitch Verb .Dwell . . . .Octave Down . Octave Up
Touch Verb .Dwell . . . .Ducking . . . Sensitivity
Yep. I have a spacialist bought from pedalpcb that I've built to play with reverb options.
 
Back
Top