T2 2.0.1.4
OSX 3.9
867 mhz G4
1G ram
Going from T1 superworkflow to T2 has put me of working with music for months. Why? I never get the answare for this:
Projects made in T1 much slower to edit in T2.
This is slow: Every step of zoom is a 10sec load!!!!
Every freaking step!!!! Say you going from full song view down to do a precise cut or moove, it will take 5 minutes at least!!! Because every step of the zoom takes the loading time of 10sec. And when you hold the zoom key down, it makes tiny steps of 10 sec zooms! T2 is at this time at 25% cpu, and at zero cpu when e to e is of.
I go so crazy i cant work like this. So I bought Live 5 instead, which is realy cool. But its kinda retard on the arangement part, arangements is better suitet in T, Cubase, logic etc. But I dont want to use yet another sequencer, I love T, and I also want to finish all my 2 year projects in it!!
Help!!!
OSX 3.9
867 G4
1G ram
if possible can export to new system:
(though ALL my vst presets made through and with T1 is corupted and unusable in other DAWs -T or others, why??)
W XP
Centrino 2GHZ
1G ram
T2: super slow zoom!
-
- KVRian
- 500 posts since 27 Nov, 2003 from Oslo, Norway
Last edited by Sleepwalker on Thu Oct 06, 2005 5:20 am, edited 1 time in total.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Just a word to the wise-- a thread title like that is misleading and untrue. It's not working for you, but it's working fine for thousands of people and therefore isn't unusable.
That out of the way, let's see if we can help:
Have you disabled 64-bit processing in the 'settings' page? It's a new T2 feature and the warning's right on the menu option that it can use more CPU. People with 3GHz computers don't seem to notice, but an 867 mHz G4? I bet it'd make a big difference.
I'm not going to 'push' the idea of getting a faster computer, but the fact is that T2 DOES consume a few more resources, especially in 64-bit mixer mode. Since it's consuming resources, you might be pushing an 867 to the max.
Regarding your VST presets-- did you save them as separate .fxb or .fxp? I haven't tried saving and then re-opening in another host, but it's something to look into. It's generally the plug-in's job and if the plug-in itself has a 'save' function, you should use that. However, T DOES provide an interface for plug-ins and if it's not doing the job, Mackie needs to sort it out.
Greg
That out of the way, let's see if we can help:
Have you disabled 64-bit processing in the 'settings' page? It's a new T2 feature and the warning's right on the menu option that it can use more CPU. People with 3GHz computers don't seem to notice, but an 867 mHz G4? I bet it'd make a big difference.
I'm not going to 'push' the idea of getting a faster computer, but the fact is that T2 DOES consume a few more resources, especially in 64-bit mixer mode. Since it's consuming resources, you might be pushing an 867 to the max.
Regarding your VST presets-- did you save them as separate .fxb or .fxp? I haven't tried saving and then re-opening in another host, but it's something to look into. It's generally the plug-in's job and if the plug-in itself has a 'save' function, you should use that. However, T DOES provide an interface for plug-ins and if it's not doing the job, Mackie needs to sort it out.
Greg
-
- KVRian
- Topic Starter
- 500 posts since 27 Nov, 2003 from Oslo, Norway
Sorry, I corected it! I was so frustrated and mad I probably woke up the neighbours, screaming out loud!!Lunch Money wrote:Just a word to the wise-- a thread title like that is misleading and untrue. It's not working for you, but it's working fine for thousands of people and therefore isn't unusable.
-
- KVRian
- Topic Starter
- 500 posts since 27 Nov, 2003 from Oslo, Norway
Because T1 turns into another version of T2 when I also have T2 installed, odly enough. But, yes thats what I had to do previously.. Only by now id like to use T2!!PT wrote:Why not keep using T1 if it was working for you?
-
- KVRian
- Topic Starter
- 500 posts since 27 Nov, 2003 from Oslo, Norway
I newer use 64 bit, its a G4!!Lunch Money wrote: Have you disabled 64-bit processing in the 'settings' page? It's a new T2 feature and the warning's right on the menu option that it can use more CPU. People with 3GHz computers don't seem to notice, but an 867 mHz G4? I bet it'd make a big difference.
I'm not going to 'push' the idea of getting a faster computer, but the fact is that T2 DOES consume a few more resources, especially in 64-bit mixer mode. Since it's consuming resources, you might be pushing an 867 to the max.
Regarding your VST presets-- did you save them as separate .fxb or .fxp? I haven't tried saving and then re-opening in another host, but it's something to look into. It's generally the plug-in's job and if the plug-in itself has a 'save' function, you should use that. However, T DOES provide an interface for plug-ins and if it's not doing the job, Mackie needs to sort it out.
Greg
I do have a new laptop, Centrino 2ghz, fast and frenzy. But its a hell of a jobb transfering all the projects with presets and all (I think?) not forgeting the files from mac to pc situasion..
Im thinking about bying a G5, finish my tracks, and return it to the shop.. ahem..
And yes, the presets dont work in other hosts. I wrote a note at the mackie/tracktion forum as well, so we will see what they say.. Neighter the vst plugins saved presets, nor the tracktions saved vst presets (fxp) works in other hosts. Even not in tracktion at windowsXP on another computer..
Also midi files exported from T1/2 is missing notes, and is not on time in the sequence when imported in other hosts... For instance getting some midi files exported to Live, I had to first import them to Cubase XS, edit and corect them, then export again to be able to get them corect, and imported in Live.
Sorry for having all this problems, and thanks for helping out, Greg!
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Apologize for having problems? No way! But awesomely cool of you to edit the title (which you didn't HAVE to do, but I'm glad you did anyhow. 
) and to clarify.
I'm not much further help, but I know that you CAN run Tracktion and Tracktion2 quite happily beside each other. I don't know Mac well enough to advise you on how to do it with Mac, but it works with PC.
Maybe a Mac person (or a Mackie person!) can help out.
I'll have to investigate the presets and MIDI file thing. I only own eXT as a second VST-loading host, but at least it's a start.
Sorry to hear it's not working optimally for you.
Greg
) and to clarify.I'm not much further help, but I know that you CAN run Tracktion and Tracktion2 quite happily beside each other. I don't know Mac well enough to advise you on how to do it with Mac, but it works with PC.
Maybe a Mac person (or a Mackie person!) can help out.
I'll have to investigate the presets and MIDI file thing. I only own eXT as a second VST-loading host, but at least it's a start.
Sorry to hear it's not working optimally for you.
Greg
-
- KVRian
- Topic Starter
- 500 posts since 27 Nov, 2003 from Oslo, Norway
Thanks for the kind words Greg! I had a moment of uncontrolled frustration when I wrote the topic, as youve probably understood by now!!
Ill wait for answers from mackie..
Ill wait for answers from mackie..
-
- KVRAF
- 3441 posts since 15 Mar, 2003
If you install T2 into a folder named T2 and T1 into a folder named T1 they will both be available to use.
I have them both and use T1 most of the time because I am on a win98 machine and T2 doesn't see my midi inputs.
I understand your wanting to use T2. You must have some sort of botched install. I use an old 500 mhz pc and T2 runs fine and the zoom is fine also. I just ran it stock
from the standard install.
I have them both and use T1 most of the time because I am on a win98 machine and T2 doesn't see my midi inputs.
I understand your wanting to use T2. You must have some sort of botched install. I use an old 500 mhz pc and T2 runs fine and the zoom is fine also. I just ran it stock
from the standard install.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Does this happen if you load a different preset in the colour editor? I've never heard of this with anyone else before, but at one point people were reporting issues with some skins causing slow graphical redraws. I don't know how easy it is to reinstall the graphics drivers on a mac, as i never use them, but that would be the next thing i'd try ....
I'd also check where the temp folders are set to in tracktion, and make sure there's actually space there.
As a last resort, close tracktion, delete or move your settings file, and reopen traction, in case something is corrupt in there. Does that make any difference? (although i'm clutching at straws here to be honest)
That's the things i'd try ...
I'd also check where the temp folders are set to in tracktion, and make sure there's actually space there.
As a last resort, close tracktion, delete or move your settings file, and reopen traction, in case something is corrupt in there. Does that make any difference? (although i'm clutching at straws here to be honest)
That's the things i'd try ...
"my gosh it's a friggin hardware"
-
- KVRAF
- 2009 posts since 9 Apr, 2003 from Cornwall, UK
Yeah, change skins..
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
this may not apply to everyone, but i was interested in the idea of the skins having an effect on general operation. i did a little test a little while ago that involved making two specific skins; one had ALL properties with an alpha value of 50%, and the other had ALL the alpha values at 100%. Theoretically, assuming that the alpha parameter might affect efficiency, the 'all semi-transparent' one should be perfectly as CPU draining as possible, whereas the 'all opaque' one would have no extra load. When i tried them both, i found absolutely no difference in performance.
Now, perhaps i may try it again, for two reasons:
1) i didn't try to load up an edit that pushes T2 really hard; i should really have tried to get it to do some serious work ON TOP of any colour related calcualations it may be doing, and really try to move stuff around. As it was, i just tried a fairly simple edit and tried to do what i could that would normally require colours to be recalculated.
2) Having the alphas at 50% may actually be a fairly light CPU drain; a 'half' calculation is pretty darned quick, so perhaps some choice odd alpha value might make it as taxing a calculation as possible.. truth be told they weren't all at 50%, because it's a bloody task to set every property, and i got very bored. This point may therefore be moot.
This is all taking the idea that the alpha calculations are only an issue when there are inopaque properties; it may well of course be that there is no optimisation if a property has an opaque colour (i.e. regardless, there will always be an alpha calculation, e.g. *1 )... which is kind of what my original test seemed to show. Perhaps i shall reperform it...
if this is all unintelligible, i apologise
Now, perhaps i may try it again, for two reasons:
1) i didn't try to load up an edit that pushes T2 really hard; i should really have tried to get it to do some serious work ON TOP of any colour related calcualations it may be doing, and really try to move stuff around. As it was, i just tried a fairly simple edit and tried to do what i could that would normally require colours to be recalculated.
2) Having the alphas at 50% may actually be a fairly light CPU drain; a 'half' calculation is pretty darned quick, so perhaps some choice odd alpha value might make it as taxing a calculation as possible.. truth be told they weren't all at 50%, because it's a bloody task to set every property, and i got very bored. This point may therefore be moot.
This is all taking the idea that the alpha calculations are only an issue when there are inopaque properties; it may well of course be that there is no optimisation if a property has an opaque colour (i.e. regardless, there will always be an alpha calculation, e.g. *1 )... which is kind of what my original test seemed to show. Perhaps i shall reperform it...
if this is all unintelligible, i apologise
Kick, punch, it's all in the mind.
-
- KVRian
- 991 posts since 16 Feb, 2005 from USA
whoever made the protools kinda pro looking skin posted in the sticky..my eyes thank you yet again.
i have a litle stutter when i scroll...but that is because I have my graphics card set up to consume very low resources so it doesn't fight with my firewire interface.
i have a litle stutter when i scroll...but that is because I have my graphics card set up to consume very low resources so it doesn't fight with my firewire interface.
-
- KVRAF
- 1615 posts since 28 Mar, 2005
I have had this problem also on mac when zoomed out!!
-
- KVRAF
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
Can you lower your monitor's refresh rate? Recently another program did this to me and bringing down the refresh rate made the program fly (it wasn't T2, though, but could be worth a shot)