Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Vocal Tune Studio AUv3/standalone released

1235

Comments

  • @dwrae said:

    @attakk said:
    Hope that clarifies?

    Cheers 👍😊

    Absolutely, thanks. I just hope that the AU witin a AU thing is not causing the issue somehow. In any case, please don't select a folder within another app. For testing, you could just select the VocalTuneStudio folder that is auto-created (which is the folder where the standalone version writes to).

    Ok - I’ll give that a go (using the default folder). Unfortunately, erm, life means I can’t come back to you straight away.

    Cheers 😊

  • @dwrae said:

    @attakk said:
    Hope that clarifies?

    Cheers 👍😊

    Absolutely, thanks. I just hope that the AU witin a AU thing is not causing the issue somehow. In any case, please don't select a folder within another app. For testing, you could just select the VocalTuneStudio folder that is auto-created (which is the folder where the standalone version writes to).

    Oh - it’s not actually an au within an au - VTS is loaded as a normal insert fx on a NS2 track - it’s just the audio on that track is provided by a sampler auv3 and not a dedicated audio track (… trying not to open that old NS2 debate 😂)

    Cheers 😊

  • Vocal Tune Studio 1.3.4 released:

    • Loop playback didn't work in Loopy Pro. Solved.
    • When the storage folder was removed, the app will now ask to select a new storage folder

    @espiegel123
    Please let me know if this solves the issue for you as well

  • @dwrae what a champ

  • @dwrae said:
    Vocal Tune Studio 1.3.4 released:

    • Loop playback didn't work in Loopy Pro. Solved.
    • When the storage folder was removed, the app will now ask to select a new storage folder

    @espiegel123
    Please let me know if this solves the issue for you as well

    Working great! Thanks for the update.

  • @dwrae said:

    @attakk said:
    Hope that clarifies?

    Cheers 👍😊

    Absolutely, thanks. I just hope that the AU witin a AU thing is not causing the issue somehow. In any case, please don't select a folder within another app. For testing, you could just select the VocalTuneStudio folder that is auto-created (which is the folder where the standalone version writes to).

    Hi - just to let you know that choosing the auto-created folder worked 👍

    Thank you for all your help 🙏

    Cheers.

  • @attakk said:
    Hi - just to let you know that choosing the auto-created folder worked 👍

    Thank you for all your help 🙏

    Ok, good to hear that! Please note though that when you uninstall the app, the recordings and pitch files will be deleted as well and therefore, VTS instances present in a project/DAW will fail to load. That's the downside of using that folder.

  • @dwrae said:

    @attakk said:
    Hi - just to let you know that choosing the auto-created folder worked 👍

    Thank you for all your help 🙏

    Ok, good to hear that! Please note though that when you uninstall the app, the recordings and pitch files will be deleted as well and therefore, VTS instances present in a project/DAW will fail to load. That's the downside of using that folder.

    Shouldn’t offloading leave the app folder in place with all the files intact?
    https://9to5mac.com/2020/01/21/how-to-offload-apps-in-ios-to-save-space-without-deleting-their-data/

  • @dwrae said:

    @attakk said:
    Hi - just to let you know that choosing the auto-created folder worked 👍

    Thank you for all your help 🙏

    Ok, good to hear that! Please note though that when you uninstall the app, the recordings and pitch files will be deleted as well and therefore, VTS instances present in a project/DAW will fail to load. That's the downside of using that folder.

    Thanks for the info - for my workflow it’s not a problem as once corrected I will bounce out to audio and then unload VTS anyway. That’s my standard practice with everything 👍

    Cheers.

  • @bargale said:

    Ok, good to hear that! Please note though that when you uninstall the app, the recordings and pitch files will be deleted as well and therefore, VTS instances present in a project/DAW will fail to load. That's the downside of using that folder.

    Shouldn’t offloading leave the app folder in place with all the files intact?
    https://9to5mac.com/2020/01/21/how-to-offload-apps-in-ios-to-save-space-without-deleting-their-data/

    It should, yes. I guess offloading means that it copies to iCloud rather than keeping the files on your device which wouldn't help in freeing up space.

  • @dwrae said:

    @bargale said:

    Ok, good to hear that! Please note though that when you uninstall the app, the recordings and pitch files will be deleted as well and therefore, VTS instances present in a project/DAW will fail to load. That's the downside of using that folder.

    Shouldn’t offloading leave the app folder in place with all the files intact?
    https://9to5mac.com/2020/01/21/how-to-offload-apps-in-ios-to-save-space-without-deleting-their-data/

    It should, yes. I guess offloading means that it copies to iCloud rather than keeping the files on your device which wouldn't help in freeing up space.

    I believe offloading deletes the app but leaves all the data and preferences. It’s useful for apps that use a lot of space or if one has lots of infrequently used apps.

  • @Artem said:
    @dwrae The second time there was such a problem in Cubasis: after closing the project and opening it after a while, the vocal track "shifted" on the timeline and started playing earlier than necessary, in addition, the vocal pitch changed. That is, the plug-in is still unstable.
    The only way to avoid this is to freeze the track immediately after correction, but this is a bad option, since it often happens that you need to adjust the settings later. In general, I decided to stop using the plug-in until it starts working more stably. :(

    @dwrae I looked at the files that VTS saves to a folder and it looks like at some point their sample rate changes from 48 to 44.1. This explains what I wrote above. It is also unclear why the bitrate is reduced by about 2 times.
    The project settings, of course, are always the same.

  • @Artem said:

    @Artem said:
    @dwrae The second time there was such a problem in Cubasis: after closing the project and opening it after a while, the vocal track "shifted" on the timeline and started playing earlier than necessary, in addition, the vocal pitch changed. That is, the plug-in is still unstable.
    The only way to avoid this is to freeze the track immediately after correction, but this is a bad option, since it often happens that you need to adjust the settings later. In general, I decided to stop using the plug-in until it starts working more stably. :(

    @dwrae I looked at the files that VTS saves to a folder and it looks like at some point their sample rate changes from 48 to 44.1. This explains what I wrote above. It is also unclear why the bitrate is reduced by about 2 times.
    The project settings, of course, are always the same.

    FLAC is lossless, so the bitrate doesn't matter. It will convert the sample rate as necessary. If you are in standalone mode and the app detects that your device cannot natively play the sample rate of the file, it will automatically convert it. If you are in AUv3 mode, it will convert to the host's sample rate. It will also detect if the left and right channels are equal and turn it into mono. Both to reduce problems and CPU usage.

  • @dwrae said:

    @Artem said:

    @Artem said:
    @dwrae The second time there was such a problem in Cubasis: after closing the project and opening it after a while, the vocal track "shifted" on the timeline and started playing earlier than necessary, in addition, the vocal pitch changed. That is, the plug-in is still unstable.
    The only way to avoid this is to freeze the track immediately after correction, but this is a bad option, since it often happens that you need to adjust the settings later. In general, I decided to stop using the plug-in until it starts working more stably. :(

    @dwrae I looked at the files that VTS saves to a folder and it looks like at some point their sample rate changes from 48 to 44.1. This explains what I wrote above. It is also unclear why the bitrate is reduced by about 2 times.
    The project settings, of course, are always the same.

    FLAC is lossless, so the bitrate doesn't matter. It will convert the sample rate as necessary. If you are in standalone mode and the app detects that your device cannot natively play the sample rate of the file, it will automatically convert it. If you are in AUv3 mode, it will convert to the host's sample rate. It will also detect if the left and right channels are equal and turn it into mono. Both to reduce problems and CPU usage.

    @dwrae Let's go in order, please:
    1. In the project settings in Cubasis 3, the sample rate is set to 48.
    2. I'm recording a track in VTS auv3 and correcting it.
    3. I'm closing the project.
    4. After a while I open the project: in some cases there are no problems, but in the end, after the next opening of the project, a problem appears: the vocal track plays faster and its pitch is higher.
    5. This led me to think that VTS had changed the sample rate of the recorded track for some reason.
    6. I checked the file in the VTS folder and indeed the sample rate changed to 44.1, although the project settings are always the same.
    7. After that, I made a final check: I changed the sample rate to 44.1 in the project settings, the vocal track is played back as needed, without any problems.

    Is this information enough to understand the cause of the bug and fix it?

  • @Artem said:
    @dwrae Let's go in order, please:
    1. In the project settings in Cubasis 3, the sample rate is set to 48.
    2. I'm recording a track in VTS auv3 and correcting it.
    3. I'm closing the project.
    4. After a while I open the project: in some cases there are no problems, but in the end, after the next opening of the project, a problem appears: the vocal track plays faster and its pitch is higher.
    5. This led me to think that VTS had changed the sample rate of the recorded track for some reason.
    6. I checked the file in the VTS folder and indeed the sample rate changed to 44.1, although the project settings are always the same.
    7. After that, I made a final check: I changed the sample rate to 44.1 in the project settings, the vocal track is played back as needed, without any problems.

    Is this information enough to understand the cause of the bug and fix it?

    Unfortunately, not yet. I just tested it a few times and with the project set to 48kHz and no matter if I import a 44.1kHz track into Cubasis and let it resample at import or not, the recording in VTS is at 48kHz. I also checked this in AudioShare (and some additional logging). Please note that the sample rate used for recording and preparing playback is written to the log file. So please remove the file VTSLog.txt from the Vocal Tune Studio folder and then the next time it happens, please send me this file.

    When reloading the project later on, do you perhaps remember if you changed the 'listening device', meaning if the project was for example created when using the device's speaker, but when it failed you were using USB, BT or headphones directly connected (if that exists on your device)?

    I also checked the only when doing a file import (not recommended!) the app will possibly do sample rate conversion, so this means that if you have a VTS recording in 44.1kHz, the host at that time was passing 44.1kHz in the audio callback. So something in the host is changed if it decided to play at a different rate.

  • @dwrae said:

    @Artem said:
    @dwrae Let's go in order, please:
    1. In the project settings in Cubasis 3, the sample rate is set to 48.
    2. I'm recording a track in VTS auv3 and correcting it.
    3. I'm closing the project.
    4. After a while I open the project: in some cases there are no problems, but in the end, after the next opening of the project, a problem appears: the vocal track plays faster and its pitch is higher.
    5. This led me to think that VTS had changed the sample rate of the recorded track for some reason.
    6. I checked the file in the VTS folder and indeed the sample rate changed to 44.1, although the project settings are always the same.
    7. After that, I made a final check: I changed the sample rate to 44.1 in the project settings, the vocal track is played back as needed, without any problems.

    Is this information enough to understand the cause of the bug and fix it?

    Unfortunately, not yet. I just tested it a few times and with the project set to 48kHz and no matter if I import a 44.1kHz track into Cubasis and let it resample at import or not, the recording in VTS is at 48kHz. I also checked this in AudioShare (and some additional logging). Please note that the sample rate used for recording and preparing playback is written to the log file. So please remove the file VTSLog.txt from the Vocal Tune Studio folder and then the next time it happens, please send me this file.

    When reloading the project later on, do you perhaps remember if you changed the 'listening device', meaning if the project was for example created when using the device's speaker, but when it failed you were using USB, BT or headphones directly connected (if that exists on your device)?

    I also checked the only when doing a file import (not recommended!) the app will possibly do sample rate conversion, so this means that if you have a VTS recording in 44.1kHz, the host at that time was passing 44.1kHz in the audio callback. So something in the host is changed if it decided to play at a different rate.

    Regarding the log file: I checked, information is recorded in it, only when using the standalone version of the application, not auv3.

    Regarding the listening device: yes, it is changing. I usually work on projects with an audio interface connected (steinberg ur12), but I can also open a project without an audio interface connected.

    I've been thinking about that. If this always led to a problem, then it would be possible to conclude for sure that this is the reason. But since the problem doesn't always occur, I'm not sure.

  • @Artem said:
    Regarding the listening device: yes, it is changing. I usually work on projects with an audio interface connected (steinberg ur12), but I can also open a project without an audio interface connected.

    I've been thinking about that. If this always led to a problem, then it would be possible to conclude for sure that this is the reason. But since the problem doesn't always occur, I'm not sure.

    I can't think of anything else, so it must be related to that. There is no easy fix for that unfortunately. The host could simply use the iOS automatic resampler on output when the project's sample rate isn't available, it shouldn't change its internal sample rate because of this. Anyway, I'll try to reproduce it with connecting/disconnecting some devices.

  • @dwrae said:

    @Artem said:
    Regarding the listening device: yes, it is changing. I usually work on projects with an audio interface connected (steinberg ur12), but I can also open a project without an audio interface connected.

    I've been thinking about that. If this always led to a problem, then it would be possible to conclude for sure that this is the reason. But since the problem doesn't always occur, I'm not sure.

    I can't think of anything else, so it must be related to that. There is no easy fix for that unfortunately. The host could simply use the iOS automatic resampler on output when the project's sample rate isn't available, it shouldn't change its internal sample rate because of this. Anyway, I'll try to reproduce it with connecting/disconnecting some devices.

    Maybe you can first add an option to the settings that prohibits conversion? 🤔 For me, that would basically solve the problem.

  • @Artem said:

    @dwrae said:

    @Artem said:
    Regarding the listening device: yes, it is changing. I usually work on projects with an audio interface connected (steinberg ur12), but I can also open a project without an audio interface connected.

    I've been thinking about that. If this always led to a problem, then it would be possible to conclude for sure that this is the reason. But since the problem doesn't always occur, I'm not sure.

    I can't think of anything else, so it must be related to that. There is no easy fix for that unfortunately. The host could simply use the iOS automatic resampler on output when the project's sample rate isn't available, it shouldn't change its internal sample rate because of this. Anyway, I'll try to reproduce it with connecting/disconnecting some devices.

    Maybe you can first add an option to the settings that prohibits conversion? 🤔 For me, that would basically solve the problem.

    Well, at most that would mean that when the host restores the state of VTS and finds out that the sample rate used is not equal to the host's sample rate, it would refuse to restore the state, which would leave you with an empty screen.

  • @dwrae : is it possible that VTS is looking at hardware sample rate instead of the host’s?

  • edited April 2023

    @espiegel123 said:
    @dwrae : is it possible that VTS is looking at hardware sample rate instead of the host’s?

    No, not in AUv3 mode. The sample rate is set when the host calls the AU's 'prepare playback' method and passes a sample rate.

  • The user manual has been updated to include the importing and exporting of audio in AUv3 mode.

    https://www.audio-evolution.com/manual/vtsau/

  • Vocal Tune Studio 1.3.6 released:

    • 'Save to audio file' now saves as WAV file instead of FLAC since some apps like GarageBand cannot handle FLAC files
    • Solved a possible crash when no notes were found in the audio
  • @dwrae said:
    Vocal Tune Studio 1.3.6 released:

    • 'Save to audio file' now saves as WAV file instead of FLAC since some apps like GarageBand cannot handle FLAC files
    • Solved a possible crash when no notes were found in the audio

    👍🙏

  • I just bought VTS (in AE), for 9.99€. Not sure if this a sale, change of price, or it’s been that way for a while and I missed the memo.

  • @Fitz said:
    I just bought VTS (in AE), for 9.99€. Not sure if this a sale, change of price, or it’s been that way for a while and I missed the memo.

    It's a sale price until the end of the month since the AUv3 price is now also $9.99 until that time.

  • I use VTS as AUv3 within Cubasis.

    How can I switch between the two modes ‚Pitch and time correction‘ and ‚Time correction only‘ or return to the main menu of VTS?

    If I start in the 'wrong' mode (i.e. ‚Time correction only‘), I can't get back easily.
    So far I help myself by quitting VTS and loading another AUv3 plugin in the same Cubasis slot instead. Then I start VTS again.

  • @Iskander said:
    I use VTS as AUv3 within Cubasis.

    How can I switch between the two modes ‚Pitch and time correction‘ and ‚Time correction only‘ or return to the main menu of VTS?

    If I start in the 'wrong' mode (i.e. ‚Time correction only‘), I can't get back easily.
    So far I help myself by quitting VTS and loading another AUv3 plugin in the same Cubasis slot instead. Then I start VTS again.

    There is currently no option to switch between the two modes.

  • Vocal Tune Studio v1.3.8 released:

    • Solved an issue when used in Logic Pro for iPad

    Please note that the super low price of $9.99 is only available a few more days until the end of May!

Sign In or Register to comment.