Heads Up: NEW Igor Vasiliev app launched!

skiphunt

@looped said:
Why are you talking intuition? How is labeling something with incorrect labels more inuitive? Just label them correctly! How is it more accessible to have improper labels? You make no sense either, Skiphunt.

Buh-bye

[Deleted User]

deleted

[Deleted User]

deleted

audiomike

@looped said:

@skiphunt said:

@looped said:
Why are you talking intuition? How is labeling something with incorrect labels more inuitive? Just label them correctly! How is it more accessible to have improper labels? You make no sense either, Skiphunt.

Buh-bye

Quit acting like a child. Why are you shilling so hard and can't handle criticism? Do you have a financial interest in this app?

Nailed it.

skiphunt

@audiomike said:

@looped said:

@skiphunt said:

@looped said:
Why are you talking intuition? How is labeling something with incorrect labels more inuitive? Just label them correctly! How is it more accessible to have improper labels? You make no sense either, Skiphunt.

Buh-bye

Quit acting like a child. Why are you shilling so hard and can't handle criticism? Do you have a financial interest in this app?

Nailed it.

Nope. Just a fan. Want to see the developer profit so that he’ll continue to make great apps.

I offered speculation as to why the naming convention might be less standard, and I got insults as a reply. No time for that. Take care.

If you don’t like his apps and this one doesn’t interest you or anyone else, don’t buy it. It’s obviously not for you.

He showed it to me, I thought it was great. Found a couple bugs. He fixed them. Made someone suggestions for improvement. He said he was too close to launch to start adding new features, but likely in an update. I made him a temp logo to use in case his graphics person didn’t come through on time.

Got a redeem code, but would’ve bought it regardless. I genuinely love the app and am enthusiastic about telling others about it. Nothing in it for me.

That’s it. If you are looking for someone to troll, you’re wasting your time.

Happy Holidays!

[Deleted User]

deleted

skiphunt

@looped said:
Skiphunt, if people find the app inspiring and useful, it will sell and he can "profit." He doesn't need you to shill for his profit. At least you admit you are a shill: someone that has a close connection to the app, by helping create presets, helping with development, and designing the logo. You pretended to be an unbiased observer, but you clearly have an emotional, if not monetary investment, to this app. I'm not trolling, I'm trying to find a use case for this app, Shill on, Skiphunt. You misrepresented what this app could do with the audio input function and it took Gavinski to point out your misrepresentation. I bought the app based on your misrepresentation, and for that I am pissed off--at you. Not the developer. You aren't doing Vasiliev any favors. Bugger off.

None of this is true. I spoke about the app prerelease with the devs blessing. I even said so. I don’t think you even know what a “shill” is obviously.

I didn’t misrepresent anything. I corrected misinformation.

Get a refund if you’re not happy with the app.

@wim could you please do something about this person?

[Deleted User]

deleted

skiphunt

@looped said:
Skiphunt, here is direct quote of your misrepresentation that led me to buy the app:

"However, what I do is load ExoSphere into the effects slot. Solo that one layer and load my source to play into that layer. Once the "loop" gets going, I adjust the parameters, then solo the next layer, and then change my input source for that one, until each has received the input that I want. Once I get a soundscape/soundtrack that I want... I record it."

Unfortunately, I can't get a refund.

So now you are going to run to mommie and try to get the admin to ban me. You really are something.

What you missed is that in a follow up post I said that I load multiple instances of ExoSphere. I said it’s not ideal but it’s workable for now. I too would prefer to run directly into each layer and save those samples. That’s one of the two things I mentioned to Igor. From what I understand, he’s game to make that happen in an update.

I get no gain for this app. Only cheering on one of my favorite developers.

I’m sorry you’re not satisfied with the app. I’m loving the heck out of it.

My guess, based on your questions about the app… you’ll eventually dig the app too once it’s had an update or two, and you’ll be glad you got it now at its sale price.

If I was responsible for your purchase, then I’ll say “you’re welcome”

And Happy Holidays to you too!

[Deleted User]

deleted

skiphunt

@looped said:
Skiphunt, your followup was after Gavinski corrected you. Your original statement had nothing about needing separate instances. You clearly gave out misinformation. By the time you admitted your error, I had already purchased the app. Merry Christmas!

Hey listen, I’m only engaging with you on this as a distraction. I’m trying to keep my mind off the fact that my sister, who I love, had some serious surgery tonight and I’m not getting any information and I’m worried sick that it didn’t go well.

So, I’m sorry you’re not happy with the app. I posted about the app and why I personally am loving it and getting great use out of it.

Give it some time, you may have a change of heart.

For now, I must excuse myself from this banter with you while I try to find out what’s going on with my sister’s surgery. I know this is obviously very important to you, but all I can say is that I’m sorry that you aren’t happy and I sincerely hope you find a way to enjoy the app as much as I do.

