Obxd synthesizer

[george]

This is not at all what I am talking about. I am talking about DISPLAY VALUE in the tooltip (and host automation), not mouse dragging resolution. I would like the tooltip to show the cents precision, not deca-cents. So instead of "-0.1" I would like it to have two digits of precision, "-0.01".

It will help with more precise finetuning.

We appreciate your suggestion and recognize its potential value in improving the user experience. Currently, our system is set to a specific precision level, but we are always open to considering enhancements based on user input.

While we may not be able to implement this change immediately, I'll ensure your feedback is forwarded to our development team for consideration in future updates. We constantly strive to improve our software, and user suggestions are a vital part of this process.

Thank you again for bringing this to our attention.

[mcbpete]

Guess I can't pay to support the update... (tried 3 times but then gave up)

Order Failed
We regret that your payment or order could not be accepted. There are many reasons why this might occur. We value your business and would like to help you complete this order

[Vortifex]

..

[mixyguy2]

Well I love this synth so I'm happy to see it continuing to be updated. Was instantly turned off by the "THIS CHANGES EVERYTHING" text in the YT preview, though. Absolutely detest that kind of desperate baiting BS, but I supppose that's the era we live in...

Which is why I never click on such BS. I'm a fan of ob-xd though.

[george]

@mcbpete
Hello mcbpete,

I'm sorry to hear that you're having trouble with your payment. Could you please provide some more details about the issue? It would be helpful to know the payment method you were using and any error messages you received. In the meantime, you might want to check if your bank has any restrictions on online transactions. Feel free to contact us directly at our support page for further assistance.

@Vortifex
Hi Vortifex,

Thank you for your suggestion regarding the manual. Adding a section about the preset system is indeed a good idea. We will consider this for our next update. If you have any specific questions or need assistance with the preset system, don't hesitate to reach out to us through our contact form.

@mixyguy2
Hello mixyguy2,

We appreciate your feedback on the synth and the marketing approach. We understand that certain promotional styles may not appeal to everyone, and we always value honest input from our community. If you have any specific suggestions or concerns, feel free to share them with us. Your support as a fan of ob-xd is much appreciated!

[beely]

Just saw this was out (great - thanks!) and just tried it (AU version in Logic). It overwrote/replaced my old 2.14 version (the installer "upgraded" it, so presumably deleted the V2.x version, as it was no longer there in Logic after the install of the new version), and none of the AU presets I saved for V2.x, despite being shown for the V3 plugin load now, so all the patches saved out to the host no longer work (and presumably, any projects that also saved the state of the plugin won't recall correctly either).

So I reran the 2.14 installer, and this deleted V3, and replaced it with 2.14 again ("upgrade" again.)

If this new version is incompatible with the V2.x version, why didn't you just give it a new plugin ID, so both versions can co-exist on the same system, the old V2.14 and patches will continue to work, as will old project recall, and then users can start to use V3 as they like?

Edit: If I don't use the installer and instead manually put V2.x and V3 in the Components folder, Logic will see one "OB-Xd" plugin but give to different, undifferentiated "Stereo" versions - the first "Stereo" being V3, and the second "Stereo" being V2 - with V2 being able to recall the AU presets as before. (Though I don't know if this will give issues with project recall by loading V3 by default).

Very strange choices here, imo, unless I'm misunderstanding something... If the new version is incompatible with the old version, standard practice is generally to give the new version a new plugin ID, not reuse the previous one and just have old data not load.

For now, my best option is to uninstall V3 I think, as resaving all of those old patches out in V3 (assuming the old patches even load) is a lot of effort...

[seangm]

If you do the upgrade to 3.0 double check your cart before paying. An expansion I already own was added to the cart somehow (I'm sure I just hit "Next' and that was it) and I stupidly placed the order with my brain on autopilot without realizing it was in the cart. Anyway just a heads up to double check the cart before paying.

[george]

