Sequencer..SNG File too large...problem
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Sequencer..SNG File too large...problem
Hello friends, I have a problem while using sequencer in triton extreme. whenever i save my song in SNG or whatever type the file become too large.I have tried to save SNG file even before I start playing any thing ( Blank tracks) it started with 11k , and become around 30 k after recording 6 or 7 measures, and after 60 or 70 measures ..NOT ENOUGH MEMORY appear...I'm in problem , please help....
-
- Platinum Member
- Posts: 2206
- Joined: Wed May 31, 2006 11:56 pm
- Location: Vienna, Virginia, USA
- Contact:
The only thing I can think of is that you might be recording at a very high speed and filling 3 or 4 measures with notes where you might normally expect 1 measure to play, or that you are playing into several tracks at once rather than the expected one at a time.
Also, sequencer memory is determined by the number of events, which can include controller data, so make sure that there's not some issue with one of your controllers like expression, sending out a fairly dense data stream (lots of events) with no sound to show for it.
The trouble-shoot for this is to look at your .sng file (you can save it as a .mid standard MIDI file) in a sequencer on a computer to see just what is being recorded and where the extra data is being generated and what it does. Most sequencers will allow you to "thin" the data -- you might be able to use 3 or 4 points for a CC volume track where 300 control point changes (events) had been recorded by your initial sequencing pass.
BB
Also, sequencer memory is determined by the number of events, which can include controller data, so make sure that there's not some issue with one of your controllers like expression, sending out a fairly dense data stream (lots of events) with no sound to show for it.
The trouble-shoot for this is to look at your .sng file (you can save it as a .mid standard MIDI file) in a sequencer on a computer to see just what is being recorded and where the extra data is being generated and what it does. Most sequencers will allow you to "thin" the data -- you might be able to use 3 or 4 points for a CC volume track where 300 control point changes (events) had been recorded by your initial sequencing pass.
BB
billbaker
Triton Extreme 88, Triton Classic Pro, Trinity V3 Pro
+E-mu, Alesis, Korg, Kawai, Yamaha, Line-6, TC Elecronics, Behringer, Lexicon...
Triton Extreme 88, Triton Classic Pro, Trinity V3 Pro
+E-mu, Alesis, Korg, Kawai, Yamaha, Line-6, TC Elecronics, Behringer, Lexicon...
-
- Platinum Member
- Posts: 7860
- Joined: Fri Jul 29, 2011 7:23 am
yes, i use midi out to control vsti.however i have disconect it since the problem appear. but i still have same problem.
"Also, sequencer memory is determined by the number of events, which can include controller data, so make sure that there's not some issue with one of your controllers like expression, sending out a fairly dense data stream (lots of events) with no sound to show for it. "
would you please tell me to solve the above
"Also, sequencer memory is determined by the number of events, which can include controller data, so make sure that there's not some issue with one of your controllers like expression, sending out a fairly dense data stream (lots of events) with no sound to show for it. "
would you please tell me to solve the above