ATOM Piano Roll update is coming soon

Janosax

Needs CC too so option 2.

david_2017

One 👊🏼🙃

Darby

2, or release the future version as ATOM 3 with CC editing. ATOM 4 with MPE.

drez

@blueveek said:

@drez said:
I personally wouldn’t use it without automation. I automate everything But I’m not a randomization person, I’m a sequence what I want it to do person.

To clarify: in my post, "automation" meant CC editing. Atom itself is automate-able (parameters exposed etc.).

Yeah, that’s what I figured. If I can’t automate the thing I am sequencing, it’s useless for my use case. I see what other people are saying as useful for importing midi, but my plan was to use it as a sequencer in AUM to sequence midi notes and automate AU’s parameters like I can in a DAW. If I can’t do that, then yeah it’s not doing anything for me. Doesn’t mean people don’t need the stuff available in option 1, but for me I will be waiting.

ALB

I voted for option 2 initially, but in reading other’s comments I realize that further updates would stoke interest in the app. I really do want automation, but can live without it for now. Whatever - it will be great either way.

Lil_Stu07

Option 1, no matter what features are present at launch you will still get flooded with requests here. This crowd is never satisfied lol.

ExAsperis99

Can we define what we mean by automation?

For instance: I have a synth that is being sent midi from an instance of Atom. As this clip plays back, I manually open and close the filter on the synth. That gesture could not be recorded by Atom2, correct? Or would it be recorded but editing it would not be possible? Would love to see that in the future.

I still vote for No. 1. By a mile.

horsetrainer

I vote for option 1...

I'd like to have an AU Piano-Roll Midi editor that will enable me to record Midi notes or open a Midi file made by another App. Edit the Midi notes. Then export a Midi file from it that I can use in other Apps.

espiegel123

@0tolerance4silence said:

@ExAsperis99 said:
Can we define what we mean by automation?

For instance: I have a synth that is being sent midi from an instance of Atom. As this clip plays back, I manually open and close the filter on the synth. That gesture could not be recorded by Atom2, correct? Or would it be recorded but editing it would not be possible? Would love to see that in the future.

I still vote for No. 1. By a mile.

What you’d like to achieve won’t be possible, even later. Not without lengthy mapping etc. Software synths rarely transmit/generate midi, there is nothing Atom can do about that.

He may have meant opening and closing it via CC event from a controller -- which for me is the critical case. Capturing the CCs generated by the knobs and wheels and sliders on my controllers (and aftertouch, etc)

jblock

Option 1 for sure. People will always want more. From an agile perspective, big releases are more few and far between for many companies. More frequent, smaller releases are the way to go when you don't have an army of devs, or more importantly, QA folks to ensure a big release has all the bugs worked out.

rs2000

@0tolerance4silence said:

@espiegel123 said:

@0tolerance4silence said:

@ExAsperis99 said:
Can we define what we mean by automation?

For instance: I have a synth that is being sent midi from an instance of Atom. As this clip plays back, I manually open and close the filter on the synth. That gesture could not be recorded by Atom2, correct? Or would it be recorded but editing it would not be possible? Would love to see that in the future.

I still vote for No. 1. By a mile.

What you’d like to achieve won’t be possible, even later. Not without lengthy mapping etc. Software synths rarely transmit/generate midi, there is nothing Atom can do about that.

He may have meant opening and closing it via CC event from a controller -- which for me is the critical case. Capturing the CCs generated by the knobs and wheels and sliders on my controllers (and aftertouch, etc)

You are right!
But most of these things can already be done. The whole point is to deliver a complete experience. We have enough half solutions. If dev need to get some weight off his chest 👍 but releasing it too early has its risks.
I think this is a completely different case from f.e LK - open ended development
Atom was built with specific goal, ‘adding missing features’ is not the same as ‘adding new features’ and that will be felt on the user end.

This!

RajahP

For those who want #2.. You can always wait until it is ready.. you don’t have to use this version... unless you already have access to the beta and just want ... well

Anyway.. option #1 please..

Liquidmantis

@jblock said:
Option 1 for sure. People will always want more. From an agile perspective, big releases are more few and far between for many companies. More frequent, smaller releases are the way to go when you don't have an army of devs, or more importantly, QA folks to ensure a big release has all the bugs worked out.

