Did a quick experiment and certainly didn't cover all possibilities but I tried a few Loops from the Loop Masters included library (REX files) and they all changed tempo when I changed tempo in Sonar.

I then created a simple drum loop using SD3 bounced that to track and duplicated. One audio clip remained unchanged, the other I turned into a Groove Clip. Dragged both files into a Windows Explorer directory then played both through the browser.

The Grove Clip audio changed tempo with Sonar, the raw wave did not. Is that how it's supposed to work?

I'll try a couple more files and instruments.

Thats the problem, RAW wave were playing on sync when you change tempos before the X1b update. Now they dont sync anymore when you play the loops from the browser.
 
REX files or groove files they work as usual. Problem is only with raw waves, I dont have acidized loops so I cant comment on that...but I read that there are problems also with acid files
 
Hope they release a patch ASAP!
 
Daniel
 
 

Please excuse my ignorance, but why and how would a raw wave file respond to a tempo change? Raw waves don't have any tempo information in them do they?

Just tried the same experiment with a guitar clip and as long as it's Grove Clipped it responds to host Tempo changes in the browser.

I think I see. You had loops that were playing to tempo changes before X1b and now they are not? And they were raw wave files? I never saved a raw wave before X1b to experiment.

What's "cuted"?

HumbleNoise


Please excuse my ignorance, but why and how would a raw wave file respond to a tempo change? Raw waves don't have any tempo information in them do they?

That's correct, Larry.  Raw wavs can be played as one-shots of course.

HumbleNoise


Just tried the same experiment with a guitar clip and as long as it's Grove Clipped it responds to host Tempo changes in the browser.

When you say "as long as it's groove clipped' -- what do you mean?   Are you dragging it INTO a track?

The wavs I'm seeing as problematic are acidized loops as I've said - and auditioning them IN the browser with "preview at host tempo" is not functioning.

Groove-Clipped=Acidized....at least in this scenario
Try looping it (in the Browser) without Groove Clipping it first... 

-e.B

HumbleNoise

ba_midi

HumbleNoise


Just tried the same experiment with a guitar clip and as long as it's Grove Clipped it responds to host Tempo changes in the browser.

When you say "as long as it's groove clipped' -- what do you mean?   Are you dragging it INTO a track?

The wavs I'm seeing as problematic are acidized loops as I've said - and auditioning them IN the browser with "preview at host tempo" is not functioning.

When I say 'Groove Clipped' I mean I take a raw wave that's been bounced to clip then hit cntl 'L' to turn it into a Groove Clip. Then take that clip and get it into the browser using your method of choice (I drag the clip to the Windows Explorer) then Preview that clip in the browser to see if it will follow Tempo changes. So far as long as the clip has been 'Groove Clipped' (please save me any more embarrassment if there's a better term for it) it will will preview in the browser and match Tempo changes.

I see ... that's different.

I just did a video I'll be putting up for everyone to review.   It clearly shows how - with the right settings (preview at host tempo) - clicking on a well-established loop library (Big Fish) I used for this one example - the loops simply do NOT play in sync.

I'll post when it's online.  Sound and all.

ba_midi

HumbleNoise

ba_midi

HumbleNoise


Just tried the same experiment with a guitar clip and as long as it's Grove Clipped it responds to host Tempo changes in the browser.

When you say "as long as it's groove clipped' -- what do you mean?   Are you dragging it INTO a track?

The wavs I'm seeing as problematic are acidized loops as I've said - and auditioning them IN the browser with "preview at host tempo" is not functioning.

When I say 'Groove Clipped' I mean I take a raw wave that's been bounced to clip then hit cntl 'L' to turn it into a Groove Clip. Then take that clip and get it into the browser using your method of choice (I drag the clip to the Windows Explorer) then Preview that clip in the browser to see if it will follow Tempo changes. So far as long as the clip has been 'Groove Clipped' (please save me any more embarrassment if there's a better term for it) it will will preview in the browser and match Tempo changes.

I see ... that's different.

I just did a video I'll be putting up for everyone to review.   It clearly shows how - with the right settings (preview at host tempo) - clicking on a well-established loop library (Big Fish) I used for this one example - the loops simply do NOT play in sync.

I'll post when it's online.  Sound and all.

Are you sure the loop is acidised? Big Fish stuff is in lots of formats, including bog standard wav.
 
Grum.

grumbleweed4162

ba_midi

HumbleNoise

ba_midi

HumbleNoise


Just tried the same experiment with a guitar clip and as long as it's Grove Clipped it responds to host Tempo changes in the browser.

When you say "as long as it's groove clipped' -- what do you mean?   Are you dragging it INTO a track?

The wavs I'm seeing as problematic are acidized loops as I've said - and auditioning them IN the browser with "preview at host tempo" is not functioning.

When I say 'Groove Clipped' I mean I take a raw wave that's been bounced to clip then hit cntl 'L' to turn it into a Groove Clip. Then take that clip and get it into the browser using your method of choice (I drag the clip to the Windows Explorer) then Preview that clip in the browser to see if it will follow Tempo changes. So far as long as the clip has been 'Groove Clipped' (please save me any more embarrassment if there's a better term for it) it will will preview in the browser and match Tempo changes.

I see ... that's different.

I just did a video I'll be putting up for everyone to review.   It clearly shows how - with the right settings (preview at host tempo) - clicking on a well-established loop library (Big Fish) I used for this one example - the loops simply do NOT play in sync.

I'll post when it's online.  Sound and all.

Are you sure the loop is acidised? Big Fish stuff is in lots of formats, including bog standard wav.
 
Grum.

+1 Posted that together.

HumbleNoise


I see Big Fish duplicates their loops into 5 different formats. Apple Loops, REX, Acid, WAV and RMX. Do ANY of the formats work?

Acid, & REX should loop fine (unless your name is Billy ). WAV was also working in X1 prior to the X1B release.

As has been mentioned, Big Fish loop sets are notoriously inconsistent regarding the formats that they are released in.


-e.B

eBlue

HumbleNoise


I see Big Fish duplicates their loops into 5 different formats. Apple Loops, REX, Acid, WAV and RMX. Do ANY of the formats work?

Acid, & REX should loop fine (unless your name is Billy ). WAV was also working in X1 prior to the X1B release.

As has been mentioned, Big Fish loop sets are notoriously inconsistent regarding the formats that they are released in.


-e.B

I really wish I could go back in time so I can understand what Sonar used to do that made you so happy. A wav can be of anything (sound-wise) so the thought that Sonar was making anything (of any length?) follow a different tempo freaks my brain.  
 
Grum.

HumbleNoise

eBlue


WAV was also working in X1 prior to the X1B release.

I wish I understood how a standard WAV file can respond to tempo changes - in any version of Sonar.

I think it's computed based off of the sample rate and length of the file. It's essentially the same thing as applying the 'groove-clip' feature except that it's being done automatically.


-e.B

eBlue

HumbleNoise

eBlue


WAV was also working in X1 prior to the X1B release.

I wish I understood how a standard WAV file can respond to tempo changes - in any version of Sonar.

I think it's computed based off of the sample rate and length of the file. It's essentially the same thing as applying the 'groove-clip' feature except that it's being done automatically.


-e.B
 

But surely that is so random that the result will be totally hit or miss? A reverb tail will totally screw up the length of a beat.
 
Grum.