Jump to content

SRF_Audio

Member
  • Posts

    222
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SRF_Audio's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. Ok, so adding some more specificity. I was having that issue in one project. I opened a new empty project and tried the same thing on a single region. In the new project, it did allow me to select notes, but I was able to get the behavior to reproduce after deleting a note. So, let's say we enter 4 quarter notes. Now, I want a rest on beat 3. Command+Option+K to close Step Input, left arrow to select beat 3, and delete. Now press left and right arrow. The score editor is still in Key Focus, but you can't select any notes, even after changing key focus back and forth.
  2. Nice! Yeah, so the Factory method is essentially defining all of the variable cases with the integer values that each case needs? Again, this is where my coding inexperience really hurts me. I'm following everything in the script, but coming up with that and putting it in the correct order into the correct syntax is where I'm really weak. I tried a few different versions of this, but I just never quite got it into the right syntax for it to work as expected. Again, so cool. Thank you.
  3. I meant other variable definitions in the header of the script. So, for example, CC's or notes.
  4. Man...please let me know when this is done. I would love to take a look at this under the hood...and I know a lot of people would find this useful.
  5. Hello all, This has been driving me nuts, and I'm hoping that I'm just missing something. So let's say you're building a new part using the Step Input into the score editor. Create a region on a software instrument track. Command+Option+K, enter a few notes. Hit it again to turn off step editor. The score editor is still in key focus. Now use the arrow keys to navigate to the next MIDI event on the score...and nothing. Strangely, Shift+Up/Down will work by selecting highest or lowest notes, and then you can use the arrow keys normally. But otherwise, it's really frustrating to not be able to immediately navigate between the events you just created. Is it my system, or is this an actual bug?
  6. So cool man! Thanks. And really, in theory, this script should be able to send *any* MIDI message as long as it's entered as a new var entry, yes?
  7. Hey Dewdman42, just wanted to follow up to say thanks. I gave you a big shout out in my recent tutorial on this topic: And also, good call on needing an instrument. That solved it!
  8. I've been reading through the Effects manual, and your code looks correct...I don't know why it's not working. BUT, I did find a pretty useful workaround for future reference. In the Scripter Presets under Factory->Tutorial Scripts->9- NeedsTimingInfo and GetTimingInfo you can essentially get the same information...it just won't be filtered by PC's. It will display the beat position value from where ever you hit play, so you can quickly go through your hit points and log the beat position.
  9. Dewdman42, Ok, I actually do need a bit of help with the script that prints beat position to the console. I've cut and pasted the script, and it's on a MIDI track with PC's, but no output to the console.
  10. Ah geez...never mind. Math in public. I forgot to subtract 3 beats to get the previous downbeat. *sheepish grin* It works great man. Thank you so much. This is just incredible.
  11. @Dewdman42 Gotcha. Actually, quick question if you've got some time. I'm using your script, and I successfully got PC's triggering patch changes, but the beat position timing doesn't seem to correspond correctly. Maybe I'm not doing my beat position math correctly? For example, I'm trying to have a patch change at beat 1 of Bar 8. So I did the math (4*8=32, +1 for the downbeat)...but when I hit play, the patch change occurs at Bar 25 Beat 4. Any ideas?
  12. Dewdman42, I just need you to know that you are so awesome. Thanks for taking the time to both write the script and share it. I have done every method of automating MainStage up until scripting, and all of them had pros and cons. I knew scripting would end up being the solution, but my programming chops just aren't there yet. (I'm doing the first few lessons on Java with Codeacademy right now). This saves me so much time and effort, so thank you very much.
  13. Thanks Dewdman. I haven't messed with it since a few weeks ago, but when I was in there working with it...it seemed to trigger the beat clock at a totally weird time scale. I had Snoize MIDI monitor open so I could see when things were happening, and it was just all over the place. I couldn't get an accurate view of when it was triggering the file, vs. when Mainstage received and responded. I'll work on it some more next week and get back to you guys. This has been almost a 2 year quest to get this "Mainstage fully automated" pipe dream to come true. I was using another method, that worked (sort of)...but the IAC bus is so damn unreliable in it's MIDI timing.
  14. That kinda makes sense. might rethink using 88.2k again. I split it up by task. For sound design, foley, SFX, etc. I record everything at 96Khz. For music projects and instruments, I record at 48Khz, and even that is just for video compatibility. Otherwise, 44.1 is fine. The big disadvantage to higher sample rates is, of course, increased file size.
  15. Important to note though, the material must actually be recorded at the higher sample rate. Upconverting a file originally recorded at 44.1Khz gives no benefit.
×
×
  • Create New...