Original MBox and RiffWorks T4

[thesciguy]

I have just tested T4 with my original MBox and Dell laptop (Latitude D510 with a Pentium M 1.6Ghz....I think). So far, so good.

My questions are:
- Am I just lucky or have many reported success?
- Will I be pushing my luck with the full version?
- How far can I push this software before I do get some issues with my current setup?

Thanks.

[d3drocks]

i have mbox 2 mini and Riffworks doesnt even see it's asio drivers.

[davenz]

If it works, you should be able to use it no problems. The issues will start when you load it up with tracks and there is no real way of knowing until you try the full version.

Riffworks is CPU hungry, possibly even more than RAM hungry and your CPU should do the job OK. The reality is though that the better your machine, the better your mileage.

Dave.

[thesciguy]

If by tracks, you mean layers, that may be the problem since T4 only allows 4 max. It would be interesting to know exactly what issues are known to not include the original MBox on the hardware list. Because, like I said, so far so good.

[d3drocks]

Riffworks is CPU hungry

oh man, it totally isnt. for what it does, possibly but as a DAW, no.
in FL-Studio i usually have about 10 reverbs, 15 parametric EQs, 2 or 3 choruses, multiple VSTi/Fruity plugins (usually 10 to 11)
i run my system up to about 90% CPU usage.
Riffworks cant come near that ony my system.

[davenz]

Riffworks is CPU hungry

oh man, it totally isnt. for what it does, possibly but as a DAW, no.
in FL-Studio i usually have about 10 reverbs, 15 parametric EQs, 2 or 3 choruses, multiple VSTi/Fruity plugins (usually 10 to 11)
i run my system up to about 90% CPU usage.
Riffworks cant come near that ony my system.

Well, sorry, but it is, especially when using some of the reverb/chorus/delay effects; the clicking and popping people hear with those and set-too-low buffers is the CPU not keeping up, a very common problem with Riffworks, on Windows at least. I don't know how it compares to other DAW's as I don't use any; all I know is what it is like on my machine and from what others say in these forums. If it doesn't on your machine, that's great but on mine, it pushes it sometimes and my machine is no slug.

Dave.

[d3drocks]

Riffworks is CPU hungry

oh man, it totally isnt. for what it does, possibly but as a DAW, no.
in FL-Studio i usually have about 10 reverbs, 15 parametric EQs, 2 or 3 choruses, multiple VSTi/Fruity plugins (usually 10 to 11)
i run my system up to about 90% CPU usage.
Riffworks cant come near that ony my system.

Well, sorry, but it is, especially when using some of the reverb/chorus/delay effects; the clicking and popping people hear with those and set-too-low buffers is the CPU not keeping up, a very common problem with Riffworks, on Windows at least. I don't know how it compares to other DAW's as I don't use any; all I know is what it is like on my machine and from what others say in these forums. If it doesn't on your machine, that's great but on mine, it pushes it sometimes and my machine is no slug.

Dave.

wow, thats very supprising to me.
my ASIO buffer is always at 256 samples, with no issues ever.