Plogue chipsynth C64

[Charlie Firpo]

Ah, i see! Well it's no biggie, but here's a few simple steps if you want to check it out:
1. Init patch
2. In the matrix set step 1 as source. "Osc1 gate" as destination.
3. Goto Mods. Set Steps = 4, Num = 1, Den = 16, Speed = 0.25, Loop = Notegate.
4. Activate the first "block" in the steptable window and set the loop points at the start and end of it. The remaining 3 steps are silent/empty.
5. Play a few note on the keyboard.

[davidv@plogue]

Ah, i see! Well it's no biggie, but here's a few simple steps if you want to check it out:
1. Init patch
2. In the matrix set step 1 as source. "Osc1 gate" as destination.
3. Goto Mods. Set Steps = 4, Num = 1, Den = 16, Speed = 0.25, Loop = Notegate.
4. Activate the first "block" in the steptable window and set the loop points at the start and end of it. The remaining 3 steps are silent/empty.
5. Play a few note on the keyboard.

Ok Reproed. That is ... interesting.

[Charlie Firpo]

Having a blast with this! Just two feature ideas:

1. When working with long steptables, it would be nice to see at which stepnumber (horizontal) the mousepointer is currently at. (It already shows you the wave number when hoovering the mouse).

2. I really like the various speed/delay/ramp knobs. It would be great to have a knob that makes the steptable speed go from fast to slow. (Like the ramp knob but in opposite direction). Other than that, i like the steptables very much. Powerful stuff!

[MrJubbly]

Is there any reason why the CLAP version of the plugin had an extra "_x64" suffix added to the name?

I feel like it is unnecessary and that it doesn't look as clean and professional within the DAW plugin selector as the VST/VST3 version.

"chipsynth C64" vs "chipsynth C64_x64"

_64 Suffix on CLAP format.png

Why couldn't the CLAP version just carry the same "clean" title as the other Steinberg VST formats, without having that unnecessary text added? None of my other CLAP plugins look like this.

Also, would it cause any plugin loading/performance problems, if I were to manually rename the CLAP plugin and rescan it, so that it doesn't have the extra "_x64" appendage?

Apologies if this comes across as a bit rude for asking. But I just think plugins that have such "_x64" "_x32/86", etc. look untidy and ugly, when trying to locate the plugins within DAWs' menus and plugin pickers.

[davidv@plogue]

The reason is we ship both a "chipsynth C64_arm64x.clap" and a "chipsynth C64_x64.clap" and they sadly have to share the same folder. You can rename it and rescan plugins in your DAW if it bothers you. Note that DAWs should never rely on plugin names but "internal" names for display.

Cheers

[MrJubbly]

The reason is we ship both a "chipsynth C64_arm64x.clap" and a "chipsynth C64_x64.clap" and they sadly have to share the same folder. You can rename it and rescan plugins in your DAW if it bothers you. Note that DAWs should never rely on plugin names but "internal" names for display.

Cheers

Thank you for replying.

I manually renamed the CLAP file to remove the "_x64" suffix and rescanned my plugins, which fixed the issue.

The synth is now easier to read and locate in my plugin menu lists.

I'll just have to remember to also repeat this again, if I ever update the CLAP plugin in the future.

[Charlie Firpo]

Thank you for the latest update David. The fixed freq as a destination for modulation is very nice. You also did a change with the gate destination mod. However, the problem with a ghostnote still remains. (Using the steps from my post above). I cant loop a single gateblock (using notegate) without it creating an extra note on release?

[davidv@plogue]

Thank you for the latest update David. The fixed freq as a destination for modulation is very nice. You also did a change with the gate destination mod. However, the problem with a ghostnote still remains. (Using the steps from my post above). I cant loop a single gateblock (using notegate) without it creating an extra note on release?

You might have to start a fresh instance and hit "init" preset before you try it again, otherwise the session is in "pre v1.006" compatibility mode. And this fix needs a v1.006+ session
I really need to add a flag somewhere to warn the user about this.
Cheers

[Charlie Firpo]

Thanks for the answer David. I had made my own init template and no matter what i did (tried to select the "init" option etc), the compatibily mode were still there. So i uninstalled everything and removed the maps from appdata, and did a fresh install: And now the gate works without the ghostnotes. Awesome! Thank you David.

[davidv@plogue]

Thanks for the answer David. I had made my own init template and no matter what i did (tried to select the "init" option etc), the compatibily mode were still there. So i uninstalled everything and removed the maps from appdata, and did a fresh install: And now the gate works without the ghostnotes. Awesome! Thank you David.

Ah you are right using "Save As Default" might permanently stall the product in legacy mode.
(this is stored in AppData). Need to put notes on this. Thanks

[Charlie Firpo]

I'm having so much fun with this! A feature request for David: It would be nice to have some kind of oneshot midi envelope (in different speed) as a source in the matrix (that goes from zero to full/and the other way). I would like to modulate the release so that it goes from 0 to e.g 9 on every keypress. You can already do this with midiCC, but it would save so much time with "oneshot source". Or if you could modulate the individual A/D/S/R with a steptable.

[davidv@plogue]

I'm having so much fun with this! A feature request for David: It would be nice to have some kind of oneshot midi envelope (in different speed) as a source in the matrix (that goes from zero to full/and the other way). I would like to modulate the release so that it goes from 0 to e.g 9 on every keypress. You can already do this with midiCC, but it would save so much time with "oneshot source". Or if you could modulate the individual A/D/S/R with a steptable.

Abusing the ADSR in SID land is rather dangerous (even with the hacks and protections). So maybe a concrete example of why you need this and how it would work in perhaps more state driven flow?

[Charlie Firpo]

Hi david! Sure, but first of all i must say excellent job on the adsr. Feels great not having to bother about the sid bugs. In all the different sidplayers they used different tricks to get around the adsr bugs. (Hardrestart, softrestart etc). Now thankfully, we don't have to worry about this in cs64 (which i'm thankfull for). But i still find it fun to play around with the gate & stall for a diffrent flavour. While doing that i noticed that if i leave a silent gate off before gate on (1/96 50 hz), you can get sharp attack on the first wave in the table. But when retriggering the note at poly1 with a release above 8, it makes that first sharp attack a bit slower. Now this happens on the real maschine too.

The solution is to midicc the release so that it's always at zero on note on and then quickly goes up to whatever release value you want. This way the attack stays consistent no matter what release value you choose. With that said, i'm only brainstorming now, and this only concerns when you start playing around with the gate Cs64 is a dream come true, and i'm very grateful for your fantastic work.

[Drew64]

If anyone can help, I can’t find much info on “Multi MIDI Mode” (the three oscillators and PCM are activated by separate MIDI channels), does anyone know which DAWs can utilise this? I’ve so far tried Renoise (which I love, but got nowhere) and faffed around in Logic Pro with no luck.

[Charlie Firpo]

1) Open a new instance of Cs64 in instrument slot 00
2) select mode = multi in Cs64
3) Go to next instrument slot 01 in Renoise & Select Vst Alias Cs64 from the instrument/plugin directory.
4) Click the plugin tab on the Renoise gui and select midi channel 2.
(Repeat the above steps for more midi channels: The Vst "Alias" is the key here)