workaround for Live's 2gb clip size limit in Windows
Posted: Tue Sep 12, 2006 9:05 am
After chatting w/ the team in Germany, they agree that Live fails when manipulating clips at 2gb and larger. (In all fairness, this is a problem in the specification for WAV files and a problem deep-down in Windows' file I/O that Ableton would need to workaround). I found this when I was trying to record tracks for a 5 hour live performance. All my tests before the performance would fail. So I ended up using Audacity just to get by. It only let me record two tracks. But it gets around the size problem by saving the data in many many 1mb files which is knows how to reconstruct with a metafile.
But I'd like to move to Live to be able to full access my ASIO hardware and record more than two tracks. So...what workarounds might I find? So far, I've thought of two. In both, I would have multiple audio tracks setup with inputs coming from my external ASIO audio bus.
1) arm all the tracks. Launch the 1st scene which will start all the track recording. Depending on the sample rate/depth, have a human launch the next scene. I assume Live will cleanly capture up to the quantization in the current scene's clips and then start capturing the very next bit into the new scene.
2) use a tool, maybe midiox, to send midi signals to Live. Have specific midi signals setup for scene 1, 2, 3, etc. Write a script using midiox's COM interface and have the script delay the needed number of minutes before launching the next scene by sending the next midi sequence.
1 needs babysitting by a human. Good to watch for problems. Bad for causing problems.
2 is a hack-o-riffic idea and untested. All that automation might be full of bugs and exceptions cases.
Ideas? Comments? Other workarounds?
But I'd like to move to Live to be able to full access my ASIO hardware and record more than two tracks. So...what workarounds might I find? So far, I've thought of two. In both, I would have multiple audio tracks setup with inputs coming from my external ASIO audio bus.
1) arm all the tracks. Launch the 1st scene which will start all the track recording. Depending on the sample rate/depth, have a human launch the next scene. I assume Live will cleanly capture up to the quantization in the current scene's clips and then start capturing the very next bit into the new scene.
2) use a tool, maybe midiox, to send midi signals to Live. Have specific midi signals setup for scene 1, 2, 3, etc. Write a script using midiox's COM interface and have the script delay the needed number of minutes before launching the next scene by sending the next midi sequence.
1 needs babysitting by a human. Good to watch for problems. Bad for causing problems.
2 is a hack-o-riffic idea and untested. All that automation might be full of bugs and exceptions cases.
Ideas? Comments? Other workarounds?