v4.7pre13 - July 6 2014

[gofer]

v4.7pre13 - July 6 2014
+ Fixed 'Link preset to MIDI program change' menu items shortcuts [issueid=4910]
# Fixed track color perfs refresh issues [p=1374635]
+ Audio Units: use new Audio Unit API for increased compatibility on 10.6 and newer
# OSX: faster retina display updating (SSE optimized)

[xpander]

Portable x64 install crashes when trying to open projects with mp4 files. This both with fresh install and with configuration imported from the regular v4.62 (x64) install. Same thing with pre12, haven't checked further back.

Faulting module seems to be the K-Lite Codec Pack, but I wonder why that doesn't crash my regular 4.62 (x64) nor the latest x32 portable installs.

OS Win 8.1.

Log Name: Application
Source: Application Error
Date: 6.7.2014 18:21:08
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xxx
Description:
Faulting application name: reaper.exe, version: 4.6.9.23, time stamp: 0x53b95f2e
Faulting module name: ffdshow.ax, version: 1.3.4529.0, time stamp: 0x52f3be86
Exception code: 0xc0000005
Fault offset: 0x000000000018179d
Faulting process ID: 0x1a40
Faulting application start time: 0x01cf992de348a9b0
Faulting application path: G:\Reaper test\reaper.exe
Faulting module path: C:\Program Files (x86)\K-Lite Codec Pack\Filters\ffdshow64\ffdshow.ax
Report ID: 26f4497d-0521-11e4-8285-001e101f214d
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-06T15:21:08.000000000Z" />
<EventRecordID>15794</EventRecordID>
<Channel>Application</Channel>
<Computer>xxx</Computer>
<Security />
</System>
<EventData>
<Data>reaper.exe</Data>
<Data>4.6.9.23</Data>
<Data>53b95f2e</Data>
<Data>ffdshow.ax</Data>
<Data>1.3.4529.0</Data>
<Data>52f3be86</Data>
<Data>c0000005</Data>
<Data>000000000018179d</Data>
<Data>1a40</Data>
<Data>01cf992de348a9b0</Data>
<Data>G:\Reaper test\reaper.exe</Data>
<Data>C:\Program Files (x86)\K-Lite Codec Pack\Filters\ffdshow64\ffdshow.ax</Data>
<Data>26f4497d-0521-11e4-8285-001e101f214d</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[Justin]

Your regular non-portable install probably has an FFmpeg installed that supports the m4a, avoiding the other codec.

[xpander]

Ok, thanks. I was trying to figure out from where I could tell to the portable install to use the same codec as the non-portable version. Importing the full configuration from the non-portable doesn't seem to make that happen and I haven't found any ini which would have paths pointing to that K-lite codec either. I'll remove that codec and see what happens.

---
edit: Removed the K-Lite Codec pack 10.3. Now I can load mp4 projects to the portable x64 install without crash, but they won't play...apparently since the codec is missing. The regular x64 version still plays them fine, but exporting that config to the portable install doesn't make any difference. This would mean that exporting/importing configs won't grab the codec settings for the portable x64? However, this still works in portable x32 install.

---

Item source properties from the regular x64 install:

Using FFmpeg DLL decoder v54.42.100
Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 652 kb/s
Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, s16, 125 kb/s

Loaded from: C:\Program Files\REAPER (x64)\avcodec-54.dll

Same project/item with portable x32, no codec path stated there but works:

Length: 1:14:46.605
Video: 240x320@1.#Jfps, Aspect=1.00, Decoding format=
Audio: 44100Hz 2ch 16bps
Using DirectShow decoder

And the source properties from the portable x64:

Invalid file

This while the root and Plugins directories of this portable install have the same codec(s) as mentioned with the regular x64 install above?

Same with v4.62 already, not a new thing so I'll stop polluting the thread with this.

[airon]

This might be a good time to recommend FFMPEG library packages, since they can travel with a portable Reaper installation. I haven't kept up because I'm primarily using VLC for playback these days and only keep a 64-bit FFMPEG library package installed in the Reaper directory for occasional WEBM encodings.

My 64-bit FFMPEG package is libav-win64-20130209.7z . Perhaps others can chip in with working 32-bit FFMPEG library versions.

-edit-
Did a quick test. Here's a reliable FFMPEG version for portable 32-bit installs.

http://ffmpeg.zeranoe.com/builds/win...in32-shared.7z

Works for the current pre. Copy the DLLs from the "ffmpeg-1.2-win32-shared.7z\ffmpeg-1.2-win32-shared\bin" directory in to the Reaper directory, alongside the Reaper.exe. You should be in business.

Versions above 1.2 do not seem to work(2.x and up). Not tested any new LibAV builds or looked at Aegiscorp builds yet.

Apart from that, at least install VLC(non-portable) 64-bit on your system, if you use Reapers 64-bit version most of the time.

Perhaps you can install VLC 64-bit and VLC 32-bit side by side, but I haven't tested that yet. Worth a try though, because Codec packages don't seem to be quite the ticket.

-edit-
That doesn't fucking work and it's likely to be VLC's fault, as hardly anyone needs to install and use both versions I presume. The 32-bit portable install doesn't see the other installed 32-bit VLC. Maybe it'll work for you.

VLC has been working reliably for a lot of people and is very easy to aquire and install. And most folks who own other machines probably know it as a reliable media player anyway. Remember to use normal installers, not the portable versions.

[musicbynumbers]

VLC works for me here too apart from not being able to preview videos that don't have audio in the media player.

[xpander]

Originally Posted by airon

Apart from that, at least install VLC(non-portable) 64-bit on your system, if you use Reapers 64-bit version most of the time.

That did it, thanks airon. First time I was running also Reaper 64-bit portable and the FFMPEG library I have and works with the regular x64 install not working with the portable x64 surprised me.

[DarkStar]

Originally Posted by gofer

v4.7pre13 - July 6 2014
+ Fixed 'Link preset to MIDI program change' menu items shortcuts [issueid=4910]
# Fixed track color perfs refresh issues [p=1374635]

Woo hoo - 2 of mine - I'm curious, what was the cause of that first one? Pic is over here: http://forum.cockos.com/project.php?issueid=4910

Also, I've just see this folder

C:\Users\DarkStar\AppData\Roaming\REAPER\UserPlugi ns

it's empty - any idea what it's for?

[Jeffos]

Originally Posted by DarkStar

Also, I've just see this folder

C:\Users\DarkStar\AppData\Roaming\REAPER\UserPlugi ns

it's empty - any idea what it's for?

<REAPER_resources_dir>/UserPlugins is where you would install an extension plugin (like SWS) so that it'd be shared by different (& non-portable) versions of REAPER, unlike <REAPER_install_dir>/Plugins.
This is primarily meant for OS X, that's why this folder is empty on Win but it should work there too...

[plush2]

Are there any plans for optimizations on the windows side for high resolution displays (>200 ppi)?

[musicbynumbers]

Originally Posted by plush2

Are there any plans for optimizations on the windows side for high resolution displays (>200 ppi)?

That would good to know as I'm thinking of a surface pro 3.

Although might fine on it so probably good.

we do have the scale option but that might be too heavy handed

[Garrick]

Not sure if this is a pre prob but I noticed it at pre 10



In the first example, painting midi notes has unexpected behaviour after tempo mapping with SWS/BR Convert project markers to tempo markers

the second example has the expected behavior after tempo mapping with sws/br move closest grid line to edit cursor.

[vidalsh]

could comeback the external MIDI editor in those beta versions someday?

[airon]

How long is whatever this pre-stuff is going to take ?

I'm already scratching and it ain't getting better.