Newbie Guide - Tips for workflow and usage

45 replies [Last post]
Joined: 06/27/2010

Some of the Q&A here in the Support forum have highlighted some workflow practices and other tips that can be useful to know when you're first learning your way around NanoSync. I'll try to collate them as I find them into this first thread (provided this Drupal instance doesn't time out editing rights for a post at some point)

-------- RTFM --------

The documentation that Blip wrote is actually very detailed yet minimalist and preemptively answers most of the typical issues/questions you'll have while learning your way around NanoSynth. But for those of you who don't "Read the Fraking Manual", the following tips cover the stuff you're least likely to figure out on your own by hacking around in the app interface.

--------- Setting the song tempo ----------

Finding the tempo setting can be confusing until you learn where to look for it:

Menu > Song > Tools > Tempo

To set the relative volume of the metronome click and the length of the recording count-in:

Menu > Song > Tools > Preferences

--------- Help! A note got stuck "on" somehow! How do I turn it off without losing my work? ---------

There are a few bugs lurking in v1.0 that can result in a note being stuck "on" and nothing you do will seem to shut it off. When this happens (it's very rare), just save your project work to that point (don't forget to save any Eden Synth presets you might have been in the middle of tweaking), then quit NanoStudio. Wait a few seconds, then restart NanoStudio, reload your project and carry on. No problem!

-------- Keeping the Demo projects "safe" ------------

The demo projects are not specially write-protected in any way, so it's easy to inadvertently modify one of them. The only way to restore the demo projects in v1.0 is to delete the app from your iDevice, then reinstall it from the App Store (you won't be charged again). Of course, this will effectively erase all your own project data, imported samples, resamples, etc. so don't do this lightly.

You can avoid the problem altogether by copying a demo project to a new project before you play around with it:

- Menu > Manage > Project > Load > select the demo project > Load
- Now before you mess around, Menu > Manage > Project > Save As > specify something other than the original project name > (checkmark)

-------- Keeping YOUR projects "safe" ----------------

Similar to the section above about keeping the Demo projects from being accidentally overwritten, you can use a similar workflow to keep your own work safe and versioned as you build up a song from scratch:

- Every time you come back to your project for another round of experimentation and refinement (or any time you want to "snapshot" what you have so far), do Menu > Manage > Project > Save As. NanoStudio will save this as a new copy of your original project and *automatically* append a nice -01, -02, -03, etc. sequentially-numbered suffix to the project name.

This approach enables you to easily go back to any snapshot within your project history and start again from that point, if need be. So anytime you get to a place you really like and don't want to risk losing all that work, do a Save As and accept the default project name with the new -03, -04, -05 suffix that NanoStudio proposes.

Blip: Nice touch on the automatic sequential project names for Save As! This is very workflow-friendly!

-------- Understanding the Start up dialog about auto-saved projects -------

When you quit NanoStudio *and* you have made any changes at all to a project *and* you have not manually saved those changes before quitting, the next time you start NanoStudio you are presented with an auto-save dialog:

- Choose "My Save" if you want to revert the project to it's last manually-saved state
- Choose "Auto Save" if you want to resume where you left off when you last closed the app

Note that reverting with "My Save" will *not* remove any sample files that you might have copied into the project folder, such as when you audition (import) a TRG bank and choose "OK" when prompted "Do you wish to copy the samples into the project folder".

-------- Making/Managing project folders, and what to keep in them ----------------

This section is more "something to think about" instead of being explicit advice. Blip made some very nice design decisions about storage of samples (.wav files), of Eden presets (patches/voices), and of project files. You have a lot of options for project file management.

- If you create a new project and save it without doing anything else, the project file ends up in the Projects folder.
- After a while this can get cluttered, especially if you regularly do "Save As..." to make multiple versions of a project as you go along (which enables you to revert to an earlier point and branch in a different direction, etc.).
- This root Projects folder can become especially cluttered when you start importing your own samples into NanoStudio, or if you make the (easy to do) mistake of choosing "Copy samples to my project folder" when importing a different drum bank into the TRG-16.

A useful practice is therefore to create one sub-folder beneath Projects for every separate project you're working on. This enables some very useful things:

- You can do as many "Save As..." operations as you like to keep multiple versions of your project, and it remains easy to pick the right one when you resume work on that project.
- You can indeed copy in all the samples from a TRG-16 drum bank and then *modify them* as needed for your project without affecting how they sound in other projects.
- You can import/load custom samples used just for that project (in either the TRG bank or as the sound generator for Eden synths) and keep them isolated from samples used in other projects.

