I’m coming from years of use of Izoptope Rx so I’m having to equate tasks that I do in RX and relate it to SL11 Pro. Is there a way to export files after working on them and have the meta data follow? I can see the meta data in the meta data project file menu but when I export everything starts at 0, and doesn’t have the true start time. I’m used to pulling a file into RX Advanced, stand alone, work on it and then export the file with the original meta data. It’s important as I’m working for video editors and the meta data has to be available. I couldn’t see a way to do this. I’m still learning SL11 Pro so any videos or tutorials you can point me to would be appreciated!
So what happens when you save the actual project file (in slp format)?
Are you saying that the meta data erases when exported? Can you explain your scenario a little more? When you export your data then where are you importing it to?
Here is a typical scenario. I record sound on location for an example a documentary interview. One channel will be the lav mic, the other the boom mic. Time code will be time of day. So let’s say 13:20:25:11. The boom mic picks up more room noise so I want to take it into SL11Pro to reduce the noise. Whether I import the file or simply drag it in, the transport counter always has all zeros for the session start. Not 13:20:25:11. If I start a new project the meta data is shown in the meta data window under the project menu. The time stamp was there but not accurate. I had to edit the time stamp. If I simply drag the file into SLP there is no meta data at all shown.
If I export the file either as a Wav file or a slp file the result is always the same. All zeros for the session start.
For my work flow I need the original time code to follow from the original file into SLP, and back out to an exported file. The noise reduced file might be sent to a video editor who needs to replace the noisey file with the improved one. To efficiently do that, the time code has to match the original file. I’m using SLP as a stand alone program, not round tripping from a DAW.
Well I hear “ARA” is supposed to deal with this, however I also hear a lot of bugs and instability issues with “ARA”. Then again I have no idea what other application you’re using Spectralayers with.
I can confirm that I have experienced some timecode issues (in-regards to start times). However it wouldn’t be fair to make a commentary about that without given a clear cut example for the developer to reproduce so the developer can patch it (as I myself dont remember specifically exactly what it was I was doing at the time to get those timecode bugs).
My advice is post your example here (audio examples along with pictures) and be as specific as possible so the developer can reproduce the error and fix it for the next patch.
The thing is in RX you can just “save” and that means printing all your changes to the very audio file you are working on. So it keeps everything that hasn’t changed (i.e. the timecode) the same.
There is no such thing in SL, you can only “export” a new file from your session, so we need an option to “port original file metadata into export” to be able to do what Bernie is asking.
In my opinion this is a very needed feature. ARA is very unreliable and near impossible to work with at the moment.
What Bernie says!
I also work as a sound recordist and want to be able to work with the great-sounding Voice Denoised on recorded Poly Wave files.
For starters, how about an option in SL11 to leave the meta data alone and just process the audio. That would be a great option.
As of now, SL strips ALL meta data from processed sound files.
Actually, stripping the sound file of all meta data should be optional.
Cheers
Frederick
To ever really compete with Izotope RX, this time code situation needs to be figured out. A work around would be to export the file after processing in SL, then edit the metadata in WaveAgent and resave it with the edited meta data. Clunky, but not terribly time consuming. In RX I never alter the original file, I export the noise reduced file with the same name as the original plus _CU. This gives the video editor the noise reduced file, original name from the field recorder plus the _CU which indicates the file has been “cleaned up” or noise reduced. Its a good set of tools, but the lack of time code support is a serious omission if its meant to be used as a standalone application.
Joey, thanks for your reply. ARA works within the DAW of choice. I’m using SL as a standalone application. As for posting examples etc., my typical use description describes exactly what needs to happen. I’m sure there are other recordists/post audio folks on here with the same issue.
You’re right!
I’ve been using Spectralayers since the first early release and from my observation(from the early versions till now 11) I believe the main developer @Robin_Lobel mostly viewed Spectralayers as an application for audio restoration and nothing more. Don’t get me wrong, @Robin_Lobel is a talented developer but I believe @Robin_Lobel got a little short-sighted when it comes to this type of stuff(Time code meta data). I can’t speak for anyone (I’m only assuming) but sometimes when you’re under contract to do yearly releases and updates, the main focus starts becoming “let’s add features” and less about “how is what we are doing actually helping people and how are what we are doing is benefiting people”.
I had suggested for an official image format for audio because I had ran into a situation where (during covid where everyone was quarantined and couldn’t have no more than 3 people in one room) I had to send high quality multi-track files to a client and the files exceeded well over 10 GBs, and I had to send those files using only my cell phone data plan (meaning no high speed broadband network) and it was a horrible experience. The reason why I bring this experience up is because there are problems that need to be solved and sometimes when you get complacent you stop thinking long-term and solving problems no longer becomes the priority. I also use that example to make the point that sometimes you can become narrow-minded/complacent to the point where you’re not aware that hollywood producers(like Pixar, Paramount) are using your application to create new blockbuster films and are not having pleasant desirable experiences, and those things not only ruin your reputation but the company’s(Steinberg’s) reputation.
My advice to Steinberg is to do some self-assessment on Spectralayers and take a break from these yearly releases (because it will ruin your reputation if it continues). If you(Steinberg) know ARA is a problem and you know people are having trouble with ARA, then the best thing to do is to make sure that your customers have a good experience with ARA, otherwise people arent going to talk highly of ARA and they’re not going to use ARA and they’re going to use something else that does work.
Request noted !
@Robin_Lobel
thanks for the comms on your fantastic software =-D
From my standpoint, it is greatly appreciated that you wade in and personally address your user base