Discovery Pro synthesizer 6.4 to 8.0

[Boy Wonder]

Discovery's Sync To Host parameters confuse me. In other synths, you'd see values like 1/4, 1/16, 1/16 dotted, etc. Here, you have ticks, from 128 to 0.5 in 1-unit increments. How does this translate into 1/4, 1/16, 1/16 dotted, etc.? Is there a formula?

[Ghostwave]

The vst3 version is buggy in Bitwig 4.3. For example, if I move the OSC2 pitch knob, the amplitude attack knob also moves (they sync together). This doesn't happen with the vst2 version.

[Uncle E]

The red skin is gorgeous. Is that the Nordic Dawn skin? Is there an equivalent red skin for Discovery?

[Examigan]

Discovery's Sync To Host parameters confuse me. In other synths, you'd see values like 1/4, 1/16, 1/16 dotted, etc. Here, you have ticks, from 128 to 0.5 in 1-unit increments. How does this translate into 1/4, 1/16, 1/16 dotted, etc.? Is there a formula?

IIRC a setting of 4 ticks is 1/4, 2 is 1/2 and 1 tick is 1/16. Something like that, but George might have a better explanation for you.

[e-musician]

Discovery Pro 7.8 released.

• New Silver Haze skin by Ilkka Rosma.
• Updated default Nordic Dawn skin.
• New Shadow Wave skin.
• Updated and new skins now include 30x and 40x assets for high-resolution 1.5x and 2x GUI size display.
• Fixed standalone program change function.
• Fixed Quick Stack behavior. Now, current layer blinks if it's active.
• Added octave submenus to Custom Key Split dropdown.
• Clicking Key Split dropdown / led now rotates between Off, Dual, Custom, Custom (edit) states.
• Other minor fixes and enhancements.

Hm, strange ... After updating, the new skins are listed in "Skins" but clicking on either of them doesn't do anything. The assets (images), however, are all there, in the Documents folder, where they are supposed to be, and where all the pictures for the other skins reside, too.
Loading the new skins doesn't work, no matter if standalone, VST2 or VST 3, and no matter which size is chosen. And as the default red Nordic Dawn is not in the Documents folder, I can't tell if the skin that loads per default is the updated version.
The version number, though, is shown as 7.8.

Has anyone else been encountering this problem? Or, has anyone been able to successfully load the new skins?

BTW: I'm on Windows 10.

[mountainmaster]

Hm, strange ... After updating, the new skins are listed in "Skins" but clicking on either of them doesn't do anything. The assets (images), however, are all there, in the Documents folder, where they are supposed to be, and where all the pictures for the other skins reside, too.
Loading the new skins doesn't work, no matter if standalone, VST2 or VST 3, and no matter which size is chosen. And as the default red Nordic Dawn is not in the Documents folder, I can't tell if the skin that loads per default is the updated version.
The version number, though, is shown as 7.8.

Has anyone else been encountering this problem? Or, has anyone been able to successfully load the new skins?

BTW: I'm on Windows 10.

I am now using the new Silver Haze skin. No problems with loading on Windows 11.

[george]

The vst3 version is buggy in Bitwig 4.3. For example, if I move the OSC2 pitch knob, the amplitude attack knob also moves (they sync together). This doesn't happen with the vst2 version.

Please unzip the attached file and add the MIDI template Custom.xml and switch to that one. You can find the location of the file at Documents > discoDSP > Discovery Pro > MIDI. Once you replace the file, it should work correctly. We are working on a fix.

[e-musician]

Hm, strange ... After updating, the new skins are listed in "Skins" but clicking on either of them doesn't do anything. The assets (images), however, are all there, in the Documents folder, where they are supposed to be, and where all the pictures for the other skins reside, too.
Loading the new skins doesn't work, no matter if standalone, VST2 or VST 3, and no matter which size is chosen. And as the default red Nordic Dawn is not in the Documents folder, I can't tell if the skin that loads per default is the updated version.
The version number, though, is shown as 7.8.

Has anyone else been encountering this problem? Or, has anyone been able to successfully load the new skins?

BTW: I'm on Windows 10.

I am now using the new Silver Haze skin. No problems with loading on Windows 11.

