Polyverse Music - Comet Reverb

[plexuss]

I'd love a ducking feature...

Run it through a compressor or gate with sidechain?

For the moment I use DDMF Metaplugin to make my own ducking feature but I'm afraid it uses more CPU than needed...

Interesting. I'll have to try and duck the long tail and see what that sounds like. It might just be a cool feature to have. you could use it to modulate the amplitude of the tail as well by muting the sidechain source - that might be interesting with such a long tail.

[Neon Breath]

Comet =

[AssafDarSagol]

Thank you all so much for the wonderful input!
Bypass, ducking it will all be considered!

Does anyone else have an issue with the latest update where 'Size' responds to MIDI and there is no way to disable? When using on individual tracks this feature does not make a lot of sense when you don't want the Size modulated.

I'm not sure i understand the issue. If you don't send midi, it will not modulate the reverb.

[Neon Breath]

Man, I crossed the streams....

Comet crossed with Zynaptiq Adaptiverb in the same fx chain. My god, I think I just passed a sonic event horizon....

[daily patcher]

Thank you all so much for the wonderful input!
Bypass, ducking it will all be considered!

Does anyone else have an issue with the latest update where 'Size' responds to MIDI and there is no way to disable? When using on individual tracks this feature does not make a lot of sense when you don't want the Size modulated.

I'm not sure i understand the issue. If you don't send midi, it will not modulate the reverb.

Easiest way to replicate this is to load up a DAW (maybe this is affecting Bitwig only? I am surprised no one else has reported this), place a VST in an instrument track and put Comet after the VST. Feed MIDI into the instrument track. Comet will always respond to the MIDI even if you just want the instrument VST placed before Comet to use the MIDI data.

So, with Comet placed after a VST in a chain that has MIDI going into it, Comet is listening and the reverb size is reacting to MIDI even though it's placed after the VST. This is not desirable behavior when you are just trying to use it with no Size changes.

Ideally, there is a toggle for Comet to listen and respond to MIDI for the Size parameter. Having it ALWAYS respond to MIDI is problematic for individual tracks (this may be DAW specific)

[AssafDarSagol]

That is a perfect explanation, We will issue a fix for this one very soon.

[Sound Author]

Weird. In Ableton, I can't get MIDI note data to change the size. I thought there would be some sort of MIDI routing thing to pipe it in, but apparently you just place comet after a VST on a MIDI track and it "listens"? It doesn't seem to be listening very well, because I can't hear anything different.

[shonky]

After looking at the morphing possibilities with Comet, I rediscovered Reverbical which allows you to set up 64 different reverbs on a grid and morph between them. Different beast to Comet but worth checking out, doesn't get enough love in my opinion www.realtimeonly.com

https://www.youtube.com/watch?v=Wuv1IIAiZTs

[daily patcher]

That is a perfect explanation, We will issue a fix for this one very soon.

Much appreciated!

Weird. In Ableton, I can't get MIDI note data to change the size. I thought there would be some sort of MIDI routing thing to pipe it in, but apparently you just place comet after a VST on a MIDI track and it "listens"? It doesn't seem to be listening very well, because I can't hear anything different.

I think Ableton handles MIDI a bit differently then, as does Logic - I cant replicate this in Logic, only seems to happen in Bitwig.

[Sampleconstruct]

Processing a granular lithophone texture with Comet, morphing between five custom presets. This plug-in will also be very useful on stage, the CPU load is low, sound is great and the morphing too.

https://www.youtube.com/watch?v=TyQ748Qj8G4

[Hez]

Easiest way to replicate this is to load up a DAW (maybe this is affecting Bitwig only? I am surprised no one else has reported this), place a VST in an instrument track and put Comet after the VST. Feed MIDI into the instrument track. Comet will always respond to the MIDI even if you just want the instrument VST placed before Comet to use the MIDI data.

