Wishlists

1661 replies [Last post]
tom_tm
Offline
Joined: 06/29/2011

"you'd have thought it'd be the trail-blazing reference implementation!"

No, I disagree. I think if Apple were to make an app that would put an end to all other apps, then there would be both no incentive to write any other apps, and Apple would end up being slammed just like Microsoft were for being anti-competitive.

Slam-Cut
Offline
Joined: 09/07/2011

"I still spend too much time dicking around with apps instead of putting together songs."

Yeah, that. I'm focused on completing an album project and therefore sticking to the handful of apps that are the eaisest in my workflow for the sound I'm after, but I therefore don't push the boundaries and discover new things because of the time and mental effort it takes to get apps working together. I just got AUM and hope that will help a bit, but NS2 with MIDI out would make the whole of iOS music making so much easier for me. I can't wait for the day I read the post in the Annoucements section... Guessing now that'll be fall/winter.

Galaxyexplorer (not verified)

"you'd have thought it'd be the trail-blazing reference implementation!"

"No, I disagree. I think if Apple were to make an app that would put an end to all other apps, then there would be both no incentive to write any other apps, and Apple would end up being slammed just like Microsoft were for being anti-competitive."

Could be true. If Apple one day would release an offer like Mainstage (or even Logic Mobile) with all it´s tools it would make nearly all iOS music apps obsolete in a second.
But if they would care to kill some niche developers? Not sure? They could use it to sell devices."

However, like blip said, the expectations are very high, especially with BM3, FL-Studio Mobile 3 f.e. coming cross platform this year (maybe).
Well, pressure is the best fuel for innovation ;)

Stiksi
Offline
Joined: 11/21/2010

"If Apple one day would release an offer like Mainstage (or even Logic Mobile) with all its tools it would make nearly all iOS music apps obsolete in a second."

FOR a second. It's Apple, guys, remember? It would be a flagship app, so it would only work on the absolutely latest hardware and every update would remove its ability to work with old systems like the soon to be replaced iCloud (actually, I think iCloud could go for a year or two in the current incarnation but after that it's all bets off again). The new systems would be broken at launch. It would be slow as molasses after one update and about as easy to use for making music outside the usecases shown in video ads.

Even if it were free, it would still be cheaper to buy a desktop DAW than to update your iDevice every year to the latest version. If they ever release a "pro" app, it's going to be iPad Pro exclusive.

Slam-Cut
Offline
Joined: 09/07/2011

Funny stuff Stiksi!

Slam-Cut
Offline
Joined: 09/07/2011

This has probably already been mentioned, but in the resetting X/Y pads category, a double tap to reset might be helpful, especially when performing live, but I think it would be helpful when performing dead as well.

Stiksi
Offline
Joined: 11/21/2010

Accidental double taps could be a problem… for me at least.

Slam-Cut
Offline
Joined: 09/07/2011

Yeah, I thought about that, but I think there could be some user adjustment to avoid that. Unless you have a better idea for resetting the X/Y pads? There seems to be room for a small button on the left hand side.

Galaxyexplorer (not verified)

Double tap with 2 fingers f.e.? Or another multi-touch gesture.

syrupcore
Offline
Joined: 09/26/2010

Resetting the XYs would be useful but what would it reset to? The position it was in when saved? The position of the knob it's related to when saved?

Related request: a 'record the current XY position to the sequencer' would be more useful to me. If you drag your finger around and get something sounding good and then want to automate *from* there, it's really difficult to start at the exact spot. Usually not a huge deal to be off a bit but some settings like sample start/length or lfo speed can be really delicate; hitting record and then trying to move the XY just enough to register a change and then reset to the original coordinates is basically impossible for my fat fingers. Alternatively, a text based representation of the current XY positions (X42,Y94) would allow you to go in to the piano roll and manually set the controller positions.

Galaxyexplorer (not verified)

