Atom | Piano Roll 2 is now available

Jamie_Mallender

@espiegel123 said:

@Jamie_Mallender said:

@tk32 said:
Atom2 is very low on resources, and was bomb tested on various models dating back as far as the iPad Air2.

It sounds like the other apps may be more responsible for your CPU drain @Jamie_Mallender and I've heard drum computer is not exactly lightweight when it's running 8 separate drum synth chains in real time.

I would suggest increasing your host's audio buffer to 512 or even 1024 samples to give your iPad a little more CPU capacity.

I’ve already increased the buffer to 512. Haven’t tried 1024 yet though. I’ve also tried swapping out the AUV3s for different AUV3s several times. Even when I’m up and running and everything is fine with about 30 - 35 DSP, there’s a huge spike when I open an Atom 2 instance.

Is the crash happening when you load atom during playback or even if everything is idle?

When idle. It is much worse during playback.

blueveek

@Jamie_Mallender said:

@espiegel123 said:

@Jamie_Mallender said:

@tk32 said:
Atom2 is very low on resources, and was bomb tested on various models dating back as far as the iPad Air2.

It sounds like the other apps may be more responsible for your CPU drain @Jamie_Mallender and I've heard drum computer is not exactly lightweight when it's running 8 separate drum synth chains in real time.

I would suggest increasing your host's audio buffer to 512 or even 1024 samples to give your iPad a little more CPU capacity.

I’ve already increased the buffer to 512. Haven’t tried 1024 yet though. I’ve also tried swapping out the AUV3s for different AUV3s several times. Even when I’m up and running and everything is fine with about 30 - 35 DSP, there’s a huge spike when I open an Atom 2 instance.

Is the crash happening when you load atom during playback or even if everything is idle?

When idle. It is much worse during playback.

To be fair, you’re also using an iPad with an A9 processor, which is the same as in an iPhone 6s. So, really quite old by now. You might be hitting the limits of what your device is capable of. As a last resort, you could try setting “reduce motion” in your iOS settings to see if that helps. You might also want to try a host that’s not animating windows when opening instances, I’ve heard people saying they sometimes experience CPU spikes because of that.

Samu

@Jamie_Mallender Have you tried enabling "Reduce Motion" under Accessibility > Motion?

On my iPad Air 2 it makes a huge difference when it comes to CPU usage...
...I also try to keep just once instance visible at one time.

@blueveek I do wish it was possible to keep one Atom 2 window open and switch the instances without close/open/close.
(Ie. just keep one 'edit window' open and select which instance to edit using a pop-up similar to the layer thing).

This would reduce the 'open, close, open, close, open, close, open, close' that easily gets quite annoying after a while

Jamie_Mallender

@Samu said:
@Jamie_Mallender Have you tried enabling "Reduce Motion" under Accessibility > Motion?

On my iPad Air 2 it makes a huge difference when it comes to CPU usage...
...I also try to keep just once instance visible at one time.

@blueveek I do wish it was possible to keep one Atom 2 window open and switch the instances without close/open/close.
(Ie. just keep one 'edit window' open and select which instance to edit using a pop-up similar to the layer thing).

This would reduce the 'open, close, open, close, open, close, open, close' that easily gets quite annoying after a while

I haven’t tried that Samuel. I’ll make a note of that for future but for now my problems have gone

Jamie_Mallender

Thank you very much everyone who tried to help yesterday. Funny thing.... I disconnected all my controllers and erm.... now everything’s working brilliant! I didn’t even know that was a thing....

blueveek

@Jamie_Mallender said:
Thank you very much everyone who tried to help yesterday. Funny thing.... I disconnected all my controllers and erm.... now everything’s working brilliant! I didn’t even know that was a thing....

Oh! In that case, it's likely that there was a MIDI routing problem causing an overflow with the other plugins. It might not be that, but from your description the symptoms point to that. I'm glad to hear you got it resolved.

blueveek

Version 2.0.4 is out:

