v4.731 - September 26 2014

[musicbynumbers]

+ OSX: updated signing for OSX 10.9.5+
+ Tab to transient: fixed MIDI transient inaccuracies [issueid=5310]
+ WAV reading: fixed incorrect reading of files with 125 or more bytes per sample-frame (e.g. 48+ channel 24 bit files)

[witti]

Thanks ! But what about this ?

http://forum.cockos.com/showthread.php?t=144835

http://forum.cockos.com/showthread.php?t=146573

http://forum.cockos.com/showthread.php?t=145316

http://forum.cockos.com/showthread.php?t=141650

All freshly added in the recent updates (starting from 4.62, i think...)

witti

[EvilDragon]

There's yet another bug in the MIDI editor. If there's no MIDI item loaded to MIDI editor, and Scale mode is enabled, the piano roll keyboard to the left isn't refreshed with new settings (for example changing the root note). One has to mouse over the piano roll to refresh the shaded display.

[Coachz]

Midi schmidi ! Arghhhhhhh

[Justin]

Originally Posted by Coachz

Midi schmidi ! Arghhhhhhh

Booo hooo important things getting fixed boo

[Coachz]

i would kiss that llama !

[ivansc]

Now settle down, you two boys!

[Coachz]

I have dreams of Reaper following Airons direction and ruling the world!

[planetnine]

Get on with that coding already then Coachz..!



>

[Coachz]

Is there a git repo? Can we contribute code to Reaper?

[Lawrence]

Originally Posted by Coachz

Is there a git repo?

gityerstinkinhandsoffmycode.com.

You bored C++ guys should go over and help Ardour. Our good friend Telenator ripped them a new one.

[ivansc]

Lawrence - there should SO be a real site t that fake address....

[Coachz]

I'm not a C++ guy, I do web apps in laravel but I"m so bored watching years of midi features dribble in when I really don't need midi features and virtually none of the feature requests I hoped Reaper would get, I would learn C++ to help out if possible. I'm really saddened by the pace of development but I have stated that many times in the past.

I think Airon does the best job of distilling what Reaper could be and you know sometimes it does require a rewrite. I have rewritten many projects from the ground up to add things that the architecture didn't support. Luckily I can make great music in Reaper but I just see how much more it could be and I watch years go by without any of those features ever happening. Oh well.

[EvilDragon]

It's not been just MIDI improvements, really, you can't say that.

Besides, "what Reaper could be according to a number of forum users" and "what developers want Reaper to be" aren't equivalent terms. You can only hope that at some point they will include some of the proposed features (some of which might not be very easy to do or do require a complete rewrite in some areas of code, which I'm not sure Cockos is really eager to do often). Same goes for MIDI folks, same goes for audio folks, same goes for automation folks, etc.

[Coachz]

I can't really think of any substantial new features or imporovements that I find useful that have come in the last 2 years though,. but your point is well taken.

Another thing I like about Reaper is we can have these discussions in a mature way. I do wish devs would engage conversations about feature requests. I really hate the silence.

[EvilDragon]

I'm thinking this silence pretty much implies that R5 alpha is impeding on us. Very likely before the end of this year. Just my assumption, though. It has been the same with R4 alpha, more or less...

[Coachz]

I mean in general. They never seem to engage feature discussions. Also, can you have an R5 without significant new features?

[ivansc]

Maybe they finally decided to implement a hybrid MIDI stave?

[Breeder]

Originally Posted by Coachz

Is there a git repo? Can we contribute code to Reaper?

https://github.com/Jeff0S/sws

Yes, I know you can't change everything through extensions, but I'm also sure that some of your needs could get implemented through extensions. So fork the repo and help us make SWS better

[Coachz]

um, yeah i'll pass until the actual code is available but thanks

[Breeder]

Originally Posted by Coachz

yeah i'll pass until the actual code is available

Coding for SWS is an excellent way to learn (indirectly) how some parts of REAPER work from the inside

[Coachz]

sorry it's just not for me.

[Argitoth]

--OFF TOPIC--
If you use a computer to do work, coding is for you. You just don't know it yet. (amazing quote from the Great Argitoth)
--OFF TOPIC--

