X2 X1 backwards compatability?

Author
Post
Essentials Only Full Version
paultucci
Max Output Level: -90 dBFS
  • Total Posts : 13
  • Joined: 2012/11/26 20:35:27
  • Status: offline
2012/11/26 21:29:01 (permalink)

X2 X1 backwards compatability?

Fellas, A little help here please! First, the symptom is this.... Monitoring a new track's audio during recording is whack. Way behind the beat (150 mS) and unplayable on a keyboard. This is a new problem after upgrading to X2. I may have opened an X1 project, saved it as X2, and then tried to reopen in X1. This seems to be my thinking so far. Still troubleshooting. Anything sound familiar? PT
#1

4 Replies Related Threads
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:X2 X1 backwards compatability? 2012/11/26 22:00:10 (permalink)
    No not really. You need to take a look at your latency in either your ASIO panel or the WDM slider in Sonar. Adjust it to get good latency with no drop outs.  If you have a good audio interface this should not be a problem. 

    Best
    John
    #2
    paultucci
    Max Output Level: -90 dBFS
    • Total Posts : 13
    • Joined: 2012/11/26 20:35:27
    • Status: offline
    Re:X2 X1 backwards compatability? 2012/11/26 22:13:22 (permalink)
    Thanks for a quick look. All had been good within X1 by itself, within X2 by itself and just fine when creating/unbundling between different machines in X1. Now my X1 projects that were saved as X2 bundles and unbundled in X1 are misbehaving. Projects that reside in the computer in X1 behave normally. Somewhere, something is whack. PT
    #3
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re:X2 X1 backwards compatability? 2012/11/27 03:22:16 (permalink)
    Don't save as a bundle!

    Save as a normal cwp.

    If for some reason your cwp ever becomes corrupted, you can, theoretically rebuild in from the wavs stored on disc which will not be corrupt.

    If for some reason your cwb ever becomes corrupt, that's it, game over, you've lost everything in that project permanently

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #4
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:X2 X1 backwards compatability? 2012/11/27 04:15:07 (permalink)
    paultucci


    Thanks for a quick look. All had been good within X1 by itself, within X2 by itself and just fine when creating/unbundling between different machines in X1. Now my X1 projects that were saved as X2 bundles and unbundled in X1 are misbehaving. Projects that reside in the computer in X1 behave normally. Somewhere, something is whack. PT

    If I understand you right you are opening bundle files created with X2 in X1. If that is so no wonder it is giving you problems. Don't do that. Never open a file if you can avoid it made with a newer version in an older version. You can open an older file in a new version but its a crap game the other way around. 

    Best
    John
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1