As disappointing as it is, I had to quit X1b build 255

I've been very happy with X1b, running it for months with no problems whatsoever.  I applied all the quick fixes up through build 246, and it ran like a dream.  Then, last week I applied build 255, and I had nothing but problems.  I finally did a system restore back to build 246, and it's been running great since then.  This concerns me because X1c will be released in a few weeks which will contain all the quick fixes including 255.  At this point, I'm going with the philosophy that if it isn't broken, don't fix it.  Perhaps you're in the same boat that I'm in.  Try rolling back a fix or two and see if you have better luck.  I hope the best for you.

I'm not sure you guys understand how updates work. A bug that appeared in QuickFix 255 might very well have been fixed in X1c. Each update is a continuation of the last with new changes/ fixes happening throughout the process. It's not an amalgam of different updates put together, so an issue you experienced in QF255 won't necessarily happen with X1c.

Its also very important to remember that the QuickFixes are not officially tested updates, but rather 'hotfixes' that address very specific issues. If you hadn't experienced the issues listed in a QuickFix's change log then you probably shouldn't use it.

If you're having issues with QF255 then go back to X1b or QF246 (if it addressed issues you were having with X1b).

SP

First off, don't call me 'son'. Second, my post is in response to the guys above me who said they were having issues with QuickFix 255 and were hesitant to update to the upcoming X1c patch because it contains the previous QuickFixes. I'm merely trying to explain how the updates actually work, as there is obviously some confusion about it.

SP

That is irreverent. You should show respect to myself and the others who mod this forum. Period. Hopefully, my explanation of how the updates work will help the OP and the others who actually posted on topic in this thread.

SP

Seth Perlstein [Cakewalk
]

I'm not sure you guys understand how updates work. A bug that appeared in QuickFix 255 might very well have been fixed in X1c. Each update is a continuation of the last with new changes/ fixes happening throughout the process. It's not an amalgam of different updates put together, so an issue you experienced in QF255 won't necessarily happen with X1c.

Its also very important to remember that the QuickFixes are not officially tested updates, but rather 'hotfixes' that address very specific issues. If you hadn't experienced the issues listed in a QuickFix's change log then you probably shouldn't use it.

If you're having issues with QF255 then go back to X1b or QF246 (if it addressed issues you were having with X1b).

SP

Well that's just the point isn't it isn't it. For quite a few of us the updates don't work.
And how do you know that those users applied updates un-necessarily. That's an assumption on your part.
 
And as for respect - if you want it you have to show it. Nothing respectful in your last couple of posts in this thread.
 
 

I'm sorry if you think I was being negative or dark, but I was simply trying to explain how the update process works. Hopefully it makes sense to you all now so that you won't be afraid to try out X1c when it ships.

Don't let us get ya down, ol pal.  We're an ornery bunch.  Rock on.
 
 
Edit:  Never mind.

mudgel

Seth Perlstein [Cakewalk
]

I'm not sure you guys understand how updates work. A bug that appeared in QuickFix 255 might very well have been fixed in X1c. Each update is a continuation of the last with new changes/ fixes happening throughout the process. It's not an amalgam of different updates put together, so an issue you experienced in QF255 won't necessarily happen with X1c.

Its also very important to remember that the QuickFixes are not officially tested updates, but rather 'hotfixes' that address very specific issues. If you hadn't experienced the issues listed in a QuickFix's change log then you probably shouldn't use it.

If you're having issues with QF255 then go back to X1b or QF246 (if it addressed issues you were having with X1b).

SP

Well that's just the point isn't it isn't it. For quite a few of us the updates don't work.
And how do you know that those users applied updates un-necessarily. That's an assumption on your part.
 
And as for respect - if you want it you have to show it. Nothing respectful in your last couple of posts in this thread.
 
 

As I said before, the QuickFixes are not tested and should only be used when the specific problems arise that they are designed to fix. Because they are not tested they might cause other issues, which is what could be going on with the OP and the other following posters who had uses 255 and had experienced instability.

It is important to understand this when using a QuickFix. It is also important to understand that you can go back to the X1b release build or to an earlier QuickFix, and that issues with QuickFixes don't necessarily mean that X1c will have the same issue(s) even though the QuickFix is a 'part' of X1c.

Also, X1c can be installed right on top of release build X1 so you don't have to install X1a, X1b, QuickFies, etc. then X1c.

Hopefully that makes sense.

SP

Why has this board gotten SO contentious? Geez. And I do think "son" or "ol pal" would rub me the wrong way in a professional setting as well (and I am FAR from a fanboy). 

Jerry, did you try just installing the 32-bit version? You said in your post a lot of your plugs are older, and I listened to you site, and you seem to primarily a soft synth/virtual instrument composer. What plugs are you using? Did you cross-reference them with the one on point #10  http://forum.cakewalk.com/tm.aspx?m=1862515


Assuming you are proficient with computers and correctly installed everything and the drivers are up to date, it should be stable. I don't care as much for X1 as I like 8.5; but it is stable.

