While I am working great and fast with my new system and AL 7.2 I come to the same problem as before. I am working at dual monitors. When I zoom out the timeline to full (frame) I got a freeze but I noticed that is not a "real" freeze because task manager reports Liquid to work. All of 4 cores are going at 40% like the they need to render something. I just thought on disabling the 2nd monitor WHILE this is happening and guess what? Liquid returns to normal. This could mean that this is a driver issue. I am not sure but as I posted a long time ago this is happening only on a BIG timeline like I am now (50 minutes), not on smaller ones.

After some timeline scrubbing and it happens at 1 monitor setup as well. Waiting some time then things are going to normal again.

At both instances waiting some time wakes Liquid. I think this is a kind of a bug or driver problem. 

I get that with a 2900xt card. Actually, the computer just blue screens. The behaviour i get is if i configure Liquid within the software to use duel monitor, it works fine but as soon as i close liquid and try going back in, the computer blue screens.

More interseting is that this is happening not on the center of timeline (in and out from one monitor to another) but when I try to scrub out of the right edge or out of the left edge!!!

After a while system reverts to normal. Having render on or off has no affect. Its the same. 

This is happening for zoom 10 and under. 

zck:

I get that with a 2900xt card. Actually, the computer just blue screens. The behaviour i get is if i configure Liquid within the software to use duel monitor, it works fine but as soon as i close liquid and try going back in, the computer blue screens.

I don't think we are talking about same issue here. I don't have any blue screen at all and Liquid comes back to normal again after some time.

Read carefully what I wrote. I see this only at zoom 10 and under. Otherwise it works great.
 

Yes it's happening only to big timelines with hundred of cuts and effects wherever I scrub and for zoom 10 and under.

That's what I get each time at MTBF file.

2007-10-06 04:37:39.812=UMI.EXE - Was Killed with 00000000
2007-10-06 04:37:40.359=StudioU.mod - Crashed with 40010004 ,1 Play,477 Seek
2007-10-06 04:37:40.437=CLOSE Liquid ,1 Play,477 Seek

For this to happen it must be first start the playback and then stop by space.

After this if I zoom full and try to scrub right or left to seek I have that froze. But as I said at task manager it says that Liquid is working. I hear the fan of CPU to struggle as it reaches 45%. 

I have 237 cuts and a lot of FX's at a 51 minute timeline with 5 vob's x2 minutes each.

And this is from STATS. 

 

Liquid 7.20 Build 4296 at 2007-10-06 04:37:40.359
 #  Action                                                          Count  Duration(s) Last time
-----------------------------------------------------------------------------------------------------------------
  2: Play                                                               1         0    2007-10-06 04:37:11.875
  3: Seek                                                             477         0    2007-10-06 04:37:12.765
  8: VMChange:[768x576@25.00 1.33]                                      2         0    2007-10-06 04:35:35.750
  9: AMChange:[0@0]                                                     1         0    2007-10-06 04:35:35.640
 10: AMChange:[2@0]                                                     1         0    2007-10-06 04:35:35.750
 11: AMChange:[2@48000]                                                 3         0    2007-10-06 04:35:42.187
 12: AMChange:[18@48000]                                                1         0    2007-10-06 04:35:35.750
 24: DeviceChanged                                                      3         0    2007-10-06 04:35:44.906
 25: VMChange:[720x576@25.00 1.33]DV (AVI)                              1         0    2007-10-06 04:35:42.546
258: Fire:CompRec:00000fa5                                              2         0    2007-10-06 04:37:11.796
266: Fire:CompRec:00001b8c                                             54         0    2007-10-06 04:37:07.500
298: Fire:CompRec:00001b8d                                             27         0    2007-10-06 04:37:05.312

Another candidate for a move to the hardware forum.

I hope that someone take a look at that seriously. I am not sure if someone else delivers 50' shows with Liquid so we could share opinions.

But it's a long time I have posted this. And is the same with 2 different systems.

I would like to know what's happening but something isn't right for sure. 

Uninstall 7.9 drivers and install 7.8 without CCC.

Same but now Liquid comes to life faster than before after the fake freeze. 

Thought that it was the Logitech center uninstall it but it happens the same.

Scrubbing out of the 2nd monitor at right or out from the 1st monitor at left time line freezes, Liquid seems to work and it comes back after some seconds.

This is a bug for long time lines from ZOOM 6 and under.
 

I am very close nailing this down. I will run some more tests.

I think it may has to do with Smartsound... 

Well listen good because I found the problem which haunts me for some time now or I hope that I did.

It happens only then and like an experienced user of Liquid (and former beta tester at LE 5 ) I have found something that it is too big detail.

It happens only on big time lines and when you use a dissolve between 2 audio tracks, the one being smartsound and only again for zoom of 6 and under.

Then the timeline freezes and if you click the middle (third button) wheel button of a Logitech or maybe other mouse, you can scroll left or right the timeline (you must have set the wheel to scroll) and to avoid that specific point. Then and only then Liquid returns to normal. If you delete that dissolve everything is fine.

You could tell me that we must not set any dissolve at a smartsound track but I don't agree because it should work right.

Please report this issue as I can't do it and it is a bug. 

I deleted all the render files of the 51' project just to see at what speed and how is going to go with my Quad.

Unbelievable fast with up to 80% for all cores for the first 50% and then up to 50% for the rest 50%.

It did render my whole 51' timeline at not more than 4-5 minutes... 

Sverkalo,

I escalated your thread to our engineering team in Munich

Respect Bertrand.

Sapphire has brought out a version of 2900 which is called pro has 1GB of memory and costs 250 Euros...

 

About the problem I saw.  I have tested everything!

The problem occurs ONLY when the timeline is big with HUNDREDS of CLIPS, CUTS and EFFECTS. Everything is RENDERED. My both monitors are setup correctly.

There is no problem with 7.9 driver. It works excellent on every aspect. 

I repeat: 

It is working flawlessly UNTIL the time I add a dissolve between a SMARTSOUND track and a SONG which is a .wav or .mp3 file.

If I remove that dissolve everything runs smoothly.

This CAN NOT be a problem of hardware. 

P.S. Thank you Draske. 

Well that's even worse.

Even if timeline is empty it happens.

Adding a smartsound file and an mp3 44100 and add a cross dissolve between them.

Trying to zoom by holding down the down arrow and when zoom goes under 6 it freezes.

Holding the middle button and scrolling away from the point that the dissolve is wakes Liquid.

   

I'm not at my editing machine right now, but do you suppose SmartSound clips don't play nicely with audio sampled at other than 48KHz (or something along those lines)?

That's what I try to figure out.

When there is a dissolve between a smartsound track and an mp3 44100(which Liquid converts to .wav anyway) there is that freeze if you zoom fast and try to scrub then.

When I remove that dissolve everything works great. So the dissolve between it's the problem. 

What happens if you create the crossfade on two different tracks (SmartSound on one, mp3 on the other) using the keyframes instead of a crossfade effect? Don't forget, SmartSounds are very specialized audio tracks that work differently than just a standard audio clip. It would not surprise me that you can't dissolve from a SmartSound clip to an mp3 clip without issues.

In addition, I would suspect that if you export the SMartsound track as a regular WAV file, then do your dissolve, that the problem will disappear. Like Lew said, the Smartsound file isn't the same as other audio files, and is always subject to change, dpednding on how long the track has to be. So it is always ready to change, so its not a fixed length, unlike any other sound files.

I know but this must be fixed.

From 7.2 smartsound behaves a slot better and even if you enlarge it, it plays great.