If you ever want to reuse a sample from one project sub-folder in another project, there are two ways you can do this: by just referencing the original sample over in its original project sub-folder, or by copying the sample into your current project folder. Copying samples like this is somewhat counterintuitive at first, but very simple: you start from the project you want to copy the sample *into*, edit the TRG-16 pad or Eden Oscillator page, tap "Load" in the "Sample" area, browse to the project folder (or the NanoStudio "Samples" or "TRG Banks" system folders) that contains the sample you want, select the sample, then tap "Load Copy". This copies the selected sample into the same folder as your current project file. This is effectively what happens when you import an entire TRG-16 bank and answer "OK" to the prompt "Do you wish to copy the samples into the project folder".

-------- How to create new project subfolders and ensure your project files go in them ----------------

This is something everyone will figure out with enough experimentation, but if you're the type to RTFM, I can save you a few false starts:

- One thing to be aware of is that the automated numbering of sequential SAVE AS operations for a project file is based on:
++ When you first give the song a new name (either at initial creation or via a "Save As"
++ NanoStudio completely ignores any manual -nn suffix you might manually specify when naming a file

Why are the preceding two facts important? Say you inadvertently created a new project called SongOne in the root Projects folder and did a few SAVE AS while working along. So the file is now called SongOne-04. Now you decide that you want to put that project into its own subfolder because you're about to import a bunch of samples specifically for it and you want to keep everything organized. The only way to do this is:
1) Open SongOne-04.
2) Main Menu > MANAGE > Save As.
3) Tap "Browse" > navigate to the folder under which you want to create the new sub-folder > tap "New Folder" > Name the folder "SongOne" > tap the green check mark.
4) Tap the newly-created folder to drill into it.
5) Tap "New File" and specify "SongOne-04" as the name, because you want to make it clear that this is the version -04 of the project and you plan to keep the original, -02, and -03 versions around for a bit in their original folder path just in case you need them again.
6) So you make some new changes/additions to the project and do "Save As" to save a version -05 and... hey, wait a minute! NanoStudio is trying to name the new Save As "SongOne-02"! Sure, you can overwrite this each time, but that's a pain.

The guideline here is simple: When trying to manage and organize your projects, don't ever manually add a version suffix to any given Save As operation. If you end up moving a project file into a different folder for any reason, just give the new copy of the file a basic name and let NanoStudio start all over again with its automatic version numbers from -02 onwards.

As for how, exactly to create new folders and ensure that your project is placed in the right folder, use the same general pattern in the above example procedure. Just do this right off the bat for entirely new projects that you start working on, and plan your folder structure accordingly. I use a hierarchy that goes: Projects/My Stuff/(all my project folders as children of "My Stuff")

-------- Understanding/Managing the Eden Synth presets ----------------

The GLOBAL A and GLOBAL B preset banks for the Eden synths are just that -- global. This means if you "WRITE" any change back into those global banks, you will irreversibly alter the factory default presets that are available to every new/existing project. Sometimes this is exactly what you want, but understand that if you ever delete and reload the app from your iDevice, you'll effectively lose any such customizations made to the GLOBAL banks. It's also entirely possible that any app update might overwrite the GLOBAL banks with the factory defaults once again.

So while it might be tempting to modify a factory default preset, the safer option is to always WRITE your custom presets into the PROJECT bank! However, there are issues with this approach in the current v1.0 of NanoStudio
- In v1.0, the custom preset then exists *only* in that one project file and won't be available if you create a NEW project file.
- In v1.0, there is NO WAY to move the special project files (.bnk, .prj, and .sng) from your iDevice into your computer. (NanoSync only "sees" and moves .wav files at present.)
- Once we get the ability to move/sync the special project folders and files (specifically the "Eden.bnk" file) from your iDevice into your computer, we'll be able to effectively copy the custom Eden presets in the PROJECT bank from one project into another.

In the meantime, a workaround for copying a custom preset from the PROJECT bank for one project into the PROJECT bank for a different project is to use a slot in one of the GLOBAL banks as a "staging" area:

