That's a mouthful, hence people simply saying "StrongLoop" generally. Many people, including myself, use StrongLoop as a way to referring to the 'product' but technically the product name is "StrongLoop Node.js API Platform". "StrongLoop" by itself means the company that IBM consumed a few months ago. In a nutshell though - LoopBack is what lets you build the API. Of course, in the real world, you need custom business logic, security, etc. We're talking five minutes from concept to an API. If I'm a cat web site, I can quickly create a full API around getting cat data. What that means is I can quickly create a REST-based API based on a model, where a model represents the content I'm working with. LoopBack is an open source Node.js/Express-based framework for rapidly building APIs. I've blogged (and presented) on LoopBack a bunch of times now. But for now, let me give you some context to how these three products relate. If you haven't heard about it, well, that's part of my job, and you will be seeing me present on it and blog about it more (both here and on the StrongBlog. It is a big deal, and I've been trying to get up to speed on it (along with LoopBack and StrongLoop), which is why I haven't blogged on it yet. Justin is referring to a product, API Connect, that I haven't yet discussed on the blog. So earlier today I was sent the following what is diff between loopback & API connect? SL docs say use apiconnect but loopback.io says use Strongloop- Justin James April 27, 2016 I'll include links to all the boringofficial resources for folks who want that side of the story, but what follows is 100% my own words only. Yeah, I work for IBM, but I think folks know that when I blog, I have my own voice and my own way of saying things. So now I'm sort of kicking myself for going through all of this trouble with a cheaper software when I could have just shelled a little extra cash earlier and gotten a more reliable product.So first and foremost - let me start off by being explicitly clear that what follows is 100% not IBM-approved material at all. It made no sense to me and was pissing me off so I said screw it and just got Loopback and it worked basically instantly. I'd have to fiddle with it unchecking and rechecking some boxes in Sound Siphon or in my aggregate audio device in MacOS and then it would just magically start capturing.Īnyway yesterday I spent hours trying to get Sound Siphon to work properly - it was capturing Zoom audio but not anything else. Getting it to capture Discord was also troublesome, just seemed random whether or not it would actually work. It never wanted to capture the audio from Chrome but would capture it from Firefox just fine. Problem is, I never could quite get Sound Siphon working perfectly. It basically does exactly what Soundflower/Loopback for Mac does, except it's only $30 for a license instead of $100. I was also using it to route the monitored audio from the DAW to a virtual audio device defined with Sound Siphon which I would use as the virtual mic so that remote guests could hear clips and stuff that I would play on my computer. I bought Sound Siphon nearly a year ago at this point and have been using it every week for a podcast in order to capture audio from different programs and route them to their own dedicated tracks in my DAW. Does anyone here use Sound Siphon and experience seemingly random, impossible to diagnose issues?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |