Steps to take that might reproduce johnny first crash----

new project load Ueberscshall elestik player on Track 1 - 7
Load Rob Papen Predator on 8
Load virsyn tera 3 on 9 and 10

create four to the floor drum beat at tempo of 144
midi is spread out on each track...
Track 1 = kik
2 = snr
3- c ht
4 - o ht

Load single shot kik into Elastik vst on track 1
single shot clap into Elastik on track 2
single shot c ht in elastik on track 3
single shot o ht in elestik on 4

elastiks on 5 is loaded with a ride
elastik on 6 loaded with a crash
elastik on 7 is blank

8 bars of music have been created....

Predator is playing a bass line on track 8
Tera number one is playing a lead riff on 9
tera number two is playing a lead riff on track 10

track six elastik crash cymbal is being gated with camel space. all cymbals except for the ride, because it has not been written in midi yet have mackie mono six band eq cutting thier low end freqeuncy at around 500 htz

all elastik players are routed to a drums sub... ( I forgot about this so we will call it track 10, but really its track 8 and everything else moves up 1 ) and the drums sub mix, is nomad factory reverb, and nomad factory compresser....

the transport is on play. 8 bars are looped and going around and around.... click on elastik player on track 5 ( your ride cymbal sample ) to tweek proper setting of ( s ) --- s is a little green button that syncs to tempo I do this before I drop my midi notes in. and right at that second. as I click on the elastik that is on track 5 " Poof is Gone "

Altough the new build is a lot more stable I just got the poof crash when manipulating the "noname-eq" with a midi controller. Only one instance of "Surge" before the eq. Tracktion was still active in the task manager but when ending the process, and waiting for a minute or so, Tracktion disappeared and I was able to restart it...

Do you want us to post crashes other than poof to desktop type? I'm getting some truly evil blue screen of death occurrences.

Also getting really weird behaviour when recording audio and pressing "abort and start again" or whatever it's called.

I got the poof with the update from hitting the spacebar.

I have an edit that reliably poofs when pasting an automation curve from the master fader onto a track fader. It occurs at the paste command. Tracktion can be immediately restarted without issue.

AMD 4400 X2
Asus A8V
M Audio Audiophile Delta 2496
2 gb ram

I still got poof crash as well lately when loading a wave IR file in Reflection LE...

Hello,

I'm a new Tracktion 3 user. I was having trouble with the DVD installed version so I downloaded the latest update. I'm still having issues. I can hang the machine everytime by trying to launch the Kontakt VST on a midi track. I was also able to get SampleTank to crash. The machine just freezes up and I have to power down to get out of it.

I'm on an Intel based IBM 2.4 Ghz P4 machine with 512 meg of RAM. My CPU resources seem OK just before attempting to launch. I plan to add more RAM, but I wonder if that is the cause.

For soundcard, I'm using the EMU1212.

Any help would be appreciated.

One other item that might be useful is that I was able to launch Kontakt in the Tracktion V2 demo I still had installed.

Thanks,

Brent

Got a new poof crash, here.
Using the latest version of DFH Superior drum plugin:
Not always, but 90% of the time, clicking the "construct" button that should take you to the plugin page where you can change the kit pieces, will unceremoniously dump you to the desktop.

This is with the plug in a rack, WinXP, and T3033. Haven't tried it outside a rack 'cause frankly, it's not worth much unless it's in a rack.

edit: The plug and T3 seem to play nice when not used in a rack.
The plug works fine in a rack in T2. Looks like it's back to T2 for drums for awhile.

I got two types of crashes: a) T3 dissapears from screen but stays in memory and cannot be killed and b) T3 starts playing a loud "saw" tone and cannot even be closed.
Both crashes happen sometimes after some minutes when playing a song but I cannot say what exactly causes the crash, because I always did something different before that.
But what I can say is that these crashes do NOT appear here when only 1 core is used within T3. Anyway I am playing around with T3 for one hour now and all is working fine ...with 1 core. So maybe the problem is due to the multicore support.

Greets, Kristian.
Last edited by crisis-at-music on Thu Oct 04, 2007 1:21 pm; edited 2 times in total

I'm getting regular crashes with DFHS, though it's wrapped in eXT. Not just crashes, all kinds of horrible CPU spikes & glitches.

What version of DFHS are you running? T3 seemed fine with ver 1.3, but started crashing when I updated to 1.6.
I thought about wrapping it in eXT, but sounds like that may not be a good workaround.

1.6 is the only version I've tried.

Ok, I have to correct myself: the type b) of crash mentioned above does also appear when only 1 core is used. And the "saw" tone is a very short looped sound of what should actually be played in the song. It happens when I switch on "play" by pressing spacebar or double-click on an empty track with left mouse button. After this crash the GUI is hanging and T3 stays in memory even when I close it via the taskbar (so the GUI closes, but not the process...).
Two times it happened when I was only playing a sampled instrument (Sampletank or PAAX3 (SF2))in solo mode. So MAYBE there COULD be some problem with sampled instruments. At least I read about this idea just a few posts earlier.

I've seen several crashes (Tracktion just disappears) after copying filters to other tracks.

This is also a request for the Tracktion problem reporting tool so I can provide some feedback. (I'll send a PM as requested).

Regards,

Stuart.

"random poof crash"