[Repro-1] Public Beta

[Hanz Meyzer]

I ran into the following problem while using this repro 1 beta in Renoise 3.1 64bit OSX:



As you can see in the video, the first pattern will played with totally overused CPU, but from 2nd pattern, the replaying starts to be fine.

This is very strange, because the 2nd pattern starts to use lot of more instances. Also the option "disable on silence" is deactivated.

Also as you can see in the video, after 2nd pattern, also the 1st pattern starts to play fine.

Though my assumption would be, that either your plugin or Renoise is causing denormal slowdowns, if the instance wasn't played yet? And since Renoise works flawlessly with most synths, I would assume that it's a repro1 problem?

[Urs]

This is killing my CPU, much worse than Diva. Anything I can do to optimise?

You don't need to do anything. It's a beta, the final version will be much more optimised.

Hmmm... any chance of getting it optimised while its still cheap? Dont want to risk leaving it, only to find its been optimised very little....

The current discount is because of the risk of buying into a beta.

Doesnt answer my question.

Yeah, hmm... then the answer is "not very likely" I'm afraid... I'll be happy to report on progress but I'm not going to post betas without finally optimised code. There might be one with the sequencer stalls/freezes fixed.

Sometimes we do a sanity check for the release candidate, say, overnight before release. That would be a good opportunity to get a "risk free" intro offer, but considering how smooth the current beta phase runs, I'm not sure we'll need to do this.

[Urs]

I ran into the following problem while using this repro 1 beta in Renoise 3.1 64bit OSX

Do you use Repro-1's built-in sequencer or arpeggiator? - There is a known issue with debug code that can stall the DAW for a few seconds.

Otherwise it would be great to get the project so the devs can reproduce the issue...

[simonfloris]

Hi,

i just noticed that when I change the LFO to Host Sync, the LFO controls do not change appearance (as suggested in the manual) but instead the modulation source labelled as "LFO" is coming from the Clock Control ( changing the rate of LFO does not has any effect anymore).
Is this a known issue?

[Hanz Meyzer]

I ran into the following problem while using this repro 1 beta in Renoise 3.1 64bit OSX

Do you use Repro-1's built-in sequencer or arpeggiator? - There is a known issue with debug code that can stall the DAW for a few seconds.

Otherwise it would be great to get the project so the devs can reproduce the issue...

Oh yes, I use the sequencer. Where can I mail the song file to?

[zvenx]

I am sure others have mentioned it in the thread, just perchance if they haven't, seems like pattern A and B are now called pattern 1 and 2, manual refers to pattern A and B, and the gui refers to pattern 1 and 2, except the root notes..I imagine you would want to change that from A, B to 1 and 2.
thanks
rsp

It was a last-minute-rename. The User Guide will be updated accordingly

Well it would need the user guide AND the root notes labeling. no?
rsp

[acidsmiley]

The cutting thru sound, the inspiring sequencer, the gorgeous GIU and NKS support make it a great synth. Bought it right now and used it already in a current project. This is my first U-he synth and I´m really happy with it. Thank you!

[lentferj]

This is my first U-he synth ....

You missed a lot then until now

[Urs]

Well it would need the user guide AND the root notes labeling. no?
rsp

Certainly!

[Urs]

I ran into the following problem while using this repro 1 beta in Renoise 3.1 64bit OSX

Do you use Repro-1's built-in sequencer or arpeggiator? - There is a known issue with debug code that can stall the DAW for a few seconds.

Otherwise it would be great to get the project so the devs can reproduce the issue...

Oh yes, I use the sequencer. Where can I mail the song file to?

Great! Please send to support@u-he.com, maybe with a link to your post.

There is a known issue with the sequencer freezing up. The guys are working hard on fixing this.

[sqigls]

Maybe a bug, maybe just a current limitation of the preset system, could even be the OS (Windows here) but apostrophe's don't show up correctly. Example: I name a preset LEAD - Let's Go Sync and it turns into Lead - Let_s Go Sync. Would be nice if these showed up in the browser as written.

Also any chance of getting delay time values or (note values) to appear in Lyrebird? Same request for things like the frequency in the EQ.

U-he don't DO delay times or frequencies.
Just 0-100, so friggon annoying sometimes

[Funkybot's Evil Twin]

Maybe a bug, maybe just a current limitation of the preset system, could even be the OS (Windows here) but apostrophe's don't show up correctly. Example: I name a preset LEAD - Let's Go Sync and it turns into Lead - Let_s Go Sync. Would be nice if these showed up in the browser as written.

Also any chance of getting delay time values or (note values) to appear in Lyrebird? Same request for things like the frequency in the EQ.

U-he don't DO delay times or frequencies.
Just 0-100, so friggon annoying sometimes

Yeah, this bothers me about Diva too, but it sounds like it's on the to-do list.

[Funkybot's Evil Twin]

Here's 20 presets for anyone interested. Been having a lot of fun making these.

[Funkybot's Evil Twin]

With certain more "soft" patches even at maximum mixer volumes and maximum main volume those are still a bit too quiet, at least they do no reach a state were they do clip when seting the mixer at the host track to a 0dB level.

Would it be possible to add some additional gain somewhere, mybe in the preferences? Maybe something like +3dB, +6dB and +9 dB (while mostly +6 dB should be enough).

With Diva i never seemed to have the problem that it is too quiet.

I've used the Sonic Conditioner once or twice where this became a problem, but I agree more output would be a "nice to have." The Sonic Conditioner adds some saturation, so it's not clean gain. If it were possible to add another 6db to the output knob's range without breaking things, I think it would be worth adding. Otherwise, I'll just compensate elsewhere.

[david.beholder]

ya'll to young

It was about 1980, I was about 20 years old, and used a computer for the first time ever in a computer class (Fortran). You had to type out a bloody punch card for every command line, turn in your stack of cards, and come back hours later to see what happened (it never worked right the first time). I don't miss those days.

Despite usual use I'm thinking limited 8 bit assembler like avr in machine codes might be not bad on punch cards - especially with fixed lenght of instruciton to one column. Other than that it's totally no fun.

he can have it back once I finish a new model for a Diva update, adding 5 years of experience back into it

Such a great news.