Editing Clips???

[50ftbk]

"This section deals with Tracktion's most powerful features - editing clips."...

I copied this text directly from the Traction Help Pages.

If editing clips is Traction's most powerful feature, then I must be doing something way wrong.
Every time I cut/edit the beginning or the end of a clip, I get audio glitching a second or two after the cursor passes over the edited part of the clip. This also happens when I do 'punch-ins'.
The sound just drops out a second or two after the cursor passes over the beginning of an edited clip.
Is there a trick to editing clips that I dont know about?
In the Help pages under "detailed help", it basically says to check the "quickstart guide". Whats up with that?
The quickstart guide has a brief discription of how to streatch and/or edit the ends of a clip. But no trouble shooting.
If I cant edit clips, then I have no use for Traction.
I love the program, but Ive had more trouble with it in 1 month, than a whole year of using the free version Pro Tools. Im starting to feel like the only reason im still bothering with it at all, is because I paid $$ for it instead of getting it for free off of some P2P network. Which I found out is very easy to do.
Have I wasted my money
Someone please help restore my faith in this program, and tell me how to edit clips.

Please Help!!

[Lunch Money]

"This section deals with Tracktion's most powerful features - editing clips."...

I copied this text directly from the Traction Help Pages.

If editing clips is Traction's most powerful feature, then I must be doing something way wrong.

Yup, let's see if we can find out what.

Every time I cut/edit the beginning or the end of a clip, I get audio glitching a second or two after the cursor passes over the edited part of the clip.

Not sure what you mean here-- if the cut is not at a zero crossing, you might get a loud pop or click...? Easiest way to fix this is to zoom in a "whackload" and then use the fade handle to fade in a wee bit. Pop/click eliminated.

This also happens when I do 'punch-ins'.
The sound just drops out a second or two after the cursor passes over the beginning of an edited clip.
Is there a trick to editing clips that I dont know about?

Bizarre.... I don't get it. It sounds like you're getting unconventional behaviour that is not related to Tracktion itself. My best guess is that you have your latency set too low, and when sound "comes in" (ie. Tracktion is suddenly told "hey, start processing a signal!") the CPU, HDD, and soundcard aren't agreeing on a smooth way of accomplishing that task. So in other words, your latency is set too low, your resolution is set too high, or your CPU and/or HDD can't handle it. In any case, it's a limitation of your settings and your system rather than Tracktion. The good news-- it can be fixed!!!

In the Help pages under "detailed help", it basically says to check the "quickstart guide". Whats up with that?
The quickstart guide has a brief discription of how to streatch and/or edit the ends of a clip. But no trouble shooting.
If I cant edit clips, then I have no use for Traction.

Beats me. Help guide? Never needed one...

I love the program, but Ive had more trouble with it in 1 month, than a whole year of using the free version Pro Tools. Im starting to feel like the only reason im still bothering with it at all, is because I paid $$ for it instead of getting it for free off of some P2P network. Which I found out is very easy to do.

Well, the fact that you love the program is evidence that you like its way of doing things, so we've got a good start. The next step is to trouble-shoot the possible sources one by one. The reason the guides won't help you trouble shoot is for the same reason that no software manual can trouble-shoot all problems. This is unconventional (in fact, it's the first time I've heard of anyone with this problem) and not related to Tracktion itself.

Have I wasted my money
Someone please help restore my faith in this program, and tell me how to edit clips.

Faith on its way! You're doing it right, from what I can tell. You use '/' to cut clips where you want... delete segments with 'del'... use the fade handles to fade in and out... there's not much more to it than that. So let's concentrate on figuring out what's going on.

Please Help!!

I'm sure we'll try!

Here are some questions to start it off-- girlfriend's on her way over so I won't be on for long, but hopefully someone will pick up where I've left off (since I'm not a pro anyhow)

