I think I may have found out how to reproduce the Prochannel drawing bug

I have been liking X2 a lot, but still getting the occaisional crash when I would select a master or sub group on the console (I have had this in X1).  I noticed that the inspector in ProChannel view would not pain correctly just prior t a crash, or would not paint correctly and then crash if I touched it.  I think I have found what is happening and how to reproduce it, but I would like someone with dual monitors to see if that can reproduce it also.

Test 1 (reference)
Open the Normal.cwt template. Slide the busses into view, and insert an Audi  track.  At this point my view shows everything on my right screen, with tracks on top, colsole in multidock on teh bottom, browser on right and inspector on left.  Inspector is set for ProChannel view.

a)
Click on the inserted console strip for the track and then the master bus - watch the Inspector view change.  Repeat this bu selecting track and then the Master in the track view - again the inspector should update correctly.

b)
Drag the console to the left screen, and once more select Audio Channel, and then the Master Channel using the console view.


Return the console to the multi dock.

Test 2 (fault)

Select the Master Buss, and in the inspector, right click on the title bar for teh Console Emulator and insert th eLeveller, and then the concrete limiter.

Repeat test a) Everything should be fine.

now repeat b) Click on the Audio Input Channel Strip should be fine ( and the metronome should be good too).  You should still be able to select input and master in the track view.   However, when you click on the master console strip, the Inspector will mis-paint, and Sonar will either crash straight away, or will wait for you to touch the inspector and then crash.

[UPDATE] I was ble to reproduce this when I dragged the console view from the multi-dock to the same screen

I have played with other modules in the ProChannel, and it appears to be related to the overall height of the modules and not the type or order. 

So in summary
    The offending Prochannel must be loaded with enough modules to trigger the condition. 
    The Console view must be undocked (but can be on same screen).
     The strip with the "overloaded" Prochannel must be clicked in the undocked console view.



AND - curiously
This seems to only happen when the master has the "overloaded"  Prochannel - I hve not been able to reproduce it by loading up the metronome, or adjacent audio channels.  In addition it seems the transition to cause the failure must be from input to master and not bus to bus.

I do have the Quick Fix installed.

Cheers

Grif



Quad Core Zeon, 8GB, NVidia Silent 8600, 6TB across 4 SATA drives, Win7 64, Presonus Studio Live 

Do you get the "Fault Module Name: StackHash_1dc2"

I shall test it out tomorrow when I have more time.

synkrotron


does the fault reporter pop up?

It did once and I pushed it through.  hat was when I mis-painted the prochannel in the inspector but did not immediately show the windows dialog.  The fault reporter came up when I clicked on the pro channel in the inspector.


Cheers


Grif

SteveGriffiths


I have been liking X2 a lot, but still getting the occaisional crash when I would select a master or sub group on the console (I have had this in X1).  I noticed that the inspector in ProChannel view would not pain correctly just prior t a crash, or would not paint correctly and then crash if I touched it.  I think I have found what is happening and how to reproduce it, but I would like someone with dual monitors to see if that can reproduce it also.

Test 1 (reference)
Open the Normal.cwt template. Slide the busses into view, and insert an Audi  track.  At this point my view shows everything on my right screen, with tracks on top, colsole in multidock on teh bottom, browser on right and inspector on left.  Inspector is set for ProChannel view.

a)
Click on the inserted console strip for the track and then the master bus - watch the Inspector view change.  Repeat this bu selecting track and then the Master in the track view - again the inspector should update correctly.

b)
Drag the console to the left screen, and once more select Audio Channel, and then the Master Channel using the console view.


Return the console to the multi dock.

Test 2 (fault)

Select the Master Buss, and in the inspector, right click on the title bar for teh Console Emulator and insert th eLeveller, and then the concrete limiter.

Repeat test a) Everything should be fine.

now repeat b) Click on the Audio Input Channel Strip should be fine ( and the metronome should be good too).  You should still be able to select input and master in the track view.   However, when you click on the master console strip, the Inspector will mis-paint, and Sonar will either crash straight away, or will wait for you to touch the inspector and then crash.

[UPDATE] I was ble to reproduce this when I dragged the console view from the multi-dock to the same screen

I have played with other modules in the ProChannel, and it appears to be related to the overall height of the modules and not the type or order. 

So in summary
    The offending Prochannel must be loaded with enough modules to trigger the condition. 
    The Console view must be undocked (but can be on same screen).
   The strip with the "overloaded" Prochannel must be clicked in the undocked console view.



AND - curiously
This seems to only happen when the master has the "overloaded"  Prochannel - I hve not been able to reproduce it by loading up the metronome, or adjacent audio channels.  In addition it seems the transition to cause the failure must be from input to master and not bus to bus.

I do have the Quick Fix installed.

Cheers

Grif



Quad Core Zeon, 8GB, NVidia Silent 8600, 6TB across 4 SATA drives, Win7 64, Presonus Studio Live 

Confirmed, reproducible on my system (3 monitors, but I tested using 2). With quick fix 308 installed. I followed the steps, and it crashed exactly at the same spot as you mentioned and I've also submitted the auto-crash reporter.


Just like to check.. do you have aero running ? I'm running classic look and feel.

Cheers!

tomixornot

Confirmed, reproducible on my system (3 monitors, but I tested using 2). With quick fix 308 installed. I followed the steps, and it crashed exactly at the same spot as you mentioned and I've also submitted the auto-crash reporter.


Just like to check.. do you have aero running ? I'm running classic look and feel.

Cheers!

I am running Aero, so that means we can reproduce it with and without.


Cheers


Grif

SteveGriffiths

tomixornot

Confirmed, reproducible on my system (3 monitors, but I tested using 2). With quick fix 308 installed. I followed the steps, and it crashed exactly at the same spot as you mentioned and I've also submitted the auto-crash reporter.


Just like to check.. do you have aero running ? I'm running classic look and feel.

Cheers!

I am running Aero, so that means we can reproduce it with and without.


Cheers


Grif

I've just filled a new problem reporter on this.

Hi John,

   It seemed ok with default PC, but  it certainly seems triggered by click on Master bus in CV after clickin gon channel bus.  I just listed what I could do to make it fail every time

Cheers


Grif

John


I have seen this problem. I have not had the PC overloaded yet it did crash upon clicking on it. I think its about having the CV floated.

Yes , I got a crash following your steps . 
Crashdump was sent .
I`m on Win 7 32 bit with the latest quick fix for X2 .
All the best
Jan

Reported?
http://www.cakewalk.com/support/contact/problemreport.aspx