justin = { main feed , music , code , askjf , social , pubkey };
Ask Justin Frankel
No reasonable question unanswered since 2009!

Suggested topics: programming, music, sleep, coffee, etc.

Note: please do not ask questions about REAPER features, bugs or scheduling, use the forums instead.


Name: Ask: Human (enter yes):
[unreplied] | [replied] | [all]
[older questions]

Question: ever go back to SF, just to visit? [permalink]
Asked by ROLF (79.246.226.x) on August 25 2016, 9:26pm

Question: seen this interesting language? https://www.gitbook.com/book/ponylang/pony-tutorial/details [permalink]
Asked by semiquaver (107.184.43.x) on August 22 2016, 2:03pm
Reply on August 22 2016, 6:37pm:
    I like the name

Question: The year is 2035. The reiteration of Moore's Law has produced an unprecedented amount of computing power in the average device, exceeding even the most elaborate of science fiction fantasies. A revolutionary new audio program is released that changes audio production forever. What kind of fanciful new features would it have? [permalink]
Asked by fmap (142.162.42.x) on August 22 2016, 12:28pm
Reply on August 22 2016, 6:38pm:
    I'd imagine it would measure your biofeedback and automix until you were pleased?

Question: Any thoughts on using AI for audio processing? (Such as taking a mixed track and breaking it down into stems?) [permalink]
Asked by Will (76.97.150.x) on August 16 2016, 8:05pm
Reply on August 17 2016, 8:17pm:
    I don't know much about AI, I suppose you could train a neural network to pick apart things, but you might run into information theory limits there, I dunno.

Question: hi Justin.I've tried Reaper from /dev in landoleet on Ubuntu studio 16.04 and it works fine. Do you plan an official release in the future. Should i buy a license for this version (will it stop working after 60 days?) [permalink]
Asked by fred (37.164.70.x) on August 16 2016, 12:43pm
Reply on August 17 2016, 8:18pm:
    I won't stop working after 60 days, but if you find it adequate for your uses (most people would probably not), then I suppose purchasing a license would be appropriate.

Question: Ah that's a shame. I'd probably work for free just to say I contributed to Reaper. Although financial sustenance is also great. Reaper's got such a diverse feature set, I figure a few people could work on it without getting in each other's way. You really think it'd be a pain? What about Git access? Maybe a few well-done pull requests would change your mind? [permalink]
Asked by fmap (142.162.42.x) on August 15 2016, 10:10pm
Reply on August 15 2016, 11:06pm:
    If REAPER was open source, that could work... but alas, it isn't. ;)

Question: What languages, and it what order, would you recommend someone learn if they wanted to get into audio/music related programming? And has this answer changed significantly over the past couple decades? [permalink]
Asked by Nick (107.77.76.x) on August 15 2016, 9:10pm
Reply on August 15 2016, 11:08pm:
    I'd say C would be the biggest. Then assembly language (so you understand approximately what code your C compile generates). You can go C++ after that, if you want, but I'd say only use a small percentage of what C++ offers over C (templates, simple classes/single interfaces, etc).

Question: (Whoops, character limit) ...Safe, correct code vs "it works"? Beard vs longer beard? Expertise level between "hello world" and "my toaster has root access to the NSA's mainframe"? [permalink]
Asked by fmap (142.162.42.x) on August 15 2016, 8:05pm
Reply on August 15 2016, 11:11pm:
    To answer the other questions: raw programming ability is important. Being a daily REAPER user is important. Ins and outs of audio production less so. Efficiency in produced code is important, the right amount of design is important (not over, not under, though over is generally a bigger risk). We do minimalist C++, check out WDL (e.g. wdlstring.h, wdlcstring.h, ptrlist.h, lice/) if you want examples. No exceptions. Prefer code that gracefully handles failures. blah blah blah. Beards are overrated.

Question: Any chance you'd hire another dev? If so, what sort of qualities would you be looking for? How important is raw programming ability vs being conversant in the ins and outs of audio production? Flexible high-level interface/architecture design vs low-level efficiency? Strict C style or more OO or functional style? Creative vision vs productivity? Safe, correc [permalink]
Asked by fmap (142.162.42.x) on August 15 2016, 6:56pm
Reply on August 15 2016, 7:55pm:
    Nah, I'm no good at managing people.

