>> v4.0alphax.x bugs >> here please <<

[hopi]

Originally Posted by Fabian

Hmm... I have mouse click on item different for lower and upper half. Maybe that's it?

don't know... is it OK if you change that setting?

[hopi]

Nice catch bblue

[gofer]

Originally Posted by bblue

The colors of selected and unselected docker tabs, which have settings in the Theme Editor, are not being set at all.

They are currently static with a white selected and cyan gray (aka pea green) unselected tab.

--Bill

That's probably because the theme in question has images for docker tabs. These will override Theme Editor colors (or do they? Maybe it's possible to let those colors shine through in transparent areas of the pngs, dunno). It's the usual behavior for some of the colors in the theme editor list.

EDIT, just tried. Removing the images tab***.png, as well as unchecking "Theme uses image resources" both makes the colors visible. All's well .

[AdamWathan]

There's still a bug with toolbar buttons. I can't reuse some default toolbar icons, they always show up as text. For example I am trying to move the "autocrossfade toggle" button to the floating toolbar and delete it from the main toolbar, but if I try to reuse the icon it just shows up as text:

http://www.adamwathan.com/reaper/r4toolbarbug2.swf

[bblue]

Originally Posted by gofer

That's probably because the theme in question has images for docker tabs. These will override Theme Editor colors (or do they? Maybe it's possible to let those colors shine through in transparent areas of the pngs, dunno). It's the usual behavior for some of the colors in the theme editor list.

EDIT, just tried. Removing the images tab***.png, as well as unchecking "Theme uses image resources" both makes the colors visible. All's well .

Why would you need to uncheck 'Theme uses images resources'? That would negate other images as well, wouldn't it?

I just removed the four tab* files from the theme directory and the docker tabs now color according to the theme editor. How did I miss that?

Problem now is what you define in the editor are flat colors. If you want them shaded or with some other visual character you need the tab* files colored accordingly. Easy enough to fix now!

Thanks Gofer!

--Bill

[bblue]

I'll try to redeem myself for the space wasted on docker tabs. Back to automation for this late breaking story.

1. You have an audio track with one FX. I don't think it matters which one (or how many), and you have extended one or more of its controls to appear in the TCP. That all works fine.

2. Now you arm a volume or pan envelope on that track. It can actually be any envelope, except one for the plugin. Set it to something color visible like touch/latch, write or read.

3. Note that any envelope armed and visible in step #2 will cause the fader or pan (whatever you armed) visual to color itself according to the mode. This is fine.

4. But it ALSO sets the text color of all the FX controls in the TCP, even though they are not the subject of arming.

I don't believe that any FX control should show armed text coloring unless it is specifically armed by definition.

--Bill

[AdamWathan]

Originally Posted by AdamWathan

There's still a bug with toolbar buttons. I can't reuse some default toolbar icons, they always show up as text. For example I am trying to move the "autocrossfade toggle" button to the floating toolbar and delete it from the main toolbar, but if I try to reuse the icon it just shows up as text:

http://www.adamwathan.com/reaper/r4toolbarbug2.swf

Anyone care to confirm? I originally reported this on December 2/2010...

http://forum.cockos.com/showpost.php...2&postcount=95

I can reuse the icons but only if I'm not reusing them for the actual action.

IE. I can use the metronome icon to toggle autocrossfades but I can't use the metronome icon to toggle the metronome. I can use the autocrossfade icon to toggle item grouping but I can't use it to toggle autocrossfades. Even cutting and pasting those entries within Reaper from the main toolbar to a floating toolbar doesn't preserve the icon, it's always text even when I explicitly change it to the proper icon.

This effectively means you cannot take any button that has 2 PNG states and move it to a floating toolbar, since it is hardcoded in Reaper for specific actions to work with the 2 (or 3 with ripple editing) PNGs in the toolbar icons folder.

This works fine in V3, please fix!

[AdamWathan]

Still having this bug with slip editing not tracking to the mouse cursor properly as well:

http://www.adamwathan.com/reaper/r4slipmousebug.swf

Originally reported here:

http://forum.cockos.com/showpost.php...postcount=1256

And here's a static screenshot that means nothing because I don't have LICECap for OSX, but at least will make the post stand out and attract attention

[gofer]

Originally Posted by bblue

Why would you need to uncheck 'Theme uses images resources'? That would negate other images as well, wouldn't it?

