image description


Locating in Studio One 2.6.2 is slow?
  Forum Index » Studio One Forum Community Support 
Author
Message
admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

I don't know if this is normal behaviour or not, but in any project, clicking to change the cursor position is laggy. There's an annoying delay between clicking the mouse and the playback cursor moving.

Using the 'Locate Mouse Cursor' key has less lag, but it's still slightly laggy. If I hold the key down, then I can swipe the playback cursor to any location instantly.

Is this common? Is it a known issue? Any fixes?

edit: I found this thread http://forumsarchive.presonus.com/posts/list/25949.page showing that it is intentional for clicking in an empty space, however there still is a lag if I cmd/ctrl-click or use the 'Locate Mouse Cursor' function.

This message was edited 3 times. Last update was at 22/06/2014 03:26:10

Kiwicomposer
Presonic
[Avatar]

Joined: 02/12/2011 15:38:39
Messages: 284
Location: Wellington, New Zealand
Offline

Interesting.. Just tried it in a couple of songs..
No noticeable lag here. Instantaneous action really.
I am on a MAC and it has SSD drive not a Trad HDD used Command Space to Locate Mouse Cursor at at Mouse position.

I put the mouse 20 or 30 bars away from the playback cursor hit the CMD + Spacebar combo and bam it is there.

Is the song full of tracks alap 100 tracks or something?
Have you done a recent save or is it after a lot of editing?
Try clearing the cache and see what happens?

Sorry cant seem to reproduce any lag on moving the cursor.

Steve Currington
de Composer
Wellington, New Zealand
Twitter: @kiwicomposer
Facebook: kiwicomposer
SkypeID: kiwicomposer
----------------------------------------

Primary Hardware: Presonus Studio One v2.6.2, Presonus Audiobox1818vsl, Presonus Audiobox USB, Presonus Faderport, Focusrite Liquid Saffire 56, MOTU Traveler Mk3, TC-Helicon VoiceworksPlus, FMR RNC, FMR RNLA, Axiom Pro 49 Keyboard, other sundry hardware, numerous mics, audio plugins and instruments.
Primary Software: Sibelius v7.x, Notion v4.x, Logic Studio. V9.x., Melodyne Editor.

Running on iMac's and MacBookAir with OSX 10.9.x Mavericks

admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

Kiwicomposer wrote:Interesting.. Just tried it in a couple of songs..
No noticeable lag here. Instantaneous action really.
I am on a MAC and it has SSD drive not a Trad HDD used Command Space to Locate Mouse Cursor at at Mouse position.

I put the mouse 20 or 30 bars away from the playback cursor hit the CMD + Spacebar combo and bam it is there.

Is the song full of tracks alap 100 tracks or something?
Have you done a recent save or is it after a lot of editing?
Try clearing the cache and see what happens?

Sorry cant seem to reproduce any lag on moving the cursor.



New project, single track, no events. No plugins. Studio One 2.6.2 on OS X 10.9.3.

Can you tell me if cmd-clicking is laggy for you or not? That shows the same behaviour as clicking an empty space.

This message was edited 1 time. Last update was at 22/06/2014 18:56:51

musician2373
Prenoob
[Avatar]

Joined: 04/11/2013 22:45:18
Messages: 44
Location: México
Offline



admiralbumblebee wrote:New project, single track, no events. No plugins. Studio One 2.6.2 on OS X 10.9.3.

Can you tell me if cmd-clicking is laggy for you or not? That shows the same behaviour as clicking and empty space.


I just did that not laggy at all, same version of Studio One same OS.
--------------------Luis Aguilar---------------------------

Studio One 2.6 Professional---Studio Live 16.4.2---Studio Channel---Eureka (2)---Audio Technica ATH M50 (2)---Audio Technica AT4040 (2)---CAD Trion 8000---Audio Technica AT2020 (2)---AKG K701---Sony MDR 7506---Rode NT1-A---Windows 7 Home Premium i7 Processor 2.80GHz,16GB 64 Bit---Waves---FabFilter---Nomad Factory---UAD-2 Solo Card---Sonar X3 Producer---Cubase 6.5 Artist---Logic Pro X---Macbook Pro i5 16 Gb---FaderPort---Ozone 5---Shure SM7B---Eris E8---Pro Tools Express---Fast Track Solo.
dr4kan
Presonic
[Avatar]

Joined: 25/08/2013 13:40:40
Messages: 590
Offline

not laggy here as well (same OS and S1 versions)
System: Mac i7, 16 GB ram, 2 x SSD Samsung 840 Pro 256 GB + 1 x SSD Samsung 840 Pro 512 GB + 2 X 2TB HDD (backup), OSX 10.8.4

Hardware: 2xMr816X, 2x896mk3, Ultralite, Adam A7X, CC121, MCU
admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

