Waldorf Pulse 2: officially released (OS updated to v1.18)

[Hermetech Mastering]

Regarding the German interview: OMFG! AN OPTIONAL EFFECTS BOARD!!! Wow, I hadn't heard about this before. Can't wait for details to be released. I hope it has a bucket brigade modulation unit (flanger, chorus, delay etc.) and other nice goodies.

[Marzac@Waldorf]

Hello guys.

The version 1.11 online on our website contains the fix for MIDI thru.
Concerning changelog, there is one, it is included in the zip file.

[Ingonator]

Hello guys.

The version 1.11 online on our website contains the fix for MIDI thru.
Concerning changelog, there is one, it is included in the zip file.

Hi,

this is the changelog included with the text file at the OS 1.11 download:

Changes since V1.10
* Arp / clock troubles when sending clock with MIDI & USB
* MIDI thru can freeze the user interface
* Active sensing works with all clock modes
* Envelope attack time cannot overflow
* Envelope short attack / decay / release time are accurate
* Envelope looping modes fixed
* GUI fixes (redrawing, selection)
* MIDI clock sync / autostart of the arpeggiator
* Spurious behavior when receiving Unimplemented sys. common messages
* New modulation sources / destinations

Changes since V1.05
* Improved hardware / filter tuning
* Corrected VCA curve
* CC remapping with legacy mode working
* New modulation sources
* Sound selection saved on power down
* GUI fixes (parameter selection / editing)
* Corrected drive gain
* Reduction of scanning noise
* Preset / Bank selection fixed


The change called "Corrected drive gain" is resposnible for many factory sounds not sounding like intended (as i already reported). The Drive amount with patches using it has to be reduced by around 20.
I already posted a fix for my own patches here but many patches of other sound designers have to be fixed too.



Ingo

[Tupapupa]

Hello guys.

The version 1.11 online on our website contains the fix for MIDI thru.
Concerning changelog, there is one, it is included in the zip file.

that was the first i have tested yesterday - it still hangs, knobs and display are functioning but it doesn't respond anymore to midi...

[sqigls]

that is a serious bug.
should i stay at 1,1?

[Tupapupa]

why? this bug was also in V1.10

you can help yourself with 2 midi tracks, one for the keyboard, one for recording things from Pulse2 (but no Out Channel here!)

[sqigls]

i see, silly me.

[sqigls]

my Pulse should arrive any day now, just getting nervy

[Tupapupa]

keep quiet, you will not be disappointed

[sqigls]

I actually build MIDI controllers, and I am going to build a dedicated Pulse 2 with all possible parameters available at my fingertips

[Ingonator]

why? this bug was also in V1.10

you can help yourself with 2 midi tracks, one for the keyboard, one for recording things from Pulse2 (but no Out Channel here!)

Hi,

i already heard several times about the MIDI thru bug but could someone tell a procedure how this bug could be easily reproduced (with OS 1.10 or earlier)?

During the Beta test (before official release) i used my Pulse 2 test unit to record tracks with Ableton Live 9 Suite (using the USB connection) and did not observe a crash of either Live or the Pulse 2 there. For recording in Live i also used a keyboard connected by USB instead of the usual MIDI connection (that i use when not recording in Live). I then rendered the audio to an audio track in Live.

Besides for several of my demos i had also recorded the audio directly (no MIDI track recording) using Wavelab Elements 7.

With all those attempts i did not care about any MIDI thru settings either in the Pulse 2 or the DAW software which is maybe a reason why i did not notice that bug during the beta testing.

AFAIK (also in another forum) problems concerning the MIDI thru setting in Cubase were reported and also fixed using a different setting there.


Ingo

[Tupapupa]

You have first to activate the Midi-through in your DAW

normaly if you make a fresh midi track, the input and output are the same
- Pulse2 in this case

if you remove the input to any keyboard for playing (output is Pulse2) - everything is ok


but if you wish to record anything (midi) from the Pulse and switch the entrance from the keyboard to Pulse2 (output is also Pulse2) - then this happens...

but this is not a normal behavior, no other synth doesn't hang up with this



you can temporarily "fix" it with deactivting midi-through in the DAW, but that is nonsense cause you need that for playing any other Synth via a keyboard

the other way is two midi channels
one with the keyboard (input) and Pulse2 (output)
second with pulse2 (input) and NO output - thats for recording from pulse2

[Ingonator]

if you remove the input to any keyboard for playing (output is Pulse2) - everything is ok

but if you wish to record anything (midi) from the Pulse and switch the entrance from the keyboard to Pulse2 (output is also Pulse2) - then this happens...

but this is not a normal behavior, no other synth doesn't hang up with this

you can temporarily "fix" it with deactivting midi-through in the DAW, but that is nonsense cause you need that for playing any other Synth via a keyboard

First I don't see a MIDi trough setting in the Live 9 MIDI setup. I guess this is done automatically with certain routings that are set in the mixer page.

Second this could explain why i did not recognize a problem in Live 9 during the Beta testing. I recorded MIDi notes from a keyboard connected by USB and the notes were sent to the Pulse 2 by another USB connection. As also MIDI thru at the Pulse 2 was turned off it did not transmit MIDI date but just received data.

When using the Pulse 2 without a DAW i used a standard MIDI connection but still with MIDI thru off.


Ingo

[Tupapupa]

Midi through at my Pulse2 is off since i have it, it was also off by default

[luke4421]

Really interested in this synth up in Canada, do the current owners recommend an early purchase?

anywhere I can see a bug list?

Thanks!