I created new templates a few months ago and no longer had the problem. It reappeared in a project recently, but I had imported screensets from an older project. It does not happen if I start with a blank project.

tenfoot
I created new templates a few months ago and no longer had the problem. It reappeared in a project recently, but I had imported screensets from an older project. It does not happen if I start with a blank project.

How do you import screensets? I wonder if I imported screensets from the default template that would fix it.


I've tried deleting a bunch of tracks even my track folders. I then created a new track folder and the same thing happens. Also I for got to mention I'm using the latest Platinum, latest installs and updates.
 
I just loaded the default template, closed the console view,  created an audio track, then a midi track, then selected both, cloned 22 times to create 46 tracks. I put track 25-36 in a track folder and the exact same behavior is present.

Worth a try. You import screensets by having two projects open and using the import screensets function in the drop-down menu of the screensets module in the project you wish to import the screensets to.

http://www.cakewalk.com/D...agement.8.html#1260131

Considering I just duplicated the problem very easily in a clean default template, it seems like importing a screenset wouldn't be too useful, after all the default template should have up to date screensets. Can anyone try the recipe I did above using the default template to see if you get the same results.
 
The most recent default template I've found in Platinum is dated 9/4/13. Is that right? Seems pretty old

gmp
Considering I just duplicated the problem very easily in a clean default template, it seems like importing a screenset wouldn't be too useful, after all the default template should have up to date screensets. Can anyone try the recipe I did above using the default template to see if you get the same results.
 
The most recent default template I've found in Platinum is dated 9/4/13. Is that right? Seems pretty old

Wow - I will try when I get back to the studio Gerry. Maybe my old template/screenset theory is just a post hoc fallacy. 

You are absolutely right Gerry. This problem certainly seems to be back full time. If someone else could spare 2 mins to confirm this would be a great help.
 
1. Create a new project using the blank project option.
2. Right click in track view and use insert multiple tracks to insert 50 audio tracks.
3. Scroll down and select the last track, right click and choose 'move to new folder'
4. Now close the folder containing the new track using the ' - ' symdol on the folder track. The track view will jump back to the top of the screen
5. Scroll back down and open the folder again using the plus symbol.
6.Close the folder again. Track view will again jump to the top of the track list.
 
I have removed all controll surfaces, have no altered or locked screensets and the problem persists.
If others don't have the issue we can continue to search for a system cause.
Apologies for the post hoc red herring!
 
 

@tenfoot @gmp
confirmed. Same problem here. When I close a folder the track view jumps back to beginning.
Not only when I put in the last track to a folder, on other tracks it's the same.
 
But it stays when you put in the first track to a folder too. Maybe this could be a workarround.
 
Imo, a bug.
 
-Markus

mdages
@tenfoot @gmp
confirmed. Same problem here. When I close a folder the track view jumps back to beginning.
Not only when I put in the last track to a folder, on other tracks it's the same.
 
But it stays when you put in the first track to a folder too Maybe this could be a workarround.
 
Imo, a bug.
 
-Markus

Thanks Markus. Good catch with putting the first track in a folder!
EDIT. Workaround confirmed.

mdages
 
But it stays when you put in the first track to a folder too. Maybe this could be a workarround.
 
-Markus

Thanks very much Marcus - the workaround works a treat! The problem only occurs when the first track of the project is not in a folder. Tested the workaround on an old problematic project and all is good:) Also explains why my new templates worked as the first track was in a folder. Hopefully this helps solve the issue for you too Gerry:)
 
FWIW I submitted a problem report: CWBRN-49605