Creating a region clip works fine as long as the whole clip is visible.
 
If I've trimmed the clip (non destructively) so part of the wave form isn't visible and then try and use region FX on this, Sonar crashes.
Anyone can reproduce this?

Just for clarification, are you slip editing the sides of the clip or just selecting the middle of a clip?

Yes, I'm slip editing

How long does the clip clock in at?

If you apply trimming or bounce to clip it doesn't exhibit this behavior correct?

I'm not sure what you mean by how long the clip clock in at.
But it's correct that if I bounce the clip first Sonar doesn't crash when I select region edit

Loptec
I'm not sure what you mean by how long the clip clock in at.
But it's correct that if I bounce the clip first Sonar doesn't crash when I select region edit

Overall length of the clip?

I'll definitely make sure this is investigated further for updates.

Ah alright :)
I've tried this in several project where the clip lengths have been different.
 
In the project I'm working in at the moment I tried it on a vocal track that was about three minuets in total length.
 
I selected the silent parts between verses and pressed delete to get rid of the silence. After this I tried applying region FX on the still visible parts of the clip and got the crash.
 
After this I did the exact same procedure, except that I bounced the visible clip regions before applying the FX. No crash.
 
Thanks for the fast reply Seth! Hope you'll figure it out :)

Loptec
Ah alright :)
I've tried this in several project where the clip lengths have been different.
 
In the project I'm working in at the moment I tried it on a vocal track that was about three minuets in total length.
 
I selected the silent parts between verses and pressed delete to get rid of the silence. After this I tried applying region FX on the still visible parts of the clip and got the crash.
 
After this I did the exact same procedure, except that I bounced the visible clip regions before applying the FX. No crash.
 
Thanks for the fast reply Seth! Hope you'll figure it out :)

Yup, no worries. We just need to check if it's on which end this is happening. I'm sorry that it impacts your preferred workflow.

I can't reproduce it, seems to work fine here.
 
Dan