1. What is your system spec? (RAM, CPU, HDD, and soundcard will do for starters!)
2. What driver is installed, and is it selected in the Settings page? Is it a low-latency driver? (ie. ASIO)
3. Describe the noise in a little more detail
4. Is the CPU meter (in the bottom right) jumping into the red when these problems occur?
5. What else is in the hardware signal path? Mixer?
6. What else is in the software signal path? (ie. filters/plug-ins)?
7. What samplerate and bit-depth have you selected?
8. What is your buffer size in your audio device drivers? (ie. what's your latency configured at?)

That should be a good start.

Greg

[djsubject]

this is deff not norm 4 tracktion & its probley easy to fix first if u import a audio file (not record it in dose it happen?

is yr latensey low try putting it up to full if u have a non asio sound card (a cheap one)?

get back with souch info as listed here & abouve & u will find helpfull tips posted after verry soon good luck


p.s u said u was running pro tools free witch only works on dos based windows (win 95,98,me) i run win2000 found it loads better 4 audio appz


good luck with yr probs T is worth the cash

[50ftbk]

"Lunch Money" wrote

1. What is your system spec? (RAM, CPU, HDD, and soundcard will do for starters!)

Im running Traction v.1.6.0.1 on Mac OSX. 128MB RAM, CPU-G4 700MHz, 40 GIG HD.

2. What driver is installed, and is it selected in the Settings page? Is it a low-latency driver? (ie. ASIO)

ASIO is a windows thing. Im using a Mac. The only driver I have installed is the driver to run my audio interface. Which is a tascam US-122 USB audio interface. And it is selected in the settings page.

3. Describe the noise in a little more detail

Its not really a noise... the sound completely drops out for a second or two, and then it comes back and keeps playing. This happens just a few seconds after the cursor passes over the starting point of a clip. But only on clips that ive cut or punched in.

4. Is the CPU meter (in the bottom right) jumping into the red when these problems occur?

Nope.

5. What else is in the hardware signal path? Mixer?

No mixer. Just the Tascam audio interface. Im basically recording 1 track at a time. Guitars,bass,keys,vox,etc. Audio only... no midi. Everything works fine until I try to cut or trim a clip.

6. What else is in the software signal path? (ie. filters/plug-ins)?

No filters or anything. I havnt even gotten that far yet. I dont even want to think about the problems im gonna have when I start running plug ins n filters.

7. What samplerate and bit-depth have you selected?

Sample rate:44100Hz. Bit depth: 24 bit.

8. What is your buffer size in your audio device drivers? (ie. what's your latency configured at?)

The buffer in my audio device driver is about half way. I'll try bringing that up more. I have the latency completely maxxed.

So what do ya think?? Any ideas??

ps. thanx for the reply and the good suggestions.

[djsubject]

RIGHT NOT A MAC USER SOZ, but u say yr sound card is selected, in windows there's like 4 diff drivers i can pick 4 my 1 soundcard, is this so on the mac vershion if so try the others by the sounds of yr spek u should be fine



Oi any other mac users here able to help

[nuisance sonore]

50ftbk, is it possible you're simply running out of ram? Can you monitor your ram useage?
I mean, my latest project is fairly simple, and It's using 572 MB...I didn't even know you could run a multitrack audio program on 128MB only.

[Id Lab]

this is deff not norm 4 tracktion & its probley easy to fix first if u import a audio file

I read this far before I had to go and have a stiff drink. Please put 'Not safe for English speakers' at the top of any future posts, or I'll die of alcohol poisoning.

Back on the topic, I find that the buffer in my audio mixer needs to be at minimum for glitchless audio. (It's a Terratec 24/96 on a Windows PC, so relevance is not guaranteed.) Try lower values there, keeping the Tracktion latency slider fairly high.

[mapper]

128mb of ram is definately not enough.
Its hardly enough to run the OS alone.

OSX likes at least 256mb and would recommend getting the max you can afford.

I ran Tracktion on a G4-400 mhz with 1gb of ram with no problems.

I currently run an ibook 1.2ghz with 768mb ram

I would suggest getting at least another 256 stick of ram.

see if that smooths things out.

regards

[djsubject]

this is deff not norm 4 tracktion & its probley easy to fix first if u import a audio file

I read this far before I had to go and have a stiff drink. Please put 'Not safe for English speakers' at the top of any future posts, or I'll die of alcohol poisoning.

Weed is much less harmfull to the human body



if i could spell propley then im shure my grammer would vastly improve


But i cant so

[Id Lab]

I loves you, I do... *hic*.

[djsubject]

I loves you, I do... *hic*.

[Lunch Money]

50ftbk:

-128 isn't nearly enough RAM, so that might be your problem; then again, it might not be, and that's not something we can easily look into.

-the CPU is also not very fast; however, if you could play back on Pro Tools LE without a weird glitch, Tracktion should also be fine as it's not a CPU hog.

-When you say your latency is maxxed, do you mean that it's maxxed for 'performance' (ie. only a few milliseconds) or that it's maxxed as in there's a long delay (20+ milliseconds)?

I have to admit, the main thing that jumped out at me was the system spec, but that's because I'm not a Mac guy. I wonder what's different in your PTLE setup and your T setup. Knowing that'll solve all mysteries.

Greg

[Beno]

Yes,
Tracktion Loves RAM and it's hard to trouble shoot past that if you only have 128 MB. I have 512 and it seems to be just barely enough for OSX let allone another app. I have a G4 1 GHz with 512 but a desktop with a slower 800 MHz Proc but 1152 MB Ram and it has always felt much snappier due to the added RAM. I keep eyeing a 1 GB stick for my laptop but they are so expensive. But I woul definitely recomend if you are going to upgrade RAM, not wasting time adding 256 MB, add 512 at least. The price difference isn't much at the smaller amounts.

Ben

[valley]

I have 512 and it seems to be just barely enough for OSX let allone another app.

What the hell happened to Steve Jobs? NeXT was so efficient it was uncanny. That sounds more like MS on a bad day.