Jump to content

msa

Member
  • Content Count

    22
  • Joined

  • Last visited

About msa

  • Rank
    Member

Profile Information

  • Location
    Cusco, Peru

Recent Profile Visitors

614 profile views
  1. That did the trick, I uninstalled blueutil from homebrew, called the workflow and downloaded the utility in the shared_resources as you mentioned. Great thanks for the help!
  2. Great workflow, just wanted to point out that the update (via OneUpdater) didn't seem to connect for some reason to the blueutil located in the shared_resources directory so broke the workflow, however I installed blueutil via homebrew as you recommended and it works again. Not sure why it didn't connect but just wanted to let you know. I can send you the debug report if you like.
  3. Flow: A Minimal Project Management Workflow Flow is an Alfred workflow that provides a File Action for quick project management processes written in Bash. It's a minimal solution for tasks and project management that stays out of your way so you can stay focused. Version 1.1 Updates 1. More simplicity for the workflow variable declarations. You can now declare your variables with the standard path syntax such as notes=~/Documents/Notes. 2. Also in version 1.1, the tag cli tool is included for those who do not have it installed via homebrew so you do not need to install it.
  4. Right, that too helps. I should have been clearer with my phrasing but you both answered and helped me make sure I don't make that mistake and accidentally change it globally. This was what I started with in my script but as @vitor and you have pointed out now, it was useless because it was in a script. I'll do some more digging with this topic on my own just to make sure I'm super clear with it. Thanks everyone!
  5. Is there a way to mark this question as Solved/Answered?
  6. Got it! Simply brilliant @vitor. So many users here are wonderfully helpful, this is a great community. I love this path.
  7. Hi @deanishe, sorry it took me some time to get back to this - duty called. So from what I understand now, all my bash scripts will execute in their own subshells and therefore variables (like the IFS setting) are basically local to that script and will not pollute the parent shell is that correct? If I were to create a function instead of a script however, then that runs in the parent shell correct? I just want to make sure i'm on the right path here. From what I understand though, subshells execute slower and use more processes so should would you recommend I should be looking at a different
  8. Thanks @vitor, very kind and succinct. Exactly what I was looking for. I had no idea that IFS setting in a script doesn't change anything outside the script so I was being as safe as possible (intention). The rest of your feedback is excellent and I'm embarrassed at missing the elif but thankful for catching that. Also, shellcheck - I had never used that before and it's exactly what I needed. I've picked up a lot today and looking forward to implementing the changes. Have a great day/night everyone.
  9. As promised, here is the working code for anyone interested for my workflow script added below. I welcome any feedback. The script takes folder/file input and searches through the input for any video files and creates lo-res proxies suitable for importing into an NLE (e.g. Premiere Pro) and organizes the hi-res and lo-res footage into their respective directories. It's not ready for public as I'll add the ability to specify the proxy width in the next version, it's currently hard coding the proxies at 640px wide. #!/usr/bin/env bash # SET PATH TO SHARED RESOURCES PATH="$(./_shared
  10. Thank you so much everyone! I have the workflow working now thanks to your help. I leave the details below to help anyone else that has a similar question. Firstly, I do apologize for not copying the script here, I wasn't intending to debug the script (since it was working locally) as much as understanding the bundling process. In hindsight, I see it would have helped and thank you all for your patience in my short sightedness. Secondly, this was a great pointer for me to understand how to optimize exporting workflows. I've been creating different workflow processes for the
  11. Hello! I know I'm missing something basic here - I have a workflow that works great on my computer and I'd like to finally export it out to install on another computer. Because it's just a bash script that references the ffmpeg binary (installed in /usr/local/bin via homebrew) I've copied over the ffmpeg binary to the workflow folder and got it to work - on my computer. When I install it on another user's computer I get the error "Library not loaded: /usr/local/Cellar..etc." which makes sense since that user hasn't installed homebrew nor the ffmpeg. What I'm looking for
  12. Good morning and thank you Deanishe - so much. I'll get the hang of the forum space I promise, sorry about that : ). That said, thanks not only for the help but the direction. Happily I can get ffmpeg at least recognized as I better understand the PATH issue. I'll be spending more time with the variables and getting to better understand them. I'm really happy with Alfred and have been wanting to take it up another level for quite some time. Your resources are extremely helpful. Have a great rest of your Afternoon! -MSA
  13. Hello everyone, first off thanks for checking in with this hopeful simple question. I'm trying to write my first simple workflow that incorporates user input, saves the arguments as variables and then passes them into the script to run. I've debugged it through Alfred and all the variables are coming through fine. The problem comes when I try to run and compile the variables into the script. Here is the script I'm trying to run: ffmpeg -i {var:file-location} -b {var:v-bitrate} -r {var:frame-rate} -ar {var:sample-rate} -ab {var:a-bitrate}k {var:file-location} Now as I'm a firs
×
×
  • Create New...