Melodyne has no audio on selected range during playback - TS VERIFIED ISSUE IN X3

looks like the problem is once again with an X2 origin possibly. This project I am having trouble with was painstakingly built with X2 and X2a.
 
I closed the project from X3, saved in 8.5, reopened in X3 and with a region fx newly created, the audio is heard, can be retuned and everything I was expecting.
 
Looks to be some type of corruption from X2 that X3 did not translate properly or something. 100% reproducible.

Thanks Noel, it only happens once in a while. Once I get the clips in Melodyne, the audio does play. There are no clip envelopes on that track I was working with. It is a mono bass track I used just to try out Melodyne.

I think this has something to do with the way that X3 opens X2 projects. I saved the project in 8.5 and reopened it in X3 without any issues. I was able to get the desired playback as expected after that.

Another funny thing is that when I changed the blobs, I still got the old note playback. I did not hear the change in playback. It was always original unmodified audio.

Just for grins, I opened up another X2a project and tried the melodyne create range fx. No audio playback on that either. Digging deeper, I noticed that the track had all the takes collapsed and there were underlying muted takes. Removing the takes allowed the Melodyne tool to change the note blobs and playback, but I heard the original notes and the changed notes. Something is not right here.
 
So, this may or may not be a X2 corruption, but I am getting mixed results and none of them desired so far. Uploading to my FTP. I will open a support issue. Not a good start with X3...

Thanks for the reply Michael, I think I can use it if it worked like it was supposed to in SONAR. There seems to be an implementation issue. Melodyne is for sure a huge utility with a lot of opportunities. I am looking forward to getting this fixed.

I talked to a TS guy, NOT the one who closed my ticket without even looking at it or trying the project, and we went over the project I was having issues with. The problem is with the way X3 processes take lane processing. I had a single track with 2 takes. Take 1 was muted, Take 2 was solo'd.
 
With the take lanes collapsed, I selected a portion of the clip to create a range FX. X3 processed the muted clip instead of the solo'd clip and that is why I got the no audio playback. Not only that, The create region fx process cut the sudio from the solo'd track and discarded it. fortunately I could slip edit the prior clip to replace what X3 determined not necessary for the project on it's own.
 
So, TS reopened the issue and has additional info and I will be waiting for X3c to get this fixed. I hope it will be soon.

great, I am no longer able to select ANYTHING else but a fade option in the main audio track for audio processing when the lanes are collapsed. Then when the lanes are visible, right clicking in the main track lane selects the whole track and not the clip that is separated in the lane for which I clicked.

Looks like we are being FORCED to process any take edits in the lane and are no longer able to process clips from the main track lane if the takes are collapsed. Was this noted?
 
That seems like a lazy fix. I don't like to be forced to work in lanes. I don't like having to use up all the screen real estate.
 

Thanks Tom, but I shouldn't have to. That is my point. In the whole history of lane takes, this has never happened. In X3, lane processing is supposed to be one of the products key features. X3D just changed the way track processing audio works. This is a huge work flow changer.