exporting issues - TranceAddict Forums

TranceAddict Forums (www.tranceaddict.com/forums)
- Production Studio
-- exporting issues

Posted by celestialmind on Oct-05-2006 14:19:

exporting issues

Guys, I've posted about this before but it was hard to get answers from folks. I've posted this topic on several forums with no avail.

When I export my track as an audio file out of reason 2.5, it exports it but when I try playing it in winamp, it plays a minute of the track or so, and then either starts stuttering, goes mono, or simply stops and there is no sound. I've exported it over 7 times last night after I recall somebody saying that the reason won't properly read the track after the first 5 or 6.

I've saved it as a wav. file, I've messed around with bit rates, I've changed settings to save cpu, and blah, blah blah. For some reason, it exports the first part of the track but after a minute or so, for whatever reason, the audio doesn't get transfered. Does anyone have any ideas as to what else could be wrong with it? My guess is Ram, but I got 512 so I doubt that that's it.

Posted by Synchronicity on Oct-05-2006 19:18:

Is it only winamp this happens in?

Have you opened the wav in soundforge or any other audio editor to see if the problem is with reason?

If the wav goes blank half way through in the audio editor, the problem is with reason. If this is the case, does it happen with every reason project you have?

Posted by KilldaDJ on Oct-05-2006 20:00:

is it a erm...how should i put this...dodgy version of reason?

Posted by celestialmind on Oct-05-2006 20:06:

quote:
Originally posted by KilldaDJ
is it a erm...how should i put this...dodgy version of reason?
no, I bought it with my Midi Ozone as a pack few years back, even registered it along with reason adaptaded and recycle 2.1. Totally support all the products by propellerheads because of everything it has offered me - being able to create music to my liking.

As for the questions for Synchronicity, It's beeen doing that lately, pretty much after I had to reinstall reason after my hdd crashed on me. I'm assuming it may have something to do with cpu usage but not sure. I know it's not winamp 'cause the other day I forgot to check the quality of the track and simply exported it out to listen to it on a cd in a car and had the same problem, after 30 seconds or so it started to stutter and then wen't entirely blank. Haven't checked in soundforge yet, will do that tonight. Do you guys know what in reason may be causing it?

Posted by Synchronicity on Oct-05-2006 22:43:

Well it's probably safe to say the problem's with reason. I doubt if it's a ram or cpu, no menu setting should cause that either. It sounds like a bad install to me - have you reinstalled reason since this started? If not, it wouldn't do any harm to give it a go. I also have a program called 'registryfix' which helps clean the registry - in this type of situation I'd run it between the uninstall and re-install, and also clear my temp folders.

Posted by celestialmind on Oct-05-2006 22:52:

quote:
Originally posted by Synchronicity
Well it's probably safe to say the problem's with reason. I doubt if it's a ram or cpu, no menu setting should cause that either. It sounds like a bad install to me - have you reinstalled reason since this started? If not, it wouldn't do any harm to give it a go. I also have a program called 'registryfix' which helps clean the registry - in this type of situation I'd run it between the uninstall and re-install, and also clear my temp folders.
you maybe right. I didn't have this problem before but ever since I reinstalled it I started happening. I'll try reinstalling it again tonight, in the meantime, do you think there is anything I can do prior to reinstallation to save me the headache? I've already messed around with bit rates and so forth.

Posted by substorm on Oct-05-2006 23:11:

Try this out. Put the left loop marker all the way to the start of the track and the the right loop marker all the way to the end of the track. Then dubble click on Stop so that the start marker is at the start. Now render it and see what happens!?

Posted by celestialmind on Oct-06-2006 00:03:

quote:
Originally posted by substorm
Try this out. Put the left loop marker all the way to the start of the track and the the right loop marker all the way to the end of the track. Then dubble click on Stop so that the start marker is at the start. Now render it and see what happens!?
I did that too dude. It still didn't work.