To tell you the truth (I'll probably regret admiting this), I've never really been able to tell the difference between the higher resolutions and regular 16bit/44.1. I mean I can definitely tell the difference between 22khz, and 44.1khz. But not between 48khz, and 41khz, or between 16bit and 24bit. I had a DAT machine that recorded at 48khz, and I worked in PT for a while at higher resolutions but I really never could tell the difference.
Maybe I just have a tin ear or something. But it seems that we're more limited by our own ears than our equipment anymore. I mean theres a certain range that people can hear. I dont make music for dolphins and bats. Mostly humans listen to my music so as long as I'm in their hearing range its all good.
Focus on exporting!!!
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Incidentally Aleatoric, i've never called you an asshole, but surely you can see that posting multiple threads about the same problem to bring it to the developer's attention doesn't help anything?
My girlfriend once travelled across the sahara desert as a kid with her folks, and as you'd imagine, it's a wee bit hot, dry and dusty. So all the white british people were struggling a bit, especially one guy who kept going on and on about the heat, how tired he was etc. Eventually this guy complains one time too many to one of the local dudes, basically how can you guys live out here with all this heat and dust and heat and dust? And the guy said we get by because we have to. We all know it's hot. We all know it's tiring. We all know it's dusty. But it's 3 times as hot when someone moans about it.
I'm not saying you shouldn't expect the rendering problems to be sorted. I'm sure Jules wants them sorted too. Why wouldn't he? Why wouldn't anyone? But continually going "They're not sorted yet, why hasn't this been done yet?" doesn't sort them. Trying to establish a common issue when they fail might help sort them.
The way this thread is now going is the way it should do, people saying "I sometimes get the problem when I do this", things that can be tested and might lead to a solution.
Look, we all want T to be great, okay? Peace
chico
My girlfriend once travelled across the sahara desert as a kid with her folks, and as you'd imagine, it's a wee bit hot, dry and dusty. So all the white british people were struggling a bit, especially one guy who kept going on and on about the heat, how tired he was etc. Eventually this guy complains one time too many to one of the local dudes, basically how can you guys live out here with all this heat and dust and heat and dust? And the guy said we get by because we have to. We all know it's hot. We all know it's tiring. We all know it's dusty. But it's 3 times as hot when someone moans about it.
I'm not saying you shouldn't expect the rendering problems to be sorted. I'm sure Jules wants them sorted too. Why wouldn't he? Why wouldn't anyone? But continually going "They're not sorted yet, why hasn't this been done yet?" doesn't sort them. Trying to establish a common issue when they fail might help sort them.
The way this thread is now going is the way it should do, people saying "I sometimes get the problem when I do this", things that can be tested and might lead to a solution.
Look, we all want T to be great, okay? Peace
chico
"my gosh it's a friggin hardware"
-
- KVRist
- 274 posts since 11 Jun, 2004
okay guys
ive asked jules to put up a known bugs sticky
so hopefully that'll be there soon
so no more fisticuffs
cheers
ive asked jules to put up a known bugs sticky
so hopefully that'll be there soon
so no more fisticuffs
cheers
I aint famous enough to be handin out signatures
-
- Chief Tracktioneer
- 532 posts since 14 Nov, 2002 from London
Right..Jules please focus on exporting problems in mac OSX.......lots of times there is skips midi note problems etc that only occur while exporting a wav file and not during normal playback....ie...my song sounds great so I export it as a wav file (aiff 24bit dont work at all) and it has all sorts of little errors including midi that was perfectly in synch not being in synch or cut notes.....specifically if there is a long ride cymbal hit that is say 6 seconds it is cut off after 3 seconds......this type of shit makes me not want to use Tracktion.......cause I scared the more time I put into a track the more dissapointed I will be by render errors. This is a must......also see monkatron's (professional sound designer for MTV) post about exporting errors on a mac. Also the one click render needs to be 24 bit already! sheeeeesh.....Jules should hire, valley, Modular and the Karbon dude to do his dirty work! Whatever......for some reason I feel reporting bugs here is pointless anyway....Jules proably wont read it if he does he will just right it off and other forum members will explain in one way or another that I am a winer, life is not perfect, niether is software and of course....Jules is only one man and a busy one at that.......Please start working on a better version 1.5 than all this version 2 shit that is keeping me from having a solid Tracktion.
1) 24-bit aiff does work on the mac. For some reason Quicktime doesn't play the files right, but iTunes and other apps have no problem reading them, therefore there's nothing wrong with them. I made sure to use the lowest common denominator aiff format for exporting, but can't guarantee it'll work with every reader out there.
2) Track render - this will be 24 bit if your audio card is 24-bit. If your audio card isn't 24 bit then you can use the normal renderer - I'm sorry if that takes an extra couple of seconds to acheive the same result, but life can be tough. I'll try to live with the guilt.
3) If your rendered song has problems like notes cutting off early, that's bad, but probably due to the synth you're using getting confused when it's rendering at greater-than-realtime speed. There's no point me trying to recreate this - I could spend weeks without it happening - but if you've got a small project that shows up the bug, then email it over to me and I'll take a look.
And that's a good general rule if you need a bug fixing: I've no time to sit here reading through paragraphs of unpunctuated ranting looking for clues about bugs and then trying to reproduce them myself - but if you can send me a project file that will instantly reproduce the problem, and a quick, clear explanation, then I'll probably look at it immediately.
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
jules,
how do we send it to you? just by email?
also, btw i think we should quote jules comments on bugfixing and put it as a sticky on top so we stop getting people who ruin the sanctity of the board
Thanks
RonC
how do we send it to you? just by email?
also, btw i think we should quote jules comments on bugfixing and put it as a sticky on top so we stop getting people who ruin the sanctity of the board
Thanks
RonC
-
- Chief Tracktioneer
- 532 posts since 14 Nov, 2002 from London
yeah - the more concise the better! My email address is in my signature, so you can use that rather than going via the KVR email thing.how do we send it to you? just by email?
-
- KVRist
- Topic Starter
- 199 posts since 2 Mar, 2003 from NYC
Jules regarding number 2, this is not so. In PC Tracktion track rendering is 24bit if your audio card is. I am on the mac version using a 24 bit audio card and Tracktions track rendering is 16bit. Others get the same result. Please address this in the next Tracktion built so the mac version is like the PC version and track rendering IS 24bit if your audio cards output bit rate is 24bit. Thanks for your time.
-
- KVRist
- Topic Starter
- 199 posts since 2 Mar, 2003 from NYC
I set a similar email to Jules as my post above and I got back some good news.
Hi there
Ah - ok.. I did check this today before I posted, because it's
exactly
the same code for mac + pc, so it should work identically, but you
made
me think and I dug a bit deeper.. turns out that my CoreAudio code
was
always saying it's 16 bit even it it's not. I'll get that sorted out
for
the next point release.
Thanks for forcing me to look into this one, and sorry for doubting
everyone!
All the best
Jules
So things will work accordingly for mac users as PC regarding track rendering and your audio card! Great news. Thanks bunches again Jules.
Hi there
Ah - ok.. I did check this today before I posted, because it's
exactly
the same code for mac + pc, so it should work identically, but you
made
me think and I dug a bit deeper.. turns out that my CoreAudio code
was
always saying it's 16 bit even it it's not. I'll get that sorted out
for
the next point release.
Thanks for forcing me to look into this one, and sorry for doubting
everyone!
All the best
Jules
So things will work accordingly for mac users as PC regarding track rendering and your audio card! Great news. Thanks bunches again Jules.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
We can all sleep safely in our beds again. Until next time true believers, same bat time, same bat channel
"my gosh it's a friggin hardware"
-
- KVRian
- 500 posts since 27 Nov, 2003 from Oslo, Norway
HURRA!!!
-
christianmusicmaker christianmusicmaker https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=12152 - KVRAF
- 1670 posts since 1 Feb, 2004 from UK
jules wrote:
Right..
1) 24-bit aiff does work on the mac. For some reason Quicktime doesn't play the files right, but iTunes and other apps have no problem reading them, therefore there's nothing wrong with them. I made sure to use the lowest common denominator aiff format for exporting, but can't guarantee it'll work with every reader out there.
2) Track render - this will be 24 bit if your audio card is 24-bit. If your audio card isn't 24 bit then you can use the normal renderer - I'm sorry if that takes an extra couple of seconds to acheive the same result, but life can be tough. I'll try to live with the guilt.
3) If your rendered song has problems like notes cutting off early, that's bad, but probably due to the synth you're using getting confused when it's rendering at greater-than-realtime speed. There's no point me trying to recreate this - I could spend weeks without it happening - but if you've got a small project that shows up the bug, then email it over to me and I'll take a look.
And that's a good general rule if you need a bug fixing: I've no time to sit here reading through paragraphs of unpunctuated ranting looking for clues about bugs and then trying to reproduce them myself - but if you can send me a project file that will instantly reproduce the problem, and a quick, clear explanation, then I'll probably look at it immediately.
I assume Jules is referring to the bit depth setting in the properties panel for the wave device section in Tracktion. (Correct me If I am wrong).
If this is so, is this only a Mac issue or is it a PC one as well?
My question is…using the PC version of Tracktion…I assume
A. Track renders in a 32 bit project will be rendered as a 32 bit file (if the bit depth setting in Tracktion is 32 bit)
B.Track renders in a 24 bit project will be rendered as a 24 bit file (if the bit depth setting in Tracktion is 24 bit)
C. Track renders in a 16 bit project will be rendered as a 16 bit file (if the bit depth setting in Tracktion is 16 bit)
Also that file *exports* audio or midi will have the same bit depth value that is set for any wave device in the properties panel under the settings page in Tracktion using the *bit depth* setting.
Is this correct?
Anyone?
-
- KVRian
- 500 posts since 27 Nov, 2003 from Oslo, Norway
>If this is so, is this only a Mac issue or is it a PC one as well?
PC is fine. Mac render "into project", and "freeze" is only 16bit at the moment.
But "export" is fine.
>My question is…using the PC version of Tracktion…I assume
>A. Track renders in a 32 bit project will be rendered as a 32 bit file (if the bit depth setting in Tracktion is 32 bit)
yes
>B.Track renders in a 24 bit project will be rendered as a 24 bit file (if the bit depth setting in Tracktion is 24 bit)
yes
>C. Track renders in a 16 bit project will be rendered as a 16 bit file (if the bit depth setting in Tracktion is 16 bit)
yes
>Also that file *exports* audio or midi will have the same bit depth value that is set for any wave device in the properties panel under the settings page in Tracktion using the *bit depth* setting.
>Is this correct?
yes!
PC is fine. Mac render "into project", and "freeze" is only 16bit at the moment.
But "export" is fine.
>My question is…using the PC version of Tracktion…I assume
>A. Track renders in a 32 bit project will be rendered as a 32 bit file (if the bit depth setting in Tracktion is 32 bit)
yes
>B.Track renders in a 24 bit project will be rendered as a 24 bit file (if the bit depth setting in Tracktion is 24 bit)
yes
>C. Track renders in a 16 bit project will be rendered as a 16 bit file (if the bit depth setting in Tracktion is 16 bit)
yes
>Also that file *exports* audio or midi will have the same bit depth value that is set for any wave device in the properties panel under the settings page in Tracktion using the *bit depth* setting.
>Is this correct?
yes!
-
christianmusicmaker christianmusicmaker https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=12152
- KVRAF
- 1670 posts since 1 Feb, 2004 from UK
Many thanks...!Sleepwalker wrote:>If this is so, is this only a Mac issue or is it a PC one as well?
PC is fine. Mac render "into project", and "freeze" is only 16bit at the moment.
But "export" is fine.
>My question is…using the PC version of Tracktion…I assume
>A. Track renders in a 32 bit project will be rendered as a 32 bit file (if the bit depth setting in Tracktion is 32 bit)
yes
>B.Track renders in a 24 bit project will be rendered as a 24 bit file (if the bit depth setting in Tracktion is 24 bit)
yes
>C. Track renders in a 16 bit project will be rendered as a 16 bit file (if the bit depth setting in Tracktion is 16 bit)
yes
>Also that file *exports* audio or midi will have the same bit depth value that is set for any wave device in the properties panel under the settings page in Tracktion using the *bit depth* setting.
>Is this correct?
yes!