[Coachz]

um yeah i code all day every day for my job in laravel, php, mysql, css, html, javascript, and jquery :-)

[morgon]

Originally Posted by Coachz

I can't really think of any substantial new features or imporovements that I find useful that have come in the last 2 years though,. but your point is well taken.

Another thing I like about Reaper is we can have these discussions in a mature way. I do wish devs would engage conversations about feature requests. I really hate the silence.

Coachz, your pov valid of course.

Lots of homestudio operators, pro or amateur use MIDI, I wouldn't be here typing this if it werent for functional MIDI. MIDI is easily manouverable, its light, it doesn't wear out strings, drumskins or wake the neighbors, it can play drums like a demon if a bit of creative effort made at it.

From my pov [and many others Id say] the main requirements of a DAW are good audio tracking and editing, track routing and freeze/render modes that sound same as unfreezed, vst[i] hosting, and MIDI.

Regions, stretch markers, media explorer ie synced loop audition and extra project tabs is also very useful often used functions.

So Id say Im typical of an instrumentalist who has a main inst they play, but prefer to program the others. I don't particularly enjoy programming MIDI, but its well worth the convenience of always able to improve/work on the track, even years later, when most of the physical conditions may have changed.

So from my pov and others with similar requirements, the main/right things are being done and done well, with stability one of the most important features.

Everything else is a bonus to users like me, its fun to explore useful time and effort saver things and add them to the toolbar, I've hardly scratched the surface there.

[Coachz]

Yeah, its all about finding the tool that matches your needs. I record live bands and as such have little use for midi but that's just me.

[Lawrence]

Originally Posted by EvilDragon

Besides, "what Reaper could be according to a number of forum users" and "what developers want Reaper to be" aren't equivalent terms.

Quoted for truth. That's the catalyst of probably 90% of daw forum user feature complaints everywhere, for every product, the disconnect between the creator's vision or intent, and what some users think it could or should be.

At the end of the day if the venture is successful and most users are happy, that equals "success".

[Coachz]

True. Now make me happy!

[Lawrence]

Originally Posted by EvilDragon

I'm thinking this silence pretty much implies that R5 alpha is impeding on us.

im·pede
verb

delay or prevent (someone or something) by obstructing them; hinder.
synonyms: hinder, obstruct, hamper, hold back/up, delay, interfere with, disrupt, retard, slow (down), hobble, cripple;

[/me being a complete douchebag]

[Argitoth]

I know were not supposed to have discussions in prerelease thread, but things have clearly gotten out of hand and I'm just going to add more fuel to this fire.

PLEASE do not remove PiP in REAPER 5!

Originally Posted by EvilDragon

Same goes for MIDI folks, same goes for audio folks, same goes for automation folks, etc.

I think every folk has a use for PiP and I'm starting to integrate it in my sample cutting and sample processing routine. The downfall of PiP will only be the lack of advertisement. If some REAPER gurus and composers make spank-tastic PiP videos, I'm sure people will be raving.

...damn, not getting audio from my PiP...

I'm trying to use pip to consolidate wav files for sample cutting rather than rendering/consolidating...oh but the files must be rendered anyway before they show up as audio in a PiP...that kinda defeats the purpose WHATEVER just don't kill the PiPs.

[musicbynumbers]

I know we shouldn't but I can't help but agree and say "please finish PIPs for reaper 5 devs" They are a "major league power" in sound design!

Originally Posted by Argitoth

I know were not supposed to have discussions in prerelease thread, but things have clearly gotten out of hand and I'm just going to add more fuel to this fire.

PLEASE do not remove PiP in REAPER 5!


I think every folk has a use for PiP and I'm starting to integrate it in my sample cutting and sample processing routine. The downfall of PiP will only be the lack of advertisement. If some REAPER gurus and composers make spank-tastic PiP videos, I'm sure people will be raving.

...damn, not getting audio from my PiP...

I'm trying to use pip to consolidate wav files for sample cutting rather than rendering/consolidating...oh but the files must be rendered anyway before they show up as audio in a PiP...that kinda defeats the purpose WHATEVER just don't kill the PiPs.