naus3a / naumodular Goto Github PK

After letting the Perlin module run for a while the curTime variable (a float) if "full" hitting the float limit and adding deltaTime to it does not have any effect anymore, hence producing a constant output.

The Perlin noise generator is always producing the same pattern.
To reproduce : record the output and have a look to the signal, you'll see a single pattern being repeated.

Some ideas to correct this faulty behavior can perhaps be found here in this very short c++ Perlin implementation (I have not tested this code, just an idea to fix the Perlin generator) :
https://github.com/Reputeless/PerlinNoise/blob/master/PerlinNoise.hpp

Rack v0.5.1 will include a plugin manager, and plugins need to follow the versioning guidelines in order to be accepted. You can use this example plugin Makefile and Tutorial.cpp file as a reference for making sure the version is the same in the C++, Makefile, and JSON manifest.

• Your plugin is versioned as v1.0. This needs to be v0.5.something.

Once you've fixed this, send a PR to the Rack community repository and remove the "disabled" property in the JSON manifest file.

The VERSION needs to be updated in the Makefile to 0.6.0, no dev suffix. Thank you!

Hi,
Here you can find the compiled version for Windows platform (for your releases repo).
Regards.

NauModular-0.5.2-win.zip

NauModular.zip

getting compiler errors for:
arpa/inet.h
and
sys/select.h

first answer on the search said to use Winsock2.h instead, but that doesn't cut it.

Hi!

I m helping Andrew with the plugin manager. I went throu all the module packs today and saw that you only provide Mac binaries. I wanted to know if you need someone to compile your modules for Windows and Linux? Because people like me can´t use your modules unless I compile them myself. Not everyone knows how to do that.

Your plugin is not compatible any longer with the current version of VCV Rack. Are you planning on updating it and releasing a new version?

Please can we have a Linux release?

The Rack way of doing the above is simply

#ifdef ARCH_LIN
...
#ifdef ARCH_MAC
...
#ifdef ARCH_WIN

because the Makefile system passes these defines as flags to the compiler.

With master at c7680cd I get

src/Osc.cpp:209:26: error: ‘memset’ was not declared in this scope
     memset(_buf,0,_bufLen);
                          ^
src/Osc.cpp:210:49: error: ‘strlen’ was not declared in this scope
     uint32_t ii = (uint32_t)strlen(_addr.c_str());
                                                 ^

Including <string.h> appears to it fix for me, for example:

diff --git a/src/NauModular.hpp b/src/NauModular.hpp
index 6a20010..7691b83 100644
--- a/src/NauModular.hpp
+++ b/src/NauModular.hpp
@@ -20,6 +20,10 @@
 #include <mach/clock_types.h>
 #endif
 
+#if defined(TARGET_LINUX)
+#include <string.h>
+#endif
+
 using namespace rack;
 
 extern Plugin * plugin;

Not a linux cpp pro, so not sure how generically useful this info is - hope it's some use! :)

I noticed it opens network ports and I was wondering why.

OS: win
Rack: dev
Plugins: dev

somehow the module just goes mute after a while and i can't turn it back on with any of the controls.
also tried the menu options initialize and randomize.
i have to delete the module and load a fresh instance.

great module ideas btw, thx so much.

I was trying to get a real smooth slow lfo going but it doesn't seem to slow down enough. It seems to just stop. And then it gets worse over time. It will stop at a higher and higher value. Maybe related to that other issue #3

Platform: Windows 7 Pro SP1 x64 (French localized).
VCV Rack v0.5.1 (not dev).
NauModular v0.5.2.

Hello, firstly, thank you very much about your NauModular modules. ;)

However, I report huge voltages issues, concerning BitHammer and Function modules.

I've recorder & posted a (non-indexed) video on YouTube (2 min), showing the voltage issues on these modules. Also, I precise the oscillators I've used, TinySine and TinySawish (both by AS) deliver voltages into range -/+5 V.

Of course it's possible I'm wrong somewhere about voltage measurements, by using Fundamental's Scope.

Perhaps you'll must add a "voltage limitation" in code (for future release) to stay in range -/+12 V (in my opinion).

Link to YT video: here
(please advise me when you have seen it, btw I'll remove it, thanks in advance).

Regards.
Dominique Camus.