Hi, folks.

I'll be using this thread to maintain the latest versions of EOF in one place. To start, download and extract EOF 1.8RC13:
https://ignition4.customsforge.com/eof

You can keep that zip file handy to avoid downloading it more than once. When I release a new hotfix, all you have to do is replace the files from the above zip file with the ones from the hotfix.  The latest hotfixes get posted in the same place:
https://ignition4.customsforge.com/eof

*If you use a non QWERTY US English keyboard layout, and keyboard controls/shortcuts aren't working for you, please make a post describing what keyboard shortcuts aren't working, and what the Info panel says the "CODE" and "ASCII" values are after you use each of the keyboard controls in question.

I used to make Mac releases, but Apple dropped support for 32 bit applications so the user base dwindled away and I can't port the entire application to 64 bit at this time.  The latest Mac build (2-7-2025) is here:
https://ignition4.customsforge.com/eof/download/17
Unless you have oggenc and LAME installed (these don't come with the Mac build for licensing reasons), you won't be able to have EOF automatically convert from MP3 to OGG when you create a new chart. If you have trouble getting those set up on your system, here is a package that should get them installed and usable by EOF:
http://www.t3-i.com/apps/eof/downloads/eof_utilities.pkg

Please provide any and all feedback, including bugs and feature requests. If possible, also please review the included documentation (manual, tutorials) and let me know if you find any room for improvement there. Eventually I plan to add a Rocksmith authoring section to the pro guitar tutorial, but the community's knowledge of the Rocksmith songs' makeup changes pretty quickly so it's hard to know when particular features are considered fully known. For any features that ARE fully known (like anchors), please feel free to remind me if they aren't incorporated into EOF yet, in case I missed any information being passed around on this forum or the Google group.

Note: If you are reporting a bug, please specify which hotfix (date) you're using. I release hotfixes on a somewhat random schedule, sometimes more than once per day, so the issue being reported may have been fixed in a release you haven't tried yet.

Hi, it's me again :P. I'm using Canadian Multilangue keyboard layout... I noticed that I can extend sustains, but I can't make them smaller... ''ç'' works (it's supposed to be ] for US) but ^ doesn't (which is [ for US).

EOF is already using scan codes to read those keys, so it should read the same regardless of keyboard layout. If that's not the case, there's may be nothing I can immediately do about it. What code and ASCII numbers does EOF report in the Information panel when you press the "^" key?

Actually, it doesn't update at all. It would be the last key I pressed before.

@@Alternity, because something vvrong vvith that symbol\key http://www.microsoft.com/resources/msdn/goglobal/keyboards/kbdcan.html

 

also http://superuser.com/questions/743920/how-to-type-french-specific-characters-on-a-standard-us-keyboard-on-windows-usin

Well that's annoying, but I can understand that's how accent keys are meant to work. The other way to lengthen/shorten notes is by using the mouse's scroll wheel. If you don't have a scroll wheel on your mouse, it kind of limits your options and you'd be stuck with changing the OS' keyboard layout for EOF (it may be able to track this on a per application basis?) or getting a spare mouse with a scroll wheel.

If you don't have a scroll wheel on your mouse,

 

WHAT YEAR IS THIS?

@@SmellyOrc, touchpad, mthfkr :D

If you're using a notebook/laptop, you know it has USB ports that you can use to hook up a mouse, right? :huh:

If you're using a desktop and still using a touchpad, you'd better find a mental hospital. ;)

If you're using a notebook/laptop, you know it has USB ports that you can use to hook up a mouse, right?

Maybe not certain Mac laptops or tablet-style Windows laptops.

If you're using a notebook/laptop, you know it has USB ports that you can use to hook up a mouse, right? :huh:

If you're using a desktop and still using a touchpad, you'd better find a mental hospital. ;)

 

Sometimes I have to use a touch screen PC with no mouse and no keyboard.  Very frustrating and I end up using a lot of very bad words.

Well that's annoying, but I can understand that's how accent keys are meant to work. The other way to lengthen/shorten notes is by using the mouse's scroll wheel. If you don't have a scroll wheel on your mouse, it kind of limits your options and you'd be stuck with changing the OS' keyboard layout for EOF (it may be able to track this on a per application basis?) or getting a spare mouse with a scroll wheel.

