UncleAge@4mica wrote:
When I was a wee lad, my best friend’s dad bought him a C64, with the monochrome green monitor. One day his older brother got it hooked up to the big color TV in the living room, and it was Impossible Mission and Raid Over Moscow all weekend!
Remember when the programs were on cassette, and you had to wait 20-30 minutes to load something? That taught me patience!
Patience? Patience is typing in the programs that they would put into the magazines. Oh, and don’t f-up and make a typographical error 😆 Page-after-page-after-page…
UncleAge@Slomo wrote:
@Zynewave wrote:
Are you that old too? 😉 Ahh, the good old Commodore 64 days.
Oh yeah, my first ‘DAW’ was Steinberg Pro 16 on my trusty old C64, with a handbuilt MIDI-interface…or maybe it was Pro 24.
bnch of newbies on your fancy color screened VIC-20 and C-64’s. Real computer screens were monochrome baby!!! None of that fancy amber crap either, mean green all the way! 😛
UncleAgeI am a little surprised by some of the negative reactions. But as another user put it, maybe it’s a sign of a certain demographic’s response to change. I’m 43 in a few weeks and I have been a computer zealot since I sat down at a Commodore PET in 9th grade and started learning assembly code for the 6502 processor. I embrace change. I always like to hear about the latest greatest thing and I try to imagine how that new technology could be leveraged to my advantage.
In 2008 I was setting up a new business for myself, after working for someone else 13 years. While I was waiting for some government certifications I took a quickie gig as a chauffeur, for the NFL, during the SuperBowl here in Phoenix. After driving around an unnamed quarterback all day (who was really a great guy) he gave me a bunch of stuff as a tip. One of those things was an iPod Touch. Now I’ve been a MS guy most of my adult life but I have no bad feelings for Apple so I gave it a spin. And I LOVED IT!! That experience led me to buy and iPhone later on and an iMac earlier this year. As you might guess my next purchase will probably be some sort of tablet. Maybe even an iPad.
I think that within the next couple of generations we will have mobile devices that will handle most tasks effectively. And I think it’s foolish to ignore what is so glaringly obvious. I don’t see any mobile device handling heavy studio work for at least 5-10 years. But there are quite a few applications for “Mobium” outside of my studio work. Having the ability to record performances on location and do a simple transfer of the project back to my main setup back at the ranch is very useful. Something more full featured than a Zoom for field recordings would be welcomed as well. I can see Podcasting taking another step forward with the correct app as well. Hell, I think every videographer is waiting for an app to come along that will handle audio captured on-set in a way that will transfer easily to post-production. And I could go on and on…
Ok. Enough of this rant stuff.
Frits, just keep going with it. It’s all good. You took a risk spilling the beans this way but I think it was a good thing to do. And when you are ready to test things out in OSX land, give me a holler.
Also, I think you are wise to keep your options open to iOS and Android. I have an iPhone (hacked to work on T-Mobile) but I am seriously considering an Android phone because I don’t like the constrictions that are placed on me and my phone by Apple’s development. And even though I could develop apps for the iPhone I won’t because I’m not a huge fan of their approval process.
One more thing. Don’t think for a moment that other dev’s are not doing the same thing behind closed doors. Every major host developer is more than likely trying to custom tailor their product for one of those two environments, if not both. If you’re going to do it then do it now. You will gain little from trying to compete with them after their products are released. You are the small dev and should take advantage of the fact that you can be more nimble in the decision making process than folks that have to please the shareholders.
Ok, this time I really mean it…rant over 🙂
UncleAgeI remember when I first bought Podium I was all kinda lost. It was a much different app then 🙂 Anyway, what would amaze me is that, it seemed as though no matter what time of day I would post a question, Fritz would answer. Swear to my god I thought he never slept. I try and take that approach with everyone who comes to me looking for help in my business as well. And I totally respect his approach to customer service and the many times he has taken a different development path because we all needed feature “X” or something else to make life a little easier.
I say that to say this. I think the OP has made a fair point.
I think the troll did not.
And I have never seen that trollish approach work here. It has largely been a respectful forum for years. I doubt that your posts will change that. And I didn’t want to hijack what was a purposeful and probably much needed thread. But it needed to be said.
And Fritz, should some other posts in this thread come up missing 😛 please delete this one as well.
UncleAgeAny requirements like total inputs/outputs, mic pre’s or any other things along those lines?
UncleAgeUncleAgeYour English is light-years better than my Espanol! And I think you would do fine abroad.
UncleAgeUncleAgeModularity:
A substructure handling the routing of all midi and audio should be the basis of any future DAW. It is one of the more challenging and often limiting factors in the hardware/analog realm. eXT and Bidule (and others) have laid some ground work for this type of functionality. However, how it is exposed to the end user should also be a concern. I can route midi and audio all around in Reaper but I don’t really like the interface that’s exposed for me to use. I’d much prefer a more graphical approach.
Racks:
I am amazed that none of the DAWs out there have been able to meet or surpass Tracktion’s implementation of racks. Live and Reason allow you to combine a chain of instruments and fx but don’t allow you to route the midi and audio as freely as you could in Tracktion (parallel routing, not just serial). You basically get a chain or preset of a set of plugs. Other hosts have a “rack” but seem to totally miss the opportunity to do more with this type of feature.
Whether or not these can be implemented in Podium, well, I dunno. But the buzz created (if done properly) would be immense, in-my-humble-opinion…
UncleAge@Zynewave wrote:
Just a quick halfdone mockup to illustrate my idea:
I have no idea if this is good for this particular problem but… the idea of floating a context window that allows for fine adjusts is a really cool idea. Reminds me of the dashboard feature on my mac.
UncleAge@druid wrote:
I always liked it, personally.
I agree. Its one of those things that once you see it, you wonder, “Why doesn’t every app do it like this?”
UncleAge😯 I think you did an awesome job considering the circumstance. Based on your description I was expecting it to be horrible. Now that you popped that cherry you can start building that resume’
Thanks for sharing…
UncleAge@druid wrote:
Not ideal; my ideal is the way XT1 (and 2?) does it, which is to have a submenu and then list folders, then .dll files. When it opens that submenu of that folder, it loads that folder at the time.
I don’t think XT1/2 verifies plugins upon startup at all. My understanding is that it verifies them when you load them on a track. And I could be wrong but I’m pretty sure it is the only host that does this.
The two programs that handle this pretty well (IMO) are Tracktion and Studio One. They both do a full scan but they don’t crash on bad .dll’s. They just blacklist them and let you know which plugins failed.
With that said, I like the idea suggested. A plugin mapping/cache that is its own thing that can be managed separately. This would also allow different plugin templates to be managed separately from the project templates. So for instance you could have a mixing template or a mastering template and yet another template for doing voice-overs or podcasts. I have used project templates to handle this process in the past because I don’t like to see the very long list of vst’s that popup in the context menus.
UncleAgeLiquidProj3ct, there’s some good advice coming your way in this thread. I’ll just a add a couple other things that I’ve learned so far. I’m not a pro, but I have recorded others a few times and here’s what I’d add to the quilt:
1. Remember that it’s supposed to be fun. Stress is contagious. If you are relaxed and focused it will translate to the band and make the whole process come out better.
2. You’re the engineer not the producer. Avoid making comments on the performance unless asked.
3. Mic placement will do more towards getting a good recording than almost anything else you do. There is a direct relationship between mic placement and the time it will take to mix the session.
4. Templates are your friend. Once you get the mic levels set, the tracks marked with meaningful names and such, save it as a template. This will allow to move quickly between sets, songs, takes and whatever else. The band will appreciate that when they were ready to go, so were you.
5. Take notes. As many as you need. This will be what you refer to later on when the band is not there and you are mixing the session.
6. Did I mention mic placement? 🙂
Have fun! Can’t wait to hear how things turn out.
UncleAge