A snap option (like Mitosynth f.e.) would be nice. Wherever you are, after release the XY pad it snaps back to a default point. On top it would be great to have the option to choose the point, speed and slope for snap back.
Or just draw automation lines visually direct in an XY pad with different options to manipulate the points and lines (like in Logic's Sculpture).

syrupcore
Offline
Joined: 09/26/2010

Yeah, Matt's made murmur of wanting to support snap back in the past. Maybe we'll see it at some point. That (along with a 'hold current', probably the default setting) would actually take care of the use case I described having trouble with. Little bit of overhead but if you started recording, moved the dot someplace else and let it snap back, the last value recorded would be, presumably, the current 'hold' value. Delete the rest and get on with it.

While low on my wish list, curve control for snap back really does greatly extend the musicality of them since you can play them rhythmically a lot more easily/interestingly. I'm imagining it would be something like a set of extra envelopes (or single cycle LFOs), the guts of which are hidden from the user—they'd have preset shapes (linear, logarithmic, expo, S...), musical fade times (same as LFO speeds) and be triggered on release instead of Keydown.

Slam-Cut
Offline
Joined: 09/07/2011

Curve control for snap back sounds really cool. Those are the kind of features that might really set NS2 apart from the pack, but I wouldn't mind if that came later as a part of an update or IAP.
But once I tried using presets with that feature, I could see myself getting addicted and thinking it an absolute necessity.

Galaxyexplorer (not verified)

Since it's still much time i have some more wishes:
14 bit midi cc's
....that's it for now! :)

Slam-Cut
Offline
Joined: 09/07/2011

So what is the benefit for the larger bit sized MIDI? More, faster, better?

kitejan
Offline
Joined: 04/05/2011

I would guess more than 127 values for the midi values - so less "zipper" type noise. I recall the original midi (being made back in the gold old days where 8 bit values were seen as excessive) only used 7bits for their values (0-127). The full 8 bits would be 0-255, and 14 bits would be, oh 0-8192.

I think....

Galaxyexplorer (not verified)

14 bit midi has value from 0-16383 (or 8192 in each direction),
It's common for pitchbend but apps like the Moog Model 15 offers it for (nearly) all parameters and it can make a huge different on some parameters.
Midi Designer Pro 2 app can send it f.e. and a few hardware controllers as well.
It's not a common thing (like MPE isn't sadly too) but it's time to move on!
7 bit messages are sometimes a bit too steppy for my taste. Automations in a DAW have much higher resolution but it's too static.
Last days i had trouble with my Seaboard, DAW setup and a few other things and gone for a few days to an iOS only setup. Beside that Audiobus still sucks (or some apps inside a session) often and crash the whole thing i loved it and the live input and changes you can do via multi-touch are awesome.
My iPhone's 3D touch (yay, the phone works again fine) is really fantastic for expressive playing and modulation. As good as my Seaboard and even better in some cases (beside velocity).
I consider again to buy me an iPad Pro (maybe the next new 12.9" one) and let the Galaxyexplorer live up again. Or even try to do another iPhone only projects.
I thought windows 10 might be an option but developers won't make real multi-touch apps for it, so i forgot about it.
My desktop setup offers some awesome synths like the new (not even officially released) Icarus which is my favourite synth now but playing with apps in iOS and putting some better FX in the chain sounds very close these days.
I might be go back to iOS only some day. It has some big trouble and the stabilty is not there but a lot things are also so much more easy on it.
Also i said i will make 1000 patches for NS2.......:) I will do if it comes at least somewhere in 2017!

Stiksi
Offline
Joined: 11/21/2010

Well, 14bit would probably be faster in the sense that there is less need for interpolation, so you get a more immediate response. But if I had to guess, that advantage is pretty negligible. But more accurate settings is a big plus.

I also hope the midi sampling rate is increased in the next NS version. 1/64 is not quick enough and I'm already resorting to doubling the BPM.

Galaxyexplorer (not verified)

