What'S The Current State Of 1.8 Voting Results On Backstage?

[Jonas (Djeroek)]

lol at direct x plugin support, how time flies.

[rhowaldt]

this makes me wonder, it states:
“new votings will soon be available”

not so soon imo

but seriously, was feature-voting just a thing of the past, now revoked in favour of the current “don’t ask don’t tell” policy? (not bashing the policy, i enjoy the suprise every time)

[maes]

@gentleclockdivider

yeah for sure ,I registered renoise 1.9 …that was back in 2008 …renoise has come a long way …the developers are on roll .

great

haha, i heard that “grrreat” in my head when i saw the pic! almost forgot about those sketches.

for those of you who haven’t seen it:

The Very Best of Jazz Club

xDD

[gentleclockdivider]

yeah the fast show , back in the goold old days when I had a television .
the gay landlord and his housekeeper , the fucking geezer …rofl
hilarious show

[esaruoho]

From: Why Buy?
Registered users get voting power at Renoise Backstage. You will decide which features we work on.

[insane (allie)]

I was wondering about that back when I was introduced to Renoise at 2.1, but then I forgot to mention it, followed by me completely forgetting about it until just now.

[martyfmelb]

I reckon it’s time for a new poll! What do you want now?

• More XRNI extensions (modular XRNI construction / soft keyzones / per-instrument and/or per-voice and/or per-sample DSP-chains with internal sends, etc.)
• Clip arranger / pattern as instrument / other macro-perspective composition tool
• Renoise as a VST plug-in (think of “we put a Renoise in yo Renoise, so u can track while u track”: this could actually supplant the first and second ideas to a great extent)
• Instrument library/manager with tagging (hopefully based on an internal database, file metadata, or better – both, with 2-way sync)
• Further modernised envelope editing (splines / different ramp-type per segment / inter-segment smoothing / larger envelope view)
• Detachable / dockable panels
• Piano roll
• Audio tracks / waveform graphical overlay
• Pitch shifter / time-stretcher
• DirectX plugin support (haha … I mean, respectfully, I don’t see the point)
• Your Idea Here

Just a proposal though! (Should I turn this into a proper forum poll, or am I hijacking what should be up to the devs to decide?)

[vvoois (vV)]

@esaruoho

I was looking at the “development cycle of version 1.8” Voting results today and was just wondering, how many of these have not been addressed by 2.7? There’s only 3 left, or something?

Yes the voting more or less seems overruled by the ideas and suggestions forum these days.
We look at what is most requested in these forums and more or less attempt to get some of these options into the next version.
Also adding/ implementing suggestions done during the Beta phase also seem pleasing enough for many.

[wahrk]

I’ve been checking that periodically since I bought 2.1 hoping they would start a new round of voting, but have been disappointed each time.

[thewitchkings]

renoise is a republic, not a democracy!

[Conner_Bw]

The real answer is that the voting script is tied to the rest of the Backstage. It’s sort of hardcoded if you will, and changing it has proven difficult because it affects the rest of the Backstage (downloads, accounts, upgrades, …)

It’s one of those things where if you could go in a time machine and do over, you would.

It’s on the TODO list, way at the bottom.

[rhowaldt]

@Conner_Bw

It’s on the TODO list, way at the bottom.

personally, i don’t really mind. as vV pointed out, it seems the ideas/suggestions forum has indeed taken over the role of the voting function, but i do not think it’s a bad development, seeing for example with 2.7b how many stuff from that forum has been implemented.

[vvoois (vV)]

@rhowaldt

personally, i don’t really mind. as vV pointed out, it seems the ideas/suggestions forum has indeed taken over the role of the voting function, but i do not think it’s a bad development, seeing for example with 2.7b how many stuff from that forum has been implemented.

I had a small argument about this with some guy a couple of years ago stating that the beta forums are open to everyone so the feature discussion is no longer exclusive to registered users.
It is true, however non-registered users still have no access to the Beta downloads so they don’t really have a solid base experience to join the discussion either.

[esaruoho]

Interesting…

https://forum.renoise.com/t/if-then-device/32575

From thread:
“The Highly Alpha version of the formula device. It is unofficially available under the hood but officially not supported and can cause crashes if not used properly.”

[vvoois (vV)]

@esaruoho

Interesting…

http://www.renoise.c…post__p__238442

From thread:
“The Highly Alpha version of the formula device. It is unofficially available under the hood but officially not supported and can cause crashes if not used properly.”

The device was already available since Renoise 2.6.
If you know which start-parameter to use, you can also script in 2.5 (be it that the API isn’t yet that advanced in 2.5)