So, best of luck to you and I hope it all works out for you in the end.

Cheers

become

@looped said:. I wish the developer the best and hope he can develop this into something like a cross between Spacefields and this.

Exactly what I’m looking for, I love the way I can just start playing phrases into the mic input in SpaceFields and continually evolve the interactions. But from what I’ve heard the sounds this produces are much more my thing.

As skiphunt suggested, writing to him may help nudge the development in that direction.

Nighur

I tried to make something using ExoSphere as a “background effect”. I used 2 instances of Pure Piano driven by the same Piano Motif, one fed into ExoSphere.
Reels on the final mix for all that dirt.

garden

A weird, fascinating app as always from this developer. Instant mysterious love.

I have no problem with the naming of the parameters. Once you twist a knob and see what it does, you get it and move on. And I understand "presence" just fine. It simply means the presence - the sense of being there or not - in the mix.

One thing I don't quite get is Midi parameter control. It seems that mapping a control only... activates it? Or something. For example, mapping an incoming sequencer to the Flow Tone (pitch) just triggers a jump in that value when a specific note arrives. It doesn't "track." As far as I can tell, at least.

Still. Lustmord beckons.

seawind161

@looped said:
Why are you talking intuition? How is labeling something with incorrect labels more inuitive? Just label them correctly! How is it more accessible to have improper labels? You make no sense either, Skiphunt.

I would jump at the chance to use YOUR correctly labeled apps. Can you post a link?

jblock

I walk through an ExoSphere patch I made using short clips I recorded with the modern digital Mellotron:

timfromtheborder

From Igor’s blog:

https://motion-soundscape.blogspot.com/2025/12/upcoming-updates-for-exosphere.html?m=1

Next Update

In the very next release, each sound layer will receive a dedicated mode button. This will allow users to choose between three options:

• Sample playback
• External input recording into a loop
• Playback of the recorded loop

With these controls, it will be possible to capture and loop external signals independently for each layer, opening new ways to blend live input with ExoSphere’s evolving textures.

Planned Features in Future Releases

Looking ahead, several major enhancements are already in development:

Multi-channel input and output support – assign separate input channels to each layer and route individual outputs for more advanced mixing.
Improved sample manager – select and organize samples with group operations for faster workflow.
MIDI keyboard support – change the pitch of layers directly from a connected MIDI controller.
Sample and preset packages – load and use complete collections as a single file for easier sharing and setup.
General improvements and fixes – ongoing refinements based on user feedback.

anickt

Based on the above 👆🏼 a purchase has been made…

rheslip

This sounds really good - everything Gavinski mentioned needed improvement. It’s a great app but with these changes it will be next level. Good developers listen to their customers!

Simon

Today is last day of intro price.

skiphunt

For the record… Igor was planning on these updates before launch. He just wanted to get it out there and get some feedback. Hopefully get some holiday sale action. It’s a very stable, useful, and extremely fun app as-is. For the current sale price, it’s a steal. With the updates coming… some of you will be disappointed you didn’t grab it on sale

skiphunt

Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

Gavinski

@skiphunt said:
Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

The exact times differ per layer, I can't remember exactly, but it is written there in the manual. Some layers will be fully overwritten in something short like 3 seconds, some take more like 10 or 15 seconds.

skiphunt

@Gavinski said:

@skiphunt said:
Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

The exact times differ per layer, I can't remember exactly, but it is written there in the manual. Some layers will be fully overwritten in something short like 3 seconds, some take more like 10 or 15 seconds.

Thx 🙏 I saw those figures in the manual, but they are recommended sample lengths for each layer. Unless I’m missing something. When I get a buffer filled, the overdub onto it… the previous recording… mixed with the overdubbed input… seem to go on much longer than that. It could be that I have the echo cranked high. It’s cool to build live compositions by adding and removing input sources, though a little cumbersome to do it this way. I think I’ll test a basic sound and remove all echos and delays to get a handle on how long the overdubbed buffer holds. FYI: I initially, mistakenly typed oversample but meant overdub

Gavinski

@skiphunt said:

@Gavinski said:

@skiphunt said:
Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

The exact times differ per layer, I can't remember exactly, but it is written there in the manual. Some layers will be fully overwritten in something short like 3 seconds, some take more like 10 or 15 seconds.

Thx 🙏 I saw those figures in the manual, but they are recommended sample lengths for each layer. Unless I’m missing something. When I get a buffer filled, the overdub onto it… the previous recording… mixed with the overdubbed input… seem to go on much longer than that. It could be that I have the echo cranked high. It’s cool to build live compositions by adding and removing input sources, though a little cumbersome to do it this way. I think I’ll test a basic sound and remove all echos and delays to get a handle on how long the overdubbed buffer holds. FYI: I initially, mistakenly typed oversample but meant overdub

I remember there were two different sets of figures in the manual, one was recommended sample lengths for each layer, the other was about how long the buffer was when recording. Definitely there somewhere!

