New project

[sgspecker]

I tried the camtasia.new_project() function today and it failed on Windows.

It looks like the function is expecting to create (or find?) a directory structure associated with Mac .camproj. The new_project function hardcodes with "/", although I cannot remember if python automatically switches to "" automatically, based on the operating system. (I need to go back and look at your book. :-)

I've gotten used to using the os module to build all my paths so that I can run my scripts on either system. (Just started doing that with VBA, too, as many of my old Office macros can now be run on the Mac.)

For reference, here's the code I tried:

import camtasia

NEW_FOLDER = r'C:\Users\sg\Downloads\New folder\_TEST'
new = camtasia.new_project(NEW_FOLDER)

---

As a side note, what I was hoping to do was to create a new project, add two folders worth of media assets (pics and audio). Add the audio to the timeline, then add the associated pictures to the timeline and stretch them to match the length of the audio tracks. Not that difficult to do by hand, but automation would be faster. Hence, my wanting to use new_project().

Next, I'll have to figure out how to play with the timeline. It looks like your API handles manipulating all the project's JSON data, but it always takes some time figuring out a new object model that I've not used before. I'm guessing that you know the feeling.

FWIW,
Scott

[abingham]

Ah, you're absolutely right that I got lazy with my file separator on line 98. I've just pushed a fix for that. I think it worked properly before, but I like the explicitness of os.path.join (or, probably even better, pathlib.Path). Still, I'm a bit puzzled by the error. Is there not a "c:\python37\lib\site-packages\camtasia\resources\new.cmproj" on your system? That should be installed as "package data" with python-camtasia. The idea is that I ship a canned empty project that new projects can always be copied from. What you're trying to do is very much exactly what python-camtasia is designed for. In our case, we have existing audio-only projects. To make our full video, we 1) generate a number of stills and movies 2) copy the audio project 3) use python-camtasia insert the movies and stills in the copied project. This all works very well for us on mac, so I'm sure we can make it work for you on windows. I've got a windows VM around, I think, so I'll test it out when I get a chance. Regarding the API, I'd appreciate any feedback or ideas. It was written very much on-the-fly and in an environment where we're immediately using it as it's written, so it hasn't had the benefit of deep thought or multiple iterations. I'm certain there are areas where I've just approach things from the wrong direction, but I don't know where those are yet...known unknowns.

…

On Wed, Sep 25, 2019 at 10:12 PM Scott Specker ***@***.***> wrote: I tried the camtasia.new_project() function today and it failed on Windows. [image: image] <https://user-images.githubusercontent.com/19363779/65635215-824a0e00-dfa5-11e9-9bd0-e72f7fa534b4.png> It looks like the function is expecting to create (or find?) a directory structure associated with Mac .camproj. The new_project function hardcodes with "/", although I cannot remember if python automatically switches to "" automatically, based on the operating system. (I need to go back and look at your book. :-) I've gotten used to using the os module to build all my paths so that I can run my scripts on either system. (Just started doing that with VBA, too, as many of my old Office macros can now be run on the Mac.) ------------------------------ As a side note, what I was hoping to do was to create a new project, add two folders worth of media assets (pics and audio). Add the audio to the timeline, then add the associated pictures to the timeline and stretch them to match the length of the audio tracks. Not that difficult to do by hand, but automation would be faster. Hence, my wanting to use new_project(). Next, I'll have to figure out how to play with the timeline. It looks like your API handles manipulating all the project's JSON data, but it always takes some time figuring out a new object model that I've not used before. I'm guessing that you know the feeling. FWIW, Scott — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#11?email_source=notifications&email_token=AAATK6BPAVSVFQ3R6GWW2ILQLPA2BA5CNFSM4I2RRAB2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNWPI2A>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAATK6FWNTW46UN4CSTFVOTQLPA2BANCNFSM4I2RRABQ> .

[abingham]

I need to go back and look at your book.

By the way, we hope you're enjoying it! If you'd like a copy of the next book in the series, let me know and I'll fix one up for you.