Just saw this was out (great - thanks!) and just tried it (AU version in Logic). It overwrote/replaced my old 2.14 version (the installer "upgraded" it, so presumably deleted the V2.x version, as it was no longer there in Logic after the install of the new version), and none of the AU presets I saved for V2.x, despite being shown for the V3 plugin load now, so all the patches saved out to the host no longer work (and presumably, any projects that also saved the state of the plugin won't recall correctly either).

Thank you for your feedback regarding the OB-Xd 3.x update. OB-Xd 3.x has a new plugin ID and filename, which means it operates independently from the 2.x versions. Importantly, the 3.x installer does not overwrite 2.x files.

If you are a registered user and need further assistance with this transition, our support team would be happy to help. You can reach out to us at https://www.discodsp.com/support for more personalized support.

OB 3.x will load 2.x presets, as we have coded a parser that will translate them. Ensure they are in FXP/FXB format and saved using OB-Xd, not the DAW functions.

[george]

If you do the upgrade to 3.0 double check your cart before paying. An expansion I already own was added to the cart somehow (I'm sure I just hit "Next' and that was it) and I stupidly placed the order with my brain on autopilot without realizing it was in the cart. Anyway just a heads up to double check the cart before paying.

Thank you for bringing this to our attention. It's possible that the item was added to your cart in a existing session or from a previous purchase attempt and got saved in the browser. Please rest assured that we do not, under any circumstances, add other products to your cart automatically. We always aim to provide a transparent and user-controlled shopping experience.

[BrokenTrance]

no update to the discodsp preset browsers yet?????

[digitalboytn]

We always aim to provide a transparent and user-controlled experience.

[beely]

Thank you for your feedback regarding the OB-Xd 3.x update. OB-Xd 3.x has a new plugin ID and filename, which means it operates independently from the 2.x versions.

Logic does not recognise V3 as a different plugin to V2, which is why when they are both installed, both show up under the same plugin name. I will investigate more, possibly the installer overwriting the plugin is confusing the AU cache. I will also check the ID's my system sees.

Importantly, the 3.x installer does not overwrite 2.x files.

This is incorrect, and is not how the installer behaves here. With 2.14 installed, running the Mac V3 installer "upgrades" 2.14 to V3 - the V2.14 component is deleted and the V3 component is left in it's place. I just did it again and observed the plugin folder and it's demonstrably true - the V3 AU does indeed remove V2 when installing V3. I can happily show you if it's something you want to check, because the Mac installer is not behaving how you intend it to behave in that regard.

(Also, re-installing V2 overwrites the V3 component in the same way.)

[mixyguy2]

@mixyguy2
Hello mixyguy2,

We appreciate your feedback on the synth and the marketing approach. We understand that certain promotional styles may not appeal to everyone, and we always value honest input from our community. If you have any specific suggestions or concerns, feel free to share them with us. Your support as a fan of ob-xd is much appreciated!

Thank you for that very diplomatic response. Basically spare us the sensationalism would be my vote. But that said, if it seems to be working for you, it's hard to argue with results. Just IMO

And thank YOU for a great synth. The only other thing I would ask for is some Jan Hammer presets You get some presets to match this and I'll have your love child...

[george]

Thank you for that very diplomatic response. Basically spare us the sensationalism would be my vote. But that said, if it seems to be working for you, it's hard to argue with results. Just IMO

And thank YOU for a great synth. The only other thing I would ask for is some Jan Hammer presets You get some presets to match this and I'll have your love child...

Thank you for your kind words and constructive feedback. We're delighted to hear that you're enjoying our synth and appreciate your honest input regarding our communication style.

Regarding your request for Jan Hammer-inspired presets, it's a fantastic suggestion! Jan Hammer's work, especially his iconic sounds in the '80s, has been a source of inspiration for many. While we currently don't have presets specifically modeled after his style, I'm thrilled to take this suggestion back to our team. It's ideas like these that help us enhance our product and cater to the diverse musical tastes of our user base.

In the meantime, our existing presets offer a wide range of sounds that you might find useful and inspiring. We also encourage our users to experiment with the synth's parameters to create their unique sounds, possibly even capturing some of that classic Jan Hammer essence!

We're continually working on updates and new features, and feedback like yours helps guide our efforts. Please keep an eye out for future updates, as we're always looking to add more exciting content that resonates with our users.

Thank you once again for your support and for being a part of our community. Your enthusiasm for our product is what drives us to keep innovating and improving.

[george]

This is incorrect, and is not how the installer behaves here. With 2.14 installed, running the Mac V3 installer "upgrades" 2.14 to V3 - the V2.14 component is deleted and the V3 component is left in it's place. I just did it again and observed the plugin folder and it's demonstrably true - the V3 AU does indeed remove V2 when installing V3. I can happily show you if it's something you want to check, because the Mac installer is not behaving how you intend it to behave in that regard.

Dear beely,

Thank you for your detailed feedback and for highlighting these issues with the OB-Xd 3.x installation on Mac. It's crucial for us to receive such direct user experiences to improve our products and services.

Concerning the installer's behavior, it's troubling to hear that the OB-Xd 3.x installation process is not performing as intended on your system. The reported behavior where version 2.14 is being overwritten by version 3 is not consistent with our design for the installer. We appreciate you bringing this to our attention, and we will conduct a thorough review to address this discrepancy.

We would indeed like to check this issue more closely. Could you please contact us via our contact form? Providing us with your license details and any additional information you can share will be greatly beneficial for our technical support team to assist you effectively.

We apologize for any inconvenience this has caused and are committed to resolving these issues promptly. Your feedback is invaluable in helping us enhance the user experience for all our customers.

Thank you for your patience and cooperation.