Of course. I did it only to find out whether the theme editor colors work when it doesn't use the images. Wasn't meant as a workaround but to report that there is nothing wrong.

[rhythminmind]

When normalizing a floating point file that has peaks over 0dbfs, Reap won't bring the gain down correctly. You still get overs.

[airon]

The custom action editor has the names of actions cut off, unlike the actions window.

Alpha 39

[likenokevin]

I am getting this same crash in alpha 39 and the work around in this thread does not seem to help.

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

[llanafreak44]

Over 9000 empty items. When I start recording a new take on a track where there is already something recorded, regardless of where I start recording, it makes the other already recorded item into a first take, with the empty item as the most recent take. Really messes up the work flow when I have to go back, explode tracks, click 'em all to delete.


EDIT: As I'm slip editing, if the Empty item is behind the track, every time I split, the empty items come forward, forcing me to delete every slip. GAH

[chriscomfort]

I'm getting wrong behavior for setting Timebase for a recorded MIDI item. I've set Timebase to "Time" in the Project Settings, Item Properties and Track Properties by right-clicking in the TCP and yet my MIDI part still time compresses when I increase the tempo from 120 to 140. I can't even change the playback rate in the Item Properties cause that number always says 1.000000. The length stays the same cause extra blank space is added to the end. I don't get it.

XP SP3, V4.0 Alpha 39, SWS Extensions 2.0.0 Build #10, Full clean install (not porbable). I'd renamed my old Program Files folder and DocsSettings/Admin, etc, etc before install so that the folders would be totally clean and fresh.

[chriscomfort]

Some of my preferences: Load template project when starting up and not loading last project, No backups
are being ignored. Everything was fine when I was running a portable install, but as soon as I did a full install, these things are being ignored.

Originally Posted by chriscomfort

XP SP3, V4.0 Alpha 39, SWS Extensions 2.0.0 Build #10, Full clean install (not porbable). I'd renamed my old Program Files folder and DocsSettings/Admin, etc, etc before install so that the folders would be totally clean and fresh.

[lawrs]

Urgent help needed guys..

I have a session later on, and I'll be using a temp studio, they are running on Mac OSX. I need to import video for the session. I'm running a test on my MacBook Pro now, and after installing the FFmpeg.dylib into "UserPlugins" , it still doesn't show up, and videos are still being decoded via Quicktime Decoder. Please suggest anything if you've encountered this. Thanks. Running v4 a38

[qwanta]

When I try to rotate knobs or move sliders with the mouse on some older plugins, I am only allowed to move to the max or min position, nothing in between. This happens with Ohmboyz delay and GForce Oddity. Presets load fine, and in Oddity I can manually type in slider values OK.

This doesn't happen in 3.75, not sure about older alphas as this may have been the 1st time I used these plugins in v4 (alpha 39).

[Guido]

Originally Posted by chriscomfort

I'm getting wrong behavior for setting Timebase for a recorded MIDI item. I've set Timebase to "Time" in the Project Settings, Item Properties and Track Properties by right-clicking in the TCP and yet my MIDI part still time compresses when I increase the tempo from 120 to 140. I can't even change the playback rate in the Item Properties cause that number always says 1.000000. The length stays the same cause extra blank space is added to the end. I don't get it.

Hi,
Confirmed.
This is the way ive always seen the midi item's behavior to be. Since b4 V3.. As a matter of fact the only way i know how to make the midi item play at its current rate,while changing Reapers tempo, is to go into EVERY midi item's properties and set the item to "ignore project tempo." a real PITA when ur trying tempo map a song that wasn't recorded to a click! Try it!And if u split that midi item, the positions of notes goes crazy. I never posted bout it because there seems to be bigger midi fish to fry...hung midi notes on ext midi gear when any track is solo'ed anyone?...just thought no body else would care.^^

Guido

[hopi]

Originally Posted by lawrs

Urgent help needed guys..

I have a session later on, and I'll be using a temp studio, they are running on Mac OSX. I need to import video for the session. I'm running a test on my MacBook Pro now, and after installing the FFmpeg.dylib into "UserPlugins" , it still doesn't show up, and videos are still being decoded via Quicktime Decoder. Please suggest anything if you've encountered this. Thanks. Running v4 a38

don't have a mac nearby to check... but don't think that is the correct location on a mac for the lib. Sorry I can't help more than that atm.

