pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
win10 timing bug - any more info?
i'm not seeing the issues others are, for example with the ca-2a, but i'm also failing to find any other discussion about it on the interwebz - i'd have thought it'd be everywhere - can any one share any links? (not including links to this forum!)
cheers
p
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 10:27:50
(permalink)
|
Sanderxpander
Max Output Level: -36.5 dBFS
- Total Posts : 3873
- Joined: 2013/09/30 10:08:24
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 10:49:54
(permalink)
http://forum.cakewalk.com/m/tm.aspx?m=3526221
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 10:59:25
(permalink)
John
What timing bug?
how would you better describe it? (i'm assuming you weren't just trolling me)
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:03:29
(permalink)
It's an interoperability issue that may only affect VST plugins, and possibly only Cakewalk's due to the way they're coded. The issue was triggered/exposed by the Win10 update, but that doesn't mean there's a unilateral problem with Win10 that affects other software. That's why you're not seeing any reports outside of this space.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:25:04
(permalink)
brundlefly
It's an interoperability issue that may only affect VST plugins, and possibly only Cakewalk's due to the way they're coded.
...and possibly only Cakewalk VST plug-ins that were coded during a particular time period that used a particular set of tools.
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:29:30
(permalink)
thanks dave, i get the common understanding of it as per this forum, i was just fishing for more info - like, is it to do with directsound/directshow, for example? i can't get ca-2a to crash in other hosts, and i'd like to know why not! it's being blamed on a win10 update, but which one? why doesn't that update have an effect on other hosts?if a windows update hosed some essential audio stack gubbins, the whole internet would be alight...
what is sonar doing differently than other hosts, that exposes this decades old windows bug? (i can speculate but was avoiding doing that, more polite to ask first)
cheers
p
(edited for typo)
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:30:37
(permalink)
thanks craig - so shouldn't i see the same issue in other daws when i try and use the ca-2a? that's the bit i don't get
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:43:38
(permalink)
pwalpwal
John
What timing bug?
how would you better describe it? (i'm assuming you weren't just trolling me)
I know of no Windows bug timing or otherwise. One could be there I just haven't heard of it. Hence the question. I still am not seeing any evidence of a bug. I don't troll.
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:52:06
(permalink)
John
pwalpwal
John
What timing bug?
how would you better describe it? (i'm assuming you weren't just trolling me)
I know of no Windows bug timing or otherwise. One could be there I just haven't heard of it. Hence the question. I still am not seeing any evidence of a bug. I don't troll.
do you read these forums? check sander's link? you are a "host" after all, your input should be useful, shurely?
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:52:36
(permalink)
When this issue first arose, as usual I went a-googling for additional information. And found none. No bulletins, no emergency patches, no discussion on gaming- or audio-related forums. Usually you can count on gamers to get vocal about even minor O/S inconveniences. But nuttin'.
From reports on this forum, it seems to be specific to Win10. Folks who pre-emptively stayed on Win 7 or 8.1 (nobody stayed on 8.0) aren't seeing the problem. "Interoperabilty issue" is a good choice of words. It's what you say when two programs are fine on their own but cannot work together. Even though the problem isn't entirely within SONAR, my guess is the fix is still going to come from Cakewalk, not Microsoft.
I'd love for Noel to drop by and give us a technical explanation, but he's probably pretty busy right now.
 All else is in doubt, so this is the truth I cling to. My Stuff
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 11:59:40
(permalink)
bitflipper
When this issue first arose, as usual I went a-googling for additional information. And found none. No bulletins, no emergency patches, no discussion on gaming- or audio-related forums. Usually you can count on gamers to get vocal about even minor O/S inconveniences. But nuttin'.
From reports on this forum, it seems to be specific to Win10. Folks who pre-emptively stayed on Win 7 or 8.1 (nobody stayed on 8.0) aren't seeing the problem. "Interoperabilty issue" is a good choice of words. It's what you say when two programs are fine on their own but cannot work together. Even though the problem isn't entirely within SONAR, my guess is the fix is still going to come from Cakewalk, not Microsoft.
I'd love for Noel to drop by and give us a technical explanation, but he's probably pretty busy right now.
thanks dave, i too would like a technical explanation (if only because i have win10, etc etc, but am not seeing the issue) - "interop issue" is still rather vague as an explanation (a bit like "the key doesn't fit the lock") (edit to add, i did read your debugging/troubleshooting posts)
|
dlesaux
Max Output Level: -70 dBFS
- Total Posts : 1034
- Joined: 2009/09/13 09:25:18
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:07:11
(permalink)
I'd appreciate an update.. Will the fix be coming in a week, a month..?
Peace! Daniel Sonar Platinum - 2017.10 and PreSonus Studio One 3.5.5
Windows 10 64 bit
Studiocat Skylake Desktop PC with Intel i7 6700k processor @ 4.20 GHz / 16G RAM
Focusrite Scarlett 2i2 Audio Interface and Cakewalk UM-2G Midi Interface Check out my website
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:08:55
(permalink)
pwalpwal
John
pwalpwal
John
What timing bug?
how would you better describe it? (i'm assuming you weren't just trolling me)
I know of no Windows bug timing or otherwise. One could be there I just haven't heard of it. Hence the question. I still am not seeing any evidence of a bug. I don't troll.
do you read these forums? check sander's link? you are a "host" after all, your input should be useful, shurely?
I asked the question before the "link" was posted. Further the link does not link to anything. I have read a ton of things about crashing and problems since the Sonar update. I don't know of any confirmed bug report about Windows. I have not had any problem with Sonar or Windows. There has been some speculation as to why this update is a problem for some and not others. But no one that I have read has reported a timing bug in Windows.
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:13:33
(permalink)
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:15:48
(permalink)
quote from lance's post, linked by sander above, and discussed in other threads before lance posted, "We are able to reproduce the issue and it appears to only affect some systems since it is timing related."
|
bapu
Max Output Level: 0 dBFS
- Total Posts : 86000
- Joined: 2006/11/25 21:23:28
- Location: Thousand Oaks, CA
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:16:44
(permalink)
I know all about interoperability issues. I'm a bass player.
On a good note AFAIK I'm on the latest Win 10 update and have not experienced any of the problems reported by other on this forum.
|
dlesaux
Max Output Level: -70 dBFS
- Total Posts : 1034
- Joined: 2009/09/13 09:25:18
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:17:43
(permalink)
Here is what Lance said in a separate post:
Instability with certain Cakewalk plugins after recent Windows 10 updatesIt has come to our attention that a recent Windows 10 update has introduced instability in a subset of our plug-ins and may cause SONAR or other Windows DAWs to crash. The problem is related to a change in the timing for thread initialization on Windows, which leads to intermittent crashing on project load, plug-in scanning, or adding these plug-ins to a project. We are able to reproduce the issue and it appears to only affect some systems since it is timing related. We are actively working on a resolution and will release fixes to the affected plugins as soon as possible.
So yeah, calling it a timing issue is entirely appropriate.
Peace! Daniel Sonar Platinum - 2017.10 and PreSonus Studio One 3.5.5
Windows 10 64 bit
Studiocat Skylake Desktop PC with Intel i7 6700k processor @ 4.20 GHz / 16G RAM
Focusrite Scarlett 2i2 Audio Interface and Cakewalk UM-2G Midi Interface Check out my website
|
dlesaux
Max Output Level: -70 dBFS
- Total Posts : 1034
- Joined: 2009/09/13 09:25:18
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:19:30
(permalink)
John
pwalpwal
John
pwalpwal
John
What timing bug?
how would you better describe it? (i'm assuming you weren't just trolling me)
I know of no Windows bug timing or otherwise. One could be there I just haven't heard of it. Hence the question. I still am not seeing any evidence of a bug. I don't troll.
do you read these forums? check sander's link? you are a "host" after all, your input should be useful, shurely?
I asked the question before the "link" was posted. Further the link does not link to anything. I have read a ton of things about crashing and problems since the Sonar update. I don't know of any confirmed bug report about Windows. I have not had any problem with Sonar or Windows.
There has been some speculation as to why this update is a problem for some and not others. But no one that I have read has reported a timing bug in Windows.
I'm glad you're not experiencing any problems. That's awesome!  Unfortunately, some of us are seeing the issue so we're eager to see what the next steps are..
Peace! Daniel Sonar Platinum - 2017.10 and PreSonus Studio One 3.5.5
Windows 10 64 bit
Studiocat Skylake Desktop PC with Intel i7 6700k processor @ 4.20 GHz / 16G RAM
Focusrite Scarlett 2i2 Audio Interface and Cakewalk UM-2G Midi Interface Check out my website
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:31:30
(permalink)
Please understand that is not confirmation of a bug. That is as it states speculation. "It Appears" is used. Jumping to conclusions about it is premature. As far as I can see CW is seeing an issue and is looking into it.
I fully understand the wish to have any issue solved as soon as possible but we don't know as fact what the problem is yet.
|
Sanderxpander
Max Output Level: -36.5 dBFS
- Total Posts : 3873
- Joined: 2013/09/30 10:08:24
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:41:26
(permalink)
It appears John is being deliberately obtuse.
|
dlesaux
Max Output Level: -70 dBFS
- Total Posts : 1034
- Joined: 2009/09/13 09:25:18
- Status: offline
Re: win10 timing bug - any more info?
2016/12/12 12:44:00
(permalink)
Thanks for you insight John! I think we all just want the same thing anyway.. We all just want to make music! Happy Holidays to everyone! *<|:o)
Peace! Daniel Sonar Platinum - 2017.10 and PreSonus Studio One 3.5.5
Windows 10 64 bit
Studiocat Skylake Desktop PC with Intel i7 6700k processor @ 4.20 GHz / 16G RAM
Focusrite Scarlett 2i2 Audio Interface and Cakewalk UM-2G Midi Interface Check out my website
|