That buffer setting has nothing at all to do with the length of your recording! Essentially, the buffer is the number of samples that the software holds in its internal memory in order to ensure that recording and playback of audio can be smooth and uninterrupted. (That is rather a simplification of the process, but I think you get the idea!)
As to why your recording stops after about 2 minutes, I think we need to be told an awful lot more about your computer (OS, processor, HDD space), about the precise version of Samplitude you're running, exactly how you are setting up the recording session and does the "stop" always occur at the same time stamp?
Any advice/ideas to offer will also need to come from a Samplitude user, I think!
The computer is a asus laptop with amd 10 core processor, windows 10, 8gb ram, 1 tb hd, running focusrite scarlett 212.
I set up the recording as custom 16 track 5 minute length.
Perhaps I started the timer accidentally? I farted around recording some more guitar with vandall and it seemed to work pretty well.....BUT.... when i stopp recording...i get a error message saying it encountered a asio error?????????
i get a error message saying it encountered a asio error?????????
Sometimes when working at lower latency, Samplitude flags up Asio errors commonly known as LABs (Lost Asio buffers). If you get 1 or 2 it's probably not a problem unless you can hear some glitches in the playback. It's when you start getting 20 or 30 or more that you need to check your computer settings to see if it's optimised for audio recording. If you run latency monitor software it will tell you how capable your computer is of recording audio. Get it here : http://www.resplendence.com/latencymon
One other thing worth noting is that some Focusrite interfaces can be problematic with Samplitude. Apparently there is a newer driver which improves the situation so it might be worth looking into that if you have problems.