Is dual core support in the works for tracktion?

[maximilians1]

Hi, just wondering if anybody knows if dual-core support is in the works or planned for Tracktion. I won't be upgrading for a while but it looks like prices for entry level dual cores X2 3800 and the 64 3800 are roughly the same price? and by the time I upgrade they should actually be affordable .

[bchamp]

Hi, just wondering if anybody knows if dual-core support is in the works or planned for Tracktion. I won't be upgrading for a while but it looks like prices for entry level dual cores X2 3800 and the 64 3800 are roughly the same price? and by the time I upgrade they should actually be affordable .

Don't hold your breath. We can't even get some simple bug fixes in a timely fashion.

[mandolarian]

Ben said this a few weeks back:
"Tracktion is multi threaded, however the audio engine will only use one cpu/core. However, other things like the GUI, midi, etc will run in another thread."

However, as I understand it, in future versions you will be able to dedicate one core just for bugs.

[Lunch Money]

Which bugfixes are you dying for, bchamp, that haven't gotten to you in a timely fashion and are hindering your workflow?

It's like people just can't keep it to one or two threads, but have to pollute EVERY thread with their pet problems.

max: I wouldn't count on it, either. It seems to me (I can't say for sure) that dual-core support would be a CPU-specific thing, no? Tracktion's code core is meant to be as portable and flexible as possible, making it usable on Mac and PC, and at least maintaining the possiblity (wouldn't hold your breath) that it would be ported to Linux one day.

Apps like Sonar don't have to worry about it because they're PC-only, so they don't need to worry about the logistics of splitting the code base in two.

From what I hear, dual-core is pretty sweet, but not the dramatic improvement that one would think. I imagine you'll get other intrinsic benefits of a dual-core platform even if T itself doesn't use it. [edit: mandolarian's point pretty much covers this]

[edit2: what are these legendary hordes of bugs that people are crying about? I can't name one single bugfix that we're waiting for. Feature requests, sure, but not bugs... mind you, better to start another thread titled, "Legendary Bugs We're Waiting to be Fixed" rather than continue on this thread]

[edit3: I'm not saying there aren't bugs, I'm just saying I'm not sure what specific bugs people are dying to have fixed that are stopping them in their tracks]
Greg

[mandolarian]

The GUI bugs that linger for some...
The Pops 'n Clicks from the latest release (Didn't you go back to the March release after suffering this, Greg?)
The rendering bug / TapeIt Marketing Plan
Installation Corrupt issue

To name just a few...

[bchamp]

I'm running T2 on a Mac, and I'm experiencing several bugs that are getting on my nerves. These aren't show stoppers, but they are frustrating and don't exactly enhance the creative process.

1.) Window resize issues. Sometimes the app gets in a state where I can't maximize the window...the settings panel gets concealed.
2.) Sometimes, the input selects act weird. For example, I select 'MIDI input' and the track gets enabled for 'audio input'.
3.) Occasionally, a muted virtual instrument doesn't get muted on playback unless I toggle the mute button a few times.
4.) I've had some GUI corruption with Minimonsta and BBE Sonic maximizer plugin. Not sure if this is Tracktions fault, but these work fine under Logic. Maybe the AU versions are more solid?
5.) I've had a few audio glitches especially during looping.

Not show stoppers, but still frustrating.

BC

[Lunch Money]

The GUI bugs that linger for some...

OK, for fewer, though. I just assumed that when they cleared up for me with 2.0.1.3 that the majority of other people would have similar experiences. Also, it's never been 100% clear what the cause was. I had a further reduction in "GUI issues" when I finally replaced my Matrox G550 with a new card. I distrust ATI cards, and the replacement was just a cheapie, but the results are tough to argue with. I wonder if other people need to get a new card, too, or sort out PCI timing issues.

I'm not saying that to be smug or act like I solved the problem myself. For all I know, I'm imagining that modifying my PCI latency and replacing my card was an improvement. ALL the improvements could have just come from Tracktion, since it all happened at around the same time.

