Screen Sets Pause audio for a second!

I have a brand New Roland Interface quad Capture. Its been a night and day interface from my Tascam fw 1884 as far as the drivers Go, I haven't seen any issues till today, not sure if its related to X1c or not, just cause I never used screensets before because of various reasons.. 
 Whats happening is while Playing back when I hit any screen set number I get a pause in audio while the new screenset is loading, Is this normal? 

I just call support ,, We tried classic mode no good same thing ..
 Faster I stand correct its not a pause its a drop out your right, and for a slip second I hear the track go out of sync.
  I remember you saying something about disabling the floppy drive in the bios wonder if thats the problem..   I have a pretty decent computer , 2.8 quad core, ssd Hd, 4800hd crossfire graphics card, 8 gigs of ram. Do I need a better video card ? Do I have to spend $300 on a video card to have it run flawless? I so despise pause's pop clicks and noises , its just soooo unprofessional when you have clients in the room. 

Does it drop out all the time? My system is under powered by Cakewalk's recommended minimum and lower than yours by the look of it. I do get the occasional drop out changing SS, but I have to provoke it a bit. ie. flick through 3 or 4 in as many seconds.

Other than that sometimes the GUI will slow up but the audio remains unaffected. I certainly don't have a good video card. See my earlier post for the "experience" score

The floppy disk controller tip worked for me but just speeded up the changing process rather than make it more reliable.

djjhart@aol.com


I dont know if it dose it all the time , I had a few crashes way back and never used them since then, I decided to give it try again today and the first click to screen set #2 dropped out the audio. 
. Clicking today I notice drop outs when ever I click a new screen set, and its a pretty full project so I guess thats the catalyst, oh well
I was going to do some mixing ect , and thought what the hell lets use the screen sets . Bad experience then and Bad experience now. :(    From the way support was talking it is what it is.. Nothing you can do. To me it makes no sense why we should have drop outs when clicking a screen set.

 
Btw Thanks Guys for your Responses!.
John

John,

I don't know if you did it already - but the "disabling floppy" in the BIOS made a HUGE differenece for me when I first tried X1.

I haven't touched it in a while, but I do intend to install and check out X1C so if there's something different with screensets, I should be able to see that.    But in the meanwhile do disable the floppy in bios if you haven't.

My MB dosen't support floppy drive .. Oh well..

This must be system specific because with the Javier Conon demo project playing back I can change screensets with no dropouts, pausing, or anything at 64 sample (1.5ms) latency. I'm running an i7 on an SSD boot drive with Win7 X64, so that certainly doesn't hurt. My GPUs are modest, though, as I have two nVidia 8400Ggs cards (512meg RAM each) in the system.

SP

It's not buggy as it does everything it intends to do. But Screensets require a quick machine to perform smoothly during playback of large projects.

SP

Seth Perlstein [Cakewalk
]

This must be system specific because with the Javier Conon demo project playing back I can change screensets with no dropouts, pausing, or anything at 64 sample (1.5ms) latency. I'm running an i7 on an SSD boot drive with Win7 X64, so that certainly doesn't hurt. My GPUs are modest, though, as I have two nVidia 8400Ggs cards (512meg RAM each) in the system.

SP

I installed X1C - after not using X1 for many months.   I was rechecking all my settings - things looked fine.

Previously Screensets were working fine for me.   Not now.  I just crashed twice changing Ssets.

THe only project loaded was my normal.cwt which has maschine and some plugins.   I wasn't in playback - just idle.

I'm going to investigate more and see if there are .dmp files to send up to problemreporter;  but I just can't seem to get a groove on with X1 yet for some reason.

It's Gapless Audio Engine 2.0.

'Member those threads? Good times...

Gapless Audio Engines are so last decade:-)

ba_midi


well, more bad news .... crashing often here.

So I'm putting X1C away --- i just don't time for playing mr debugger.

Oh well.

Oh nooess!

Not sure I even want to bother testing X1C myself, since X1 is not even installed right now.

I must say, after upgrading every year since PA9, I have used a lot of my time debugging - and the issues were almost never related to my system in all those years, but instead to Sonar or occasionally a plugin. There is always this chorus of "works fine here, must be you" but I find many of those reports are from what I would term superficial users (no offense anyone) who use a subset of the available features only and don't happen to encounter problems.

Now that I am staying on 8.5.3, I am able to be more productive instead of messing about with new bugs and forced workflow changes. It has done something nice for my head to have limitations and bugs that I know well and just ignore the "next big thing".

I'll watch for a major release or two to see Cakewalk's new approach now that they say they have put down new foundations with skylight etc. I'd really like to see major work go into getting everything we have now working properly before more bells and whistles and plugins are bolted on to the fledgling new interface. If that were done, I would consider returning to the frequent upgrade path, but I have just lost my taste for it after X1.

D.

Seth Perlstein [Cakewalk
]

cornieleous

ba_midi


well, more bad news .... crashing often here.

So I'm putting X1C away --- i just don't time for playing mr debugger.

