Old 08-04-2018, 12:35 AM   #1
xpander
Human being with feelings
 
xpander's Avatar
 
Join Date: Jun 2007
Location: Terra incognita
Posts: 7,670
Default v5.941 - August 4 2018

v5.941 : I mean, it's one banana Michael. How much could it cost? 10 dollars?

API: fix ReaLearn crash
API: support GetSetMediaTrackInfo(P_PROJECT)
MIDI hardware: allow saving project/other limited UI actions while waiting for a hung MIDI device


v5.94 - August 3 2018

+ Control surfaces: send active-sensing messages for HUI mode
+ FX: do not default to square envelope points on parameters that have a large number of steps defined [p=2016907]
+ FX: improve win32/mac plug-in filename parsing for projects saved on linux
+ Glue: do not re-open MIDI editors for items whose editors were hidden
+ JSFX: add rate control for spectrograph plug-in
+ JSFX: gfx_getchar(65536) returns special window information flags
+ Linux: add ALSA MIDI support, do not show MIDI-only devices in audio configuration
+ Linux: add system hidpi detection, can disable using ui_scale_auto=0 in reaper.ini, or override using ui_scale=
+ Linux: reuse existing REAPER instances when opening files from desktop environment (use -newinst command line parameter to override)
+ Linux: improve appearance, include libSwell.colortheme (copy to .config/REAPER/libSwell-user.colortheme to override)
+ Linux: rename main executable reaper (from reaper5)
+ Linux: fix control surface support
+ Linux: fix external editor support
+ Linux: fix file association icons
+ Linux: simplify desktop integration to only add a single item to applications list
+ MIDI devices: add retry button to audio/MIDI device error window
+ MIDI devices: warn when a previously-enabled device is not connected (you may see new warnings about MIDI devices from your past)
+ MIDI devices: show previously-connected devices in device list, allow forgetting those devices
+ MIDI devices: allow changing the device ID of input/output devices to enable I/O consistency between multiple computers
+ MIDI devices: rescan when opening MIDI device tab or resetting (may depend on specific driver/OS behavior)
+ ReaScript: fix validation of PCM_source parameters [p=2015950]
+ ReaScript: gfx.getchar(65536) or gfx_getchar(65536) return special window information flags
+ Video: add ffmpeg 4.0 support
+ Video: add Colorize preset
+ Video: gfx_procrect() can take mode=1 to apply Y values to U/V (colorization mode)


Generated by X-Raym's REAPER ChangeLog to BBCode

Last edited by xpander; 08-06-2018 at 12:44 AM. Reason: added 5.941 update
xpander is online now   Reply With Quote
Old 08-04-2018, 12:46 AM   #2
vitalker
Human being with feelings
 
vitalker's Avatar
 
Join Date: Dec 2012
Posts: 13,333
Default

Added name of 5.94.
https://forum.cockos.com/showpost.ph...7&postcount=60
Whole thread: https://forum.cockos.com/showthread.php?t=200010
vitalker is online now   Reply With Quote
Old 08-04-2018, 09:22 AM   #3
MEHRZAD-TUNGSTEN
Human being with feelings
 
Join Date: Jun 2015
Posts: 24
Default

please design a chord track such as cubase and s1
MEHRZAD-TUNGSTEN is offline   Reply With Quote
Old 08-04-2018, 12:11 PM   #4
Stevie
Human being with feelings
 
Stevie's Avatar
 
Join Date: Feb 2015
Location: Ukraine, Russia
Posts: 255
Default

what's going on
Stevie is offline   Reply With Quote
Old 08-06-2018, 01:06 AM   #5
xpander
Human being with feelings
 
xpander's Avatar
 
Join Date: Jun 2007
Location: Terra incognita
Posts: 7,670
Default

Sorry Stevie, I checked two pages deep before creating this post, but it seems I still managed to miss your topic about the new version. I updated this one to the latest version changes, but mods could of course sticky yours instead...
xpander is online now   Reply With Quote
Old 08-06-2018, 10:01 AM   #6
jgnelson
Human being with feelings
 
Join Date: Feb 2014
Posts: 74
Default

just downloaded the newest version, and it is back to opening the properties files every time I try to drag a wav anywhere. so I went back to the previous version, and it is ok. I will stick with it..
jgnelson is offline   Reply With Quote
Old 08-06-2018, 10:41 AM   #7
Plarnuvius
Human being with feelings
 
Plarnuvius's Avatar
 
Join Date: Sep 2017
Posts: 76
Default

Just loaded v.941
Not only getting no sound out from the new version, but even older versions have now ceased sending sound out
got this on boot up

The following MIDI inputs could not be opened:
AKAI drum pad
Roland - UM-ONE
The following MIDI outputs could not be opened:
AKAI drum pad

NOTE: I reloaded 5.93, restarted computer , and everything seems OK
__________________
Technology drives me crazy. Making music keeps me sane.
https://www.youtube.com/channel/UC1_...yiTS0hVF4kgG4Q
https://avenueg1.podomatic.com/

Last edited by Plarnuvius; 08-06-2018 at 11:34 AM. Reason: follow-up
Plarnuvius is offline   Reply With Quote
Old 08-06-2018, 02:24 PM   #8
Stevie
Human being with feelings
 
Stevie's Avatar
 
Join Date: Feb 2015
Location: Ukraine, Russia
Posts: 255
Default

Quote:
Originally Posted by xpander View Post
Sorry Stevie, I checked two pages deep before creating this post, but it seems I still managed to miss your topic about the new version. I updated this one to the latest version changes, but mods could of course sticky yours instead...
it's okay
Stevie is offline   Reply With Quote
Old 08-06-2018, 11:12 PM   #9
woogish
Human being with feelings
 
