Spectral edit does not work unless item is split...! (FIXED)

[Fabian]

I have an item with several spectral edits for de-essing. One of those spectral edits does not work unless I split the item somewhere in front of it.

Two licecaps below. The top one shows the non-functional version. As you can se, rotating the gain does not affect the audio, even though the spectral edit display indicates that the chosen frequencies are adjusted. The bottom licecap shows the same scenario after I have split the item at the previous beat. Now we see that the spectral edit indeed affects both the display and the audio.





Again, the only difference between the top and bottom gif is that for the bottom gif I have split the item 372 ms before the start of the time selection.

In general, spectral edits is such a great idea, sadly underdeveloped for now, but surely this must be a real bug, right?

EDIT: Just to be clear, if I heal the split item, that spectral edit again does not work. And if I split the item again, the spectral edit works again. This is reproducible.

[Fabian]

Apparently only me stumbled on this issue...

I tried to replicate the problem, and I managed!

Here https://chalmersuniversity.box.com/s...b125t6eard.zip is a 130 kB zip file with a project that includes a small pink noise item with two spectral edits. The first one works as expected, but the second one does not work unless the item is split before it, like at 1.1.50.

Can there be only one spectral edit per item?
Or is this a bug?

I hope it is not a trivial pilot error, so if anyone could check this, I would be grateful.

[valy]

I got the same result as you with your project.

But then I created a new project and imported a random audio file. I was able to successfully create two consecutive spectral edits in the same item. So it seems there is something with your project settings, although I can't imagine what?

[Fabian]

Originally Posted by valy

I got the same result as you with your project.

But then I created a new project and imported a random audio file. I was able to successfully create two consecutive spectral edits in the same item. So it seems there is something with your project settings, although I can't imagine what?

Thanks for testing and confirming.

I've been experimenting more...

Could you maybe try to place the item slightly to the right off grid and then to drag the left side of the item to the nearest grid line. Then put two spectra edits there. Do both work in that case?

Thanks

EDIT: This definitely has something to do with the item not starting on the grid and/or being extended to the left. In the project linked to above, if I drag the item left edge to where the small triangle whatever-it-is-called is, the second spectral edit works! If I drag the left edge back to the left, the second spectral edit stops working. And this working/not-working happens as I drag the edge back and forth while the project plays and loops over the second spectral edit.

Surely this is a real bug.

[Fabian]

Here it shows. If I drag the left edge of the item to the left, the second spectral edit stops working.



In the gif above, the project plays and loops over the second spectral edit. Initially this one works as we can see in the ReaEQ graph. Then I drag the left edge out just a little bit, and at one point the spectral edit stops working. Agan, the ReaEQ graph shows this, but note that the spectral view in the spectral view in the item looks the same as when the edit is not working. And then I drag the left edge back and forth, and the spectral edit consistently stops and starts to work. This is fully replicable.

[Justin]

Thanks, fixing!

[Fabian]

Originally Posted by Justin

Thanks, fixing!

Great! Thanks.

While you're giving spectral edits some love, could you please, please let us copy/paste spectral edits. That would improve this already very useful feature so much. Thanks.

[valy]

Originally Posted by Fabian

Great! Thanks.

While you're giving spectral edits some love, could you please, please let us copy/paste spectral edits. That would improve this already very useful feature so much. Thanks.

Seconded...or maybe a "spectral-edit item" akin to automation items so we can drag 'em around

[Fabian]

Originally Posted by valy

Seconded...or maybe a "spectral-edit item" akin to automation items so we can drag 'em around

Well, we can already drag them around within an item (or rather, take), so being able to copy/paste between takes would solve the most urgent issues, I think.

But yes... being able to save and recall spectral edits like automation items would be great, of course. And with some API calls so we can invent some clever stuff of our own on top of it.

[valy]

Originally Posted by Fabian

Well, we can already drag them around within an item (or rather, take), so being able to copy/paste between takes would solve the most urgent issues, I think.

But yes... being able to save and recall spectral edits like automation items would be great, of course. And with some API calls so we can invent some clever stuff of our own on top of it.

I'd take whatever I could get, yeah. Being able to use the Media Bay with them would be nice.

[Meo-Ada Mespotine]

Originally Posted by Fabian

But yes... being able to save and recall spectral edits like automation items would be great, of course. And with some API calls so we can invent some clever stuff of our own on top of it.

