Structure v1.1 error 9031 and 9019

[insanesounds]

Well for me, as I've written, all of my drives are formatted as per Avid's Windows recommendations (32k allocation, NTFS). 8.0.1 has not had an error all day. Anytime I had that error when using 8.0.4 was with Structure present but since it's working fine with 8.0.1, something in the PT code changed between the versions (yes, i know that's obvious!) - as I remember a lot of people had probs with the white noise issue for a spell with 8.0.3. I have noticed that when I hook up an external drive from a client and its not fast enough I can get that white noise issue. Now I always drag off files to my drives anyway so that's never an issue anymore. So something has changed in how PT accesses the drives in 8.0.3 and later I would presume. Pretty much we're just waiting on you to encounter the issue. Quite honestly, if my system stays like this with 8.0.1 and trouble free, I'm totally content, but I realize future releases need to get this issue fixed.

[Alio 45]

Have there been any developments on this. I've been working on location for two weeks and not used Structure but i'm about to start using it again.

All my drives are formatted Mac OS Extended (journaled).

Al

[Alio 45]

well it seems I was mistaken. I'm getting this error message even when I'm not using Structure.

Al

[suicune]

Yes whilst structure came under a reasonable amount of suspicion I think the general consensus was it was not responsible. There isn't really an update or solution yet except to go back to PT 8.0.1cs2 or earlier. If you want to read some other threads on the subject the links are:

http://duc.digidesign.com/showthread.php?t=278809
http://duc.digidesign.com/showthread.php?t=265212
http://duc.digidesign.com/showthread.php?t=264102

There's probably more but those are the ones I was aware of.

[DigiTechSupt]

Originally Posted by suicune

Yes whilst structure came under a reasonable amount of suspicion I think the general consensus was it was not responsible. There isn't really an update or solution yet except to go back to PT 8.0.1cs2 or earlier. If you want to read some other threads on the subject the links are:

http://duc.digidesign.com/showthread.php?t=278809
http://duc.digidesign.com/showthread.php?t=265212
http://duc.digidesign.com/showthread.php?t=264102

There's probably more but those are the ones I was aware of.

That's what we're finding - no connection to Structure.

What we *are* seeing is that these errors are drive related - usually due to using GUID when you should be using APM and vice versa, or using a system with mixed APM and GUID drives. Some people have said they've checked this and re-partitioned (in most cases we're talking about the single, monolithic partition scheme for the drive, not actually dividing the drive up into several partitions...) but it hasn't solved it.

If possible, can anyone experiencing this detail their drive setup (how many, what type, brand, connection, etc) and exactly which partition scheme each drive is using, as well as when it was last erased/partitioned and which software was used to do it? Ideally you should use Disk Utility.

[Alio 45]

I've just created a new session. One stereo audio track. One track of Addictive Drums, On Track of Stylus RMX, One track of Velvet. I then wanted to add bass so I opened Structure and guess what......

I don't know.

I have a major show opening in less than three weeks and the producers are coming down on me for the tracks, I don't have time for this or to mess about with drives, etc.

It was working fine on the drives I have before the upgrade.

500 GB internal mac drive (3 partitions)
1TB Lacie FW 800 Drive (4 Partitions) into 500 GB FW Western Digital drive (5 partitions)

Al

[Alio 45]

I had the foresight to save before i opened Structure. i just opened the saved session and used a bass from Expand instead and it's working fine. I'm also using GPO4 and EW Play in the same session with no problems.

I don't know if it is Structure or not but I have lost confidence in it. Even after buying the PTIEP and the Goliath library.

If this persists i will have to look for another DAW if I'm to complete this job.

Al

[andreªs]

Originally Posted by DigiTechSupt

That's what we're finding - no connection to Structure.

Sorry, but I don't think so. When I remove Structure, those problems won't occur. For me it's absolutely related to Structure. I use all kinds of different VIs without having those errors.

-Andreas

[suicune]

If possible, can anyone experiencing this detail their drive setup (how many, what type, brand, connection, etc) and exactly which partition scheme each drive is using, as well as when it was last erased/partitioned and which software was used to do it? Ideally you should use Disk Utility.

Sure thing digi (notice they've not enforced AvidTechSupt on you yet ):

Bay 1 System drive: :
300GB Seagate ST3250820AS P (as supplied with MacPro)
GUID partition table - 1 partition
Mac OS Extended (Journaled)
Never been reformatted or replaced since we got the mac, so was done however apple did it!

Bay 2 Samples Drive:
500GB WDC WD5000AAKS-75TMA0
GUID partition table - 1 partition
Mac OS Extended (Journaled)
Formatted using disk utility when I installed it - approx 3 yrs ago

Bay 3 Current Client's audio drive:
300GB MAXTOR STM3320820AS
GUID partition table - 1 partition
Mac OS Extended (Journaled)
Formatted using disk utility at the start of their previous album summer 2008

Bay 4 Main audio drive:
1TB Seagate ST31000333AS
GUID partition table - 1 partition
Mac OS Extended (Journaled)
Formatted using disk utility when I installed it Jan this year

All passed TechToolPro's suite of disk tests including surface scan, all were optimised April this year just prior to me giving up on 8.0.3 altogether. No firewire disks were in use when we had the errors, they were the first thing I disconnected.

Machine is MacPro 2x2.66 Dual-Core Xeon, 5GB RAM, OS 10.5.8.

If the errors were structure's fault that doesn't explain why they don't happen in 8.0.1 with the same version of stucture. So come on guys, post your disk setups like they asked. I really wanna try that HEAT thing, but there's no way I'm upgrading again until this been either fixed or at least the reason and a workaround found. I'll reformat all the drives if I need to - as long as I know it'll definitely work!

[Alio 45]

Any news yet Digi?

I did a session last night with many VIs and the only time I had 9031 and 9019 errors was when i tried to use structure. Other than that the session was trouble free.

Al