Yes i agree , Arguru needs to develop Aodix exclusive synths , samplers , etc.. , just give it some time.rokkon wrote:it doesn't have a builed in sampler? right?
that's bad.
IMHO the big advantage of trackers is the builed in sampler and the great way to control it through the sequencer... it makes midi users look like neanderthalers... but a tracker that needs a midi-driven sampler? who needs that?
Aodix 4 Released
-
- KVRer
- 25 posts since 28 Nov, 2004
-
- KVRist
- 133 posts since 19 Jan, 2003
I did, but it just placed the notes one after the another on the same track. Do I have to enable some feature for this? (Or maybe use midi keyboard? I've only tried it with computer keyboard.)Scr1pt3r wrote: Aodix records chords, try it.
-
- KVRist
- 453 posts since 16 Sep, 2002 from Malaga (Spain)
Indeed, a pianoroll implementation is just as easy as add some GUI code (events functionality is already there and it's just a matter of display/gui input), it wouldnt suppose any problem. The problem is really related with the fact of keep aodix application as conceptually simple and polished as possible (along code), being very careful with the features to be implemented and rejecting all features (and suggestions) of users wich leads the app to add too many extra or redundant functionality, increasing code and binary size, etc, like the pianoroll, without the "about" bitmap, the aodix executable compressed with rar is like 90kbytes iirc with no additional dependencies than necessary for run a win32 application.
Despite I agree , u'll be thinking now 'but guys, you're selling a product, it's not freeware, this is not a bit contradictory?' Well, yeah, could sound strange and kind of egoist, but I see it this way: i'm extremelly pleased with the aodix code, very small and clear, everything carefully placed and polished imho (i have to say it's my first app I can say this), then, when you start to add functionality you'll never use and see bloated lines of code here and there, I personally start to lose motivation on it and support extra stuff is painful and very unpleasant. So I preferred going the risky way: stick to something simple that works fine, and make/get the best of it. Yes, u'll not reaching more audience of course, but is better a happy coder + happy code with less money than stressed coder with more cash.
The current interface have the drawback against pianoroll wich is that chords or overlapped events get stacked visually one in top of another (but despite, they're there and working, u can record also and move them to other tracks), but pianoroll have also lot of cons, specially visualizating automation stuff and events that are not note messages (midi cc's, etc), of course all of this is personal point of view, and a lot of ppl wont agree, but hey: what's definitelly not planned in my TODO list for aodix? please to everyone.
...
See ya guys! (ben: can u move this to company forums?, it's getting a bit annoying in main forums hehe)
Despite I agree , u'll be thinking now 'but guys, you're selling a product, it's not freeware, this is not a bit contradictory?' Well, yeah, could sound strange and kind of egoist, but I see it this way: i'm extremelly pleased with the aodix code, very small and clear, everything carefully placed and polished imho (i have to say it's my first app I can say this), then, when you start to add functionality you'll never use and see bloated lines of code here and there, I personally start to lose motivation on it and support extra stuff is painful and very unpleasant. So I preferred going the risky way: stick to something simple that works fine, and make/get the best of it. Yes, u'll not reaching more audience of course, but is better a happy coder + happy code with less money than stressed coder with more cash.
The current interface have the drawback against pianoroll wich is that chords or overlapped events get stacked visually one in top of another (but despite, they're there and working, u can record also and move them to other tracks), but pianoroll have also lot of cons, specially visualizating automation stuff and events that are not note messages (midi cc's, etc), of course all of this is personal point of view, and a lot of ppl wont agree, but hey: what's definitelly not planned in my TODO list for aodix? please to everyone.
Some toys coming!Yes i agree , Arguru needs to develop Aodix exclusive synths , samplers , etc.. , just give it some time.
...
See ya guys! (ben: can u move this to company forums?, it's getting a bit annoying in main forums hehe)
-
- KVRAF
- 1974 posts since 21 Jun, 2002 from Earth
man, I couldn't agree more! Sometimes I think users can really spoil one's original intent and vision... granted, I do wish it had an internal sampler with all the effects, especially 09 offset type stuff... but as VST specific tracker, it's already very nice and unbloated. I look forward to seeing where this goes... been following your tracker efforts for a LONG time arguru! hehehe 
ModuLR / Radio
-
- KVRer
- 25 posts since 28 Nov, 2004
Glad you enjoyed the idea Arguruarguru wrote:Indeed, a pianoroll implementation is just as easy as add some GUI code (events functionality is already there and it's just a matter of display/gui input), it wouldnt suppose any problem. The problem is really related with the fact of keep aodix application as conceptually simple and polished as possible (along code), being very careful with the features to be implemented and rejecting all features (and suggestions) of users wich leads the app to add too many extra or redundant functionality, increasing code and binary size, etc, like the pianoroll, without the "about" bitmap, the aodix executable compressed with rar is like 90kbytes iirc with no additional dependencies than necessary for run a win32 application.
Despite I agree , u'll be thinking now 'but guys, you're selling a product, it's not freeware, this is not a bit contradictory?' Well, yeah, could sound strange and kind of egoist, but I see it this way: i'm extremelly pleased with the aodix code, very small and clear, everything carefully placed and polished imho (i have to say it's my first app I can say this), then, when you start to add functionality you'll never use and see bloated lines of code here and there, I personally start to lose motivation on it and support extra stuff is painful and very unpleasant. So I preferred going the risky way: stick to something simple that works fine, and make/get the best of it. Yes, u'll not reaching more audience of course, but is better a happy coder + happy code with less money than stressed coder with more cash.
The current interface have the drawback against pianoroll wich is that chords or overlapped events get stacked visually one in top of another (but despite, they're there and working, u can record also and move them to other tracks), but pianoroll have also lot of cons, specially visualizating automation stuff and events that are not note messages (midi cc's, etc), of course all of this is personal point of view, and a lot of ppl wont agree, but hey: what's definitelly not planned in my TODO list for aodix? please to everyone.![]()
Some toys coming!Yes i agree , Arguru needs to develop Aodix exclusive synths , samplers , etc.. , just give it some time.
...
See ya guys! (ben: can u move this to company forums?, it's getting a bit annoying in main forums hehe)
-
- KVRist
- Topic Starter
- 243 posts since 20 Aug, 2003
Well, I think Aodix is already released for a week now.
What do you guys think of it so far ?
Honestly I had no time to check it in depth the last week as I been busy in the university.
So... what are the impressions about it so far ?
What do you guys think of it so far ?
Honestly I had no time to check it in depth the last week as I been busy in the university.
So... what are the impressions about it so far ?
-
- KVRAF
- 3528 posts since 18 Apr, 2002 from British Columbia, Canada
glad to see this rolling along. And for those that want a tracker that is lousy with features, they're out there, one that free even, but that is something different from what the point of this one is. And that is just fine. People want every app to support all the same features -- what's the point of that? what would be the point of having different apps then?
Just a thought, and not trying to call anyone out here. Cheerz.
G.
Just a thought, and not trying to call anyone out here. Cheerz.
G.