why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked??

Author
pwalpwal
Max Output Level: -43 dBFS
  • Total Posts : 3249
  • Joined: 2015/01/17 03:52:50
  • Status: offline
2017/04/23 13:21:30 (permalink)

why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked??

i was going to comment that bob's info was really useful because reaper was ok but sonar not so much, surely there's some useful comparison to be done there?
/fwiw

just a sec

#1

11 Replies Related Threads

    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 13:24:43 (permalink)
    A Waves reinstall solved the problem. I cannot say for sure but my guess is Jim locked the thread because the user fixed his system problem.
    #2
    BobF
    Max Output Level: 0 dBFS
    • Total Posts : 8124
    • Joined: 2003/11/05 18:43:11
    • Location: Missouri - USA
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 13:25:41 (permalink)
    scook
    A Waves reinstall solved the problem. I cannot say for sure but my guess is Jim locked the thread because the user fixed his system problem.




    As expected ...

    Bob  --
    Angels are crying because truth has died ...
    Illegitimi non carborundum
    --
    Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
    Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
    Waves Gold/IKM Max/Nomad Factory IS3/K11U

    #3
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 13:37:31 (permalink)
    ok

    just a sec

    #4
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 13:41:58 (permalink)
    i expect that he will lock all the other "solved" threads then, for consistency

    just a sec

    #5
    BobF
    Max Output Level: 0 dBFS
    • Total Posts : 8124
    • Joined: 2003/11/05 18:43:11
    • Location: Missouri - USA
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 14:43:54 (permalink)


    Bob  --
    Angels are crying because truth has died ...
    Illegitimi non carborundum
    --
    Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
    Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
    Waves Gold/IKM Max/Nomad Factory IS3/K11U

    #6
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 14:53:37 (permalink)


    just a sec

    #7
    Anderton
    Max Output Level: 0 dBFS
    • Total Posts : 14070
    • Joined: 2003/11/06 14:02:03
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 15:33:38 (permalink)
    pwalpwal
    i expect that he will lock all the other "solved" threads then, for consistency



    That would make sense only if there was only one flavor of "solved." Some solved issues are of universal importance, some aren't.

    The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
    #8
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 15:42:08 (permalink)
    Anderton
    pwalpwal
    i expect that he will lock all the other "solved" threads then, for consistency



    That would make sense only if there was only one flavor of "solved." Some solved issues are of universal importance, some aren't.


    just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)

    just a sec

    #9
    SquireBum
    Max Output Level: -84 dBFS
    • Total Posts : 347
    • Joined: 2013/06/26 13:23:55
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 16:03:08 (permalink)
    pwalpwal
     
    just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)




    When the thread is related to Early Release posts in the Problem Reports forum, I think Jim Lima locks the report to indicate that he has either reported the problem to the developers or the user has solved the problem.  Locking indicates that Jim or someone else from Cakewalk no longer has to review that problem when reviewing the list of Early Release issues in the forum.
     
    -- Ron

    Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
    Windows 10 x64
    AMD Phenom II X4 955 3.20 GHz
    8 GB Ram
    Nvidia GeForce 9500 GT
    Echo Gina 3G
    #10
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 16:09:52 (permalink)
    SquireBum
    pwalpwal
     
    just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)




    When the thread is related to Early Release posts in the Problem Reports forum, I think Jim Lima locks the report to indicate that he has either reported the problem to the developers or the user has solved the problem.  Locking indicates that Jim or someone else from Cakewalk no longer has to review that problem when reviewing the list of Early Release issues in the forum.
     
    -- Ron


    fair enough, seems like a reasonable thing to do
     
    took a quick browse of that forum: has he only just (the last few days) started doing this, or are all the not-locked threads still "not seen yet"?

    just a sec

    #11
    SquireBum
    Max Output Level: -84 dBFS
    • Total Posts : 347
    • Joined: 2013/06/26 13:23:55
    • Status: offline
    Re: why did the "Re: 17.04 Early + Waves 9.91 = choke on scan " thread get locked?? 2017/04/23 17:07:21 (permalink)
    pwalpwal
    SquireBum
    pwalpwal
     
    just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)




    When the thread is related to Early Release posts in the Problem Reports forum, I think Jim Lima locks the report to indicate that he has either reported the problem to the developers or the user has solved the problem.  Locking indicates that Jim or someone else from Cakewalk no longer has to review that problem when reviewing the list of Early Release issues in the forum.
     
    -- Ron


    fair enough, seems like a reasonable thing to do
     
    took a quick browse of that forum: has he only just (the last few days) started doing this, or are all the not-locked threads still "not seen yet"?




    If you go back far enough in the Problem Reports forum to view Early Release problems for the last few months, you can see that Jim has been locking posts for Early Release problems as he addresses them.  These issues seem to always be addressed in the next release.  I can't answer for the "not-locked" posts, because I find that sometimes the problem may be fixed in the next release or it may not be fixed.
     
    --Ron
     

    Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
    Windows 10 x64
    AMD Phenom II X4 955 3.20 GHz
    8 GB Ram
    Nvidia GeForce 9500 GT
    Echo Gina 3G
    #12
    Jump to:
    © 2024 APG vNext Commercial Version 5.1