Thanks for your reply!

Meanwhile, I have found out what the reason for the issue I described is, and I am posting this here just in case others might encounter the same problem - which I highly doubt .

It seems that Discovery Pro can only deal with a certain amount of skins inside the "Skins" folder, with the maximum number of skins being 35 (so, together with the default one, that gives you a total of 36 skins).
If you have more than 35 skins in the folder, you will be able to choose from the first 35 skins listed "only". In my case, I had 39 skins in the folder at the time of writing. And as the new skins Shadow Wave and Silver Haze were at the very bottom of the list, I could not load them.
So, deleting some skins in the folder has solved the problem.

[Ghostwave]

The vst3 version is buggy in Bitwig 4.3. For example, if I move the OSC2 pitch knob, the amplitude attack knob also moves (they sync together). This doesn't happen with the vst2 version.

Please unzip the attached file and replace the MIDI template Default.xml with the new one. You can find the location of the file at Documents > discoDSP > Discovery Pro > MIDI. Once you replace the file, it should work correctly. This fix will be added for version 7.8.1.

Thanks for looking to it. I did exactly what you asked but the issue is still present. Maybe it's a problem on my end. Is anyone else having the same issue?

[george]

Thanks for looking to it. I did exactly what you asked but the issue is still present. Maybe it's a problem on my end. Is anyone else having the same issue?

Rename it to Custom.xml and select it using MIDI. The issue wasn't as easy to fix and we are working on it.

[Ghostwave]

Thanks for looking to it. I did exactly what you asked but the issue is still present. Maybe it's a problem on my end. Is anyone else having the same issue?

Rename it to Custom.xml and select it using MIDI. The issue wasn't as easy to fix and we are working on it.

Still the same problem. However, If I select another one like the Access Virus TI2 Desktop, the knobs are no longer linked (but they are with the next one down, Arturia MicroFreak)

Edit: Another thing I noticed is that most of the vst3 version's automation parameters aren't picked up by Bitwig. The vst2 one works as it should.

[george]

Still the same problem. However, If I select another one like the Access Virus TI2 Desktop, the knobs are no longer linked (but they are with the next one down, Arturia MicroFreak)

Yes, it looks like the VST3 wrapper can't handle two different internal parameter types properly, which explains why it happens with VST3 build only. Working on a fix.

[seangm]

Man you guys (Disco DSP) really need to get a proper account management system on your site. Tried five times to login to get the update, entered the invoice # and it supposedly emailed me a 6 digit code which never arrived (checked spam folder of course, blah blah blah). So no way to access the update. This has happened before to me with Disco DSP and it's pretty damn annoying. Just use a standard email/password combo to let us login and download our products like pretty much every other developer. I need to look up the invoice number every time I want to download something and half the time the email verification isn't sent. It's putting me off to their products, too much aggravation and time wasting.

[dayjob]

Man you guys (Disco DSP) really need to get a proper account management system on your site. Tried five times to login to get the update, entered the invoice # and it supposedly emailed me a 6 digit code which never arrived (checked spam folder of course, blah blah blah). So no way to access the update. This has happened before to me with Disco DSP and it's pretty damn annoying. Just use a standard email/password combo to let us login and download our products like pretty much every other developer. I need to look up the invoice number every time I want to download something and half the time the email verification isn't sent. It's putting me off to their products, too much aggravation and time wasting.

i had the same issue. it showed up eventually but took all day. there's a logjam in the system somewhere.

[seangm]

Man you guys (Disco DSP) really need to get a proper account management system on your site. Tried five times to login to get the update, entered the invoice # and it supposedly emailed me a 6 digit code which never arrived (checked spam folder of course, blah blah blah). So no way to access the update. This has happened before to me with Disco DSP and it's pretty damn annoying. Just use a standard email/password combo to let us login and download our products like pretty much every other developer. I need to look up the invoice number every time I want to download something and half the time the email verification isn't sent. It's putting me off to their products, too much aggravation and time wasting.

i had the same issue. it showed up eventually but took all day. there's a logjam in the system somewhere.

Yeah it finally came through after a few hours. I'd still prefer a real account to login to but as long as I can get to the download for now.