Slightly dissapointed about tge lack of love for Mixer, but it's a step in right direction!
Forward the video to your friends & family
If you asked me, then it's about time for them to fire the iOS ones and hire Windows/MacOS ones instead to bring up the *actual* Reason up to speed. It's an awesome DAW, but lots of new people who started producing in last 5 years simply won't accept some of the archaic aspects of the GUI and sequencer in particular AND will be alienated by the concept of Rack. iOS/Android apps can be a good, complementary business model but the real money (and users) are in the core software.
Android is not an audio-friendly OS so getting sensible performance out of it is a real chore.antic604 wrote: ↑27 Mar 2019If you asked me, then it's about time for them to fire the iOS ones and hire Windows/MacOS ones instead to bring up the *actual* Reason up to speed. It's an awesome DAW, but lots of new people who started producing in last 5 years simply won't accept some of the archaic aspects of the GUI and sequencer in particular AND will be alienated by the concept of Rack. iOS/Android apps can be a good, complementary business model but the real money (and users) are in the core software.
How did you test this? Or are you repeating something you heard about Android 3? Android's round-trip audio latency is now better than 20 ms. So it's fine for monitoring while recording. But that's hardly what a DAW is used for anyway. Most of the work is sequencing and playback, which has no real latency requirements at all.
To be fair, latency very much does affect the experience in this case. I know on the iPhone at least, when I choose 128 samples in Korg Gadget, the resulting lower latency is almost hardware-like when I use MIDI controllers or the touch screen. If I increase the sample buffer to 2048, the increased latency is noticeable even on the touch screen when playing back percussive stuff. Trying the stay in sync with the sequencer when recording is almost impossible. And using a MIDI controller only makes it worse (especially over Bluetooth, which has its own latency issues).ScuzzyEye wrote: ↑27 Mar 2019How did you test this? Or are you repeating something you heard about Android 3? Android's round-trip audio latency is now better than 20 ms. So it's fine for monitoring while recording. But that's hardly what a DAW is used for anyway. Most of the work is sequencing and playback, which has no real latency requirements at all.
Android is fine. Just no one really wants to use a DAW on their phone. Google is down-playing Android on tablets at this point, and focusing their efforts on Chrome OS. So maybe the web-DAW isn't a bad idea.
Touch to audio output is around 9 to 12 ms depending on the device. I've been meaning to test the USB and Bluetooth MIDI latency, but haven't gotten around to it. Android devices can actually show up as MIDI controllers when plugged into a computer, if an app activates that mode. That's what TouchDAW does.EnochLight wrote: ↑27 Mar 2019To be fair, latency very much does affect the experience in this case. I know on the iPhone at least, when I choose 128 samples in Korg Gadget, the resulting lower latency is almost hardware-like when I use MIDI controllers or the touch screen. If I increase the sample buffer to 2048, the increased latency is noticeable even on the touch screen when playing back percussive stuff. Trying the stay in sync with the sequencer when recording is almost impossible. And using a MIDI controller only makes it worse (especially over Bluetooth, which has its own latency issues).
20ms round trip latency isn't terrible I suppose, but I wonder what that would translate to when performing live or recording to a sequencer via a touchscreen or MIDI controller?
I know this is part of the issue. Android has literally dozens upon dozens of different hardware configurations to run on, so I'm curious if the performance you're reporting is the same for all devices?
Different touch encoders have their own latencies. Any recent device from Samsung, LG, and Google will have excellent latency from the touch to the OS. $50 Chinese phones, not always so much. But you can tell that pretty easily when dragging to scroll up and down. On my Pixel 2, which has almost no touch latency, it feels like what ever you're scrolling is locked to your finger. Those cheap phones it feels like the screen is attached by a rubber band.EnochLight wrote: ↑27 Mar 2019I know this is part of the issue. Android has literally dozens upon dozens of different hardware configurations to run on, so I'm curious if the performance you're reporting is the same for all devices?
Because I've developed audio apps for iOS and Android. It's not the latency that's the issue. It's the consistency of the delays. Sometimes the OS does other stuff and interrupts the audio stream. The very latest flavours of Android have made big leaps forward but they are far from perfect and you can't develop an Android app that just targets the very latest flavour of Android because you limit your market. iOS on the other hand, in common with almost all Apple platforms, is very stable and predictable for audio and other real-time stuff. It's no coincidence that the coolest audio apps are only on iOS.
Beats me if I know the solution!EnochLight wrote: ↑27 Mar 2019
Well, since the rack is a critical part of the Reason paradigm, then there's really no way to address that without becoming like every other DAW. I feel you on the graphics/GUI/UX though (4K/high dpi please)!
Well, YOU don't know because YOU've been using it for years, I assume. But whenever I post something from Reason on a non-Reason forum/group, especially with a video, then I typically get comments like "it looks scary", "it looks confusing" or "how can you do anything there" and I can believe it is for a 20-something who never had to wire hardware devices. Most people don't get signal flow in their DAWs, let alone would want to control it.guitfnky wrote: ↑27 Mar 2019I don’t get why anyone would be put off by using the rack. you can just add everything in series if you want, and shift-drag stuff around if you want to easily reorder things. you don’t need to flip the rack most of the time for that.
sure, there’s a learning period where you might have to adapt to it being different than other DAWs, but that doesn’t take long. the beauty of the rack is that it’s as simple, or as complex as you want it to be.
The bizarre thing is, if the resurgence of hardware popularity and the modular world is anything to go by, IRL hardware isn't going anywhere anytime soon, and Reason is literally the only DAW on the market that can prepare said 20-somethings for operating IRL, especially in a studio environment where racks are commonplace. Hell, even many hobbyist/enthusiasts out there have racks of hardware in their home studios.antic604 wrote: ↑27 Mar 2019Well, YOU don't know because YOU've been using it for years, I assume. But whenever I post something from Reason on a non-Reason forum/group, especially with a video, then I typically get comments like "it looks scary", "it looks confusing" or "how can you do anything there" and I can believe it is for a 20-something who never had to wire hardware devices. Most people don't get signal flow in their DAWs, let alone would want to control it.guitfnky wrote: ↑27 Mar 2019I don’t get why anyone would be put off by using the rack. you can just add everything in series if you want, and shift-drag stuff around if you want to easily reorder things. you don’t need to flip the rack most of the time for that.
sure, there’s a learning period where you might have to adapt to it being different than other DAWs, but that doesn’t take long. the beauty of the rack is that it’s as simple, or as complex as you want it to be.
So perhaps there should be some "easy" mode, with lots of things abstracted and "advanced" one that we have now? I've no clue, just thinking out loud
Ditto with my 14 year old. And now he regularly records his middle school bandmates using my old Spirit F1 mixer and Delta 44 for guitars and bass, and midi for his Alesis drumkit. As soon as you have to use hardware, Reason makes sense. But I appreciate there's a ton of kids out there who haven't had that pleasure.EnochLight wrote: ↑27 Mar 2019
My 11 year old uses Reason, and she seems to have grasped it pretty well without much fuss, but I did spend a hot minute showing her the back of an actual piece of hardware and where the inputs/outputs are.
Users browsing this forum: Trendiction [Bot] and 35 guests