skiphunt

@Gavinski said:

@skiphunt said:

@Gavinski said:

@skiphunt said:
Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

The exact times differ per layer, I can't remember exactly, but it is written there in the manual. Some layers will be fully overwritten in something short like 3 seconds, some take more like 10 or 15 seconds.

Thx 🙏 I saw those figures in the manual, but they are recommended sample lengths for each layer. Unless I’m missing something. When I get a buffer filled, the overdub onto it… the previous recording… mixed with the overdubbed input… seem to go on much longer than that. It could be that I have the echo cranked high. It’s cool to build live compositions by adding and removing input sources, though a little cumbersome to do it this way. I think I’ll test a basic sound and remove all echos and delays to get a handle on how long the overdubbed buffer holds. FYI: I initially, mistakenly typed oversample but meant overdub

I remember there were two different sets of figures in the manual, one was recommended sample lengths for each layer, the other was about how long the buffer was when recording. Definitely there somewhere!

Thx, I could’ve missed it. Will double check. Yeah, I don’t mind the “wall of text” you critique, but it’d sure be easier with a word search included

skiphunt

@Gavinski said:

@skiphunt said:

@Gavinski said:

@skiphunt said:
Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

The exact times differ per layer, I can't remember exactly, but it is written there in the manual. Some layers will be fully overwritten in something short like 3 seconds, some take more like 10 or 15 seconds.

Thx 🙏 I saw those figures in the manual, but they are recommended sample lengths for each layer. Unless I’m missing something. When I get a buffer filled, the overdub onto it… the previous recording… mixed with the overdubbed input… seem to go on much longer than that. It could be that I have the echo cranked high. It’s cool to build live compositions by adding and removing input sources, though a little cumbersome to do it this way. I think I’ll test a basic sound and remove all echos and delays to get a handle on how long the overdubbed buffer holds. FYI: I initially, mistakenly typed oversample but meant overdub

I remember there were two different sets of figures in the manual, one was recommended sample lengths for each layer, the other was about how long the buffer was when recording. Definitely there somewhere!

Yep, thanks 🙏 it’s right there. Not sure how I missed it. Must be my aggressive echo settings that are giving the illusion of a longer overdubbed length

“Loop buffer sizes per layer:

Core, Flow, Grain - 5 seconds
Shard - 15 seconds
Glow - 10 seconds”

skiphunt

@skiphunt said:

@Gavinski said:

@skiphunt said:

@Gavinski said:

@skiphunt said:
Quick question 🙋‍♂️ - until recently, I’ve primarily used ExoSphere in either standalone mode and importing in samples or hosted and playing with layered buffers via external inputs.

Lately I’ve also been playing with using multiple channels in AUM and using just 1 or 2 ExoSphere layers via the effects slot of just one of the AUM channels. My question is, when you’ve got something going in a couple of the ExoSphere buffers, then change the input.

Does anyone know how long it takes to completely replace what’s in the buffer of any given ExoSphere layer with new input and no longer an oversampled mix?

I’ll ask Igor too, but there’s a significant time difference and wondering if anyone else knows.

The exact times differ per layer, I can't remember exactly, but it is written there in the manual. Some layers will be fully overwritten in something short like 3 seconds, some take more like 10 or 15 seconds.

Thx 🙏 I saw those figures in the manual, but they are recommended sample lengths for each layer. Unless I’m missing something. When I get a buffer filled, the overdub onto it… the previous recording… mixed with the overdubbed input… seem to go on much longer than that. It could be that I have the echo cranked high. It’s cool to build live compositions by adding and removing input sources, though a little cumbersome to do it this way. I think I’ll test a basic sound and remove all echos and delays to get a handle on how long the overdubbed buffer holds. FYI: I initially, mistakenly typed oversample but meant overdub

I remember there were two different sets of figures in the manual, one was recommended sample lengths for each layer, the other was about how long the buffer was when recording. Definitely there somewhere!

Yep, thanks 🙏 it’s right there. Not sure how I missed it. Must be my aggressive echo settings that are giving the illusion of a longer overdubbed length

“Loop buffer sizes per layer:

Core, Flow, Grain - 5 seconds
Shard - 15 seconds
Glow - 10 seconds”

Ok, looks like I’m mistaken. It’s not actually overdubbing. It adds new input to the looped buffer, not to exceed the prescribed amount for that ExoSphere layer. Not in a laying fashion like Enso does. At least not the “Shard” layer (15sec buffer).

Only posting the correction because I thought it was overdubbing and posted incorrect info. At least, that’s how it is now with the current build.

anickt

seawind161

@>; @skiphunt said:

Yeah, I don’t mind the “wall of text” you critique, but it’d sure be easier with a word search included

Download the manual from Igor’s site and pop it into Books (or your favorite reader). Instant searchability!