1) If you want to keep the GLOBAL preset currently in the GLOBAL slot you plan to use for staging, WRITE the GLOBAL preset currently in the slot into an empty slot in your PROJECT bank.
2) WRITE the PROJECT preset into that now-available slot in the GLOBAL bank (overwriting what's currently there).
3) Load the other project.
4) WRITE the preset from the staging slot in GLOBAL into some PROJECT slot.
5) Repeat this process (or just use multiple GLOBAL slots for staging and do it all in one go).
6) If you want to recover the factory presets you temporarily moved into the first project in step 1, load up that project again and WRITE those presets from the PROJECT bank back into their original GLOBAL slots.

--------- Patterns are extremely powerful (and understanding Parts versus Patterns) ---------

Understanding the difference between parts and patterns is the key to really make NanoSynth sing and dance and do backflips for you.

- When you real-time record something to a track (or manually draw in events to a portion of a track using the "Draw" tool), what's created is called a part.
- You can subsequently convert a part to a pattern (or a pattern back to a part). This is described further below.
- Patterns and parts are easy to distinguish in the "Song Editor" and "Part Editor". In the song editor, patterns have a number in the upper left corner, and parts are not numbered. When you select a pattern and "Edit" it, the name displayed in the "Status Bar" will be something like "Pattern 05". When you edit a part, the displayed name will be "Edit part".

A part is a discrete instance of a set of MIDI "events". If you copy the part and paste it into the same track or another track, you are duplicating that entire set of events and eating up precious resources!

A pattern, on the other hand, is effectively a link to a shared pool of events. No matter how many times you copy the pattern and paste it into the same track or another track, you are not duplicating the set of events. Therefore, you are conserving resources in your project. There are other benefits too, covered further below.

- Under the covers, what happens when you convert a part to a pattern is that the events in the part are stored in a named memory location (pool) called "Pattern nn"
- You can see all the patterns in a project by: Menu > Song > select any existing pattern > More > Properties > Pattern. The "Using Pattern" control does two things here:
+++ A) It tells you which pattern is currently assigned to the selection
+++ B) It tells you the length of the pattern and the number of events in the pattern
+++ C) It enables you to choose a *different* pattern for that same selection

When you delete all instances of a certain pattern from your "Edit Song" interface, the pattern itself remains in the pattern pool unless you use a special command sequence to delete all patterns that aren't currently linked in the song. For example, open the "Minimal" demo project and look at the "Edit Song" window. You'll notice that there is no Pattern 04 in any of the song tracks. Follow the above-mentioned path to view all the patterns currently stored in the project and you'll see that there is a Pattern 04 in the list of available patterns! Try replacing one of the existing patterns in the "Edit Song" window with Pattern 04 and see/listen to what happens to that selection within that track!

Besides saving resources by sharing a single pool of events into multiple instances throughout your song, patterns serve two other very useful purposes:

