réactions à la news Commentaires sur la news : Tonverk, il suffisait d'en parler pour qu'il sorte enfin

keys did not scroll through the song row columns.

The active track was not remembered after reboot.

The default PITCH BEND value was incorrectly set to -128 instead of 0.

There were inconsistent MIDI CC-to-knob mappings across different FX machines for Bus/Send FX/Mix tracks.

Turning the knob counter-clockwise while parameter locking the RTIM parameter did not work correctly.

Attempting to create a directory with an empty name in the File browser resulted in the wrong error message.

The Subtracks machine responded to MIDI messages outside of the dedicated octave.

The Sample Recorder did not work in some newly created projects.

The Popup message reporting failure to create a project did not fit properly on screen.

Pasting tracks with certain LFO configurations could cause the device to become unresponsive.

Trigs placed on the supertrack did not trigger FX or Track LFOs.

Removing a trig with parameter locks on a Subtracks machine’s supertrack did not actually remove the parameter locks.

It was not possible to clear a pre-existing PROB (probability) parameter lock.

Live-recorded parameter locks could not be cleared for the Subtracks machine.

Rapid, repeated TRIG copy/clear/paste operations could cause trigs to disappear.

Some parameters did not respond when turning the encoder very slowly.

It was not possible to scroll the FX LFO and MIDI control destination lists.

Pattern copy/undo/memorize operations were sometimes not retained after loading a new instrument to the Subtracks machine.

Repeatedly loading presets and playing on a single track could cause the track to stop producing sound.

The Sample Recorder could become unresponsive if the device was synced to an external MIDI clock running at a lower tempo than the one set on Tonverk.

Replacing a loaded sample immediately after startup could sometimes fail to highlight the currently loaded sample.

Under certain circumstances, it was possible to have both the MIDI machine and another SRC machine loaded on the same track at the same time.

Opening the File browser to some locations could cause the device to be unresponsive.

Loading a multi-sampled instrument could under some circumstances cause the device to become unresponsive.

The loop counter for trig conditions was not reset on Stop/Start from external transport.

The metronome could fail to sync to external transport if internal transport was already running.

The MIDI CC mapping for the Filter Folder FX machine was wrong when it was placed in FX slot 2.

It was possible to interrupt a software update by pressing the power button.

The TEMPO LED did not always flash as intended in certain situations.

Arp did not reset its playback in certain situations.

The arpeggiator sequence was not saved as part of a preset.

On first playback, the arpeggiator played the first step in the arpeggiator pattern even if it was muted.

Some MIDI mappings were inconsistent.

Various MIDI machine parameters were not saved as expected in projects and presets.

Pattern change settings that exceeded the pattern reset settings could prevent scheduled pattern changes.

Some large projects would not load as expected.