Question

according to the manual Studio One records BWF wave files with timestamps

I'd like to have functions to be applied to a selected audio event (one, or more, or all audio events selected):

"move selected events to original time stamp"

"assign user time stamp to selected events" (based on the current position in the time line)

and

"move selected events to user time stamp"

and of course the rendered, bounced and exported files should retain the original and user timestamps

Answer 1

Thank you for the feature request. 

If anyone else agrees or disagrees, then please vote it up, or down. 

To vote:

In agreement click on the thumbs up.

In disagreement click on the thumbs down.

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. 

Just viewing and agreeing but not clicking on the vote does not help the issue. 

Please click on one or the other. 

Answer 2

"move selected events to original time stamp"

Edit > Move to Origin

Answer 3

Me too!

Trying to re-mix / apply quality mics to a video file with camera built-in mic is TEDIOUS. Setting the clocks on all devices before a session and then being able to use that to find the neighborhood of where the video audio sync track lines up to my quality Studio One audio tracks, would save me, literally, hours, in some cases.

I'm sure others have found a better workflow (and have full-featured video editing software), but I'm an audio-focused person trying to do a little video. I want to set up my live session multi-tracks with the actual date/time-stamp at which they were recorded, then I can import a temp sync-track exported from the video camera, set my start/end markers for the song/event mixdown, and create a remastered replacement audio mixdown and then paste that into my Quicktime video file. Without time stamps, I have a pro singer who's got her delivery so good (consistent from take to take), I'm dragging the sync track around looking for a match and it's literally fake-synced like a chorus on the wrong take, for like 60seconds straight, before I realize a little pop here or there is telling me its not the same timeframe.