Tips and Tricks
Putting the tempo of a loop in the filename will help c3n loops to detect tempo correctly. If you don't put the tempo in the filename the app will guess the tempo. Those guesses make assumptions, that the tempo is close to 125 with four beat in a bar, and might therefore be wrong.
So name your files in the following formats to ensure correct tempo detection. filename_tempo.wav eg. HouseKick125.wav.
When importing loops try to import them in groups that make sense to you. The app will group all loops imported at a specific occasion in a spiral cluster. This makes it easier to find what you are looking for. If all your kicks are in one cluster and all your bases are in another they are easier to find. Another way you could group your loops is by track. So that if you import all loops that belong to the same track they will appear in the same cluster. All loops can be moved to whatever location you like after they have been imported. So if you make a mistake don't fret it just move the loops to wherever you want them to be.
We recommend the AudioShare app by Kymatica for importing loops. This is the only app that we know of that lets you import entire folders. This will create a cluster of all the folder’s loops in one operation instead of many individual file imports.
The first loop you play after starting the app will set the global tempo. Anything played after this loop will match the current tempo. If you stop everything this tempo will persist until you restart the app. This is a conscious design decision. We chose this mode of operation to support beatmatching with record players. When the correct tempo has been found multiple attempts to cue the app in sync with the record does not reset the tempo. Kill and restart the app if you like to reset the tempo.
If you want to temporarily remove loops that you are not currently using you can do so from iTunes. The loops will still appear on the surface as “Ghosts” and if you import them again they will start to work immediately.
My loops keep getting weird tempos , how can i fix this ?
The best way to ensure that your correct tempos are detected by c3n loops is to name your files correctly. The prefered format is filename_tempo.format eg HouseKick125.aif.
Why can´t i import wav files via google drive ?
This is an issue with google drive. For some reason wav files will are greyed out. Aif files work fine though.
How do i save my surfaces/loop-sets ?
This can easily be done via iTunes file import. Just navigate to the usual place in iTunes where you drag and drop files. Create a folder where you want to save your files. Select all files and drag them to this folder. When the copying process is done just delete all the files and you are ready to start a new surface. When you want to restore the old state just do this process in reverse. Delete all files via iTunes filesharing and the drag in all the files you saved in your folder. You will be prompted if you want to replace the database say yes. You have now restored the app to the exact same state as it was in when you "saved". The app cannot be running during this process and has to be shut down during the save/restore process.
How do MIDI and AbletonLink sync work?
To enable MIDI you double tap on the surface, in the top right corner you will see four symbols – the third midi 5 pin din cable symbol is the MIDI setting. Tap the symbol to enable or disable midi.
The status circle over the symbol is grey when MIDI is disable and fully white when enabled.
There are four combinations
- MIDI disabled & Link disabled -> everything is disabled
- MIDI enabled & Link disabled -> c3n loops sends MIDI sync to both to internal (inter-app) MIDI-ports and external MIDI-ports
- MIDI enabled & Link enabled -> c3n loops sends MIDI sync to only external MIDI-ports, inter-app and inter-device sync is via Link
- MIDI disabled & Link enabled -> inter-app and inter-device sync is done via Link, this setting is useful if you have another app doing the MIDI sync to your external gear
The MIDI sync, when enabled, is straightforward. Tap play of a loop or a scene to start any connected midi device. c3n loops sends clock pulses for one beat before it sends the start message. Thus, the connected devices have the correct tempo when they receive the start message.
Issues with playback speed of certain audio formats.
We have discovered that certain files that have sample rates other than 44.1khz play back with the wrong speed. To work around this bug use only 44.1khz files.
App sometimes freezes on iPad Air2 when connected via AudioBus.
If you have this issue please contact us on the adress below and state what AudioBus apps you where using and how the crash/freeze occurred.
Occasional crashes when deleting files from iTunes file share
The app occasional crashes when you delete files from iTunes file share. If this happened to you need to reboot the app.
When importing loops via iTunes with c3n loops closed may cause crash on some hardware.
First time launch issue
When starting c3n play one for the first time, after closing the tutorial video, the user interface might feel sluggish. You can fix this issue by killing the app and start it again.
We are grateful for all bug reports you send us. We always work to resolve bugs as fast as we can. We will put up info about bugs here to help you avoid/work around them.
Something we forgot ?
email us at firstname.lastname@example.org and we will try to help you out best we can.