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, 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 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, 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 good for the version you bought (ex. 1.0) and all the releases for that version (ex. 1.3, 1.4.3, etc). When Version 2.0.0 will be published, your license might not still work with that new version depending of the purchase date but the prior versions will still work.

LoopToGo is not a DAW, it's a looper!!!! LoopToGo is designed for live performance using loops. Standard DAW features not intended for live performance are not implemented, making LoopToGo a very easy to use software. Yet, if you are proud of your performance, you can still work on your mix and export it into a wav file. More details on the Help page.

LoopToGo does not come with native effects or midi instruments. You have to install VST3 plugins in order to have acces to effects and instruments. There is plenty of excellent VST3 plugins (free or paid). A good place to start is https://www.kvraudio.com/plugins/ (make sure you check VST3 plugin filter). 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, etc.

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

There might be many ways to do that. Here is one that has been reported to work.

1) Install an ASIO plugin for OBS (obs-asio).
2) Install Jack Audio connection kit (Jack2).
3) Start the Jack2 driver with QjackCtl (your audio interface ASIO driver must be selected prior to starting the Jack2 driver).
4) Start LoopToGo and select JackRouter (instead of your audio interface ASIO driver). Note : Using name mapping (Preferneces/Audio) to tag your inputs and outputs channels is a could practice to avoid having to modify your song.
5) Start OBS Studio
6) Use the Graph window in QjackCtl to reroute audio channels as follow (or use any routing that corresponds to your need) :

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: [email protected]

We try very hard to make LoopToGo crash proof but bad things happen sometimes. If you found a way to make LoopToGo terminate abruptly please email us with the details at [email protected] In the meantime, when LoopToGo crashes, it tries to save the project in {User's document folder}/LoopToGo/crashFile.xml. Note that depending on the type of errors, LoopToGo might not have been able to save the project. After loading a crash file, remember to save the project under a new name.

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. If the font are too small

• The best solution is too lower your screen resolution. It is suggested to use half of the recommended resolution (if possible) for a crisper result of all fonts (including other applications).

If the fonts are blurred

• Use a font scale factor of 100% (display seetings) if possible

or

• Edit the qt.conf (set dpiawareness to 1 instead of 0). It is not recommended if the fonct scale factor is greater than 130%. This file is located in the folder where you installed LoopToGo. Note that this setup will be reset at the next installation. If this become too annoying, please contact us!

Surge XT is working in release 1.13.5 and higher. 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 that are used in chain, song, metronome or persistent chain can not be deleted. You have to assign them to other mappings in order to delete the old mapped IO. Also, if you load a song (or chain) and the mapping does not exist, it will create a mapped name (not mapped to a real IO). You will have to remap them to real IO in order to work.