Artefacts sounding like a Bit Crusher

[nkf]

Hi,

I don't disbelieve you, I'm just trying to nail down some specific parameters for the problem. As I mentioned in my previous post, we need some specifics. Can you make us a preset that illustrates the problem and post it here or send it in as a support ticket? This would give me something specific for the software developers to look at.

Greg

As I wrote a preset can't do it - it doesn't matter, because it has to do with knob movement, no matter if the DAW (Nuendo 11) is running or not. Just use the settings I showed in a screenshot here. Is that too difficult to dial in roughly two parameter settings and flipping a switch and then twist the knobs as described several times here? If you think that is NOT specific enough, I give up - this is an unproductive behaviour from your side.
I'm getting angry how this thread now develops. You have way enough info now. Maybe you haven't read closely enough.

[cherryaudio Greg]

Hi,

But the settings do matter? Did you say it didn't happen if you just select New? Or if you click New (resetting to the default settings), can you get it to happen?

The screenshot seems to show basically the New state, with Sync turned on, Direct Signal and Reverb off, Repeat Rate and Intensity turned up.

Are those changes necessary to reproduce the problem? Does Sync have to be turned on? Does Direct Signal have to turned off?

If you can reproduce it after clicking New, would we reproduce it by just turning up Repeat Rate all the way, or do you also have to increase Intensity?

Thanks for your patience!



Greg

[nkf]

Hi,

But the settings do matter? Did you say it didn't happen if you just select New? Or if you click New (resetting to the default settings), can you get it to happen?

The screenshot seems to show basically the New state, with Sync turned on, Direct Signal and Reverb off, Repeat Rate and Intensity turned up.

Are those changes necessary to reproduce the problem? Does Sync have to be turned on? Does Direct Signal have to turned off?

If you can reproduce it after clicking New, would we reproduce it by just turning up Repeat Rate all the way, or do you also have to increase Intensity?

Thanks for your patience!



Greg

I'm, now sure you haven't read my descriptions (carefully)! You cause unnecessary work for us here. May be you read it this time carefully enough!?
I'm not a native English speaker, but I know my English isn't that bad, that I couldn't make clear how to proceed. It is now my last post for this topic, it is getting absurd here. I explained in this thread:
"You can use any preset! The problem is not baken into a preset setting! It is all about playing audio into the input, raise "Intensity" to have some feedback and speed up and down the delay times. If you do it several times and then lengthen the delay time (bring "Repeat Time" to the counter left!) just listen to the result ...
There is your "devil"! Was it clearer now?"
"It doesn't matter if you choose a new preset, recall one or whatever. When the problematic parameters are chosen the problems begin.
Use Nuendo 11 (Mac or PC), the VST3 of StarDust 201 is loaded and dial in the settings in my screenshot. Play some notes of VSTi or alike, make it clear, simple sounds. Let the feedback roll - now quickly< turn Repeat Rate to the left to the longest rate, bam! nice bit crusher sounds.
It is 100% repeatable in N11. In WaveLab I was NOT able to reproduce it. You have to use Nuendo 11 - newest release 11.0.40.
Don't use other hosts to replicate this problem."
"As I wrote a preset can't do it - it doesn't matter, because it has to do with knob movement, no matter if the DAW (Nuendo 11) is running or not. Just use the settings I showed in a screenshot here. Is that too difficult to dial in roughly two parameter settings and flipping a switch and then twist the knobs as described several times here?"

[cherryaudio Greg]

Hi,

It would help if you could directly answer my questions. I take it from what you just posted, that I could do the following and hear the problem?

1. Use VST3 in Nuendo.
2. Click New to set the default preset.
3. Turn up Intensity and Repeat Rate.

Is that correct, or is there more to it? If you try that right now, do you hear the problem?

Or do I have to recreate your screenshot with the other settings?

Does it only happen with VST3? Does it happen with VST?

Greg

[nkf]

Now several months are gone and there isn't still a new update available to prevent the 'bit crusher sound' problems.
When can we expect an update? Also for implementing a noise on/off switch.

[cherryaudio Greg]

Hi,

It only happens with VST3 in Nuendo?

Greg

[nkf]

You guys want to have your customers doing the detail work!? It would be easy for yourself to try that.
But I did try the VST2 in Nuendo 11.0.41. When trying to replicate this bug Nuendo just crashes, pooof ... just gone.
here are the crashed threads:
Process: Nuendo 11 [1395]
Path: /Applications/Nuendo 11.app/Contents/MacOS/Nuendo 11
Identifier: com.steinberg.nuendo11
Version: 11.0.41.448 (11.0.41.448)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Nuendo 11 [1395]
User ID: 501

Date/Time: 2022-01-24 19:17:43.624 +0100
OS Version: Mac OS X 10.14.6 (18G6032)
Report Version: 12
Anonymous UUID: xxxxxxxxx


Time Awake Since Boot: 14000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1395]