I just tried in windows 8.1 on the same computer and ctrl-click is instant.

I would really love to track this issue down
JoseDrums
Prenoob

Joined: 29/05/2011 04:26:21
Messages: 55
Offline

Perhaps you are just running low on CPU?
My S1 starts acting up like that when I am running low...

Try closing the file you have open and opening up a fresh project page and hit play. See if everything is fine
HP Pavilion HPE Series
Studio One Pro 2
StudioLive 16.4.2
Yamaha StagePas 300 Speakers
Midi Keyboards
Multiple Guitars
admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

JoseDrums wrote:Perhaps you are just running low on CPU?
My S1 starts acting up like that when I am running low...

Try closing the file you have open and opening up a fresh project page and hit play. See if everything is fine


After I tried it in windows I did that from a fresh restart, no other applications opened, brand new project. Cmd-click still lags, Locate Mouse Cursor still lags, but slightly less.

I'm going to go try it on some of my other computers now.
FinalSaga
Presonic
[Avatar]

Joined: 29/07/2012 06:08:06
Messages: 308
Location: Denmark
Offline

Hey Admiral

Somtimes when the latency is set quite high, it does tend to lag from hitting start 'till it plays - say 2048 or more
Would you mind checking if you have the right audio driver selected?
Just something I remembered from way back - Happens alot when using 'windows audio'

Ch33rs
Saga

This message was edited 1 time. Last update was at 22/06/2014 19:37:48

LMike
Baconator
[Avatar]

Joined: 19/02/2011 12:02:34
Messages: 8233
Offline

I think it has to do with the track type you click on. Some tracks perform actions on double click like adding an audio part or a midi clip so it has to pause to make sure it's not a double click (I think).

Make one audio track, one midi track and one automation track and locate on each of them in succession. You'll see the audio and midi track locates being slower due to (I presume) the above.
Studio One Tips For Newbs

"So.... Bitwig. I wonder what's queued up next in line on the drama list?"
admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

FinalSaga wrote:Hey Admiral

Somtimes when the latency is set quite high, it does tend to lag from hitting start 'till it plays - say 2048 or more
Would you mind checking if you have the right audio driver selected?
Just something I remembered from way back - Happens alot when using 'windows audio'

Ch33rs
Saga


That is a good thought. I do have the correct driver selected, and the buffer is set to 32ms. I will try some other audio interfaces and buffers sizes.

I also tested on a 2011 MacBook pro (i7, 8gb) and a 2010 mac mini. The MacBook pro has the cmd-click lag and the mac mini does not. The MBP is a fresh clean install of OS X and the mini is a 4 year old installation. Both tests were with os x 10.9.3, S1 2.6.2 and onboard audio.
admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

When you guys test this, are you cmd-clicking on an event? That seems to be when it lags the worst.

If I cmd-click an empty space then it is not that bad, but if I cmd-click an event then it is quite slow. This applies to ALL the systems I've tested in OS X. (ignore the previous message, since I didn't recognize this difference yet)
LMike
Baconator
[Avatar]

Joined: 19/02/2011 12:02:34
Messages: 8233
Offline

Same reason (imo). Double clicking an event opens the editor so it has to pause to make sure you want to locate, and not open the editor.

Edit: Just for kicks, I went into the Windows Control Panel and changed the mouse double click speed to as fast as it can go, tried locating in S1 with CTRL over an event, then set double click as slow as it can be set, and did the same. I can see the difference. Maybe you should increase your mouse double click speed.

This message was edited 1 time. Last update was at 23/06/2014 00:24:11

Studio One Tips For Newbs

"So.... Bitwig. I wonder what's queued up next in line on the drama list?"
admiralbumblebee
Prenoob

Joined: 27/04/2013 20:57:21
Messages: 15
Offline

LMike wrote:Same reason (imo). Double clicking an event opens the editor so it has to pause to make sure you want to locate, and not open the editor.

Edit: Just for kicks, I went into the Windows Control Panel and changed the mouse double click speed to as fast as it can go, tried locating in S1 with CTRL over an event, then set double click as slow as it can be set, and did the same. I can see the difference. Maybe you should increase your mouse double click speed.



Cmd/ctrl-double-clicking doesn't do anything different from simply double clicking, so ideally there shouldn't be a delay to wait for a second click when command/ctrl is held.

That makes sense however, and I guess that this is intended behaviour. It's still bothersome to have to wait for clicks on events when every other daw I've used is instant (and doesn't require a modifier key to be held).

FWIW in OS X my double click speed is set to the fastest setting. It has been this whole time and is like that on all my machines.

Thank you for looking into this.

This message was edited 1 time. Last update was at 23/06/2014 02:18:08

 
Forum Index » Studio One Forum Community Support
Go to: