Let's see.. one automation event would be under 40 bytes, to be generous. That's 25ish events in 1 kB, not quite 2 quarter beats at 1/64 resolution. A megabyte then contains 25,000 events, which is something like 400 4/4 bars with an automation value for every 64th note... Did my math go wrong somewhere or is there something odd going on? You'd still need hundreds of those to get to this file size.
Matt, can you put the file (preferably from before your edits) somewhere to be examined?
Toby, please ignore my patch #47 in light of this and the vector automation patch a while back.
Citerar Matt Brooks <email@example.com>:--
Thank you for the advice!
I took a look at the file and discovered a massive number of lines for one
automation track. After finding out the name of the track that caused the
problem I began editing the project file, clearing the automation and
rewriting it at a resolution of 32 as opposed to 64. While doing that it
froze and I'm now waiting for it to wake up again (usually this takes about
an hour). If I ever get through the whole automation track I'll let you all
know the resulting file size.
On Dec 11, 2013 2:45 PM, "Tobias Doerffel" <firstname.lastname@example.org>
Probably you're using "too much" of automation, so there's a lot of
automation data in the files (one line/XML-tag per value). You could try to
reduce usage of automation. Alternatively take a look at the file in an
editor and try to find out what uses to much data.
04 00 83 83 95