• A user manual is now available. Find it in an instance's app menu.
• Tapping will now preview notes on the piano roll vertical keyboard.
• Powerful new swing controls: apply negative swing, nudge the timings or control the durations.
• Drag and drop not just MIDI, but also scripts, styles or configurations onto your clips, and they will immediately apply to your session. Want to try out a different skin? Or bring your controller to life? Just drag and drop. Easily import and use code that others wrote!
• Scripts now support message logging. A new directory called "Logs" is created in your Atom folder containing log files. Devices, input and output ports are automatically logged for convenience. Use console.log(...) to log a custom message from your script.
• Controller scripts specifying an input and output port can now use either the short name or the longer label for port identification.
• Added new ways of visualizing velocity: with colors, opacity, bar positioning or thickness, or the numerical value itself.
• Added new ways of visualizing pitch: octave colors, highlighting in and out of scale notes and others.
• Added a plethora of additional example styles to get you inspired.
• Fixed an issue where certain controllers (like the Launchkey Mini) would emit high-pitched sounds when manually routed.
• MIDI clock is now passed-through with Novation controllers when routed through clips.
• CC messages are now passed-through (but not recorded yet) when routed through clips.
• Mutation panel controls are now reset to default after baking non-destructive processing operations.
• The velocity offset slider is now more accurate.

Gdub

@blueveek
Cool
Nice work
Thanks

Jamie_Mallender

@blueveek said:
Version 2.0.4 is out:

• A user manual is now available. Find it in an instance's app menu.
• Tapping will now preview notes on the piano roll vertical keyboard.
• Powerful new swing controls: apply negative swing, nudge the timings or control the durations.
• Drag and drop not just MIDI, but also scripts, styles or configurations onto your clips, and they will immediately apply to your session. Want to try out a different skin? Or bring your controller to life? Just drag and drop. Easily import and use code that others wrote!
• Scripts now support message logging. A new directory called "Logs" is created in your Atom folder containing log files. Devices, input and output ports are automatically logged for convenience. Use console.log(...) to log a custom message from your script.
• Controller scripts specifying an input and output port can now use either the short name or the longer label for port identification.
• Added new ways of visualizing velocity: with colors, opacity, bar positioning or thickness, or the numerical value itself.
• Added new ways of visualizing pitch: octave colors, highlighting in and out of scale notes and others.
• Added a plethora of additional example styles to get you inspired.
• Fixed an issue where certain controllers (like the Launchkey Mini) would emit high-pitched sounds when manually routed.
• MIDI clock is now passed-through with Novation controllers when routed through clips.
• CC messages are now passed-through (but not recorded yet) when routed through clips.
• Mutation panel controls are now reset to default after baking non-destructive processing operations.
• The velocity offset slider is now more accurate.

Oh wow! This is exciting! Thank you for your hard work and patience

galmandsværk

I have an issue that I hope someone can help me on.

