By CharlesRandolph
Wed Dec 18, 2019 11:35 pm
Frisbi wrote:Yeah but on a new hardware
Why would they do all this and not add it to the existing hardware? Just hold tight and see what happens.
Frisbi wrote:Yeah but on a new hardware
Certified Beatz wrote:So this network midi addition has anyone tried with a different daw.. I could careless about ableton..I'm a Cubase 10.5 user with custom presets I created for efx..
rvense wrote:40Beatz wrote:Each Track Needs a Port Assignment in order for Multi Midi In to work Properly. BUT...being as the way the Current Hardware Routing Structure of only being able to control the Active Track, they would have to Restructure the Chipsets on the I/O Board.
I've taken my Live apart (hw + sw) and I'm a bit of a Linux nerd, so I have a bit more context here than you seem to.
The MIDI "chipset" on the I/O board is a single STM32 microcontroller connected to the main processor via USB and it presents the DINs as two independent MIDI input ports to ALSA, the MIDI system that all Linux applications use. It absolutely is a software/GUI thing. If I connect my Live to my (Linux) computer in controller mode, I see the MIDI ports same as the Live does when it's in standalone, and they're completely independent.
Note that when I say "simple GUI thing", that doesn't mean it needs to be a five minute fix in the context of Akai's application. It probably breaks a lot of the assumptions that their track handling was built on, I don't know their code at all, but it's absolutely not a hardware issue. It's just that they've spent the programmer hours on this Ableton Live controller mode and the new mixer and stuff that came out with the Force instead.40Beatz wrote:Disk Streaming.....IMHO...You still would need some Memory Buffering(hardware) to handle the Large Files streaming from HDD. Right now...I think we're Maxed Out on Internal Memory lol
The Live/X are computers of a very familiar form, it's not some exotic 90's design with many different kinds of memory and complex custom hardware. There's a main processor with 2GB memory and that's it. The OS and MPC application reserve a chunk and the rest (1.3GB on my Live with 2.7[0]) is where your samples go when you load them up. For disk streaming, instead of loading entire files into the memory, you load smaller chunks at a time (so memory usage goes down, not up - that's the whole point). The problem with this is that maybe a lot of the rest of the software was built on assumptions that no longer hold if you start streaming from disk instead of having it all in RAM, but it's not that the processor is incapable of streaming a bit of audio from disk.
[0] I've actually modified the firmware on my Live to run SSH so I can log in and run commands, and that's what the Linux command 'free' outputs
Caustic Yoda wrote:decided to fast track v3. so over the live and lack of proper updates so went for an mpc3000 (so dope), just like my 2500 it makes the live seem like a cheap toy but much more so, over nukai and this system of failed updates, every other sampler i own is better than the live in most ways
vwkountz wrote:Now that they added Network midi is it possible to add code for audio over USB in standalone?


Danoc wrote:No way would l trade the Live for a 3000. I love the fact l can export tracjs explode tracks without doing it manually. Nice touch screen heck no.Folks seem to love the sound, and 1-2 features the Live doesn't have. Agreed, no way I'd trade my Live for a 3000. The furthest I'd go back is a 4000, and I wouldn't even do that, especially since I have a Z4 that I don't eve use.