I am using SONAR X3b to record foley and SFX for a film.
It appears that I cannot select and copy/paste the marker list. Is there a workaround? Are the markers stored in a CSV or similar file (perhaps under the new "assets" file) that might be somehow accessed? 
 
It would be very nice to be able to export the markers to a spreadsheet so I could then arrange the similar events (walking sounds, fight sounds, what-have-you) and easily find the locations and get all the similar sounds done in a single session, rather than having to make a separate spreadsheet by hand or read through the marker list (as I cannot CTRL-F/ search inside the marker list)
Is there another way other than doing a screen capture and then use OCR software and then manipulating that? It appears the Markers are already in a form I can use, it's just a matter of getting at them.
 
 

This sounds useful - I will hunt around a bit for them later today, and if I can get at them I will post the steps for getting them
 
Bob Bone
 

I've seen requests for this before. It's s not currently possible, and since there's no universal standard for exchanging them between DAWs, it's probably not a high priority for the Bakers.  But I did find this app that does Marker management for DAWs that can import/export marker data in some format:
 
http://www.soundsinsync.com/products/ediload
 
 So maybe there's hope if you file a feature request with Cakewalk. Squeaky wheel gets the grease when it comes to new features, and it probably wouldn't require a huge amount of coding just to generate a .CSV:
 
http://www.cakewalk.com/support/contact/featurerequest.aspx
 
 
 
 

Thanks, guys: I put in a feature request after posting the original query. 
MS Office 2010 has an ok OCR, that at least gets the data into a spreadsheet.
I used the snipping tool to make a jpg of the marker screen
I import into MS OneNote
I then can use the "copy text from picture" function and paste that into Excel
The data then needs a bit of massaging due to gaps between the beginnings of '1's which messes up the filtering, but overall it's a workaround...just not pretty or particularly fast