Jump to content
Hash, Inc. Forums


*A:M User*
  • Content Count

  • Joined

  • Last visited

  • Days Won


DrPhibes last won the day on March 22

DrPhibes had the most liked content!

Community Reputation

1 Known

About DrPhibes

  • Rank

Contact Methods

  • MSN
  • Website URL
  • ICQ

Profile Information

  • Name
    Charles Babbage
  • Location
    Portland, Oregon

Previous Fields

  • A:M version
  • Hardware Platform
  1. Solved the problem! It has everything to do with the files names! I shortened all the files names and it worked fine! I don't know why the longer files names work on other PCs. All of my machines are Windows 10. Thanks for all your help in trying to sort this out Robert! CB
  2. Recorded a new WAV - Works! Split original and save - Did not work Merged to mono and save - did not work
  3. That worked! Did you simply merge the tracks in Audacity and export to the 44.1kHz? I tried to do that just now and my file did not work, but yours worked fine.
  4. Yeah, and it works fine for me on other machines, but not on this one. All the files you sent me DO work fine here, so this is a mystery. I can't tell what the difference is in the files. I thought maybe about saving out as a entirely different format and then back to a wav. I said Audacity above when I meant Adobe Audition. I should try Audacity.
  5. Both work equally well. Import and playback without error.
  6. I can't post publicly, but I sent you a link via a PM. I thought it was because of the different sample rates. Yours was 32kHz and my original was a 48kHz, but after saving out several from Audacity changing to various sample rates, none of them worked. So there is something else different about your wav file than mine that I am missing. What software are you using when you edit or save wav files? CB
  7. That worked! What is the difference there?
  8. Thanks for at least something to try. It did not work, but it gave me hope for at least a minute CB
  9. [Solution: shorten filename] Has anyone else ever had an error dropping in a wave file into a project? I have several PC's I work on and everything is great when importing an audio file, but on one machine I get "trouble opening mci device error: 304" on this Windows 10 machine. The wave file imports, but there is no audio playback. I so I assume it's that machine and look to make sure all drivers are current and can't replicate the problem in any other app other than A:M. I can import an MP3 and that has playback no problem. Unfortunately I am noticing sync problems and it does not display a waveform in the timeline. Probably because MP3 is not fully supported yet. These kind of problems are maddening. I can't find any info on a MCI error 304 to help troubleshoot this and I don't know what A:M is specifically doing when it loads the audio file and how is accesses libraries and such. Probably on my own here but I thought I would ask. Charles
  10. I have played with this a bit, but I think I am missing something. I am getting a syntax error. Have you tried it?
  11. Hmm, I will need to research this more. This sounds promising. So then what you are saying is that on a x scale channel for example, an expression is linked to it to force the spline in the timeline to display the acceleration curve?
  12. Thank you for all your efforts Robert! To address your comment in the video about using the translate channel (or any other channel) as the source of our motion data in the conversion to the controller, this is exactly what I planned to do if there was not an easy automated way to get there with pose sliders. The 0 to 100 values, and the small size of an action file with the ability to parse out the channels from logically named pose sliders was nice. I can get to the 0 to 100 values in other ways with constraints, but when parsing the data it requires more effort due to the duplicate naming. Search a project file for "matchname =Z" and see how many hits you get I had played with some of the text editing solutions to transfer the channels as well. I think you have definitively shown that I need to stick with our first version of the tool that pulled from a position channel.
  13. It is a tool we wrote internally. It is a separate app that we wrote that is a basic converter to translate to the controller hardware we use, and we added some features to help with the real world issues of acceleration and deceleration limits of the actuators. I hope to at some point develop this stuff into an A:M plugin(s) that allows me to see in realtime on a timeline an overlay of an acceleration curve with the current position over time spline. This would allow me to animate to the limits preset into the plugin and make sure that nothing is moving in a way it can't in reality without having to save out and bring back in. When we did this during our first tests we just created an Excel project that did all of this conversion.
  14. Robert, This is getting so close to where I need to be. But yes, getting the pose sliders to record key frames would be ideal. I came across another issue I overlooked as I was working through this with you. In my other projects because of their simplicity, I can just use key framed pose sliders in an action, export that action, run it through the filtering software to refine any acceleration or deceleration issues, then import that edited action file back in to A:M, drop it on the model and watch the play back to visualize the changes. This ability goes away to some degree with the expressions. What I think I need to do is build an animation rig and a separate playback rig if I continue down this path.
  15. So to answer the first question, yes, expressions could probably be made to do what I want in this case. So the example you provided in the video was based on the "demo02" action I set up where I hand animated the actuator to match the gimbal motion. In this case if I hand animate the poses then I get what I need in the pose sliders and there is no need for a baking step. I placed this action in there to demonstrate the end result I was looking for. Look at the "demo01" action. You will see that the actuators are not moving. This is the where I would like to find a rig setup to automatically move the actuators to match the gimbal motion. Also, yes, it is true I can pull the translate value out of file and run that to the controller. It does create an extra step because I will need to process that separately from the other motions pulled from pose sliders. In fact our first version of the translation tool worked specifically on bone rotation values and not pose slider positions.
  • Create New...