Join Date: Feb 2011
Posts: 693
Default

oh, brother.....................................missed that one!!!!




GDT, WTLA
woogish is offline   Reply With Quote
Old 08-07-2018, 10:26 AM   #10
Jaybee
Human being with feelings
 
Join Date: Aug 2015
Posts: 39
Default

Since 5.941 I'm getting this error warning when my current keyboard controller is turned off. Sometimes I don't need the keyboard booted up for what I want to do in Reaper (e.g. mix) so it's annoying that this nag screen keeps appearing every time I click anywhere.

How can I set Reaper so it knows it's a current device, but just not "on" at the moment?

If I disable the keyboard in MIDI devices to stop the nag screen then it's not recognised when I actually turn it on.

Catch 22. This is not very clear at all.

TIA
Jaybee is offline   Reply With Quote
Old 08-07-2018, 01:09 PM   #11
dijon
Human being with feelings
 
dijon's Avatar
 
Join Date: Mar 2007
Location: Brooklyn, NYC
Posts: 346
Default midi inputs could not be opened

I also got a 'midi inputs could not be opened' error which I couldn't fix. Went back to 5.93 (win64) and all is good again.
dijon is offline   Reply With Quote
Old 08-07-2018, 02:12 PM   #12
vitalker
Human being with feelings
 
vitalker's Avatar
 
Join Date: Dec 2012
Posts: 13,333
Default

@Jaybee, @dijon
https://forum.cockos.com/showthread.php?t=209673
Does this help?
vitalker is online now   Reply With Quote
Old 08-07-2018, 02:18 PM   #13
Jaybee
Human being with feelings
 
Join Date: Aug 2015
Posts: 39
Default

Hi

Not really. I've forgotten the previous midi items fine. I don't want it to forget my current keyboard but when said keyboard is turned off I get the nag screen.

So I have to have the keyboard on all the time (whether being used or not) so the nag screen doesn't appear.

Surely that's not how this is supposed to work?
Jaybee is offline   Reply With Quote
Old 08-08-2018, 08:55 AM   #14
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by Jaybee View Post
Hi

Not really. I've forgotten the previous midi items fine. I don't want it to forget my current keyboard but when said keyboard is turned off I get the nag screen.

So I have to have the keyboard on all the time (whether being used or not) so the nag screen doesn't appear.

Surely that's not how this is supposed to work?
Just turn off MIDI device opening warnings then
Justin is offline   Reply With Quote
Old 08-08-2018, 08:59 AM   #15
Jaybee
Human being with feelings
 
Join Date: Aug 2015
Posts: 39
Default

Quote:
Originally Posted by Justin View Post
Just turn off MIDI device opening warnings then
Will do...
Jaybee is offline   Reply With Quote
Old 08-08-2018, 09:24 AM   #16
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Given this feedback we will add a separate option to disable warnings of non-present devices while retaining warnings of devices that could not be opened...
Justin is offline   Reply With Quote
Old 08-08-2018, 12:51 PM   #17
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,688
Default

Great !
-Michael
mschnell is online now   Reply With Quote
Old 08-11-2018, 01:08 AM   #18
flusheddata
Human being with feelings
 
flusheddata's Avatar
 
Join Date: Mar 2013
Location: Leon, Spain
Posts: 56
Default

Quote:
Originally Posted by Justin View Post
Given this feedback we will add a separate option to disable warnings of non-present devices while retaining warnings of devices that could not be opened...
Please add it to the Midi devices section. I think it makes more sense than in Audio.
Cheers,
Miguel
__________________
There are 10 types of people.
Those who understand binary and those who do not
flusheddata is offline   Reply With Quote
Old 08-12-2018, 07:36 AM   #19
jeffypop
Human being with feelings
 
Join Date: Aug 2018
Posts: 1
Default v5.491 will not install

I've tried since Aug 5th to install v5.491, without any success. The error message I keep getting seems to indicates there may be a problem with the folder's location. But, it's the exact same folder, and location I've easily installed every other update. I see a couple of users are having issues in their own right with the latest version, and then have just gone back to the previous installment. Given this bit of information, can I just leave well enough alone, and continue with v5.93, ignoring the update prompt when I open a project? Thanks -jB
jeffypop is offline   Reply With Quote
Old 08-14-2018, 09:31 AM   #20
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 217
Default

Quote:
Originally Posted by Justin View Post
Given this feedback we will add a separate option to disable warnings of non-present devices while retaining warnings of devices that could not be opened...
Really nice to see you responding to our issues Justin.
Again I am so happy I moved to Reaper. I hope all is well with you,
I know there a lot going on these day in the world.
__________________
My Music
https://soundcloud.com/midiman007
midiman007 is offline   Reply With Quote
Old 09-01-2018, 09:49 PM   #21
jesussaddle
Human being with feelings
 
Join Date: Oct 2009
Posts: 192
Default

Indeed, I have also gotten a 'midi inputs could not be opened' error which I couldn't fix. Went back to 5.93 (win64) as well and the midi inputs are back.

It seems there are not too many of us.

I use a Kork microkey and a Novation Impulse, and a few other things, one being a Fractal Audio MIDI Port, and an RME MIDI Port. Any chance someone has an update on the issue? I usually always update without any issues. This is the first issue I can recall having in years.

(UPDATE - a few days later - I find it odd that no one else is having a similar error, or that there is no discussion on how to correct this.............................................. .................................................. .................................................. .................................................. ......................

I would like to see a line on new releases as to whether this is addressed (addressed 'opening program gives error MIDI Outputs could not be opened', as I will need to stop updating for now o_o

Last edited by jesussaddle; 09-06-2018 at 03:53 PM.
jesussaddle is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:56 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.