4.1 Issues

Can't you use a clock oscillator for sync purposes? I mean that's what its made for.

 

well, i need a clock with audio sample rate and sample accurate duration of the clock signal. clock osc is event typed one. of course i can try to make such audio clock with few other modules, but i'll loose cpu power and probably quality.. nevermind...

 

Why would you need sample accurate duration of the clock signal? The important part is the rising slope... that's really all you should be using out of a sync oscillator. If you need something to sustain from that, I'd use a hold envelope.

 

Menus

Well, I finally got round to putting R4 on my new PB 15", and went straight to 4.1 - because that's how we move forward, right? Well, no real problem so far, but then I'm not really caning Reaktor. But I do want to add my oice here and say please, PLEASE get rid of the single-click menus. They are already driving me to distraction. It's safe to say that if I take the time to click on a menu, there's something in there I want to do, and another click is not a hardship. What IS a hardship is having to hold down a laptop mouse buttton until I've made my choice (and I shouldn't have to be moving my pointer around to bypass this). When an ensemble has a lot of snapshots, this becomes a major hassle. It may work for others, I know, so I suppose the optimum solution is to make it a preference setting. I can tell right now that this is going to become a major bugbear for me. It sounds trivial, but it's a core part of Reaktor - something that affects every session. It's subtle, but vital. Thanks for listening.

 

4.1 Midi out timing problem

I have an ensemble with a simple 8step sequencer controlled by 'sync clock', sending 1/8 notes with 1/16 duration via midi out pitch/gate to an external sound module. It worked well with version 4.0, but with 4.1 there are serious timing problems, ie. the pattern sounds -very- uneven. In fact, monitoring the midi messages shows uneven note starts and some durations exactly doubled. This misbehavior is independent of setting 'midi clock out' to on/off. I think it's easy to reproduce. Can somebody confirm?

Now, I've also used the ensemble to sync and record the midi notes on Logic (via virtual connection, midi clock out). Surprise: the notes are played thru and recorded with correct timing!

mb

(MacOS 10.2.6, LAP 6.3.1)

 

yeah, there is something like sustain, but it should be totally audio typed. hold envelope's "H" is event typed.

 

well, there is now at least 1 other thread about this pulse "bug" so forgive me if i repeat myself but, zedah bro, i'm not trying to call you a newbie, i'm trying to explain why this thing is not a bug. if you have your reaktor manual (the paper one), open it and you will see that the "dc offset" property of the pulse osc is deliberate. it's explained IN the manual.

and if you have a pulse osc slowed down enough to be a "clock" then you are going to hear what sound like clicks as the output jumps from pulse to pulse. since the wave is supposed to have infinite slope at these points, every harmonic that your audio rate can handle is going to be present for 1 sample, which you will hear as a click.

again, if you'd post what exactly you're trying to do, we could have a much more meaningful discussion about this. as it is, it's not a 4.1 specific "bug" and not really a "bug" at all.

pete

 

i don't hear any click, but i see it in a wave editor. as i already said in "4.1 problems" thread, generator 1.53 doesn't produce clicks, but 4.x does. ok. anyway, forget my stuff, since i clearly can see how to fix my ensembles there is no any point to continue disscussion. thanks for replies to everybody.

 

well, i just don't understand: if you're using it to clock, why are you looking at the output of the clock in a wave editor?

i mean, i don't really think it's fair to get on everyone's case here, including jwh-- who i think does a smash-up job-- over something that you won't care to explain. it's not a bug, the behavior you describe (near as i can tell since you haven't elaborated further) is documented in the manual.

i'm not sure what the point of comparing reaktor 4.1 to generator is, but anyway, i hope things work out. i mean, i'd like to hear what you're doing just because i'm curious at this point.

pete

 

Ditto, what are you doing anyway?

Watch, its a physically modeled grandfather clock or something.

 

guys, i'm really sorry about my screaming, it's stupid of me. i just got something i didn't expect and started to scream, seems it's bad part of my temper, that's my own bug

anyway, i don't want to tell you what exactly i'm doing. but i can say that after few years of checking out the same synths i got tired, now i'm just doing some experiments with sampler, wide range modulations and etc. nothing very special. i don't think i can do something really new, but with reaktor do it more flexible than ever.

 

r4.1 mac os9 vst in logic pro 6.4.1

1)when using the granular resynth samplers and loading any audiofile into them within logic, things get very very slow. it may take up to 2 mins to load even a short sample. every action that opens or closes the sample map editor will make you wait equally long...->unusable. am currently opening the standalone app for ANY editing in the sample map.

