Cybercow
Well-known member
Here is a discussion opener for sharing stereo FV-1 patches here in this forum section.
I've begun the journey into true stereo algorithm patches for the FV-1 using SpinCAD Designer build version 0.98-1035
I'm more than happy to share them here. And I think it would be a good idea to settle on which format to present them to the group here in this forum.
Should I post them as single SpinCAD Designer (.SPCD) files, SpinCAD Designer Project (.SPBK) files, single SpinASM (.SPN) files, single Hex/Bin (.HEX/.BIN) files or all of the above.
Could even do simple text files in the SpinASM format - just change the file suffix from .TXT to .SPN
The important note is the difference between the different file types. Not everyone has SpinCAD Designer and/or SpinASM Assembler interface. And some folks work only with the .HEX/.BIN files for burning directly to an EEPROM. Sharing SpinASM project files is pointless because they do not contain the actual patches, just pointers to the *.ASM files where ever they were referred to/from last.
I'm creating the three fundamental X100 patches first ( CHOR/ECHO/BOTH ) because it is the project that has driven me to going full stereo with the FV-1. These three patches will be different from all others because I am establishing the three control pots to behave in such a way that when all three control pots are set at minimum, they will nail the default X100 FX - and tweaking the controls will take each of those beyond the X100 original FX behaviors. All other patches will NOT be set up that way for more feature rich algorithms. When I start posting the actual algorithms, each will come with explanations.
Other thoughts, suggestions, ideas?
I've begun the journey into true stereo algorithm patches for the FV-1 using SpinCAD Designer build version 0.98-1035
I'm more than happy to share them here. And I think it would be a good idea to settle on which format to present them to the group here in this forum.
Should I post them as single SpinCAD Designer (.SPCD) files, SpinCAD Designer Project (.SPBK) files, single SpinASM (.SPN) files, single Hex/Bin (.HEX/.BIN) files or all of the above.
Could even do simple text files in the SpinASM format - just change the file suffix from .TXT to .SPN
The important note is the difference between the different file types. Not everyone has SpinCAD Designer and/or SpinASM Assembler interface. And some folks work only with the .HEX/.BIN files for burning directly to an EEPROM. Sharing SpinASM project files is pointless because they do not contain the actual patches, just pointers to the *.ASM files where ever they were referred to/from last.
I'm creating the three fundamental X100 patches first ( CHOR/ECHO/BOTH ) because it is the project that has driven me to going full stereo with the FV-1. These three patches will be different from all others because I am establishing the three control pots to behave in such a way that when all three control pots are set at minimum, they will nail the default X100 FX - and tweaking the controls will take each of those beyond the X100 original FX behaviors. All other patches will NOT be set up that way for more feature rich algorithms. When I start posting the actual algorithms, each will come with explanations.
Other thoughts, suggestions, ideas?