bdejong / smartelectronix Goto Github PK

Hi! Can add resize window?

http://www.steinberg.net/sdk_downloads/vstsdk366_27_06_2016_build_61.zip is no longer live. The get_steinberg_sdk.py should be updated to reflect this.

The correct URL is now:
https://www.steinberg.net/vst3sdk

Hello,

I'm wondering if there is a version of bouncy that's VST 64 so i could use for instance on the latest ableton version?

thank you

Hi,

the old supaphaser AU port had a bug that the preset within a song (Renoise DAW) always was lost after reload... I hope this is fixed now? Could you provide a building script for Apple Developer Tools? Thanks.

Being a mostly non-coder noob I am no doubt missing obvious things, but my attempts to follow your instructions aren't working. I do as specified:

git submodule update --init --recursive
python get_steinberg_sdk.py
cmake .

...and soon get this error:

-- Detecting CXX compile features - done
CMake Error at AnechoicRoomSimulator/CMakeLists.txt:3 (include):
include could not find load file:

/home/cjunit/Code/smartelectronix/AnechoicRoomSimulator/../common/common.cmake

CMake Error at AnechoicRoomSimulator/CMakeLists.txt:5 (pre_build):
Unknown CMake command "pre_build".

-- Configuring incomplete, errors occurred!

The specified file IS in the git clone root at "/common/common.cmake". It seems to me that some step is probably missing. Am I supposed to run "cmake ." from some other directory? I am stuck on what is probably a very simple problem.

Bouncy seems to crash on windows when the plugin is deleted...

Smexoscope has 2 times the same image resource, remove one.

I used these for tons of tracks back in the day. Supatrigga, in particular, is a favorite. I'd love to be able to use these plugins on newer machines in Logic and Garageband. These apps don't support VST, so AU is the only option.

Thank you!

Crashes on OSX 10.9.4 using Renoise 3.1 64bit under some specific scenario. Renoise just says "GUI crash", and then emergency-saves the song.

Steps to reproduce:

1. Renoise 3.1 64 bit, put plugin into track
2. Move all sliders and controls to minimum position (left / down)
3. Save song
4. Reload same song -> crash appears

Create modular build system for all plugins

Dark and original versions both show up as s(M)exoscope (Bram @ Smartelectronix) in Reaper so you don't know which one you're going to get. "Dark" should be added to the title.

Hi, how do I compile s(M)exoscope so that it works as a 64-bit AudioUnit on macOS High Sierra?

http://stackoverflow.com/questions/20610255/how-to-tell-cmake-where-to-put-build-files

apparently you can set the build directory with -B -H
this could be used to simplify the AppVeyor config

Hello there.
I have interest in these plugins (specially making them work on Linux) so I have a few questions...
Do you request a CLA for every single change? I see this PR #40 was just about a README, but you still mentioned it.
(tbh I think you are just pushing developers away asking for this)

I do not want to sign a CLA, but want to make use of these plugins.
Any chance at all you will import changes / fixes, or do I have to maintain a fork?

Hi!

Not sure if you are active here. But I’m one of the maintainers on Surge (https://surge-synthesizer.github.io/) a free and open source synth. We are about to do our 1.8 release and in that release we integrated quite a bit of open source software from elsewhere into the Surge signal path including filters from Odin, and effects from Airwindows.

Looking at our 1.9 release we came across this repo and were thinking that some of these FX would be lovely FX in the surge chain also. Would probably integrate them similarly to how we did Airwindows (namely have a ‘Airwindows’ effect with sub-types). And we are GPL3 and you are GPL3.

But before we go and do something like that, we like to ask folks. Would you be OK if we integrated some of these effects (with full credit to you and authors of course) into the surge signal path?

Thanks for releasing free and open source audio software! And Happy new Year!

as per subject

silly, but do it anyway :)

Currently I get:

Packaging artifacts...OK
Skip "GitHub" deployment as environment variable has not matched ("appveyor_repo_tag" is "false", should be "true")
Build success

Which is weird. This might have to do with the fact that I'm using git push --follow-tags rather than separate push and push --tags, or... something else.

The documentation is a bit.... dense:
https://www.appveyor.com/docs/deployment/github

Hi,

As the download page for the last versions of the plugins doesn't work anymore (only got "Forbidden!" displayed) i tried my best to make it with brew but when i try to "Make" i got this error after 35% completed :

/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:34:10: fatal error: 
      'CarbonSound/CarbonSound.h' file not found
#include <CarbonSound/CarbonSound.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

Is it because i have Mac os Mojave 10.14?

Also could you possibly update the x64 plugin download page so i could take the easy path by downloading the last versions of your plugins ? Because even if i tried my best I'm not so good with compiling as you can see..

All parameter getting and setting should really be done with std::string and stringstream for concatenating/etc... This would be so much cleaner...!

The provided link to download builds does not work .. :\