[rictheobscene]

Giving Renoise the ability to be a Rewire client was the one item on that list I really wanted.

That has been implemented (quite nicely I might add), so I feel like I have been listened to.

[esaruoho]

OSX Mono Input Device bug to be fixed in a future update

@taktik

We are aware of this, don’t worry, and will try our best to support mono devices on OSX in the next updates. They will behave like doubled mono channels though, as they do on windows.

[2.7.2 thread](Renoise 2.7.2 - Maintenance Release & Update For Osx Lion view findpost p 244125)

@taktik

We can’t include this “fix” in a small maintenance update. This needs testing and thus a big beta. Sorry.

–
[Autofade=true/false missing from 2.7.2 API](Access To Autofade In Lua view findpost p 247472)

@taktik

Indeed it is. We’ll add this in the next update.

–
[Api Realtime Rendering Fails When Called From A Gui]([Fixed 2.8] Api Realtime Rendering Fails When Called From A Gui view findpost p 248904)

@taktik

Wow, what a crap. This indeed does not work when called from a dialog.
You can use this snippet as a workaround, until we’ve fixed the real problem

–
[b]Osx: Possible Crash On Save When Running Out Of Diskspace[b][/b][/b]

@taktik

Found the reason for this and fixed it for the next update. This could only happen on OSX, and only in very rare conditions. Nevertheless, it can, so it’s important to have that fixed.

–
[Stutter might be coming back](Stutter gopid 251081)

@taktik

Sorry guys. Totally forgot about the stutter. We obviously have put time into other stuff.
Only thing I can promise now is that we try to take care of this (and maybe other repeating alike FX) for the next Renoise updates. I don’t think we’ll manage to get that into 2.6.

@taktik

I’m sad to announce this, but this definately has to be done. (Stutter depreceated/removed)
The stutter has born as an experimental device that wasn’t meant as a repeater as most of you might think. So it is changed in form to allow its usage on most common case of a repeater, but has changed over time so much and it has turned into something in between a strange unmangeable experimental device and a broken repeater.

Also my latest changes and fixes (to allow a more robust usage after the perfect dblue report) have “mutilated” it so i’m no more happy of how it works and sound.
What we will do here is to restore the version present in beta7 and deprecate it so it will only available for song made during the beta stage (or for people who still wants to enable it from the song xml). I hope you will not kill me for this (the ones that love the device as it is), but we are forced to do this cause i realize that the device isn’t good as my other creations. We will try to avoid those kind of confusion in the future.

As an excuse for this, i will promise you that the 2.6 release will feature a perfect working SYNC REPEATER device (just as you like) and some other sample mangling devices (i cannot say more here) and these will rock as any other Renoise device out there, if not more

–

&also
https://forum.renoise.com/c/help-support-bugs/pending-bug-fixes

[esaruoho]

http://www.renoise.com/board/index.php?/topic/32166-fixed-quitting-renoise-with-lua-modifications-cancelloop/

@taktik

Sorry for the confusion. I had tested this with a version which already behaved differently. In 2.7, hitting cancel on the Mac, indeed just brings up the dialog again in this case. Fixed for the next update…

[xrns]

@rictheobscene

Giving Renoise the ability to be a Rewire client was the one item on that list I really wanted.

That has been implemented (quite nicely I might add), so I feel like I have been listened to.

yes, whoever thought that rewire would be a good idea to implement in renoise was a clever fellow

running renoise both as rewire master to reason and as slave to other daws, has really added lots of value for me

i’m not sure i’d be using renoise at all if it wasn’t for rewire

so, again, thanks a lot for rewire!

hope to see 64-bit rewire in the future… but other features like clips or loading multiple .xrns in one single renoise instance are much more important

[esaruoho]

[http://www.renoise.com/board/index.php?/topic/32376-fixed-osx-starting-renoise-with-wav-file-as-arg-does-not-load-it/page__p__254800#entry254800](http://www.renoise.com/board/index.php?/topic/32376-fixed-osx-starting-renoise-with-wav-file-as-arg-does-not-load-it/page p 254800#entry254800)

@vV

Don’t worry, you will be able to record your mono device in the next version.

this rumors that OSX / Linux Mono Device would be coming in a next version. Or the next version. One can never say for certain what that means, however.

Pending Bug-fixes also has a couple more [fixed] posts:
[Fixed] Osx: Starting Renoise With Wav File As Arg Does Not Load It
[Fixed] Osx: Changing Aggregate Device Inputs Can Cause A Crash
[Fixed] Quitting Renoise With .lua Modifications, Cancel=Loop

Lookin good, I guess