K Halladay

Just now, John Bradley said:

Track pane, Options | On Stop, Rewind to Now Marker

Ctrl-W toggles that behavior on mine, though I don't know if that's a binding I made, or a default binding everyone has.

BLESS YOU KIND SIR! That's the one.

1 hour ago, Colin Nicholls said:

Transport behavior has been changed slightly in 2019.09 (refer to the manual) but not in this respect.

I just tested this out, and if I press the STOP button in the transport (or press SPACEBAR), the playback position returns to the NOW TIME marker. If during playback, I press the PLAY button, then playback halts (or pauses) and the playback position stops at the current location. Pressing PLAY a second time resumes playback from that position.

I don't think it is possible to re-map the SPACEBAR to a different function.

Can you clarify how you are starting and stopping the transport? Are you using a Control Surface?

Spacebar. Press it to play, press it to stop. Used to go back to original position.

In the past, when starting the transport at, say, measure 30 of a piece, then stopping it some arbitrary time later, say measure 32, the transport position has returned to the original position—back to measure 30, in this case. Now, however, when at start at 30 and stop at 32, the transport remains at 32. Starting the transport again starts from 32. I do not wish this to be the case.

Is there some keyboard shortcut I accidentally pressed that I'm unaware of? Or has this changed since the most recent update? Basically, is this my fault or something else's?

Just noticed this happened to me as well. The SI resources folders are still in the application folder, but the DLLs seem to be gone from everywhere.

Added the LP-64 (from the X2 package) to a bus, and adjusted the input level to ~2 and the output to ~3. Sounds good. Hit CTRL-S and played the track. Seemed quieter. Opened up the plugin: input and output have reset to 0.0. Again set to ~2/~3. Hit CTRL-S with the plugin window open this time, and instantly the levels reset to 0.0.

I've been using this plugin for years, and never has this happened. Something to do with the latest 05/2019 release? Anybody have an idea what's happening?