as per subject

Can someone please send me a version of Smexoscope with the dark skin for PC? I have not been able to find one and can't figure out how to get it from here. I'd really appreciate if someone can get back to me on here thanks!

was it Ambience??...
stilll around ? ..
windows ?:)

In many of the plugins the VST code and the processing code are mixed freely. This is kind of ugly...

as per subject

as per subject

As per subject

build.ps1 and get_steinberg_sdk.py should probably be inside a utils directory...

Running 'python3 get_steinberg_sdk.py' gives a file not found error:

File "get_steinberg_sdk.py", line 30, in <module>
    os.rename("VST3 SDK", "Steinberg")
FileNotFoundError: [Errno 2] No such file or directory: 'VST3 SDK' -> 'Steinberg'

This then leads to 'cannot find source file' errors when running 'cmake .' My suspicion is Steinberg have altered the directory structure of their SDK. Any chance you could take a look into this?

(For info: MacOS 12.6, Python 3.8.2, Homebrew 3.6.5, cmake 3.24.2).

Thanks!

Create a simple appveyor and travis C++ example - "hello world", that uses the same cmake/32/64 build settings as the plugins. Publish to github and try to get the release deployment working in that example project...

Great job, wonderful plugin... I've wanted to run this for the longest time, and could not because of the original being 32-bit. Major kudos to this developer, since now I can!

Not sure if s(M)exoscope is still being monitored on GitHub, but I wanted to submit a feature request, if that sort of thing is still being considered.

I'm currently migrating from Cakewalk to Mixbus. One of the glaring omissions I've noticed in Mixbus is the ability to monitor bus/master waveforms in real-time. I've included screen captures of this in both Cakewalk and Mixbus, for the sake of clarity. In the Cakewalk capture, the waveforms are being displayed in the editor bus/master lanes under the play head (at bottom of capture, in orange). In the Mixbus capture, the editor bus/master lanes are in red, just sitting there blank, doing absolutely nothing. Seems useless to me, and I can't imagine why Harrison does not display any useful information there.

The ability to monitor bus/master waveforms as the play head travels down those bus strip lanes is important, for a number of reasons:

• To display clipping (I can't always mix in floating point, for various reasons).
• The effect of any mixer adjustments be seen in the waveforms, instantly.
• Most importantly, a method to observe them as they relate to each other is a must-have.

Please forgive my lack on knowledge on this subject, as I'm not very familiar with C/C++, nor do I know much about its capabilities when it comes to DAW plugins.

Would one either of these things be possible?

• Add a feature which would allow s(M)exoscope output to display in-line in the plugin area of the DAW mixer strip, with adjustable height and length of sample. This would allow the monitoring of bus/master waveforms in the mixer, right next to each other. Currently, popping open multiple s(M)exoscope windows takes up a lot of display real estate, and this would totally solve that problem.

If all of the s(M)exoscope controls could be enabled in mixer automation, that would be a great thing too.

-or-

• Display bus waveforms in the editor, as is the case with Cakewalk. I doubt this is possible, but that would be ideal, so I just have to ask.

If the s(M)exoscope developer is still monitoring GitHub, thanks much in advance for your consideration, I appreciate it!

I've noticed this whilst working on trying to get everything up to scratch and working properly.
I can't figure out yet if this is an issue with vstgui itself, but it's the case for all the plug-ins here using vstgui4.3 with vstsdk2.4

The code here (for instance smexoscope) calls the GUI setParameter function from the setParameter function of the effect. Yet somehow the GUI still doesn't update.

Even more confusing is that the GUI displays the wrong values for the labels at all times. You can easily see this by Ctrl-Left-Clicking to do a knob reset, then you can see the displayed value is totally different to what it should be. Investigating this over the next few days.

I also need to do some more work to ensure it's not just my build.
I only recently noticed the .py script to set up the sdk files from .zip, so I'll clear my project and run that and see if it's some version dependencies issue.

as per subject

Seems like the bitray link is dead. I think you should be able to host the built vsts from this github page.

Not sure if this is suitable to post here but I don't know where else to contact.
https://dl.bintray.com/bdejong/Plugins/
and
http://bram.smartelectronix.com/
are both down, which host these plugins. KVR thread indicated they've been down for a bit: https://www.kvraudio.com/forum/viewtopic.php?t=485775

In the readme it says to run:
python get_steinberg_sdk.py

which doesn't work in python 3.x, but does in 2.x

so either it'd be good to update the readme, or update the script to support both python versions.

Error message is:
****Audio\smartelectronix_2>python get_steinberg_sdk.py
File "get_steinberg_sdk.py", line 15
print "{}%".format(progress)

Which looks easy enough to fix. Once I send you my signed NDA I'll add a PR.

The .rc files are rather simple now and could be pre-built in cmake. Just some regular templating is all that is needed with an resource.rc.in file as input.