v5.71pre16a - January 29 2018

[Jack Winter]

Originally Posted by EvilDragon

Some, but not all, and not every time.

If only it was that simple! Then I'd practice too

[deeb]

Originally Posted by Jack Winter

If only it was that simple! Then I'd practice too

you can do it! just say anything ...

[juliansader]

Originally Posted by Robert Johnson III

Thing is…. People might start switching DAW’s for bugs like these (no work around) and they might not return…

Indeed. I bought Studio One Professional a few days ago.

[LugNut]

Hi,
I must say that this set of pres is the first time I can't use them from the crashing.
Never had this unreliability before in any pre.

If all this is for ara support I vote..the hell with it:-)

With every new pre now I DL it, portable install, load my test project...it loads..i check and see if the new midi items still look a mess...second time I hit play/stop...poof.
Then I load 5.70 and work.

[schwa]

Originally Posted by LugNut

Hi,
I must say that this set of pres is the first time I can't use them from the crashing.

It would be helpful for us to have a little more information...

[EvilDragon]

Originally Posted by juliansader

Indeed. I bought Studio One Professional a few days ago.

Let us know how responsive Presonus is about fixing its bugs

[LugNut]

Originally Posted by schwa

It would be helpful for us to have a little more information...

Hi,

I understand, but it seems people with more time and skills are having same issues. For ex, it takes me hrs to capture and scale down screenies. Its me.

Also I'm on xp sp3 and I figure some will just say...its just your system..get with the program.

Sorry if my comment was unhelpful, but I had to get it off my chest.
And thank you for your response schwa...one doesn't see that anywhere else..so thank you devs for your tireless work!

[EvilDragon]

Post crashlogs? They are often much more useful than screencaps.

[nofish]

[OT]

Originally Posted by juliansader

Indeed. I bought Studio One Professional a few days ago.

Would be a loss if you leave as I see you as a driving force regarding MIDI issues (e.g. the 'Bestiary' thread).

Just wanted to take the chance to say thanks.
Sorry for OT.

[_Stevie_]

I second that Julian!

[dupont]

Originally Posted by EvilDragon

I don't think Cockos is concerned about people switching DAWs (because they aren't market-driven), so you can't use that as a leverage to get your pet peeve bug fixed. You can certainly try, though, but don't be surprised if it doesn't work.

Also, you make it say as if other DAWs don't have no workaround bugs. They sure do.

I was on Studio one a few days ago and it poof crashes to desktop several times, so back to Reaper !

[deeb]

regarding the regions bug isn't it related with "range/area selection" feature?

maybe they should be thought together when/if that time arrives

[EvilDragon]

Regions have nothing to do with area selection, man.

[deeb]

Originally Posted by EvilDragon

Regions have nothing to do with area selection, man.

the way i see: area/range selection is == region selection with Y in mind

so if range selection is done region selection is also done in terms of copy, move, duplicate and delete areas/sections/regions.

[Tod]

Originally Posted by _Stevie_

I second that Julian!

I 3rd that Julian!

[EvilDragon]

Originally Posted by deeb

the way i see: area/range selection is == region selection with Y in mind

so if range selection is done region selection is also done in terms of copy, move, duplicate and delete areas/sections/regions.

Regions in Reaper are not selections, they are sections of the project - like a 2D marker. You can make a time selection that's as long as a region, but that's not a "region selection", it's still a time selection.

[LugNut]

Hi,
I have some new info.
If I uncheck flush fx on stop in playback preferences it doesn't crash on play.
Funny I cannot change the ms adjustment for that preference. It stays at 4000.
Also the crashing vstis have the new hard reset button unchecked.

I don't have any stuck notes, but delays and reverbs continue on stop.

The crash logs from before I unchecked flush would point to the first vsti in song. Say first call horns... I would then load the song with the offending vsti deleted. Then it would crash with next vsti say b4.

This song gives me no problem in 5.70.

Thanks

[lalelu]

Originally Posted by EvilDragon

Boy, then there's an awful lot of buggy plugins out there, hmm...

Indeed, all we can do is make the plug-in developers aware of the issue. For example, I was the one who contacted Sean Costello of ValhallaDSP over at the KVR forums about it long time ago.

[deeb]

Originally Posted by EvilDragon

Regions in Reaper are not selections, they are sections of the project - like a 2D marker.

so the range selection is like 3D selection.

in the background Region operations use a time selection, in terms of moving, deleting, duplicate kind of operations, both are very much the same but range selection has parcels of Y Axis in mind, so in this regard more flexible.

[dupont]

Originally Posted by lalelu

Indeed, all we can do is make the plug-in developers aware of the issue. For example, I was the one who contacted Sean Costello of ValhallaDSP over at the KVR forums about it long time ago.

I contacted the U-he compagny about the stuck note with Tyrell N6 several weeks ago...No reply.

[Allspice]

Oli from VirtualCZ said he'll work on it in the next version. I linked him this thread for reference.

[Arthur]

Originally Posted by Robert Johnson III

Thing is…. People might start switching DAW’s for bugs like these (no work around) and they might not return… (Kudos for the improvements already made in this area though)

