FAQ

This problem has been reported to occurs on some computers from Release 1.8.0 to 1.9.3. Solution: upgrade to the latest Release

You should test the Free version before buying the Pro version to check if LoopToGo runs smoothly on your setup. Here is our minimal recommandation :

• Windows 10 or higher (64 bit only)
• Intel I3, 3 Ghz or better
• 8 Gb of RAM or higher
• An audio interface with ASIO driver (LoopToGo needs to connect to an ASIO driver to run properly)
• An SSD drive is recommanded for fast loading of plugins and songs

VST3. Steinberg does not provide new license for VST2 plugins. Don't worry most of the plugins now have a VST3 version. In fact, if a plugin is still supported, chances are that there is a VST3 version. If you have old VST2 plugins that you really like, it is still possible to use them in LoopToGO through a plugin wrapper such as Metaplugin from DDMF, Elements FX from Kushview, DISTRHO Ildaeil, AudioGridder, etc. As for CLAP plugins, LoopToGo does not support this new format (not for now). To use CLAP plugin in LoopToGo, you have to use a CLAP plugin wrapper such as DISTRHO Ildaeil.

Steinberg no longer issues new licenses for VST2 plugins. However, most plugins now offer a VST3 version. If a plugin is still actively supported, it is likely that a VST3 version is available. For users who have a preference for old VST2 plugins, it is still feasible to use them in LoopToGO through a plugin wrapper, such as Metaplugin from DDMF, Elements FX from Kushview, DISTRHO Ildaeil, AudioGridder, etc.

No, only Windows 10 (64 bits) and higher.

We want to concentrate our effort in one platform for now. We have no plan to support it in a near future.

No, it is a lifetime license. However, it will only be valid for the version you purchased (e.g., 2.0) and all the releases within that version (e.g., 2.3, 2.4.3, etc.). When Version 3.0 is released, your license may not be compatible with that new version, depending on the purchase date. Nevertheless, the license will continue to work for the prior versions.

LoopToGo is not a DAW; it's a looper designed for live performances using loops. Standard DAW features not intended for live performance are intentionally excluded, ensuring LoopToGo is straightforward and user-friendly. However, if you're satisfied with your performance, you still have the option to fine-tune your mix and export it as a WAV file. Additional details can be found on the Help page.

LoopToGo does not include native effects or MIDI instruments. To access effects and instruments, you need to install VST3 plugins. There are numerous excellent VST3 plugins available, both free and paid. A recommended starting point is https://www.kvraudio.com/plugins/ (ensure you use the VST3 plugin filter and the Windows filter). For users who have a preference for old VST2 plugins, it is still possible to use them in LoopToGo through a plugin wrapper such as Metaplugin from DDMF, Elements FX from Kushview, AudioGridder, etc.

Yes you can! See the Help page for more details.

There are various ways to achieve this, and here are 3 ways that have been reported to work: - Some Audio Interface supports Loopback Channel, this is the easiest way - Use Jack Audio Connection Kit (Jack2) (free) - Use Inject from Audiomovers (not free but reported to be simpler than Jack Audio) Steps for using Jack Audio: 1 - Install an ASIO plugin for OBS (obs-asio). 2 - Install Jack Audio Connection Kit (Jack2). 3 - Launch the Jack2 driver using QjackCtl (ensure your audio interface ASIO driver is selected before starting the Jack2 driver). 4 - Open LoopToGo and choose JackRouter instead of your audio interface ASIO driver. Note: Using name mapping (Preferences/Audio) to tag your input and output channels is a good practice to avoid the need for song modifications. 5 - Launch OBS Studio. 6 - Use the Graph window in QjackCtl to reroute audio channels as follows (or set up routing according to your requirements). Note: it might be necessary to disable the midi routing in Jack2. To do so, keep only the -S argument in Settings/Advanced/Server Prefix Please note that these steps may need adjustment based on your specific setup and requirements.

Sure! We already have a list of new features that we plan to add to LoopToGo but we really want to hear from your. What is the next feature that you want us to add? Keep in mind that LoopToGo is intended for live performance. To send us Feature request or any comment: info.looptogo@gmail.com.

While we strive to ensure LoopToGo is crash-proof, unforeseen issues may arise. If you discover a way to cause LoopToGo to terminate abruptly, kindly reach out to us at info.looptogo@gmail.com with the details. In the meantime, LoopToGo automatically creates periodic backups of your work when the song is not playing or recording. In the event of a crash, LoopToGo will prompt you to open this backup copy. The copy will be loaded as a new project, allowing you to decide whether to overwrite the last manually saved project.

LoopToGo is in active development phase and we are using an approach inspired by CICD practices (see https://en.wikipedia.org/wiki/CI/CD for more details). We want to quickly fix the bugs that we find or that are reported to us. Also, we want the user to quickly have access to the cool new features that we add frequently to LoopToGo. You should always use the latest version available. We keep the oldest releases on our web site for 2 reasons : 1) If ever there is a new bug introduced in a new version, the user can easily go back to a old release that does not have this bug. 2) If a user find a bug or a strange behavior in it's project, he or she can easily compare with older version. This information will help us to pinpoint the problem quickly. The advantages of this approach are numerous but the drawback is that an unstable version can be released even if we tested it intensively. Before using LoopToGo on a live performance with an audience, always make sure that you are confident with the stability of the version you're using. LoopToGo Studio can not assume responsibility for any issues related to the use of its software.

Since release 1.7.3, LoopToGo does not take into account the Windows Font scale factor. Create and set a Windows environment variable called QT_SCALE_FACTOR. Set it to a value higher than 1.0

Surge XT is working in release 1.13.4 and lower. Indeed, Surge XT was one of the only VST3 plugins not working with LoopToGo (it's the only one known to us). We found and fix the problem in Release 1.13.5. Meanwhile, you can still use Surge 1.9 which is still available for download on the surge-synth-team website. Note: please contact us if you know of other VST3 plugins not working with LoopToGo!

This is probably due to the fact that the Download page is "cached" either on your computer or on the web server. To make sure you see the latest page, do the following: A) In LoopToGo, select ? (question mark)/Check for new version B) When a dialog box appears, press the "Open download page..." button

Mappings used in a chain, song, metronome, or persistent chain cannot be deleted directly. To remove them, assign them to other mappings before deleting the old mapped I/O. If you load a song (or chain) and the mapping doesn't exist, a mapped name (not linked to a real I/O) will be created. You must remap them to real I/O for proper functionality.

Yes, from Release 3.4.0, there is 2 ways to do this. 1) Files/Export/Export Song... 2) View/Show Live Audio Recorder... The first one is a tool to export a song after it has been performed. The second one is a more standard recorder where you must press "Record" before the performance and "Stop" to end the recording. Make sure you set the recording time accordingly before starting to record. Most of the time, the first solution will be fine. The second solution is recommended when you have parts in your song where you jam over repeated sections.

All LoopToGo configurations (Plugin list, Preferences, etc.) are stored as a collection of XML files in the LoopToGo working folder. Starting with release 2.15.2, upon application startup, all XML configuration files are automatically backed up into directories named Copies/A, Copies/B, and so forth, up to a maximum of 10 folders. Once this limit is reached, new backups overwrite the files in the first directory, continuing in a cyclic manner. To recover a previously saved configuration, simply copy one or more files from these subfolders back to the working folder. Since the files are overwritten after a few cycles, it's crucial to address any issues promptly without excessively restarting the application. If you require assistance, please refrain from loading LoopToGo to avoid overwriting and potentially losing a good configuration. Instead, contact us by email for help.