In need of Spectral Edit Api-calls? Come into the colorful world of Ultraschall-Api, which provides exactly that.
Should be possible to code copying spectral edit scripts with that, but I never tried.

https://mespotin.uber.space/Ultrasch..._Spectral_Edit

[Fabian]

Originally Posted by Meo-Ada Mespotine

In need of Spectral Edit Api-calls? Come into the colorful world of Ultraschall-Api, which provides exactly that.
Should be possible to code copying spectral edit scripts with that, but I never tried.

https://mespotin.uber.space/Ultrasch..._Spectral_Edit

Ah! I didn't know. This looks great. Thanks.

One question: the API talks of "MediaItems" but spectral edits are really specific to takes. Are only single-take media items covered?

[Meo-Ada Mespotine]

Originally Posted by Fabian

Ah! I didn't know. This looks great. Thanks.

One question: the API talks of "MediaItems" but spectral edits are really specific to takes. Are only single-take media items covered?

Hmm, you're the first person to ask, actually

Will check and see, if I missed something. And if, I'll add this to the functions as well.

Edit:
You're right, currently it only supports the first take. Will add this for other takes too.
Thanks for pointing this out

[Fabian]

Originally Posted by Meo-Ada Mespotine

You're right, currently it only supports the first take. Will add this for other takes too.
Thanks for pointing this out

Please do.
This already bit me

EDIT: I thought that was what bit me, but the following code prints "numspeceds: -1" for the example project I linked to above.

dofile(reaper.GetResourcePath().."/UserPlugins/ultraschall_api.lua")
local rpr = reaper
local usch = ultraschall

local CURR_PROJ = 0

local DO_DEBUG = true 
local function Msg(str)
   if DO_DEBUG then reaper.ShowConsoleMsg(tostring(str).."\n") end
end

local numselitems = rpr.CountSelectedMediaItems(CURR_PROJ)
if numselitems ~= 1 then Msg("One and only one selected item, please"); return end

local item = rpr.GetSelectedMediaItem(CURR_PROJ, 0)
assert(item)

local numtakes = rpr.GetMediaItemNumTakes(item)
Msg("numtakes: "..numtakes)
local acttake = rpr.GetMediaItemInfo_Value(item,"I_CURTAKE")
if acttake ~= 0 then Msg("Active take is ("..acttake..") not the first take!"); return end

local itemidx = usch.GetItem_Number(item) -- global index
local numspeceds = usch.CountItemSpectralEdits(itemidx)
Msg("numspeceds: "..numspeceds)

I *know* there are two spectral edits there.

[Meo-Ada Mespotine]

Originally Posted by Fabian

Please do.
This already bit me

EDIT: I thought that was what bit me, but the following code prints "numspeceds: -1" for the example project I linked to above.

dofile(reaper.GetResourcePath().."/UserPlugins/ultraschall_api.lua")
local rpr = reaper
local usch = ultraschall

local CURR_PROJ = 0

local DO_DEBUG = true 
local function Msg(str)
   if DO_DEBUG then reaper.ShowConsoleMsg(tostring(str).."\n") end
end

local numselitems = rpr.CountSelectedMediaItems(CURR_PROJ)
if numselitems ~= 1 then Msg("One and only one selected item, please"); return end

local item = rpr.GetSelectedMediaItem(CURR_PROJ, 0)
assert(item)

local numtakes = rpr.GetMediaItemNumTakes(item)
Msg("numtakes: "..numtakes)
local acttake = rpr.GetMediaItemInfo_Value(item,"I_CURTAKE")
if acttake ~= 0 then Msg("Active take is ("..acttake..") not the first take!"); return end

local itemidx = usch.GetItem_Number(item) -- global index
local numspeceds = usch.CountItemSpectralEdits(itemidx)
Msg("numspeceds: "..numspeceds)

I *know* there are two spectral edits there.

Yeah, consider the functions broken for the moment.
Only SetItemSpectralVisibilityState and GetItemSpectralVisibilityState work, as expected.
I'll reimplement them from scratch as new functions and deprecate the current ones.
Gives me the chance, to clean up the code for the future.

[Fabian]

Originally Posted by Meo-Ada Mespotine

Yeah, consider the functions broken for the moment.
Only SetItemSpectralVisibilityState and GetItemSpectralVisibilityState work, as expected.
I'll reimplement them from scratch as new functions and deprecate the current ones.
Gives me the chance, to clean up the code for the future.

OK, great!
Thanks.