Bug exists today, tomorrow will not exist, but the program will remain,
and it's an awesome DAW. Thanks COCKOS !!!

[ivansc]

Originally Posted by juliansader

Indeed. I bought Studio One Professional a few days ago.

(grin) really? I mean, REALLY???

I dumped out after persevering through versions up to and including 2.6.3... cpu hog plus it felt like I was being forced to work how the software wanted all the time.
You are more resourceful and better clued in on programming, scripting than I am so I will be VERY interested to see how you make out with it.

[krahosk]

Originally Posted by ivansc

(grin) really? I mean, REALLY???

I dumped out after persevering through versions up to and including 2.6.3... cpu hog plus it felt like I was being forced to work how the software wanted all the time.
You are more resourceful and better clued in on programming, scripting than I am so I will be VERY interested to see how you make out with it.

Bought Studio One 3 too but not out of spite. But went back to Reaper because it's better.

[Gianfini]

Originally Posted by EvilDragon

I don't think Cockos is concerned about people switching DAWs (because they aren't market-driven),

WOW... I'm seriously scared now. "Not being market driven" often means no growth plans, no willingness to ensure continuity and extend the core team capable to keep the product alive, and high risk to just get bored and stop the whole game all of a sudden...

I'm sure this will not be the case for Cockos!

But not being market driven is not necessarily good

(just my two cents since the thread has gone nuts already)

[vanhaze]

Originally Posted by EvilDragon

Regions have nothing to do with area selection, man.

No, that's correct ED, but these native features (the first one as an Option) would be very welcome i think, making a direct relationship between Region and Area Selection:

a) When creating a Region, automatically the whole arrange area that "falls" in that Region is selected, including envelopes and Automation Items.

b) Mouse Modifier for Context: Project Region - Left mouseclick.
Then you can have for instance: left mouseclick on Region defaults to selecting whole arrange area within Region.

[EvilDragon]

Originally Posted by Gianfini

WOW... I'm seriously scared now. "Not being market driven" often means no growth plans, no willingness to ensure continuity and extend the core team capable to keep the product alive, and high risk to just get bored and stop the whole game all of a sudden...

I'm sure this will not be the case for Cockos!

But not being market driven is not necessarily good

Yes, Cockos has no growth plans, which shows in them being just two developers now. However since Justin is working on Reaper because he WANTS to use it, I'd say chances of getting bored are pretty slim.

Why would they need to be market-driven when Justin already has all the money one could possibly want (to the point of him being openly embarrased about it)?

[mccrabney]

hello noise, i'm signal

so i posted this the other day in Bug Reports, but it belongs here because it's new as of this pre cycle



i've isolated the issue to REAPER by backtesting the pres to 5.70, which doesn't change bidule's routing

this makes me nervous because my bidule routings are deeply embedded on several tracks and it was difficult to track down what was happening to prevent my [insert function] from working. if this were to happen somewhere in a larger, more complex bidule and then get saved over itself, repairing it would potentially take a great deal of reverse engineering

repro
1- open project
2- examine bidule routing
3- save project to new name
4- open the newly saved project
5- notice missing bidule links

[EvilDragon]

Originally Posted by mccrabney

hello noise, i'm signal

Brilliant!

[schwa]

Originally Posted by mccrabney

hello noise, i'm signal

Thank you.

I'm not super familiar with Bidule. This problem is likely related to multichannel routing, and I don't know how to set up multiple channels in Bidule.

Is it easy for you to save a very simple project with Bidule that demonstrates the problem, and attach it or email to support at cockos, so we can reproduce the error?

[mccrabney]

sent. thanks. in Bidule, the white cables are midi and the blue ones are audio.

I'm not super familiar with Bidule

it lets me do things with midi that i couldn't do unless i was a better programmer.

[deeb]

Originally Posted by mccrabney

it lets me do things with midi that i couldn't do unless i was a better programmer.

sorry because out of topic: What kind of things ? some practical example?

[ferropop]

Originally Posted by EvilDragon

Regions have nothing to do with area selection, man.

Area duplication is just "selective" region duplication, they're absolutely related.

[EvilDragon]

Implementation-wise they're unrelated.

[ferropop]

In Excel, whether you highlight an entire column or just the first 3 cells in a column, I'm pretty sure the code running "behind the scenes" is the same, or rather just a subset.

[EvilDragon]

But regions in Reaper are primarily not selection devices, they are first and foremost delimiting devices. Sure you can create a time selection by double-clicking on them, but this is not their primary function.

[deeb]

Originally Posted by EvilDragon

Implementation-wise they're unrelated.

If area selection is implemented. All functions related to copy, duplicate , move are equal.

[EvilDragon]

OK you guys obviously don't understand what I'm saying. Nevermind.

[ferropop]

EvilDragon, if you Ctrl-Drag a region you get Horizontal Area Duplication essentially. Proper area selection would leverage a subset of that same Region code.

[dasdeck]

The latests Landoleet version crashes my Peng plugin as soon as I'm using multiple outputs.
It seems to crash inside the juce wrapper code, but i did not come around to debug it yet.

very likely candidate is this one:

v5.71pre10 - January 9 2018
...
# VST: fix VST3 output issues [p=1937585]

I can test possible fixes.

Cheers!