The Pops 'n Clicks from the latest release (Didn't you go back to the March release after suffering this, Greg?)

Yup, I had to roll back to an earlier release at one point in time from pops and clicks. However, I'm currently using a different version altogether.

The rendering bug / TapeIt Marketing Plan

The rendering bug has been sorted for ages and ages. This new one that one user mentioned is a one-off and it hasn't been trouble-shot yet. There are no other rendering bugs, and T's rendering was actually put to the test very recently and found to be flawless. I don't know why people still think there's a rendering bug, but there are none that I'm aware of, except for that one fellow who's having a tricky time, getting a "tinny" render. That's certainly not a pervasive problem and I don't know any other users having it.

Installation Corrupt issue

Never heard of this one. Can't say anything one way or the other, except that I've never run into it myself or heard of it before.

To name just a few...

Possibly you couldn't think of any others. <that's a joke... yeah, I sort of believe it, but I'm MOSTLY just saying it to tease you!> I'm not saying other people aren't having problems, but what I'm saying is that it's a mistake to confuse bugs with support issues. When a whole bunch of people have NEVER had a GUI slowdown, some people have said, "Wow, it's much more responsive now," and only one or two are still saying, "I'm getting GUI slowdowns", it starts to look less like a bug and more like a support or hardware issue.

Since there are people who come here for support, it's not a surprise that we'll see a good chunk of our threads with subjects like, "Yikes, I'm getting too many pops and crackles!" FWIW, in recent times there have been ongoing threads for Cubase and eXT regarding pops and crackles, too. Pops and crackles are a very common problem, not always rooted in the software itself.

I dunno...

I don't want to sound too adversarial, because I quite like you, and I know that you add a lot to this community. But you have to admit that in a big group like this, there will ALWAYS be a certain demographic who will use OTHER people's problems to bolster the validity of their own claims. It's not enough for some people to just say, "I wish features got added more often." For some reason, they feel the need to make it seem like Mackie is ignoring them, so they throw in things like, "what about the bugs?" when in fact they've never experienced these alleged bugs.

And then it just sort of spreads from there... not like a "rumour" exactly, but definitely unchecked. And part of the problem is that when things get resolved, like the rendering bug (which WAS a bug, and WAS fixed in a very timely and responsive fashion), not everyone knows about it. And then if they never heard that it got fixed, they mention it in a thread again, sometimes offhandedly, "Tracktion's rendering is flawed anyhow, use TapeIt", without knowing that their bug has been fixed. Then it spreads AGAIN.

I will ALWAYS agree with people that a more publicly available database of ongoing bugs and fixes would make everyone's life a lot easier. It would certainly make MINE easier. But in the meantime, it just gets annoying when people use each others' complaints (real or imagined; Tracktion's fault or system-specific) to bolster the validity of their own complaint. It gets nobody anywhere and simply propagates a set of rumours or at least incomplete information, and sets people up (especially new forum members) to take it at face value. It's irresponsible, IMO, to simply write "Tracktion's rendering is flawed." because someone who doesn't visit the forum often might see only that post, and not my "Tracktion loyalist" response that "No, it's not. That bug was fixed."

I don't know what the hell I'm saying anymore...

I typed too much and without enough focus.

Greg

[Watto]

I'm not saying other people aren't having problems, but what I'm saying is that it's a mistake to confuse bugs with support issues. When a whole bunch of people have NEVER had a GUI slowdown, some people have said, "Wow, it's much more responsive now," and only one or two are still saying, "I'm getting GUI slowdowns", it starts to look less like a bug and more like a support or hardware issue.

I take your point, but there isn't a definte cutoff point, so unless you're the bug VS support or hardware issue police, is it really such a problem that it gets mentioned? Personally, I can't see much difference between the terms anyway.

I don't know what the hell I'm saying anymore...

I typed too much and without enough focus.

That's how you ended up here - http://www.kvraudio.com/stats.php - in 5th place!!!

[Lunch Money]

Holy crap, I'm in 5th place!! I never would've known!!

<laff>

Peace!
Greg

[maximilians1]

Thanks Greg