logic pro 6.4.1, os 9.2.2, 1.5gig of ram, r4.1as vst, g4 quicksilver 867mhz, really fresh system install free of BS

2)when loading a 24 bit sdII file into a resynth module, everything will work up to the point where you are asked wether you want to save the analysis data into the file...then the machine freezes. or maybe it is just a case of 1) extended to something like 10 mins?

 

grain cloud

here's one i haven't seen here in the forum.


i run a g5 2.0 dual with panther 10.3.1 and an ibook 733

the issue is with polyphony on the grain cloud module. in the last version connecting the module in a polyphonic instrument to the outs would make reaktor sputter and quit. this version seems to be a little more stable to even being connected - but there are still serious problems. navigating root keys in the sample maps or event resets from wire reconnections can cause quits. the display cannot decide on a voice to show - it flutters back and forth between them.

most of my work is based on table based key recall concepts which require the use of polyphony. i have succussfully applied this to the audio table and grain delay modules (thank you clist), but there is a whole other world out there with the simple "sel" input of the g.c.

please if any reaktor honchos are aware of this you should know that there is some good music waiting if youd just fix that module for the new macs

(ps i confirmed it on my other machine and these effects can be seen on jwh's granulator)

 

4.1 and logic problem

I've had reaktor 4.1 for a few days now. At first it worked standalone but not as a plug-in in Logic 5.5. Now it doesn't even work standalone. Has anyone else had this problem? I've had innumerable problems with reaktor ever since I bought it at version 3. Frankly it's really embarassing for you guys at Native Instruments. Don't you care about your reputation as a company? You're among the least reliable companies out there. What's up?
I'm not a beta tester.... I bought the software. So why do I have to deal with beta style problems?

 

Re: r4.1 mac os9 vst in logic pro 6.4.1

any reason u use the vst instead of audiounits?

i'm quite happy with the AU in logic pro 6.4.1 right now....i also own vst-to-au adapter, but never thought about using the reaktor-vst....

thx

 

Re: Re: r4.1 mac os9 vst in logic pro 6.4.1

Audio Units is OSX only and the only built-in standard in Logic under OSX (VST adapter not withstanding which does work quite well for those plug-ins not written as AU). VST is the only supported format for Logic under OS9.

 

hold module

hi guys,
the behaviour of the hold-module has been changed. now, you can't estimate the sustain time in ms anymore. and the comment in the info box about this module seems not to be very helpful. how does the control rate relate to the value of time set to hold at the hold-time-input? in other places where the functionality of a module has been changed a clickbox in the properties page is offered to restore the old behaviour which is normally enabled for ensembles written in older versions. this can be seen in the new iteration-module for example. and i really like this and am hoping to have that opportunity also in the hold module - at least for ensuring backward compability. the "h"-envelope seems to function completely in a different way than the hold module and i did not get the function of the old hold-module with that h-env-module imitated. plus you need a value converter to go from msec to the log-range of the envelopes. aside from the cpu-spike of the tapedec, i never noticed things like that with regard to the hold-module or any other modules under normal circumstances.
the other updates i found i really liked, except the auto-close behaviour of the shapshot menue... with keeping the mouse depressed and moving it outside the menue, the menue will then stay open. how is one supposed to select a snapshot in large banks without a mouse wheel or that trick mentioned above?? but those things are more a cosmetic thing. by the way, on windows one is able to resize the snapshot browser. if you do so the gui does not correctly resize (the upper part stays the same whereas the lower changes). additionally, if the position of the snapshot menue in the instrument tray would switch places with the position of the number of voices assignment "boxes", the menue would profit from wide instruments and longer snapshot names would be readable.
anyway. the programmers did a great job in the recent update and we should credit this. e.g.: do you remember the shift of position of any module to some distant, invisible corner the screen when being copied and pasted? this does not happen anymore!!!

regards,
popup

 

Re: Re: Re: r4.1 mac os9 vst in logic pro 6.4.1

hehehe, sorry for such a stupid question...shouldn't post anything past 5am....... didn't notice the "os 9.2.2"....ttssskkk....

 

Re: 4.1 and logic problem

i really don't think that Logic 5.5 is supported anymore. i think you need to update to 6.

try, re-installing 4.1 . hopefully the standalone will work then?

sowari

 

Hi,
sorry for my crappy english...
Since i'm running the 4.1 update, i got problems on a selection of ensembles, a lot of snapshots i made don't sound right anymore, i'm not an ensemble builder myself, i just use premade ensemble that i modify a little bit...
So, does anyone got similar problems with snapshots ?....
It happens with the Prophet 52 ensemble from the user library (the "release" button is switched on , even though i resave it off, which is annoying..)