hockeyjx


Why has this board gotten SO contentious? Geez. And I do think "son" or "ol pal" would rub me the wrong way in a professional setting as well (and I am FAR from a fanboy). 

Jerry, did you try just installing the 32-bit version? You said in your post a lot of your plugs are older, and I listened to you site, and you seem to primarily a soft synth/virtual instrument composer. What plugs are you using? Did you cross-reference them with the one on point #10  http://forum.cakewalk.com/tm.aspx?m=1862515


Assuming you are proficient with computers and correctly installed everything and the drivers are up to date, it should be stable. I don't care as much for X1 as I like 8.5; but it is stable.

It would not make much sense for me to install the 32 bit version. The library, Pro Requiem, makes use of a lot of gigabytes of data, more than a 32 bit OS or host can handle.  That's the only reason I "upgraded", to run this really nice library.  Funny thing is, I am usually really excited about something like this.  But this time it was all caution and planning, and an intuitive sense that this might be a mistake.  I've submitted bug reports to Cakewalk and nearly all, except for the crashing, have now been verified as bugs.  I can always load old files without their respective 32 bit plugins, that doesn't bother me, and most of my plugins are 64 bit, if I gave the impression that most were 32 bit I didn't mean to.   The 64 bit seem to work.  The bug in the staff view where the instrument pane does not sync with the active track is the dealbreaker for me.  This means that not only can you not hear an instrument you are playing without leaving that view, but also when you switch to another view, like event list, you won't have the instrument you're focusing on be the one in the event list.  That alone will inspire MIDI programming mistakes.    Thanks for the suggestion though, if I could do that I would.   But then there is no point in X1 at all as the new choir library will be too limited.  No, I just reinstalled the old DAW, with Sonar 7 and have been composing and forgetting about changing that which has worked so well for so long.  Maybe X1d or X2 will get it right. 

Jerry
www.jerrygerber.com

Son
1) A term of endearment for someone, usually a friend. Mostly refers to a male, but sometimes female.

Dude
A word that americans use to address each other. Particularly stoners, surfers and skaters.

Ol Pal who has been on the forum for some time, I'd bet my bippy the term he used was meant in the above manner.

It's pretty sad how folks are so easily getting their feathers ruffled and not giving others the benefit of the doubt.  Oh, wait, that would be like showing respect.

My bad.

OP.
The quick fixes are not tested so they are "USE AT YOUR OWN RISK".  They are also easy to revert back to the original.

An update such as X1C is a tested update which is supposed to fix certain issues, and sometime includes new features.
 

G'night.

Jerry,

It was a response to Bub saying it was the second email today saying someone "moving on". 

After the first, say 30 of those, you just blank out.   

I wasn't considering you among them, I just was trying to help.


I think we all want a fully-functioning/minimally frustrating product the we plunked down our hard-earned bank to get. I do hope X1c gets us closer to the goal.

yorolpal


I'm 59.  How old are you?

Are you serious? Don't bother telling everyone your age if you're gonna ACT like a child. You would never call a customer service agent that you're on the phone with "son", or at least without expecting a "umm...excuse me sir?" in response. You said it yourself, respect is earned. And you won't earn anyones respect by calling a company representative "son" and then following up with "i'm 59, how old are you?" I don't care if you're 59 or 95, you don't call someone "son" unless its someone you personally know, no matter what their age is. Grow up. I'm just glad you apologized... that show's your at least sensible.

Seth Perlstein [Cakewalk
] 

Greg, 

Frankly speaking, I'm not going to let someone here insult me through name calling, so I will stick up for myself (not talking about you, obviously). I'm sorry that you see that as bad form. 

SP 

Seth, come on now. I just finished watching your AudioSnap2.0 video not too long ago that YOU narrated, and then I see stuff like this. You are representing a company, be pofessional. You think Cakewalk would like you talking this way? What about Roland? Because I see both of their names up there on the top-left corner. If I was representing a company, I wouldn't dare "stick up for myself" or lecture a CUSTOMER on how to respect, for the simple fear of getting fired. Like I mentioned before, I would never expect a customer service agent talk like that to me on the phone, and would report them in a heartbeat if they did. I would report you too if you said that to ME, granted I would never say anything to you in the first place that could be confused for an insult.


As for me, I do hope that X1c solves the stability issues once and for all. It's well into the second week of August, and still no solid release date. So hopefully that means they are taking their time to make sure it's stable instead of rushing the release (we can only hope). I've been hearing a lot of horror stories about crashes and whatnot... if it happens on Jerry's i7 with his 16GB of RAM, what's to keep it from my i5 with 4GB? I'm crossing my fingers for X1c and keeping my hopes up.

hockeyjx

It was a response to Bub saying it was the second email today saying someone "moving on". 

After the first, say 30 of those, you just blank out.   

Yeah, and the people who shouldn't have, have blanked them out as well.