- Patterns automatically loop themselves when you change the length of the pattern by selecting it and dragging the "Length" handle (the bottom right handle). This is a powerful way to create a 4-bar phrase and then loop it out to 16 or 32 bars without actually creating 4x or 8x as many events or needing to mess with event copy-paste, etc. Or to chop a 4-bar phrase in half to a 2-bar phrase in certain places.
- If you edit one instance of a pattern, the same changes automatically occur in all other instances of the pattern throughout the song (because you're effectively editing a single shared set of events).

You convert parts to patterns (and vice-versa) by selecting the part and choosing: More > Properties > Pattern > Convert to pattern/part. Why would you want to convert a pattern back into a part? Say you've made a simple 4-bar drum loop part and you converted it to a pattern, then pasted that pattern into various places in your song arrangement. Now you decide you want to convert some of those instances into a drum fill. You can't just edit the pattern to contain a fill in the last bar, because this would take effect in every instance of the pattern! So what you do first is split the pattern at the points where you want to create fills, then select each new, split instance of the pattern and convert them back to parts. Now you can edit each part to be a different-sounding drum fill, and the original drum "loop" stays unchanged!

---------- Recording a long track while auto-looping sections of another track(s) ----------

NanoStudio doesn't have a loop on/off per track but you can perform a manual workaround to achieve the same result:

- Firstly, make the part that you want to loop, such as a drum loop for 4 bars.
- Select the drum loop part and turn it into a pattern (More/Properties/Convert to pattern)
- Use the 'length' drag handle to make the pattern nice and long (eg. 100 bars). It'll automatically repeat every 4 bars.
- In "The Main Menu", toggle the "Loop" button off so that the recorder won't loop at the measures marked by the "Bar ribbon" in the "Song Editor".
- Now record your long instrumental track.

--------- Why can I resample only X bars of my song? Working around the 4MB limitation for resamples ---------

You try to resample a project (for example, into an empty TRG-16 pad), which is currently 16 bars long, but, for some reason, the "Number of Bars" option won't go past 7.

The reason this happens is due to a current 4MB limit on sample sizes that can be imported into a TRG-16 pad (or into an Eden Synth when you use the "Sample" option on the Oscillator page). Depending on your song tempo, NanoStudio calculates on the fly how many bars of your song will fit into this 4MB limitation when resampling.

The workaround is simple: resample the max number of bars that NanoStudio will let you resample (for example, bars 1-7), then edit a different TRG-16 pad (or eden synth) and resample the next section of your song (bars 8-14: "Start from bar" = 8), etc. Be sure to Pre-roll at least one or two bars for the subsequent resamples (the 8-14 one, for example) so that any trailing effects from the first resample will smoothly mesh with the second resample, and so on.

--------- Changing among several synth presets within a given sequencer track ---------

If you haven't read the manual carefully you might not think it's possible to mix several different presets on a single track based on typical experimentation. However, you *can* set up any single Eden track to change its preset (voice/patch) as many times as you like!

- First, record a "part" or a "pattern" on the track for the measures that you want to specify to use a specific voice.
- Select the part/pattern, then tap More > Properties > Preset
- Tap Enable, then choose the specific preset to use during that part/pattern when the song is being played.

- When recording, the sound you hear will alway be the currently-selected preset in the Eden Synth for that track.
- You can changes presets like this only for the Eden tracks, not for the TRG-16 tracks
- Instances of a given pattern share only their event data, not the Eden preset that plays those events. For example, if you change one instance of Pattern 05 to use preset X and change another instance of Pattern 05 to use preset Y, each instance will play back using different voices. Meanwhile all the other Pattern 05 instances that you didn't explicitly set to use a certain preset will play back using the preset that is currently assigned to the Eden synth for that track!

--------- Exporting single tracks (or specific parts/patterns/bars of selected tracks) to WAV ---------

At first it might seem like you can export only an entire song to WAV format, but in fact you can easily export any single track, and with a simple workaround you can also easily export any selected bars from any combination of tracks or any single part/pattern from any track.

To export an entire single track or combination of tracks:
- Mute all the tracks you don't want and use the standard "Mix to wav" button.

To export any selected bars from any combination of tracks:
1) Save your project
2) Delete bars you DON'T want in the exported WAV
3) Mute the tracks you DON'T want in the exported WAV
4) Use the standard "Mix to wav" button
5) Important: Reload your saved project to get everything back the way it was. If you don't want to risk accidentally clobbering your project by forgetting this step, then in step 1 do a "Save As" and do the remaining steps on that temporary copy of your project. Then delete that temporary copy.

To export any one part or pattern to WAV:
- There are two ways to do this:
++ One is to use the same technique as for exporting any selected bars above, selecting only the bars within which the part/pattern sits. You could actually mix any number of parts/patterns that sit within this range of bars by muting/un-muting tracks as needed.
++ The other is to resample those bars within which the part(s)/pattern(s) sit to a TRG-16 pad, then use NanoSync to move the resulting sample WAV file to your computer. Note that there's a 4MB limitation on file size with this technique, so depending on your song tempo, this usually equates to 8 bars or less.

--------- Setting Pan for Eden and TRG tracks ---------

Due to space considerations, the "Mixer" does not have dedicated pan controls. The app documentation states that pan is assigned instead within each instrument. This is fairly straightforward for the TRG tracks, but less so for the Eden tracks. So here's how to set pan:

TRG tracks:

Pan is assigned individually for each pad (voice), so for example bass drum could be center, snare a little to the left, and high-hat a little to the right, etc. for a realistic spread on a drum set. To set the pan for a given pad:

Menu > TRG-16 > Home icon > EDIT > tap the pad to edit > PAN knob

Eden tracks:

There is no Pan knob anywhere for Eden synths in v1.0. Instead, you must assign the Pan CC to either the "Knob" controller that sits between the Pitch Wheel and the XY pads, or else to one of the XY pads, and then use those controllers as your "pan knob".

