| View previous topic :: View next topic |
| Author |
Message |
Sherz Jamologist

Joined: 27 Nov 2005 Posts: 102
|
Posted: Thu Oct 18, 2012 8:54 pm Post subject: Problem with time sig changes |
|
|
I'm not sure if anyone has encountered this but it seems JS3.5 may have a problem with time signature changes (Cubase 6.07)?
I have a couple of 2/4 bars in a 4/4 song, I have the JS option to 'allow time sig changes' set, I have reset the 'brain' to force a recompose but JS insists on playing the bar as 4/4. Perhaps I have missed something?
Cheers
 |
|
| Back to top |
|
 |
Ralph [RZ] Site Admin

Joined: 02 Jan 2008 Posts: 13332
|
Posted: Fri Oct 19, 2012 8:27 am Post subject: |
|
|
Here is the check list:
- ‘Allow Time Sig Changes’ in the OPTIONS must be checked.
- For every time sig change in your host, there must be a part change in JS at the exact same time.
- Each part in JS must have its proper time sig set in the part length edit box. _________________ Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com |
|
| Back to top |
|
 |
Sherz Jamologist

Joined: 27 Nov 2005 Posts: 102
|
Posted: Fri Oct 19, 2012 9:50 pm Post subject: |
|
|
| Ralph [RZ] wrote: | Here is the check list:
- ‘Allow Time Sig Changes’ in the OPTIONS must be checked.
- For every time sig change in your host, there must be a part change in JS at the exact same time.
- Each part in JS must have its proper time sig set in the part length edit box. |
Yes, I was aware of the above and had everything set up correctly. As it happens the issue has spontaneously resolved itself. Not sure why though as I didn't change anything?
If While it was not co-operating the symptoms were that when it got to the point where the time sig changes JS seemed to jump ahead momentarily. Also, if I clicked on the part *sometimes* the time-sig showed up as 4/4 and was 'greyed out', and therefore couldn't be changed, other times it showed as 2/4 ok as I'd originally set it and it was editble, but regardless it still played back as if it was 4/4. I restarted the project several times and reset JS a couple of times too. But at the time nothing seemed to be helping... hence this post.
Anyway, seems to be working for now so I'll keep an eye on it with fingers crossed!  |
|
| Back to top |
|
 |
|