We're in the middle of switching from quarterly releases to weekly. I hear you. I don't feel that the MVP! Iterate! approach is always ideal, but there's always going to be a #2 to work on.

JimP4nsen

I also vote for option 1. I have been waiting for loading MIDI files in for quite some time

And, to emphasize this again, thanks for this brilliant plugin!

ExAsperis99

@espiegel123 said:

@0tolerance4silence said:

@ExAsperis99 said:
Can we define what we mean by automation?

For instance: I have a synth that is being sent midi from an instance of Atom. As this clip plays back, I manually open and close the filter on the synth. That gesture could not be recorded by Atom2, correct? Or would it be recorded but editing it would not be possible? Would love to see that in the future.

I still vote for No. 1. By a mile.

What you’d like to achieve won’t be possible, even later. Not without lengthy mapping etc. Software synths rarely transmit/generate midi, there is nothing Atom can do about that.

He may have meant opening and closing it via CC event from a controller -- which for me is the critical case. Capturing the CCs generated by the knobs and wheels and sliders on my controllers (and aftertouch, etc)

This is what I mean, but I'm surprised this was even in the offing. I'm not looking for Atom2 to edit all the movement of my instruments in the final iteration, but that would be wonderful. (I was always banking on at some point moving the midi or the stems to a DAW for further refinement.)

I really just want a fast and flexible and reliable solution to capturing the songwriting/jamming process within AUM.

espiegel123

@ExAsperis99 said:

@espiegel123 said:

@0tolerance4silence said:

@ExAsperis99 said:
Can we define what we mean by automation?

For instance: I have a synth that is being sent midi from an instance of Atom. As this clip plays back, I manually open and close the filter on the synth. That gesture could not be recorded by Atom2, correct? Or would it be recorded but editing it would not be possible? Would love to see that in the future.

I still vote for No. 1. By a mile.

What you’d like to achieve won’t be possible, even later. Not without lengthy mapping etc. Software synths rarely transmit/generate midi, there is nothing Atom can do about that.

He may have meant opening and closing it via CC event from a controller -- which for me is the critical case. Capturing the CCs generated by the knobs and wheels and sliders on my controllers (and aftertouch, etc)

This is what I mean, but I'm surprised this was even in the offing. I'm not looking for Atom2 to edit all the movement of my instruments in the final iteration, but that would be wonderful. (I was always banking on at some point moving the midi or the stems to a DAW for further refinement.)

I really just want a fast and flexible and reliable solution to capturing the songwriting/jamming process within AUM.

+1

and there is nothing that does that. Photon ALMOST does, but its lack of state saving makes it a pain to use and just enough extra steps to get your recording assigned to a pad and playing back that it feels clunky. ATOM1 is almost there -- except that it doesn't record the MIDI channel info with the incoming notes and doesn't record controllers.

I'd love controller editing when it comes -- but if it is usable sooner than that without it I think that would serve a lot of people's needs. LK is nice as a clip launcher but for a piano roll note editor, I'd choose ATOM -- and LK only handles 4/4.

craftycurate

Option 1 for sure ... it's been quite a wait already, and so releasing gets it out the door, plus gives you more time to get automation sorted without the pressure of everyone waiting for SOMETHING to drop, especially as you set such high standards for yourself.

Jeezs

Don’s understand the dilemma.
If it is release now those who want to buy it can buy now, it those who want to wait can wait. 😀😀
Where is the problem ?

lukesleepwalker

@espiegel123 said:

@ExAsperis99 said:

@espiegel123 said:

@0tolerance4silence said:

@ExAsperis99 said:
Can we define what we mean by automation?

For instance: I have a synth that is being sent midi from an instance of Atom. As this clip plays back, I manually open and close the filter on the synth. That gesture could not be recorded by Atom2, correct? Or would it be recorded but editing it would not be possible? Would love to see that in the future.

I still vote for No. 1. By a mile.

What you’d like to achieve won’t be possible, even later. Not without lengthy mapping etc. Software synths rarely transmit/generate midi, there is nothing Atom can do about that.

He may have meant opening and closing it via CC event from a controller -- which for me is the critical case. Capturing the CCs generated by the knobs and wheels and sliders on my controllers (and aftertouch, etc)

