RENDER TO Wonderfulness! - Live 4 is heaven!
-
Riff Valley
- Posts: 39
- Joined: Sun May 01, 2005 10:03 am
-
::mic-minimal::
- Posts: 658
- Joined: Tue Mar 04, 2003 8:32 am
- Location: behind you
I render all the time, 16bit and 24it, have no problem with either, I also have silver spikes tape it but it has now become a pain and is much easier to just render, like i said never any problems. my setup is a panasonic laptop centrino and an amd desktop both get the job done right.
for the love of Live
no worries, it's late at night here. LATE at night - in spirit rather than by the clock. Damn this Austalian Hemp.smutek wrote:forge wrote:I think live sounds better when you cover one eye and stand on one leg howling at the window.
Or maybe that's just when you take the blue pill.
Note to self: Red pill next time![]()
Thanks for the early morning smile forge.
(here on the other side of the world)
-
tomperson
- Posts: 1018
- Joined: Fri Oct 08, 2004 11:55 am
- Location: MVD, Uruguay, South America
- Contact:
Hmmmmm. Why would the ASIO driver latency and such would make any difference when rendering to disk? I almost swear I could even do a render to disk in a machine without soundcard at all! Moreso, several times I've rendered stuff that was having glitches when played due to overload, and the render was just fine.
Whats that ASIO "compression" thing???
Whats that ASIO "compression" thing???
Turn up the radio. Turn up the tape machine. Look into the sunset up ahead. Roll the windows down for a better taste of the cool desert wind. Ah yes. This is what it's all about. Total control now.
-
Sales Dude McBoob
- Posts: 2844
- Joined: Thu Dec 02, 2004 9:34 pm
- Location: Durham, NC. USA
- Contact:
From what I gather, the ASIO compression issue is what brought about the demand for such products as the Dangerous Audio 8 Bus.
The problem is that when you play a song back in its host application be it Pro Tools or whatever as a multitrack file it sounds a certian way- but when you ask your computer to take the 30 or so tracks and do all of the math to sum those 30 tracks down to 2 track stereo for rendering, the song loses some of the life and playfulness it had going as a multitrack session.
But I gotta say, once again, I got my rendering in Live to sound really sweet last night so maybe it's more of a Pro Tools issue.
The problem is that when you play a song back in its host application be it Pro Tools or whatever as a multitrack file it sounds a certian way- but when you ask your computer to take the 30 or so tracks and do all of the math to sum those 30 tracks down to 2 track stereo for rendering, the song loses some of the life and playfulness it had going as a multitrack session.
But I gotta say, once again, I got my rendering in Live to sound really sweet last night so maybe it's more of a Pro Tools issue.
Tapeit has some gain control that it applies, this is likely what I'm preferring, and I prefer standing on my right leg while howling at the window, as opposed to the left, where I've got some sciatica.I render all the time, 16bit and 24it, have no problem with either, I also have silver spikes tape it but it has now become a pain and is much easier to just render, like i said never any problems. my setup is a panasonic laptop centrino and an amd desktop both get the job done right.
UTENZIL a tool... of the muse.
Played the movie in Cubase on a separate computer...but in the end, we could've used quicktime to do the same. All the musical elements were done in Ableton.Benshik wrote:Hi shtreimelshtreimel wrote:Wrote, recorded and mixed and entire score for a major documentary film (to be released in Canada Fall '05) only using Live. That's it, that's all....zip. No other software was used. The only comments from the NFB (National Film Board of Canada) that my partner and I received was: "Excellent music".
you say no other software was used for the ENTIRE score? How did you sync the music with the picture, as Live doesnt have video capabilities?
Or was it some tune that that guys in NFB tagged theirselves to the edit? In this case, they often re-process...
Cheers
Ben
-
Robert Henke
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
Okay, here comes the secret science behind render.
Usually a realtime audio application is calculating everthing it needs to calculate for processing one single sample which is then sent to the soundcard, then it waits till it needs to calculate the next sample and so on. If it needs only half of the time between two samples to calculate everything, your CPU load is 50%. If you try to calculate more then you can handle before the soundcard wants the next sample you`ll get a problem. Some applications do the same but with blocks of samples, say 64 samples at once. But the basic idea is the same. When rendering, the computer does not need to wait for the soundcard, and instead of waiting it starts calculating the next sample immideateley after it finished the current one. As you see, there is no difference in sound quality, because the soundcard or the file does not even know how much time the computer spends with waiting...
But:
The internal processing is done with 32 or 64 bit. The soundfile has 16 or 24 bit. If you have a sound file and you put the fader almost all the way down the file internally still has a good resolution, but if you record/render it with 16bit you will maybe end up using ony 12 bit and this is definitly audible. Also internally there is no upper limit for headroom ( well _almost_ no limit), but if you record/render a file with +6dB peak you will get ugly clipping.
Normalise:
If normalise is turned on, Live does two passes: In the first pass it runs thru the whole file and is looking for the maximum peak. If this is -6.32 dB, then it stores this value.
In a second step it raises the master volume slider internally by 6.32dB before rendering. Now you will get a file where the maximum is at 0.0dB.
After the rendering, the Master Volume is restetted to it`s previous value.
Consolidate does the same trick and this is why the clip volume slider ist allways at -xxx after consolidate.
This ensures that the consolidated file has the best possible resolution on disk.
Hope this helps a bit.
Robert
Usually a realtime audio application is calculating everthing it needs to calculate for processing one single sample which is then sent to the soundcard, then it waits till it needs to calculate the next sample and so on. If it needs only half of the time between two samples to calculate everything, your CPU load is 50%. If you try to calculate more then you can handle before the soundcard wants the next sample you`ll get a problem. Some applications do the same but with blocks of samples, say 64 samples at once. But the basic idea is the same. When rendering, the computer does not need to wait for the soundcard, and instead of waiting it starts calculating the next sample immideateley after it finished the current one. As you see, there is no difference in sound quality, because the soundcard or the file does not even know how much time the computer spends with waiting...
But:
The internal processing is done with 32 or 64 bit. The soundfile has 16 or 24 bit. If you have a sound file and you put the fader almost all the way down the file internally still has a good resolution, but if you record/render it with 16bit you will maybe end up using ony 12 bit and this is definitly audible. Also internally there is no upper limit for headroom ( well _almost_ no limit), but if you record/render a file with +6dB peak you will get ugly clipping.
Normalise:
If normalise is turned on, Live does two passes: In the first pass it runs thru the whole file and is looking for the maximum peak. If this is -6.32 dB, then it stores this value.
In a second step it raises the master volume slider internally by 6.32dB before rendering. Now you will get a file where the maximum is at 0.0dB.
After the rendering, the Master Volume is restetted to it`s previous value.
Consolidate does the same trick and this is why the clip volume slider ist allways at -xxx after consolidate.
This ensures that the consolidated file has the best possible resolution on disk.
Hope this helps a bit.
Robert
-
montrealbreaks
- Posts: 995
- Joined: Thu Mar 04, 2004 11:38 pm
- Location: Montreal Canada
Cool. I want to help. Hey Robert, does Ableton wanna start up a Montreal office?MrSleep wrote:Hay Robert..., is it true that.., you and the other guy, (I forget his name), go through the threads and have a lough about some of the silly posts being made in a fancy hotel with lots of beutiful lapdancers and booz???
I have changed my username; Now posting as:
M. Bréqs
all of my renders sound great... not complaints here.
but then again, I am also on a mac.
15" powerbook G4 1.25ghz.
but then again, I am also on a mac.
15" powerbook G4 1.25ghz.
http://dustbreeding.com
http://www.unrecnow.com
___________________________
macbook|monome 128/64|kmxmini
http://www.unrecnow.com
___________________________
macbook|monome 128/64|kmxmini