Bugs are added to this list when the last release has a known bug. When the bug is fixed, the table is updated. See the releases notes for all the bugs that were fixed.
| Decription | Category | Work around | Apply to Release |
|---|---|---|---|
| Humanizing MIDI notes in a track is not working properly: some notes may not play during loop playback. | Major bug | Update to last release to use humanization function | Prior to 2.19.0 |
| Midi mappings get erased after restarting LoopToGo | Major bug | Install 2.14.3 or higher | 2.14.1 and 2.14.2 |
| MIDI pitch is incorrect when using a MIDI device as output for a transposed chain with a MIDI effect plugin (transposed value applied twice). | Major bug | Use release 2.13.4 and higher or don’t combined Transposition and MIDI effects in a chain that outputs MIDI events to another chain or to an external MIDI devices | Before release 2.12.4 |
| When choosing a midi device as output, the same midi device will be added to the list of input device when a chain will be reloaded. This will cause a problem if a midi input device with the same name exists | Major bug | Use Release 2.12.3 and higher or make sure that there is no corresponding Input and output midi devices by using mapped names | Before Release 2.12.3 |
| When paused, the monitoring mode should consider whether the song tick is over a Record Loop, which is currently not the case. | Wrong behavior | If necessary for a performance setting, changing the monitoring mode to ‘Always’ for certain tracks may resolve the issue. If this is not feasible, a script can be utilized to temporarily modify the monitoring mode. | All release (A fix for this issue will be provided in an upcoming release.) |
| Double clicking on a section in the Song Structure view while song is playing will create a jump to the wrong section | Major bug | Use release 2.9.1 and after | 2.8.3 to 2.9.0 (fixed in 2.9.1) |
| Recording and playing monitor mode could be set to wrong mode after closing « Select io » dialog (bug introduced in 2.7.0) | Major bug | Use Release 2.7.8 and after | 2.7.0 to 2.7.7 (fixed in 2.7.8) |
| Impossible to remove or edit an empty script line in the Manage script dialog (bottom list). | Major Bug | Manually remove the problematic line in MyConf.xml. Will be fixed in Release 2.7.1 | 2.7.0 and before |
| Pan Slider: reset to middle reset the cursor but not the actual panning setting | Bug | After resetting the pan slider to middle, move slightly the slider and bring it back to the center. Alternatively, always reset the pan slider manually. | Before 2.4.1 |
| Some plugin preset are not reloaded properly | Major bug | Use release 2.4.0 and higher | Before 2.4.0 |
| The function concept in Release 2.3.0 has been reported to have some bugs | Major bug for function concept in the scripting language | Don’t use the function concept. A new release will fix this problem soon | 2.3.0 |
| Free tempo mode not working properly for audio loops | Major bug | Use release 2.0.6 or 2.1.8 and higher | 2.1.1 to 2.1.7 |
| VST3 Plugins not working in LoopToGo: – NeuralAmpModelerPlugin prior to release 0.7.3 (sound is erratic) – Please inform us of any VST3 plugins not working properly | Compatibility bug | NeuralAmpModelerPlugin 0.7.3 now works in LoopToGo. Make sure you have the lastest release of NAMP! | Before 2.7.2 |
| A few VST3 plugins do not work properly in LoopToGo due to communication problem between the UI and the DSP. The result is some part of the UI not working properly Known plugins not working properly: – SonicProjects plugins | Compatibility bug | This bug has been fixed in 1.15.6 | Before 1.15.6 |
| Use of paths with shortcuts (.lnk) in it might cause LoopToGo to freeze | Major bug | This issue has been fixed in 2.0.0. | Before 2.0.0 |
| Use of plugin midi mapping along with recycle bin lead to multiple mapping assignation and huge file. When files get too big, LoopToGo takes more and more time to load song and a crash can even occur. | Major bug | Upgrade to 1.14.5 and higher or disable use of recycle bin (available for release 1.14.) or don’t use midi mapping for plugins. | Between 1.13.0 and 1.14.4 |
| Jumping to different sections while in jam mode is not really usable. Release 1.15.0 fixes this issue. | LoopToGo Behavior | Don’t use Section jumping as a way to live perform or at least make sure it works well with the structure of your song. | Before 1.15.0 |
| Playing a midi note at the end of a loop just before jumping to another loop can lead to unwanted results. (Before means in the « Pre Record midi time »). Release 1.15.0 fixes this issue. | Bug | There is no real workaround but to avoid to play a note in before a jump to a new loop. Note that the « Pre record Midi time » can be set in the Song/metronome configuration dialog. | Before 1.15.0 |
| Use of recycle bin – a feature to accelerate loading of song on a live show – can lead to weird behavior for some plugins and in some cases, LoopToGo can crash. This is due to a bad implementation of default parameter values or setState() method for some plugins. The crash will occur when deleting a plugin (a chain, a song) or when duplicating a track. Please, let us know if you are aware of a plugin with this problem. We will contact the vendor. | Bug | 1 – Make sure you have the latest plugin release. In many cases, this will fix the issue or 2 – Upgrade to LoopToGo 1.15.0 or higher and disable the use of the recycle bin (in Preferences/Plugins). | 1.13.0 and higher In release 1.14.3, use of Recycle bin is disabled by default. reenabling it can cause the bug with some plugins. From 1.15.0, the recycle bin (when enabled) is only used when loading songs or chains (not for new songs or chains or when dragging plugin from the plugin view). This solve most of the problematic cases. Please let us know if a plugin is not compatible with the use of recycle bin. |
| LoopToGo does not work properly on some computers (only showing a black window). Release 1.9.4 and higher fixes this problem. | Bug for some computers | Upgrade LoopToGo to 2.18.0 or higher | 1.8.0 to 1.9.3 and 2.17.0 to 2.17.4 Fixed from 2.18.0 (was also fixed between 1.9.4 to 2.16.4) |