- Use the "Knob" controller when you want to set a single, static pan position for the selected part/pattern.
- Use one of the XY pads when you want to record real-time panning moves for the selected part/pattern.

The downside of doing this just to get some control over Pan is that you'll effectively erase whatever controller data might have previously been assigned to the "Knob" or XY pad. Make sure you care more about controlling pan for a particular Eden synth part/pattern than whatever controller data might have been previously assigned *before* you do the following steps!

To elaborate just a bit about controllers in general: Every Eden Synth part/pattern each has effectively 5 CC values that you can *flexibly* set and record. No more; no less. (There are other *fixed* CC values for pitchbend, velocity, etc.) Four of the *flexible* CCs are assigned to the axes of the two XY pads, and the 5th (Knob) is assigned to the small knob between the Pitch Wheel and the XY pads. You use the Patch Bay to assign the specific CC you want on each XY axis and on the "Knob". So again if Pan is important to you for a given part/pattern on an Eden track, that will eat up 2 of your 5 available *flexible, user-assigned* CCs that you can record. The other small gotcha is that the VALUE that you assign to a control surface can range from 0 to +100 or 0 to -100, but not from -100 to +100. So if you use only one control surface such as the "Knob" you can use the knob to sweep from Center to Left or Center to Right in its total range of motion, but not from Left to Right within its range. So if you want full Left to Right control, you must use the XY pad and devote one axis to be center to Left and the other axis to be center to right.

Setting up full Left to Right control on an XY Pad for recording real-time panning moves

1) In the "Song Editor", select the part/pattern for which you want to record some pan movement (or a static pan position), drag the loop markers on the "Song Ribbon" to match the start and end points of the part/pattern, then do Menu > toggle "LOOP" on. This setup ensures that while you're recording pan movement for the selected part/pattern, you stay within the boundaries of the selection and don't accidentally overwrite two of the XY CCs for the parts/patterns on the same track that immediately precede the one that you're tweaking for pan.

2) Menu > select the Eden track for the selected part/pattern > right-side page down button to the "Patchbay Page" > select Source: XYPad 1 X > tap the Destination +- buttons until Osc appears > tap the Parameter +- buttons until Pan appears > tap the Amount +- buttons to specify Amount: 100

3) While still on the "Patchbay Page" > select Source: XYPad 1 Y > tap the Destination +- buttons until Osc appears > tap the Parameter +- buttons until Pan appears > tap the Amount +- buttons to specify Amount: -100

4) Go back to the "Performance Modulation Page" (where the two XY pads are) and experiment with XY PAD 1 while just playing some notes. You'll see that any position in the upper-left quadrant pans the sound to the left, while any position in the lower-right quadrant pans the sound to the right. Now we're ready to record the pan movement for the selected part/pattern!

5) Hit the record button and after the count-in, *ONLY* move the XY PAD 1 around as desired for the duration of the looped section. This overwrites any existing CC events that might have been there already.

6) If you want to fine tune your XY movements, use Menu > Song > select the part/pattern > EDIT > tap the Note button just below the red record button > choose one of the Pad axes or the "Knob" > edit to your heart's content. This is a great way to draw visual slopes and curves. The height of each vertical line equals the velocity value assigned to the CC at that point. For CCs like pan, remember that 0 = center and +1.0 = extreme left or extreme right depending on which pad axis you're looking at. If you assigned pad axis X to +100 in the patchbay, and pad axis Y to -100 in the patchbay, then seeing a high bar in the Pad X and a low bar in Pad Y at the same timestamp means the pan will be RIGHT. Seeing a high bar in Pad Y and a low bar in Pad X at the same timestamp means the pan will be LEFT.

NOTE: Trying to record pan motion for *patterns* can yield some results that don't make sense until you remember that a pattern that looks 16 bars long in the song editor might in fact be a simple 1-bar phrase that is auto-looped 16 times! In this case, only one bar's worth of XY PAD movement is recorded, and then whatever you do next in bar 2 of the song *overwrites* what you just did in bar 1, which is then overwritten again in bar 3 and so on! So do yourself a favor and convert the pattern to a part whenever you want to record a lot of XY motion of any sort, not just pan.

Setting up a static pan position on the "Knob"

Read the above section because I'm just going to summarize what's different in this case. The trick here is to assign a patchbay VALUE of -100 to the "Knob" if you want the Eden part/pattern to sit somewhere on the Left side of the stereo field, and to assign a VALUE of 100 if you wat the part/pattern to sit somewhere on the Right side of the stereo field.

