iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
Hi.
First of all let me see I really appreciate the tolerance of people using all kinds of different Cakewalk versions, without harassing anybody to upgrade to the latest version. I also appreciate the openness and tolerance here even of use of other DAW's, and that the focus is what music you make ... not how.
My question is, I'm wondering about how well a project created in one version of Cakewalk translates between different versions. Is it possible to create a project say in the latest CbB edition, then to open this project for some other works say in an older version say Sonar VS or say hypothetically Sonar 1 ? Is there some limits in terms of compatibility between versions downward, I'm thinking of the project file in it self ... and of course not taking into consideration using plugins and features specific to the newer version which is not found in the older version.
Thank You, Sven
|
Skyline_UK
Max Output Level: -54 dBFS
- Total Posts : 2133
- Joined: 2004/04/15 17:55:09
- Location: Midlands, UK
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 13:00:08
(permalink)
☼ Best Answerby iRelevant 2018/04/18 15:39:11
Yes, I've been freely doing that. It's the same code, after all.
My stuff Intel Sandy Bridge i7 2600 @ 3.4GHz, 4 cores, 8 threads, 16GB RAM.OS & Programs drive: 240GB SSD
Data drives: 1 x 1TB drive RAID mirrored, plus extra 1TB data drive
Windows 10 Home 64 bit
Cakewalk by BandLab 64 bit, Studio One 3, Band In A Box 2016, Ozone 8+ too many other pluginsBandLab page
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 13:08:19
(permalink)
That following is just a guess (from CWP format):
* Sonar 8.5 - CbB projects should be more or less recognized by any other version in the range
* Sonar ? - 5 projects was significantly different, I doubt these versions can open CbB projects
* Sonar 6 - 8 I do not know
But CbB should be able to open any project, so whats the problem?
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 13:19:55
(permalink)
azslow3
But CbB should be able to open any project, so whats the problem?
he wants to make the project in cbb and then open it in an older version
|
bluzdog
Max Output Level: -56 dBFS
- Total Posts : 1928
- Joined: 2007/10/06 17:15:14
- Location: Lakewood, Colorado
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 13:25:57
(permalink)
For projects from versions that existed before per project audio folders as far back as Sonar 1.x I saved bundle files and can open them in Platinum. They open but I usually have missing plugins. That's fine by me because I usually create a new mix anyway.
For projects that have been created since per project audio folders have been around I can open them without issue other than an occasional missing plugin. If I save them in the latest version of Sonar the chance of opening them in an older version is hit or miss. I don't usually care about backwards compatibility in this case but circumstances have changed and going forward I'll make sure to use "save as" so I still have the older version of the project.
Rocky
|
Midiboy
Max Output Level: -82 dBFS
- Total Posts : 414
- Joined: 2015/01/14 09:29:54
- Location: Northwood
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 13:50:32
(permalink)
Usually, "going backwards" doesn't work so well due to project pathing and feature updates. Opening up OLDER projects in newer versions works pretty well, most of the time...at least as far as the Sonar days. Older versions of CW, I'm not sure.
---- Gregg Midiboy Music www.facebook.com/midiboygregg Win10x64 (Eng), Sonar Platinum x64 (Eng w/ lifetime updates), 32GB DDR4 RAM, Intel i7 5820, nVidia 960, Alesis MultiMix 8 USB2 w/ Alesis MultiMix driver. Native Instruments Komplete Kontrol S88, Korg NanoControl.
|
daveny5
Max Output Level: 0 dBFS
- Total Posts : 16934
- Joined: 2003/11/06 09:54:36
- Location: North Carolina
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 14:02:05
(permalink)
I think most people would advise against using CWB or BUN format for saving files. The size of the files cause them to have a tendency to get corrupted or unable to load.
Dave Computer: Intel i7, ASROCK H170M, 16GB/5TB+, Windows 10 Pro 64-bit, Sonar Platinum, TASCAM US-16x08, Cakewalk UM-3G MIDI I/F Instruments: SL-880 Keyboard controller, Korg 05R/W, Korg N1R, KORG Wavestation EX Axes: Fender Stratocaster, Line6 Variax 300, Ovation Acoustic, Takamine Nylon Acoustic, Behringer GX212 amp, Shure SM-58 mic, Rode NT1 condenser mic. Outboard: Mackie 1402-VLZ mixer, TC Helicon VoiceLive 2, Digitech Vocalist WS EX, PODXTLive, various stompboxes and stuff. Controllers: Korg nanoKONTROL, Wacom Bamboo Touchpad
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:15:46
(permalink)
he wants to make the project in cbb and then open it in an older version?
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:17:13
(permalink)
OPIs it possible to create a project say in the latest CbB edition, then to open this project for some other works say in an older version say Sonar VS or say hypothetically Sonar 1 ?
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:17:44
(permalink)
|
iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:39:52
(permalink)
|
iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:42:46
(permalink)
azslow3
That following is just a guess (from CWP format):
* Sonar 8.5 - CbB projects should be more or less recognized by any other version in the range
* Sonar ? - 5 projects was significantly different, I doubt these versions can open CbB projects
* Sonar 6 - 8 I do not know
But CbB should be able to open any project, so whats the problem?
There is no problem. I'm more trying to familiarize myself with my options and the nature of *.cwp files.
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:42:52
(permalink)
☄ Helpfulby pwalpwal 2018/04/18 16:28:10
I tried to open a SPLAT CWP in 8.5 and it was a no go. I was told that it's due to AUX tracks.
|
iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:47:06
(permalink)
daveny5
I think most people would advise against using CWB or BUN format for saving files. The size of the files cause them to have a tendency to get corrupted or unable to load.
OK. Thanks, I understand the *.CWP is a more flexible option then ?
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:49:21
(permalink)
☄ Helpfulby pwalpwal 2018/04/18 16:28:25
Refer to the Backward Compatibility section in the Readme.rtf in the most recent version of SONAR available. Also note that projects containing patch points or aux tracks will not open in any version of SONAR that does not support the feature.
|
iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 15:53:57
(permalink)
pwalpwal
housekeeping?
Just familiarizing myself with my options. I''m still make heavily use of 32-bit plugs, and there might be scenarios where I will move "down" a level to work purely in the 32-bit domain ... before moving back up again to CbB for the final touch. Was just wondering if it was a NO NO ... apart from the obvious plugs/features thing. As I understand it so far, it may be doable.
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 16:30:16
(permalink)
iRelevant
pwalpwal
housekeeping?
Just familiarizing myself with my options...
sorry, no, i meant this:
|
iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 16:55:30
(permalink)
scook
Refer to the Backward Compatibility section in the Readme.rtf in the most recent version of SONAR available. Also note that projects containing patch points or aux tracks will not open in any version of SONAR that does not support the feature.
Thank you very much Scook, your the man. Answered all my questions.
|
iRelevant
Max Output Level: -82 dBFS
- Total Posts : 430
- Joined: 2017/10/25 21:14:48
- Location: Norway
- Status: offline
Re: Interversion compatibility of Cackewalk project files (*.cwp/*.cwb)
2018/04/18 17:00:49
(permalink)
☄ Helpfulby pwalpwal 2018/04/18 18:12:55
pwalpwal
iRelevant
pwalpwal
housekeeping?
Just familiarizing myself with my options...
sorry, no, i meant this:
No, not now, some other time ....
|