I have two rows of Atoms triggering an instance of BeatHawk. One row is doing various beat patterns (choke on), the other row contains various percussive patterns (no choke). Row one sends in channel 1, row two send on channel 2. BeatHawk receives this and plays accordingly.
I then use my AKAI MPD226 to shift/trigger clips in Atom. It is programmed to send midi in channel 11. I set it up to trigger the different atom clips, and it works with no problem.
But, here’s the problem. When I press a pad on my AKAI controller, it also triggers a sample in BeatHawk (because they share the same midi CC value. It seems that the midi information travels “through” Atom and on into BeatHawk. I have muted the Listen function in all Atoms, but to no avail. BeatHawk is set to receive midi on only channel 1 + 2.
How can I avoid this triggering? This doesn’t happen when I use Atom to trigger i.e. Kong Module or Digitrix.

Edward_Alexander

@blueveek said:
Version 2.0.4 is out:

• A user manual is now available. Find it in an instance's app menu.
• Tapping will now preview notes on the piano roll vertical keyboard.
• Powerful new swing controls: apply negative swing, nudge the timings or control the durations.
• Drag and drop not just MIDI, but also scripts, styles or configurations onto your clips, and they will immediately apply to your session. Want to try out a different skin? Or bring your controller to life? Just drag and drop. Easily import and use code that others wrote!
• Scripts now support message logging. A new directory called "Logs" is created in your Atom folder containing log files. Devices, input and output ports are automatically logged for convenience. Use console.log(...) to log a custom message from your script.
• Controller scripts specifying an input and output port can now use either the short name or the longer label for port identification.
• Added new ways of visualizing velocity: with colors, opacity, bar positioning or thickness, or the numerical value itself.
• Added new ways of visualizing pitch: octave colors, highlighting in and out of scale notes and others.
• Added a plethora of additional example styles to get you inspired.
• Fixed an issue where certain controllers (like the Launchkey Mini) would emit high-pitched sounds when manually routed.
• MIDI clock is now passed-through with Novation controllers when routed through clips.
• CC messages are now passed-through (but not recorded yet) when routed through clips.
• Mutation panel controls are now reset to default after baking non-destructive processing operations.
• The velocity offset slider is now more accurate.

Wow! Just look at those patch notes!

Thank you SO much @blueveek

blueveek

@galmandsværk said:
I have an issue that I hope someone can help me on.

I have two rows of Atoms triggering an instance of BeatHawk. One row is doing various beat patterns (choke on), the other row contains various percussive patterns (no choke). Row one sends in channel 1, row two send on channel 2. BeatHawk receives this and plays accordingly.
I then use my AKAI MPD226 to shift/trigger clips in Atom. It is programmed to send midi in channel 11. I set it up to trigger the different atom clips, and it works with no problem.
But, here’s the problem. When I press a pad on my AKAI controller, it also triggers a sample in BeatHawk (because they share the same midi CC value. It seems that the midi information travels “through” Atom and on into BeatHawk. I have muted the Listen function in all Atoms, but to no avail. BeatHawk is set to receive midi on only channel 1 + 2.
How can I avoid this triggering? This doesn’t happen when I use Atom to trigger i.e. Kong Module or Digitrix.

Disable "Thru Input" from your clip's menu. Notice the helpful tip telling you to do so when you set a launch note or cc from the advanced clip settings. Hope this helps.

galmandsværk

@galmandsværk said:
I have an issue that I hope someone can help me on.

I have two rows of Atoms triggering an instance of BeatHawk. One row is doing various beat patterns (choke on), the other row contains various percussive patterns (no choke). Row one sends in channel 1, row two send on channel 2. BeatHawk receives this and plays accordingly.
I then use my AKAI MPD226 to shift/trigger clips in Atom. It is programmed to send midi in channel 11. I set it up to trigger the different atom clips, and it works with no problem.
But, here’s the problem. When I press a pad on my AKAI controller, it also triggers a sample in BeatHawk (because they share the same midi CC value. It seems that the midi information travels “through” Atom and on into BeatHawk. I have muted the Listen function in all Atoms, but to no avail. BeatHawk is set to receive midi on only channel 1 + 2.
How can I avoid this triggering? This doesn’t happen when I use Atom to trigger i.e. Kong Module or Digitrix.

Never mind. I worked out it out. Needed to disable midi thru in each clip. Silly me. Learning every day

mlau

Gorgeous @blueveek

Edward_Alexander

@blueveek and whoever else worked on it, The Manual is beautiful!

Including the manual inside the app as a feature is brilliant and definitely gives Atom 2 that AAA title vibe.

However:

It took me waaaay longer than I’d like to admit to scramble and repair my Dropbox account so I could download and a view the manual outside of an Atom2 instance.

Could you include a link to the manual that doesn’t involve Dropbox? (for other/future users that may not have or use Dropbox) Or maybe just a link on your website?

blueveek

@Intrepolicious said:
@blueveek and whoever else worked on it, The Manual is beautiful!

@tk32 is the best designer there is.

Including the manual inside the app as a feature is brilliant and definitely gives Atom 2 that AAA title vibe.

However:

It took me waaaay longer than I’d like to admit to scramble and repair my Dropbox account so I could download and a view the manual outside of an Atom2 instance.

There’s no need for a Dropbox account to download the manual, it’s just the exact link that wasn’t optimal for that. We’re updating it right now, and the manual inside the app will magically update too.

EDIT: Links updated, manual in the app already updated.

• tinyurl.com/Atom2Manual
• tinyurl.com/Atom2PrintMan

RajahP

@blueveek said:
Version 2.0.4 is out:

• A user manual is now available. Find it in an instance's app menu.
• Tapping will now preview notes on the piano roll vertical keyboard.
• Powerful new swing controls: apply negative swing, nudge the timings or control the durations.
• Drag and drop not just MIDI, but also scripts, styles or configurations onto your clips, and they will immediately apply to your session. Want to try out a different skin? Or bring your controller to life? Just drag and drop. Easily import and use code that others wrote!
• Scripts now support message logging. A new directory called "Logs" is created in your Atom folder containing log files. Devices, input and output ports are automatically logged for convenience. Use console.log(...) to log a custom message from your script.
• Controller scripts specifying an input and output port can now use either the short name or the longer label for port identification.
• Added new ways of visualizing velocity: with colors, opacity, bar positioning or thickness, or the numerical value itself.
• Added new ways of visualizing pitch: octave colors, highlighting in and out of scale notes and others.
• Added a plethora of additional example styles to get you inspired.
• Fixed an issue where certain controllers (like the Launchkey Mini) would emit high-pitched sounds when manually routed.
• MIDI clock is now passed-through with Novation controllers when routed through clips.
• CC messages are now passed-through (but not recorded yet) when routed through clips.
• Mutation panel controls are now reset to default after baking non-destructive processing operations.
• The velocity offset slider is now more accurate.

Thanks for all your work... Don't be afraid to IAP us... we are more than willing... Thanks..

vasilymilovidov

It’s kinda incredible that atom 2 and aum look, feel and work better than most AAA apps. also kinda sad and inspiring all at the same time.

tk32

@Intrepolicious - many thanks for the kind words. All of the manual links have now been updated to no longer require any dropbox login. The version inside the app is updated with the new links too.

Atom2 Manual - Full colour version:
tinyurl.com/Atom2Manual

Atom 2 Manual - Printable version:
tinyurl.com/Atom2PrintMan

slicetwo

@blueveek Massive ups for adding the note preview via vertical keyboard touch! Thank you so much!!

FloRi89

So, right on this new release where you can now drag & drop your themes, I finally have the theming video ready . I was recovering from a cold, you can still here that in my voice. I hope it works anyway. Enjoy, I‘m covering all of the basics for theming there I think:

Edward_Alexander

@blueveek said:

@Intrepolicious said:
@blueveek and whoever else worked on it, The Manual is beautiful!

@tk32 is the best designer there is.

Including the manual inside the app as a feature is brilliant and definitely gives Atom 2 that AAA title vibe.

However:

It took me waaaay longer than I’d like to admit to scramble and repair my Dropbox account so I could download and a view the manual outside of an Atom2 instance.

There’s no need for a Dropbox account to download the manual, it’s just the exact link that wasn’t optimal for that. We’re updating it right now, and the manual inside the app will magically update too.

EDIT: Links updated, manual in the app already updated.

• tinyurl.com/Atom2Manual
• tinyurl.com/Atom2PrintMan

@tk32 said:
@Intrepolicious - many thanks for the kind words. All of the manual links have now been updated to no longer require any dropbox login. The version inside the app is updated with the new links too.

Atom2 Manual - Full colour version:
tinyurl.com/Atom2Manual

Atom 2 Manual - Printable version:
tinyurl.com/Atom2PrintMan

Thanks fellas! You guys are amazing!

One more thing I was just thinking the manual needs at the end, or page 24 (and I know it’s still a WIP, so you probably are already putting it together), but maybe a “Final Thoughts” or Acknowledgments and credits page where you can share your contact info, yours and anyone’s else that worked on Atom2 pictures here, and any important links, like the much anticipated Patchstorage link.

Stuntman_mike

Bravo @blueveek and @tk32!!! You all are elevating the game!

Richtowns

@tk32 the manual is an impressive piece of work.

ashh

Can anyone help me out? I have 2 instances of Files open, side by side. If I try to drag and drop the stylesheet from the root of my iCloud drive I get the circle with a bar across it at the end of the filename. I can save the files to any folder in iCloud except Atom2. How do I put the stylesheets into Atom's folder?

I hate Files.

blueveek

@ashh said:
Can anyone help me out? I have 2 instances of Files open, side by side. If I try to drag and drop the stylesheet from the root of my iCloud drive I get the circle with a bar across it at the end of the filename. I can save the files to any folder in iCloud except Atom2. How do I put the stylesheets into Atom's folder?

I hate Files.

Drag and drop onto an Atom instance.

Maybe also take a look at the "File Menu" section in the manual now that it's available, under "Installing styles, configs, scripts".

ipadbeatmaking

@blueveek congrats on another stellar release! @tk32 incredible work on the manual, both versions look great! That BM3 one must be a monster in length!!

Quick question, since I’ve seen the Roli Noise app and ZenBeats change the Roli lightpad blocks in real-time, I’m wondering @blueveek, do you think it’s possible to have the Roli Lightpad(s) have the feature set(s) of the launchpads with Atom?

Tim6502

@blueveek said:

@ashh said:
Can anyone help me out? I have 2 instances of Files open, side by side. If I try to drag and drop the stylesheet from the root of my iCloud drive I get the circle with a bar across it at the end of the filename. I can save the files to any folder in iCloud except Atom2. How do I put the stylesheets into Atom's folder?

I hate Files.

Drag and drop onto an Atom instance.

Maybe also take a look at the "File Menu" section in the manual now that it's available, under "Installing styles, configs, scripts".

So only drag-and-drop works for this?!
(Generally I disable multi-touch gestures, since these mess with many music UIs. Thus not a fan of strictly drag-and-drop idioms.)

blueveek

@ipadbeatmaking said:
@blueveek congrats on another stellar release! @tk32 incredible work on the manual, both versions look great! That BM3 one must be a monster in length!!

Quick question, since I’ve seen the Roli Noise app and ZenBeats change the Roli lightpad blocks in real-time, I’m wondering @blueveek, do you think it’s possible to have the Roli Lightpad(s) have the feature set(s) of the launchpads with Atom?

If the Lightpads support external control, then there’s no reason I can think of why they couldn’t be scripted by Atom.

@Tim6502 said:

@blueveek said:

@ashh said:
Can anyone help me out? I have 2 instances of Files open, side by side. If I try to drag and drop the stylesheet from the root of my iCloud drive I get the circle with a bar across it at the end of the filename. I can save the files to any folder in iCloud except Atom2. How do I put the stylesheets into Atom's folder?

I hate Files.

Drag and drop onto an Atom instance.

Maybe also take a look at the "File Menu" section in the manual now that it's available, under "Installing styles, configs, scripts".

So only drag-and-drop works for this?!
(Generally I disable multi-touch gestures, since these mess with many music UIs. Thus not a fan of strictly drag-and-drop idioms.)

Then you can use a third party app (e.g Textastic) to add or copy files inside any App folder on iCloud, or do it on your desktop. As an aside, drag and drop doesn’t necessarily require multi touch (e.g. when having an app already open side-by-side).

ErrkaPetti

@blueveek said:
Version 2.0.4 is out:

• A user manual is now available. Find it in an instance's app menu.
• Tapping will now preview notes on the piano roll vertical keyboard.
• Powerful new swing controls: apply negative swing, nudge the timings or control the durations.
• Drag and drop not just MIDI, but also scripts, styles or configurations onto your clips, and they will immediately apply to your session. Want to try out a different skin? Or bring your controller to life? Just drag and drop. Easily import and use code that others wrote!
• Scripts now support message logging. A new directory called "Logs" is created in your Atom folder containing log files. Devices, input and output ports are automatically logged for convenience. Use console.log(...) to log a custom message from your script.
• Controller scripts specifying an input and output port can now use either the short name or the longer label for port identification.
• Added new ways of visualizing velocity: with colors, opacity, bar positioning or thickness, or the numerical value itself.
• Added new ways of visualizing pitch: octave colors, highlighting in and out of scale notes and others.
• Added a plethora of additional example styles to get you inspired.
• Fixed an issue where certain controllers (like the Launchkey Mini) would emit high-pitched sounds when manually routed.
• MIDI clock is now passed-through with Novation controllers when routed through clips.
• CC messages are now passed-through (but not recorded yet) when routed through clips.
• Mutation panel controls are now reset to default after baking non-destructive processing operations.
• The velocity offset slider is now more accurate.

WTF!!! Victor, do you EVER sleep??

Atom 2 is soooo amazing and awesome that this Eastern holliday is a joy (to be on vacation)...

Perhaps time for some IAP so we can give you some more cash?