Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Pre-Release Discussion

Reply
 
Thread Tools Display Modes
Old 05-19-2017, 11:15 AM   #1
vitalker
Human being with feelings
 
vitalker's Avatar
 
Join Date: Dec 2012
Posts: 13,333
Default v5.50pre9 - May 19 2017

v5.50pre9 - May 19 2017
+ Transport: new option to flash transport status yellow on possible audio device underrun
+ VST3: IContextInfoHandler2/IContextInfoProvider2 support
+ Windows: support receiving ASIO overload notifications
# Automation items: add option to trim existing items behind edited items
# Automation items: edits to unselected items do not affect selected items when other pooled items are affected [p=1843967]
# Automation items: fix item length after re-looping [p=1843705]
# Automation items: fix undo after closing automation item properties dialog [p=1843695]
# Automation items: fix uneditable points in looped items [p=1843639]
# Automation items: ignore "edits affect pooled copies" option when copying
# Automation items: improve "collect points" behavior when editing pooled automation items
# Automation items: improve ripple editing behavior
# Preferences: add "trim content behind media items when editing" to Preferences/Project/Media item defaults
# Video: try to open .aac files with video decoders


Full changelog - Latest pre-releases

I was using great script by Edgemeal to create this changelog. The link: https://stash.reaper.fm/v/30246/Reape...%20Release.zip

Last edited by vitalker; 05-19-2017 at 11:22 AM.
vitalker is online now   Reply With Quote
Old 05-19-2017, 11:32 AM   #2
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

How should AIs work with VCAs and "Envelope: apply all VCAs to selected tracks and remove from VCA groups" when an AI is on the VCA track?
bFooz is offline   Reply With Quote
Old 05-19-2017, 11:57 AM   #3
Jae.Thomas
Human being with feelings
 
Join Date: Jun 2006
Posts: 22,567
Default

Quote:
Originally Posted by vitalker View Post
v5.50pre9 - May 19 2017
+ Transport: new option to flash transport status yellow on possible audio device underrun
+ VST3: IContextInfoHandler2/IContextInfoProvider2 support
+ Windows: support receiving ASIO overload notifications
awesome! So maybe someone could script a marker to drop in places where this might have happened
Jae.Thomas is offline   Reply With Quote
Old 05-19-2017, 01:18 PM   #4
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Creating new pooled AI's is broken with "edits affect all pooled automation items at the same time position" on.


  • Create AI with option-left drag (macOS) (draw a pooled copy of the selected automation item)
  • Select created AI
  • Create AI with option-left drag (macOS) (draw a pooled copy of the selected automation item)
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:25 PM   #5
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Collect points with "edits affect all pooled automation items at the same time position" on gives different results depending on what was selected last!



Easy-replication:
  • Create an AI on a Volume Track (1)
  • Create a pooled copy of (1) starting at the same time on a Pan Track
  • Collect Left (Cmd-left drag macOS).
  • Alternate this process after selecting the 'other ai' once.
  • Try this process after selecting back and forth manually.
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:30 PM   #6
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

With "edits affect all pooled automation items at the same time position" on, Collecting points only can collect the bottom AI.



Gif should be self-explanatory.

This may not be strictly a bug per-se, however I think the expectation would be that the selected, or acted upon, AI is what consumes the envelope.
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:38 PM   #7
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

When writing automation manually, if the written automation crosses an AI boundary, then the automation seems to almost always be written 1-2 points "late" to the AI.



The gif doesn't show an example where it's particularly problematic, however there are times when that automation point that ends up 'under' the AI is a vital part of a complex motion.
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:42 PM   #8
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,747
Default

Regarding posts 5 and 6, maybe the best solution is for the "affects all pooled automation items" option not to apply to the "collect points" mouse modifier?
schwa is offline   Reply With Quote
Old 05-19-2017, 01:43 PM   #9
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

http://forum.cockos.com/showpost.php...0&postcount=25

^^

This behaviour still exists. How points can be moved relative to other points depends on the current snap to grid setting.

This appears to be a regression, since 5.40 behaves sensibly.
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:44 PM   #10
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by schwa View Post
Regarding posts 5 and 6, maybe the best solution is for the "affects all pooled automation items" option not to apply to the "collect points" mouse modifier?


That seems reasonable. It seems like it's a lot of source of headaches.
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:52 PM   #11
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

While checking old bugs... I ran in to this guy again: http://forum.cockos.com/showpost.php...7&postcount=46



However this time I saved the project with undo history. It is attached to this post.
Attached Files
File Type: zip weirdbug.zip (56.9 KB, 95 views)
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 01:53 PM   #12
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

This still happens consistently: http://forum.cockos.com/showpost.php...4&postcount=47

Related:

When splitting overlapping items, sometimes AIs get oddly re-ordered. Sometimes they do not.


