Samplerate and Reaktor

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
kaju
Posts: 160
Joined: Mon Mar 08, 2004 4:00 pm

Post by kaju »

I would like to change the samplerate from 41k to 48k.
All my other instruments let me do it after I have changed it in Scope, and perform ok, but not Reaktor. It works ok under Cubase VST 5.2, but not as a standalone.
My card is Luna II with Scope 3.1.

kaju
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

not a help for your present problem, but i would suggest that 44.1khz is the best sample rate to use if you plan on ending up on cd. 48khz will not give better results. downsampling from 48khz to 44.1khz(the cd samplerate) will eliminate any modest gains from working at 48khz and probably make the quality worse than starting at 44.1khz in the first place. the difference would be very slight in either case, probably only noticeable to a trained ear on a very good system(or maybe more noticeable than that, in some situations...).

gotta leave it to a reason user to tell you the secret of how to make reason lock to scope's clock(i'm sure it's a setting in reason)....

<font size=-1>[ This Message was edited by: garyb on 2004-09-24 03:59 ]</font>
kaju
Posts: 160
Joined: Mon Mar 08, 2004 4:00 pm

Post by kaju »

garyb,

I'm sure there's a reason of using reason, but I have no Reason as I'm using Reaktor.
Thanks anyway.

By the way,I think I can hear the difference. That's why I wanted to make the change. However, it's still just an experiment.

kaju

<font size=-1>[ This Message was edited by: kaju on 2004-09-26 15:10 ]</font>
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

uhhh, reaktor....
same advice.
i don't doubt you hear a difference. just not a positive one in the final product. good luck on your quest.
kaju
Posts: 160
Joined: Mon Mar 08, 2004 4:00 pm

Post by kaju »

Thanks garyb, your advice is of course the right one. I mean I just thought similarly myself. The point is Reaktor doesn't let me change the samplerate when it's working as a standalone unit. As a VST instruments its ok. As it should.
I'll toy with this small problem still for awhile. Nothing really tragic at all :smile:

kaju
User avatar
valis
Posts: 7684
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Post by valis »

Setting the samplerate in SFP to 48khz while nothing is open (ie, using the ASIO driver) and then running reaktor doesn't work?
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

yeah, that makes sense. you probably need to restart reaktor after you change the samplerate.
User avatar
valis
Posts: 7684
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Post by valis »

Well...I tried testing your problem.

After downloading and installing the Reaktor 4 demo I had everything set to 44.1Khz. When I change samplerate in SFP first to 48Khz with Reaktor running, Reaktor crashes immediately.

Running SFP first and setting it to 48Khz results Reaktor crashing on loading (its set to 44.1 in its config and you never get a prompt detecting the change in samplerate).

Running Reaktor first and changing to a default (but unloaded) SFP wav driver resulted in an error but the app loaded. I then launched SFP.exe and changed it to 48khz. Back in Reaktor I went into the Audio&Midi config page and selected the ASIO driver and again Reaktor crashed. It occured to me that 44.1 was still set in the dropdown menu so I closed SFP and again launched Reaktor by itself, set it to a nonexisting wav driver, launched SFP.exe and set it to 48khz, selected 48khz FIRST from the dropdown in reaktor then selected the ASIO page to get the SCOPE asio driver and CRASH......

Running SFP.exe again and loading Reaktor and everything works fine except its now stuck on the Multimedia driver. So I reselected ASIO and hit OK and everything works fine... in 44.1khz.

I have no idea why it won't work in 48khz but its the first app I've seen with that behavior. I don't run many NI standalone apps (or much NI at all anymore) but I'd say its probably something they need to address...
Post Reply