Timestretch in the project page?

[andgar]

None of the usual timestretch options from the song page seen to available in the project page. Does anyone know if it can be done within a mastering session? I just want to slow a song down a few BPM. I can do it via Izotope RX, but would prefer to stay in S1 if possible

 

[SwitchBack]

The Project page allows you to work directly with audiofiles if you must, but ideally your project consists of links to Songs. If you want to do something like timestretching then you do it in the Song, and then the Project will update to the new version of that Song.

 

[Dave71]

As mentioned above, time stretching is not part of mastering. The project page assumes that your mix is done, the song is done, all that is needed now is to optimize it for radio or streaming, and enhance the sound if needed. This is the stage where you utilize more resource heavy plugins for example, which you can't use while mixing because it takes too much CPU power. So to summarize: Song page is to finish the song, project page is to enhance the final result.

 

[andgar]

Thanks all. But they project page is also great for mastering other people's songs that weren't necessarily made in S1! I know it's not a common mastering move, but it is considered part of the general mastering toolbox and it's strange that S1 clearly has the capability but it's not available in the project page.

 

[SwitchBack]

Trying to avoid any "this should be in that toolbox" discussions let's think solutions. In this case you can put that other person's song in a Song, and then in your Project link to that Song. You may even be able to do your mastering in the Song as it's just a single track. This has 'template' written all over it, me thinks

 

[lokeyfly]

As mentioned above, time stretching is not part of mastering. The project page assumes that your mix is done, the song is done, all that is needed now is to optimize it for radio or streaming, and enhance the sound if needed. This is the stage where you utilize more resource heavy plugins for example, which you can't use while mixing because it takes too much CPU power. So to summarize: Song page is to finish the song, project page is to enhance the final result.

Hi Dave, I would echo what SwitchBack says. Yes, You are correct in that mastering assumes the song(s) is/are done. However, with Studio One, it does not. And while heavy plugin lifting can be performed at this level, any overall editing aside from clip gain adjustment needs to be edited back at the song level. Is what it is. It would be a nice adjustment. Only it sort of breaks the barriers of having to refer back to such an extreme kind of edit.

I guess the argument could be "well doesn't clip gain also stray from having to go back?"

It does, but not as drastically. Stretch ability in the project page could be a reasonable FR, I guess.

I think it was the developers intent to keep songs and projects separate but able to refer back entities. That truly does not convolute what was edited, and where edited? Its a good system that works well.