JARG

I messed around with a similar pedal back in the day. It was a two-step affair: you clicked the button to start the audio capture and then clicked it again to end the capture, which then started the loop until you decided to end it. As I recall, it could capture a max of 8 seconds.

Wasn't clicking it (I don't think I clicked it in the old version, either), but that's done the trick. Thanks!

No change as far as I can tell. Thanks for trying.

Will do.

If I had to hazard a guess, I'd say the cookie expires after about 60 minutes. Previously the expire was very long -- I could stay logged in for days at a time if I didn't close the browser and/or log off from the site (I purge all cookies when I close my browser). I don't think we need to go back to that, so maybe expire after 12 hours? Update: actually, the expire seems shorter than I previously thought, so now I'm thinking it's not a cookie issue, but maybe a session variable issue. Banks use session variables to automatically expire your session if you're inactive after a certain period of time -- maybe that's what's going on here?

Can the login cookie duration time value be increased? It seems like it expires sooner than before the software upgrade.

He does a good job at emulating Randy's vibrato, too.

http://youtu.be/PlJQXwCsZWg

Alex and Geddy both have performed while sitting in chairs.

How difficult was it for Rush to transition from recording bed tracks "off the floor" as a band, to tracking individual performances? Whose idea was it? Do you feel that what was gained by such an approach overcame any losses?

Thank you for doing this! I've had the CD set (and DVD) since the day it came out, and I had no idea there was a bonus video of Vital Signs on the CD! Could you share how you extracted this? I put the 3rd CD in my disk drive of my MacBook Pro, and I can't find anything besides the tracks. All the same, thank you for your restoration work and for posting it on YouTube! :) The video is from a bootleg of the show, I gather, and is not part of the RIR set. Right, not from the official RiR capture. We have the audio from the CD and a bootleg video of the exact same performance that the audio is from (that was wasn't clear to me earlier), so TGR married the "official" audio with the bootleg video.

Can confirm it was recorded on 19th Oct 2002 at the Quebec City gig - the same gig that video footage is taken from. I think in general Geddy's vocals were very strong on the Vapor Trails Tour, I'm guessing because they were so well rested after not touring for 5 years. https://www.rhino.com/product/in-rio Thanks for confirming.

I get that the audio is a bonus on the RiR CD, but is the source of that audio from that tour? It sounds much earlier in their career, based on Geddy's voice.

:lol: The infamous misheard lyric!

Just read this: Good news?

Interesting take. Of all the countless times I've looked at the MP album cover, it never occurred to me that the pictures might be being removed. The body positioning of the movers always made me think the pictures were headed into the building.

I've been getting sporadic slowdowns and a couple of 404s in the past few hours, ever since I started archiving RS. I think I'll turn that off for now, and later tonight I'll shut the board down and optimize and repair the database again. After all the content we've removed from it in the past few days it could probably use a little freshening up. As for your Chrome troubles, I know nothing about Chrome (I've never used it) so I don't know if your problems are strictly related to that browser. Can anyone help? Will clearing cache and cookies fix some things? I suspect the culprit isn't the browser, but your house-keeping activities. I just tried the site in Chrome and didn't face any issues. It's probably not a bad idea to shut the board down when you're doing your house-keeping stuff.

Another thing to consider is the ability of the market to adapt under different conditions. For example, if companies have equipment, permits, employees, etc., in place working a fracking well but they're only producing at 50% then if a spike occurs, they can easily increase production. If they don't have those things in place then it may take years to do it. If Canada can increase their oil drilling production in remote areas, but have no way to move it, then their production increase is limited until they have a pipeline or road built to move the oil which could take years. Yup. Logistics networks, infrastructure, and architecture are all part of the "supply" half of the "supply and demand" relationship.

Indeed The effect of this ought not to be understated. Demand dropped due to COVID and production followed suit. That's the exact order you'd expect. Now that demand has returned, production needs to catch up, and until it does, the disparity between demand and production will be a factor in cost to consumer.

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently. Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in. I can't believe how long that problem has existed. It's not something I ever thought to check for, even knowing we were still in need of an SSL certificate -- "Does our link in a search result actually work?" Who knows how many people were looking for a Rush forum to join, found us on Google, clicked the link and got nothing, then just walked away. It's embarrassing. Our pages are are asp.net, but here's a redirect I wrote to handle a related issue where we want to load our https page even if users came to it from an http link: string current_url = HttpContext.Current.Request.Url.AbsoluteUri; if(current_url.IndexOf("https://") == -1) { current_url = current_url.Replace("http://", "https://"); Response.Redirect(current_url); } It may be possible to do something similar here. Yeah, we're in the opposite boat right now -- search engine links looking for an https TRF and not finding us because we're still http. Once we're https compliant, the search engine links should connect right up. We'll find out soon enough. That redirect you wrote could be something to use in the short term, though. Can you simply flip-flop the http and https in that Replace command? That, and you change the check from == -1 to > -1, so this: if(current_url.IndexOf("https://") > -1) { current_url = current_url.Replace("https://", "http://"); Response.Redirect(current_url); } The previous check says "if the page URL doesn't contain 'https://' then do the swap. This one says "if the page URL does contain 'https://' then do the swap, only this time the swap is flip-flopped.

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently. Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in. I can't believe how long that problem has existed. It's not something I ever thought to check for, even knowing we were still in need of an SSL certificate -- "Does our link in a search result actually work?" Who knows how many people were looking for a Rush forum to join, found us on Google, clicked the link and got nothing, then just walked away. It's embarrassing. Our pages are are asp.net, but here's a redirect I wrote to handle a related issue where we want to load our https page even if users came to it from an http link: string current_url = HttpContext.Current.Request.Url.AbsoluteUri; if(current_url.IndexOf("https://") == -1) { current_url = current_url.Replace("http://", "https://"); Response.Redirect(current_url); } It may be possible to do something similar here.

Yes, fetching records out of a set of 5 million is going to take some time, regardless of indexing. And yes, your parameters are extremely conservative. I have a ticketing tool app that archives cases 30 days after their closure date. Are all the posted comments stored in a single table or does each sub-forum have a dedicated table? Single table. I don't know enough about this stuff to know if that's advantageous or not. I think it's probably fine. Having them all in one table certainly makes house-keeping tasks, such as archiving, easier. The most obvious drawback is that the table has a buttload of rows.