Groove-clipping will not turn off? [SOLVED*]

I've always struggled with this issue... If I drag an audio clip that was exported with loop data embedded in it, SONAR won't allow me to disable it. It stays as a groove-clip no matter what.
 
Why is this?
 
Is there a way to import audio without loop data?
 
Is there a way to turn off looping on 'pre-looped' audio?
 
EDIT:
It seems SONAR doesn't allow any audio clip properties (such as tempo and looping) to be changed on 32-bit ACID wave files.
Note... FL Studio exports ACID files up to 32-bit.

How are you attempting to disable it? You should be able to right-click a clip and disable Groove Clip Looping via menu option, as well. I believe any acidized WAV or REX file you import will default to a Groove Clip.

Try "Bounce to Clip(s)" on the Track View Clips menu

scook
Try "Bounce to Clip(s)" on the Track View Clips menu

I hate it when that is my only option.
What's the point if something that is supposed to work, isn't working?!
 
Thanks, guys!

telecharge

Samuel540
I hate it when that is my only option.
What's the point if something that is supposed to work, isn't working?!
 
Thanks, guys!

What type of file is it? I couldn't tell from your video.
 
Another option is to freeze the track...
 
"To disable looping of a REX-based Groove Clip
If you want to disable looping of REX based Groove Clips, use the Track view Clips > Bounce to Clip(s) command or click the track’s Freeze button render the REX based Groove Clip to a standard audio clip."
 
https://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=Looping.13.html

It's an audio file that I exported from FL Studio. FL Studio exports wave files with loop points.

It may not be an Acidized file. I've used thousands of them over the years and Ctrl+L turns groove clip looping on and off every time. Of course I don't know if FL locks the format or does something else that's not a standard acidized file.
 
You may be trying to treat a REX file like an Acidized file. They are not the same thing. SONAR will import a REX file with its transient markers intact because they are an inherent part of the REX file format. It will also look like an Acidized file in SONAR because you can roll it out, loop it, etc.
 
However, you cannot turn a REX file's transient markers on and off as you can with an Acidized file, any more than you can have the REX file follow pitch markers. The file format doesn't allow either option.

Samuel540

Anderton
It may not be an Acidized file. I've used thousands of them over the years and Ctrl+L turns groove clip looping on and off every time. Of course I don't know if FL locks the format or does something else that's not a standard acidized file.
 
You may be trying to treat a REX file like an Acidized file. They are not the same thing. SONAR will import a REX file with its transient markers intact because they are an inherent part of the REX file format. It will also look like an Acidized file in SONAR because you can roll it out, loop it, etc.
 
However, you cannot turn a REX file's transient markers on and off as you can with an Acidized file, any more than you can have the REX file follow pitch markers. The file format doesn't allow either option.

I think I just figured out what's causing the 'lock'.
The audio file was rendered at 32bit float.
Maybe SONAR isn't fond of 32bit audio files.
 
 If anyone wishes to try it out, here's a link to the loop I made...
https://www.dropbox.com/s...it%20Float%29.wav?dl=0

I just downloaded the file, and imported it into SONAR. Then I bounced to clip (I have Shift+Ctrl+C as my shortcut). Groove looping turned off.
Ctrl+L to turn on or off again.

 
 

 
I prefer not to use the Bounce to clip(s) process especially in this case where the tempo of the audio file was not accurate in SONAR and resulted in a crackling sound throughout the clip. The 'crackling' remains present even after I used Bounce to clip(s).
 
Hopefully, the developers catches up with this.

SquireBum
Have you tried @Anderton's suggestion?  [quoted below]
After following the suggestion, I was able to enable/disable Looping and the file did not have the crackling sound.
[EDIT] The resulting file also had the correct tempo of 118 BPM.
 

Anderton
If you save the imported loop from the Loop Construction window, it will do whatever conversions are necessary to create a compatible Acidized file.

-- Ron

Yeah, there's something weird about the file format but it is a "mostly Acidized" file. So if you save it within SONAR's Loop Construction window, that makes whatever changes are necessary. You do not have to bounce the clip to itself.
 
It may relate to the 32-bit floating point, I don't know. All Acidized files I've seen are 16- or 24-bit. You might also want to check if FL Studio has any export options that can be set to solve the issue. As I mentioned, the orange transient markers are definitely something I haven't seen before in SONAR.

"All Acidized files I've seen are 16- or 24-bit." Quote Craig Anderton.
You clearly must have missed this to still be referring to this as a developer issue. 
Go back and export your file from FL Studio at a lower bit rate and report back so we can all learn if that is the fix for your issue.
 

Samuel540
 
Well, I've already settled it. It's definitely the bit rate.
I've experienced this issue a couple times before in the past but never knew why. I've recently ran into the problem again so, I decided to experiment with it. The confusing and very frustrating part of it was trying to understand why the audio file was being imported as a loop in SONAR, but when dragged into FL Studio and Ableton Live, the audio file was imported as normal. No weird, sped-up tempos etc.. 

Something is telling the file to have transient markers, and SONAR sees them. Perhaps other programs convert on the way in, or don't "see" that data so it gets stripped off.

Samuel540

Anderton
Something is telling the file to have transient markers, and SONAR sees them. Perhaps other programs convert on the way in, or don't "see" that data so it gets stripped off.

I wish SONAR did the same as the other DAWs and saved me the stress. #NoMoreStressFromSONAR

I don't know for sure where the issue lies, but the header on the file you have appears to be different from a typical Acidized file. This reminds me of the thread where someone complained about SONAR having a "serious bug" because it couldn't export floating-point files into the FLAC format without artifacts...and then someone pointed out that FLAC doesn't support floating-point. 
 
Only SONAR and Acid Pro allow creating and editing Acidized files from scratch. Maybe one man's stress is another man's flexibility . 

Actually I agree that SONAR's "you can do anything" philosophy presents its share of difficulties. For example consider how many people find the Export dialog confusing...which it is. But, it also means you can handle all kinds of export scenarios, including esoteric ones. One could counter "but doesn't saving presets solve those kinds of issues?," however, you need to know what a preset should be...which means you need to know what all the export options are anyway.
 
Ultimately I think something like Lenses is moving in the right direction. All DAWs have increased their capabilities to the point where many (most?) people find them difficult and confusing to learn. I think the "final frontier" for DAWs will be how to simplify them and also, "suggest" to the person what to do instead of depending solely on the user knowing exactly what it is they want to do. Artificial Intelligence could be of tremendous help here...but we're not there yet. 

I hadn't noticed that "Save Slice Markers" was a separate entry. I'd bet that's the source of the problem. Saving an Acidized file automatically saves any needed slice markers. Perhaps the "Save Slice Markers" option is for those who want to convert the WAV into a REX file or something...

telecharge
Not sure it would make a difference, but I would have turned of the 'Save ACIDized' and 'Save slice markers' options (as I mentioned in post #10) and re-exported. Dunno why you would leave those on if you don't want your file to time-stretch/loop.

The thing is, I didn't have those options (Save slice markers or Save ACIDized) turned on when I exported the wave file because I was going to use the file in Ableton Live and that's where I will do all my looping and time-stretching.
As it turns out, it seems the issue of the clips being embedded with slice markers, comes from Edison (FL Studio's audio editor). It seems as though Edison embeds slice markers by default.