Dropping out between riffs... revisited

[qwerty42]

I seem to be having an issue in V2 which I never had in the old version of Riffworks. When using a riff as a lead-in riff, if a note is held across the transition between the lead-in riff and the main riff, the sound completely cuts out for a brief instant at the transition. This seems to happen regardless of any settings--drummers on/off, mixed down or not, etc etc. I'm using Gearbox for the sound input, although I don't see how that should make any difference. I really don't think it's an issue with my computer, either, because it's running on a VERY recent install of Windows and there is plenty of available memory and cpu power with Riffworks running and recording. Here is a short wav clip of the problem: http://home.centurytel.net/mrsdeets/cutout.wav Is anyone else out there having this issue? Should I try reinstalling Riffworks? Any help is appreciated!

[jisg]

I'm not having that problem... but just a thought here... to have you click the info button to see if the audio is really missing from the wave pattern, if not see if you can re-adjust the audio (thin white line) back up to get sound on the missing note. again, just a thought, maybe a bug clicked the audio adjustment in the info bar all the way down on the transition.

[qwerty42]

Thanks for the suggestion. I actually had checked that already, and the volume is up all the way across. If you open the output wav in another program, the audio is indeed totally gone. I don't have any idea what the problem is, but I'm going to try reinstalling Riffworks to see if maybe it's just a fluke.

[qwerty42]

Well, I uninstalled and reinstalled RW, and it's still doing it. I can work around it by using the songlayers, but I still find it odd that I'm the only one having this problem...

Here's one other thing I noticed. If I open my old songs from V1 in V2, they play across the transitions correctly, but if I try to record any new ones with the riff-as-lead-in, it has the same cut-out problem. Hmmmm

[gatorjj]

qwerty42 is it only happening with Riff Lead in's? I quit using them once songlayers came in but will try one tonight if you don't get any response.

J.J.

[qwerty42]

Yeah J.J., it's only with the riffs as lead-ins. Everything else works completely flawlessly for me. I'm baffled at this point... I have messed with everything I can think of, including the buffer size for the input. It appears that for some reason, when it's recording, there is a slight "stutter" as it transitions between riffs, and a small fragment of the audio data is lost. I wish one of the all-knowing software designers would chime in on this and let me know if I'm just going crazy. I could just do the transition parts in song layers, but as often as I use the lead-in riffs I'd end up having almost my entire song in the song layers instead of the riff tracks. I've wondered if it could possibly be a memory issue. I only have 512 mb of RAM in this computer, with ~250 mb free when RW is running. Any more thoughts, anyone?

[jisg]

ah - the old less than 1G of RAM scenario...

qwerty42 -
I know what you really need is to have dug

Chime in

here
but -
there have been many a problem caused by less than 1G and fixed after installation of more RAM. SWW usually recommend it for optimum running even though their requirements state 512 as minimum.

[dave]

RAM might be an issue. Just because you have free memory doesn't mean that Windows didn't swap a bunch of our stuff to the hard disk to make that memory free.

If you do get a stutter right there, it is possible that we couldn't complete the transition in time and the audio was dropped. You could try increasing the buffer size in the Audio Setup panel. This will increase your latency, but it will also give us more time if we were swapped to disk.

Dave

[qwerty42]

Hey, thanks for the response Dave. It definitely seems like RAM is a likely culprit. I've tried maxing out the buffer size and it still does it, so I'll quit putting off the RAM upgrade and see if that takes care of things. I really appreciate the program and all the hard work put into it, by the way. There are certain aspects of Riffworks that no other recording software can touch, in terms of ease-of-use, simplicity, and getting ideas down and songs roughed out quickly.

[hbursk]

Hey Dave,

I was having the same problem. I thought it was the fade times that you changed between the old version and the new version, but maybe not. Maybe there's something more to it. I can't use riff as lead in though because I too get a transition that's just unusable.

[GuitarSlinger]

I noticed the same problem with buffers at 256 on my machine but then went to the song layers. Also if your using tonedirect monitoring without any vst then there is no reason not to kick the buffer way up to max as long as the drums dont stutter. I have mine set at 2048 and the perceived latency is 0.

[Izegrim]

I am experiencing the same problems. I also have Riffworks crash alot. When can I expect an update on this?

[dave]

Izegrim,

I'm not sure what you're asking specifically about... If you are getting repeated crashes, could you go to the support page and enter a support case? We'd be happy to help you, we just need some more information about your crashes and its easier to track from the support form.

Dave