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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Loopy save issue.
Spoke to Michael and said devs will check for issue.
This happened again though so thought id enquire with the community.
I think I have an idea. Although a guess and unsure how programming works.
Its perhaps to do with loopy feedback and to Drambo ( perhaps Drambo feedback module in a project )
The feedback is feeding back some glitch.
So it cant state save.
It then goes over to aum.
Id have to delete loopy and make another loopy controller ( with feedback turned off )
Its not usual or not heard anyone else complain.
Comments
Although all knobs are saved here in off position and only load again in the off position.
Its not an off position thing.
Before it were with knobs on etc and could save updates.
A file seems corrupted on both cases.
Like a file dont exist or because the project were renamed the same as another project.
but it would be common.
So think its to do with feedback causing a glitch ( just not sure how programming works )
best to just send off for repair.
@sigma79 : it looks like you have the same project open in different hosts at the same time. That may be causing problems.
As I explained to you in another thread, knobs that only send midi , do not have a state that can be saved. I sent you a link to a wiki article showing how to use an intermediate stepped dial to save state.
This isnt about that question.
When I save the project. If I turn a knob. It dosent update the save position of the knob.
I opened in aum to show the project dosent also update when saved.
When I went to aum tho. The save file had actually disappeared also and says Null.
Drambo also said null.
So grabbed a Drambo state save to regain the loopy project.
The state saving of knobs still dosent update with saves.
Deleted app.
Remaking but with feedback off. Save points off. Not much overlap in widget position etc but will send the vid to the dev. They may need project sent.
Watch vid.
I press save. It dosent save position of knob.
I think before it seemed best to uninstall loopy. Rather than remake the project. I think ( not sure ) It would re-introduce in a remake.
This template takes a while to map also.
Like if twitchy from some type of scummy drug lol.
Rotary knob position can be saved.
Even saved to send feedback to the midi out knobs. So you dont have to move all knobs when opening project.
This just dosent save a knob position.
It gets stuck in a saved position.
If you turn a knob that is not tied to a parameter or other persistent value, the position isn’t persistent. Knob values are not saved. When you see a knob whose value stays the same when you re-open that is the knob reflecting the value of what I controls.
I see what you mean.
If you give a widget a command. It saves at 0.
If you have a widget with no command. It will save the position it were moved to.
The problem with the file becoming corrupted is probably related to some combination of the filename '-', you can see that at some point loopy says the name is (null) and your having the same project open in two different hosts at the same time.
Whether a knob's value is the same when you reopen the file as when you close it depends on what the knob does.
I suggest you create a little test project to understand. Create a two knobs. One that that adjusts the master volume and one that sends midi. You will see that the knob that adjusts the master volume has a persistent value and the 'send midi' knob doesn't. That is because (as I explained earlier) "send midi message" doesn't have any state info associated with it. So if you turn a knob that sends MIDI and reopen the project, the knob is at 0. It has no idea what the last MIDI command was.
If you want the knob to reopen in the same position, you need to tie it to something (like a stepped dial) that has a persistent sate. See
https://wiki.loopypro.com/Tech_Note:_Persistent_Send_MIDI_Widgets
Thats weird because iv been able to map loopy knobs with a midi learn rather than the edit mode. I thought it werevthe way to send midi commands out from loopy.
Sometimes that dosent work ( the midi learn way ) Like now.
This is when iv seen and thought ok. Loopy gets feedback from what it controls, so I dont have to tweak knobs at start of project.
Everything is explained in the wiki article as well as how to use a stepped dials to remember the value.
I promise you. If you set up a knob whose action is to send midi that knob will reopen at 0 unless you do something like article suggest —unless loopy is receiving midi that sets the knob.
Thanks espiegel