So, with Comet placed after a VST in a chain that has MIDI going into it, Comet is listening and the reverb size is reacting to MIDI even though it's placed after the VST. This is not desirable behavior when you are just trying to use it with no Size changes.

Ideally, there is a toggle for Comet to listen and respond to MIDI for the Size parameter. Having it ALWAYS respond to MIDI is problematic for individual tracks (this may be DAW specific)

Bitwig is somewhat unique amongst DAWs in that it doesn't really separate VST instruments from VST effects - on any instrument/MIDI channel, MIDI flows through all the devices on the channel unless you manually 'stop' it at some point. Most other DAWs will require an instrument/MIDI channel to have a VST instrument (not VST effect) as the first device on the channel, and no MIDI signal will continue downstream after the VST instrument.

The easiest way to handle this in Bitwig is to put a Note Receiver device right after your VST instrument if you don't want downstream VST FX to respond to the MIDI controlling the instrument.

[Sound Author]

Okay, so yay, MIDI implementation works great in Bitwig.

As for the rest of us, what do we do to make it work for us?

[Gamma-UT]

Okay, so yay, MIDI implementation works great in Bitwig.

As for the rest of us, what do we do to make it work for us?

In Live, it works the same way as effects like Stutter Edit. You need to set up a second MIDI track.

In that track, don't add anything to it, just click in the "MIDI To" dropdown just above where the Sends would be if it were an audio-enabled track. Select the Live channel that contains Comet and then select 1-Comet in the box that appears below that (it will say "Track In" when it appears). Arm that track and play keys.

[Sampleconstruct]