I didn't know I could do that with the wheel. Keyboard doesn't really matter now, thanks!

Thinking about the transpose between strings feature, @@Alex360 was looking into writing such logic before, but I don't know if that's something he's still working on.

@@raynebc, vvell I have some Ideas about this,hit me vvhen you'll start to  codeit, I'll share vvhat I've got ;)

@@raynebc,another uestion\idea, I knovv EOF can search for note opatterns from  catalog, so vvouldit search for note patterns for seleted notes vv\o adding it to catalog? I just messed up vvith fixing errors in my songs and Catalog is ver hand for that :D

I'm sure it would be pretty easily do-able for me to do that, although they'd probably need to share the same menu functions (since the menu is already really crowded) and keyboard shortcuts (since those are in short supply). I'd just need to determine a good way to determine whether to search for the selected notes' pattern or the catalog entry's pattern, perhaps:

*If the fret catalog is being displayed, search by catalog entry.

*If the fret catalog is not being displayed, but notes are selected, search by selected notes.

Let me know if that sounds like it would do it.

Is it just me or is raynebc's labour of love EoF infinitely more enjoyable to work with than what this Rockband authoring video demonstrates.

 

http://ca.ign.com/videos/2015/05/08/how-a-rock-band-song-gets-made-ign-first

 

Kudos to you raynebc!

 

This video almost looks like they are working in Microsfot Excel, yuck!

Is it just me or is raynebc's labour of love EoF infinitely more enjoyable to work with than what this Rockband authoring video demonstrates.

 

http://ca.ign.com/videos/2015/05/08/how-a-rock-band-song-gets-made-ign-first

 

Kudos to you raynebc!

 

This video almost looks like they are working in Microsfot Excel, yuck!

Well, they are just using midi tracks in Reaper for charting and Reaper isn't really a very good looking DAW in itself, imo, but when combined with the midi editor layout it looks especially unappealing.

So you're right. Kudos to raynebc for a piece of software that looks a lot better and is more intuitive to work with.

I'm working with both Reaper and EoF. I must say both have good and bad sides, but personally, if pro/adv/real keys would be supported in EoF, I really doubt I'd be using Reaper.

I'm still interested in working on pro keys support some day. Pro guitar always interested me more, plus it's a bummer that the Rock Band franchise is dropping the keys instrument. Synthesia isn't quite a game, but if they ever added support for a backing track it would be much more like a rhythm game and I would make it a priority.

Hi, folks. The latest hotfix (r1404) is in the first post. Changes are as follows:

*Fixed a bug where using Beat>Add, Beat>Delete or "Beat>Delete anchor" where a non #/4 time signature and the accurate TS song property were in effect would move beats into the wrong positions.

*Improved the accuracy of the grid snap logic.

*Fixed the secondary piano roll logic so that when swapping piano rolls, EOF's title bar reflects the correct active difficulty.

*Corrected the Track>Rename function to begin with the input field empty if the track doesn't have a custom name already.

*Fixed a GP import bug where chords that contained both tie notes and normal notes would be imported as all normal notes. It now will import only the normal notes as intended, making the import look much closer to the original tablature.

*Improved GP import so that tie notes having a different strum direction definition than the connected note won't cause it to import as a separate linked note. If it was intended to be a separate played note, it would be authored as such in the GP file.

*Fixed a GP import bug where slide notation may not be imported in some circumstances.

Thanks a lot, that's just peaches now :D

 

 

 

Edit - that revision is severly broken I'm afraid.  Drag some beat markers about on a populated track and you will see what I mean.  It's doing very weird and very destructive things.

 

I made a quick vid

 

I've always wondered but never asked, is there a reason why we can't use .GPX files? 

@@Brooklyn_Sounds, It's just FS for gp5 like files, there is code in python and C# for gpx I knovv, plus it's time  consuming to implement?

Edit - that revision is severly broken I'm afraid.  Drag some beat markers about on a populated track and you will see what I mean.  It's doing very weird and very destructive things.

 

 I encountered the same problem this morning on a new song with the release 1404.

 I needed to delete all notes and reimport them after a beat move ...

@@Brooklyn_Sounds, It's just FS for gp5 like files, there is code in python and C# for gpx I knovv, plus it's time  consuming to implement?

Ok, i thought it had to do with code. Thanks for the info @Alex360.  :D