Oh well.

Oh nooess!

Not sure I even want to bother testing X1C myself, since X1 is not even installed right now.

I must say, after upgrading every year since PA9, I have used a lot of my time debugging - and the issues were almost never related to my system in all those years, but instead to Sonar or occasionally a plugin. There is always this chorus of "works fine here, must be you" but I find many of those reports are from what I would term superficial users (no offense anyone) who use a subset of the available features only and don't happen to encounter problems.

Now that I am staying on 8.5.3, I am able to be more productive instead of messing about with new bugs and forced workflow changes. It has done something nice for my head to have limitations and bugs that I know well and just ignore the "next big thing".

I'll watch for a major release or two to see Cakewalk's new approach now that they say they have put down new foundations with skylight etc. I'd really like to see major work go into getting everything we have now working properly before more bells and whistles and plugins are bolted on to the fledgling new interface. If that were done, I would consider returning to the frequent upgrade path, but I have just lost my taste for it after X1.

D.

With all due respect, I wouldn't let ba_midi's personal experiences sway you one way or the other.

Also, this thread is about Screensets so lets stay on topic.

SP

While I have a feeling you mean that in a somewhat negative manner, I do agree that my personal experience shouldn't sway ANYONE.   We know there are those who are doing fine with X1 (I don't know about "C" yet, too soon to hear from everyone), so I have no doubt there will be many doing fine with C too.

It's the screensets that keep crashing for me, btw - so it is on topic.   And it wasn't happening before, as I mentioned.   So it's a bit strange in that regard.

But as I said, I'm not interested in playing mr debugger, sorry to say;  you'll have plenty of those when need be I'm sure.   I'll just keep my eyes open for X1D or whatever comes down the pike.

I'm definitely wanting to get X1 going here, I just don't have time to mess with problems.   And I'm not having problems with 4 other major DAW softwares at this point.   So what can I say.

I'll keep my eyes and ears posted here for more follow up.

Seth Perlstein [Cakewalk]

My GPUs are modest, though, as I have two nVidia 8400Ggs cards (512meg RAM each) in the system.

SP

I've been using screensets a lot lately. I really like the idea. I just loaded a big project in X1C and changed screensets on the fly with no dropouts, but I did hear a slight pop. The project is 26 wav tracks plus Session Drummer 3 (unfrozen) @ 96kHz/32bit, so I think if I was going to have trouble, I would with that project.
 
Hi Seth, we talked about this a long time ago, but I'm still a little confused on it so hopefully you can set me straight.

I bought an ATI equivalent to the Nvidia 9500GT because the ATI was fanless and had 1GB RAM. The ATI died so I put the Nvidia back in. When I did, I noticed the refresh rate of X1 got worse, and the picture data took forever to draw for waves. Plus the other thing I've noticed, when using the Waveform preview on a bus, it doesn't line up with the Waveforms of the tracks. It's a good second or two off. I never looked that close before, so it may have been happening with the ATI as well.

My question is, I know adding a second 9500GT for processing power is not going to help, but do you think adding a second one for the additional 512MB RAM would help?

Thanks,

Bub

djjhart@aol.com


My MB dosen't support floppy drive .. Oh well..

Did you check the BIOS?
 
I have worked on comps in the past 2 years that did not have floppy connectors but did have BIOS settings.
 
j

Seth Perlstein [Cakewalk
]

No, I don;t mean it in a negative manner at all. Its just that you've had Screenset crashing issues since day one while nobody else has, and we can;t replicate your issues. With all due respect, I think you've got something funky going on with your system, and I don't mean that in a negative manner at all.

But to hear other users not want to use X1 because of these unpredictable issues is a little worrisome.

Again, not negative at all, just saying.

SP

That's not all correct actually.  INITIALLY I had screenset issues (others did too) and it was mostly due to that Floppy BIOS thing.   I then updated my video card (Doubled video ram, etc) and things were fine with screensets.

It was other things that kept me from using X1 actually.


As for other users -- this is a public forum.  Every day I / we see various opinions and experiences.  It's normal.   And I definitely don't suggest that others stay away from X1 because I might or do.   Everyone should see what works for themselves, always.

However I *strongly* disagree about my system.   Seth, I've been switching between 8.5.3, Live, and Studio One very much lately.   I am not having any crashing issues or other weirdness.   Only with X1 do I seem to struggle.    I just think it's more of a "X1 wants to see certain types of hardware configs" more than "my" config so to speak.

IOW, I think with a lot of the new features and approaches in X1,  it probably is a better fit with certain types of setups -- like x64, more RAM, etc.    Speculation on my part, but based on my doing tons of music work with the DAWs I mentioned above without issues, it's just not reasonable to point to my "system" -- which really is speculation on your part ;)

Anyway - most importantly - I will continue to keep my eyes open for improvements, etc.   And I do intend to put together a Windows 7 system when time frees up (which it hasn't lately) - so maybe with a COMPLETELY fresh environment, X1 will find a home here too some day.