I´m trying to open a Logic project made yesterday which involves Comet and it always crashes, here is the important part of the crashlog - this is on Sierra, Mac Pro (ashtray model):

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.polyversemusic.comet 0x000000015671d996 0x15669b000 + 534934
1 com.polyversemusic.comet 0x00000001566d6b10 0x15669b000 + 244496
2 com.polyversemusic.comet 0x00000001566e238e 0x15669b000 + 291726
3 com.polyversemusic.comet 0x000000015669d1d8 0x15669b000 + 8664
4 com.polyversemusic.comet 0x00000001566ad49e 0x15669b000 + 74910
5 com.polyversemusic.comet 0x00000001566b7c28 0x15669b000 + 117800
6 com.apple.audio.toolbox.AudioToolbox 0x00007fff87e20583 APComponent::NewInstance(unsigned int, bool, void (ComponentInstanceRecord*, int) block_pointer) + 619
7 com.apple.audio.toolbox.AudioToolbox 0x00007fff87e19517 Instantiate(OpaqueAudioComponent*, unsigned int, bool, void (ComponentInstanceRecord*, int) block_pointer) + 110
8 com.apple.audio.toolbox.AudioToolbox 0x00007fff87e1994d __AudioComponentInstanceNew_block_invoke + 95
9 com.apple.audio.toolbox.AudioToolbox 0x00007fff87e19867 AudioComponentInstanceNew + 315
10 com.apple.music.apps.MAAudioEngine 0x000000010a515663 CMDAudioUnit::CreateAudioUnit(void*) + 179
11 com.apple.music.apps.MAAudioEngine 0x000000010a5153a5 CMDAudioUnit::CMDAudioUnit(int) + 2565
12 com.apple.music.apps.MAAudioEngine 0x000000010a514977 CMDAudioUnit::CreateAudioUnit(int) + 535
13 com.apple.music.apps.MAAudioEngine 0x000000010a41c341 MD::GetProtoPlug(short) + 545
14 com.apple.music.apps.MAAudioEngine 0x000000010a41c46b MD::NewPlug(CPlugIn**, short, long, long, long, bool) + 43
15 com.apple.logic10 0x0000000105c97e94 0x105986000 + 3219092
16 com.apple.logic10 0x0000000105af708b 0x105986000 + 1511563
17 com.apple.logic10 0x0000000105af5184 0x105986000 + 1503620
18 com.apple.logic10 0x0000000105af2a65 0x105986000 + 1493605
19 com.apple.logic10 0x0000000105ac097a 0x105986000 + 1288570
20 com.apple.logic10 0x00000001069140ac 0x105986000 + 16310444
21 com.apple.logic10 0x00000001059fcf9c 0x105986000 + 487324
22 com.apple.logic10 0x0000000105d993d0 0x105986000 + 4273104
23 com.apple.logic10 0x0000000105e48f5b 0x105986000 + 4992859
24 com.apple.logic10 0x000000010640199c 0x105986000 + 10992028
25 com.apple.logic10 0x00000001063b5306 0x105986000 + 10679046
26 com.apple.logic10 0x00000001063b550b 0x105986000 + 10679563
27 com.apple.AppKit 0x00007fff86c1add7 -[NSDocument _initWithContentsOfURL:ofType:error:] + 172
28 com.apple.AppKit 0x00007fff86c1acbc -[NSDocument initWithContentsOfURL:ofType:error:] + 231
29 com.apple.AppKit 0x00007fff86cf82b0 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 644
30 com.apple.logic10 0x0000000106b8547d 0x105986000 + 18871421
31 com.apple.AppKit 0x00007fff86f585bc -[NSDocumentController(NSDeprecated) openDocumentWithContentsOfURL:display:error:] + 915
32 com.apple.logic10 0x00000001070038c3 0x105986000 + 23582915
33 com.apple.Foundation 0x00007fff8a958e49 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
34 com.apple.Foundation 0x00007fff8a958b2c -[NSBlockOperation main] + 101
35 com.apple.Foundation 0x00007fff8a957254 -[__NSOperationInternal _start:] + 672
36 com.apple.Foundation 0x00007fff8a95310b __NSOQSchedule_f + 201
37 libdispatch.dylib 0x00007fff9ea8f8fc _dispatch_client_callout + 8
38 libdispatch.dylib 0x00007fff9ea9caac _dispatch_main_queue_callback_4CF + 925
39 com.apple.CoreFoundation 0x00007fff88f45cc9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
40 com.apple.CoreFoundation 0x00007fff88f06f7d __CFRunLoopRun + 2221
41 com.apple.CoreFoundation 0x00007fff88f06474 CFRunLoopRunSpecific + 420
42 com.apple.HIToolbox 0x00007fff88464ebc RunCurrentEventLoopInMode + 240
43 com.apple.HIToolbox 0x00007fff88464cf1 ReceiveNextEventCommon + 432
44 com.apple.HIToolbox 0x00007fff88464b26 _BlockUntilNextEventMatchingListInModeWithFilter + 71
45 com.apple.AppKit 0x00007fff869f9a54 _DPSNextEvent + 1120
46 com.apple.AppKit 0x00007fff871757ee -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
47 com.apple.logic10 0x000000010700ba7d 0x105986000 + 23616125
48 com.apple.AppKit 0x00007fff869ee3db -[NSApplication run] + 926
49 com.apple.AppKit 0x00007fff869b8e0e NSApplicationMain + 1237
50 com.apple.logic10 0x00000001063a225d 0x105986000 + 10601053
51 libdyld.dylib 0x00007fff9eac5235 start + 1

[plexuss]

I´m trying to open a Logic project made yesterday which involves Comet and it always crashes, here is the important part of the crashlog - this is on Sierra, Mac Pro (ashtray model):

Story of my life. I hate what Apple has done to Logic. Anyway, this is likely one of those weird core audio problems. One way I have of working around this b-llsh-t is to open a new project and put the plugin Logic said crashed it in and then close the project and try opening the project that crashes.

Check this latest Logic bs out that I experienced: all of a sudden a project would start my tracks at different times when I rendered offline in 44.1k. But if I render in realtime it works. it also works at 96k in offline. But going back to 44.1k, offline render, the tracks are out of place. no audio tracks - all midi with v instruments.

Ok I'll stop before I start an anti-apple rant....