Question: Any clue how to go about programming a DAW? [permalink]
Asked by Yobi (144.118.241.x) on August 8 2016, 9:22pm
Reply on August 8 2016, 11:56pm:
    Step 1: collect underpants. Seriously though, maybe start by making plug-ins, or audio processors, or something with a more limited scope?

Question: Your shiz is on hackernews. https://news.ycombinator.com/item?id=12246202 [permalink]
Asked by Will (50.84.190.x) on August 8 2016, 5:50pm
Reply on August 8 2016, 11:56pm:
    Hah thanks though that hasn't been mine for many many years, posted in the comments though :)

Question: Hello :) Is it a good idea to turn off "Use audio driver reported latency" in the recording preferences if i am using Amp Sims like Guitar Rig and therefore the monitoring inside Reaper? Because I guess while playing through Guitar Rig I compensate for the latency myself and therefore the compensation would be done twice ? [permalink]
Asked by Tobias (95.90.212.x) on August 5 2016, 10:16pm
Reply on August 6 2016, 7:14pm:
    There's a per track option for "preserve pdc-delayed monitoring"... it also counts the driver latency along with any pdc

Question: Could you explain to a noob like me what Win32 is responsible for in a 64 bit environment and especially in the coding of REAPER? [permalink]
Asked by Albi (78.159.29.x) on August 5 2016, 9:36am
Reply on August 5 2016, 1:46pm:
    Disregard the "32" in Win32, it really should be "WinAPI" or "Windows API". AFAIK it was called Win32 initially to differentiate it from an earlier API which was 16-bit. On 64-bit it is pretty much the same API, though with many 32 bit values 64 bit.

    What is it responsible for? Pretty much anything you want to do on Windows (there are often other ways that are built on top of Win32, but they'll all use Win32 internally). Open a file, create a window, create a thread, draw to screen, etc.

Question: Fears that M$ will remove Win32 at some point? Tim Sweeney is very vocal about his dislike about UWP. goo.gl/eHX6FG [permalink]
Asked by Gio (79.130.179.x) on August 3 2016, 6:32am
Reply on August 3 2016, 1:17pm:
    I can't imagine them doing that, it would be really idiotic, to throw away decades of backwards compatibility. If they did, though, we'd make SWELL support a UWP backend, I suppose.

Question: Is Brennan like, for real, doing OK? just chillin in sf? miss that dude. [permalink]
Asked by @mhashemi (107.3.131.x) on July 31 2016, 2:43am
Reply on July 31 2016, 6:04pm:
    OK, yes, I think so.

Question: Can you name some of the heaviest bands you listen to? [permalink]
Asked by Albi (91.109.30.x) on July 29 2016, 8:11pm
Reply on July 30 2016, 3:08am:
    Hmm not sure what makes a band heavy... loudness? A few things come to mind, not sure if they qualify: Comets on Fire, Tool, Mogwai, Papier Tigre...

Question: Have you seen Plane9 vis? :) www.plane9.com/ [permalink]
Asked by Will (107.203.156.x) on July 25 2016, 12:15am
Reply on July 26 2016, 2:35am:
    Looks neat!

Question: Why did `pete ultimately write so many audio components for WinAMP? Seems like you're pretty well versed in win32 audio! [permalink]
Asked by Will (107.203.156.x) on July 24 2016, 10:10pm
Reply on July 26 2016, 2:35am:
    I feel like that was after my time?

Question: Have you considered running gitlab for the central repo? We use it at work. It's tits. [permalink]
Asked by Will (172.56.6.x) on July 21 2016, 6:21pm
Reply on July 22 2016, 2:55am:
    Will look at it, but everything working alright now :)

Question: What's the git workflow for the cockos' team? And how you effectively use merge and rebase? Thanks. [permalink]
Asked by Gio (79.130.179.x) on July 21 2016, 12:07am
Reply on July 21 2016, 12:25am:
    We put releases on master, and almost never rewrite master.

    For prerelease builds we have a dev-pub branch, which gets pre_* feature branches (and master) merged, and if all of the pre_* branches graduate, the whole thing gets merged back to master (though sometimes we will rewrite dev-pub to remove branches, or revert the merge of a feature branch to remove it).

    Typically pre_* (or wip_) branches have an implied owner, which doesn't prevent others from committing on those branches, but they do so at the pleasure of the owner.

    If we want to do a maintenance release, we can always do one from master (ideally).

    We keep a central repository which we use to synchronize.
[unreplied] | [replied] | [all]
[older questions]
Copyright 2016 Justin Frankel. | RSS