For most parameters it would be over the top but for very subtle settings it would be a great add on.
But if Matt would be add all our wishes we will only can run one instance of the included synth on the latest iPad Pro.
Analog modeled filters, audio rate modulations......i mean i'm still mainly interested in the synth.
Maybe it will be the Falcon of iOS :D
I don't expect that i can run 16 instances of the Model 15 like quality but i hope it will be well balanced between cpu/ram usage and quality!
But then i'm not sure if Matt doesn't give up and developed it to death (like it's happened to a few other independent developers) due to the endless search to make it perfect.
I mean i love blip interactive but in general i don't trust anyone ;) including myself :D

Slam-Cut
Offline
Joined: 09/07/2011

Oh.
Thanks for 'splaining that!

Slam-Cut
Offline
Joined: 09/07/2011

Re: can't copy preset banks A-G

This point came up on a support thread, and I'm often trying to work around this issue, again this morning. My problem being cross-iDevice syncing of banks. My iPhone and iPad preset banks have never been the same. I didn't take the time to manually move all of the presets in anticipation of NS2 and possible librarian/syncing feature. My fault on that. I should have just bit the bullet (because 'Mericans actually do that...) and set it up long ago.

I know the point of a librarian has been brought up a lot in the past, but I don't remember any discussion of syncing preset banks on multiple devices. Cross-device syncing is a popular feature on other non-musical apps, and I'm throwing a vote in for it on NS2. I also have lots of tweaked or completely new presets in various project files and I can see a problem looming in knowing how to distinguish between presets that are the same and those that are different. A date stamp might help with that.

Would an short editable metadata file for each preset be unreasonable? Would it make the preset file too big? If not, I would like to add some notes to presets in NS2.

(This is the point where Matt's constant NS2-caused headache flares up)
Sorry Matt!

syrupcore
Offline
Joined: 09/26/2010

> For most parameters it would be over the top but for very subtle settings it would be a great add on.

Indeed. I'm seeing it more and more lately on 'critical' controls like filter cutoff and the like. It's also great for controls where dividing it by 127 between its min and max values really restricts it (like a delay with a max time of 4 seconds would be 19ms jumps between 0-127). Same idea behind pitch bend being 14bit really—would just sounds like shit if it weren't!

Blip Interactive
Offline
Joined: 04/05/2010

> I don't remember any discussion of syncing preset banks on multiple devices

I think a full sync is tricky unless almost everything else (mainly projects) are kept in sync too.

To go back a step for a moment, one of the design challenges is to make the best use of the storage space on the device, particularly when it comes to audio files (which are the main offenders as they tend to be the largest files). One extreme is to always copy everything. eg. when a project uses a synth preset, copy that preset and all the samples it needs to the project folder. This neatly removes all dependencies on that preset - ie. you may then delete/change/modify the preset and the project won't be affected. The downside is rapid storage bloat and possibly an unresponsive UI as it copies all these large files around when try a different present.

To solve this, I've yet to find a better way than the current NS1 model for projects. By this, I mean that projects only tend to refer to what they need (rather than take copies) and then the user decides at what point he or she wants to 'make a break' and export it into a self contained nsp file.

What this means is that projects have live dependencies on the synth presets until they become an nsp. If only the presets are being kept in sync, then deleting a preset on one device will delete the preset on your other devices (when they sync), and projects may get borked.

In NS2, synth presets are represented as individual folders. The folder contains the preset file (XML) together with any samples that preset uses. This results in some inefficiency (eg. two patches using the same sample will have their own copy of that sample) but does mean that they're fully 'self contained' and can be moved to another device without worrying about missing samples.

The bank system is gone in NS2 and replaced with a flat list of presets, but you can filter, sort and search by tag, type or name.

There will be some way to select one or more presets and export them to another device (airdrop/dropbox whatever).

NSPs will still be the main way to distribute and archive projects. In NS2 they're called archives and they have an NSA extension, but they're largely the same thing.

Galaxyexplorer (not verified)

I wonder how Mitosynth from Wooji Juice managed it. There it is possible that presets share the same samples without it needs to copy it and at the same time the samples are also contained in a preset.
It's still "by a country mile"....or a lightyear the best patch browser and patch managment system in the iOS world.

Slam-Cut
Offline
Joined: 09/07/2011

Yes, I see that syncing presets could be problematic. I also assume that 'borking' is much like 'dorking'...? :o/
I'm in favor of NS1 model as I am comfortable with it, and a list of tagable/searchable presets sounds cool. Hopefully there is no artificial limit to the number of presets? Is there still a project bank? Yay for Dropbox!! Thanks for that cool glimpse into the future. :o)

Whoa! NSA files! Great. Now the NSA is going to be reading all my posts and emails (which are amiditedly boring). :o/

Blip Interactive
Offline
Joined: 04/05/2010

http://www.urbandictionary.com/define.php?term=borked

I always thought it was from a corruption of 'broken' but maybe not.

Mitosynth seems to keep references to samples, and then makes the copy at the 'export package' stage, just like NanoStudio does with export NSP. It seems slightly borked to me (I was deliberately trying to bork it!). If you import a package containing samples which have the same name as samples already on the device, those samples aren't copied - even if the content of the samples is different. It seems to deal with patch file name clashes but not the resources they use.

This is type of issue I'm trying to avoid in NS2 by copying samples with the patch (unless they're factory or IAP content). Unlike a simple standalone synth, NS2 has a sample editor (so sample files can change on the device) and has multiple synths/instruments sharing the same sample files, so it's much easier to get in a tangle with regards to sample dependencies without some very simple copying rules.

Galaxyexplorer (not verified)

...and has multiple synths/instruments sharing the same sample files....
;)

Blip Interactive
Offline
Joined: 04/05/2010

.. I kind of meant 'instrument instances' but interpret what you will ...

Slam-Cut
Offline
Joined: 09/07/2011

"Very simple sample copying rules" sounds good to me. Don't bork that!
Sounds weird to me. Must be British slang. Or maybe I'm just too old to know what the 'kids' are saying nowadays.

Stiksi
Offline
Joined: 11/21/2010

Huh, I always thought "borked" was a combination of "broken" and "f***ed" (also "porked").

And the library system with Dropbox support Blip described sounds pretty sweet to me!