Last edited by Robert Randolph; 05-19-2017 at 01:58 PM.
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 02:01 PM   #13
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Splitting an AI makes a pooled copy.

Media items and Midi items do not do this. Is that intentional?
Robert Randolph is offline   Reply With Quote
Old 05-19-2017, 02:09 PM   #14
Edgemeal
Human being with feelings
 
Edgemeal's Avatar
 
Join Date: Apr 2016
Location: ASU`ogacihC
Posts: 3,913
Default

Simple item copy to a new track with "points move with items" was working in Pre8, broken in Pre9...

Edgemeal is offline   Reply With Quote
Old 05-19-2017, 02:54 PM   #15
vanhaze
Human being with feelings
 
vanhaze's Avatar
 
Join Date: Jul 2012
Location: Netherlands
Posts: 5,247
Default

Quote:
Originally Posted by vitalker View Post
v5.50pre9 - May 19 2017
+ Transport: new option to flash transport status yellow on possible audio device underrun
Hallelujah !
Many thanks for this Cockos !

For the ones interested in this option:
I noticed this option can be found by right-clicking in the time indicator area of the Transport Bar.
It seems, by default, the option is now turned OFF. (great !).
__________________
Macbook Pro INTEL | Reaper, always latest version | OSX Ventura | Presonus Studio 24c
My Reaper Tips&Tricks YouTube Channel: https://www.youtube.com/user/vanhaze2000/playlists
vanhaze is offline   Reply With Quote
Old 05-19-2017, 04:12 PM   #16
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
Default

Quote:
Originally Posted by vitalker View Post
# Video: try to open .aac files with video decoders
Thanks.
nofish is offline   Reply With Quote
Old 05-19-2017, 05:36 PM   #17
PitchSlap
Human being with feelings
 
PitchSlap's Avatar
 
Join Date: Jan 2008
Location: Vancouver, BC
Posts: 3,793
Default

Quote:
Originally Posted by vanhaze View Post

For the ones interested in this option:
I noticed this option can be found by right-clicking in the time indicator area of the Transport Bar.
It seems, by default, the option is now turned OFF. (great !).
Thanks, I was wondering where to find it (checked device settings but no dice).
__________________
FRs: v5 Media Explorer Requests, Global Quantization, Session View
Win10 Pro 64-bit, Reaper 6(x64), AMD 3950x, Aorus X570 Master, 64GB DDR4 3600, PowerColor Red Devil 5700XT, EVO 970 2TB, 10TB HD, Define R6
PitchSlap is online now   Reply With Quote
Old 05-19-2017, 10:37 PM   #18
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

# Automation items: fix uneditable points in looped items [p=1843639]

Gutted, i was hoping this mean't we could select points inside an automation item and run actions, this badly needs adding
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 05-20-2017, 06:48 AM   #19
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by gpunk_w View Post
# Automation items: fix uneditable points in looped items [p=1843639]

Gutted, i was hoping this mean't we could select points inside an automation item and run actions, this badly needs adding


To elaborate, here's a list of non-script actions that don't seem to work on points in AIs:
  • Envelope: Copy points within time selection (Copies the AI, not the points)
  • Envelope: Copy selected points (Copies oddly. Paste is done oddly)
  • Envelope: Cut points within time selection (Cuts the AI, not the points)
  • Envelope: Cut selected points (Copies oddly. Paste is done oddly)

SWS/BR actions largely don't work correctly. I haven't found any that do in a quick look.
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 06:58 AM   #20
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,747
Default

Quote:
Originally Posted by Robert Randolph View Post
While checking old bugs
Finally fixed this one, thanks for including the undo history!
schwa is offline   Reply With Quote
Old 05-20-2017, 07:01 AM   #21
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Collecting points leaves an 'edge point' of the AI behind.


  • Collect points with AI over existing envelope points (edge-left drag macOS)
  • Move AI to reveal underlying envelope

The collection action seems to create a new edge point that's added to both the AI and the underlying envelope.

Option-left drag to consume points with a new AI acts like I'd expect.



I understand that the AI needs a new point added when collecting, but the underlying envelope should not get that point.
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 07:08 AM   #22
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

The mouse modifier "Move automation items relative to other selected items" is available as a left-drag option.

If this is intentional, then it doesn't work.



Shouldn't this be for the "Automation Item" context?
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 07:17 AM   #23
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,747
Default

Quote:
Originally Posted by Robert Randolph View Post
The mouse modifier "Move automation items relative to other selected items" is available as a left-drag option.

If this is intentional, then it doesn't work.

Shouldn't this be for the "Automation Item" context?
You need at least 3 selected items at different positions for this to have an effect.
schwa is offline   Reply With Quote
Old 05-20-2017, 07:25 AM   #24
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by schwa View Post
If layered, they are handled as two envelopes in series.
There's still an 'issue' when any AI has an -Inf value. All other envelopes values are cancelled. Previously reported here: http://forum.cockos.com/showpost.php...9&postcount=21



This is a problem because when mouse-editing, even on a high-res monitor with a very large envelope lane, the lowest value you can drag to is about -50dbFS before it snaps to -inf.

It's also easy to end up with a -inf value when using external controllers. Possible to even end up cancelling out all your overlapped envelopes when writing data in the Latch automation mode!

I don't know what the suggested behaviour is, however there's been probably a dozen times where I thought my envelope was bugged because an -inf value ended up on an overlapped AI.
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 07:29 AM   #25
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by schwa View Post
You need at least 3 selected items at different positions for this to have an effect.
I suggest trying this with various selections of 3+ items. It doesn't work consistently at all.

I've only found 1 case where it actually does something: when right-edge editing 3 overlapping items at different times. Any other selection of 3+ items does something different.

I can make another gif of various selections of 3+ items if you'd like.
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 07:37 AM   #26
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,747
Default

Quote:
Originally Posted by Robert Randolph View Post
There's still an 'issue' when any AI has an -Inf value. All other envelopes values are cancelled.
That's the intended behavior. Imagine that you have two volume faders in a row. If either of the faders is at -inf, the output should be silent.
schwa is offline   Reply With Quote
Old 05-20-2017, 07:38 AM   #27
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,747
Default

Quote:
Originally Posted by Robert Randolph View Post
I suggest trying this with various selections of 3+ items. It doesn't work consistently at all.

I've only found 1 case where it actually does something: when right-edge editing 3 overlapping items at different times. Any other selection of 3+ items does something different.

I can make another gif of various selections of 3+ items if you'd like.
Please do illustrate cases where it doesn't work as expected.
schwa is offline   Reply With Quote
Old 05-20-2017, 07:50 AM   #28
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by schwa View Post
That's the intended behavior. Imagine that you have two volume faders in a row. If either of the faders is at -inf, the output should be silent.
I think the issue is how easy it is to end up with -inf values in envelopes.

It's totally fine with the current envelope system, but with overlapping AIs it gets rather confusing.

Take this example:


  1. In the first example with the Parametric LFO at an amplitude of 100; my highest value of the combine envelope is -1.82dbFS. My lowest value is a huge jump down to -inf. The visual representation of a modulated sine is not what's being rendered.
  2. In the first example with the Parametric LFO at an amplitude of 99; my highest value of the combine envelope is -1.86dbFS. My lowest value is -46.2dbFS. The visual representation of a modulated sine is intact.


So I won't beat this to death, but I wish to restate that I understand the logical idea behind this. However, the resulting behaviour is unintuitive and can cause unexpected behaviour that's difficult to track down.

Thank you for humouring me in this specific topic.
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 08:03 AM   #29
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by schwa View Post
Please do illustrate cases where it doesn't work as expected.
Ok, so I guess I'm misunderstanding how this is supposed to work here or something. It only works if you left-drag the right most or left most selected item.

I think this is my mistake then. The name of the command doesn't make much sense to me.

---

However, there is a visual bug when you do this...



Edit: This is not just a visual bug. The AI's don't work at all when they overlap the envelope!
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 08:09 AM   #30
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,747
Default

Quote:
Originally Posted by Robert Randolph View Post
So I won't beat this to death, but I wish to restate that I understand the logical idea behind this.

With respect .. this behavior is intended and, I believe, preferable to any alternative. -46dbFS to -inf is not actually a huge jump. That change represents the equivalent movement on the volume fader as going from +0.0 to +0.01. In amplitude terms, -46dbFS is one-half of one percent of full scale. So, it's an expected result when changing the LFO amplitude by one percent. I think we are now beating this to death
schwa is offline   Reply With Quote
Old 05-20-2017, 08:53 AM   #31
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by Robert Randolph View Post
To elaborate, here's a list of non-script actions that don't seem to work on points in AIs:
  • Envelope: Copy points within time selection (Copies the AI, not the points)
  • Envelope: Copy selected points (Copies oddly. Paste is done oddly)
  • Envelope: Cut points within time selection (Cuts the AI, not the points)
  • Envelope: Cut selected points (Copies oddly. Paste is done oddly)

SWS/BR actions largely don't work correctly. I haven't found any that do in a quick look.
There are no actions that work on selected points within in an AI, it is a terribly flawed design, this is going to annoy a lot of people in use.
Having to slice an AI to run actions on it is just bizarre (Edit, i mistyped here, i meant having to create a time selection)
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!

Last edited by Win Conway; 05-21-2017 at 12:57 PM.
Win Conway is offline   Reply With Quote
Old 05-20-2017, 09:55 AM   #32
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by gpunk_w View Post
There are no actions that work on selected points within in an AI, it is a terribly flawed design, this is going to annoy a lot of people in use.
Having to slice an AI to run actions on it is just bizarre
I don't think that's correct. I tried literally every envelope point action when writing that post. The only ones that didn't work were what I listed.

Can you give a specific example?
Robert Randolph is offline   Reply With Quote
Old 05-20-2017, 10:49 AM   #33
Embass
Human being with feelings
 
Embass's Avatar
 
Join Date: Jan 2014
Posts: 923
Default

copy paste unlooped automation item with start offset.

https://goo.gl/LTf3au
Embass is offline   Reply With Quote
Old 05-20-2017, 05:15 PM   #34
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by Robert Randolph View Post
I don't think that's correct. I tried literally every envelope point action when writing that post. The only ones that didn't work were what I listed.

Can you give a specific example?
No point actions work on selected points within an automation item, they only work on selected automation items, so i cant select half the points inside an automation item and run the reduce points action for instance.
It will reduce the points of the entire automation item.
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 05-21-2017, 08:16 AM   #35
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by gpunk_w View Post
No point actions work on selected points within an automation item, they only work on selected automation items, so i cant select half the points inside an automation item and run the reduce points action for instance.
It will reduce the points of the entire automation item.
Those commands don't work on selected points outside AIs either though. They apply to the whole envelope.

So I assume that working on the whole AI is intended.
Robert Randolph is offline   Reply With Quote
Old 05-21-2017, 12:55 PM   #36
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

My point is (Pun fully intended) that it is a flawed design, just because the original automation system had a flaw, does it mean we should carry it through to the new system ?

You can run the reduce action only in time selection, which is bad UX, most people will expect to just make a point selection, not have to make a time selection.

I am not sure why these features are considered strange, it just makes sense, select points, run point actions on only those points, no points selected, run point action on selected automation item or selected envelope lane if no automation item selected or present.
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!

Last edited by Win Conway; 05-21-2017 at 01:01 PM.
Win Conway is offline   Reply With Quote
Old 05-21-2017, 02:02 PM   #37
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Quote:
Originally Posted by gpunk_w View Post
My point is (Pun fully intended) that it is a flawed design, just because the original automation system had a flaw, does it mean we should carry it through to the new system ?

You can run the reduce action only in time selection, which is bad UX, most people will expect to just make a point selection, not have to make a time selection.

I am not sure why these features are considered strange, it just makes sense, select points, run point actions on only those points, no points selected, run point action on selected automation item or selected envelope lane if no automation item selected or present.
I think you'd get a better response if you phrased your request more thoroughly.

The issue isn't that a bunch of actions don't work on AIs (since many DO work), it's that you want 2 specific actions to work differently than they do currently.


So it seems that the request is that it would be very useful to have the 2 following actions:
  • Envelope: Reduce number of points in selected points
  • Envelope: Reduce number of selected points by half

And perhaps to have the current commands to be renamed to indicate that they work on the whole AI/envelope or time selection.
Robert Randolph is offline   Reply With Quote
Old 05-22-2017, 10:09 AM   #38
Robert Randolph
Human being with feelings
 
Robert Randolph's Avatar
 
Join Date: Apr 2017
Location: St. Petersburg, FL
Posts: 880
Default

Not a bug, but a request:



It's rather difficult to grab a point when it's in the lower right or lower left of an AI. There's 4 possible zones here and they are really close together.

A large part of the issue is that the cursor changes make it difficult to know where the cursor is pointing so you can adjust to find the envelope point.

I do not have a suggestion for how to improve this, but it's been very annoying to deal with when using AIs in actual production.
Robert Randolph is offline   Reply With Quote
Old 05-22-2017, 10:14 AM   #39
Jonas Ekstrom
Human being with feelings
 
Jonas Ekstrom's Avatar
 
Join Date: Feb 2017
Location: Stockholm
Posts: 98
Default

Quote:
Originally Posted by Jason Brian Merrill View Post
awesome! So maybe someone could script a marker to drop in places where this might have happened
Yes! Please ☺👍🍺
__________________
Jonas Ekstrom
www.northmastering.com
Jonas Ekstrom is offline   Reply With Quote
Old 05-22-2017, 03:01 PM   #40
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by Robert Randolph View Post
I think you'd get a better response if you phrased your request more thoroughly.

The issue isn't that a bunch of actions don't work on AIs (since many DO work), it's that you want 2 specific actions to work differently than they do currently.


So it seems that the request is that it would be very useful to have the 2 following actions:
  • Envelope: Reduce number of points in selected points
  • Envelope: Reduce number of selected points by half

And perhaps to have the current commands to be renamed to indicate that they work on the whole AI/envelope or time selection.
Erm no
All point based actions should run how i previously stated.
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway 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 06:43 AM.


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