After doing this, the knob at its zero position (full left) will be center, and the knob at its max position (full right) will be either extreme left or extreme right depending on whether you defined a positive or negative value in the patchbay.

Isn't NanoStudio just amazingly deep for an iDevice app? The patchbay is beyond cool.

--------- Using the Eden Synths to create good drum sounds ---------

KrisM has authored a really nice, detailed guide to using multiple Eden Synths to create good drum sounds. No need to go digging around for drum sample libraries! The basic idea is that you use multiple Eden tracks to create a drum sound you like, then resample all of them combined into a TRG-16 pad, which also creates a .wav file that you can keep in your NanoStudio/NanoSync library and assign to other TRG-16 banks (or to an Eden synth preset) as needed.

Here's KrisM's post:

--------- Editing sample loop start/end points in real time while hearing your edits immediately ---------

The v1.0 Sample Editor does not have true loop points yet, so tweaking a sample loop currently requires that you actually trim the start/end points of a sample. This can be clunky if you do it the most obvious way because:

- The Sample Editor is destructive
- The Sample Editor does not provide a way to audition your trim changes during editing

There is a simple workaround for v1.0 that enables you to hear your edits in real-time and overcome the destructive nature of the editing process:

1) Record a part/pattern that triggers your original sample when you want it in the context of your other parts/patterns that you're trying to match it up to.
2) Start the sequencer playing in loop mode over the bars that contain the part/pattern with the sample in it.
3) While the looped section is played over and over, open the Sample Editor.
4) Change the timebase displayed in the Sample Editor to display bars/beats instead of time (tap the upper right TIME button).
5) Now trim the sample start/end points and you'll hear the changes in context, in real time.
6) Use the UNDO menu to walk backward through your changes if you need to get back to some earlier point in your edits.
7) Once you have trimmed the sample the way that you like it, exit the Sample Editor and use SAVE AS to save your trimmed version as a new sample with a different name, so that your original remains unaltered. The TRG-16 Pad or Eden Synth in your project will automatically use the new, trimmed version of your sample.

--------- MORE TIPS COMING SOON! ---------

Joined: 07/22/2010

I missed the part about changing presets in the middle of the song. I feared I was going to have to do a lot more bouncing/resampling that I'll actually have to. :)

Blip Interactive
Joined: 04/05/2010

Wow! That's an impressive post - cheers!

Joined: 06/27/2010

Thanks! I just added a section at the bottom on how to do panning for Eden and TRG tracks. The Eden side of things isn't very easy to figure out; I needed to see a tip from you in some other post here to see how it could be done. ;) Hopefully the iPad version will have enough realestate in the Mixer page to allow adding some useful knobs such as Pan.

Joined: 07/12/2010

Brilliant tips, keep 'em coming :)


Joined: 06/27/2010

Just a quick note to people keeping track of this thread: When I discover and add new tips, I often insert them into the middle of the original post in this thread, not at the beginning or end of the post. I'm trying to order the tips in top-down order roughly by easiest > hardest AND most-common > least common.

So skim the bold sub-headings to see if there's anything new since the last time you checked it out.

Bob Morris 1963
Joined: 07/25/2010

Maybe I'm thick, i've looked at the manual and may have missed it but can anyone tell me how to cut and paste / copy and paste?
I just realised I want to copy bars 9-12 to bars 1-4 how do I do this?
When I select 19-12, the copy just seems to put the copied bars to 13-16... but i want them to be copied to 1-4....

Blip Interactive
Joined: 04/05/2010

The sequencer doesn't really have a paste as such, just a 'copy the current selection'. The copied parts are always placed straight after the originals but they stay selected so you can move them elsewhere. So what you need to do is:

- Select the parts you want to copy
- Tap copy
- Use the position drag handle (the smallish orange button on the bottom left) to move the copied parts so they start on bar 1

Hope that makes sense!

Bob Morris 1963
Joined: 07/25/2010

i've sussed it...

Joined: 06/27/2010

Just a bump to the top again, since I've added a lot more material to the OP in this thread over the last few days. Remember folks, this post will grow over time as people have questions and tips and workarounds are discovered.

Blip Interactive
Joined: 04/05/2010

I've made this post sticky so it stays at the top now. I can always prune any comments if they get 'committed' to OP to declutter the thread. Not sure if it's a good/bad thing to do that.