VM Regions Near 0x18:
-->
__TEXT 000000010313c000-00000001068ea000 [ 55.7M] r-x/rwx SM=COW /Applications/Nuendo 11.app/Contents/MacOS/Nuendo 11

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.cherryaudio.stardust201 0x000000016ae4142d juce::Slider::Pimpl::sendDragEnd() + 13
1 com.cherryaudio.stardust201 0x000000016ae56498 juce::Slider::Pimpl::~Pimpl() + 296
2 com.cherryaudio.stardust201 0x000000016ae55f5e juce::Slider::Pimpl::~Pimpl() + 14
3 com.cherryaudio.stardust201 0x000000016ae3db3e juce::Slider::~Slider() + 62
4 com.cherryaudio.stardust201 0x000000016ab120c8 non-virtual thunk to PSKnob::~PSKnob() + 24
5 com.cherryaudio.stardust201 0x000000016aaf2222 PSHost::ModuleComponent_FreeComponent(long) + 66
6 Module.dylib 0x000000016b40b080 ModuleComponent::~ModuleComponent() + 48
7 Module.dylib 0x000000016b40b83e ModuleKnob::~ModuleKnob() + 14
8 Module.dylib 0x000000016b413d09 Stardust201::~Stardust201() + 441
9 Module.dylib 0x000000016b40f35e Stardust201::~Stardust201() + 14
10 com.cherryaudio.stardust201 0x000000016ac04fd7 PSContainer::OnShutDown() + 295
11 com.cherryaudio.stardust201 0x000000016abd50ae GuiManager::ReloadPlugin() + 3150
12 com.cherryaudio.stardust201 0x000000016abca784 GuiManager::actionListenerCallback(juce::String const&) + 3508
13 com.cherryaudio.stardust201 0x000000016ad11ea9 juce::MessageQueue::runLoopSourceCallback(void*) + 121
14 com.apple.CoreFoundation 0x00007fff2d02a9fb __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
15 com.apple.CoreFoundation 0x00007fff2d02a9a1 __CFRunLoopDoSource0 + 108
16 com.apple.CoreFoundation 0x00007fff2d00e8af __CFRunLoopDoSources0 + 195
17 com.apple.CoreFoundation 0x00007fff2d00de77 __CFRunLoopRun + 1196
18 com.apple.CoreFoundation 0x00007fff2d00d779 CFRunLoopRunSpecific + 459
19 com.apple.HIToolbox 0x00007fff2c25e1ab RunCurrentEventLoopInMode + 292
20 com.apple.HIToolbox 0x00007fff2c25dee5 ReceiveNextEventCommon + 603
21 com.apple.HIToolbox 0x00007fff2c25dc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
22 com.apple.AppKit 0x00007fff2a5f577d _DPSNextEvent + 1135
23 com.apple.AppKit 0x00007fff2a5f446b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
24 com.apple.AppKit 0x00007fff2a5ee588 -[NSApplication run] + 699
25 com.steinberg.nuendo11 0x00000001054058d8 0x10313c000 + 36477144
26 com.steinberg.nuendo11 0x0000000105220ba6 0x10313c000 + 34491302
27 com.steinberg.nuendo11 0x0000000104d9cb4d 0x10313c000 + 29756237
28 com.steinberg.nuendo11 0x0000000104d9c98e 0x10313c000 + 29755790
29 com.steinberg.nuendo11 0x0000000104d9ccfb 0x10313c000 + 29756667
30 libdyld.dylib 0x00007fff590293d5 start + 1

Thread 1:: CRASH THREAD
0 libsystem_kernel.dylib 0x00007fff5915e26e semaphore_timedwait_trap + 10
1 com.steinberg.nuendo11 0x0000000104dbfbf2 0x10313c000 + 29899762
2 com.steinberg.nuendo11 0x0000000104125141 0x10313c000 + 16683329
3 com.steinberg.nuendo11 0x0000000104dbee74 0x10313c000 + 29896308
4 libsystem_pthread.dylib 0x00007fff5921d2eb _pthread_body + 126
5 libsystem_pthread.dylib 0x00007fff59220249 _pthread_start + 66
6 libsystem_pthread.dylib 0x00007fff5921c40d thread_start + 13

[martb]

Hi,

It only happens with VST3 in Nuendo?

Greg

nkf previously wrote:

It is 100% repeatable in N11. In WaveLab I was NOT able to reproduce it. You have to use Nuendo 11 - newest release 11.0.40.
Don't use other hosts to replicate this problem.

[nkf]

Yes, as if the VST3 problems alone are not worth to examine what's going wrong.
This handling of a serious bug shatters my good impression I had about Cherry Audio somewhat. It is like not being willing to accept a bug. Instead asking for more confirmation, this and that - just to do nothing about what was already reported.
The problem was reported by others on FaceBook too btw.

[cherryaudio Greg]

But I did try the VST2 in Nuendo 11.0.41. When trying to replicate this bug Nuendo just crashes, pooof ... just gone.
here are the crashed threads:
Process: Nuendo 11 [1395]

Hi,

Thanks for posting your crash info. Can you also send your log files? Please archive them, and then attach them to a support request.

To locate your log files, launch Stardust 201 and click on "Settings" followed by clicking "General". Click "Show Log Folder". Please zip or archive all your log files and attach it to your reply.

Greg