While rendering midi to wav I am getting very subtle but annoying timing errors on the MIDI portion. Some notes are pushed back slightly with respect to others. The softsynth works fine live, but seems to be screwing up only during a render. Realtrax sounds fine.
I'm playing four midi tracks (one for each string of a mandolin) through the forte dxi synth. All four MIDI tracks are displaying the same shifting at the same time, as if someone were trying to impose a slight erratic lilt to the melody.
I'll see if I can find some way to record live for now, but rendering is a great feature if I can get it to work properly.
Hmmm new one for me
Can you post an example? Have you tried freezing the tracks? Just in case it is re-generating something a little different.
System specs? (anything that may help; soundcard, processor, RAM, etc)
I just listened to the whole song this time and the renderer starts dropping MIDI notes about 30 seconds in before dropping the rest of the MIDI tracks completely.
I had it split the tracks out individually and you can still definitely hear it.
I've never had a problem rendering before on this machine, so I am thinking it's something in BiaB 2011. 4Gib RAM, 2GHz. Dual-processor. One of the processors runs at 95% while rendering, but the other one stays relatively sleepy. Playing in real time puts no load on the system at all.
Do I need to freeze the MIDI track? It shouldn't be doing anything with those except playing what I tell it to through the soft synth... but maybe there is some lilt effect on the note timing? Why would it only show up during a render and not during normal playback?
--This is why I need to record the playback live as a workaround. I wanted to mail this version out today.
Hi John,
Welcome to the forums.
Regarding recording it "live" ...
Go to Windows "Recording Properties" and select the option "What You Hear" or equivalent. With this selected, when you record the audio, the track created will be a recording of what's coming out of the speakers.
Regards,
Noel
Ah thanks for that.
It's not dropping notes on the render any more. That might have been a one-off. I rebooted my machine to clear an any OS problems but the MIDI tracks are still wobbly on render. I estimate +/- 2o ms.
This shouldn't be an ASIO4ALL problem, right? That shouldn't even be used during a render.
I don't know why some people use Asio. Caused me nothing but 2 months of misery. After never going there again all was well. I can render, I can do midi I can play my keyboard, all with not a glitch.
But that's moi.
I certainly did the asio dance. I left that girl in the shed. Some girls you don't take to the barn.
Hi John,
Quote:
This shouldn't be an ASIO4ALL problem
I don't know if ASIO could be causing this but it's easy enough to test out.
Use Opt | SAve Preferences to save your present audio settings and then use Opt | Preferences | Audio to change ASIO to MME. It would be best to exit and restart BIAB to make sure these settings are loaded; some people even recommend rebooting the computer as this guarantees clearing the computer's memory. If after trying MME, the problem persists and you want to return to your previous settings, simply use Opt | Open Preferences to load your saved settings.
Like John Conley above, I have found ASIO an unpredicable dance partner. I keep ASIO4ALL installed so that it's there to use when I need it (usually recording vocals) but, if MME does the job for me, I always use MME. The MME driver is more Windows friendly.
Regards,
Noel
I don't need to use ASIO however I've done some testing and it's been OK with BIAB however I don't think I'd trust it. Now on the other hand I do use ASIO with my IKMultimedia guitar interface & the Ampeg SVX modeling plugin and it's awesome. Never a glitch & it's set at 2 MS. I guess part of the lesson here is that it's probably best if a program and an interface were designed by the same company. If PG were to design & build and interface for their programs I'm sure it would work fine.
Hi John Vreeland, and welcome!
At this point the most relevant information needed to know here would be:
*What is your chosen MIDI DXi device with this problem?
*What is your OS?
*What soundcard or sound device?
This problem might be solved by going under the Options menu in BiaB and choosing, "Return to Factory Settings" picking the second button down there, which will re-invoke the MIDI/Audio setup wizard. Sometimes having the program re-address these two critical assignments can clear up any corruptions or the like.
Of course, there can be other causes of the problem as well, make sure that you have visited the Support page and have downloaded and installed the latest UPDATE PATCH for your version of the program as there are often problems such as this one that have been addressed and fixed with the patches.
--Mac
Reset all prefs to factory. No change.
Version is BiaB 2011 build 313
I'm using the HD Audio on my MSI motherboard. Not sure what the audio chip is.
The problem occurs with both Coyote Forte and the Coyote WT wrapper.
Real styles are fine but it is affecting all MIDI styles, which are experiencing the exact same timing problems. As if some beats are a little late or early, or all late but to varying degrees. It's the sort of thing you might expect during live playback if you were taxing your system, not during a render when time is free.
Defragged the hard drive recently?
Doubt it is that, but am running out of ideas and it may be worth a try.
I'm sure you've rebooted the machine, right? Windoze loves to be rebooted.
--Mac
Since live playback is just fine it cannot be due to system inadequacy in any way. It must be something that only happens during MIDI render, which implies a software problem.
It sounds like some wacked "humanize" effect. As if humanize is set to "maximum annoying" during a render.
Also, render is dropping notes again, so it isn't a 1-off. That seems to be the bigger problem. At first the notes are all there, but about 1-minute into the song they start disappearing until they are all gone.
** I've had the choppy rendering happen here after installing a lot of new realtracks and as it turned out, defragging the disk eliminated the problem.
All I could figure at the time is that the playback is a different dance than the render beause playback was fine, render had dropouts and missing instrument tracks in places.
--Mac
Hi - I'm having the same problem. I just defragged my hard drive, no joy, rendering a song with all midi tracks produces a .WAV that still has timing glitches. Playback of the same song is fine. Renering w/ real tracks seems to be fine. I installed Biab 2011 just a few weeks ago.
What are you using for the synth that is doing the rendering? (default DXi synth)
Maybe you guys are onto something .. (?)
I think I'm using CoyoteWT, re: Opt.->Preferences->Midi Driver, VST/DXi Synth Settings...CoyoteWT.
I wonder if John Vreeland is using the same (?)
I've tried it with both Coyote Forte (licensed) and Coyote WT
I just checked some of my older recordings and I did NOT have this problem under BiaB 2010. Same machine, same OS. The only difference is that BiaB is upgraded.
Just wondering if it has to do with the Coyote WT .. as this is new with this version.
If Forte does it too, I don't think it has changed, so problem may lie elsewhere.
Yeah this problem kills MIDI rendering dead, but at least real-time MIDI works. I suppose a lot of people are using external modules anyway, so they always record in real time.
I use both software and hardware modules, selecting what seems to sound or work best to my ears for each project.
I also tend to ignore the Rendering process altogether when using the softsynths - except for the occasional quick job - as I'm old fashioned and learned to do "hands on" mixdowns where the entire piece must be played from beginning to end while being recorded to a stereo track. Neat way to add a few Vol changes or Pans etc. to the thing without resorting to automated insertion, if you get the hang of it.
--Mac