Joined: 06/27/2010

Your call; your'e the board moderator ;-) IMO it doesn't matter how long the comments/replies get as long as Drupal keeps allowing me to edit post #1 in the thread as needed for updates.

Joined: 08/11/2010

great thread and fantastic tips - thank you :)

Joined: 06/05/2010

Yeah. This is great. It's like a deep dive into the workings of nanostudio. It's much appreciated. Thanks.

Joined: 09/12/2010

Very helpful indeed. Much appreciated!

Joined: 10/04/2010


First of all, thank you Blip for the making dreams of a sequencer this easy to use and fantastic-sounding come true. And I've been dreaming a long time...

My question is about Midi Export. I've done the Project Export bit on the iphone, but on Nanosync on my Mac all I can see are wave files inside my project folders, not the nsp.

Sorry if this is completely obvious, I have been trying and reading the help files though.

Thanks again for a superb app.

Blip Interactive
Joined: 04/05/2010

There a couple of ways to export MIDI. You can do it from the song editor (Tools->MIDI File tab->Export). Alternatively when you export your project as an nsp file (MANAGE->Project tab->Export) it puts a MIDI version of the sequence inside the nsp file, which you can rename to .zip on your PC/Mac and then open using a zip tool.

Sounds like you've done the last one OK so I suspect you're probably running NanoSync V1.0? You can see files of all extensions (not just wavs) if you hold down CTRL+SHIFT when you click on the Connect button, but I'd recommend upgrading to V1.1 which will let you see all these files by default.

Joined: 10/04/2010


What a pr*ck I am! Sorry. It never even occurred to me that I had to update Nanosync. You are the man. Can't believe you are online answering questions at half ten on a Sunday. Thank you.

You really do need a paypal donate button on your site.

Blip Interactive
Joined: 04/05/2010

Just fitting in a couple of replies before bedtime ...

Joined: 10/10/2010

Hi blip, is there a way of spitting a recorded Eden part into two separate parts, like in logic where you can split at the playhead,

Blip Interactive
Joined: 04/05/2010

Yes there's a split function under the 'More...' button in the song editor.

Joined: 08/22/2010

I write a beatslicing tutorial focused to Trg (and BM too) so you can use a "pseudorex files" in your songs

Joined: 11/16/2010

when you highlight them the two little boxes with arrows in the middle towards the bottom let you move and lengthen the bars. All you have to do is touch the little box on the left and drag all the way to the spot you want.

Joined: 08/31/2010

@shannong You ROCK!
Thanks so much for the great tips! This is a fantastic resource!

Joined: 07/23/2010

Hi, nice useful post! Thanks Shannong.

Just noticed a really unimportant something, maybe am I reading it the bad way but you wrote
"that can be useful to know when you're first learning your way around NANOSYNC" at the very beginning of your post, shouldn't it be 'Nanostudio' instead??

Joined: 08/11/2010

I don't know if anyone has posted this before but an (obvious) idea I've had recently when I've needed more than 4 edens playing at once, is to mute one of the existing edens in the sequencer and then audition a new Eden part. Then delete one of the existing Eden tracks and record the new parts. Now save the song with a different name. The tracks can ultimately be united in a DAW. I know you can also resample Eden into the TRG but I find the pads can get pretty crowded, there is a sample size limit, and any subsequent tempo changes cause the sampled loops to go out of time.

Joined: 03/30/2011

Ok so I was trying out multiple presets on the same track and noticed like it said in your *note* that all the parts on the track will still play the same selected preset. How do I get it so I can hear the change from one preset to another? I'm still pretty noob at this but learning fast.

Joined: 10/07/2010

EDIT - Ignore, I misread your question...
EDIT2 : You need to have the 1 parts

parts 1 and 2 need to be set to 2 different presets for the sound on the synth to change. :)

Joined: 07/30/2011

I must be BLIND, but I cannot locate the File Dialog box for the life of me! How do I get to it??????

Joined: 07/31/2011

Tap that three horizontal bars on the top left corner and click the "Manage" button.

Joined: 11/26/2011

Thank you for this post. I really didn't read the manual; I found the print on the iPod too tiny. The program is easy (I find some of the questions funny) and figured most features by trial and error. This really helped and I cannot wait to start using Nano more effectively.

Thanks again, I love NanoStudio,

Lucky G