Tracktion Software

ceenda · Post by **ceenda** » Thu Apr 07, 2005 9:40 am

Not to keep banging an old drum, but the fact is that the user shouldn't have to find work-arounds for basic functionality. I agree with scenarios where the user needs to find certain work-arounds to stop a package becoming bloated and option-dialog-laden. But this is a problem with how the application should actually 'work' and I was rather hoping it would've been fixed.

aldi · Post by **aldi** » Thu Apr 07, 2005 9:40 am

pHz wrote:
Lunch Money wrote:Aim the dryer at your hair rather than your hands, and you'll be sorted. Also, hold by the handle, not by the side vents.
Those 2 tips alone could have saved you 10 burns if you had known up front!
but theyre both ONLY workarounds ... the burning issue should have been addressed before the hairdryer was shipped ...

slainte rob

headquest · Post by **headquest** » Thu Apr 07, 2005 9:43 am

Breakpete wrote:I fully agree with headquest on the dropped note issue. This bug got a lot of attention in T1 and really should be worked out now. While most apps will have some bugs, this one has been around for a long time. You'd think they could fix it for v2, especially at the new price which sort of puts it in a new league.

I have been advised by somebody here that they probably can't fix it until the rewrite the whole audio engine

Lunch Money · Post by **Lunch Money** » Thu Apr 07, 2005 9:50 am

I already agreed that a workaround shouldn't be needed. My only point is that people make it seem like something that cripples T's ability to function, when really... get some perspective... it's a 30-second fix at most.

So, it really IS beating a dead mule to keep bringing it up... even people like me for whom it has never been an issue, will agree that it should've been fixed. Who else needs convincing? Nobody. There's not a person who would say, "Nah, leave the bug in, it's fine." We'd ALL like to see it fixed, so it's a bit... old and tired... to keep mentioning it. Sure, mention it every now and then just to make sure it's not forgotten, but have some pity on a poor man's patience and sanity and stop mentioning it 5 times per non-related (or even related) thread.

Greg

Breakpete · Post by **Breakpete** » Thu Apr 07, 2005 10:04 am

headquest wrote:I have been advised by somebody here that they probably can't fix it until the rewrite the whole audio engine

I thought by this time that's what they had done, seeing as T2 has been a long time coming.

If what you are saying is true, it seems to me the entire midi implementation is based on flawed code. Seriously, this is a proven bug, and I don't see mackie advertising "slightly broken midi sequencing".

LM, it may be a badly beaten up dead and rotting mule, but apparently the mule still needs some beating, because the bug hasn't been fixed yet.

headquest · Post by **headquest** » Thu Apr 07, 2005 10:04 am

Lunch Money wrote:I already agreed that a workaround shouldn't be needed. My only point is that people make it seem like something that cripples T's ability to function, when really... get some perspective... it's a 30-second fix at most.

Not if you use lots of seperate MIDI clips as I do.

Plus, I find that even though I nudge notes by a couple of ticks to stop the bug, I sometimes find that when I reopen the edit a couple of days later the nudging has gone (i.e. the notes have been Quantised back to their original dropped state). So then you have to stop quantising... and so it goes.

That's not a 30 second problem

So, it really IS beating a dead mule to keep bringing it up... even people like me for whom it has never been an issue, will agree that it should've been fixed. Who else needs convincing? Nobody. There's not a person who would say, "Nah, leave the bug in, it's fine." We'd ALL like to see it fixed, so it's a bit... old and tired... to keep mentioning it. Sure, mention it every now and then just to make sure it's not forgotten, but have some pity on a poor man's patience and sanity and stop mentioning it 5 times per non-related (or even related) thread.

Greg

...but that IS a fair point. I won't mention it again today once this present discussion is done (unless specifically asked. normal terms and conditions apply.

)

headquest · Post by **headquest** » Thu Apr 07, 2005 10:05 am

Breakpete wrote:
headquest wrote:I have been advised by somebody here that they probably can't fix it until the rewrite the whole audio engine

I thought by this time that's what they had done, seeing as T2 has been a long time coming.

If what you are saying is true, it seems to me the entire midi implementation is based on flawed code. Seriously, this is a proven bug, and I don't see mackie advertising "slightly broken midi sequencing".

LM, it may be a badly beaten up dead and rotting mule, but apparently the mule still needs some beating, because the bug hasn't been fixed yet.

Spot on.

chico.co.uk · Post by **chico.co.uk** » Thu Apr 07, 2005 10:51 am

uh ... right ... so if you mention it every day, it gets fixed quicker ... i see ...

headquest · Post by **headquest** » Thu Apr 07, 2005 11:12 am

chico.co.uk wrote:uh ... right ... so if you mention it every day, it gets fixed quicker ... i see ...

Apparently you can mention it for two years and it doesn't get fixed. Hence the frustration.

But if you're ok with a MIDI implementation built on flawed code, I can understand you wishing we would shut up about it

chico.co.uk · Post by **chico.co.uk** » Thu Apr 07, 2005 11:49 am

Yes, i love it, i especially love it when i have to read about it every day. Over. and over. and over. and over. and over again. That's my favourite.

DHR53 · Post by **DHR53** » Thu Apr 07, 2005 12:16 pm

I've found a couple of variables that affect the condition... For instance I noticed that if I start with a 2 bar clip instead of a 1 bar clip, it doesn't happen... Also, if the first note is moved, then placed back at the first beat, it will play properly... And so far, in live recording of VSTs in T2 (OSX version) I haven't had a dropped note... So I'm sort of speculating at this point whether it's still as bad as it was... Frankly, I've been "individually adjusting" notes in Reason for years, due to the fact that when Reason snaps to the bar, if you group notes (which I always do) the first note is always in between the bar... which produces a grouped clip 2 bars long instead of 1 bar! Annoying, but I just got used to it... And furthermore I like to turn snap off and adjust notes anyway, just for feel... So I guess although I've complained a lot about "T" I'm always doing similar adjustments in other programs... Would it be nice if it was perfect? Yep! But Logic has some quirks like this, and as I mentioned so does Reason! In the end it's whether you can live with em' And which program frustrates you the least...

bewing77 · Post by **bewing77** » Thu Apr 07, 2005 12:48 pm

I for one think that one thing that really is needed is a fix for the first midi note bug.

.jon · Post by **.jon** » Thu Apr 07, 2005 1:59 pm

What's the situation with the first MIDI note bug? Is it fixed already?

I've never started any songs in any sequencer on the first beat/first bar, but I'd really like to feel like part of the community.

haydxn · Post by **haydxn** » Thu Apr 07, 2005 2:47 pm

i read a while ago about some kind of Midi Notepad drop-zone bug spray? is that something that is present in T2?

stephengardner · Post by **stephengardner** » Thu Apr 07, 2005 6:56 pm

I spent two months coproducing a project in Nashville on Dp with a guy that teaches it at the local college . the features are great on dp, but the sound.?...T sounds a lot better to me.

Tracktion Software

KVR Audio

my feelings