[Lawrence]

Got the BSOD during a mix. Don't know where the dump file will be so if someone can point me to it I'll post it here. Thanks.

[Dstruct]

Originally Posted by Dstruct

4.0alpha22

-> insert item
-> rightclick on it to open context menu

Result: "Move item" mouse cursor shown in the menu too. Very confusing.

Expected: Normal arrow mouse cursor shown in context menu navigation

Fixed in 4.0alpha40 but not completely:

-> insert item
-> hover mouse over left or right edge so that the resize cursor is shown
-> rightclick to open context menu


Result: "Resize" mouse cursor shown in the menu too.

Expected: Normal arrow mouse cursor shown in context menu.

[PitchSlap]

For some reason in alpha 40 I can no longer drag VST(i)'s from the FX Browser to the TCP or MCP. I can only add FX by double-clicking. Once they are on a track I can still drag to copy though.

[Dstruct]

Originally Posted by PitchSlap

For some reason in alpha 40 I can no longer drag VST(i)'s from the FX Browser to the TCP or MCP. I can only add FX by double-clicking. Once they are on a track I can still drag to copy though.

Confirmed.

FIXED (4.0alpha40a)

[inspired]

present in alpha40

maximum number of lanes option does not seem to store changes...
everytime i start reaper it is set to 1

[lawrs]

Originally Posted by hopi

don't have a mac nearby to check... but don't think that is the correct location on a mac for the lib. Sorry I can't help more than that atm.

Thanks hopi for replying..

I've searched eveyiwhere possible to place the ffmpeg.dylib. I've made some progress by placing the ffmpeg.dylib into "application > reaper "show package content" > content > plugins" . That's where I found many other dylib files, hence I placed the ffmpeg there, low and behold, I now have the "Ffmpeg" render in format dropdown list. But MY VIDEO ITEMS STILL SHOW "USING QUICKTIME DECODER" in SOURCE PROPERTIES.

This has got to be a bug. Cockos, please tell us where the file needs to be placed instead of us having to make wild guesses n try n errors.

[Bernstraw]

* In take envelopes, if you move a point over another one, your point starts running to the left border of the item.
Same behaviour with grid snap on or off (the classic envelopes do not allow to move points over each others) :

[IMG]http://img687.**************/img687/9290/pitchenvpoints3.gif[/IMG]


* Old bug : if docked (attached or floating) the FX browser always clears the filter field after closing.
I've also noted that the undocked FX browser window is the only one having a large window frame with a maximize button (windows7).

[hopi]

seems like painting a major chord works as expected but not true for a minor chord...

test... set grid to say 1/8
set cursor at start of bar
set 'Key' and set to maj chord

paint vertically ONLY in the first 1/8 note column


now change to minor chord and move the cursor to next measure start [just for clarity]

for me the minor chord notes barely paint... very sketchy

[hopi]

do you think it would be good to have some indication on the piano keys for the inline editor to show which octave we are looking at?

[lowellben]

Originally Posted by Tomm

The hover state of the top fx button does not deactivate properly when moving up into the "Input Effect" button:

brief aside please:

what theme is that? I really like it!

[Dstruct]

Originally Posted by lowellben

brief aside please:

what theme is that? I really like it!

The new v4 default theme?

[hopi]

edit post moved to normal 40a thread

[lowellben]

Originally Posted by Dstruct

The new v4 default theme?

Oh, sorry. I didn't know that - thanks!

[reaperdeeper]

Some bug:

when loading a project , some plug in messages stay behind the spalsh screen.
For example typical Kontakt message "Physical memory is getting low" is not visible and project stops loading till u search the window and click OK.
They should be in front of the splash screen.

[gwok]

Originally Posted by reaperdeeper

Some bug:

when loading a project , some plug in messages stay behind the spalsh screen.
For example typical Kontakt message "Physical memory is getting low" is not visible and project stops loading till u search the window and click OK.
They should be in front of the splash screen.

yup, happens here too sometimes

[lawrs]

TRACK SELECTION PROBLEMS

1. Media item left click changes track selection, but media item left drag doesn't.

[img] http://img51.**************/img51/9449/trackselection.gif[/img]

GIF above shows behavior of "media item left click > shift >
add item to selection and extend time selection" across multiple tracks.

This is the desired behavior, as it automatically (smart) selects all
affected tracks which selected media items are in. Very intuitive.