This is what I mean, but I'm surprised this was even in the offing. I'm not looking for Atom2 to edit all the movement of my instruments in the final iteration, but that would be wonderful. (I was always banking on at some point moving the midi or the stems to a DAW for further refinement.)

I really just want a fast and flexible and reliable solution to capturing the songwriting/jamming process within AUM.

+1

and there is nothing that does that. Photon ALMOST does, but its lack of state saving makes it a pain to use and just enough extra steps to get your recording assigned to a pad and playing back that it feels clunky. ATOM1 is almost there -- except that it doesn't record the MIDI channel info with the incoming notes and doesn't record controllers.

I'd love controller editing when it comes -- but if it is usable sooner than that without it I think that would serve a lot of people's needs. LK is nice as a clip launcher but for a piano roll note editor, I'd choose ATOM -- and LK only handles 4/4.

This is why I respectfully disagree with @rs2000 and @0tolerance4silence when they say "most of these things can already be done". I'd say a large market segment exists that simply wants what you describe above.

Fingolfinzz

I’m going to vote option 1. Updates and features being added are always something I generally expect to happen after the first version of an app anyway. People will endlessly ask for features anyway and automation will be awesome but i think the main draw for the app is the piano roll features

Pierre118

@blueveek A consequence of a release now will bring you in the situation that you must also reply at posts that will be placed here in this thread. The community will ask you questions, will post bugs and will ask for features. This will distract you. If you want to focus on the further development of Atom 2, don't release it now. That's a choice you can/must make yourself.

onerez

Hmmmm. so I have been not in the game lately and I’m a dolt... are we saying that version 1 will not let you draw automation for exposed parameters in AUM for example?

RJB

I’ve seen screen grabs for weeks to know I could make good use of this app as is so Option 1 for me.

Outtram

Option 1 please.

If you do option 2 the pressure will be too much!!!

A good update is also like another birthday present 🎁

It’s like your giving two amazing gifts to the community

Or put me onto the Beta list hahaha 🤣

Synthi

@espiegel123 said:

@blueveek said:
@espiegel123 CC.

It would be very annoying to record CC and not be able to edit/delete it (e.g. if a new layer or a different phrase is recorded).

Regarding channels, you can pick whichever channel to output on (there's a new toolbar on the left that was shown in previous screenshots). Atom listens to everything it receives, and filtering input can be done at the host level.

I disagree somewhat. I would strongly recommend an option to be able to record all received information and play it back even if it weren’t editable (other than say maybe select all and moving everything in time).

It is the single biggest hole in the MIDI recording AU world..the ability to simply capture and playback everything that comes in.

Sure there are lots times where one wants to edit the CC stuff...but I’d rather be able to capture and play everything without editing than not have that.

MY vote goes for option 1 BUT with CC recording enabled! you can filter CC if you need to record notes only!
I really miss a AUv3 MIDI recorder capable of recording all MIDI events.
Then later you can finish and add the CC edit feature in a future update. I think thats the best scenario for us users! Thanks for bringing the question to public!

[Deleted User]

The user and all related content has been deleted.

[Deleted User]

The user and all related content has been deleted.

Polyphonix

Clearly and without a doubt option1 please. We can expect an outstanding tool with lots of new features compared to the first version that will immediately advance our AUv3 piano roll workflow tremendously. So why wait? Automation is coming anyway. It's about creating music now! And not to wait for the very last perfectly implemented future feature and the ultimate version, which is per se an utopia because it will never exist, the perfect app. In any case, I'm glad that Imaginando does not make us wait three years with LK and then present their final >I can now (still not) do everything< version. 😉 Victor himself provides the best argument for option 1: “...and this doesn't really affect anything: in the long term we'll arrive at the same thing.”

So guys, be thankful and use the tools he wants to provide you with right now for your benefit.

I don't know why so many here are concerned when it comes to expectations, feature requests and distractions. Victor certainly knows how to deal with them, I'm sure these issues won't present him with any particular challenges. He seems to know pretty well what he wants to achieve with Atom 2. I have full confidence in his abilities and determination. Thank you Victor for your dedicated work and your openness here in the forum!

sloJordan

ya youve def just unleashed like 10 pages worth of battling @blueveek

lukesleepwalker

@sloJordan said:
ya youve def just unleashed like 10 pages worth of battling @blueveek

He's just playin us. He wants to beat the Drambo thread for longest running thread before launch.