File extension 20/20 hindsight

Author
musicroom
Max Output Level: -51 dBFS
  • Total Posts : 2421
  • Joined: 2004/04/26 22:31:02
  • Status: offline
2012/05/05 03:19:23 (permalink)

File extension 20/20 hindsight

While I'm bouncing back and forth finishing up some projects that originated in 8.5.3, it occurs to me that with all the major differences between X1 and 8.5.3 cake would have helped that process by giving X1 a slightly different file extension to help differentiate. I like the idea of also giving us the option to save X1 files to better match the backward compatibility better.

Typically the 8.5.3 files I port to X1 and or port X1 to 8.5.3 usually have some quirky things happening. I noticed in particular, the sends all look like they are the same, but I've noticed some major differences in how they actually work. Also, if you use prochannel in X1, you are probably going to face some weirdness if you decide to work on the project in an earlier version. Something similar to how MS office handles options for saving for backward compatibility.

Just a thought as I fought that issue this evening.


Dave




 
Dave
Songs
___________________________________
Desktop: Platinum / RME Multiface II / Purrfect Audio DAW  I7-3770 / 16 GB RAM / Win 10 Pro / Remote Laptop i7 6500U / 12GB RAM /  RME Babyface



 
 
#1

5 Replies Related Threads

    mudgel
    Max Output Level: 0 dBFS
    • Total Posts : 12010
    • Joined: 2004/08/13 00:56:05
    • Location: Linton Victoria (Near Ballarat)
    • Status: offline
    Re:File extension 20/20 hindsight 2012/05/05 04:18:09 (permalink)
    That's one reason that I only work new projects in X1. While I don't use 8.5.3 on a day to day basis I have it loaded for all my pre X1 Projects and never bring them forward to X1. Neither do I ever retro grade a project made in X1 by going back to 8.5 or working back and forth between versions.
    Too many hinkie things going on when I tried that.

    Now I've retired 8.5 for day to day use and use X1D exp. as my regular go to SONAR version. Pretty much been the case since about 1 month after X1C proved to be stable enough for day to day use




    Mike V. (MUDGEL)

    STUDIO: Win 10 Pro x64, SPlat & CbB x64,
    PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz.
    Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2.
    Monitors: Adam A7X, JBL 10” Sub.
    Audio I/O & DSP Server: DIGIGRID IOS & IOX.
    Screen: Raven MTi + 43" HD 4K TV Monitor.
    Keyboard Controller: Native Instruments Komplete Kontrol S88.
    #2
    musicroom
    Max Output Level: -51 dBFS
    • Total Posts : 2421
    • Joined: 2004/04/26 22:31:02
    • Status: offline
    Re:File extension 20/20 hindsight 2012/05/05 13:57:18 (permalink)
    That's what I learned last evening as well. I had tried 8.5.3 projects in X1A,B,C but had not tried any with the X1D upgrade.

    Like I mentioned, things appeared to be in place, but were not. For instance, I would solo a vox and the guitar track would be playing from a bus that no Send was in place for the gtr to be connected to that bus. I stopped all the sends from the vox track, and the gtr disappeared. So then, I deleted the sends from the vox and reinserted them - all was well. That fixed it - no more piggy backing of the gtr track - which had no relation to anyway. 

    After finding more of this type of signal crossing, I decided to continue my mix in 8.5.3. and thinking of compatibility between the two and how that could have been improved.

    I like working in X1 better, so I may port the files into a new X1 template. But that's not really the topic.

     
    Dave
    Songs
    ___________________________________
    Desktop: Platinum / RME Multiface II / Purrfect Audio DAW  I7-3770 / 16 GB RAM / Win 10 Pro / Remote Laptop i7 6500U / 12GB RAM /  RME Babyface



     
     
    #3
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:File extension 20/20 hindsight 2012/05/05 14:07:34 (permalink)
    I have always added the version of Sonar to my project files when I know it will matter. For X1 projects I simply save it with X1 in the file name. Same with past versions.

    To me this is user 20 20 vision. This also lets me open a version of a project done in that version.





    Best
    John
    #4
    musicroom
    Max Output Level: -51 dBFS
    • Total Posts : 2421
    • Joined: 2004/04/26 22:31:02
    • Status: offline
    Re:File extension 20/20 hindsight 2012/05/05 14:19:53 (permalink)
    Like that idea John - good one!

    This is the first time in my sonar days that backward capability caused issues. I could always open files from previous versions of Sonar and use them with confidence. Once saved in a newer version, I knew I wouldn't or shouldn't go backwards. This series change was significant. So I still would have "liked" either more of a heads up for treating files the way you do or extension choices for compatibility.

    FWIW - MSExcel is a great example of this. 

     
    Dave
    Songs
    ___________________________________
    Desktop: Platinum / RME Multiface II / Purrfect Audio DAW  I7-3770 / 16 GB RAM / Win 10 Pro / Remote Laptop i7 6500U / 12GB RAM /  RME Babyface



     
     
    #5
    Blogman
    Max Output Level: -81 dBFS
    • Total Posts : 481
    • Joined: 2011/02/08 02:32:48
    • Status: offline
    Re:File extension 20/20 hindsight 2012/05/06 12:01:21 (permalink)
    +1 for adding the project Version to the file name. Never fails someone needs a soundtrack for something they did 3 years ago... Nice to see what version to use. PLUS, with Fastbouncing of Antares/Melodyne killed as of X1D, I copy, rename -8.53, then open in Sonar 8.53 for Tuning/timing editing. After I'm don with that I re-copy the file and re-name that PROJECT_tuned_x1expd, then open that copy. In fact I almost never open the last copy of a project without copy/re-naming. X1 has been bad about corrupting.
    #6
    Jump to:
    © 2025 APG vNext Commercial Version 5.1