[img]http://img408.**************/img408/9652/trackselection3.gif [/img]

This GIF shows unwanted behavior of "media item left drag >
marque select items and time" across multiple tracks.

This is the undesired behavior, as it doesn't automatically
select the tracks which the selected media item are in.
At 7 secs, I'm using "media item left click" which shows the desired behaviour.





2. "Track left click > shift > extend time selection"
across multiple tracks doesn't add track selection

[img]http://img88.**************/img88/2297/trackselection2.gif [/img]

GIF above shows undesired behavior when left clicking across empty tracks.
If clicked across multiple tracks, extending time selection should add track selections.







3. Additional action for "media item left click"

[img]http://img156.**************/img156/2133/timeselectionstartend.gif[/img]

"media item left click" > shift > "add to item selection
and extend time selection (auto set start time selection on
beginning of 1st item, and end time selection on end of last item)

This should also have "add to track selection",
having these 3 (time, item, and track) would make it easier for
users to use smart copy/cut commands.





4. Locking items should bypass locked items from ripple, not disable ripple.


[img]http://img337.**************/img337/1760/lockripple.gif[/img]
GIF above shows what happens when an item in a project is locked,
ripple all mode doesn't allow dragging of items. It makes a lot
more sense to bypass the locked items from being affected by ripple all,
rather than totally disable ripple all. Much needed when cutting down
long projects into shorter versions.



e.g : when doing an ad of 20sec, 15sec, 10sec, usually the
longest (20sec) will be done first, then we cut it down into 15sec.
Ripple all mode is best for this, but sometimes there's a track that
you don't want affected by ripple all. Not happenin', there isn't such
a choice. Tough luck.






I really hope the devs will take a look at these issues seriously,
as I spent lots of time to gather it here and put it together with
GIFs and explanation. These are some of the workflow breakers that
I encounter on a daily basis which I feel is hindering Reaper from
becoming more intuitive and user-friendly.

[NickScottGuitar]

V4 Alp4 Bug:

When using arrow keys to move selection (I do this for really precise stuff), reaper plays back even after I let go (for quite some time, actually).

When scrolled out, I get the chipmunk effect, and it will continue even 5 seconds after I let go of the arrow keys.

[Dstruct]

Originally Posted by Wilkesin

Yeah, checked that. Still seems to be running...

edit: clicking on the audio properties and just hitting ok withough changing anything seems to fix the problem. Now Im not sure if this is a reaper problem at all. How do drivers work fine one day and crap out the next?

ASIO drivers?

[Jeffos]

4aplha41, crashes vs takes (Win XP 32). I see many different crash offsets, 2 examples below. All is OK with the same projects in 4aplha39.

1) Load the attached project "empty_takes2.RPP" => crash when loading

The application, C:\Program Files\REAPER\REAPER.exe, generated an application error
The error occurred on 02/14/2011 @ 21:22:01.406 The exception generated was c0000005 at address 7C911766 (ntdll!RtlInitializeCriticalSection)

2) Load the attached project "take4a41.RPP" (loading the prj succeeds), quit REAPER => crash

Application popup: reaper.exe - Application Error :
The instruction at "0x7c910a19" referenced memory at "0x00000000". The memory could not be "read".

EDIT: fixed (4aplha42)

.

[Guido]

Originally Posted by reaperdeeper

Some bug:

when loading a project , some plug in messages stay behind the spalsh screen.
For example typical Kontakt message "Physical memory is getting low" is not visible and project stops loading till u search the window and click OK.
They should be in front of the splash screen.

Confirmed.Been that way since the alphas started.btw do u use a custom splash screen?

Guido

SP32SP3 Reaper V4a40

[Dannii]

Originally Posted by Dannii

I think I've found a WALTER bug in A38. In my Neve, Calrec, Bob Katz theme, I've set up the input FX button to disappear on small MCP heights (with narrow MCP option) and it works perfectly in A37. In A38, the input FX button disappears at the correct resize but reappears as the height is further decreased.

Here's a couple of licecaps....



I've tried the following rtconfig code responsible for the resize which works fine in A37 but not A38...

set mcp.fxin ?recarm h>380 [23 110 20 20 0 1 0 1]

or

set mcp.fxin ?recarm h<380 [0] [23 110 20 20 0 1 0 1]

Just confirming that in A40 and 41 this is now fixed. Great stuff devs.